Hanna, Keith wrote:
>
> From memory, DLCI's are only 'locally significant' ie only
> relevant to get data onto the line, and doesn't care what the
> 'far-end' DLCI is.
>
> Traditional to keep them different for troubleshooting purposes
> tho.....
Yup, but pretty common to have both ends of a PVC use the same DLCI too for
simplicty's sake, if the providers oblige, from what I've heard?
Regardless, we agree that this is probably not relevant to his fundamental
problem of the link between the router and the switch being up/down, with
LMI being down.
To bring up the PVC, he would need to make sure his DTE router is using the
correct DLCI, that the DCE switch has a correct statement on the incoming
interface that says what to do with frames that come in for that DLCI, and
that the DTE router at the other end is correctly configured with a correct
DLCI also. And the two ends should be using the same frame relay encap type.
However, we aren't to the point of getting a PVC up yet. We're still working
on the link bewteen that first router and the switch. For that to work, he
needs physical connectivity (which seems OK, since it's up/down), correct
LMI type, matching keepalives. and a switch that knows it's really a switch,
and maybe a few other things that I'm forgetting.
Priscilla
>
> -----Original Message-----
> From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx]
> Sent: 04 August 2004 16:50
> To: cisco@xxxxxxxxxxxxxx
> Subject: RE: Serial up, line protocol down [7:91448]
>
>
> Ryan Sullivan wrote:
> >
> > Looks like you might have your frame-relay routes wrong. You
> > are routing
> > from DLCI 210 on interface S1/1 to DLCI 210 on S1/0. Serial
> > 1/1 and 1/0
> > should not have the same DLCI I don't think.
>
> I noticed that too, but I don't think it matters. As long as
> the switch
> knows that if it comes in this port, send it out this other
> port, I don't
> think it matters how it identifies the legs of the path (i.e.
> what DLCIs it
> uses)?
>
> Anyone else have an opinion?
>
> Hopefully the original poster will tell us that he got it
> working and how.
> GroupStudy is pretty useless if we don't see the resolution to
> problems.
>
> Priscilla
>
>
> >
> > Example for your frame switch.
> > interface Serial1/0
> > description Connection to Router 1
> > no ip address
> > encapsulation frame-relay
> > clockrate 128000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 102 interface Serial1/1 201
> >
> > interface Serial1/1
> > description Connection to Router 2
> > no ip address
> > encapsulation frame-relay
> > clockrate 128000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 201 interface Serial1/0 102
> >
> >
> > -----Original Message-----
> > From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx]
> > Sent: Tuesday, August 03, 2004 3:32 PM
> > To: cisco@xxxxxxxxxxxxxx
> > Subject: Serial up, line protocol down [7:91448]
> >
> > Can any one tell me what prevents the line protocol to come
> up?
> > Everything in the physical interface is UP and no error
> > reported.
> > RouterSwitch is a 2612 and RouterC is a 4700-M. The former is
> > configured on
> > s1/1 as a frame-relay switch the second on s3 as a DTE. They
> > are connected
> > with a DCE-DTE cable (60pins). I annex attach below the config
> > and the show
> > interface serial.
> >
> > Lee
> >
> > RouterSwitch#show running-config
> > ..
> > !
> > interface Serial1/1
> > no ip address
> > encapsulation frame-relay
> > clockrate 128000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 210 interface Serial1/0 210
> > !
> > ..
> >
> > RouterC#show running-config
> > ..
> > !
> > interface Serial3
> > no ip address
> > encapsulation frame-relay
> > frame-relay lmi-type ansi
> > !
> > ..
> >
> > RouterSwitch#show interface serial 1/1
> >
> > Serial1/1 is up, line protocol is down
> > Hardware is CD2430 in sync mode
> > MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
> > reliability 255/255, txload 1/255, rxload 1/255
> > Encapsulation FRAME-RELAY, loopback not set
> > Keepalive set (10 sec)
> > LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0
> > LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0, DCE LMI
> > down
> > LMI DLCI 0 LMI type is ANSI Annex D frame relay DCE
> > FR SVC disabled, LAPF state down
> > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface
> > broadcasts 0
> > Last input never, output never, output hang never
> > Last clearing of "show interface" counters 01:19:00
> > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output
> > drops: 0
> > Queueing strategy: weighted fair
> > Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> > Conversations 0/0/32 (active/max active/max total)
> > Reserved Conversations 0/0 (allocated/max allocated)
> > Available Bandwidth 96 kilobits/sec
> > 5 minute input rate 0 bits/sec, 0 packets/sec
> > 5 minute output rate 0 bits/sec, 0 packets/sec
> > 0 packets input, 0 bytes, 0 no buffer
> > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0
> > abort
> > 0 packets output, 0 bytes, 0 underruns
> > 0 output errors, 0 collisions, 150 interface resets
> > 0 output buffer failures, 0 output buffers swapped out
> > 305 carrier transitions
> > DCD=up DSR=up DTR=up RTS=up CTS=up
> >
> >
> >
> >
> >
> > RouterC#show interface s3
> >
> > Serial3 is up, line protocol is down
> > Hardware is HD64570
> > MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
> > reliability 255/255, txload 1/255, rxload 1/255
> > Encapsulation FRAME-RELAY, loopback not set
> > Keepalive set (10 sec)
> > LMI enq sent 436, LMI stat recvd 0, LMI upd recvd 0, DTE
> LMI
> > down
> > LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
> > LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
> > FR SVC disabled, LAPF state down
> > Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface
> > broadcasts 0
> > Last input never, output 00:00:01, output hang never
> > Last clearing of "show interface" counters 01:12:47
> > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output
> > drops: 0
> > Queueing strategy: weighted fair
> > Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> > Conversations 0/1/256 (active/max active/max total)
> > Reserved Conversations 0/0 (allocated/max allocated)
> > Available Bandwidth 96 kilobits/sec
> > 5 minute input rate 0 bits/sec, 0 packets/sec
> > 5 minute output rate 0 bits/sec, 0 packets/sec
> > 0 packets input, 0 bytes, 0 no buffer
> > Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0
> > abort
> > 438 packets output, 6099 bytes, 0 underruns
> > 0 output errors, 0 collisions, 142 interface resets
> > 0 output buffer failures, 0 output buffers swapped out
> > 280 carrier transitions
> > DCD=up DSR=up DTR=up RTS=up CTS=up
> > RouterC#
>
>
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=91481&t=91448
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
