Port Show

7/31/2019 Port Show

1/22

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

1

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 ?
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijay

7/31/2019 Port Show

2/22



2

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

7/31/2019 Port Show

3/22



3

Tags: portshow

bijukrishnan256 posts since

Apr 9, 20081.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

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:
http://community.brocade.com/message/5578#5578/FW-1436http://community.brocade.com/message/5578#5578/FW-1424http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5578#5578http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnanhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnan

7/31/2019 Port Show

4/22



4

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

Dishvijay14 posts since

Sep 13, 20082.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.
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5578#5578http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5578#5578http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5578#5578http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5578#5578http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5579#5579http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijay

7/31/2019 Port Show

5/22



5

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

7/31/2019 Port Show

6/22



6



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.

bijukrishnan256 posts sinceApr 9, 20084.Re: PORTSHOW - tips and tricks Sep 20, 2008 10:05 AM


Check this out....incase it helps..!

Attachments:

portErrShow.pdf (10.3 K)
http://servlet/JiveServlet/download/5581-1453/portErrShow.pdfhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5579#5579http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5579#5579http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5581#5581http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnanhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnanhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5579#5579http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5579#5579http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5580#5580http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnanhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnan

7/31/2019 Port Show

7/22



7


Sep 13, 20085.Re: PORTSHOW - tips and tricks Sep 21, 2008 12:14 PM


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.
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5580#5580http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5580#5580http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5582#5582http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijay

7/31/2019 Port Show

8/22



8

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 0 0 0 0 741k 7 0 0 0 0 0

1: 883m 4.1g 0 0 0 0 0 10k 4 0 0 0 0 0

2: 968m 3.1g 0 0 0 0 0 416k 21 0 0 0 0 0

3: 2.7g 3.0g 0 0 0 0 0 120m 0 0 0 0 0 0

4: 128m 767m 0 0 0 0 0 0 0 0 0 0 0 0

5: 6.7m 4.4m 0 0 0 0 0 370m 0 0 0 0 0 0

6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0

7: 193m 78m 0 0 0 0 0 0 0 0 0 0 0 0

8: 1.0g 774m 0 0 0 0 0 4 0 0 0 0 0 0

9: 3.8g 1.5g 0 0 0 0 0 578k 1 0 0 1 0 0

10: 3.7g 2.3g 0 0 0 0 0 277k 5.7k 0 0 0 0 0

11: 871m 589m 0 0 0 0 0 45k 0 0 0 0 0 0

12: 686m 664m 0 0 0 0 0 175k 0 0 0 0 0 0

13: 931m 2.0g 0 0 0 0 0 18k 8 0 0 0 0 0

14: 1.5g 1.6g 0 0 0 0 0 27k 0 0 0 0 0 0

15: 3.5g 3.2g 0 0 0 0 0 100 0 0 0 0 0 0

16: 0 0 0 0 0 0 0 27k 0 0 0 1 0 0

7/31/2019 Port Show

9/22



9

17: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

18: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

19: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

20: 0 0 0 0 0 0 0 78k 0 0 0 1 0 0

21: 70m 2.7g 0 0 0 0 0 248m 1 0 0 0 0 0

22: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

23: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

24: 0 0 0 0 0 0 0 33k 0 0 0 1 0 0

25: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

26: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

27: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

28: 0 0 0 0 0 0 0 14k 0 0 0 1 0 0

29: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

30: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

31: 0 0 0 0 0 0 0 0 0 0 0 1 0 0

32: 538m 637m 0 0 0 0 0 2.2k 0 0 0 0 0 0

33: 956m 1.1g 0 0 0 0 0 34k 7 0 0 0 0 0

34: 2.0g 1.0g 0 0 0 0 0 403 38 0 0 1 0 0

35: 3.5g 3.9g 0 0 0 0 0 1.0m 0 0 0 0 0 0

36: 30k 131k 0 0 0 0 0 19m 0 0 0 0 0 0

37: 3.2g 3.7g 0 0 0 0 0 2.3k 1 0 0 0 0 0

38: 922m 3.8g 0 0 0 0 0 572m 2 0 0 0 0 0

7/31/2019 Port Show

10/22



10

39: 276m 3.3g 0 0 0 0 0 1.4m 18 0 0 0 0 0

40: 2.9g 114m 0 0 0 0 0 19m 54 0 0 1 0 0

41: 28m 2.5g 0 0 0 0 0 34k 0 0 0 0 0 0

42: 3.3g 2.6g 0 0 0 0 0 27k 0 0 0 0 0 0

43: 120 60k 0 0 0 0 0 177 0 0 0 0 0 0

44: 771m 3.2g 0 0 0 0 0 20m 0 0 0 0 0 0

45: 1.1g 2.0g 0 786 0 0 0 20 981 0 0 0 0 0

46: 3.5g 4.0g 0 0 0 0 0 95 260 0 0 0 0 0

47: 325m 3.3g 0 0 0 0 0 149 0 0 0 0 0 0

48: 986m 1.2g 0 0 0 0 0 2.4m 20 0 0 1 0 0

49: 2.6g 346m 0 0 0 0 0 2.1m 486 0 0 0 0 0

50: 2.9g 2.0g 0 0 0 0 0 635k 0 0 0 0 0 0

51: 278k 297k 0 0 0 0 0 25k 0 0 0 1 0 0

52: 2.6g 2.0g 0 0 0 0 0 167 0 0 0 0 0 0

53: 3.1g 2.8g 0 0 0 0 0 9.3m 0 0 0 0 0 0

54: 1.7g 1.0g 0 0 0 0 0 20k 0 0 0 0 0 0

55: 1.3g 3.0g 0 0 0 0 0 472k 1 0 0 0 0 0

56: 4.0g 2.2g 0 0 0 0 0 5.7m 3 0 0 1 0 0

57: 3.4g 4.1g 0 0 0 0 0 350k 0 0 0 0 0 0

58: 3.3g 1.2g 0 0 0 0 0 45k 0 0 0 0 0 0

59: 129 67k 0 0 0 0 0 204 0 0 0 0 0 0

60: 2.2g 2.1g 0 102k 0 0 0 458k 32k 0 0 0 0 0

7/31/2019 Port Show

11/22



11

61: 1.6g 2.3g 0 102k 0 0 0 317k 31k 0 0 0 0 0

62: 3.5g 3.3g 0 0 0 0 0 29m 13 0 0 0 0 0

63: 2.0g 3.8g 0 0 0 0 0 206 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 Online

portPhys: 6 In_Sync

portScn: 32 F_Port

port generation number: 18

portId: 090500

portIfId: 4372001e

portWwn: 20:05:00:60:69:80:40:03

portWwn of device(s) connected:

21:00:00:e0:8b:9d:8f:39

7/31/2019 Port Show

12/22



12

Distance: normal

portSpeed: N2Gbps

Interrupts: 302428 Link_failure: 7 Frjt: 0

Unknown: 156 Loss_of_sync: 289323 Fbsy: 0

Lli: 289845 Loss_of_sig: 4

Proc_rqrd: 12574 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: 66

Suspended: 0 Lr_out: 14

Parity_err: 0 Ols_in: 1

2_parity_err: 0 Ols_out: 7

CMI_bus_err: 0

diagshow

Diagnostics Status: Sun Sep 21 12:58:10 2008

7/31/2019 Port Show

13/22



13

Slot: 7 UPORTS

Port BPort Diag Active Speed FrTX FrRX LLI Errs Loopback

7/0 15 OK UP 2G Auto 1862053547 4046259472 741536

7/1 14 OK UP 2G Auto 883880975 4159773045 10693

7/2 13 OK DN 2G Auto -- -- --

7/3 12 OK UP 2G Auto 2726713752 3087444726 120429791

7/4 31 OK UP 2G Auto 128605871 767856745 0

7/5 30 OK UP 2G Auto 6711709 4442748 370031614

7/6 29 OK UP 2G Auto 0 0 0

7/7 28 OK UP 2G Auto 193382237 78401570 0

7/8 47 OK UP 2G Auto 1084493194 774674253 4

7/9 46 OK DN 2G Auto -- -- --

7/10 45 OK UP 2G Auto 3710993523 2333646051 277072

7/11 44 OK UP 2G Auto 871452296 589906482 45260

7/12 63 OK UP 2G Auto 686091364 664115536 175774

7/13 62 OK UP 2G Auto 931839521 2020569575 18559

7/14 61 OK UP 2Gbps 1550691611 1652174816 27220

7/15 60 OK UP 2G Auto 3510938986 3209788284 100

Central Memory: OK

Total Diag Frames Tx: 0

7/31/2019 Port Show

14/22



14

Total Diag Frames Rx: 0

Slot: 8 UPORTS


8/0 15 OK DN 2G Auto -- -- --

8/1 14 OK DN 2G Auto -- -- --

8/2 13 OK DN 2G Auto -- -- --

8/3 12 OK DN 2G Auto -- -- --

8/4 31 OK DN 2G Auto -- -- --

8/5 30 OK UP 2G Auto 70211136 2757874551 248247692

8/6 29 OK DN 2G Auto -- -- --

8/7 28 OK DN 2G Auto -- -- --

8/8 47 OK DN 2G Auto -- -- --

8/9 46 OK DN 2G Auto -- -- --

8/10 45 OK DN 2G Auto -- -- --

8/11 44 OK DN 2G Auto -- -- --

8/12 63 OK DN 2G Auto -- -- --

8/13 62 OK DN 2G Auto -- -- --

8/14 61 OK DN 2G Auto -- -- --

8/15 60 OK DN 2G Auto -- -- --

Central Memory: OK

7/31/2019 Port Show

15/22



15



Slot: 9 UPORTS


9/0 15 OK UP 2G Auto 538074606 637107728 2288

9/1 14 OK UP 2G Auto 956477849 1160958483 34880

9/2 13 OK DN 2G Auto -- -- --

9/3 12 OK UP 2G Auto 3558320257 3988416384 1054443

9/4 31 OK UP 2G Auto 30501 131341 19328168

9/5 30 OK UP 2G Auto 3200488231 3783501242 2386

9/6 29 OK UP 2G Auto 922077094 3836900686 572378702

9/7 28 OK UP 2G Auto 276632482 3370669139 1443352

9/8 47 OK DN 2G Auto -- -- --

9/9 46 OK UP 2G Auto 28867979 2591357751 34043

9/10 45 OK UP 2G Auto 3322061614 2682996886 27215

9/11 44 OK UP 2G Auto 120 60122 177

9/12 63 OK UP 2G Auto 771901593 3273115214 20528175

9/13 62 OK UP 2G Auto 1121902354 2086586583 806

9/14 61 OK UP 2G Auto 3568726127 4016274357 95

9/15 60 OK UP 2G Auto 325327198 3359424437 149

7/31/2019 Port Show

16/22



16

Central Memory: OK



Slot: 10 UPORTS


10/0 15 OK DN 2G Auto -- -- --

10/1 14 OK UP 2G Auto 2669522499 346653356 2169525

10/2 13 OK UP 2G Auto 2979276987 2091594080 635930

10/3 12 OK DN 2G Auto -- -- --

10/4 31 OK UP 2G Auto 2672619973 2063941345 167

10/5 30 OK UP 2G Auto 3155474975 2845353988 9394693

10/6 29 OK UP 2G Auto 1718579477 1089344763 20986

10/7 28 OK UP 2G Auto 1389913663 3096686855 472299

10/8 47 OK DN 2G Auto -- -- --

10/9 46 OK UP 2G Auto 3431364347 4125561933 350488

10/10 45 OK UP 2G Auto 3397951292 1287685156 45404

10/11 44 OK UP 2G Auto 129 67013 204

10/12 63 OK UP 2G Auto 2216390361 2116839766 560915

10/13 62 OK UP 2G Auto 1601766910 2383454207 420500

10/14 61 OK UP 1G Auto 3528457047 3345891224 29878002

10/15 60 OK UP 2G Auto 2084196779 3899724786 206

7/31/2019 Port Show

17/22



17

Central Memory: OK



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.
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5580#5580http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5580#5580http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5583#5583http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/servlet/JiveServlet/download/5582-1454/errshow.txt

7/31/2019 Port Show

18/22



18

TheEsp138 posts since

Feb 27, 20087.Re: PORTSHOW - tips and tricks Sep 23, 2008 8:32 PM


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
http://community.brocade.com/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5583#5583http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5583#5583http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5571#5571http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/TheEsphttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/TheEsp

7/31/2019 Port Show

19/22



19


Sep 13, 20088.Re: PORTSHOW - tips and tricks Sep 27, 2008 11:13 AM


Biju,

Already posted the outouts you requested, aint you have some time to look and this and

help me here ?

Thanks

Vij
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5581#5581http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5581#5581http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5602#5602http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijay

7/31/2019 Port Show

20/22



20




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 0 0 20 981 0 0 0 0 0

60: 2.2g 2.1g 0 102k 0 0 0 458k 32k 0 0 0 0 0

61: 1.6g 2.3g 0 102k 0 0 0 317k 31k 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.
http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5602#5602http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5602#5602http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5616#5616http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnanhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/bijukrishnan

7/31/2019 Port Show

21/22



21

Free_buffer: 0 Address_err: 0

Overrun: 0 Lr_in: 66

Suspended: 0 Lr_out: 14

Parity_err: 0 Ols_in: 1

2_parity_err: 0 Ols_out: 7

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.



http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5616#5616http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5616#5616http://localhost/var/www/apps/conversion/current/tmp/scratch28553/message/5626#5626http://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijayhttp://localhost/var/www/apps/conversion/current/tmp/scratch28553/people/Dishvijay

7/31/2019 Port Show

22/22


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

Documents

Port Show