Cisco Bug: CSCvs15821 - SNMP OID 220.127.116.11.18.104.22.168.22.214.171.124.1.7.1 returns STRING instead of HEX STRING.
Aug 24, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
10.5(2.10000.5) 11.5(1.10000.6) 12.0(1.10000.10) 12.5(1.10000.22) 12.5(1.11900.146)
Symptom: We could see for some CUCM IP's the 126.96.36.199.188.8.131.52.184.108.40.206.1.7.1 respond with STRING as below, ideally the response should be a HEX STRING [root@romulus108 ~]# snmpwalk -c public -v2c localhost 220.127.116.11.18.104.22.168.22.214.171.124.1.7.1 SNMPv2-SMI::enterprises.126.96.36.199.188.8.131.52.1 = STRING: " M0l" [root@romulus108 ~]# Some OIDs returns incorrect values, as they return String, instead of Hex-String while running snmp walk. The issue happens for only specific CUCM IP addresses. Conditions: When third party monitoring polls CUCM SNMP 184.108.40.206.220.127.116.11.18.104.22.168.1.7.1 to get the InetAddress. Also it depends on CUCM IP addresses for which the code in nets-snmp side to display the output of snmp walk, prints STRING if the IP octet is a printable and space
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases