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 20000 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]

**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]

Reply via email to