From: robert patterson (rpatters@xxxxxxxxxxx)
Date: Sun May 07 2000 - 16:33:10 GMT-3
Thanks Mike,
I was following that story line and threw the config into
the lab equipment last night. I created static saps while
debug bugging ipx sap and kept getting the error that
the route of my sap was not in the table. Sure enough,
the ipx route of my sap origin lnterface was not in any of the routers
that carried the 'rsup-only' command. Debug of ipx eigrp routing
showed that route updates didn't even attempt to go out these
'rsup-only' interfaces even though they were both part of the
same ipx eigrp system. Without the route first being in the table,
the sap will not be accepted.
Caslows' book..page 511, says IPX EIGRP does not send out periodic
updates of saps or routes unless a change occurs. However, on the one
router with a static sap configured, I get the following meesage every
60 seconds:
router-5#
IPXSAP: positing update to 50.ffff.ffff.ffff via Loopback0 (broadcast)
(full)
IPXSAP: suppressing null update to 50.ffff.ffff.ffff
IPXSAP: positing update to 303.ffff.ffff.ffff via Ethernet0
(broadcast) (full)
IPXSAP: Update type 0x2 len 96 src:303.0000.0c3e.7d74
dest:303.ffff.ffff.ffff(45
2)
type 0x0, "server", 50.0000.0000.0001(4), 6 hops
IPXSAP: positing update to 50.ffff.ffff.ffff via Loopback0 (broadcast)
(full)
IPXSAP: suppressing null update to 50.ffff.ffff.ffff
IPXSAP: positing update to 303.ffff.ffff.ffff via Ethernet0
(broadcast) (full)
IPXSAP: Update type 0x2 len 96 src:303.0000.0c3e.7d74
dest:303.ffff.ffff.ffff(45
2)
type 0x0, "server", 50.0000.0000.0001(4), 6 hops
IPXSAP: positing update to 50.ffff.ffff.ffff via Loopback0 (broadcast)
(full)
IPXSAP: suppressing null update to 50.ffff.ffff.ffff
IPXSAP: positing update to 303.ffff.ffff.ffff via Ethernet0
(broadcast) (full)
IPXSAP: Update type 0x2 len 96 src:303.0000.0c3e.7d74
dest:303.ffff.ffff.ffff(45
2)
type 0x0, "server", 50.0000.0000.0001(4), 6 hops
the router config...
!
ipx router eigrp 1
network 303
network 50
!
!
ipx router rip
no network all
!
!
ipx sap 0 server 50.0000.0000.0001 4 5
Do you see any problems here??? Why is it still sapping?
Robert Patterson B.A.EE MCSE CNE 4.0 CCNP CCDA
Senior Systems Engineer
KentDatacomm
----------
> From: Mike@ccci.com
> To: Bob Reed <bobr@mmcable.com>; peter brown <pita40@hotmail.com>;
ccielab@groupstudy.com
> Subject: Re: SAP traffic
> Date: Monday, June 05, 2000 4:36 PM
>
> It's my understanding that there is a huge potential pitfall to be
aware of
> here. When you use the reliable SAP protocol via the 'rsup-only'
> keyword, IPX EIGRP no longer sends IPX routes. Routing must occur
via RIP.
>
> Details Here:
> http://www.cisco.com/univercd/cc/td/doc/cisintwk/ics/cs005.htm
>
> HTH,
> Mike
> Halifax, next Tues - Wed
>
> At 02:16 PM 5/6/00 -0500, Bob Reed wrote:
> >ipx eigrp will do this, you also can use just the incemental sap
update part
> >of it with out using eigrp. That is what the rsup option does.
> >
> >Bob Reed
> >----- Original Message -----
> >From: peter brown <pita40@hotmail.com>
> >To: <ccielab@groupstudy.com>
> >Sent: Saturday, May 06, 2000 1:03 PM
> >Subject: SAP traffic
> >
> >
> > > Because my network is generating alot of SAP traffic, I want to
allow SAP
> > > only when a server is added or deleted from the network. Is
using ipx
> >eigrp
> > > the correct way to accomplish this?
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:27 GMT-3