From: Richard Foltz (ccie2b@xxxxxxxxxx)
Date: Mon Dec 03 2001 - 12:56:24 GMT-3
Thats close, except the router-id command doesnt have to reference any
addresses of interfaces on the routers. you can use it to say, assign a
router is of 1.1.1.1 ro touter 1, and 2.2.2.2 to router 2. good for
debugging, and setting up virtual links.
Richard Foltz, CCIE#8339, CCNP-Voice, CCDP, MCSE+I, Network+, A+
----- Original Message -----
From: <SFeldberg@edeltacom.com>
To: "Rajeev Siddappa" <raj_lab@yahoo.com>
Cc: <ccielab@groupstudy.com>
Sent: Monday, December 03, 2001 8:57 AM
Subject: Re: Router-ID
> My understanding of the application of this command is to "lock down" a
> known ID for an OSPF process. It will add stability through reliably by
> assigning the same ID to your OSPF router after a reload. You will still
> need to reference an IP address that is in use on a physical or logical
> interface- logical being more than physical. This configuration step
> becomes more critical with the use of multiple OSPF processes with
> virtual-links involved. This is the only way that you can insure that
each
> OSPF process is assigned the same ID every time.
>
> Steve
>
>
>
> Rajeev
> Siddappa To: Frank B
<frank@buff-net.com>, ccielab@groupstudy.com
> <raj_lab@yahoo cc:
> .com> Subject: Router-ID
> Sent by:
> nobody@groupst
> udy.com
>
>
> 12/01/2001
> 11:37 PM
> Please respond
> to Rajeev
> Siddappa
>
>
>
>
>
>
> If I use the command,
>
> Router-ID under OSPF what will be the stability f the
> OSPF process. Will it be similr to an loop back
> interface ip address or Physical.
>
> Thank you,
> Rajeev.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:36 GMT-3