Re: NLSP route aggregation

From: Kent (cciecn@xxxxxxxxx)
Date: Mon Aug 21 2000 - 19:19:28 GMT-3


   
IPX uses hexdecimal, so 18 is hex.

Kent
--- John Conzone <jkconzone@home.com> wrote:
> Need some help with NLSP area and route
> aggregation. Excerpt from doc CD.
>
> Area Addresses
> An area address uniquely identifies an NLSP area.
> The area addresses configured on each router
> determine the areas to which a router belongs.
>
> 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 networks in the area. For
> example, the area address pair 12345600FFFFFF00
> describes an area composed of 256 networks in the
> range 12345600 to 123456FF.
>
> 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
> paragraph 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
> An aggregated route is the single, compact data
> structure that describes many IPX network numbers
> simultaneously. The aggregated route represents all
> the explicit routes defined by the route summary. In
> an LSP, the router expresses an 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.
>
> The must match bits equal 24, not 18. Hence i would
> expect 24 12345600, not 18 12345600. What am I
> missing?
>
> Thanks!
>
>



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