cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1349
Views
12
Helpful
12
Replies

Frame Relay encaps for new DLCI

stevenpaterson
Level 1
Level 1

Hi

We have recently installed a new frame circuit to an extranet site.

The one site had to have fresh frame-relay infrastructure installed. No problems at that site, the frame circuit has a functioning PVC on DLCI16.

At the other site we are adding a PVC.

Following config added at non-functioning site:

Interface Serial0/0

no ip address

encapsulation frame-relay

no ip mroute-cache

no fair-queue

frame-relay lmi-type ansi

interface Serial0/0.2 point-to-point

ip address

frame-relay interface-dlci 60

A debug frame-relay packet gives me the following:

encaps failed--line down

Two other PVCs are operating successfully on the circuit.

Tried adding:

frame-relay interface-dlci 60 IETF

No luck, the PVC is deleted.

Have confirmed PVC with ISP. LMI confirmed as ANSI. Does anyone have any other suggestions?

1 Accepted Solution

Accepted Solutions

Steven

I am glad that we are able to help. I think the show frame-relay pvc is informative but I believe that the debug frame-relay lmi is especially convincing that the frame relay switch is not announcing DLCI 60 to you.

If you get an answer I encourage you to post back to the forum indicating what you found (and if the problem is resolved (hopefully) what the resolution was). It makes the forum more useful when we can read about a problem and then see what the answer or the resolution was.

HTH

Rick

HTH

Rick

View solution in original post

12 Replies 12

mahmoodmkl
Level 7
Level 7

HI

I think u should add mapping statements in ur configuration.i.e

frame-realy map ip dlci broadcast ietf.

Thanks

Mahmood

Thank you for your response.

I tried doing this by setting a frame-relay map on the subinterface and it claims the interface is not point-to-point:

FRAME-RELAY INTERFACE-DLCI command should be used on point-to-point interfaces

Interface header is as follows:

interface Serial0/0.2 point-to-point

I suppose the other option is inverse arp? The other PVCs are running without frame-relay maps.

It could be the router not detecting the interface as point-to-point. Have tried recreating the subinterface and setting it on a new subinterface.

can you just post the status of sub interface...and sh run output...

regards

Devang

HI

Can u set the frame-relay encapsulation to ietf as it will be by default to cisco.As u r using ANSI i think this should work.

Thanks

Mahmood

Hi

try to disable the inverse Arp.maybe i will solv ur problem.

10xs

Ali

Steven

I would suggest running debug frame-relay lmi and see what is being sent from the switch.

It might also be helpful if the output of show frame-relay pvc would be posted.

I am interested in the part of your message about attempting to specify encap ietf and the error that was generated. Could you possible try this again and post a screen shot of the command that you entered and the resulting error message.

HTH

Rick

HTH

Rick

Hi Rick

Encapsulation is failing with both encapsulation types:

(config)#int serial0/0.2

(config-subif)#frame-relay interface-dlci 60 IETF

Jun 13 09:18:19.709: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:18:19.713: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:18:19.713: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:18:19.713: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:18:19.713: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:18:19.713: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:18:19.793: broadcast dequeue

Jun 13 09:18:19.793: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:18:19.793: broadcast dequeue

Jun 13 09:18:19.793: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:18:19.793: broadcast dequeue

Jun 13 09:18:19.793: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:19:10.250: Serial0/0.2: encaps failed--line down

(config)#int serial0/0.2

(config-subif)#frame-relay interface-dlci 60

Jun 13 09:22:29.244: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:22:29.244: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:22:29.248: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:22:29.248: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:22:29.248: Serial0/0.2: Broadcast on DLCI 60 link 65(CDP)

Jun 13 09:22:29.248: Serial0/0.2(o): dlci 60(0xCC1), pkt type 0x2000(CDP), datag

ramsize 307

Jun 13 09:22:29.336: broadcast dequeue

Jun 13 09:22:29.336: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:22:29.336: broadcast dequeue

Jun 13 09:22:29.336: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:22:29.336: broadcast dequeue

Jun 13 09:22:29.336: Serial0/0.2(o):Pkt sent on dlci 60(0xCC1), pkt type 0x2000(

CDP), datagramsize 307

Jun 13 09:23:10.252: Serial0/0.2: encaps failed--line down

Please check attachments for additional debugging and show commands.

Thank you all for your input.

Steven

Thanks for the additional information. I believe that the output of both the show frame-relay pvc and of debug frame-relay lmi are consistent and show that there is no DLCI 60 coming to you from the switch. I know that your original post indicates that you have confirmed the PVC with the provider, but the evidence of the show commands does not support that. In the show frame-relay pvc the status of deleted usually is an indicator that you have identified the PVC but that the switch is not configured for it. Also the debug frame-relay lmi shows the information that the switch is sending to you including the PVCs that it is sending. This output is pretty clear that the switch is sending you 2 PVCs (DLCIs 17 and 18) but not 60.

Jun 13 09:26:10.254: Serial0/0(in): Status, myseq 133

Jun 13 09:26:10.254: RT IE 1, length 1, type 0

Jun 13 09:26:10.254: KA IE 3, length 2, yourseq 108, myseq 133

Jun 13 09:26:10.254: PVC IE 0x7 , length 0x3 , dlci 17, status 0x2

Jun 13 09:26:10.254: PVC IE 0x7 , length 0x3 , dlci 18, status 0x2

Your attempting to send on a DLCI that the switch does not recognize as yours is also consistent with the encapsulation error.

I suggest that you talk to the provider again. Because it surely does not look to me like their switch is sending this router DLCI 60.

HTH

Rick

HTH

Rick

Hi Rick

I certainly feel more confident taking this to them again with a very competent second opinion.

Much appreciated.

Steven

I am glad that we are able to help. I think the show frame-relay pvc is informative but I believe that the debug frame-relay lmi is especially convincing that the frame relay switch is not announcing DLCI 60 to you.

If you get an answer I encourage you to post back to the forum indicating what you found (and if the problem is resolved (hopefully) what the resolution was). It makes the forum more useful when we can read about a problem and then see what the answer or the resolution was.

HTH

Rick

HTH

Rick

Rick

I queried them again and made the tech actually look at what DLCIs were running on the circuit, and yes, we discovered we were talking about totally different circuits!

Steven

I am glad that you found the answer. That kind of confusion in provisioning new connections does happen sometimes - especially when there is more than one circuit for a customer.

Thanks for posting back to the forum and indicating the solution. This makes the forum more useful when people can read about a problem and can see what its solution was.

I encourage you to continue your participation in the forum.

HTH

Rick

HTH

Rick
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: