HP Tachyon XL2 Fibre Channel

[Robert Bryan]

How do I upgrade the XL2 chip version to 2.3 from 2.2

I have one fibre card that is at the 2.2 revision level...the other three cards are at 2.3...
I was recieving async write errors from the 2.2 version card until I installed the latest patch...but the Maximum Frame Size = 1024, all the other cards are at 2048 and the Bad Rx Char errors are increasing


CSO-C col3shu1 # fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.2
PCI Sub-system Vendor ID is = 0x00103c PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x010000
N_Port Node World Wide Name = 0x50060b0000106f05
N_Port Port World Wide Name = 0x50060b0000106f04
Driver state = ONLINE
Hardware Path is = 1/0/2/0/0
Number of Assisted IOs = 3599171
Number of Active Login Sessions = 2
Dino Present on Card = NO
Maximum Frame Size = 1024
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 PHSS_31326) /ux/kern/kisu/TL/src/common
/wsio/td_glue.c: Sep 5 2005, 10:14:40

# fcmsutil /dev/td0 stat
Mon Jan 23 08:13:47 2006
Channel Statistics

Statistics From Link Status Registers ...
Loss of signal 53 Bad Rx Char 45645
Loss of Sync 56 Link Fail 67
Received EOFa 0 Discarded Frame 0
Bad CRC 0 Protocol Error 0

[Andrew Rutter]

hi robert,

This is usually only done by HP.

hp will usually update the cards through STM or the use of ss_config if needed. I doubt that you will even get the updated firmware out of them to try yourself and also the firmware update utility may ask you for a password, hp only one.

Best thing is to call HP with the serial number of your server.

Andy

[Robert Bryan]

Well thats what I didn't want to hear...

Thanks for your help

[Sameer_Nirmal]

Hi,

XL2 chip revision is chip manufacturing version number. If you see it is 2.2 , then this card was manufactured with XL2 2.2 chip. Saying this, this card has old XL2 (2.2) chip than the others who have XL2 (2.3) chip.
You are right in differntiating the "maximum frame size"
XL2/2.2 chip has 1024 bytes
XL2/2.3 chip has 2048 bytes
This is because the XL2/2.3 is new version and having new features.

Hence you need to replace the FC HBA card with latest one having XL2 (2.3) chip.

I guess you are seeing increasing the "Bad Rx Char" values after applying the patch, right?
If yes, then you can collect the stats for this card using following commands.
# fcmsutil vpd
# fcmsutil devstat all
# fcmsutil lb plm ( loopback test with loopback cable)
# fcmsutil stat -s
# tddiag

You can also run STM infotool and logtool to get more details.

Maybe the card or FC cable the FC port at switch side is at fault assuming latest "FCMS" driver installed.

[Robert Bryan]

Here is the output from the commands...
I just do not understand how the errors could be from the Maximum Frame Size = 1024 instead of 2048...

I know the EFI version: '000000'is wrong, but that shouldn't cause these errors either..



CSO-C col3shu1 # fcmsutil /dev/td0 vpd
V I T A L P R O D U C T D A T A
--------- ------------- -------

Product Discription :'A6795A 2Gbps/1Gbps Fibre Channel 4X PCI HBA'

Part number :'A6795-62001'

Engineering Date Code :'A-4210'

Part Serial number :'A56466102374'

Misc. Information :'PW=15W'

Mfd. Date :'A-4211'

Check Sum : 0x66

EFI version : '000000'

Asset Tag :'NA'

------------------------------------------

CSO-C col3shu1 # fcmsutil /dev/td0 stat -s
Tue Jan 24 07:27:16 2006
Channel Statistics

Statistics From Link Status Registers ...
Loss of signal 208 Bad Rx Char 179520
Loss of Sync 212 Link Fail 261
Received EOFa 0 Discarded Frame 1
Bad CRC 0 Protocol Error 0

-------------------------------------------

CSO-C col3shu1 # fcmsutil /dev/td0 devstat all
Tue Jan 24 07:26:27 2006
Device Statistics for Nport_id 0x010100

Successful opens of the device 469
Failed Open of previously opened device 0
Fast failure of the Open 0
PLOGIs sent to the device 269
PLOGIs Timedout 0
PRLIs sent to the device 109
PRLIs Timedout 0
Bad PRLI resps 0
PRLOs received 0
ADISCs sent to the device 0
ADISCs Timedout 0
Authentication failures 0
LOGOs sent to the device 8
LOGOs Timedout 0
LOGOs received 81
Target resets sent 0
Target resets failed 0
Implicit Logouts on the device 100
Bad TPRLO resp 0

PLOGI Resps error statistics ...
LS_RJTs recvd for PLOGI/PDISC sent 0
Short PLOGI Resps recvd 0
Low supported version higher than FC-PH-3 0
High supported version lower than FC-PH 4.3 0
No Class3 support 0
PWWN authentication failure 0
NWWN authentication failure 0
PLOGI retries in state dvs_open_plogi_delay 260

I/O Statistics ...
Assisted I/O requests 10600308
Timedout I/Os 0
No CDB available for I/O 0
2nd Level Error Recovery 0

I/O Completion Statistics ...
Good I/O completions 10587104
Read underflows 13048
Link Failure During FCP_RSP 0
FCP_RSP Overflow 0
Outbound Error For FCP_CMND 0
No resource For IO 0
Channel transient conditions 1064
Channel/Device not Online 0
Implicit aborts 1220
I/Os aborted 0

I/O Inbound Error Statistics ...
PLDA Non-Compliance 0
Unassisted FCP_RSP 0
Unassisted FCP_DATA 0
Bad Unassisted FCP_DATA 0
Unassisted FCP_CMND 0
UA FCP With Bad OX_ID 0
UA FCP With Bad F_CTL 0
Bad FCP_XFER_RDY 0
FCP_XFER_RDY and SEST invalid 0
FCP_XFER_RDY in invalid state 0
Bad Length For FCP_RSP Frame 0
FCP_RSP in invalid state 0
Bad Category For FCP Frame 0
Bad data_ro In FCP_XFER_RDY 0
Late ABTS Responses Received 0
BA_RJT for ABTS received 0
Bad responses to ABTS 0
IO Underruns 0

Other I/O Event Statistics ...
Unassisted FCP_XFER_RDY 0
Retries For Resources 0
Host Programming Errors 0
I/O Overflow Errors 0
LKF On Outbound Sequence 0
ASN On Outbound Sequence 0
Frame TimeOut Errors 0
Unexpected OCMs for I/Os 0
New I/Os on ERQ At LDN 0
I/Os on SLL At LDN 0
LUP Events For I/O 0
ABTS Sent 0
ABTS Resent 0
Unaccepted ABTS 0
LDNs Before Sending ABTS 0
LUPs For Sending ABTS 0
IFCM While Aborting I/O 0
FCP_RSP While Aborting I/O Requests 0
RRQ sent 0
RRQ send failures 0
RRQ replies recvd 0
-------------------------------------------------------------

Tue Jan 24 07:26:27 2006
Device Statistics for Nport_id 0x010200

Successful opens of the device 469
Failed Open of previously opened device 0
Fast failure of the Open 0
PLOGIs sent to the device 255
PLOGIs Timedout 0
PRLIs sent to the device 95
PRLIs Timedout 0
Bad PRLI resps 0
PRLOs received 0
ADISCs sent to the device 0
ADISCs Timedout 0
Authentication failures 0
LOGOs sent to the device 8
LOGOs Timedout 0
LOGOs received 34
Target resets sent 0
Target resets failed 0
Implicit Logouts on the device 34
Bad TPRLO resp 0

PLOGI Resps error statistics ...
LS_RJTs recvd for PLOGI/PDISC sent 0
Short PLOGI Resps recvd 0
Low supported version higher than FC-PH-3 0
High supported version lower than FC-PH 4.3 0
No Class3 support 0
PWWN authentication failure 0
NWWN authentication failure 0
PLOGI retries in state dvs_open_plogi_delay 246

I/O Statistics ...
Assisted I/O requests 14412
Timedout I/Os 0
No CDB available for I/O 0
2nd Level Error Recovery 0

I/O Completion Statistics ...
Good I/O completions 1330
Read underflows 13048
Link Failure During FCP_RSP 0
FCP_RSP Overflow 0
Outbound Error For FCP_CMND 0
No resource For IO 0
Channel transient conditions 28
Channel/Device not Online 0
Implicit aborts 34
I/Os aborted 0

I/O Inbound Error Statistics ...
PLDA Non-Compliance 0
Unassisted FCP_RSP 0
Unassisted FCP_DATA 0
Bad Unassisted FCP_DATA 0
Unassisted FCP_CMND 0
UA FCP With Bad OX_ID 0
UA FCP With Bad F_CTL 0
Bad FCP_XFER_RDY 0
FCP_XFER_RDY and SEST invalid 0
FCP_XFER_RDY in invalid state 0
Bad Length For FCP_RSP Frame 0
FCP_RSP in invalid state 0
Bad Category For FCP Frame 0
Bad data_ro In FCP_XFER_RDY 0
Late ABTS Responses Received 0
BA_RJT for ABTS received 0
Bad responses to ABTS 0
IO Underruns 0

Other I/O Event Statistics ...
Unassisted FCP_XFER_RDY 0
Retries For Resources 0
Host Programming Errors 0
I/O Overflow Errors 0
LKF On Outbound Sequence 0
ASN On Outbound Sequence 0
Frame TimeOut Errors 0
Unexpected OCMs for I/Os 0
New I/Os on ERQ At LDN 0
I/Os on SLL At LDN 0
LUP Events For I/O 0
ABTS Sent 0
ABTS Resent 0
Unaccepted ABTS 0
LDNs Before Sending ABTS 0
LUPs For Sending ABTS 0
IFCM While Aborting I/O 0
FCP_RSP While Aborting I/O Requests 0
RRQ sent 0
RRQ send failures 0
RRQ replies recvd 0
--------------------------------------------

[marie-noelle jeanson_1]

Bryan,

I do not think the errors come from the rev 2.2 or from the max frame size.
The Bad Rx and Link Fail stats may indicate a problem on the FC link somewhere and not a problem with the card...

Marie.

[Sameer_Nirmal · Accepted solution]

Hi,

There could be problems with MFS mismatch between originating device and target device on a FC channel. You can check the other end of the channel i.e. switch port and its MFS set, compatibility with MFS 1K.
As far as the XL2/2.2 chip is concerned, there were issues with it for 2K MFS. Hence 1K MFS is used with this chip.

Is this HBA installed in an Integrity Server? If yes, then there has to be latest EFI driver installed.

As per the stats posted, the high values of
'Bad Rx Char" maybe related to substantial
"Channel transient conditions". It maybe a case of transient protection failure with one of the devices ( HBA port or switch port or cable). In this case, switch port could be changed and error be observed. If same situation, then cable and then HBA could suspected/changed.

[Sameer_Nirmal]

Wanted to add...

The issue with MFS mis-match was taken care by the latest patch at driver level. So probability of cause of those errors on account MFS is less. More probably its hardware error with HBA/cable/switch port.

[Robert Bryan]

The server is an RP7410...Would the lack of an EFI driver cause the Bad Rx Char errors?

I am looking at replacing the cable between the server and the VA7400 array...If that does not work, I may need to replace the array controller.

[Sameer_Nirmal]

Hi,

No. EFI driver only comes into picture for Intergrity server. EFI is equivalent of BCH on PA-RISC servers. EFI driver on integrity server is used for HBA support and booting OS through HBA from a LUN.

Bad Rx Char errors are occuring at link level in FC channel level so hardware is fix is required.