Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Enterprise Edition
Description
Bonjour,
Nous avons remarqué une incohérence sur la valeur affiché sur la partie memory des 7705.
Sur Observium nous avons une valeur que nous savons pas à quoi cela correspond car lorsqu'on va sur le routeur nous ne trouvons cette valeur nul part.
Exemple :
La valeur sur Observium:
La valeur sur le 7705:
===============================================================================
Memory Pools
===============================================================================
-------------------------------------------------------------------------------
Current Total Size : 1,140,495,992 bytes 1.3.6.1.4.1.6527.3.1.2.1.1.
Total In Use : 483,283,848 bytes 1.3.6.1.4.1.6527.3.1.2.1.1.2
Available Memory : 613,114,160 bytes 1.3.6.1.4.1.6527.3.1.2.1.1.3
===============================================================================
Pourriez vous nous indiquer a quoi correspond la métrique sur Observium svp?
Attachments
Activity
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Assignee | Original: Mike Stupalov [ landy ] | New: Adam Armstrong [ adama ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Pending Response [ 10000 ] | New: Resolved [ 5 ] |
Hi,
I can't read french, but i assume this is a Nokia 7705 showing inaccurate memory metrics?
You can see where these are being collected/discovered with:
./discovery.php -h <device_id> -m mempools
./discovery.php -h <device_id> -m mempools
It looks like we're using the wrong OIDs to select the total. It looks like we need to use sgiMemoryPoolAllocated + sgiMemoryAvailable as "total", instead of just sgiMemoryPoolAvailable.
The way the device reports this is somewhat messy. They show "not allocated to pools", "allocated to pools" and "used within pools".
This should now be fixed in revision 11951.
adam.
| Component/s | New: Default [ 10900 ] |
| Assignee | Original: Adam Armstrong [ adama ] | New: Mike Stupalov [ landy ] |
| Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
This comment is added automatically.
Hi Adam,
Yes that's it.
Thank you for your assistance.