olaf
21 April 2021 19:31
#1
Hi,
has anybody experience with Cisco UCS CIMC? It is displayed as generic device but if i do a snmpwalk I can see some informations. It’s quiet new. Do I need to configure anything? validate is ok
Here the output from snmpwalk.
/usr/bin/snmpwalk -v2c -c .1.3.6.1.4.1.9.9.719.1
iso.3.6.1.4.1.9.9.719.1.9.6.1.2.1 = STRING: “sys/rack-unit-1/board”
iso.3.6.1.4.1.9.9.719.1.9.6.1.3.1 = STRING: “board”
iso.3.6.1.4.1.9.9.719.1.9.6.1.4.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.5.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.6.1 = STRING: “UCSC-C240-M5SX”
iso.3.6.1.4.1.9.9.719.1.9.6.1.7.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.8.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.9.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.10.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.11.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.12.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.6.1.13.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.6.1.14.1 = STRING: “WZP2449Z0LW”
iso.3.6.1.4.1.9.9.719.1.9.6.1.15.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.16.1 = STRING: “Cisco Systems Inc”
iso.3.6.1.4.1.9.9.719.1.9.6.1.17.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.35.1.2.1 = STRING: “sys/rack-unit-1”
iso.3.6.1.4.1.9.9.719.1.9.35.1.3.1 = STRING: “rack-unit-1”
iso.3.6.1.4.1.9.9.719.1.9.35.1.4.1 = INTEGER: 31
iso.3.6.1.4.1.9.9.719.1.9.35.1.5.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.6.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.7.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.8.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.9.1 = Gauge32: 393216
iso.3.6.1.4.1.9.9.719.1.9.35.1.10.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.11.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.12.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.13.1 = STRING: “ESX11”
iso.3.6.1.4.1.9.9.719.1.9.35.1.14.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.15.1 = Counter64: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.16.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.17.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.18.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.19.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.20.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.21.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.22.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.23.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.24.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.25.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.26.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.27.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.28.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.29.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.30.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.31.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.32.1 = STRING: “UCSC-C240-M5SX”
iso.3.6.1.4.1.9.9.719.1.9.35.1.33.1 = STRING: “UCS C240 M5SX”
iso.3.6.1.4.1.9.9.719.1.9.35.1.34.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.35.1 = Gauge32: 24
iso.3.6.1.4.1.9.9.719.1.9.35.1.36.1 = Gauge32: 2
iso.3.6.1.4.1.9.9.719.1.9.35.1.37.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.38.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.39.1 = Gauge32: 48
iso.3.6.1.4.1.9.9.719.1.9.35.1.40.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.41.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.42.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.35.1.43.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.44.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.45.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.35.1.46.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.47.1 = STRING: “WZP24500DEK”
iso.3.6.1.4.1.9.9.719.1.9.35.1.48.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.49.1 = Gauge32: 393216
iso.3.6.1.4.1.9.9.719.1.9.35.1.50.1 = STRING: “xxxxxxxxx”
iso.3.6.1.4.1.9.9.719.1.9.35.1.51.1 = STRING: “Cisco Systems Inc”
iso.3.6.1.4.1.9.9.719.1.9.35.1.52.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.53.1 = Gauge32: 24
iso.3.6.1.4.1.9.9.719.1.9.35.1.54.1 = INTEGER: 2
iso.3.6.1.4.1.9.9.719.1.9.35.1.55.1 = Gauge32: 2400
iso.3.6.1.4.1.9.9.719.1.9.35.1.56.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.56.1 = No more variables left in this MIB View (It is past the end of the MIB tree)
Hello @olaf
It probably means LibreNMS does not yet know about this CIMC. According to the YAML file here includes/definitions/cimc.yaml
, right now, the discovery recognise CIMC using sysdescr :
discovery:
-
sysDescr:
- 'Cisco Integrated Management Controller'
So you need to check how sysDescr looks like on yours, and probably add a new line with the new sysDescr syntax.
For instance :
discovery:
-
sysDescr:
- 'Cisco Integrated Management Controller'
- 'New Version Cisco Integrated Management Controller'
When done, you can submit a Pull Request so we can integrate this into LibreNMS. This will ensure updates will not try to overwrite your patched YAML file.
Bye
1 Like
olaf
23 April 2021 04:40
#3
Hi PipoCanaja,
thank you for the reply.
unfortunately, it is not the solution. I have tried to add the PID or Product Name (UCSC-C240-M5SX // UCS C240 M5SX) which you can see in the snmpwalk. Should I see in the snmpwalk the STRING
“Cisco Integrated Management Controller” ?
This is all what I can read:
/usr/bin/snmpwalk -v2c -c xxxxxx 10.99.1.51 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.2.1 = STRING: “sys/rack-unit-1/board”
iso.3.6.1.4.1.9.9.719.1.9.6.1.3.1 = STRING: “board”
iso.3.6.1.4.1.9.9.719.1.9.6.1.4.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.5.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.6.1 = STRING: “UCSC-C240-M5SX”
iso.3.6.1.4.1.9.9.719.1.9.6.1.7.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.8.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.9.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.10.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.11.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.6.1.12.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.6.1.13.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.6.1.14.1 = STRING: “WZP2449Z0LW”
iso.3.6.1.4.1.9.9.719.1.9.6.1.15.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.6.1.16.1 = STRING: “Cisco Systems Inc”
iso.3.6.1.4.1.9.9.719.1.9.6.1.17.1 = INTEGER: 100
iso.3.6.1.4.1.9.9.719.1.9.35.1.2.1 = STRING: “sys/rack-unit-1”
iso.3.6.1.4.1.9.9.719.1.9.35.1.3.1 = STRING: “rack-unit-1”
iso.3.6.1.4.1.9.9.719.1.9.35.1.4.1 = INTEGER: 31
iso.3.6.1.4.1.9.9.719.1.9.35.1.5.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.6.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.7.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.8.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.9.1 = Gauge32: 393216
iso.3.6.1.4.1.9.9.719.1.9.35.1.10.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.11.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.12.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.13.1 = STRING: “ESX11”
iso.3.6.1.4.1.9.9.719.1.9.35.1.14.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.15.1 = Counter64: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.16.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.17.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.18.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.19.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.20.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.21.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.22.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.23.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.24.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.25.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.26.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.27.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.28.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.29.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.30.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.31.1 = INTEGER: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.32.1 = STRING: “UCSC-C240-M5SX”
iso.3.6.1.4.1.9.9.719.1.9.35.1.33.1 = STRING: “UCS C240 M5SX”
iso.3.6.1.4.1.9.9.719.1.9.35.1.34.1 = Gauge32: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.35.1 = Gauge32: 24
iso.3.6.1.4.1.9.9.719.1.9.35.1.36.1 = Gauge32: 2
iso.3.6.1.4.1.9.9.719.1.9.35.1.37.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.38.1 = Gauge32: 0
iso.3.6.1.4.1.9.9.719.1.9.35.1.39.1 = Gauge32: 48
iso.3.6.1.4.1.9.9.719.1.9.35.1.40.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.41.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.42.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.35.1.43.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.44.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.45.1 = INTEGER: 10
iso.3.6.1.4.1.9.9.719.1.9.35.1.46.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.47.1 = STRING: “WZP24500DEK”
iso.3.6.1.4.1.9.9.719.1.9.35.1.48.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.49.1 = Gauge32: 393216
iso.3.6.1.4.1.9.9.719.1.9.35.1.50.1 = STRING: “FEE3AFD5-A468-4A0B-BDCE-DACB84B95020”
iso.3.6.1.4.1.9.9.719.1.9.35.1.51.1 = STRING: “Cisco Systems Inc”
iso.3.6.1.4.1.9.9.719.1.9.35.1.52.1 = INTEGER: 1
iso.3.6.1.4.1.9.9.719.1.9.35.1.53.1 = Gauge32: 24
iso.3.6.1.4.1.9.9.719.1.9.35.1.54.1 = INTEGER: 2
iso.3.6.1.4.1.9.9.719.1.9.35.1.55.1 = Gauge32: 2400
iso.3.6.1.4.1.9.9.719.1.9.35.1.56.1 = “”
iso.3.6.1.4.1.9.9.719.1.9.35.1.56.1 = No more variables left in this MIB View (It is past the end of the MIB tree)
olaf
23 April 2021 04:48
#4
I think it is still Cisco Integrated Managment Controller because the WebGui shows this
Check the result of :
/usr/bin/snmpwalk -v2c -c xxxxxx 10.99.1.51 1.3.6.1.2.1.1.1
This is the string we parse right now, and that should be equal to “Cisco Integrated Management Controller” to recognise the CIMC. I bet they changed slightly the reply of this OID.
olaf
23 April 2021 07:28
#6
/usr/bin/snmpwalk -v2c -c xxxxxx 10.99.1.51 1.3.6.1.2.1.1.1
iso.3.6.1.2.1.1.1 = No Such Object available on this agent at this OID
Are you sure your SNMP configuration is completely opened in CIMC ? I suspect you have some kind of filtering on the OID replies. Because sysDescr is completely standard and almost mandatory. I would be very surprised Cisco removed it.
Sometimes, filtering is called “snmp view”. It should be set to “.” or “1” to ensure all the SNMP tree is visible.
olaf
23 April 2021 10:44
#8
Ok, I will ask my colleague next week. He is the expert for servers.
olaf
26 April 2021 11:30
#9
you were right, the snmp view was limeted. My colleague has changed this.
I added as string “Cisco Integrated Management Controller(Cisco IMC)” in the yaml-file and now it works (now with snmpv3)
system
Closed
3 May 2021 11:31
#10
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.