From: John Neiberger (neiby@xxxxxxxxxx)
Date: Fri Mar 29 2002 - 01:39:45 GMT-3
While wrestling with this I discovered that this is correct.
However, it appears that the NLSP 'distribute-sap-list' in only
works on a router that is running RIP/EIGRP and NLSP. The 'in'
keyword tells the router to filter the SAP when redistributing
from IPX RIP into NLSP.
On one of the receiving routers that is running NLSP I tried a
distribute-sap-list in and I had no luck filtering the incoming
SAP. I would expect not to be able to filter routes since NLSP
is link-state, but I didn't think it applied to SAPs and I also
don't see why I can't filter incoming on an NLSP-only router.
Perhaps I was doing it incorrectly.
Regardless, on the router running RIP and NLSP, a distribute-
sap-list in did the trick. The key to remember here is the the
NLSP distribute-list and distribute-sap-list syntax is reversed
from the IP version of the command.
Regards,
John
---- On Thu, 28 Mar 2002, Ling Ling Liang
(potatomato@rogers.com) wrote:
> Hi, there,
>
> Since NLSP is a link state protocol, you should
use 'distribute-list
> in'
> .
>
> Regards!
>
> LL
>
> ----- Original Message -----
> From: "John Neiberger" <neiby@ureach.com>
> To: <ccielab@groupstudy.com>
> Sent: Thursday, March 28, 2002 10:54 PM
> Subject: Filtering SAPs in NLSP
>
>
> > I keep running into this problem and I don't know how to fix
> > it. When using IPX RIP, I can filter saps using an output-
sap-
> > filter. If you're not using RIP and you're using NLSP you
must
> > use another method.
> >
> > I tried adding a distribute list to the NLSP process and
this
> > did not work:
> >
> > access-list 1000 deny FFFFFFFF 7
> > access-list 1000 permit FFFFFFFF
> > !
> > ipx router nlsp
> > distribute-sap-list 1000 out Ethernet0
> > area-address 0 0
> > !
> > ipx sap 4 MyServer 100.0001.0001.0002 451 1
> > ipx sap 7 MyPrinter 100.0001.0001.0003 451 1
> > !
> >
> > That ought to filter my printer sap in updates going out
> > Ethernet0, but it doesn't. The two NLSP neighbors on that
> > segment both continue to receive updates with that sap.
> >
> > Any ideas?
> >
> > Thanks,
> > John
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:25 GMT-3