From: Danny.Andaluz@triaton-na.com
Date: Wed Oct 15 2003 - 12:27:22 GMT-3
Thanks for the explanation. Do you mean if the dialer argument isn't
configured on the client, it won't dial to exchange routing information when
the active time comes around? The doc CD says this is an optional argument.
Thanks,
Danny
-----Original Message-----
From: Annu Roopa [mailto:annu_roopa@yahoo.com]
Sent: Wednesday, October 15, 2003 11:00 AM
To: Andaluz, Danilo, Triaton/NA; ccielab@groupstudy.com
Subject: Re: Snapshot routing client side
Danny,
This is how i have understood it.
snapshot client 5 30 - this wont not let the client side to call the server
side.So with "dialer" option it makesthe client dial when the quite period
expires to xchange Routing table.
snapshot client 5 30 dialer - This will enable the client to dial. When the
active time gets over say 5 mts it goes into Quite state for 30 mts. Now let
us say u ping from this router to the other side while in quite state (
"show snapshot" shows router is in Quite state and still 10 mts left) the
Bri0 interface comes up and router transitions to "Active" state for next 5
mts and router xchanges routing updates.
snapshot client 5 30 suppress-statechange-update dialer - same as above
except that when u ping, the interface comes up but routing updates wont be
exchanged and it wont transition to Active state....meaning any transition
of interface wont make a state change.At end of Quite period it calls and
xchanges routing information.
HTH. Let me know if u need more clarity.
Regards,
Annu
Danny.Andaluz@triaton-na.com wrote:
Hey, Group. I am having trouble understanding this argument on the snapshot
client configuration. It's the "dialer" option at the end of the command.
This is straight from CCO:
snapshot client 5 30 suppress-statechange-update dialer
!-- This is a client side with an active period of 5 minutes and quiet
period of
!-- 30 minutes. Routing table updates are not exchanged when other
interesting
!-- traffic has activated the interface. <<
!-- start the active period for exchanging routing table updates.>>>
As far as the above, doesn't the client do this anyway. He is the one that
initiates the call to get routing information.
This is what the command reference says on the doc cd. It's equally as vague
(to me anyway):
Thanks,
Danny
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Mon Nov 24 2003 - 07:53:02 GMT-3