Re: NLSP route aggregation

From: dhbrown@xxxxxxxxxxxx
Date: Tue Aug 22 2000 - 10:52:11 GMT-3


   
John,

NLSP uses hex, 0x18 = 24 bits.

David

John Conzone <jkconzone@home.com> wrote:
>

    Need some help with NLSP area and route
aggregation. Excerpt from doc CD.

Area Addresses<A TARGET="Link" name=1002087>

<P>An area address uniquely identifies an NLSP area. The area addresses
configured on each router determine the areas to which a router belongs.

<P>An area address consists of a pair of 32-bit hexadecimal numbers that
include an area number and a corresponding mask. The mask indicates how much of

the area number identifies the area, and how much identifies individual network
s
in the area. For example, the area address pair 12345600FFFFFF00 describes an
area composed of 256 networks in the range 12345600 to 123456FF.
<P>I'm okay with this I think. We're masking the first 24 bits, and don't care
on the last 8. 8 bits for networks and possible 256 networks. The next paragrap
h
describes route summarie, which make sense. They follow the area address format
.
Now the next part is where I lose it. Here it is.
Aggregated Routes</A><A TARGET="Link" name=1002096>
<P>An aggregated route is the single, compact data structure that describes
many IPX network numbers simultaneously. The aggregated route represents all th
e
explicit routes defined by the route summary. In an LSP, the router expresses a
n
aggregated route as a 1-byte number that gives the length, in bits, of the
portion of the 32-bit network number common to all summarized addresses. The
aggregated route for 12345600FFFFFF00 is 18 12345600.
<P> The must match bits equal 24, not 18. Hence i would expect 24 12345600,
not 18 12345600. What am I missing?
<P>Thanks!</A><A TARGET="Link" name=1002087></A>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:28 GMT-3