From: Wade Edwards (wade.edwards@xxxxxxxxxxxxxxxxxxx)
Date: Thu Feb 21 2002 - 12:43:12 GMT-3
This brings up something interesting I remember about the way IS-IS does
passive interfaces. In other routing protocols you add the interface to
the routing process then make it passive. With IS-IS you make it
passive which will add it to the IS-IS routing process without doing the
ip router isis command. So it seems backward from all the other routing
protocols. I wonder why Cisco did it this way. I could never find out
why it is this way on CCO. Does anyone out there know why?
L8r.
-----Original Message-----
From: John Neiberger [mailto:neiby@ureach.com]
Sent: Thursday, February 21, 2002 9:19 AM
To: alee@cccis.com; ccielab@groupstudy.com
Subject: Re: advertise loopback interface in ISIS
Take a look at the following link:
http://www.cisco.com/warp/public/97/is-is-ip-config.html
Toward the bottom of the page it mentions the following:
"The above output shows that the loopback address of this
router is advertised with a value of 0. This is because the
loopback is advertised with a passive-interface command under
the router IS-IS process, and the loopback interface by itself
is not enabled for IS-IS. All other IP prefixes have a value of
10, which is the default cost on the interfaces running IS-IS. "
This seems to be saying that if you create a loopback interface
but don't add ip router isis to it, and then you add a passive-
interface command this will cause the loopback address to be
advertised with a metric of zero.
I'm not sure what that means and I don't have a way to test it
here at work. However, that may be what you're looking for.
HTH,
John
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:29 GMT-3