From: Chris Lewis \(chrlewis\) (chrlewis@cisco.com)
Date: Tue Jun 28 2005 - 11:08:33 GMT-3
San,
I don't quite understand what you are saying.
It is safe to assume that anything given to you in the formate
49.0255.x.x.x.00 is already in hex.
It is also safe to assume that if you are told in the question, an area
has to have a value, say 255, it must be converted in to hex before
being used in the NET value.
The only significance to the number of x's in my post was that each
value between the periods will have 4 characters.
The key issue is that the six bytes before the n-selctor are the system
ID, anything before that is the system ID, so in the example you give
the area ID will be 00.00ff.x assuming that in your case x represents
the two byte value that is inserted between periods in the NET value
format.
Chris
-----Original Message-----
From: san [mailto:san.study@gmail.com]
Sent: Monday, June 27, 2005 9:03 PM
To: Chris Lewis (chrlewis)
Cc: ccie2be; Lee Carter; CCIE LAB
Subject: Re: ISIS Networks
Chris,
net 49.0255.x.x.x.x.00 if its given in hex & equivalent area id in
decimal will be a huge number correct ?
For the above question (255 in decimal to net value )
ff.x.x.x.x.00 => is wrong value ? No assumptions of Zero at begining
is it ??
00.00ff.x.x.x.x.00 => is the correct value !!
/SAN
On 6/27/05, Chris Lewis (chrlewis) <chrlewis@cisco.com> wrote:
> One last point, consider the format of the NET.
>
> The NET can be 8-20 bytes, with the last byte set to zero. The 6 bytes
> directly in front of this last byte are the system ID. All bytes in
> front of the system ID are the area ID. So if you are given 255 in
> decimal as the area ID, look at it like this:
>
> 00.00FF.xxxx.xxxx.xxxx.00
> Area ID.System ID .N-selector and must be 0
>
> Chris
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of ccie2be
> Sent: Monday, June 27, 2005 5:12 PM
> To: 'Lee Carter'; 'CCIE LAB'
> Subject: RE: ISIS Networks
>
> Lee,
>
> As long as you remember that the NET is in HEX, you should be fine.
> In all likelihood, the task will be worded in such a way there won't
> be any ambiguity.
>
> However, if you're unsure, ALWAYS ask the proctor.
>
> Tim
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Lee Carter
> Sent: Monday, June 27, 2005 5:50 PM
> To: CCIE LAB
> Subject: ISIS Networks
>
> All,
>
> Ok, so when defining isis net's I have seen two different solutions
> where they say.. Put a particual isis network in say net 255 to keep
> it easy.
>
> One solution would use:
>
> net 49.0255.xxxx.xxxx.xxxx.00
>
> The other (which I believe is correct) would use:
>
> FF.0000.xxxx.xxxx.xxxx.00
>
> Since the firt two bits are in HEX.
>
> Thoughts?
>
>
>
> ____________________________________________________
> Yahoo! Sports
> Rekindle the Rivalries. Sign up for Fantasy Football
> http://football.fantasysports.yahoo.com
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:45 GMT-3