From: Katopodis, Ange (angek@xxxxxxxxx)
Date: Sun Nov 25 2001 - 08:20:00 GMT-3
Vincent you are right ipx update interval sap behaves as you explained.
ipx update sap interval changes-only is used when the routing protocol
in use is ipx rip. It results in a 'link state like' behaviour where the
router only sends SAP changes instead of the default periodic updates
every 60 seconds.
ipx sap-incremental eigrp X does the same thing when the ipx-eigrp
routing protocol is used.
Note that most Novell File Servers run IPX RIP and use the default
RIP/SAP periodic update timers of 60 secs. They age entries if they miss
three updates. So if you are using the above methods ensure that no File
Servers are on the interfaces where the timers are being implemented; or
else it will result is RIP/SAP flapping and loss of visibility.
Ange
-----Original Message-----
From: Matt Smith [mailto:matt-n-donna@cablespeed.com]
Sent: Sunday, 25 November 2001 7:14 AM
To: Vincent Zhang; ccielab@groupstudy.com
Subject: Re: IPX SAP udate
I also have one question to add to this one. How does the ipx update sap
interval changes-only compare to the ipx sap-incremental eigrp X ??
Anyone
have a clear understanding of when to use one versuses the other?
Thanks in advance for your time
Matt Smith
----- Original Message -----
From: "Vincent Zhang" <vincentzhang@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, November 24, 2001 1:17 AM
Subject: IPX SAP udate
> Hi all,
>
> What is the difference of two parameters of" passive" and
"changes-only"
in
> command "ipx update intervl sap ...."?
>
> for passive, -> Listen but do not send periodic SAP updates and
flashes
> for changes-only, -> update on change ony
>
> these two will reduce the unnecessary SAP trffic,right ?
>
> BTW, it's from bootcamp 19 , IPX section , item 3.
>
> Thanks, V
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:22 GMT-3