RE: link down problem
maybe you are configuring a remote loop. if this is the case the same problem will persist anyway. but, if it is a local loop, an the problem remains, maybe you got a lower level problem. > -Mensaje original- > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > Enviado el: Tuesday, September 19, 2000 10:31 PM > Para: Omar Baceski; 'cisco@groupstudy. com (E-mail)' > Asunto: RE: link down problem > > But a loopback of the interface shows line protocol down as well > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Omar Baceski > Sent: Tuesday, September 19, 2000 8:40 PM > To: cisco@groupstudy. com (E-mail) > Subject: RE: link down problem > > > i suspect that the problem is at the FR switch... > > if you remember the dlci status are: > active: both ends and switch working > inactive: near end and switch working, remote end dead > deleted: the switch does not recognice the dlci number. > > i can see that in one of your routers you have an ACTIVE dlci, so it must > be > up with another peer. maybe you have a misconfiguration in the switching > table at the switch... > > i hope it helps. > > > > -Mensaje original- > > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > > Enviado el: Monday, September 18, 2000 11:38 PM > > Para: cisco@groupstudy. com (E-mail) > > Asunto: link down problem > > > > hi fellow studymates, > > > > Need your comments on this particular problem > > > > It seems that one side pvc active the other pvc inactive and LMI down > > > > I have confirmed the following LMI type correct , could not ping on > either > > side > > > > Can it be the side that the pvc is down is due to physical layer problem > ? > > > > > > need your comments on this > > > > thanks > > > > Situation goes this way : > > > > configuration of router at one end : > > > > Router#sh run > > Building configuration... > > Current configuration: > > ! > > version 11.2 > > no service password-encryption > > no service udp-small-servers > > no service tcp-small-servers > > ! > > hostname Router > > ! > > ! > > ! > > interface Ethernet0 > > no ip address > > shutdown > > ! > > interface Serial0 > > ip address 202.161.128.158 255.255.255.252 > > encapsulation frame-relay IETF > > no fair-queue > > frame-relay interface-dlci 659 > > frame-relay lmi-type ansi > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 202.161.128.157 > > ! > > line con 0 > > line vty 0 4 > > login > > ! > > end > > Router#sh int s0 > > Serial0 is up, line protocol is down (looped) > > Internet address is 202.161.128.158/30 > > MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 > > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) > > > LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down > > LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 > > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts > 0 > > Last input 00:00:09, output 00:00:00, output hang never > > Last clearing of "show interface" counters never > > Queueing strategy: fifo > > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 693 packets input, 37348 bytes, 0 no buffer > > Received 72 broadcasts, 0 runts, 0 giants, 0 throttles > > 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort > > 962 packets output, 87013 bytes, 0 underruns > > 0 output errors, 0 collisions, 2890 interface resets > > 0 output buffer failures, 0 output buffers swapped out > > 12 carrier transitions > > DCD=up DSR=up DTR=up RTS=up CTS=up > > --More-- > > Router#sh frame-relay pvc > > PVC Statistics for interface Serial0 (Frame Relay DTE) > > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = > Serial0 > > > > input pkts 0 output pkts 0 in bytes 0 > > out bytes 0 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 > > pvc create time 02:03:22, last time pvc status changed 02:03:22 > > Router# > > > > configuration
RE: link down problem
But a loopback of the interface shows line protocol down as well -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Omar Baceski Sent: Tuesday, September 19, 2000 8:40 PM To: cisco@groupstudy. com (E-mail) Subject: RE: link down problem i suspect that the problem is at the FR switch... if you remember the dlci status are: active: both ends and switch working inactive: near end and switch working, remote end dead deleted: the switch does not recognice the dlci number. i can see that in one of your routers you have an ACTIVE dlci, so it must be up with another peer. maybe you have a misconfiguration in the switching table at the switch... i hope it helps. > -Mensaje original- > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > Enviado el: Monday, September 18, 2000 11:38 PM > Para: cisco@groupstudy. com (E-mail) > Asunto: link down problem > > hi fellow studymates, > > Need your comments on this particular problem > > It seems that one side pvc active the other pvc inactive and LMI down > > I have confirmed the following LMI type correct , could not ping on either > side > > Can it be the side that the pvc is down is due to physical layer problem ? > > > need your comments on this > > thanks > > Situation goes this way : > > configuration of router at one end : > > Router#sh run > Building configuration... > Current configuration: > ! > version 11.2 > no service password-encryption > no service udp-small-servers > no service tcp-small-servers > ! > hostname Router > ! > ! > ! > interface Ethernet0 > no ip address > shutdown > ! > interface Serial0 > ip address 202.161.128.158 255.255.255.252 > encapsulation frame-relay IETF > no fair-queue > frame-relay interface-dlci 659 > frame-relay lmi-type ansi > ! > ip classless > ip route 0.0.0.0 0.0.0.0 202.161.128.157 > ! > line con 0 > line vty 0 4 > login > ! > end > Router#sh int s0 > Serial0 is up, line protocol is down (looped) > Internet address is 202.161.128.158/30 > MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) > LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down > LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0 > Last input 00:00:09, output 00:00:00, output hang never > Last clearing of "show interface" counters never > Queueing strategy: fifo > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 693 packets input, 37348 bytes, 0 no buffer > Received 72 broadcasts, 0 runts, 0 giants, 0 throttles > 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort > 962 packets output, 87013 bytes, 0 underruns > 0 output errors, 0 collisions, 2890 interface resets > 0 output buffer failures, 0 output buffers swapped out > 12 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > --More-- > Router#sh frame-relay pvc > PVC Statistics for interface Serial0 (Frame Relay DTE) > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0 > > input pkts 0 output pkts 0 in bytes 0 > out bytes 0 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 > pvc create time 02:03:22, last time pvc status changed 02:03:22 > Router# > > configuration of router at the other end > kap-cdr-02>sh frame-relay pvc 659 > > PVC Statistics for interface Hssi4/0 (Frame Relay DTE) > > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = > Hssi4/0.659 > > input pkts 598 output pkts 120463 in bytes 154900 > out bytes 42196627 dropped pkts 3 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 8614 out bcast bytes 3101040 > pvc create time 1w5d, last time pvc status changed 5d15h > kap-cdr-02> > Hssi4/0.659 (up): point-to-point dlci, dlci 659(0x293,0xA430), broadcast > status defined, active > > > > > **NOTE: New CCNA/CCDA List has been formed. For more information go to > http://www.groupstudy.com/list/Associates.html > _ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archiv
RE: link down problem
thank you I suspect it is the other side , not my side that is causing the problem. Since a loop back test indicates that the line protocol is down as well Jason -Original Message- From: Peter Simmons [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 19, 2000 5:51 PM To: Yee, Jason; [EMAIL PROTECTED] Subject: Re: link down problem Jason, I would suspect a FR service provider fault then. The status of "inactive" for the PVC indicates the problem lies downstream/upstream of this router. >From Internetworking Troubleshooting Handbook p533 (Cisco Press) Frame Relay: Cannot ping Remote Router DLCI Inactive or deleted: Step 2: If the output from Step 1 (SHOW FRAME-RELAY PVC command) shows that the PVC is deleted or inactive, there is a problem along the path to the remote router. Check the remote router or contact your carrier to check the status ofthe PVC. Hope this helps Regards Pete S. /DISCLAIMER All the ususal legal rubbish means that if If your house burns down after reading this, it's NOT my fault, OK! /DISCLAIMER OFF -Original Message- From: Yee, Jason <[EMAIL PROTECTED]> To: 'Peter Simmons' <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 19 September 2000 10:19 Subject: RE: link down problem >This is the hangover from testing not the cause after loop back is disabled >the line protocol still show down > >Jason > >-Original Message- >From: Peter Simmons [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 19, 2000 1:27 PM >To: Yee, Jason; [EMAIL PROTECTED] >Subject: Re: link down problem > > > >Jason, > >(Lots of stuff snipped) > >The output from "show int s0" > >>Router#sh int s0 >>Serial0 is up, line protocol is down (looped) >>Internet address is 202.161.128.158/30 > >shows the interface is looped at the CSU/DSU, doesn't it? > >Is this just a hangover from testing, or is this the cause? > >Regards > >Pete S. > >/DISCLAIMER >All the ususal legal rubbish means that if If your house burns down after >reading this, it's NOT my fault, OK! >/DISCLAIMER OFF > > > **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: link down problem
ok will try that out , thanks a lot Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Simon Sent: Tuesday, September 19, 2000 10:00 PM To: [EMAIL PROTECTED] Subject: Re: link down problem If you check the output from the router: LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down this shows that the router is making LMI enquires of the switch [LMI enq sent 18], but is not receiving replies [LMI stat recvd 0] - ie. the LMI has not been activated on the local link. At the opposite end things will appear OK as the router has the LMI activated at that end. Use show fr map to see if dlci 659 has mapped to a different IP address. Remember that the dlci number only has local significance, they do not have to match at both ends. I agree with Omar that it is likely that the pvc's are misconfigured if you are active on one end and not the other. Get the service provider to confirm that LMI is activated, if your interface does not go up and up, get them to put a loopback to you, and sh int to see if it loops. If it does not, it is likely that they have not cabled the opposite end of your line in the exchange. Once the interface goes up and up, the LMI stat recvd will increment with the LMI enq sent. This will confirm that the router is talking to the switch. Then you can use sh fr pvc to see which pvcs have been built, and sh fr map to see what they can see at the opposite end. Cheers, Si "Omar Baceski" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > i suspect that the problem is at the FR switch... > > if you remember the dlci status are: > active: both ends and switch working > inactive: near end and switch working, remote end dead > deleted: the switch does not recognice the dlci number. > > i can see that in one of your routers you have an ACTIVE dlci, so it must be > up with another peer. maybe you have a misconfiguration in the switching > table at the switch... > > i hope it helps. > > > > -Mensaje original- > > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > > Enviado el: Monday, September 18, 2000 11:38 PM > > Para: cisco@groupstudy. com (E-mail) > > Asunto: link down problem > > > > hi fellow studymates, > > > > Need your comments on this particular problem > > > > It seems that one side pvc active the other pvc inactive and LMI down > > > > I have confirmed the following LMI type correct , could not ping on either > > side > > > > Can it be the side that the pvc is down is due to physical layer problem ? > > > > > > need your comments on this > > > > thanks > > > > Situation goes this way : > > > > configuration of router at one end : > > > > Router#sh run > > Building configuration... > > Current configuration: > > ! > > version 11.2 > > no service password-encryption > > no service udp-small-servers > > no service tcp-small-servers > > ! > > hostname Router > > ! > > ! > > ! > > interface Ethernet0 > > no ip address > > shutdown > > ! > > interface Serial0 > > ip address 202.161.128.158 255.255.255.252 > > encapsulation frame-relay IETF > > no fair-queue > > frame-relay interface-dlci 659 > > frame-relay lmi-type ansi > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 202.161.128.157 > > ! > > line con 0 > > line vty 0 4 > > login > > ! > > end > > Router#sh int s0 > > Serial0 is up, line protocol is down (looped) > > Internet address is 202.161.128.158/30 > > MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 > > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) > > LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down > > LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 > > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0 > > Last input 00:00:09, output 00:00:00, output hang never > > Last clearing of "show interface" counters never > > Queueing strategy: fifo > > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 693 packets input, 37348 bytes, 0 no buffer > > Received 72 broadcasts, 0 runts, 0 giants, 0 throttles > > 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort > > 962 packets output, 87013 bytes, 0 underruns > > 0 output errors, 0 collisions, 2890 interface resets > > 0 o
Re: link down problem
If you check the output from the router: LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down this shows that the router is making LMI enquires of the switch [LMI enq sent 18], but is not receiving replies [LMI stat recvd 0] - ie. the LMI has not been activated on the local link. At the opposite end things will appear OK as the router has the LMI activated at that end. Use show fr map to see if dlci 659 has mapped to a different IP address. Remember that the dlci number only has local significance, they do not have to match at both ends. I agree with Omar that it is likely that the pvc's are misconfigured if you are active on one end and not the other. Get the service provider to confirm that LMI is activated, if your interface does not go up and up, get them to put a loopback to you, and sh int to see if it loops. If it does not, it is likely that they have not cabled the opposite end of your line in the exchange. Once the interface goes up and up, the LMI stat recvd will increment with the LMI enq sent. This will confirm that the router is talking to the switch. Then you can use sh fr pvc to see which pvcs have been built, and sh fr map to see what they can see at the opposite end. Cheers, Si "Omar Baceski" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > i suspect that the problem is at the FR switch... > > if you remember the dlci status are: > active: both ends and switch working > inactive: near end and switch working, remote end dead > deleted: the switch does not recognice the dlci number. > > i can see that in one of your routers you have an ACTIVE dlci, so it must be > up with another peer. maybe you have a misconfiguration in the switching > table at the switch... > > i hope it helps. > > > > -Mensaje original- > > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > > Enviado el: Monday, September 18, 2000 11:38 PM > > Para: cisco@groupstudy. com (E-mail) > > Asunto: link down problem > > > > hi fellow studymates, > > > > Need your comments on this particular problem > > > > It seems that one side pvc active the other pvc inactive and LMI down > > > > I have confirmed the following LMI type correct , could not ping on either > > side > > > > Can it be the side that the pvc is down is due to physical layer problem ? > > > > > > need your comments on this > > > > thanks > > > > Situation goes this way : > > > > configuration of router at one end : > > > > Router#sh run > > Building configuration... > > Current configuration: > > ! > > version 11.2 > > no service password-encryption > > no service udp-small-servers > > no service tcp-small-servers > > ! > > hostname Router > > ! > > ! > > ! > > interface Ethernet0 > > no ip address > > shutdown > > ! > > interface Serial0 > > ip address 202.161.128.158 255.255.255.252 > > encapsulation frame-relay IETF > > no fair-queue > > frame-relay interface-dlci 659 > > frame-relay lmi-type ansi > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 202.161.128.157 > > ! > > line con 0 > > line vty 0 4 > > login > > ! > > end > > Router#sh int s0 > > Serial0 is up, line protocol is down (looped) > > Internet address is 202.161.128.158/30 > > MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 > > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) > > LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down > > LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 > > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0 > > Last input 00:00:09, output 00:00:00, output hang never > > Last clearing of "show interface" counters never > > Queueing strategy: fifo > > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 693 packets input, 37348 bytes, 0 no buffer > > Received 72 broadcasts, 0 runts, 0 giants, 0 throttles > > 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort > > 962 packets output, 87013 bytes, 0 underruns > > 0 output errors, 0 collisions, 2890 interface resets > > 0 output buffer failures, 0 output buffers swapped out > > 12 carrier transitions > > DCD=up DSR=up DTR=up RTS=up CTS=up > > --More-- > > Router#sh frame-relay pvc > > PVC Statistics for interface Serial0 (Frame Relay DTE) > > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0 > > > > input pkts 0 output pkts 0 in bytes 0 > > out bytes 0 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 > > pvc create time 02:03:22, last time pvc status changed 02:03:22 > > Router# > > > > configuration of router at the other end > > kap-cdr-02>sh frame-relay pvc 659 > > > > PVC Statistics for interface Hssi4/0 (Frame Relay DTE) > > > > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE
RE: link down problem
i suspect that the problem is at the FR switch... if you remember the dlci status are: active: both ends and switch working inactive: near end and switch working, remote end dead deleted: the switch does not recognice the dlci number. i can see that in one of your routers you have an ACTIVE dlci, so it must be up with another peer. maybe you have a misconfiguration in the switching table at the switch... i hope it helps. > -Mensaje original- > De: Yee, Jason [SMTP:[EMAIL PROTECTED]] > Enviado el: Monday, September 18, 2000 11:38 PM > Para: cisco@groupstudy. com (E-mail) > Asunto: link down problem > > hi fellow studymates, > > Need your comments on this particular problem > > It seems that one side pvc active the other pvc inactive and LMI down > > I have confirmed the following LMI type correct , could not ping on either > side > > Can it be the side that the pvc is down is due to physical layer problem ? > > > need your comments on this > > thanks > > Situation goes this way : > > configuration of router at one end : > > Router#sh run > Building configuration... > Current configuration: > ! > version 11.2 > no service password-encryption > no service udp-small-servers > no service tcp-small-servers > ! > hostname Router > ! > ! > ! > interface Ethernet0 > no ip address > shutdown > ! > interface Serial0 > ip address 202.161.128.158 255.255.255.252 > encapsulation frame-relay IETF > no fair-queue > frame-relay interface-dlci 659 > frame-relay lmi-type ansi > ! > ip classless > ip route 0.0.0.0 0.0.0.0 202.161.128.157 > ! > line con 0 > line vty 0 4 > login > ! > end > Router#sh int s0 > Serial0 is up, line protocol is down (looped) > Internet address is 202.161.128.158/30 > MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 > Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) > LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down > LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0 > Last input 00:00:09, output 00:00:00, output hang never > Last clearing of "show interface" counters never > Queueing strategy: fifo > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > 5 minute input rate 0 bits/sec, 0 packets/sec > 5 minute output rate 0 bits/sec, 0 packets/sec > 693 packets input, 37348 bytes, 0 no buffer > Received 72 broadcasts, 0 runts, 0 giants, 0 throttles > 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort > 962 packets output, 87013 bytes, 0 underruns > 0 output errors, 0 collisions, 2890 interface resets > 0 output buffer failures, 0 output buffers swapped out > 12 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up > --More-- > Router#sh frame-relay pvc > PVC Statistics for interface Serial0 (Frame Relay DTE) > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0 > > input pkts 0 output pkts 0 in bytes 0 > out bytes 0 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 > pvc create time 02:03:22, last time pvc status changed 02:03:22 > Router# > > configuration of router at the other end > kap-cdr-02>sh frame-relay pvc 659 > > PVC Statistics for interface Hssi4/0 (Frame Relay DTE) > > DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = > Hssi4/0.659 > > input pkts 598 output pkts 120463 in bytes 154900 > out bytes 42196627 dropped pkts 3 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 8614 out bcast bytes 3101040 > pvc create time 1w5d, last time pvc status changed 5d15h > kap-cdr-02> > Hssi4/0.659 (up): point-to-point dlci, dlci 659(0x293,0xA430), broadcast > status defined, active > > > > > **NOTE: New CCNA/CCDA List has been formed. For more information go to > http://www.groupstudy.com/list/Associates.html > _ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: link down problem
Looks like LMI has not been activated on that line - check with your service provider. Cheers, Si "Peter Simmons" <[EMAIL PROTECTED]> wrote in message 02ae01c0221f$23cde300$020110ac@pii300">news:02ae01c0221f$23cde300$020110ac@pii300... > Jason, > > I would suspect a FR service provider fault then. The status of "inactive" > for the PVC indicates the problem lies downstream/upstream of this router. > > From Internetworking Troubleshooting Handbook p533 (Cisco Press) > > Frame Relay: Cannot ping Remote Router > DLCI Inactive or deleted: > > Step 2: If the output from Step 1 (SHOW FRAME-RELAY PVC command) shows that > the PVC is deleted or inactive, there is a problem along the path to the > remote router. Check the remote router or contact your carrier to check the > status ofthe PVC. > > Hope this helps > > Regards > > Pete S. > > /DISCLAIMER > All the ususal legal rubbish means that if If your house burns down after > reading this, it's NOT my fault, OK! > /DISCLAIMER OFF > > -Original Message- > From: Yee, Jason <[EMAIL PROTECTED]> > To: 'Peter Simmons' <[EMAIL PROTECTED]>; [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > Date: 19 September 2000 10:19 > Subject: RE: link down problem > > > >This is the hangover from testing not the cause after loop back is disabled > >the line protocol still show down > > > >Jason > > > >-Original Message- > >From: Peter Simmons [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, September 19, 2000 1:27 PM > >To: Yee, Jason; [EMAIL PROTECTED] > >Subject: Re: link down problem > > > > > > > >Jason, > > > >(Lots of stuff snipped) > > > >The output from "show int s0" > > > >>Router#sh int s0 > >>Serial0 is up, line protocol is down (looped) > >>Internet address is 202.161.128.158/30 > > > >shows the interface is looped at the CSU/DSU, doesn't it? > > > >Is this just a hangover from testing, or is this the cause? > > > >Regards > > > >Pete S. > > > >/DISCLAIMER > >All the ususal legal rubbish means that if If your house burns down after > >reading this, it's NOT my fault, OK! > >/DISCLAIMER OFF > > > > > > > > **NOTE: New CCNA/CCDA List has been formed. For more information go to > http://www.groupstudy.com/list/Associates.html > _ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: link down problem
Jason, I would suspect a FR service provider fault then. The status of "inactive" for the PVC indicates the problem lies downstream/upstream of this router. >From Internetworking Troubleshooting Handbook p533 (Cisco Press) Frame Relay: Cannot ping Remote Router DLCI Inactive or deleted: Step 2: If the output from Step 1 (SHOW FRAME-RELAY PVC command) shows that the PVC is deleted or inactive, there is a problem along the path to the remote router. Check the remote router or contact your carrier to check the status ofthe PVC. Hope this helps Regards Pete S. /DISCLAIMER All the ususal legal rubbish means that if If your house burns down after reading this, it's NOT my fault, OK! /DISCLAIMER OFF -Original Message- From: Yee, Jason <[EMAIL PROTECTED]> To: 'Peter Simmons' <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 19 September 2000 10:19 Subject: RE: link down problem >This is the hangover from testing not the cause after loop back is disabled >the line protocol still show down > >Jason > >-Original Message- >From: Peter Simmons [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 19, 2000 1:27 PM >To: Yee, Jason; [EMAIL PROTECTED] >Subject: Re: link down problem > > > >Jason, > >(Lots of stuff snipped) > >The output from "show int s0" > >>Router#sh int s0 >>Serial0 is up, line protocol is down (looped) >>Internet address is 202.161.128.158/30 > >shows the interface is looped at the CSU/DSU, doesn't it? > >Is this just a hangover from testing, or is this the cause? > >Regards > >Pete S. > >/DISCLAIMER >All the ususal legal rubbish means that if If your house burns down after >reading this, it's NOT my fault, OK! >/DISCLAIMER OFF > > > **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: link down problem
Jason, (Lots of stuff snipped) The output from "show int s0" >Router#sh int s0 >Serial0 is up, line protocol is down (looped) >Internet address is 202.161.128.158/30 shows the interface is looped at the CSU/DSU, doesn't it? Is this just a hangover from testing, or is this the cause? Regards Pete S. /DISCLAIMER All the ususal legal rubbish means that if If your house burns down after reading this, it's NOT my fault, OK! /DISCLAIMER OFF **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: link down problem
This is the hangover from testing not the cause after loop back is disabled the line protocol still show down Jason -Original Message- From: Peter Simmons [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 19, 2000 1:27 PM To: Yee, Jason; [EMAIL PROTECTED] Subject: Re: link down problem Jason, (Lots of stuff snipped) The output from "show int s0" >Router#sh int s0 >Serial0 is up, line protocol is down (looped) >Internet address is 202.161.128.158/30 shows the interface is looped at the CSU/DSU, doesn't it? Is this just a hangover from testing, or is this the cause? Regards Pete S. /DISCLAIMER All the ususal legal rubbish means that if If your house burns down after reading this, it's NOT my fault, OK! /DISCLAIMER OFF **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: link down problem
I am positive that I am looking at the same pvc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 19, 2000 1:59 PM To: [EMAIL PROTECTED] Subject: link down problem Don't forget that the DLCI is only locally significant - just because a PVC has DLCI 659 on one end doesn't mean that it will necessarily be 659 at the other end. Are you sure you're looking at two ends of the same PVC?] JMcL -- Forwarded by Jenny Mcleod/NSO/CSDA on 19/09/2000 04:59 pm --- "Yee, Jason" <[EMAIL PROTECTED]> on 19/09/2000 01:38:29 pm Please respond to "Yee, Jason" <[EMAIL PROTECTED]> To: "cisco@groupstudy. com (E-mail)" <[EMAIL PROTECTED]> cc:(bcc: JENNY MCLEOD/NSO/CSDA) Subject: link down problem hi fellow studymates, Need your comments on this particular problem It seems that one side pvc active the other pvc inactive and LMI down I have confirmed the following LMI type correct , could not ping on either side Can it be the side that the pvc is down is due to physical layer problem ? need your comments on this thanks Situation goes this way : configuration of router at one end : Router#sh run Building configuration... Current configuration: ! version 11.2 no service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname Router ! ! ! interface Ethernet0 no ip address shutdown ! interface Serial0 ip address 202.161.128.158 255.255.255.252 encapsulation frame-relay IETF no fair-queue frame-relay interface-dlci 659 frame-relay lmi-type ansi ! ip classless ip route 0.0.0.0 0.0.0.0 202.161.128.157 ! line con 0 line vty 0 4 login ! end Router#sh int s0 Serial0 is up, line protocol is down (looped) Internet address is 202.161.128.158/30 MTU 1500 bytes, BW 1544 Kbit, DLY 2 usec, rely 211/255, load 1/255 Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec) LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down LMI enq recvd 18, LMI stat sent 0, LMI upd sent 0 LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0 Last input 00:00:09, output 00:00:00, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 693 packets input, 37348 bytes, 0 no buffer Received 72 broadcasts, 0 runts, 0 giants, 0 throttles 831 input errors, 1 CRC, 820 frame, 0 overrun, 0 ignored, 10 abort 962 packets output, 87013 bytes, 0 underruns 0 output errors, 0 collisions, 2890 interface resets 0 output buffer failures, 0 output buffers swapped out 12 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up --More-- Router#sh frame-relay pvc PVC Statistics for interface Serial0 (Frame Relay DTE) DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0 input pkts 0 output pkts 0 in bytes 0 out bytes 0 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 pvc create time 02:03:22, last time pvc status changed 02:03:22 Router# configuration of router at the other end kap-cdr-02>sh frame-relay pvc 659 PVC Statistics for interface Hssi4/0 (Frame Relay DTE) DLCI = 659, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Hssi4/0.659 input pkts 598 output pkts 120463 in bytes 154900 out bytes 42196627 dropped pkts 3 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 8614 out bcast bytes 3101040 pvc create time 1w5d, last time pvc status changed 5d15h kap-cdr-02> Hssi4/0.659 (up): point-to-point dlci, dlci 659(0x293,0xA430), broadcast status defined, active **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
