> -----Original Message----- > From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp- > bounces at puck.nether.net] On Behalf Of Joe Provo > Sent: Thursday, April 17, 2008 10:03 PM > To: foundry-nsp at puck.nether.net > Subject: Re: [f-nsp] ISIS loopback interface configuration > > On Wed, Apr 16, 2008 at 04:32:37PM +0200, Christian Bering wrote: > [snip] > > On a Foundry I don't have that option. I seem to be able to choose > > between: > > > > A) > > interface loopback 1 > > ip router isis > > ip address x.y.z.v/32 > > > > B) > > interface loopback 1 > > ip address x.y.z.v/32 > > ! > > router isis > > address-family ipv4 unicast > > redistribute connected > > ! > > > > What is the right (best, preferred, best practice) way of doing it? > > 'redist conencted' using a route-map to manage what parts of > 'connected' > get redisted.
We've had no problems doing this in our network: interface loopback 1 ip router isis ip address x.x.x.x/32 no ip redirect isis metric 1 ! In my opinion, it is cleaner than trying to redistribute connected into the IGP. All interfaces that have ISIS enabled on them have their networks injected into the topology anyway. No redistribute is necessary.
