Fibre Channel (SAN)

Reply
Contributor
Posts: 23
Registered: ‎05-16-2017

Re: B2B Zero in Dual Fabric same Time

Dear Martin,

 

Thank´s for your Info, now I run the Commands, in attached the output ;-)

 

regards

Ernst

Brocade Moderator
Posts: 375
Registered: ‎03-29-2011

Re: B2B Zero in Dual Fabric same Time

Hi,

 

I have been looking at the provided the data - the following stands out (excluding the B2B):

 

### S000PS04

 

2017/10/08-23:47:36, [AN-1010], 6040, FID 128, WARNING, S000PS04, Severe latency bottleneck detected at E-Port 67.
2017/10/08-23:49:39, [C2-1029], 6041, CHASSIS, WARNING, DS_5300B,  Detected credit loss on Port of Slot 0, Port 67(81) vc_no=2 crd(s)lost=3 complete_loss:1.
2017/10/08-23:49:39, [C2-1014], 6042, CHASSIS, WARNING, DS_5300B,  Link Reset on Port S0,P67(81) vc_no=2 crd(s)lost=3 auto trigger.

 

  7: 67-> 17 10:00:c4:f5:7c:84:ff:f6   7 S000PS12        sp:  8.000G bw:  8.000G

 

so look like loosing buffer credit here. Check the physical link quality (sfp / cables).

 

### B2B on the ISL

 

Below is the summary of the portstatsshow - interesting (as I suspect) the high increment at 08 seems to be mostly

traffic on VC0, which is management traffic (switch to switch and Management Server and Common Transport):

 


S000PS03:admin> portstatsshow 31
stat_wtx             1520874436  4-byte words transmitted
stat_wrx             128582147   4-byte words received
stat_ftx             18146512    Frames transmitted
stat_frx             14665293    Frames received
tim_rdy_pri          53          Time R_RDY high priority
tim_txcrd_z          205366      Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   205366      0           0           0        

S000PS03:admin> portstatsshow 75
stat_wtx             1506119064  4-byte words transmitted
stat_wrx             185347612   4-byte words received
stat_ftx             18099412    Frames transmitted
stat_frx             14867850    Frames received
tim_rdy_pri          46          Time R_RDY high priority
tim_txcrd_z          0           Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   0           0           0           0        

S000PS04:admin> portstatsshow 31 (downstream) (LS)
stat_wtx             2977717946  4-byte words transmitted
stat_wrx             857340611   4-byte words received
stat_ftx             21334442    Frames transmitted
stat_frx             16471864    Frames received
tim_rdy_pri          109         Time R_RDY high priority
tim_txcrd_z          370016      Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   370016      0           0           0        
stat64_aveTxFrameSize 411         Average Tx Frame size 
stat64_aveRxFrameSize 326         Average Rx Frame size 

S000PS04:admin> portstatsshow 75 (LS)
stat_wtx             2942925478  4-byte words transmitted
stat_wrx             867030306   4-byte words received
stat_ftx             21245762    Frames transmitted
stat_frx             16546357    Frames received
tim_rdy_pri          95          Time R_RDY high priority
tim_txcrd_z          0           Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   0           0           0           0        
stat64_aveTxFrameSize 377         Average Tx Frame size
stat64_aveRxFrameSize 293         Average Rx Frame size

S001PS03:admin> portstatsshow 0 LS
stat_wtx             245804592   4-byte words transmitted
stat_wrx             1727267086  4-byte words received
stat_ftx             15039574    Frames transmitted
stat_frx             18639501    Frames received
tim_rdy_pri          434         Time R_RDY high priority
tim_txcrd_z          1877517     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   1875499     0           2018        0        
stat64_aveTxFrameSize 302         Average Tx Frame size
stat64_aveRxFrameSize 286         Average Rx Frame size

S001PS03:admin> portstatsshow 4 LS (upstream)
stat_wtx             163117231   4-byte words transmitted
stat_wrx             1730791327  4-byte words received
stat_ftx             14754779    Frames transmitted
stat_frx             18639866    Frames received
tim_rdy_pri          497         Time R_RDY high priority
tim_txcrd_z          9704357     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   9703742     0           615         0        
stat64_aveTxFrameSize 306         Average Tx Frame size
stat64_aveRxFrameSize 275         Average Rx Frame size

S001PS04:admin> portstatsshow 0
stat_wtx             850156039   4-byte words transmitted
stat_wrx             3018900184  4-byte words received
stat_ftx             16501781    Frames transmitted
stat_frx             21347324    Frames received
tim_rdy_pri          1158        Time R_RDY high priority
tim_txcrd_z          1955326     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   1946371     0           8955        0        
stat64_aveTxFrameSize 292         Average Tx Frame size
stat64_aveRxFrameSize 335         Average Rx Frame size 

S001PS04:admin> portstatsshow 4
stat_wtx             840448840   4-byte words transmitted
stat_wrx             3057960161  4-byte words received
stat_ftx             16436592    Frames transmitted
stat_frx             21452518    Frames received
tim_rdy_pri          1207        Time R_RDY high priority
tim_txcrd_z          9858095     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   9847027     0           11068       0        
stat64_aveTxFrameSize 279         Average Tx Frame size
stat64_aveRxFrameSize 372         Average Rx Frame size

 

So, next step would be portlogdump from the switches (taken at 0805) to see if there is some management traffic on the ISLs.

 

Moreover for your 5300 switches, I hope that backend credit recovery and also since it is 8GB, front end credit recovery?




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".


Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Brocade Moderator
Posts: 375
Registered: ‎03-29-2011

Re: B2B Zero in Dual Fabric same Time

Hi,

 

I have been looking at the provided the data - the following stands out (excluding the B2B):

 

### S000PS04

 

2017/10/08-23:47:36, [AN-1010], 6040, FID 128, WARNING, S000PS04, Severe latency bottleneck detected at E-Port 67.
2017/10/08-23:49:39, [C2-1029], 6041, CHASSIS, WARNING, DS_5300B,  Detected credit loss on Port of Slot 0, Port 67(81) vc_no=2 crd(s)lost=3 complete_loss:1.
2017/10/08-23:49:39, [C2-1014], 6042, CHASSIS, WARNING, DS_5300B,  Link Reset on Port S0,P67(81) vc_no=2 crd(s)lost=3 auto trigger.

 

  7: 67-> 17 10:00:c4:f5:7c:84:ff:f6   7 S000PS12        sp:  8.000G bw:  8.000G

 

so look like loosing buffer credit here. Check the physical link quality (sfp / cables).

 

### B2B on the ISL

 

Below is the summary of the portstatsshow - interesting (as I suspect) the high increment at 08 seems to be mostly

traffic on VC0, which is management traffic (switch to switch and Management Server and Common Transport):

 


S000PS03:admin> portstatsshow 31
stat_wtx             1520874436  4-byte words transmitted
stat_wrx             128582147   4-byte words received
stat_ftx             18146512    Frames transmitted
stat_frx             14665293    Frames received
tim_rdy_pri          53          Time R_RDY high priority
tim_txcrd_z          205366      Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   205366      0           0           0        

S000PS03:admin> portstatsshow 75
stat_wtx             1506119064  4-byte words transmitted
stat_wrx             185347612   4-byte words received
stat_ftx             18099412    Frames transmitted
stat_frx             14867850    Frames received
tim_rdy_pri          46          Time R_RDY high priority
tim_txcrd_z          0           Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   0           0           0           0        

S000PS04:admin> portstatsshow 31 (downstream) (LS)
stat_wtx             2977717946  4-byte words transmitted
stat_wrx             857340611   4-byte words received
stat_ftx             21334442    Frames transmitted
stat_frx             16471864    Frames received
tim_rdy_pri          109         Time R_RDY high priority
tim_txcrd_z          370016      Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   370016      0           0           0        
stat64_aveTxFrameSize 411         Average Tx Frame size 
stat64_aveRxFrameSize 326         Average Rx Frame size 

S000PS04:admin> portstatsshow 75 (LS)
stat_wtx             2942925478  4-byte words transmitted
stat_wrx             867030306   4-byte words received
stat_ftx             21245762    Frames transmitted
stat_frx             16546357    Frames received
tim_rdy_pri          95          Time R_RDY high priority
tim_txcrd_z          0           Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   0           0           0           0        
stat64_aveTxFrameSize 377         Average Tx Frame size
stat64_aveRxFrameSize 293         Average Rx Frame size

S001PS03:admin> portstatsshow 0 LS
stat_wtx             245804592   4-byte words transmitted
stat_wrx             1727267086  4-byte words received
stat_ftx             15039574    Frames transmitted
stat_frx             18639501    Frames received
tim_rdy_pri          434         Time R_RDY high priority
tim_txcrd_z          1877517     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   1875499     0           2018        0        
stat64_aveTxFrameSize 302         Average Tx Frame size
stat64_aveRxFrameSize 286         Average Rx Frame size

S001PS03:admin> portstatsshow 4 LS (upstream)
stat_wtx             163117231   4-byte words transmitted
stat_wrx             1730791327  4-byte words received
stat_ftx             14754779    Frames transmitted
stat_frx             18639866    Frames received
tim_rdy_pri          497         Time R_RDY high priority
tim_txcrd_z          9704357     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   9703742     0           615         0        
stat64_aveTxFrameSize 306         Average Tx Frame size
stat64_aveRxFrameSize 275         Average Rx Frame size

S001PS04:admin> portstatsshow 0
stat_wtx             850156039   4-byte words transmitted
stat_wrx             3018900184  4-byte words received
stat_ftx             16501781    Frames transmitted
stat_frx             21347324    Frames received
tim_rdy_pri          1158        Time R_RDY high priority
tim_txcrd_z          1955326     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   1946371     0           8955        0        
stat64_aveTxFrameSize 292         Average Tx Frame size
stat64_aveRxFrameSize 335         Average Rx Frame size 

S001PS04:admin> portstatsshow 4
stat_wtx             840448840   4-byte words transmitted
stat_wrx             3057960161  4-byte words received
stat_ftx             16436592    Frames transmitted
stat_frx             21452518    Frames received
tim_rdy_pri          1207        Time R_RDY high priority
tim_txcrd_z          9858095     Time TX Credit Zero (2.5Us ticks)
tim_txcrd_z_vc  0- 3:   9847027     0           11068       0        
stat64_aveTxFrameSize 279         Average Tx Frame size
stat64_aveRxFrameSize 372         Average Rx Frame size

 

So, next step would be portlogdump from the switches (taken at 0805) to see if there is some management traffic on the ISLs.

 

Moreover for your 5300 switches, I hope that backend credit recovery and also since it is 8GB, front end credit recovery?




If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution".


Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Contributor
Posts: 23
Registered: ‎05-16-2017

Re: B2B Zero in Dual Fabric same Time

Hi Martin,

 

Thank´s I send you the Information.

 

Regards

Ernst

Contributor
Posts: 23
Registered: ‎05-16-2017

Re: B2B Zero in Dual Fabric same Time

Dear Martin,

 

Now the Dumps from all ISL on all 24 Switches pfffhhhhh ;-)

Highlighted
Contributor
Posts: 23
Registered: ‎05-16-2017

Re: B2B Zero in Dual Fabric same Time

Sorry wrong Zip

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

Click to Register
Download FREE NVMe eBook