I've been looking at the RIF reported by using the "show dlsw circuits
detail" command. The RIF I get back is reported as:

06B0.3E83.0DD0

I've broken this down to the components :

06B0 (Routing Control Field).3E83.0DD0(Route Designator Fields)

The RD fields are as they should be with the bridge and ring numbers
matching what I have on the network. The question I have is with the RC
Field. It appears to me as if the length portion of the RC Field is left
out. The RC Field is made up of:

Routing Control Field (RCF)

            Byte 0:                 Byte 1:
bit   0 1 2 3 4 5 6 7         0 1 2 3 4 5 6 7
      B B B L L L L L      D F F F R R R R

B = Broadcast Indicators
L = Length Bits (length of RIF)
D = Direction Bit
F = Largest Frame Bits
R = Reserved Bits (always 0)

If I convert 06B0 to binary I get:

11010110000

Now if I break this up into it's consituent parts I get:

110     Single route broadcast (as dlsw should be)
?????  Length
1         Direction read right to left
011     Largest frame =  4472 bytes
0000   Reserved

I've left out the length because this is the only way I can get the numbers
to work. If I start putting in the length I don't get a valid length number
(2-18).

 My question is: Is this the way the RIF is always reported in the DLSW
connection with the length field left out?

I'm guessing if this is so it's because the RIF being terminated at the
local router means the remote router doesn't need to know what the length of
the RIF is. If anyone knows the reason for this, or if I'm correct in my
guess I'd appreciate the reply. My eyes were rolling back in their sockets
as I was trying to learn RIF reading (sounds funny) as it is.



--
James Haynes
Network Architect
Cendant IT
A+,MCSE,CCNA,CCDA,CCNP,CCDP




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=95&t=95
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to