Brocade SAN Switch status change to Down [ Edited ]

[kishor.kumar3@hpe.c…]

Hi All,

Good Day.

We are getting alerts for brocade SAN switch changing status from healthy to down.

When we check the actual status of the switch it would be healthy. And in the errshow we could see some errors like 

"2017/12/31-11:19:07, [FW-1437], 3025, FID 128, WARNING, ****************, Switch status change contributing factor Faulty ports: 1 faulty out of 48 ports:config(2.08 percent,1). (Port(s) 32(0x20))."

Can anybody please tell me how to troubleshoot this issue.

1. What is the cause ?

2. How to check which port has gone faulty (checked the status of ports all looks normal"

3. How can we prevent this kind of alerts in future.

Regards,

KK

[Antonio Bongiorno T…]

kishor.kumar3@hpe.com

stay indicated, Port 32 become faulty due incompatible SFP, or wrong setting Speed due missing License.

"2017/12/31-11:19:07, [FW-1437], 3025, FID 128, WARNING, ****************, Switch status change contributing factor Faulty ports: 1 faulty out of 48 ports:config(2.08 percent,1). (Port(s) 32(0x20))."

post follow details please:

otput from CLI

"licenseshow"

"sfpshow" from the port ins question

Additional FOS Release and Switch Type

In the mean time, wishes happy new years

[kishor.kumar3@hpe.c…]

Hi Antonio,

Thanks for the reply.

Please find the below outputs.

licenshow

YCDSgT7Eg4ZYPSMGRZ3mQStQLYCEBtGWBJEBQ:
First Ports on Demand license - additional 12 port upgrade license

sfpshow for port 32

Identifier: 3 SFP
Connector: 7 LC
Transceiver: 540c404000000000 2,4,8_Gbps M5,M6 sw Short_dist
Encoding: 1 8B10B
Baud Rate: 85 (units 100 megabaud)
Length 9u: 0 (units km)
Length 9u: 0 (units 100 meters)
Length 50u (OM2): 5 (units 10 meters)
Length 50u (OM3): 0 (units 10 meters)
Length 62.5u:2 (units 10 meters)
Length Cu: 0 (units 1 meter)
Vendor Name: BROCADE
Vendor OUI: 00:05:1e
Vendor PN: 57-1000117-01
Vendor Rev: A
Wavelength: 850 (units nm)
Options: 003a Loss_of_Sig,Tx_Fault,Tx_Disable
BR Max: 0
BR Min: 0
Serial No: UAF4130000003VV
Date Code: 130929
DD Type: 0x68
Enh Options: 0xfa
Status/Ctrl: 0x82
Alarm flags[0,1] = 0x5, 0x0
Warn Flags[0,1] = 0x5, 0x0
Alarm Warn
low high low high
Temperature: 35 Centigrade -10 90 -5 85
Current: 6.562 mAmps 1.000 17.000 2.000 14.000
Voltage: 3306.0 mVolts 2900.0 3700.0 3000.0 3600.0
RX Power: -5.0 dBm (316.6uW) 10.0 uW 1258.9 uW 15.8 uW 1000.0 uW
TX Power: -3.2 dBm (475.7 uW) 125.9 uW 631.0 uW 158.5 uW 562.3 uW

State transitions: 1
Last poll time: 12-31-2017 UTC Sun 14:26:23

Also can you please let me know what is 0x20 in 32(0x20) ?

Regards,

KK

[Antonio Bongiorno T…]

kishor.kumar3@hpe.com

the (020) stay Indicated the Port in HEX Decimal, see conversion table

simpled saied, Phisical Port 32 is HEX = 20

Decimal	31	32	33	34	35	36	37	38	39	40
Hex	1f	20	21	22	23	24	25	26	27	28

http://www.brocade.com/content/html/en/troubleshooting-guide/FOS_740_TSHOOT/GUID-3A1B4583-09D7-4278-B794-05CD2185C482.html

I ask in my preiview answer additional for FOS Release  ( I'm assuming you are on FOS 7.x )

some Defect was closed in diverse FOS Release, please tel me the exact FOS current running,

and Switch Type / Model, is this 6510 ?

[kishor.kumar3@hpe.c…]

Antonio... Really sorry ... missed to wish you "HAPPY NEW YEAR" 

I am gathering the details will give you soon.. 

[kishor.kumar3@hpe.c…]

Yes Antonio, Switch model is 6510.

And the firmware version is as below.

Appl Primary/Secondary Versions
------------------------------------------
FOS v7.1.1
v7.1.1

Please check and let me know. 

Regards,

KK

[Antonio Bongiorno T… · Accepted solution]

kishor.kumar3@hpe.com

is a Defect detected in FOS 7.1.1

DEFECT000512057

was Fixed in  follow Release

FOS7.1.2b
FOS7.2.1c
FOS7.3.0a
FOS7.3.1

and

FOS7.4.0, however in FOS 7.4.x and higher FW = Fabric Watch is not longer supported

if FW and APM License is installed, the switch become Fabric Vision capable, and you can convert to MAPS

[kishor.kumar3@hpe.c…]

Thank you Antonio .. .

I got the answer.

But still one more doubt .. Does that mean due to the defect in Firmware port is going to faulty state ? or is that actaully a false alert .. ?

Regards,

KK

[Antonio Bongiorno T… · Accepted solution]

kishor.kumar3@hpe.com

would be a false alert, it would not be a Fixed available.

I would suggest to upgrade first to next higher Fixed Rel. 7.1.2b