For Brocade SAN switch, portshow shows the port stats and counters for ports, not like the command porterrshow, which shows the statistics of ports in summary, portshow shows a single port status.
Here is a quick reference for admins to easy identify them, therefore easy to debug the problem/performance issue out.
For more trouble shotting commands, see Brocade SAN switch trouble shooting commands.
FID128:admin> portshow 36
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
POD Port: Port is licensed
portState: 1 Online
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 48
state transition count: 5
portWwn of device(s) connected: 21:01:00:1b:32:b3:e7:6e
Credit Recovery: Inactive
LE domain: 0
FC Fastwrite: OFF
Interrupts: 0 Link_failure: 0 Frjt: 0
Unknown: 0 Loss_of_sync: 0 Fbsy: 0
Lli: 20 Loss_of_sig: 2
Proc_rqrd: 3738 Protocol_err: 0
Timed_out: 0 Invalid_word: 0
Rx_flushed: 0 Invalid_crc: 0
Tx_unavail: 0 Delim_err: 0
Free_buffer: 0 Address_err: 0
Overrun: 0 Lr_in: 3
Suspended: 0 Lr_out: 2
Parity_err: 0 Ols_in: 0
2_parity_err: 0 Ols_out: 3
Here are some most useful error counters for debugging.
Total number of interrupts.
Interrupts that are not counted elsewhere.
Low-level interface (physical state, primitive sequences).
Frames delivered for embedded N_Port processing. As known as "Frames delivered for embedded N_Port processing"
It indicated the # of frames received by the port that can't be proccessed by the hardware for one or more reasons. Most typically it is due to an invalid SID or DID, invalud VC, invalid class of service, etc. In most cases, the highest counter appears on ISLs.
Frames that have timed out.
Frames requiring translation.
Frames returned from an unavailable transmitter.
Free buffer available interrupts.
Buffer overrun interrupts.
Transmission suspended interrupts.
Central memory parity errors.
Secondary transmission parity errors.
Control message interface errors.
Inbound Link reset
Outbound Link reset
Inbound Offline Sequence
Outbound Offline Sequence
The last four parameters(Lr_in,Ols_out, Lr_out, Ols_in) tell us if the destination or the source SFP is causing the error. If Lr_in and Ols_out is equal then its a normal condition, same applies for Lr_out and Ols_in.
if one counter is higher that its counterpart then the frame was already corrupted when it was received or corrupted by the switch.
"in" > "out" - frames were bad when received
"out" > "in" - corruption caused by switch
So in our case Lr_out greater than Ols_in hence the corruption is caused by faulty GBIC in switch port.