From: ali (asayyed@atheer.net.sa)
Date: Sun Jun 13 2004 - 12:50:52 GMT-3
Did that mean the ip ospf resync-timeout is used in the NSF scenario just
t is clear now.. thnx
-----Original Message-----
From: Rohan Grover [mailto:rohang@cisco.com]
Sent: Sunday, June 13, 2004 6:26 PM
To: 'ali'; ccielab@groupstudy.com
Subject: RE: ospf timers
Hi,
Ip ospf resync-timeout is used in the HA NSF (non stop forwarding scenario)
When an OSPF NSF-aware router performs a switchover to the standby processor
it send a special hello packet to its adjacent
neighbours asking help in resynchronising database with no state change
(stateful switchover)
The adjacent router maintains the resync-timeout = dead interval = 40 secs.
If the resync is not done in that time it brings down
the adjacency.
The resync timer can be made independent of the dead interval time.
Thnaks
Rohan
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ali
Sent: Sunday, June 13, 2004 8:34 PM
To: ccielab@groupstudy.com
Subject: ospf timers
Dear All
Did there is any body can tell me the deffrence between this two command in
ospf .. and how they will not overlap each other
ip ospf resync-timeout
ip ospf dead-interval
ali
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of John
Cameron (johcamer)
Sent: Sunday, June 13, 2004 5:23 PM
To: Karim; ccielab@groupstudy.com
Subject: RE: Watch-list question....
Karim,
For the first scenario - I would use two floating static and dialer-map
statements.
For the second scenario, I would use dialer-watch. Dialer-watch will not
kick in until ALL "watched" routes are lost - so it would
not work for your first scenario.
From Cisco IOS Dial Technologies Configuration Guide, Release 12.3:
"Monitoring the watched routes is done in the following sequence:
1. Whenever a watched route is deleted, Dialer Watch checks whether there is
at least one valid route for any of the defined watched
IP addresses.
2. If no valid route exists, the primary line is considered down and
unusable.
3. If a valid route exists for at least one of the defined IP addresses and
if the route is pointing to an interface other than the
backup interface configured for Dialer Watch, the primary link is considered
up.
4. If the primary link goes down, Dialer Watch is immediately notified by
the routing protocol and the secondary link is brought up.
5. Once the secondary link is up, at the expiration of each idle timeout,
the primary link is rechecked.
6. If the primary link remains down, the idle timer is indefinitely reset.
7. If the primary link is up, the secondary backup link is disconnected.
Additionally, you can set a disable timer to create a delay
for the secondary link to disconnect, after the primary link is
reestablished. "
HTH,
JDC
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Karim
Sent: Sunday, June 13, 2004 9:55 AM
To: ccielab@groupstudy.com
Subject: Watch-list question....
Hi all,
Would like to know the difference between the following 2 scenarios:
- When asked to initiate a call when losing reachability to any of 2 given
routes to watch.
I believe that I need to create 2 dialer-maps statement (if using legacy
DDR) plus dialer watch-group (in either legacy or dailer interfaces).
Whenever the reachability lost to any of the two routes, a
call will be initiated.
- I asked not to initiate a call only if reachability lost to both routes,
what will be the solution ????
Regards,
Karim.
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:39 GMT-3