From: John Conzone (jkconzone@xxxxxxxx)
Date: Sat Sep 16 2000 - 20:01:50 GMT-3
Yes. If the primary goes down, then the backup will take over. However,
the sessions on the primary drop and must restablish with the backup. No
"staeful failover" or anything like that.
When primary comes back, all new sessions will go to primary, and backup
will stay up until its LLC2 session are finished
----- Original Message -----
From: "Aaron DuShey" <aaron.dushey@dushey-consulting.com>
To: "CCIE (E-mail)" <ccielab@groupstudy.com>
Sent: Saturday, September 16, 2000 6:39 PM
Subject: dlsw backup peers
> When using DLSW backup peers, is the backup supposed to remain in the
> DISCONN state?
> see below
> Situation
> r2 normal peer
> r6,r5 -r6 primary r5 backup peer
> r2#dp
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> TCP 192.5.3.3 CONNECT 165 165 conf 0 0 0
> 01:22:40
> TCP 192.5.6.6 CONNECT 18 18 conf 0 0 0
> 00:08:07
> TCP 192.5.5.5 DISCONN 0 0 conf 0
> - -
> Total number of connected peers: 2
> Total number of connections: 2
>
> r2#r
> Building configuration...
>
>
>
> Current configuration:
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname r2
> !
> enable secret 5 $1$7Opo$gjBFI7.oa.7FdqrjO/4e8/
> !
> ip subnet-zero
> no ip domain-lookup
> ip multicast-routing
> ip dvmrp route-limit 20000
> ipx routing 0002.0002.0002
> !
> voice-port 1/0/0
> !
> voice-port 1/1/0
> !
> voice-port 1/0/1
> !
> voice-port 1/1/1
> !
> d
> source-bridge ring-group 100
> dlsw local-peer peer-id 192.5.2.2 group 100 border
> dlsw remote-peer 0 tcp 192.5.3.3
> dlsw remote-peer 0 tcp 192.5.6.6
> dlsw remote-peer 0 tcp 192.5.5.5 backup-peer 192.5.6.6
> !
> !
> !
> interface Loopback0
> ip address 192.5.2.2 255.255.255.0
> no ip directed-broadcast
>
> r2#
>
> Aaron DuShey
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:57 GMT-3