Is possible to get the chassis model for routers 800 series?? The customer wants to find the correct device type in his network. For example he wants to know that there are CISCO871-K9, CISCO876-G-K9 and so on, but the chassis model is na, and device type is Cisco 871 Integrated Services Router, Cisco 876 Integrated Services Router, and so on. From SNMP walk I can get the correct type: entityMIB.entityMIBObjects.entityPhysical.entPhysicalTable.entPhysicalEntry.entPhysicalModelName.1 : OCTET STRING- (ascii): CISCO871-K9
The 800 series routers are instrumented using the ENTITY-MIB, so the entPhysicalModelName should be extracted for the chassis. If this is not happening, there maybe a problem with the device's ENTITY-MIB support. What version of IOS are these devices running?
I tried snmpwalk from the device center and it is working for the entPhysicalModelName OID. For example: entPhysicalModelName.1 : OCTET STRING- (ascii): CISCO871-K9 IOS version is C870-ADVIPSERVICESK9-M, Version 12.4(24)T1
There is an error syncing the inventory using the ENTITY-MIB, and RME falls back to the OLD-CISCO-CHASSIS-MIB. This would explain why you're n
ot seeing the chassis model details in RME. Unfortunately, the log doesn't indicate why. I don't see any known bugs on this, and no one has yet reported the problem. I recommend you open a TAC service request for thisso further analysis can be done.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...