frame switch woes :(
Hi guys,
lately i'm having problems doing my labs, not sure what it is but i keep getting these issue(listed below). Any input is much appreciated. TIA!
lately i'm having problems doing my labs, not sure what it is but i keep getting these issue(listed below). Any input is much appreciated. TIA!
3640-R1#sh frame map [b]Serial0/0 (up): ip 0.0.0.0 dlci 113(0x71,0x1C10) broadcast, CISCO, status defined, active[/b] Serial0/0 (up): ip 0.0.0.0 dlci 105(0x69,0x1890) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 104(0x68,0x1880) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 103(0x67,0x1870) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 102(0x66,0x1860) broadcast, CISCO, status defined, inactive 3640-R1#sh frame pvc 113 PVC Statistics for interface Serial0/0 (Frame Relay DTE) DLCI = 113, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0 input pkts 4 output pkts 0 in bytes 256 out bytes 0 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 0 out bcast bytes 0 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 00:29:43, last time pvc status changed 00:05:22
3640-R2#sh frame map Serial0/0 (up): ip 0.0.0.0 dlci 315(0x13B,0x4CB0) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 314(0x13A,0x4CA0) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 312(0x138,0x4C80) broadcast, CISCO, status defined, inactive Serial0/0 (up): ip 0.0.0.0 dlci 311(0x137,0x4C70) broadcast, CISCO, status defined, active 3640-R2#sh frame pvc 311 PVC Statistics for interface Serial0/0 (Frame Relay DTE) DLCI = 311, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0 input pkts 0 output pkts 12 in bytes 0 out bytes 768 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 12 out bcast bytes 768 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 00:37:20, last time pvc status changed 00:12:59 3640-R2#
FRS#sh frame route | include Serial0 Serial0 102 Serial1 201 inactive Serial0 103 Serial2 301 inactive Serial0 104 Serial4 401 inactive Serial0 105 Serial5 501 inactive Serial0 113 Serial3 311 active Serial1 201 Serial0 102 inactive Serial2 301 Serial0 103 inactive Serial3 311 Serial0 113 active Serial4 401 Serial0 104 inactive Serial5 501 Serial0 105 inactive FRS#sh frame pvc 113 PVC Statistics for interface Serial0 (Frame Relay DCE) DLCI = 113, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial0 input pkts 249 output pkts 260 in bytes 31192 out bytes 21615 dropped pkts 0 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 245 pvc create time 02:02:59, last time pvc status changed 00:10:28 FRS#sh frame pvc 311 PVC Statistics for interface Serial3 (Frame Relay DCE) DLCI = 311, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial3 input pkts 260 output pkts 245 in bytes 21615 out bytes 30460 dropped pkts 4 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 260 pvc create time 02:03:27, last time pvc status changed 00:11:05 FRS#
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator
Comments
-
qplayed Member Posts: 303here's some debug frame-relay packet output
3640-R1#debug frame-relay pack Frame Relay packet debugging is on 3640-R1#ping 192.168.100.2 rep 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 192.168.100.2, timeout is 2 seconds: *Mar 2 23:33:05.675: Serial0/0:Encaps failed--no map entry link 7(IP). Success rate is 0 percent (0/1) 3640-R1#
3640-R2#debug frame pack Frame Relay packet debugging is on 3640-R2#ping 192.168.100.1 rep 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 192.168.100.1, timeout is 2 seconds: *Mar 3 05:44:35.739: Serial0/0:Encaps failed--no map entry link 7(IP). Success rate is 0 percent (0/1)
R1*Mar 2 23:33:14.615: Serial0/0(i): dlci 113(0x1C11), pkt type 0x800, datagramsize 64 *Mar 2 23:34:12.879: Serial0/0(i): dlci 113(0x1C11), pkt type 0x800, datagramsize 64 *Mar 2 23:35:09.779: Serial0/0(i): dlci 113(0x1C11), pkt type 0x800, datagramsize 64 *Mar 2 23:36:09.087: Serial0/0(i): dlci 113(0x1C11), pkt type 0x800, datagramsize 64
R2*Mar 3 05:45:44.371: Serial0/0: broadcast search *Mar 3 05:45:44.371: Serial0/0: Broadcast on DLCI 314 link 7 *Mar 3 05:45:44.371: DLCI 314 is either deleted or inactive *Mar 3 05:45:44.371: Serial0/0: Broadcast on DLCI 312 link 7 *Mar 3 05:45:44.371: DLCI 312 is either deleted or inactive *Mar 3 05:45:44.371: Serial0/0: Broadcast on DLCI 311 link 7 *Mar 3 05:45:44.371: Serial0/0(o): dlci 311(0x4C71), pkt type 0x800(IP), datagramsize 64 *Mar 3 05:45:44.371: DLCI 315 is either deleted or inactive *Mar 3 05:45:44.439: broadcast dequeue *Mar 3 05:45:44.439: Serial0/0(o):Pkt sent on dlci 311(0x4C71), pkt type 0x800(IP), datagramsize 64
If you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
mikej412 Member Posts: 10,086 ■■■■■■■■■■Shut down your interface before you configure it for frame relay.
Save your configuration and reload -- and they should go away.
Or change your interface encapsulation, shut down the interface, and then reconfigure it for frame-relay.
Those are usually incomplete mappings from inverse arp.:mike: Cisco Certifications -- Collect the Entire Set! -
qplayed Member Posts: 303ok a quick reload worked....but...when I when i started working on the configs
the interfaces were shutdown and was the last thing to be brought up/cnfguredShut down your interface before you configure it for frame relay.
Save your configuration and reload -- and they should go away.
Or change your interface encapsulation, shut down the interface, and then reconfigure it for frame-relay.
also to be honest, I've tried doing the above and never seemed to work :P...i've been up since 5am so i'm sorry if i'm a little stupid right now.....I'm on a lab binge before i tackle bgp on wednesday
thanksIf you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator -
mikej412 Member Posts: 10,086 ■■■■■■■■■■Don't forget that when you shut down inverse arp on one side of the link, it stops sending -- but it will still receive from the other side of the link.
If you play with Frame Relay enough, you'll learn it's just easier to shut down all the interfaces before you start your configuration. And if you're starting with a partially configured frame-relay network, a configuration save and reload is usually your best bet.:mike: Cisco Certifications -- Collect the Entire Set! -
qplayed Member Posts: 303thanksIf you cannot express in a sentence or two what
you intend to get across, then it is not focused
well enough.
—Charles Osgood, TV commentator