Basic Frame Relay trouble

[phil]

Hello all,

I am having problems with a frame relay and I am in need of advice. First off, let me state I am not by any means a cisco expert, though I've had a fair amount of networking experience.

My problem is one of connections and finger pointing. I have a point to point frame relay, with one cisco 2501 on either side. The line tests clean (according to the ISP; and they have checked it numerous times), but the pvc refuses to come up. When the cisco is restarted/reloaded the Serial0 (frame) comes up, finds the other side's DLCI (which I take as a sign that the two sides see can each other), then goes right back down.

Both DSUs are configured identically, using the same timing, line coding and framing. The provider says they can test the frame clean by looping to the DSUs, meaning they are functioning correctly. So that leaves the ciscos' configurations. But the consultants who set the ciscos up swear that its the Frame line that's at fault.

Can anyone help shed a little light on this for me? I would be eternally grateful.

Thanks in advance,

-Phil

[rhickey]

Try setting one DSU to LOOP timing the other to MASTER.

[phil]

Do you mean to set the clock source timing?

If so, my only options (adtran LT) are:

internal, network or dte

Sorry for my ignorance.

[mark-obrien]

Phil,

By "point-to-point frame relay", do you mean point-to-point sub-interfaces? If so, it may be that the wrong DLCIs were assigned to the sub-interfaces. In one of your routers, enter the command "show frame-relay pvc". The DLCI assigned to your sub-interface should show up as local and active. If not, find the DLCI that is unused and active, and have it assigned to your sub-interface after removing the wrong one. Do this in both routers.

As for the router finding the other side's DLCI after being reloaded, and then losing it, the router will assume the PVC is up after a reload, until it is lost.

Good luck.

Mark

[cairnsm]

Phil,

Can you post the output from the following commands on each router?

show frame-relay lmi

show frame-relay pvc

show frame-relay map

sh run for each serial interface

Thanks,

Mark

[phil]

Can do.

Thanks a ton for your help

---=== router A ===---- (DLCI 130)

sh frame-relay lmi:

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 24262 Num Status msgs Rcvd 24262

Num Update Status Rcvd 0 Num Status Timeouts 0

sh frame-relay pvc:

DLCI = 110, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, 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 Num Pkts Switched 0

pvc create time 2d19h, last time pvc status changed 2d19h

DLCI = 130, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = Serial0.1

input pkts 0 output pkts 1 in bytes 0

out bytes 274 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 1 out bcast bytes 274

pvc create time 2d19h, last time pvc status changed 2d19h

sh frame-relay map:

Serial0.1 (down): point-to-point dlci, dlci 130(0x82,0x2020), broadcast

status deleted

sh run:

!

interface Serial0

no ip address

encapsulation frame-relay

no ip mroute-cache

frame-relay lmi-type ansi

!

interface Serial0.1 point-to-point

description connected to Wal office

ip unnumbered Ethernet0

frame-relay interface-dlci 130

!

---=== router B ===---- (DLCI 110)

sh frame-relay lmi:

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 24173 Num Status msgs Rcvd 24173

Num Update Status Rcvd 0 Num Status Timeouts 0

sh frame-relay pvc:

DLCI = 130, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, 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 Num Pkts Switched 0

pvc create time 2d19h, last time pvc status changed 2d19h

DLCI = 110, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = Serial0.1

input pkts 0 output pkts 1 in bytes 0

out bytes 274 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 1 out bcast bytes 274

pvc create time 2d18h, last time pvc status changed 2d18h

sh frame-relay map:

Serial0.1 (down): point-to-point dlci, dlci 110(0x82,0x2020), broadcast

status deleted

sh run:

!

interface Serial0

no ip address

encapsulation frame-relay

no ip mroute-cache

frame-relay lmi-type ansi

!

interface Serial0.1 point-to-point

description connected to Prov office

ip unnumbered Ethernet0

frame-relay interface-dlci 110

!

Does that shed some light on it? Let me know if there's anything else that's needed.

-Phil

[steve.barlow · Accepted solution]

Here is a good link: http://www.cisco.com/en/US/tech/tk713/tk237/technologies_tech_note09186a008009406b.shtml

Try switching the DLCI's around at each site (ie routerA should be 110 and routerB should be 130).

Hope it helps.

Steve

[cairnsm · Accepted solution]

It does appear the DLCIs are backwards. After switching you may need to clear frame inarp. Make sure your routing is correct after you have the link up.

[phil]

That was it.

Thanks for everything guys... you saved the day.

I switched the DLCIs and re-did the routes, and it came right up.

Thanks again,

-Phil