From: DAN DORTON (DHSTS68@xxxxxxxxxxxxxxx)
Date: Mon Apr 01 2002 - 10:57:45 GMT-3
Is the sap originating from a network on a port that you wish to pass
the static sap across?
If so I would suggest using a loopback to originate the sap.
A static sap will not be passed over an interface that has the network
number that the static sap supposedly originated on.
Hell, Why would it? The sap is supposed to be local to that network
right? ;)
Dan
>>> "BEDA jain" <bedup@hotmail.com> 03/29/02 12:41PM >>>
r1-------110------------r2----220------------r3-------400
router r1 and r2 running ipx rip and r2 and r3 running nlsp. router r3
has loopback int .
i put a staitic route in r1 .
ipx sap 7 print 400.0001.0001.0001 451 2
i can see all the route in r1 ,r2 and r3 for ipx network.
i can see the server in r1, but i did not see any sap server in router
r2
and r3.
do i need to do some thing else to pass static sap to router r2 and r3
?
i can ping to network 400, but node i put for static route is not
known
to r1.
Thanks,
Beda
BEDA PRAKASH JAIN Apartment address 1116 woodway bluff circle cary,nc
27513 9196789188 res 9193922891 work 9195220242 cell >From:
steven.j.nelson@bt.com >Reply-To: steven.j.nelson@bt.com >To:
ccielab@groupstudy.com >Subject: Route Reflector and Peer Group >Date:
Fri, 29 Mar 2002 17:50:43 -0000 > >All, > >I have the following >
>R1(AS254)-------R10(AS1)-------R3(AS1)--Frame_Cloud--R6(AS1)--R7(AS1)
>
>Basically R1 is ebgp to r10, then ibgp to r3, R6 and R7 are reflector
>clients of r3 in peer group "peers", next hop self is set for the
peer
group >at R3 (As is remote AS, RR Client etc etc) > >The problem is
that
the next hop isn't being changed at R3 for the peers in >the group
even
though I have the commands :- > >neighbor peers peer-group >neighbor
peers remote-as 1 >neighbor peers route-reflector-client >neighbor
peers
next-hop-self >neighbor peers update source loopback 0 >neighbor
x.x.x.x
peer-group peers .... and so on for all routers in the peer >group >
>All
IGP functionality is fine and loopbacks are being advertised to every
>router in the workgroup, so reachability isn't an issue. > >Any
thoughts. > >Thanks > >Steve > > >Steve Nelson >Customer Engineer >BT
Ignite- National Solutions >T: +44 (0)1422 338881 M: +44 (0)7811
944172
>e-mail: steven.j.nelson@bt.com >pp HW A170, PO Box 200(HOM-NZ),
London,
N18 1ZF > > British Telecommunications plc > > Registered office: 81
Newgate Street London EC1A 7AJ > > Registered in England no. 1800000. >
>
This electronic message contains information from British
>Telecommunications plc which may be privileged or confidential. The
>information is intended to be for the use of the individual(s) or
entity
>named above. If you are not the intended recipient be aware that any
>disclosure, copying, distribution or use of the contents of this
information >is prohibited. If you have received this electronic
message
in error, please >notify us by telephone or email (to the numbers or
address above) >immediately.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:51 GMT-3