Console messages that pop up during cli login

Console messages that pop up during CLI login sessions are not displayed in
errshow / Dump (log error message) outputs unless they contain a severity level.
Console messages are messages that go to the serial port. In Linux, messages
directed to “standard error” are mirrored on the console. Console messages that
contain severity levels will be displayed in the error log. Examples of console
messages that do not include severity codes include CP sync messages. These CP
sync messages let the console know about events that occur in the CP fail over
process. Console messages can be configured to go to syslog servers.
• Management host needs:
– An available serial port
– A terminal emulation program
configured with the correct serial port
parameters
• Check the hardware reference manual
for required cable
The serial port’s parameters are fixed at 9600
baud, 8 data bits, and no parity, with flow control
set to None.
Brocade switch
Serial Console Server
Serial cable
The first point of contact with
Brocade switches is often the serial
console
What can go wrong?
• Consider connecting a terminal
server with network and modem
capability for serial console
access to switch
• Capture serial console output
during problem determination
processes, especially when a
switch reboot is required
Data Gathering
3 – 75
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 76
SAN-TS 300
Revision 0317 Beta

Events can also be filtered by using the Reports  Event Custom Reports utility.
The following columns will be displayed by default in Master Log:
• Severity
• Acknowledged
• Last Event Server Time
• Description
• Source Name
• Source Address
• Category
• Count
• Message ID
• Fabric Name
• Port Name
Data Gathering
3 – 77
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 78
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 79
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 80
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 81
SAN-TS 300
Revision 0317 Beta

Data Gathering
3 – 82
SAN-TS 300
Revision 0317 Beta

Device Connectivity
Revision 0317 Beta 4 – 1
SAN-TS 300

Device Connectivity
Revision 0317 Beta 4 – 2
SAN-TS 300

Device Connectivity
Revision 0317 Beta 4 – 3
SAN-TS 300

Footnote 1: Is there light from the host or device?
• A powered off or failed device might not provide light
• Without light there will never be a login
Footnote 2: Does the switch port speed configuration match the attached device speed
configuration?
• Devices and switch ports typically auto-negotiate
• Verify that the switch port is not locked to a speed the device cannot handle. Example if
the switch is hard set for 16 Gbps and the HBA is an 8 Gbps the device can not log into
the fabric.
Footnote 3: Devices login to a fabric using Fabric Login (FLOGI), has this occurred ?
• The end device will FLOGI to be assigned a 24-bit address. Until then, it has no fabric
port ID (PID) with which to initiate communication in the fabric.