I have encountered this issue a number of times when working on a clients WAN circuit after a critical outage is resolved.I run the command 'show frame pvc' to list the active frame circuits, and my screen scrolls through pages of interface entries. Why does this happen when we only have one circuit configured per site?. Below you can find the device and interface info, as well as the command output I have attached to here.
Please let me know if any other info is required, I have refrained from sharing the running-config at this time, as to not expose any confidential client data.
#show ip int brie Interface IP-Address OK? Method Status Protocol FastEthernet0/0 X.X.X.X YES NVRAM up up Serial0/0 unassigned YES NVRAM up up Serial0/0.1 X.X.X.X YES NVRAM up up Serial0/0.2 X.X.X.X YES NVRAM down down
#show int s0/0 Serial0/0 is up, line protocol is up Hardware is PowerQUICC Serial MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation FRAME-RELAY IETF, loopback not set Keepalive set (10 sec) LMI enq sent 574289, LMI stat recvd 574286, LMI upd recvd 0, DTE LMI up LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0 LMI DLCI 1023 LMI type is CISCO frame relay DTE Broadcast queue 0/64, broadcasts sent/dropped 1092359/1, interface broadcasts 996851 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters 9w3d Input queue: 0/75/1/0 (size/max/drops/flushes); Total output drops: 1698 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 1000 bits/sec, 2 packets/sec 5 minute output rate 1000 bits/sec, 2 packets/sec 33057480 packets input, 2859075344 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 4 giants, 0 throttles 15 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 15 abort 29897055 packets output, 1670359289 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up
#show int s0/0.1 Serial0/0.1 is up, line protocol is up Hardware is PowerQUICC Serial Internet address is X.X.X.X/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation FRAME-RELAY IETF Last clearing of "show interface" counters never
#show ver Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-I-M), Version 12.3(3), RELEASE SOFTWARE (fc2) Copyright (c) 1986-2003 by cisco Systems, Inc. Compiled Tue 19-Aug-03 16:31 by dchih Image text-base: 0x80008098, data-base: 0x80C9702C
ROM: System Bootstrap, Version 12.2(6r), RELEASE SOFTWARE (fc1)
OAKFH_HG1_F uptime is 9 weeks, 3 days, 11 hours, 12 minutes System returned to ROM by power-on System restarted at 04:23:10 GMT Sun Dec 5 2010 System image file is "flash:c2600-i-mz.123-3.bin"
cisco 2620 (MPC860) processor (revision 0x00) with 53248K/12288K bytes of memory. Processor board ID JAD06080BR8 (115486466) M860 processor: part number 0, mask 49 Bridging software. X.25 software, Version 3.0.0. 1 FastEthernet/IEEE 802.3 interface(s) 1 Serial network interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write)
This is most probably a fault of your Frame Relay service provider. The list of virtual circuits (VCs) that you see was advertised to you from your nearest FR switch via the LMI protocol. You router has not invented all these VCs by itself (unless there is some grave bug in the IOS - an upgrade would be worth trying anyway, as the 12.2(3) is severely outdated).
If the list of bogus VCs remains displayed even after reloading your router, I would suggest talking to your FR provider and showing them this list. Most probably, they have misconfigured their FRAD port.