Nope...you're right on the money...and with a pretty good explanation too!
Craig
At 02:34 PM 3/3/2001 -0500, you wrote:
>1) For each byte: abcdefgh
>
>2) Stick an axis right down the middle: abcd efgh (essentially separating
>the byte into two nibbles)
>
>3) Spin the byte around the axis: hgfe dcba
>
>4) Do this for each byte in the octet separately. The order of the bytes
>doesn't change: 1.2.3.4 -> 1.2.3.4
>
>So, your example:
>0000 0000. 0000 1100.0110 0101.0100 0011.0010 0001 (which has five bytes,
>for some reason, so I'll ignore the last one)
>
>would translate into:
>0000 0000. 0011 0000. 1010 0110. 1100 0010
>
>That's about it - I think. If I'm wrong, someone please let me know - I've
>just started studying for the CCIE written, and this is all from memory of
>Rossi's paper (about a week ago :-).
>
>BJ
>
>
>
>----- Original Message -----
>From: Michael Snyder
>Newsgroups: groupstudy.cisco
>To: [EMAIL PROTECTED]
>Sent: Saturday, March 03, 2001 1:45 PM
>Subject: Ethernet MAC <--> Token Ring MAC
>
>
>What is the bit by bit method of going from a Ethernet Mac address to a
>Tokenring Mac address?
>
>I've read the paper's, I still can't do it, and I've been doing HEX for
>years.
>
>
>For example
>
>00.00.0c.65.43.21 Ethernet MAC would be?
>
>0000 0000. 0000 1100.0110 0101.0100 0011.0010 0001
>
>Next step is?
>
>a) reverse complete bit sequence? 1000 0100.1100 0010.1010 0110. 0011 0000.
>0000.0000
>b) reverse sequence in groups of four? 0001 0010.0011 0100.0101 0110.1100
>0000 0000
>c) Transpose bits in groups of four, per byte? a.b ->b.a (seen this one a
>lot in programing)
>
>help?
>
>
>
>
>
>""perryb"" <[EMAIL PROTECTED]> wrote in message
>007901c0a011$52ec4d00$1e00a8c0@GOLDIE1">news:007901c0a011$52ec4d00$1e00a8c0@GOLDIE1...
> > Hi all,
> >
> > I'm goinf to diverge from the star/bus issue in Mr. Rossi's paper, and
> > direct everyones attention to what I believe could be a mistake (clerical
> > error) in the paper on the DLSW piece.
> >
> > Directly underneath Mr. Rossi's very first DLSW diagram, you see the RIF
> > values for "Router_A," and "Router_B." Isn't the RIF show for "Router_B"
> > just a tad bit inverted and incorrect ? Shouldn't it read
>"0630.00a1.0230"
> > instead? The reason that I say this is because I had a "not so different"
> > question on a recent exam. On this exam there were no "none of the above"
> > responses and only two possible valid RIFs. The only plausable response
>was
> > in the order that I describe above.
> >
> >
> > Forgive me if this has already been pointed out before.
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, February 26, 2001 6:45 AM
> > Subject: RE: Lou Rossi's Token Ring paper
> >
> >
> > > I agree with Nigel. It should be a physical star and a logical ring.
> > >
> > > Cletus Ugwu
> > >
> > > -----Original Message-----
> > > From: Nigel van Tura [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, February 26, 2001 7:29 AM
> > > To: Bradley J. Wilson; [EMAIL PROTECTED]
> > > Subject: RE: Lou Rossi's Token Ring paper
> > >
> > >
> > > But Bradley
> > >
> > > If we connect all to the MAU as a central hub then it becomes a physical
> > > star and a logical ring inside the MAU.
> > >
> > > Or what ?
> > > Nigel van Tura
> > >
> > > -----Original Message-----
> > > From: Bradley J. Wilson [mailto:[EMAIL PROTECTED]]
> > > Sent: 24 February 2001 01:50
> > > To: cisco
> > > Subject: Lou Rossi's Token Ring paper
> > >
> > >
> > > I'm sitting here reading Lou Rossi's Token Ring paper, and right off the
> > bat
> > > I have a question:
> > >
> > > He says that token ring is "a physical ring and a logical bus" - but
>isn't
> > > this backward? Isn't it a physical bus and a logical ring? We're not
> > > physically connecting stations together in a ring - they're all plugged
> > into
> > > a MAU and the "ring" is a logical entity inside the MAU, isn't it?
> > >
> > > Thanks in advance,
> > >
> > > BJ
> > >
> > >
> > >
> > > _________________________________
> > > FAQ, list archives, and subscription info:
> > > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > >
> > > _________________________________
> > > FAQ, list archives, and subscription info:
> > > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > >
> > > _________________________________
> > > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>
>
>_________________________________
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>_________________________________
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
