MDS CLI command to show port errors?

I would start out with “show int” ..i’ll keep looking.

This is a good one too

show interface detail-counters

ya i am looking in the 1700 page NX-OS CLI manual right now.

that is some dry reading......

Ya that one has a lot of info.   to bad i dont know what it all means:)

I need to find out what it will dispaly if say i have a bad cable or SFP. 

On Brocade when you run that porterrshow command,  normally we see that enc_out erros point to a bad cable while a combination of enc_out & crc_err point to a bad GBIC/SFP.

Problem is that at this moment i cant run these commands on the swtiches in question as i am at a different site...   So i am running them on known good switches just to see the output.

This is what i am finding so far when i get a show tech-support from the switches:

I can see that all the ports that have devices attached to them are showing high readings for:

output OLS, 7 LRR, 6 NOS, 0 loop inits under show int

The input line above this showes no change from 0 for all ports

SO i think i need to find out what OLS, LRR, and NOS means for both input and output

Interesting command

same reply on Cisco forums 

ya.  was seeing if the Cisco guys might shed some light:)

Pretty much what i found out is that you can do a "show int counters" and if you have readings under the OLS,LRR or NOS sections,  they point to a bad cable/SFP.

Hi Kenn,

You can have a look on all the  ports on MDS 9124 by the command :-

show interface brief

this will give you a table of the of the ports Vsan they belong to, modes, type of SFP and their speer etc. Once you have this list you may get the ports which you see as errorDisabled. Then to check that port you may give this command:-

show interface fc

this will give you the details of that port only.

frames input & frames output will be equivalent to Frames Tx & Rx in Brocade porterrshow and so on the errors are also listed.

There is no equivalent of Brocade's, 'porterrshow', in MDS switches, this is the how the same thing is represented in Cisco. If the errors are increasing then you may suspect the cable and have a reseat/replace of the cable done. If this does not resolve the issue you may suspect the SFP/GBIC. However if the port is connected to a number of other devices in the path from it to the other device (as in case of long distance links), the errors may be caused by any of the devices in path for example even a patch panel may introduce fault in the signal.

Hope this answers your query.