[c-nsp] OSPF NSSA Question
lee.e.rian at census.gov
lee.e.rian at census.gov
Mon Oct 4 16:19:44 EDT 2004
I just tried it in the lab & it works if the interface is not passive - eg.
router eigrp 100
passive-interface default
no passive-interface vlan903
neighbor x.x.x.150 vlan903
Can anybody at Cisco comment on what happened with bug CSCdv19648? About a
year ago I got one of those "The following defect(s) in your Bug Watcher
profile were either added..." emails and now the bug is not publicly
visible
BugID: CSCdv19648
Title: Change the behavior of the eigrp neighbor command
--
Lee
|---------+--------------------------------->
| | Dan Armstrong |
| | <dan at beanfield.com> |
| | Sent by: |
| | cisco-nsp-bounces at puck|
| | .nether.net |
| | |
| | |
| | 10/04/2004 02:05 PM |
| | Please respond to dan |
| | |
|---------+--------------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: Gert Doering <gert at greenie.muc.de> |
| cc: cisco-nsp at puck.nether.net |
| Subject: Re: [c-nsp] OSPF NSSA Question |
>---------------------------------------------------------------------------------------------------------------------------------------------|
I too thought I could set the interfaces passive, and do that:
router eigrp 100
redistribute connected route-map public_subnets
redistribute static route-map public_subnets
passive-interface default
network x.x.x.146 0.0.0.0
neighbor x.x.x.150 Vlan903
auto-summary
eigrp stub connected static summary
no eigrp log-neighbor-changes
I do the reverse on the other router.
They don't ever seem to form a relationship:
TCF-1.902.1ie2#sh ip eigrp nei
IP-EIGRP neighbors for process 100
TCF-1.902.1ie2#
On Monday 04 October 2004 13:46, Gert Doering wrote:
> Hi,
>
> On Mon, Oct 04, 2004 at 09:52:37AM -0400, Dan Armstrong wrote:
> > I could bump up the costs, but it would be nice if there was a clean
way
> > to tell EIGRP to "F-Off don't neighbour with this guy"...
>
> IIRC the trick is to make the interface passive, and explicitely list
> the neighbour you *want* with "router eigrp 4321 / neighbour 1.2.3.4".
>
> (Another, if quite ugly, hack would be to control-plane ACL the EIGRP
> hello packets from the neighbouring 6509 to death...)
>
> gert
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list