North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: [eng/rtg] changing loopbacks

  • From: David Barak
  • Date: Sun Oct 02 15:56:50 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0LDGvjWL3T4lju/qt2hUfit6EsmfBQMKJgNFejSxDInz+a83YL9obTxMaylXgy4Pyxj8U3ywp48x1fnPZW/H8shwCHbNGTzTFVaeaf6AEvvG8DmwNP4qGi2LDUUUJ68ZZ1n2aiF1IxWoFTcMw5EHg4oBL2EAyqOdWRC0Hk2GriA= ;

--- Austin <[email protected]> wrote:

> 
> It's worth noting that C's don't need actual IP
> address space assigned to 
> the router-id for OSPF. It's just an arbitrary
> value; it's probably better 
> karma to set it to whatever you want (maybe
> something that doesn't look 
> like an IP address).
> 
> RFC 2328:
> 
>         Router ID
>             A 32-bit number assigned to each router
> running the OSPF
>             protocol.  This number uniquely
> identifies the router within
>             an Autonomous System.


eek!  There are a couple of downsides to having the
router-ID divorced from a physical address:

1) you get an additional number which you have to have
to track to ensure uniqueness.

2) you lose the benefit of being able to double check
reachability (ping/ssh to router ID)

3) RFC 1403 says that the BGP router identifier must
be the same as the OSPF router ID, and do you really
want your BGP to reflect an unreachable ID?

I've had a customer who used unreachable router IDs,
and it made their NOC work quite a bit harder than
they otherwise would have had to...

-David


		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com