
13
CrossFire 8650/8651 UEM Guide to Operation, DOC-7090 v. 1.0
3. Console Configuration
Frames from different VLANs are distinguished by means of standard IEEE
802.1Q frame tags. A frame tag consists of an 8-byte SNAP protocol header
followed by a 2-byte Tag Control Information (TCI) field. It is inserted in the
Token-Ring frame after the route information field before transmission on HSTR
and subsequently recognized and removed when the frame is received.
The TCI field identifies which VLAN the frame belongs to by means of a 12-bit
VLAN identifier. This VLAN identifier uniquely identifies the BRF. It also
contains a 3-bit priority field, which is described in section "Virtual Port
Configuration" under subsection "FC Modification".
Each HSTR port can be assigned to several CRFs, but there can only be one HSTR
port per BRF/VLAN. A virtual port is created for each CRF to which the HSTR port
is assigned. All virtual ports but one must be tagged. In other words, a single virtual
port can be left untagged.
Also, see section “Virtual Port Configuration” on page 18.
Note that an HSTR port with a single untagged virtual port is functionally
equivalent to an ordinary Token-Ring port. This is also the default configuration,
with the virtual port in trcrf-default.
Virtual Port Restriction
➽
Note:
An HSTR port can have only one virtual port in each VLAN.
This follows from the nature of VLAN tagging. It would not be possible to
distinguish frames from two virtual ports in the same VLAN, since they would have
the same VLAN identifier.
Ring Number Restriction
➽
Note:
All CRFs in which an HSTR port has virtual ports must have the same ring
number.
Thus, the ring number is a per-port parameter and not a per-virtual port parameter.
This convention will also be implemented by Madge HSTR switches and is
expected to be adopted by the IEEE. To see the importance of this, consider the
implication of
not
having this restriction. If it was not in effect, the meaning of the
RIF would be ambiguous and depend on to which VLAN the frame was sent. It
would thus be incomprehensible to equipment that does not understand VLAN
tags.
When a virtual port is created in a VLAN this restriction might in some cases
require that a new CRF be created to avoid changing existing ring numbers.
865x.Book Page 13 Wednesday, October 6, 1999 2:31 PM