can you pu dial back up on Serial line PVC that has 2 DLCI's?
I have a remote site that has one cisco router with 1 CSU/DSU connecting to the S1 interface. On that I have two DLCI's that go to the Frame cloud. I have DDR backup dial interface, but it is married to the s1.1 interface. I want to use the dialbackup on the S1 interface so that when the whole circuit goes down, it will activate. Now when only one of the DLCI's goes down the dialback up activates. I have tried to move the dailbackup statement to the S1 interface with no luck.....thoughts guru's?
Here is a drawing and the config file....
Editied config.....
clock timezone pst -8
clock summer-time pdt recurring
ip subnet-zero
no ip domain-lookup
!
chat-script dialit "" "ATH" TIMEOUT 10 OK "ATDT\T" TIMEOUT 60 CONNECT
chat-script rusr "" "ATV1E0&Q1" TIMEOUT "OK" ""
!
!
!
interface Ethernet0
description Lan in KENT
ip address 128.3.250.0 255.255.0.0
ip helper-address 128.1.0.29
ip helper-address 128.1.0.26
ip helper-address 128.1.0.96
!
interface Serial0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
no fair-queue
!
interface Serial1
no ip address
encapsulation frame-relay
no ip route-cache
no ip mroute-cache
!
interface Serial1.1 point-to-point
description WAN CONNECTION TO NORFOLK DHEC.577331
backup delay 30 30
backup interface Async1
ip address 128.203.0.2 255.255.0.0
no ip route-cache
no ip mroute-cache
frame-relay class vcfif
frame-relay interface-dlci 100
!
interface Serial1.2 point-to-point
description WAN Connection to Chester MCI
ip address 128.103.0.2 255.255.0.0
no ip route-cache
no ip mroute-cache
frame-relay interface-dlci 225
!
interface Async1
ip address 128.200.0.5 255.255.0.0
encapsulation ppp
no ip route-cache
no ip mroute-cache
keepalive 10
dialer in-band
dialer idle-timeout 300
dialer wait-for-carrier-time 120
dialer map ip 128.200.0.1 name MDVBACKUP modem-script dialit broadcast 17578574052
dialer map ipx BAC0001.0004.2714.dbc0 name MDVBACKUP modem-script dialit broadcast 17578574052
dialer-group 1
async default routing
async dynamic address
async dynamic routing
async mode dedicated
ppp authentication chap
!
router eigrp 500
redistribute connected
network 128.3.0.0
network 128.103.0.0
network 128.200.0.0
network 128.203.0.0
no auto-summary
!
no ip classless
ip route 0.0.0.0 0.0.0.0 128.103.0.1
ip route 0.0.0.0 0.0.0.0 128.203.0.1 50
ip route 128.1.0.0 255.255.0.0 128.203.0.1
ip route 128.1.0.0 255.255.0.0 128.103.0.1 50
no ip http server
!
!
map-class frame-relay vcfif
frame-relay end-to-end keepalive mode request
logging 128.3.0.3
access-list 60 permit 128.1.50.2
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
fife-router-issue.jpg
Here is a drawing and the config file....
Editied config.....
clock timezone pst -8
clock summer-time pdt recurring
ip subnet-zero
no ip domain-lookup
!
chat-script dialit "" "ATH" TIMEOUT 10 OK "ATDT\T" TIMEOUT 60 CONNECT
chat-script rusr "" "ATV1E0&Q1" TIMEOUT "OK" ""
!
!
!
interface Ethernet0
description Lan in KENT
ip address 128.3.250.0 255.255.0.0
ip helper-address 128.1.0.29
ip helper-address 128.1.0.26
ip helper-address 128.1.0.96
!
interface Serial0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
no fair-queue
!
interface Serial1
no ip address
encapsulation frame-relay
no ip route-cache
no ip mroute-cache
!
interface Serial1.1 point-to-point
description WAN CONNECTION TO NORFOLK DHEC.577331
backup delay 30 30
backup interface Async1
ip address 128.203.0.2 255.255.0.0
no ip route-cache
no ip mroute-cache
frame-relay class vcfif
frame-relay interface-dlci 100
!
interface Serial1.2 point-to-point
description WAN Connection to Chester MCI
ip address 128.103.0.2 255.255.0.0
no ip route-cache
no ip mroute-cache
frame-relay interface-dlci 225
!
interface Async1
ip address 128.200.0.5 255.255.0.0
encapsulation ppp
no ip route-cache
no ip mroute-cache
keepalive 10
dialer in-band
dialer idle-timeout 300
dialer wait-for-carrier-time 120
dialer map ip 128.200.0.1 name MDVBACKUP modem-script dialit broadcast 17578574052
dialer map ipx BAC0001.0004.2714.dbc0 name MDVBACKUP modem-script dialit broadcast 17578574052
dialer-group 1
async default routing
async dynamic address
async dynamic routing
async mode dedicated
ppp authentication chap
!
router eigrp 500
redistribute connected
network 128.3.0.0
network 128.103.0.0
network 128.200.0.0
network 128.203.0.0
no auto-summary
!
no ip classless
ip route 0.0.0.0 0.0.0.0 128.103.0.1
ip route 0.0.0.0 0.0.0.0 128.203.0.1 50
ip route 128.1.0.0 255.255.0.0 128.203.0.1
ip route 128.1.0.0 255.255.0.0 128.103.0.1 50
no ip http server
!
!
map-class frame-relay vcfif
frame-relay end-to-end keepalive mode request
logging 128.3.0.3
access-list 60 permit 128.1.50.2
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
fife-router-issue.jpg
ASKER
no.....the DLCI's go to different parts of the country.
why dont you just use an ISDN backup
The point is to failover to a 3rd option only after the first two are in a down state.
If the circuits were terminating to the same router, a multilink interface with the failover would work -- which is what is needed, a single interface to handle both serial interfaces. I can't find any documentation that provides for a primary and secondary backup interface.
If the circuits were terminating to the same router, a multilink interface with the failover would work -- which is what is needed, a single interface to handle both serial interfaces. I can't find any documentation that provides for a primary and secondary backup interface.
ASKER
feya28, no help.
jesper...It is one physical interface with 2 sub interfaces "DLCI's" So the question remains:
How to put the backup on the S1 so that if both DLCI's go down, the dialback will kick in...
jesper...It is one physical interface with 2 sub interfaces "DLCI's" So the question remains:
How to put the backup on the S1 so that if both DLCI's go down, the dialback will kick in...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you looked at frame-relay multilink? You set the IP address on the multilink (ppp) interface at both ends and specify the dialer backup on that same interface.
I haven't tried it but, if you can do this, logically it should work.