using isdn as backup for frame-relay

[sunnysunsz]

following is the configurationg :

interface BRI0

ip address 192.168.201.38 255.255.255.0

encapsulation ppp

dialer idle-timeout 180

dialer map ip 192.168.201.1 name nflkk-gz2800 broadcast 02081370421

dialer map ip 192.168.201.2 name nflkk-gz2800 broadcast 02081370422

dialer map ip 192.168.201.3 name nflkk-gz2800 broadcast 02081370423

dialer load-threshold 1 either

dialer-group 1

isdn switch-type basic-net3

ppp authentication chap

ppp multilink

!

interface Serial0

description pvc-to-guangzhou

bandwidth 256

ip address 192.168.200.154 255.255.255.252

service-policy output pospolicy

encapsulation frame-relay IETF

backup delay 30 30

backup interface BRI0

frame-relay interface-dlci 100

frame-relay lmi-type ansi

!

map-class frame-relay pvcmoniter

frame-relay end-to-end keepalive mode request

when frame-relay pvc is down,the isdn line can't activated.

i just want use static route ,how can i solve this problem?

thanks

[Georg Pauwen]

Hello,

since you have configured your Frame Relay on the physical interface, the 'backup interface' indeed typically doesn't work. The easiest solution for your scenario would be to configure a subinterface:

interface Serial0

no ip address

encapsulation frame-relay IETF

frame-relay lmi-type ansi

!

interface Serial0.1 point-to-point

description pvc-to-guangzhou

bandwidth 256

ip address 192.168.200.154 255.255.255.252

service-policy output pospolicy

backup delay 30 30

backup interface BRI0

frame-relay interface-dlci 100

Can you try and see if this works for you ?

Regards,

GP

[sunnysunsz]

Thanks for your reply!

In the cisco document article ,the end-to-end keepalive

feature can solve this problem.Have you ever used this command before?

And would you mind telling me why the point-to-point subinterface is able to find the problem of pvc?

[makchitale]

The Frame Relay End-to-End Keepalive feature works between peer Cisco communications devices only, this is a requirement. Do we have 2 Cisco end devices here? Also we need to have matching parameters at either end:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1830/products_feature_guide09186a0080087a58.html

I understand you want to stick to static routing, there is a newer feature called “Reliable static routing backup using object tracking” that can fit your requirements. For more info please refer to:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5413/products_feature_guide09186a00801d862d.html#wp1071672

Thanks, Mak