RE: Backup using snapshot routing

From: Mark Thomas (Mark.Thomas@xxxxxxxxxxxxxxxx)
Date: Sat Aug 10 2002 - 03:24:58 GMT-3


   
That similar to my understanding, I should have explained more, I am creating i
nteresting traffic on the client before during and after the connection is down
It just that no route ever takes over from the one that's down similar to the e
xample as shown on page 524 in Solie unless I load balance and that's not the p
oint

I pulled that lab apart so I will recreate this later today and try downing the
 port (as suggested)on the cat rather than using ipx down or taking off the net
work addressing.

Anyone else had similar issues with snapsot routing,

Regards

Mark

-----Original Message-----
From: kasturi cisco [mailto:kasturi_cisco@hotmail.com]
Sent: Saturday, 10 August 2002 12:31 AM
To: kurt@superonline.net; Mark.Thomas@it.alstom.com.au; ccielab@groupstudy.com
Subject: RE: Backup using snapshot routing

Mark,

The way i understand it is Snapshot routing by itself is not a backup
mechanism,so when the link fails if u have interesting traffic (in form of
Ping or actual traffic) the link would come up.Snapshot routing is actually
used to ensure that DV protocols dont keep the link up due to periodic route
updates or other broadcasts. So try pinging or claering the routing table on
the client.

HTH. Anyone care to add or correct me.Let me know.

Good luck,
kasturi.

>From: Erhan Kurt <kurt@superonline.net>
>Reply-To: Erhan Kurt <kurt@superonline.net>
>To: Mark Thomas <Mark.Thomas@it.alstom.com.au>,
>"'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
>Subject: RE: Backup using snapshot routing
>Date: Fri, 9 Aug 2002 14:57:52 +0300
>
>To trigger backup interface:
>
>Use set port disable in Cat for eth.
>Use shut in FR switch in a FR interface.
>
>
>
>-----Original Message-----
>From: Mark Thomas [mailto:Mark.Thomas@it.alstom.com.au]
>Sent: 09 Apustos 2002 Cuma 14:07
>To: 'ccielab@groupstudy.com'
>Subject: Backup using snapshot routing
>
>
>Hello All
>
>Snapshot routing is driving me nuts
>
>Simple scenario
>Using ipx rip and ip rip or igrp (none of them work)
>
>The Ethernet is the primary and ISDN the backup Bri0---------Bri0
>R5 R6
>E0-----------E0
>
>I can bring the link up manually with both protocols but snapshot
>routing never works for any protocol when the Ethernet is downed by ipx
>down or shutdown or having its address removed.
>
>Here are the configs, if anyone could shed some light on this I would
>be grateful
>
>version 12.1
>!
>hostname r5
>username r6 password 0 cisco
>!
>ipx routing 0005.0005.0005
>isdn switch-type basic-ni
>!
>interface Loopback0
> ip address 5.5.5.5 255.255.255.0
> ipx network 5
>!
>interface Ethernet0
> mac-address 0005.0005.0005
> ip address 128.10.100.5 255.255.255.0
> ipx network 100
>!
>interface BRI0
> ip address 128.10.56.5 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 45
> dialer map snapshot 1 name r6 broadcast 8358662
> dialer map ip 128.10.56.6 name R6 broadcast 8358662
> dialer map ip 128.10.56.6 name R6 broadcast 8358664
> dialer map ipx 56.0006.0006.0006 name r6 broadcast 8358662 dialer
>map
>ipx
>56.0006.0006.0006 name r6 broadcast 8358664 dialer-group 1 ipx network 56
>no ipx route-cache ipx watchdog-spoof ipx spx-spoof isdn switch-type
>basic-ni isdn spid1 0835866101 8358661 isdn spid2 0835866301 8358663
>snapshot client 5 1200 suppress-statechange-update dialer ppp
>authentication chap ! router igrp 1 network 5.0.0.0 network 128.10.0.0 !
>access-list 900 deny any any sap log access-list 900 deny any any rip log
>access-list 900 deny any any 457 log access-list 900 permit any any all
>dialer-list 1 protocol ipx list 900 dialer-list 1 protocol ip permit !
>
>
>
>hostname r6
>username r5 password 0 cisco
>!
>ipx routing 0006.0006.0006
>isdn switch-type basic-ni
>!
>interface Loopback0
> ip address 6.6.6.6 255.255.255.0
> ipx network 6
>!
>interface Ethernet0
> mac-address 0006.0006.0006
> ip address 128.10.100.6 255.255.255.0
> ipx network 100
>!
>interface BRI0
> ip address 128.10.56.6 255.255.255.0
> encapsulation ppp
> dialer map ipx 56.0005.0005.0005 name r5 broadcast 8358661 dialer
>map
>ipx
>56.0005.0005.0005 name r5 broadcast 8358662 dialer-group 1 ipx network 56
>no ipx route-cache ipx watchdog-spoof ipx spx-spoof isdn switch-type
>basic-ni isdn spid1 0835866201 8358662 isdn spid2 0835866401 8358664
>snapshot server 5 dialer ppp authentication chap ! router igrp 1 network
>6.0.0.0 network 128.10.0.0 ! access-list 1 permit 5.0.0.0 log access-list
>900 deny any any rip log access-list 900 deny any any sap log access-list
>900 deny any any 457 log access-list 900 permit any any log dialer-list 1
>protocol ipx list 900 dialer-list 1 protocol ip permit ! ! ! Regards
>
>Mark
>
>CONFIDENTIAL: This e-mail and any attachments are confidential and may
>be privileged. If you are not a named recipient, please notify the
>sender immediately and do not disclose the contents to another person,
>use it for any purpose or store or copy the information in any medium.



This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:22 GMT-3