Brocade Fabric OS Message Reference (Supporting Fabric OS v7.3.0) - Manual (Page 777)

Fabric OS Message Reference 755
53-1003140-01
SEC-1028
5
SEC-1028
Message
No name is specified.
Message Type
LOG
Severity
ERROR
Probable Cause
Indicates a corruption occurred during the distribution of the security database. This can occur only when
the primary fabric configuration server (FCS) distributes the security database to the other switches in
the fabric, and then local validation finds the error in the security database. This is a rare occurrence.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in
the ready state. If a switch is in the error state, the database may not be correctly updated for that
specific switch.
SEC-1029
Message
Invalid character in .
Message Type
LOG
Severity
ERROR
Probable Cause
Indicates a corruption occurred during the distribution of the security database. This can occur only when
the primary fabric configuration server (FCS) distributes the security database to the other switches in
the fabric, and then local validation finds the error in the security database. This is a rare occurrence.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in
the ready state. If a switch is in the error state, the database may not be correctly updated for that
specific switch.
SEC-1030
Message
The length of the name is invalid.
Message Type
LOG
Severity
ERROR
Probable Cause
Indicates a corruption occurred during the distribution of the security database. This can occur only when
the primary fabric configuration server (FCS) distributes the security database to the other switches in
the fabric, and then local validation finds the error in the security database. This is a rare occurrence.
Recommended
Action
Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in
the ready state. If a switch is in the error state, the database may not be correctly updated for that
specific switch.