PORTSHOW - Tips and Tricks: Guys

PORTSHOW - tips and tricks
Dishvijay 14 posts since Sep 13, 2008
Guys,
I run portshow command and i see lots of parammeters with large figures. I see there is something wrong.
But how to to the error is from the HBA side or the Cable or the SFP/GBIC on the Switch ports or something else ?
Generated by Jive SBS on 2011-12-09-07:00 1
Any pdf to understand the PORTSHOW command better ?
And, how to reset these COUNTER, i have changed a new HBA and like to see if its showing the same large figures like before.
Thanks
Vij
Tags: portshow
bijukrishnan 256 posts since Apr 9, 2008 1. Re: PORTSHOW - tips and tricks Sep 20, 2008 2:34 AM
I have this little technote, dont quite remember the source. But this shd help you.
portstatsclear <port number>
can be used to clear stats and observe the counters again.
Identifying if SFP or the Cable is the Cause for Loss of Link

ISSUE: Loss of connectivity to a Host, Storage or another Switch can be caused by a faulty SFP or a cable. The Switch error Log would show an error similar to the following: 2007/12/06-23:50:56, http://community.brocade.com/message/5578#5578/FW-1424, 7682,, WARNING, SWITCH_1, Switch status changed from HEALTHY to MARGINAL 2007/12/06-23:50:56, http://community.brocade.com/message/5578#5578/FW-1436, 7683,, WARNING, SWITCH_1, Switch status change contributing factor Marginal ports: 1 marginal ports. (Port(s) x ) SOLUTION:
To determine whether the SFP or a cable is the cause of the loss of connectivity, perform the following: Check the output of "porterrshow " from the switch. "enc out " errors alone imply primarily cable problem. "enc out " and "crc err " combination imply primarily GBIC/SFP problem. To find out if source or destination SFP is causing the error, Check the Output of "portshow x" where x is the port number. If the pair of "Lr_in " and "Ols_out " as well the "Lr_out " and "Ols_in " values are "quite" equal, it is a normal case. If one counter is significantly higher than the other, the link problems either "reached" the switch ("in" > "out") or are caused by the switch ("out" > "in"). Note: If the "Ols_in ? value is higher than the "Lr_out ? one, then the "problem source ? is, in most cases, more related to the attached device (sending those offline sequences) and the switch responds to them with a "link reset". enc_out -> Encoding error outside of frames crc err -> Frames with CRC errors Lr_in -> Link reset In (primitive sequence), does not apply to FL_Port Lr_out -> Link reset Out (primitive sequence), does not apply to FL_Port Ols_in -> Offline reset in (primitive sequence), does not apply to FL_Port Ols_out -> offline reset out (primitive sequence), does not apply to FL_Port
Dishvijay 14 posts since Sep 13, 2008 2. Re: PORTSHOW - tips and tricks Sep 20, 2008 6:36 AM in response to: bijukrishnan
Portstats clear dint help i have tried that before posting the question here.
Biju,
The one you have sent for the loss of connctivity or SFP problem, i saw the same on one of the HP site, but is that how it works ... i have seen soome large figures on the parameters apart from the ones mentioned here so i wonder what all they represent to, or what should one forecast based on those errors.
Thanks
VIjay
bijukrishnan 256 posts since Apr 9, 2008 3. Re: PORTSHOW - tips and tricks Sep 20, 2008 9:41 AM in response to: Vijaya Prakash
The note works...! There is no doubt that its helpful. Since u have already run portstatsclear, run diagShow as well.
Just give me the o/p of porterrshow, diagshow and portshow of the affected port. If the port is a ISL then provide portshow of both ISL ports on either switches. Also helpful if you provide a problem desc in brief.
Also remember that CRC errors can travel across ISL's, we had faults in the DWDM circuits and the CRC errors floated on all the switches in that fabric.
I will try and isloate your failed FRU if you provide some stats, thats all I can say.
Check this out....incase it helps..!

Attachments: portErrShow.pdf (10.3 K)
Dishvijay 14 posts since Sep 13, 2008 5. Re: PORTSHOW - tips and tricks Sep 21, 2008 12:14 PM in response to: bijukrishnan
Biju,
I aint saying it dint work am looking for something more SOLID. Where i can get the whole picture.
I guess the portststclear command did clear the FIGURES on the PORTSHOW output, everything is ZERO, (including the port generation number ) < is this something ususal.
I have copied the outputs you asked. In short i want to understand the OUT PUT of portshow command, know or find out which is THROWING ERRORS, SFP or CABLE or HBA or something else.
Possible how to fix this as well.
porterrshow frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig
===================================================================== 0: 1.8g 4.0g 0 1: 883m 4.1g 0 2: 968m 3.1g 0 3: 2.7g 3.0g 0 4: 128m 767m 0 5: 6.7m 4.4m 0 6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 741k 7 0 10k 4 0 416k 21 0 120m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 370m 0 0 0 0 0 0 4 0 0 0
7: 193m 78m 0 8: 1.0g 774m 0 9: 3.8g 1.5g 0 10: 3.7g 2.3g 0 11: 871m 589m 0 12: 686m 664m 0 13: 931m 2.0g 0 14: 1.5g 1.6g 0 15: 3.5g 3.2g 0 16: 0 0 0
0 578k 1
0 277k 5.7k 0 0 45k 0 0 175k 0 0 18k 8 0 27k 0 0 100 0 27k 0 0 0 0 0 0 0 0 0
17: 18: 19: 20:
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0
0 0 0
0 0 0
0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 78k 0 0 0 0
21: 70m 2.7g 0 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 248m 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 33k 0 0 0 0 0 0 0 0 0 0
0 14k 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
32: 538m 637m 0 33: 956m 1.1g 0 34: 2.0g 1.0g 0 35: 3.5g 3.9g 0 36: 30k 131k 0 37: 3.2g 3.7g 0 38: 922m 3.8g 0
0 2.2k 0 0 34k 7 0 403 38 0 1.0m 0 0 19m 0 0 2.3k 1
0 572m 2
39: 276m 3.3g 0 40: 2.9g 114m 0 41: 28m 2.5g 0 42: 3.3g 2.6g 0 43: 120 60k 0 44: 771m 3.2g 0
0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 1.4m 18 0 19m 54 0 34k 0 0 27k 0 0 177 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 1 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0
0 20m 0 0 20 981 0 95 260 0 149 0
0 0
45: 1.1g 2.0g 0 786 46: 3.5g 4.0g 0 47: 325m 3.3g 0 48: 986m 1.2g 0 49: 2.6g 346m 0 50: 2.9g 2.0g 0 51: 278k 297k 0 52: 2.6g 2.0g 0 53: 3.1g 2.8g 0 54: 1.7g 1.0g 0 55: 1.3g 3.0g 0 56: 4.0g 2.2g 0 57: 3.4g 4.1g 0 58: 3.3g 1.2g 0 59: 129 67k 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0
0 1 0
0 0 0
0 0 0
0 2.4m 20 0 2.1m 486 0 635k 0 0 25k 0 0 167 0 0 0 0 0 0 0 0 0 0 0
0 1 0 0 0 0 1 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0
0 9.3m 0 0 20k 0 0 472k 1 0 5.7m 3 0 350k 0 0 45k 0 0 204 0
60: 2.2g 2.1g 0 102k 0
0 458k 32k 0
61: 1.6g 2.3g 0 102k 0 62: 3.5g 3.3g 0 63: 2.0g 3.8g 0 0 0 0 0 0 0
0 317k 31k 0 0 29m 13 0 206 0 0 0 0 0
0 0 0
0 0 0
0 0 0
portshow 7/5 portName: WIN_DDCTXUEXCLO1N2_hba2 portHealth: HEALTHY
Authentication: None portDisableReason: None portCFlags: 0x1 portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT portType: 4.1 portState: 1 portPhys: 6 Online In_Sync
portScn: 32 F_Port port generation number: portId: portIfId: 090500 4372001e 18
portWwn: 20:05:00:60:69:80:40:03 portWwn of device(s) connected: 21:00:00:e0:8b:9d:8f:39
Distance: normal portSpeed: N2Gbps
Interrupts: Unknown: Lli: Proc_rqrd: Timed_out: Rx_flushed: Tx_unavail: Free_buffer: Overrun: Suspended: Parity_err: 2_parity_err: CMI_bus_err:
302428 156 289845 12574 0 0 0 0 0 0 0 0 0
Link_failure: 7
Frjt:
0 Fbsy: 0
Loss_of_sync: 289323 Loss_of_sig: 4 Protocol_err: 0 Invalid_word: 0 Invalid_crc: 0 Delim_err: 0
Address_err: 0 Lr_in: Lr_out: Ols_in: Ols_out: 1 7 66 14
diagshow
Diagnostics Status: Sun Sep 21 12:58:10 2008
Slot: 7 UPORTS Port 7/0 7/1 7/2 7/3 7/4 7/5 7/6 7/7 7/8 7/9 7/10 7/11 7/12 7/13 7/14 7/15 BPort 15 14 13 12 31 30 29 28 47 46 45 44 63 62 61 60 Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Active Speed UP UP DN UP UP UP UP UP UP DN UP UP UP UP UP UP FrTX FrRX LLI Errs Loopback
2G Auto 1862053547 4046259472 741536 2G Auto 883880975 4159773045 10693 2G Auto ----
2G Auto 2726713752 3087444726 120429791 2G Auto 128605871 767856745 0 2G Auto 6711709 4442748 370031614 2G Auto 0 0 0
2G Auto 3710993523 2333646051 277072 2G Auto 871452296 589906482 45260 2G Auto 686091364 664115536 175774 2G Auto 931839521 2020569575 18559 2Gbps 1550691611 1652174816 27220
2G Auto 3510938986 3209788284 100
Central Memory: OK Total Diag Frames Tx: 0
Total Diag Frames Rx: 0
Slot: 8 UPORTS Port 8/0 8/1 8/2 8/3 8/4 8/5 8/6 8/7 8/8 8/9 8/10 8/11 8/12 8/13 8/14 8/15 BPort 15 14 13 12 31 30 29 28 47 46 45 44 63 62 61 60 Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Active Speed DN DN DN DN DN UP DN DN DN DN DN DN DN DN DN DN 2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -FrTX -----FrRX -----LLI Errs Loopback
2G Auto 70211136 2757874551 248247692 2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -2G Auto -2G Auto ----------------------
Central Memory: OK
Total Diag Frames Tx: 0 Total Diag Frames Rx: 0
Slot: 9 UPORTS Port 9/0 9/1 9/2 9/3 9/4 9/5 9/6 9/7 9/8 9/9 9/10 9/11 9/12 9/13 9/14 9/15 BPort 15 14 13 12 31 30 29 28 47 46 45 44 63 62 61 60 Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Active Speed UP UP DN UP UP UP UP UP DN UP UP UP UP UP UP UP FrTX FrRX LLI Errs Loopback
2G Auto 3558320257 3988416384 1054443 2G Auto 30501 131341 19328168
2G Auto 3200488231 3783501242 2386 2G Auto 922077094 3836900686 572378702 2G Auto 276632482 3370669139 1443352 2G Auto ----
2G Auto 28867979 2591357751 34043 2G Auto 3322061614 2682996886 27215 2G Auto 120 60122 177
Central Memory: OK Total Diag Frames Tx: 0 Total Diag Frames Rx: 0
Slot: 10 UPORTS Port 10/0 10/1 10/2 10/3 10/4 10/5 10/6 10/7 10/8 10/9 10/10 10/11 10/12 10/13 10/14 10/15 BPort 15 14 13 12 31 30 29 28 47 46 45 44 63 62 61 60 Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Active Speed DN UP UP DN UP UP UP UP DN UP UP UP UP UP UP UP 2G Auto -FrTX -FrRX -LLI Errs Loopback
2G Auto 2672619973 2063941345 167 2G Auto 3155474975 2845353988 9394693 2G Auto 1718579477 1089344763 20986 2G Auto 1389913663 3096686855 472299 2G Auto ----
2G Auto 3431364347 4125561933 350488 2G Auto 3397951292 1287685156 45404 2G Auto 129 67013 204
Central Memory: OK Total Diag Frames Tx: 0 Total Diag Frames Rx: 0 ddcbrcdb09:admin>
Attachments: errshow.txt (11.5 K)
Forgot to explain, this is the Exhnage server, and having performance issues and compalints only on this server. So i ahve asked them to change the HBA as of now, but i have to be the watcdog now.
hope i was clear.
TheEsp 138 posts since Feb 27, 2008 7. Re: PORTSHOW - tips and tricks Sep 23, 2008 8:32 PM in response to: Vijaya Prakash
HI Dishvijay
You can always log into the webtools on your switch's , if your getting port errors you'll see them in the switch event's window.
David
Dishvijay 14 posts since Sep 13, 2008 8. Re: PORTSHOW - tips and tricks Sep 27, 2008 11:13 AM in response to: bijukrishnan
Biju,
Already posted the outouts you requested, aint you have some time to look and this and help me here ?
Thanks Vij
ok here i go with the analysis, doing my best
You have issues with the cables connecting the follow ports.
45: 1.1g 2.0g 0 786
0 20 981
60: 2.2g 2.1g 0 102k 0 61: 1.6g 2.3g 0 102k 0
0 0
0 458k 32k 0 0 317k 31k 0
0 0
0 0
0 0
0 0
since there are only CRC errors. Remember CRC errors can traverse ISL's, hence if these are ISL ports please check the other switch as well.
For the portshow o/p u gave me, my analysis says that u need to replace first the SFP on the other end of this ISL first.
Free_buffer: Overrun: Suspended: Parity_err: 2_parity_err: 0
0 0 0
Address_err: 0 Lr_in: Lr_out: Ols_in: Ols_out: 1 7 66 14
Since in errors are more than out, I suspect the errors are coming in from the other end.
Check if the LLI errors are increasing by running repeated diagshow.
Finally check errdump -r and errshow -r to check if any ports are causing the switch to be marginal, check if theres anything u dont understand in the errorlog. I have had cases when the porterrshow does not show any issues but the switch has a faulty ASIC and this causes weird scenarios.
Thanks Very much Biju. That helps, i would do some analysis, already changed the HBA and put this server on a new port. Let me monitor for a while and come back to you.
have you ever heard this term "port generation number", under the portshow output ?
Whats your comments on this one.
Thanks Vij

PORTSHOW - Tips and Tricks: Guys

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PORTSHOW - Tips and Tricks: Guys

Uploaded by

Copyright:

Available Formats

PORTSHOW - tips and tricks

Dishvijay 14 posts since Sep 13, 2008

Generated by Jive SBS on 2011-12-09-07:00 1