From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Tue Oct 23 2001 - 21:01:31 GMT-3
Referencing a static sap to an ipx network on interface (fa0/0) will
keep the sap from being advertised out that interface, due to
split-horizon, but have any of you seen where using the ipx network on a
loopback as the reference point also seems prevent it from being
advertise out a certain interface, it still won't advertise the sap out
the intended interface (fa0/0)? What I did as a test was put "no
keep" on another fast e port, put an ipx address on it, advertised it,
and used that ipx network as a reference instead and the sap was then
advertised out fa0/0. Alternatively, I also did it by using an ipx
internal network number as the reference and that worked.
I had run some debugs when the reference was to the ipx network on lo0
and it said it was forwarding the saps out fa0/0 but the next-hop router
didn't receive them. It looks like a bug; I'm running 11.2(24) on that
particular router but it worked fine on 12.2(3) on other routers. Just
wondering if someone else had run into this before and if perhaps there
was a legitimate reason for it not working as I had expected.
basic config, which didn't work on 11.2(24), sap not advertised out
fa0/0
int lo0
ipx network 5
int fa0/0
ipx network 1
ipx router eigrp 1
network 5
network 1
ipx router rip (on by default)
ipx sap 4 server1 5.a.a.a 451 1
********
but this did work:
ipx internal-network 5
int fa0/0
ipx network 1
ipx router eigrp 1
network 5
network 1
ipx router rip (on by default)
ipx sap 4 server1 5.a.a.a 451 1
Looks like a bug but thought I'd get another set of eyes to look at to
make sure I'm not missing something obvious.
-Brian
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:24 GMT-3