Frame-relay PVC Issue - CISCO, status deleted

dkhouri · ‎10-17-2010

Hi,

Been pulling my hair out on this one!! OK in my lab environment I have a hub (R1) & spoke (R2 and R3) network with a frame relay switch (R6). For some reason, I am seeing CISCO, status deleted on the spoke routers. This is not allowing me to PING. Here's a quick look at all the configurations;

R6 - Frame Relay Switch

interface Serial0
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 56000
no fair-queue
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 122 interface Serial1 221
frame-relay route 123 interface Serial2 321
!
interface Serial1
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 56000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 221 interface Serial0 122
!
interface Serial2
no ip address
encapsulation frame-relay
logging event subif-link-status
logging event dlci-status-change
clock rate 56000
no frame-relay inverse-arp
frame-relay intf-type dce
frame-relay route 321 interface Serial0 123

R6#show frame-relay route
Input Intf      Input Dlci      Output Intf     Output Dlci     Status
Serial0         122             Serial1         221             active
Serial0         123             Serial2         321             active
Serial1         221             Serial0         122             active
Serial2         321             Serial0         123             active

R1 - Hub

R1#show run int serial 0/1
Building configuration...

Current configuration : 214 bytes
!
interface Serial0/1
ip address 172.0.123.1 255.255.255.248
encapsulation frame-relay
frame-relay map ip 172.0.123.2 122 broadcast
frame-relay map ip 172.0.123.3 123 broadcast
no frame-relay inverse-arp
end

R1#show frame-relay map
Serial0/1 (up): ip 172.0.123.2 dlci 122(0x7A,0x1CA0), static,
              broadcast,
              CISCO, status defined, active
Serial0/1 (up): ip 172.0.123.3 dlci 123(0x7B,0x1CB0), static,
              broadcast,
              CISCO, status defined, active

R1#show frame-relay pvc

PVC Statistics for interface Serial0/1 (Frame Relay DTE)

              Active     Inactive      Deleted       Static
Local          2            0            0            0
Switched       0            0            0            0
Unused         0            0            0            0

R2 - Spoke

R2#show run interface serial 0/0
Building configuration...

Current configuration : 258 bytes
!
interface Serial0/0
ip address 172.0.123.2 255.255.255.248
encapsulation frame-relay
fair-queue
frame-relay map ip 172.0.123.1 221 broadcast
frame-relay map ip 172.0.123.3 221 broadcast
frame-relay interface-dlci 221
no frame-relay inverse-arp
end

R2#show frame-relay map
Serial0/0 (up): ip 172.0.123.1 dlci 221(0xDD,0x34D0), static,
              broadcast,
              CISCO, status deleted
Serial0/0 (up): ip 172.0.123.3 dlci 221(0xDD,0x34D0), static,
              broadcast,
              CISCO, status deleted

R2#show frame-relay pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

              Active     Inactive      Deleted       Static
Local          0            0            1            0
Switched       0            0            0            0
Unused         1            0            0            0

R3 - Spoke

R3#show run int ser0/0
Building configuration...

Current configuration : 261 bytes
!
interface Serial0/0
ip address 172.0.123.3 255.255.255.248
encapsulation frame-relay
no fair-queue
frame-relay map ip 172.0.123.1 321 broadcast
frame-relay map ip 172.0.123.2 321 broadcast
frame-relay interface-dlci 321
no frame-relay inverse-arp
end

R3#show frame-relay map
Serial0/0 (up): ip 172.0.123.1 dlci 321(0x141,0x5010), static,
              broadcast,
              CISCO, status deleted
Serial0/0 (up): ip 172.0.123.2 dlci 321(0x141,0x5010), static,
              broadcast,
              CISCO, status deleted

R3#show frame-relay pvc

PVC Statistics for interface Serial0/0 (Frame Relay DTE)

              Active     Inactive      Deleted       Static
Local          0            0            1            0
Switched       0            0            0            0
Unused         1            0            0            0

Am I forgetting something??

Thanks

DK

tprendergast · ‎10-19-2010

Deleted seems to indicate your frame switch isnt passing down the DLCI to you.

1) Have you made sure "frame-relay switching" is configured on R6?

2) On all three routers do: show frame-relay pvc | i ACTIVE

3) On all three routers do: show frame-relay map

Once you post that data back, we can help you further.

Thanks!

Tim

dkhouri · ‎10-19-2010

Hi Tim,

Sorry, forgot to show that "frame-relay switching" was already configured on R6. All the other commands you asked for were already in my initial post!

I decided to erase the configuration on all routers and the FR switch. Starting again, I managed to get them showing as active.

This is what I believe was the problem:

When I enabled encapsulation grame-relay, inverse arp was enabled and may have paired incorrectly. So I shutdown the serial interface, cleared all inarp entries, removed the encapsulation frame-relay settings of the serial interface, disabled inverse-arp and reconfigured the interface as normal. After that I managed to see the spokes show up as active.

I also added 2 interface-dlci references on the hub router which I forgot to.

kridsdale · ‎06-17-2015

Hi,

In GNS3 I had the same thing and went right back to basics. Had a FR switch in the middle and ONLY put "encaps frame-relay" on a pair of (simulated) 7200 routers' interfaces - as everything else was then default. The console logging suddenly stated that the relevant interface came up, the PVC showed as created... and then I could ping across.... so for me it was going back to basics....softly softly catchee monkey !!!

Then I started adding other FR parameters, but always keeping an eye on the int/pvc status to see it was NOT torn down

cheers

Kev

Grant Curell · ‎01-24-2014

I realize this post is pretty old, but I just wanted to give everyone a heads up that what worked for me was just deleting the subinterfaces I was using and rebuilding them. It also seemed that I had to assign the IP address first before configuring the interface DLCI. It's a little different than the listed problem, but hopefully this helps someone.

kennethvargas33017179 · ‎01-18-2016

This helped me a lot.

Thanks.

I had the same issue so I a deleted the interface in the topology and it did the trick.

Thanks again.

Grant Curell · ‎01-19-2016

I'm glad it helped!

Edit: My god... did I really write that two years ago??? Feels like that was yesterday O.o