From: Masood Malik (malikm24@xxxxxxxxxxx)
Date: Wed Dec 20 2000 - 08:02:26 GMT-3
Guys,
While creating a static sap entry note the following from Caslow's book:
"With IPX static SAP's, if you place the static SAP on the network that will
be propogating the SAP's, it will not get propagated. You get "null updates
suppressed" on the Debug ipx sap statement"
This is due to split horizon effect.
This is what you have observed. A good practice in the lab exam is to create
an additional network on a loopback interface and associate static SAP's to
it. This what why loopback has worked for you. Trick here is to have the
network address from the loopback, Thus SAP's will be propogated through all
other interfaces.
Otherwise be aware of Split horizon and spend lot of precious time in
troubleshooting this landmine.
regards
Masood Malik
----- Original Message -----
From: "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
To: "'Mask Of Zorro'" <ciscokid00@hotmail.com>;
<Lauren_Dygowski@vanguard.com>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, December 20, 2000 8:13 AM
Subject: RE: IPX Sap services
> Thanks for all who replied. Tricky problem! Looks like the problem is
with
> Split-horizon and using mac address of actual node. I revised it to :
>
> ipx sap 4 fileserver 222.0000.0000.0001 0 2
>
> and that does the work. Eventhough the static sap entry was made and
> network 100 is frame-relay, I guess R2 does not want to advertise that
> network out of 100 since that is where the static is pointing to. I'm not
> sure if this is considered Split horizon problem or not as R2 never heard
> this SAP entry from IPX 100 network. I guess creating a static SAP entry
is
> the same as hearing from Network 100. I ended up creating a bogus network
> of 222 using loopback0 and also use bogus mac address...
>
> > Tin T. Bui
> > Senior Network Manager
> > Network Management Center
> > SBC Services Inc.
> > 7337 Trade Street, Rm 1110
> > San Diego, Ca 92121
> > Office #: 858-886-4589
> > Pager #: 858-494-0482
> > Fax #: 858-549-4103
> > Email: tb4565@sbc.com
> >
>
>
> -----Original Message-----
> From: Mask Of Zorro [mailto:ciscokid00@hotmail.com]
> Sent: Tuesday, December 19, 2000 1:18 PM
> To: Lauren_Dygowski@vanguard.com; BUI, TIN T (SBCSI)
> Cc: ccielab@groupstudy.com
> Subject: Re: IPX Sap services
>
>
> Definitely be aware of the direction and split horizon issues, but also
take
>
> note that your syntax for the ipx sap command is a little different that
> what you would think it would be... Don't use the actual mac address of
the
> node. Also, the sap should be advertised as 2 hops away.
>
> Mentor labs V-labs for IPX contain many examples of static sap's as that
is
> how they simulate Novell Servers in their scenario's. Check out the vlab
> entitled "1013. Configuring an IPX Network With Access Lists".
>
> Here is an example of some static sap entries done correctly:
>
> ipx sap 4 fileserver 100.0000.0000.0001 0 2
> ipx sap 7 printserver 100.0000.0000.0001 0 2
> ipx sap 107 rconsolecon 100.0000.0000.0001 0 2
>
> HTH.
>
> Z
>
>
> >From: Lauren_Dygowski@vanguard.com
> >Reply-To: Lauren_Dygowski@vanguard.com
> >To: "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
> >CC: ccielab@groupstudy.com
> >Subject: Re: IPX Sap services
> >Date: Tue, 19 Dec 2000 15:44:21 -0500
> >
> >Be mindful ofthe split-horizon rule with RIP/SAP. A router will not
send
> >a SAP
> >update back out an interface from which it came, this is also true for
> >static
> >SAPs based on the network you use in the SAP configuration. Make sure
that
>
> >you
> >provide a route for static SAPs in the correct direction, i.e. away from
> >where
> >you want the SAP to be advertised. If 100 is the frame IPX network and
> >your SAP
> >is pointing to network 100, then it will not be advertised that
direction.
>
> >One
> >way to fix this is to enter a static ipx route to a bogus network
pointing
> >out a
> >"stub" interface and use this network for the static SAP or place the
> >static
> >SAPs on an edge router so they are advertised into the backbone.
> >
> >
> >
> >
> >
> >
> >"BUI, TIN T (SBCSI)" <tb4565@sbc.com> on 12/19/2000 03:16:43 PM
> >Please respond to "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
> >
> >To: ccielab@groupstudy.com
> >cc: (bcc: Lauren Dygowski/IT/VGI)
> >Subject: IPX Sap services
> >
> >
> >
> >Does anyone know how to get SAP services advertised over frame-relay? I
> >have R5, R1, and R2 connected to Frame-relay switch. On R2 I have
defined
> >the following:
> >
> >ipx sap 4 Fileserver 100.0001.0001.0001 0 1
> >ipx sap 7 Printserver 100.0001.0001.0001 0 1
> >
> >I use frame map ipx net.node dlci broadcast on all frame interfaces and I
> >can ipx ping on all interfaces and can see all routes. However, when I
do
> >"Show ipx servers" on R5 or R1, I do not see the Fileserver or
PrintServer.
> >If I do show ipx servers on other routers (not on the Frame-relay), these
> >servers do show up okay. Any suggestions why sap servers don't get
> >advertised over frame and what commands I need to use to fix? thanks
> >
> >
> >
> > > Tin T. Bui
> > > Senior Network Manager
> > > Network Management Center
> > > SBC Services Inc.
> > > 7337 Trade Street, Rm 1110
> > > San Diego, Ca 92121
> > > Office #: 858-886-4589
> > > Pager #: 858-494-0482
> > > Fax #: 858-549-4103
> > > Email: tb4565@sbc.com
> > >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:08 GMT-3