Brocade Communications Systems 8 Reference page 306

Fabric os message reference
Hide thumbs Also See for 8:
Table of Contents

Advertisement

34
FCR-1063
Probable Cause
Indicates that the maximum number of supported EX_ports or VEX_ports was exceeded. To enable
the specified port, disable any other operational port then re-enable the port.
Recommended
No action is required.
Action
Severity
INFO
FCR-1063
Message
<timestamp>, [FCR-1063], <sequence-number>,, INFO, <system-name>, Fabric <fabric
ID> for switch with domain ID: <domain ID> mismatch with local fabric ID <local
fabric ID>.
Probable Cause
Indicates that the fabric ID of the switch does not match the local switch.
Recommended
Run the switchShow command to display the fabric ID. Change the fabric ID to match on both ends
Action
by modifying either the local or remote host using the fcrConfigure command.
Severity
INFO
FCR-1064
Message
<timestamp>, [FCR-1064], <sequence-number>,, ERROR, <system-name>, Fabric ID of
backbone FC-Routers mismatch or overlap.
Probable Cause
Indicates that either (1) a backbone fabric split and both are connected to common edge fabrics, or
(2) the fabric IDs of two backbone fabrics connected to an edge fabric are the same.
Recommended
If the backbone fabric split, merge the fabrics.
Action
If two (or more) backbone fabrics have the same IDs, make the fabric IDs unique using fcrConfigure
command.
Severity
ERROR
FCR-1065
Message
<timestamp>, [FCR-1065], <sequence-number>,, ERROR, <system-name>, Fabric on port
<port number>
Probable Cause
Indicates that another port on the switch is connected to the same edge fabric with a different
fabric ID assignment.
Recommended
Change the port fabric ID to same value as the other ports connected to the edge fabric using the
Action
portCfgExport or portCfgVexport commands.
Severity
ERROR
230
was assigned two different fabric IDs.
Fabric OS Message Reference
53-1001767-01

Advertisement

Table of Contents
loading

Table of Contents