From: liqunhui@LANGCHAO.COM.CN
Date: Mon Apr 28 2003 - 23:34:31 GMT-3
i think the backup interface command monitor the physical interface state
if physical interface is up, isdn will never go up
----- Original Message -----
From: "Tom Young" <gitsyoung@yahoo.co.jp>
To: <ccielab@groupstudy.com>
Sent: Tuesday, April 29, 2003 2:28 AM
Subject: isdn backup
> Hi, group
>
> I made a isdn backup for my s0.1. The isdn is active, but
> if I set the backup int b0 command, the b0 into the
> standby status.And don't active forever, even I shutdown
> the s0.1, maybe I couldn't use the callback in the same
> time?
>
>
> r5#sh dia
> !
> !
> interface Loopback0
> ip address 137.50.50.1 255.255.255.0
> !
> interface Loopback10
> ip address 5.5.5.5 255.255.255.0
> !
> interface Ethernet0
> no ip address
> ip ospf priority 0
> shutdown
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> frame-relay lmi-type ansi
> !
> interface Serial0.1 multipoint
> bandwidth 64
> backup delay 2 2
> backup interface BRI0
> ip address 172.168.100.5 255.255.255.0
> ip ospf priority 200
> frame-relay map ip 172.168.100.3 503 broadcast
> frame-relay map ip 172.168.100.6 506 broadcast
> no frame-relay inverse-arp
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> no ip route-cache
> no ip mroute-cache
> frame-relay lmi-type ansi
> !
> interface Serial1.1 multipoint
> ip address 172.168.200.5 255.255.255.0
> no ip route-cache
> no ip mroute-cache
> frame-relay map ip 172.168.200.4 504 broadcast
> frame-relay map ip 172.168.200.8 508 broadcast
> no frame-relay inverse-arp
> !
> interface BRI0
> ip address 65.1.1.1 255.255.255.0
> encapsulation ppp
> ip ospf demand-circuit
> dialer map ip 65.1.1.2 name r6 class call broadcast 2002
> dialer-group 1
> isdn switch-type basic-net3
> ppp callback accept
> ppp authentication chap callin
> !
> router ospf 1
> log-adjacency-changes
> area 0 range 65.0.0.0 255.0.0.0
> redistribute igrp 1 metric 200 metric-type 1 subnets
> network 65.1.1.1 0.0.0.0 area 0
> network 172.168.100.5 0.0.0.0 area 0
> neighbor 172.168.100.6 priority 1
> neighbor 172.168.100.3 priority 1
> default-information originate always metric-type 1
> !
> router igrp 1
> timers basic 5 15 0 30
> redistribute ospf 1
> passive-interface Serial0.1
> network 172.168.0.0
> default-metric 64 100 255 1 1500
> !
> router bgp 5
> bgp log-neighbor-changes
> network 5.5.5.0 mask 255.255.255.0
> neighbor 172.168.100.3 remote-as 3
> neighbor 172.168.100.6 remote-as 6
> neighbor 172.168.200.4 remote-as 4
> !
> ip kerberos source-interface any
> ip classless
> no ip http server
> !
> !
> map-class dialer call
> dialer callback-server username
> dialer-list 1 protocol ip permit
> !
> alias exec sir sh ip route
> alias exec cir clear ip route *
> !
> line con 0
> transport input none
> line aux 0
> line vty 0 4
> privilege level 15
> login
> !
> end
>
> When I show the dialer , I found the interface was down.
>
>
>
> BRI0 - dialer type = ISDN
>
> Dial String Successes Failures Last DNIS Last
> status
> 2002 33 1 00:06:12
> successful
> 0 incoming call(s) have been screened.
> 0 incoming call(s) rejected for callback.
>
> BRI0:1 - dialer type = ISDN
> Idle timer (120 secs), Fast idle timer (20 secs)
> Wait for carrier (30 secs), Re-enable (15 secs)
> Dialer state is shutdown
>
> BRI0:2 - dialer type = ISDN
> Idle timer (120 secs), Fast idle timer (20 secs)
> Wait for carrier (30 secs), Re-enable (15 secs)
> Dialer state is shutdown
> r5#
>
>
> Where the problem ?
>
>
> Thanks alot
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:09 GMT-3