Cisco ASR CPU monitoring
The outcome I want from LLD is:
cpu R0/0 utilization: X%
The difficult is in using LLD with zero hard coding.
The entity name cpu R0/0 is stored here: .1.3.6.1.2.1.47.1.1.1.1.7.131
mib-2.entityMIB.entityMIBObjects.entityPhysical.entPhy sicalTable.entPhysicalEntry.entPhysicalName.131 = STRING: "cpu R0/0"
X is stored here: .1.3.6.1.4.1.9.9.109.1.1.1.1.3.7
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoP rocessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTot alEntry.cpmCPUTotal5sec.7 = Gauge32: 10
The INDEX of the entity name cpu R0/0 is referenced here: iso.3.6.1.4.1.9.9.109.1.1.1.1.2.7 = INTEGER: 131
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoP rocessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTot alEntry.cpmCPUTotalPhysicalIndex.7 = INTEGER: 131
I need a discovery rule which walks the cpmCPUTotalPhsicalIndex, stores that value, then uses it the NAME of an item prototype like .1.3.6.1.2.1.47.1.1.1.1.7.{#INDEXMACRO} with a value OID of .1.3.6.1.4.1.9.9.109.1.1.1.1.3.7
The issue is that the SNMP INDEX between the ciscoCPUTotalEntry table and the entityPhysical MIB are not the same, but referenced.
I've been able to work around every other limitation (and raise tickets for what I've found) I have found, but this one is proving a bit much without resorting to a bash/python script.
Specific advise would be appreciated.
cpu R0/0 utilization: X%
The difficult is in using LLD with zero hard coding.
The entity name cpu R0/0 is stored here: .1.3.6.1.2.1.47.1.1.1.1.7.131
mib-2.entityMIB.entityMIBObjects.entityPhysical.entPhy sicalTable.entPhysicalEntry.entPhysicalName.131 = STRING: "cpu R0/0"
X is stored here: .1.3.6.1.4.1.9.9.109.1.1.1.1.3.7
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoP rocessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTot alEntry.cpmCPUTotal5sec.7 = Gauge32: 10
The INDEX of the entity name cpu R0/0 is referenced here: iso.3.6.1.4.1.9.9.109.1.1.1.1.2.7 = INTEGER: 131
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoP rocessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTot alEntry.cpmCPUTotalPhysicalIndex.7 = INTEGER: 131
I need a discovery rule which walks the cpmCPUTotalPhsicalIndex, stores that value, then uses it the NAME of an item prototype like .1.3.6.1.2.1.47.1.1.1.1.7.{#INDEXMACRO} with a value OID of .1.3.6.1.4.1.9.9.109.1.1.1.1.3.7
The issue is that the SNMP INDEX between the ciscoCPUTotalEntry table and the entityPhysical MIB are not the same, but referenced.
I've been able to work around every other limitation (and raise tickets for what I've found) I have found, but this one is proving a bit much without resorting to a bash/python script.
Specific advise would be appreciated.