HPE Knowledge Article

Transcription

1 HPE Knowledge Article HPE FlexFabric 5900CP Switch Series - JG838A Switch Fiber Channel Configuration and Troubleshooting Cheatsheet Article Number mmr_sf-en_us Environment Working FC config with Windows 2008 R2 and 3PAR 7400 (FC to FC config, no FcoE). Issue Troubleshooting Fiber Channel on HPE 5900CP Switch. Cause HPE 5900CP Fiber Channel Configuration and Troubleshooting guidance. Resolution 1.# Install the latest version: HP Comware Software, Version , Release 2311P06 2.#Configure advanced working mode: [5900cp-m26]system-working-mode advance Do you want to change the system working mode? [Y/N]:y The system working mode is changed, please save the configuration and reboot the system to make it effective. [5900cp-m26]quit <5900cp-m26>save safely force <5900cp-m26> reboot force 3.#Enable FCF mode: [5900cp-m26]fcoe-mode fcf 4.#Create a vsan: [5900cp-m26]vsan 100 [5900cp-m26-vsan100]domain-id 1 preferred [5900cp-m26-vsan100]quit

2 5. #Remember, 5900cp is an Ethernet switch at the core. #The phy chip understands FC, but to pass packets between ports, the switch needs to convert the frames to FCoE. #You cannot get to a vsan unless you associate a vlan to the vsan. #That explains the need for this statement: [5900cp-m26]vlan 4001 [5900cp-m26-vlan4001]fcoe enable vsan 100 [5900cp-m26-vlan4001]quit 6. #Change the personality of the port from ethernet to FC on port 11 and 12: [5900cp-m26] int ten 1/0/11 [5900CP-m26 Ten-GigabitEthernet1/0/11]port-type fc [5900cp-m26-Fc1/0/11] port access vsan 100 [5900cp-m26] int ten 1/0/12 [5900CP-m26 Ten-GigabitEthernet1/0/11]port-type fc [5900cp-m26-Fc1/0/12] port access vsan Check your work: [5900cp-m26]dis int br Brief information on FC interface(s): Admin Mode: auto - auto; E - e port; F - f port; NP - n port proxy Oper Mode: E - e port; F - f port; NP - n port proxy; TE - trunking e port; TF - trunking f port; TNP - trunking n port proxy Interface VSAN Admin Admin Oper Trunk Mode Oper Speed Status Fc1/0/ F auto F 8G UP----> set to F mode Fc1/0/ auto auto F 8G UP----> auto is default Fc1/0/ auto auto F 2G UP [5900cp-m26-Fc1/0/11]dis this # interface Fc1/0/11 speed 8000 fc mode f port access vsan 100 # return [5900cp-m26-Fc1/0/11]fc mode? auto Set the port to Auto mode e Set the port to E mode f Set the port to F mode ====================================================================== Troubleshooting FC login issue: [5900cp-m26]dis int fc1/0/11 Fc1/0/11 Current state: UP Line protocol state: UP------> FC protocol will be down is the fabric cannot login. Description: Fc1/0/11 Interface Bandwidth: kbps Maximum Transmit Unit: Mbps-speed mode Internet protocol processing: disabled Link layer protocol is FC Fill word is idle-arbff Port WWN is 28:01:44:31:92:82:84:19 FC mode is F, state is F------> this will also be FIsolate. [5900cp-m26]terminal debugging [5900cp-m26]terminal monitor [5900cp-m26]debugging fc link login-out

3 #I shutdown port fc1/0/11 and unshut' it to watch the fc login (with debug enabled). [5900cp-m26-Fc1/0/11] undo shut %Jan 1 18:01:32: cp-m26 IFNET/3/PHY_UPDOWN: Fc1/0/11 link status is up. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Received FLOGI request frame in VSAN 100. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Get FIB status 0 of FCID in VSAN 100. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Delayed sending FLOGI or FDISC ACC frame in VSAN 100. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Delay timer timed out in VSAN 100. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Sent FLOGI or FDISC ACC frame in VSAN 100. *Jan 1 18:01:32: cp-m26 FCLINK/7/LOGINOUT: Interface Fc1/0/11: Login succeeded in VSAN 100. [5900cp-m26]dis fc login Interface VSAN FCID Node WWN Port WWN Fc 1/0/ x f:f7:00:02:ac:00:88:e6 21:22:00:02:ac:00:88:e6----> 3par 7400 SAN Fc 1/0/ x f:f7:00:02:ac:00:88:e6 20:22:00:02:ac:00:88:e6----> 3par 7400 SAN Fc 1/0/ x :00:00:00:c9:93:d5:fa 10:00:00:00:c9:93:d5:fa----> windows 2008 R2 FC HBA [5900cp-m26]dis fc name-service database VSAN: 100 FCID Type PWWN(vendor) FC4-type:feature 0x x01(N) 21:22:00:02:ac:00:88:e6 SCSI-FCP:Target-----> 3par 7400 SAN 0x x01(N) 20:22:00:02:ac:00:88:e6 SCSI-FCP:Target-----> 3par 7400 SAN 0x x01(N) 10:00:00:00:c9:93:d5:fa(Emulex) SCSI-FCP:Initiator--->windows 2008 R2 FC HBA [5900cp-m26]undo debug all ========================================================================== [5900cp-m26]dis counters inbound interface [5900cp-m26]dis counters outbound interface ============================================================================= Common problem: The server could see the WWN of the disks and the disks could see the WWN of the server, but the server could not actually access the disks. This could be an interoperability issue. But also, multiple issue can result in the same symptom: On older FC HBA that only run at 2G, you may need to change the Fill word from idle-arbff to idle-idle. For example: Fc1/0/ F auto F 8G UP Fc1/0/ auto auto F 8G UP Fc1/0/ auto auto F 2G UP [5900cp-m26-Fc1/0/48]dis this # interface Fc1/0/48 speed 2000 port access vsan 100 # return [5900cp-m26-Fc1/0/48]fill? idle-arbff Sets IDLE mode for the link initialization and ARB(ff) as the fill word idle-idle Sets IDLE mode for the link initialization and IDLE as the fill

4 word [5900cp-m26-Fc1/0/48]fill idle-idle ----> changed from idle-arbff ===================================================================== 5900CP Supported Transceivers: H6Z42A Limited 10GbE, 8/4G FC SR compatible (100M) ---->'This is the wire once' transceiver. AJ718A 8/4/2G SR -----> use this for straight FC with older HBA's running 2G. AW584A 8G FC LR HPN 1/10/40 GbE see 5900 QuickSpec =================================================================== [5900cp-m26]dis zone status vsan 100 VSAN 100: Mode: basic Default zone: deny >???? Distribute: active only Hard-zoning: enabled Full zoning database: Zonesets: 0, Zones: 0, Zone-aliases: 0 Status: free [5900CP-1]vsan 100 [5900CP-1-vsan100]zone default-zone permit [5900cp-m26]dis zone status vsan 100 VSAN 100: Mode: basic Default zone: permit--->will work now! Distribute: active only Hard-zoning: enabled Full zoning database: Zonesets: 0, Zones: 0, Zone-aliases: 0 Status: free =================================================================== FC Display Commands: display fc domain // Show domain info inside VSAN display fc domain-list //Show domain-list inside VSAN display fc ess //Show fc ess negotiation results in VSAN display fc login //Show Node login info display fc name-service database//show fc name-service database in VSAN display fc scr-table //Show fc SCR registration info for N-port display fc timer //Show fc timer in VSAN? display fc fib //Show fc fib entry display fc routing-table // Show FC routing table display vsan port-member // Show port member info in VSAN ============================================================================== FC interface debugging:

5 debugging fc link // Open the fc link debugging debugging fc link login-out // Open FC login and logout debugging Fabric debugging: debugging fc configuration // Open Fabric configuration debugging debugging fc name-service //Open FC name-service debugging FC routing and forward debugging: debugging fc exchange // Open FC Exchange debugging debugging fc forward // Open FC forward debugging debugging fc rm // Open FC routing management debugging VSAN debugging: debugging vsan // Open VSAN debugging FC link bundle debugging: debugging bundle // Open FC link bundle debugging ============================================================================ Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice.the only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services.nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.