3Com CoreBuilder 3500, Руководство по внедрению, Страница: 102 / 592

102 C
HAPTER
6: F
IBER
D
ISTRIBUTED
D
ATA
I
NTERFACE
(FDDI)
■
Before the new FDDI stationMode takes effect, you must reboot your
system.
■
You cannot modify fddi-stationMode port-pairs when any of the ports
in the pair are members of a trunk.
■
In a DAS configuration, the Activity LED from the secondary port
(channel B) is not used by the port. If network traffic is passing
through Channel B, the Activity LED on Channel A indicates port
activity.
FDDI Stations
You can set the following FDDI station parameters:
■
Connection policies
■
Neighbor notification timer
■
Status reporting
Setting the
Connection Policies
The connectPolicy attribute is a bit string that represents the connection
policies that are in effect on a station. A connection’s
type is defined by
the types of the two ports involved (A, B, M, or S) in the connection. You
can set the corresponding bit for each of the connection types that you
want a particular station to reject.
The system’s FDDI ports can be of type A or type B. By default, all
connections to the systems FDDI ports are valid. Table 11 lists the possible
connections to reject and their corresponding bits.
Effects and Consequences
When you set the connection policies, consider the following:
■
By default all connections are valid on the system. An M-to-M
connection is accepted so that a system port can be connected to
another system port.
■
Although an M-to-M connection is illegal within the FDDI standard,
the CoreBuilder 3500 system allows this connection.