Why would Orion think my Cisco 2921 router has a Gi0/3 when it does not? IOS: c2900-universalk9-mz.SPA.152-1.T2.bin
I'm running Orion NPM 10.2
Debbi
Found it. Orion picked up its mac address and I traced it from there. Mac was A44C.11C9.E7D3
So here it is. It does not display in the config, obviously:
selbr-1h1-rtr1#sh platform mgf statistics cpu
BPSM counters:
0 from invalid slot, 0 not for CPU, 0 Unknown packet, 0 Invalid output packets
GigabitEthernet0/3 is up, line protocol is up
Hardware is Backplane CN Gigabit Ethernet, address is a44c.11c9.e7d3 (bia a44c.11c9.e7d3)
MTU 9576 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full Duplex, 1Gbps, media type is internal
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Interface statistics for CPU: (port 0)
Here is the description of the mgf:
The Cisco 2900 Series introduces an innovative multigigabit fabric (MGF) that allows for efficient module-to-module communication, enabling tighter services interactions across modules while reducing the overhead on the route processor.
Not sure how Orion should deal with this, but likely I am not the only one seeing it!
Anyway you can produce a Show Run? Of course with any proprietary information omitted.
The 2921 comes with 3 Ethernet ports built into it out of the Factory..
sh ip int br
Embedded-Service-Engine0/0
GigabitEthernet0/0
ISM0/0
ISM0/1
GigabitEthernet0/1
GigabitEthernet0/1.2
GigabitEthernet0/1.99
GigabitEthernet0/1.403
GigabitEthernet0/1.711
GigabitEthernet0/2
Loopback0
Orion correctly shows all of these, including the ISMs, plus a Gi0/3, which it says is up!
Here is the show run, with some things deleted for security reasons: ! ! No configuration change since last restart ! NVRAM config last updated at 11:46:40 pdt Mon Oct 8 2012 by pattond ! NVRAM config last updated at 11:46:40 pdt Mon Oct 8 2012 by pattond version 15.2 service tcp-keepalives-in service tcp-keepalives-out service timestamps debug datetime localtime service timestamps log datetime localtime service password-encryption service sequence-numbers hostname selbr-1h1-rtr1 boot-start-marker boot-end-marker clock timezone pst -8 0 clock summer-time pdt recurring no ipv6 cef no ip source-route ip cef multilink bundle-name authenticated redundancy ip telnet source-interface Loopback0 ip tftp source-interface Loopback0 interface Loopback0 ip address 172.22.20.9 255.255.255.255 no ip redirects no ip unreachables no ip proxy-arp interface Null0 no ip unreachables interface Embedded-Service-Engine0/0 no ip address shutdown interface GigabitEthernet0/0 ip address 172.21.6.70 255.255.255.0 no ip redirects no ip unreachables no ip proxy-arp duplex auto speed auto interface GigabitEthernet0/1 description selbr-1h1-asw1 Gi48 no ip address duplex auto speed auto interface GigabitEthernet0/1.2 description selbr encapsulation dot1Q 2 ip address 172.20.52.65 255.255.255.192 no ip redirects no ip unreachables no ip proxy-arp interface GigabitEthernet0/1.99 description netmanage encapsulation dot1Q 99 ip address 172.20.12.161 255.255.255.240 no ip redirects no ip unreachables no ip proxy-arp interface GigabitEthernet0/1.403 description Null trunk vlan encapsulation dot1Q 403 native interface GigabitEthernet0/1.711 description apmgmt encapsulation dot1Q 711 ip address 172.20.12.97 255.255.255.240 no ip redirects no ip unreachables no ip proxy-arp interface GigabitEthernet0/2 no ip address shutdown duplex auto speed auto router eigrp 327 network 172.21.6.0 0.0.0.255 redistribute connected eigrp stub connected summary no ip forward-protocol nd no ip forward-protocol udp tftp no ip forward-protocol udp nameserver no ip forward-protocol udp domain no ip forward-protocol udp time no ip forward-protocol udp netbios-ns no ip forward-protocol udp netbios-dgm no ip forward-protocol udp tacacs no ip http server no ip http secure-server logging trap warnings logging source-interface Loopback0 logging 172.20.199.10 control-plane line con 0 line aux 0 exec-timeout 0 1 no exec line 2 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line 131 no activation-character no exec transport preferred none transport input all transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 transport input telnet ssh transport output telnet ssh line vty 5 15 exec-timeout 0 1 no exec transport input none scheduler allocate 20000 1000 end
Ok this is odd. You have all 3 interfaces, but are showing a forth as Gig 0/3... Did you by chance replace this router at some point, and it took over the previous IP? If so was the node deleted out of Orion and re-added?
This almost seems like you swapped routers and kept using the same IP, and the interface ID and information is stuck in the DB. You can goto manage nodes and delete that single interface then go to the node and List Resources again. See if that interface shows back up when you run a fresh SNMP GET. If this is the case when you drill into that interface the charts and historical data should be messed up and not recording anything new.
Very nice find! I haven't deployed or worked directly with a 2900 yet. Interesting feature for off-loading overhead from the Proc.. I would be interested in seeing the performance gains sometime. Thanks for sharing your findings and glad you were able to trace it out!
