Brocade Fabric OS Message Reference - Supporting Fabric OS v5.3.0 (53-1000437-01, June 2007)

380 Fabric OS Message Reference
53-1000437-01
SEC-1193
63
SEC-1193
Message <timestamp>, [SEC-1193], <sequence-number>,, INFO, <system-name>, Security
violation: Login failure attempt via <connection method>. IP Addr: <IP address>
Probable Cause Indicates that a specified login security violation was reported. The incorrect password was used
while trying to log in through the specified connection method; the login failed.
Recommended
Action
The error message lists the violating IP address. Verify that this IP address is being used by a valid
switch admin. Use the correct password.
Severity INFO
SEC-1194
Message <timestamp>, [SEC-1194], <sequence-number>,, WARNING, <system-name>, This switch
does not have all the required PKI objects correctly installed.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can
only occur when the primary fabric configurations server (FCS) is distributing the security database
to the other switches in the fabric and local validation finds that there is an 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 might not be correctly updated
for that specific switch.
Severity WARNING
SEC-1195
Message <timestamp>, [SEC-1195], <sequence-number>,, WARNING, <system-name>, This switch
has no
<component> license.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can
only occur when the primary fabric configurations server (FCS) is distributing the security database
to the other switches in the fabric and local validation finds that there is an 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 might not be correctly updated
for that specific switch.
Severity WARNING