HP 5920 series Configuration Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. 5920
  6. Configuration manual
HP 5920 series Configuration Manual

HP 5920 series Configuration Manual

Hide thumbs Also See for 5920 series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Configuration Manual
HP 5920 & 5900 Switch Series
FCoE

Configuration Guide

Part number: 5998-3375
Software version: Release2207
Document version: 6W100-20121130

Advertisement

Table of Contents
loading

Related Manuals for HP 5920 series

Summary of Contents for HP 5920 series

  • Page 1: Configuration Guide

    HP 5920 & 5900 Switch Series FCoE Configuration Guide Part number: 5998-3375 Software version: Release2207 Document version: 6W100-20121130...
  • Page 2 The only warranties for HP 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.

  • Page 3: Table Of Contents

    Contents FCoE overview ····························································································································································· 1   Storage area network ······················································································································································· 1   FC SAN ·············································································································································································· 1   FC protocol ········································································································································································ 2   Basic concepts ·························································································································································· 2   Communication flow ················································································································································ 3   VSAN ········································································································································································· 4   FC zone ····································································································································································· 4  ...
  • Page 4 Configuring a domain ID for a switch ························································································································· 24   Configuring the mapping between the N_Port WWN and the FC address ··························································· 25   Configuring the fabric timers ········································································································································ 25   Configuring the fabric timers in system view ······································································································ 25  ...
  • Page 5 Configuration procedure ······································································································································ 47   Verifying the configurations ································································································································· 48   FSPF configuration example ·········································································································································· 49   Network requirements ··········································································································································· 49   Configuration procedure ······································································································································ 50   Verifying the configurations ································································································································· 51   Configuring FC zones ················································································································································ 53   Overview ········································································································································································· 53  ...
  • Page 6 Appendix A Fabric address assignment ······················································································································ 82   Appendix B Well-known fabric addresses ·················································································································· 82   Support and other resources ····································································································································· 84   Contacting HP ································································································································································ 84   Subscription service ·············································································································································· 84   Related information ························································································································································ 84   Documents ······························································································································································ 84  ...

  • Page 7: Fcoe Overview

    FCoE overview Storage area network According to the Storage Networking Industry Association dictionary, "a storage area network (SAN) is any high-performance network whose primary purpose is to enable disk devices to communicate with computer systems and with each other." A SAN enables the universal connectivity of servers and disk devices. Compared to the conventional client/server computer system, a SAN allows the servers to share data and directly access data created by one another without having to copy it, improves storage scalability, and centralizes the management of data backup, access, and security.

  • Page 8: Fc Protocol

    FC protocol The servers, FCF switches, and disk devices in an FC SAN must all support FC. Basic concepts The World Wide Name (WWN) is a 64-bit address that identifies a fabric or an entity (such as an FCF switch, node, or port) in an FC SAN. The upper-layer protocol of FC uses WWNs for communication. Each entity has a factory-assigned globally unique WWN.

  • Page 9: Communication Flow

    Figure 3 Port modes The interface on a node is called an "N_Port." An FCF switch provides the following types of ports: F_Port—Connects to an N_Port or an NP_Port on another FCF switch. E_Port—Connects to an E_Port on another FCF switch. NP_Port—Connects to an F_Port on another FCF switch.

  • Page 10: Vsan

    After the server obtains the FC address of the disk device, the server can send FC frames (with the FC address of the disk device as the destination FC address) to the FCF switch nearby. When the FCF switch receives the FC frame from the server, it queries its FIB table for a data forwarding path according to the destination FC address, and forwards the FC frame to the next-hop FCF switch.

  • Page 11: Basic Concepts

    Figure 5 FCoE for I/O consolidation As shown in Figure 5, in the traditional network, the server is connected to the LAN through an Ethernet interface and to the SAN through an FC interface. In the FCoE network, the server is connected to the FCoE-capable FCF switch, and then the FCF switch is connected to the LAN through an Ethernet interface and to the SAN through an FC interface.

  • Page 12: How Fcoe Works

    You can connect either an ENode or an FCF switch to a VFC interface. VFC interfaces support E mode, F mode (default), and NP mode. The virtual node (VN) interface is a logical interface on an ENode to simulate the function of a physical FC interface.
  • Page 13 NOTE: This section describes how FCoE works only on the FCF switch, rather than on the ENode. Procedure for receiving and sending FC frames over Ethernet An FC frame is transmitted over Ethernet using the following workflow: • FIP establishes a virtual link between the VFC interface of the FCF switch and the VN interface of the ENode or between VFC interfaces of two FCF switches.

  • Page 14: Fcoe Modes

    If it is bound, the switch checks whether the FCoE MAC address matches the bound FCoE MAC address. If they match, it replies with a solicited Discovery Advertisement, whose fcf priority field carries the FCF priority of the VFC interface. If they do not match, it discards the Discovery Solicitation.

  • Page 15: Npv Mode

    Figure 10 FCF network diagram In an FCoE environment as shown in Figure 10, different from a pure FC network, the ENode and FCF switch communicate over Ethernet interfaces on a lossless Ethernet network. The FCoE virtual link between the ENode and FCF switch connects a VN interface to a VFC interface, and the FCoE virtual link between FCF switches connects two VFC interfaces.
  • Page 16 FC-SW-5, Fibre Channel - Switch Fabric - 5 • • FC-LS-2, Fibre Channel - Link Services - 2 FC-GS-6, Fibre Channel - Generic Services - 6 • FC-BB-5, Fibre Channel - Back Bone – 5 •...

  • Page 17: Fcoe Configuration Guidelines

    FCoE configuration guidelines The switch supports FCoE only when operating in advanced mode. For more information about system operating modes, see Fundamentals Configuration Guide. FCoE features supported by different FCoE modes The switch supports two FCoE modes: FCF mode and NPV mode. Each mode has different features as shown in Table 1.

  • Page 18: Configuring Vfc Interfaces And Fip

    Configuring VFC interfaces and FIP VFC interfaces and FIP configuration task list Tasks at a glance (Required.) Configuring a VFC interface (Required.) Enabling FCoE for a VLAN and mapping a VSAN to the VLAN (Optional.) Configuring the FC-MAP value (Optional.) Configuring the FKA advertisement period value (Optional.) Configuring the FCF priority...

  • Page 19: Enabling Fcoe For A Vlan And Mapping A Vsan To The Vlan

    Step Command Remarks (Optional.) Restore the default settings for the VFC default interface. Bring up the VFC interface. undo shutdown By default, a VFC interface is up. Enabling FCoE for a VLAN and mapping a VSAN to the VLAN When you use a VFC interface to transmit packets, the Ethernet interface bound to the VFC interface may allow multiple VLANs.

  • Page 20: Configuring The Fka Advertisement Period Value

    FKA advertisement period to be greater than 90 seconds. In normal cases, use the default FKA advertisement period value (8 seconds). In the case of an • active/standby switchover or ISSU reboot on an IRF member switch with subordinate switches, HP...

  • Page 21: Configuring The Fcf Priority

    Discovery Advertisements or keepalive frames for a period of time. To prevent the peer from deleting the virtual link for failing to receive an unsolicited Discovery Advertisement and avoid service interruption, HP recommends that you set the FKA advertisement period to a value between 300 and 600 seconds.

  • Page 22: Configuring The Vfc Interface Fcf Priority

    Step Command Remarks The default setting is 128. Configure the system fcoe global fcf-priority The configuration takes effect on all VFC FCF priority. priority interfaces in F mode. Configuring the VFC interface FCF priority Step Command Remarks Enter system view. system-view Enter VFC interface interface vfc...

  • Page 23: Configuration Procedure

    Figure 12 Network diagram If the FCF switch is connected to the converged network adapter (CNA) of the server or storage device, PFC and DCBX should be configured additionally on the physical interfaces. For information about configuring PFC and DCBX, see Layer 2—LAN Switching Configuration Guide. Configuration procedure This section describes the configurations for VFC interfaces and FIP on the FCF switch.
  • Page 24 [SwitchA] interface ten-gigabitethernet1/0/2 [SwitchA-Ten-GigabitEthernet1/0/2] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/2] port trunk permit vlan 20 [SwitchA-Ten-GigabitEthernet1/0/2] quit # Enable FCoE for VLAN 20 and map it to VSAN 10. [SwitchA] vlan 20 [SwitchA-vlan20] fcoe enable vsan 10 Configure Switch B: # Create VSAN 10 and configure Switch B to operate in FCF mode. <SwitchB>...

  • Page 25: Setting Up A Fabric

    Setting up a fabric Overview A fabric transmits data for servers and disk devices. When setting up a fabric, you must assign a domain ID to each FCF switch in the fabric and assign an FC address to each node connected to the fabric. You can build a fabric through one of the following modes: •...

  • Page 26: Domain Id Assignment

    replaces the locally-record principal switch information with the principal switch information recorded in the packet, and notifies the other switches. Finally, all switches in the network make an agreement on which switch is the principal switch. When the PSST times out, if the locally-recorded principal switch information is the local switch, the switch becomes the principal switch.

  • Page 27: Fc Address Assignment

    Area_ID and Port_ID to the N_Port. Fabric setup configuration task list When you set up a fabric, HP recommends that you use the same building mode (dynamic or static) for all switches in the fabric and then perform the following configurations depending on your building mode.

  • Page 28: Building A Fabric Dynamically

    Tasks at a glance Remarks (Optional.) Configuring the fabric timers Building a fabric dynamically Tasks at a glance Remarks (Required.) Configuring VFC interfaces and FIP (Required.) Enabling or disabling the fabric configuration To dynamically build a fabric, you must function enable the fabric configuration function.

  • Page 29: Setting A Fabric Name

    Setting a fabric name The fabric name configured takes effect only on a statically-built fabric. You must configure the same fabric name for all switches in a VSAN. To set a fabric name: Step Command Remarks Enter system view. system-view Enter VSAN view.

  • Page 30: Configuring The Allowed Domain Id List

    If the runtime domain ID for a switch is beyond the new allowed ID list, the configuration will also fail. HP recommends that you specify the same allowed domain ID list for the member switches of a VSAN. To configure the allowed domain IDs for a switch:...

  • Page 31: Configuring The Mapping Between The N_Port Wwn And The Fc Address

    Step Command Remarks Configure a domain ID for domain-id domain-id { preferred | By default, the domain ID of a switch is the switch. static } 0 and is of the preferred type. Configuring the mapping between the N_Port WWN and the FC address If you bind the WWN of an N_Port to an FC address, when the N_Port requests an FC address, the switch assigns the bound FC address to it.

  • Page 32: Configuring The Fabric Timers In Vsan View

    Step Command Remarks By default, the error detection Configure the global error fc timer error-detect value timeout period is 2000 detection timeout period. milliseconds. Configure the global By default, the resource allocation resource allocation timeout fc timer resource-allocation value timeout period is 10000 period.

  • Page 33: Configuring The Auto Fabric Reconfiguration Function

    The system automatically performs a non-disruptive reconfiguration if the principal switch information of the two fabrics is different and the domain ID lists are not empty or overlapping. You can manually initiate a disruptive reconfiguration to trigger the fabric reconfiguration if ports are isolated and priority values of switches are modified.

  • Page 34: Static Fabric Building Configuration Example

    Task Command Display the domain information of the specified display fc domain [ vsan vsan-id ] VSAN. Display the list of domain IDs dynamically allocated in display fc domain-list [ vsan vsan-id ] the specified VSAN. display fc timer [ distributed-services | error-detect | Display fabric timers.

  • Page 35: Verifying The Configurations

    [SwitchB-vsan1] undo domain configure enable # Configure a name for the fabric. [SwitchA-vsan1] fabric-name 11:11:11:11:11:11:11:11 # Configure the domain ID as 2. [SwitchB-vsan1] domain-id 2 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y Verifying the configurations Verify the configurations on Switch A.

  • Page 36: Dynamic Fabric Building Configuration Example

    Principal switch running time information: Priority: 128 No interfaces available. The output shows that the domain configuration is complete and that the runtime domain ID of Switch B is 2. Dynamic fabric building configuration example Network requirements As shown in Figure 15, use the dynamic approach to build a fabric.

  • Page 37: Verifying The Configurations

    [SwitchA-Vfc1] fc mode e [SwitchA-Vfc1] port trunk vsan 1 [SwitchA-Vfc1] quit # Configure other physical-to-virtual interface bindings and VLAN-to-VSAN mappings in the same way configure the preceding ones. (Details not shown.) Configure Switch B: # Configure physical-to-virtual interface bindings and VLAN-to-VSAN mappings in the same way as you configure them on Switch A.
  • Page 38 Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1A:1A Fabric name: 48:33:43:2d:46:43:1B:1B Priority: 128 Domain ID: 11 Configuration information: Domain configure: Enabled Domain auto-reconfigure: Disabled Fabric name: 48:33:43:2d:46:43:1A:1A Priority: 128 Domain ID: 11 (preferred) Principal switch running time information: Priority: 1 Path Interface Upstream...

  • Page 39: Configuring Vsan

    Configuring VSAN Overview The virtual storage area network (VSAN) technology breaks a physical SAN into multiple VSANs, and provides more secure, reliable, and flexible services. Devices in a VSAN cannot get information about any other VSAN and devices in any other VSAN. Each VSAN performs the following operations independently: selecting a principal switch, assigning domain IDs, running routing protocols, maintaining routing table and FIB table, and providing services.

  • Page 40: Creating A Vsan

    Figure 16 Trunk VSAN network VSAN 1 VSAN 1 N_Port N_Port Disk A Server A FC Fabric F_Port F_Port E_Port E_Port F_Port F_Port FC switch A FC switch B Server B Disk B N_Port N_Port VSAN 2 VSAN 2 During the transmission process, VFT_Headers are added to and removed from the frames. A switch can use the same physical interface to support multiple VSANs.

  • Page 41: Displaying And Maintaining Vsan

    Step Command Remarks Enter system view. system-view Enter VFC interface view. interface vfc interface-number By default, a VFC interface does not Assign the VFC interface to belong to any VSAN as a trunk port. the specified VSANs as a trunk port so that the port trunk vsan vsan-id-list When you assign a VFC interface to interface allows the specified...

  • Page 42: Configuration Procedure

    Configure the two interfaces connecting FCF switch Switch A to the servers to operate in F mode, • and assign the two interfaces as trunk ports to VSAN 10 and VSAN 20, respectively. Configure the three interfaces connecting FCF switch Switch B to the disk devices to operate in F •...

  • Page 43: Verifying The Configurations

    Configure Switch B in the same way as you configure Switch A. (Details not shown.) Verifying the configurations Verify the configurations on Switch A by displaying member interfaces of all VSANs. [SwitchA- Vfc100] display vsan port-member VSAN 1: Access Ports: Trunk Ports: VSAN 10: Access Ports:...

  • Page 44: Configuring Fc Routing And Forwarding

    Configuring FC routing and forwarding Overview Routing and forwarding in an FC SAN is achieved through FCF switches. When an FCF switch receives a packet, an FCF switch selects an optimal route based on the destination address and forwards the packet to the next FCF switch in the path until the packet reaches the last FCF switch, which forwards the packet to the destination node.

  • Page 45: Direct Routes

    Protocol—Protocol type, which can be DIRECT (direct routes), STATIC (static routes), or FSPF (FSPF • routes). Preference—There might be direct routes, static routes, and FSPF routes to the same destination. All • of these types of routes are assigned preferences. Direct routes have a preference of 0, static routes have a preference of 10, and FSPF routes have a preference of 20.

  • Page 46: Fspf Routes

    However, the static routes cannot automatically adapt to network topology changes. When the network fails or the network topology changes, the routes might fail to be reachable, and the network is interrupted. In this case, you must manually modify the static routes. Static routes support equal-cost routes.

  • Page 47: Configuring Static Routes For Fc

    After receiving an LSU, a switch needs to acknowledge its LSR with an LSA. Otherwise, the neighboring switch retransmits the LSR. How FSPF works FSPF works as follows: The switch periodically sends hello packets to establish neighbor relationships with other switches. After establishing neighbor relationships, the switches synchronize LSDBs by exchanging all LSRs in their respective LSDBs.

  • Page 48: Fspf Configuration Task List

    FSPF configuration task list Tasks at a glance Change FSPF parameters for a VSAN in VSAN view: • (Required.) Enabling FSPF • (Optional.) Configuring the shortest SPF calculation interval • (Optional.) Configuring the minimum LSR receiving interval • (Optional.) Configuring the minimum LSR refresh interval (Optional.) Change FSPF parameters for an interface in E_Port interface view: •...

  • Page 49: Configuring The Minimum Lsr Receiving Interval

    Configuring the minimum LSR receiving interval The minimum LSR receiving interval specifies the time between receiving LSRs in a VSAN. Any LSR instances of the same LSR received within this time are dropped. This helps avoid frequent SPF calculations caused by LSDB updating. To configure the minimum LSR receiving interval: Step Command...

  • Page 50: Configuring The Hello Interval For An Interface

    Configuring the hello interval for an interface The hello interval specifies the time between the hello packets sent periodically by the switch to discover and maintain neighbor relationships. NOTE: The configured hello interval must be smaller than the dead interval and must be the same at the two ends of the link.

  • Page 51: Disabling Fspf For An Interface

    Step Command Remarks Enter VFC interface view. interface vfc interface-number Configure the LSR retransmission fspf retransmit-interval value interval for the VFC interface in The default setting is 5 seconds. vsan vsan-id a specified VSAN. Disabling FSPF for an interface With FSPF enabled, an interface can participate in SPF calculation. To avoid SPF calculations on an interface, disable FSPF on the interface.

  • Page 52: Displaying And Maintaining Fc Routing And Forwarding

    Displaying and maintaining FC routing and forwarding Execute display commands in any view. Task Command display fc routing-table [ vsan vsan-id ] [ statistics | verbose ] Display FC routing table information. display fc routing-table vsan vsan-id fc-id [ mask | mask-length ] [ verbose ] Display FC FIB table information.

  • Page 53: Configuration Procedure

    Configuration procedure Configure Switch A: # Configure Switch A to operate in FCF mode and bind interface VFC 100 to interface Ten-GigabitEthernet 1/0/1. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] interface Vfc 100 [SwitchA-Vfc100] bind interface Ten-GigabitEthernet1/0/1 # Configure interface VFC 100 to operate in E mode and assign it to VSAN 1 as a trunk port. [SwitchA-Vfc100] fc mode f [SwitchA-Vfc100] port trunk vsan 1 [SwitchA-Vfc100] quit...

  • Page 54: Verifying The Configurations

    [SwitchB-vsan1] domain-id 2 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchB-vsan1] quit # Enable FCoE for VLAN 10 and bind VLAN 10 to VSAN 1. [SwitchB] vlan 10 [SwitchB-vlan10] fcoe enable vsan 1 [SwitchB-vlan10] quit # Configure two static routes.

  • Page 55: Fspf Configuration Example

    0xfffffa/24 DIRECT InLoop0 0xfffffc/24 DIRECT InLoop0 0xfffffd/24 DIRECT InLoop0 # Display the FC routing table in VSAN 1 on Switch B. [SwitchB-vsan1] display fc routing-table vsan 1 Routing Table: VSAN 1 Destinations : 6 Routes : 6 Destination/mask Protocol Preference Cost Interface 0x010000/8...

  • Page 56: Configuration Procedure

    Figure 19 Network diagram Configuration procedure Configure Switch A: # Configure Switch A to operate in FCF mode and bind interface VFC 100 to interface Ten-GigabitEthernet 1/0/1. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] interface Vfc 100 [SwitchA-Vfc100] bind interface Ten-GigabitEthernet1/0/1 [SwitchA-Vfc100] fc mode e [SwitchA-Vfc100] port trunk vsan 2 [SwitchA-Vfc100] quit...

  • Page 57: Verifying The Configurations

    # Enable the fabric configuration function. [SwitchB] vsan 2 [SwitchB-vsan2] domain configure enable # Configure the domain ID as 2. [SwitchB-vsan2] domain-id 2 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchB-vsan2] quit # Enable FCoE for VLAN 10 and bind VLAN 10 to VSAN 2. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 2 [SwitchA-vlan10] quit...
  • Page 58 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 0.247/0.430/1.102 ms The output shows that Switch A can reach Switch B.

  • Page 59: Configuring Fc Zones

    Configuring FC zones Overview The VSAN technology divides a physical SAN into multiple VSANs, which are separated from one another, and provides more secure, reliable, and flexible services. A VSAN, however, cannot perform access control over the servers and disk devices (or the N_Ports) connected to a fabric. N_Ports in the same VSAN can access one another only if these N_Ports register name services.
  • Page 60 Each VSAN can have multiple zone sets, each zone set can have multiple zones, and each zone • can have multiple zone members. To facilitate configuration, zone membership configuration supports use of zone aliases. A zone • alias is a set of N_Ports, which can be considered as a whole. You can add common zone members in multiple zones to a zone alias, and call the zone alias in different zones to simplify configuration.

  • Page 61: Distributing Zones

    Default zone The N_Ports in zones of the active zone set are part of the active zone set. Registered N_Ports that are not in the active zone set automatically become part of the default zone. If members of the default zone are allowed to access each other, the default zone can be considered to be part of the active zone set, and it participates in access control among N_Ports.
  • Page 62 Figure 22 Distribution process The distribution process is as follows: The manager switch obtains the status of each managed switch through an ACA request, which carries the fabric-wide list of domain IDs (addresses of all switches in the fabric) known to the manager switch.

  • Page 63: Zone Merge

    After receiving the RCA request, the managed switch releases its change authorization state and replies with an ACC packet. The manager switch releases its change authorization state after receiving ACC packets from all managed switches. NOTE: [1] This actually requires the routing information across the fabric to be correct and consistent and •...
  • Page 64 Figure 23 Zone merge process between two switches The zone merge process is as follows: Switch A and Switch B are new neighbors to each other. Suppose that Switch A first initiates a merge to Switch B: Switch A sends an MRRA request carrying the size of its data to be merged to Switch B. After receiving the MRRA request, Switch B determines whether to accept the merge according to its local data size.

  • Page 65: Access Control

    NOTE: Consistent active zone sets among switches can be achieved by a merge. Consistent zone databases achieved after a merge, however, require all participating switches to be configured with complete merge. Zone merge rules Table 3 Zone merge rules Local database Neighbor database Merge status Merge result...

  • Page 66: Configuring Zone Aliases

    Tasks at a glance (Required.) Activating a zone set and distributing it to the entire fabric (Optional.) Triggering a complete distribution (Optional.) Renaming zone aliases, zones, and zone sets (Optional.) Copying zone aliases, zones, and zone sets (Optional.) Deleting the zone database NOTE: •...

  • Page 67: Configuring Zone Sets

    Configuring zone sets You can configure a maximum of 128 zone sets for all VSANs on a switch. To configure a zone set: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Create a zone set and If the zone set has been created, zoneset name zoneset-name enter its view.

  • Page 68: Activating A Zone Set And Distributing It To The Entire Fabric

    Activating a zone set and distributing it to the entire fabric You can activate a zone set as the active zone set on a switch, distribute the active zone set to the entire fabric, and implement access control through the active zone set. The modifications to the active zone set do not take effect until reactivation.

  • Page 69: Renaming Zone Aliases, Zones, And Zone Sets

    Renaming zone aliases, zones, and zone sets Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id The zone alias to be renamed must zone-alias rename old-name have been created, and the new Rename a zone alias. new-name zone alias must not have been created.

  • Page 70: Displaying And Maintaining Fc Zones

    Step Command Enter system view. system-view Enter VSAN view. vsan vsan-id Delete the zone database. delete zone database all Displaying and maintaining FC zones Execute display commands in any view. Task Command display zone-alias [ [ name zone-alias-name ] vsan Display zone alias information.

  • Page 71: Configuration Considerations

    Figure 24 Network diagram Configuration considerations To meet the preceding requirements, divide VSAN 1 into three zones as follows: Zone 1 consists of Server A. • Zone 2 consists of Server B and Disks A, B, and C. • Zone 3 consists of Server C and Disks B and C. •...

  • Page 72: Verifying The Configurations

    [SwitchA-vsan1-zone-Zone1] member fcid 010001 [SwitchA-vsan1-zone-Zone1] quit [SwitchA-vsan1] zone name Zone2 [SwitchA-vsan1-zone-Zone2] member fcid 010002 [SwitchA-vsan1-zone-Zone2] member pwwn 11:22:33:44:55:66:77:88 [SwitchA-vsan1-zone-Zone2] member zone-alias Alias1 [SwitchA-vsan1-zone-Zone2] quit [SwitchA-vsan1] zone name Zone3 [SwitchA-vsan1-zone-Zone3] member fcid 010003 [SwitchA-vsan1-zone-Zone3] member zone-alias Alias1 [SwitchA-vsan1-zone-Zone3] quit # Create zone set Zoneset 1 and add Zones 1, 2, and 3 as its members. [SwitchA-vsan1] zoneset name Zoneset1 [SwitchA-vsan1-zoneset-Zoneset1] member Zone1 [SwitchA-vsan1-zoneset-Zoneset1] member Zone2...
  • Page 73 pwwn 11:22:33:44:55:66:77:88 zone-alias Alias1 fcid 0x010004 pwwn 22:33:44:55:66:77:88:99 # Display the zone or zone alias to which 010004 (FC ID type) belongs. <SwitchB> display zone member fcid 010004 fcid 0x010004 VSAN 1: zone-alias Alias1 zone Zone2 zone Zone3 # Display information about the active zone set in VSAN 1. <SwitchB>...

  • Page 74: Configuring Npv

    Configuring NPV Overview NPV enables an FC SAN to accommodate more than 239 switches. NPV switches forward traffic from nodes to the core switch. Figure 25 shows a typical NPV network diagram. Figure 25 NPV network diagram NOTE: An NPV switch must be directly connected to the core switch. Downlink interface and downlink A downlink interface, also known as a server interface, is an interface through which an NPV switch connects to a node.

  • Page 75: Downlink-To-Uplink Interface Mappings

    Downlink-to-uplink interface mappings NPV switches automatically map downlink interfaces to uplink interfaces. Before a downlink interface is brought up, the NPV switch maps it to the uplink interface with the minimum load among all operational uplink interfaces. The load here indicates the number of downlink interfaces mapped to the uplink interface.

  • Page 76: Configuring Downlink Interfaces

    To configure an uplink interface: Step Command Remarks Enter system view. system-view Enter VFC interface interface vfc This interface is connected to the core switch. view. interface-number Configure the VFC By default, a VFC interface on an NPV switch interface to operate fc mode np operates in F mode.

  • Page 77: Initiating A Disruptive Load-Balancing Process

    Step Command Remarks npv traffic-map server-interface Configure a interface-type interface-number downlink-to-uplink By default, no mapping is configured. external-interface interface-type interface mapping. interface-number Initiating a disruptive load-balancing process CAUTION: This feature redistributes downlink traffic across all uplink interfaces for better load balancing, but it causes traffic interruption.

  • Page 78: Configuration Procedure

    Figure 26 Network diagram Configuration procedure # Configure Switch A to operate in NPV mode. <SwitchA> system-view [SwitchA] fcoe-mode npv # Create VSAN 10 and VLAN 20. <SwitchA> system-view [SwitchA] vsan 10 [SwitchA-vsan10] quit [SwitchA] vlan 20 [SwitchA-vlan20] quit # Configure interface Ten-GigabitEthernet 1/0/1 to allow VLAN 20. [SwitchA] interface Ten-GigabitEthernet1/0/1 [SwitchA-Ten-GigabitEthernet1/0/1] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/1] port trunk permit vlan 20...

  • Page 79: Verifying The Configurations

    [SwitchA-Vfc1] quit # Create interfaces VFC 1 and VFC 2, bind them to interfaces Ten-GigabitEthernet 1/0/2 and Ten-GigabitEthernet 1/0/3, respectively, and configure them to allow VSAN 10. [SwitchA] interface vfc 2 [SwitchA-Vfc2] bind interface Ten-GigabitEthernet1/0/2 [SwitchA-Vfc2] port trunk vsan 10 [SwitchA-Vfc2] quit [SwitchA] interface vfc 3 [SwitchA-Vfc3] bind interface Ten-GigabitEthernet1/0/3...
  • Page 80 Number of Server Interfaces: 2 # Display the traffic mapping information. [SwitchA] display npv traffic-map NPV traffic map information of VSAN 1: Server Interface External Interface vfc 2 Vfc 1 vfc 3 Vfc 1...

  • Page 81: Configuring Fc Ping

    Configuring FC ping Overview In an FC SAN, use the fcping command to check whether a destination address is reachable and to test network connectivity. The FC ping works as follows: the source device sends an echo request to the destination device and determines whether the destination is reachable based on whether it receives an echo reply.
  • Page 82 # Configure Switch A to operate in FCF mode. Create interface VFC 100, bind it to interface Ten-GigabitEthernet 1/0/2, configure it to operate in E mode, and assign it to VSAN 1 as a trunk port. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] interface Vfc 100 [SwitchA-Vfc100] bind interface Ten-GigabitEthernet1/0/2 [SwitchA-Vfc100] fc mode f...

  • Page 83: Verifying The Configurations

    [SwitchA-vlan10] quit # Configure a static route. [SwitchB-vsan1] fc route-static 010000 8 Vfc200 Verifying the configurations Check whether Switch A and Switch B can reach each other. # On Switch A, use the fcping command to ping Switch B and check whether Switch B is reachable. [SwitchA-vsan1] fcping fcid fffc02 vsan 1 FCPING fcid 0xfffc02: 128 data bytes, press CTRL_C to break.

  • Page 84: Configuring Fc Tracert

    Configuring FC tracert Overview In an FC SAN, use the fctracert command to obtain bidirectional routing information between source and destination, and check the network connectivity. You can use this feature to identify failed nodes and test network connectivity. FC tracert comprises two processes: Uplink process—In this process, beginning from the source, each switch along the path to the •...

  • Page 85: Configuration Procedure

    Switch A adds its uplink path information (including its WWN and domain ID) to the STR request packet and sends the packet to the next hop Switch B. After receiving the packet, Switch B replies with an STR ACC packet to Switch A. Switch B adds its uplink path information to the received STR packet and sends it to the destination switch, Switch C.
  • Page 86 [SwitchA-vsan1] domain-id 1 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y # Enable FSPF globally. SwitchA-vsan1] fspf enable Configure Switch B: # Enable the fabric configuration function and configure Switch B to operate in FCF mode. <SwitchB>...
  • Page 87 20:00:00:05:30:00:18:db(0xfffc02) Fctracert uncompleted: no route to destination port. The output shows that Switch A can reach Switch B, but Switch B cannot reach Switch C. Therefore, you can use the display fc routing-table command on Switch B to see whether there is a route to Switch C.

  • Page 88: Appendixes

    Appendixes Appendix A Fabric address assignment Table 4 Fabric address assignment FC_ID Description Undefined (when an N_Port uses FLOGI to request for an address, an 0x000000 all-zero FC ID is used). 0x000001–0x00FFFF Reserved. 0x010000–0xEFFFFF N_Port address. 0xF00000–0xFFF9FF Reserved. 0xFFFA00–0xFFFA0F Reserved for internal loopback. 0xFFFA10–0xFFFA1F Reserved for external loopback.
  • Page 89 FC_ID Description 0xFFFFFA Management services. 0xFFFFFB Time services. 0xFFFFFC Path services (name services).

  • Page 90: Support And Other Resources

    Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...

  • Page 91: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
  • Page 92 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 93: Index

    Index access FCoE fabric N_Port-WWN-to-FC address FC access control, 59 mapping, 25 activating FCoE fabric resource allocation timeout timer, 25 FCoE FC zone set, 62 FCoE fabric switch domain IDs, 24 active FCoE FC default zone policy, 61 FC zone database active zone set, 54 FCoE FC forwarding, 38 address FCoE FC ping, 75...
  • Page 94 FCoE fabric N_Port-WWN-to-FC address FCoE load balancing process initiation, 71 mapping configuration, 25 NPV load balancing, 69 FCoE fabric name setting, 23 distributed service timeout timer, 25 FCoE fabric principal switch selection, 19 distributing FCoE fabric setup, 19, 21 FCoE FC zone set to fabric, 62 FCoE fabric switch domain ID configuration, 24 domain FCoE fabric switch priority setting, 23...
  • Page 95 domain ID assignment, 20 zone distribution, 55 dynamic fabric building configuration, 30 zone distribution process, 55 error detection timeout timer, 25 zone distribution triggering methods, 55 FC access control, 59 zone merge, 57 FC address assignment, 21 zone merge process, 57 FC interface configuration, 22 zone merge rules, 59 FC zone distribution, 55...
  • Page 96 FSPF shortest calculation interval NPV uplink interface configuration, 69 configuration, 42 procedure of receiving and sending FC frame, 7 FC ping configuration, 75 protocols and standards, 9 FC protocol, 2 static fabric building configuration, 28 FC routing configuration, 38 VFC interface, 5 FC SAN, 1 VN interface, 5 FC static route configuration, 41, 46...
  • Page 97 GR Restarter configuration, 45 FC FSPF interface LSR retransmission interval how it works, 41 configuration, 44 interface cost configuration, 43 FC FSPF LSR, 40 interface dead interval configuration, 44 FC FSPF min LSR receiving interval configuration, interface hello interval configuration, 44 interface LSR retransmission interval configuration, FC FSPF min LSR refresh interval configuration, 43 maintaining...
  • Page 98 FC FSPF packet type, 40 FCoE interface modes, 2 FC FSPF routes, 40 FCoE NPV disruptive load balancing, 69 FSPF shortest calculation interval FCoE NPV disruptive load balancing process configuration, 42 initiation, 71 FC protocol, 2 FCoE NPV downlink, 68 FC SAN, 1 FCoE NPV downlink interface, 68 FC static route configuration, 41...
  • Page 99 FCoE VFC interface, 5 FC zone merge process, 57 FCoE VN interface, 5 FC zone merge rules, 59 FCoE description, 4 configuration, 68, 69, 71 FCoE dynamic fabric building configuration, 30 displaying, 71 FCoE fabric address assignment, 82 disruptive load balancing, 69 FCoE fabric setup, 19, 21 disruptive load balancing process initiation, 71 FCoE FC zone, 4...
  • Page 100 configuring FCoE fabric error detection timeout maintaining FC routing, 46 timer, 25 maintaining VFC interfaces and FIP, 16 configuring FCoE fabric N_Port-WWN-to-FC mapping FCoE VSAN to VLAN, 13 address mapping, 25 renaming FCoE FC zone sets, 63 configuring FCoE fabric resource allocation renaming FCoE FC zones, 63 timeout timer, 25 setting FCoE fabric name, 23...
  • Page 101 FC zone merge rules, 59 FCoE FC zone copying, 63 FCoE FC default zone policy configuration, 61 FCoE FC zone database deletion, 63 FCoE FC forwarding configuration, 38 FCoE FC zone distribution configuration, 61 FCoE FC ping configuration, 75 FCoE FC zone merge type configuration, 61 FCoE FC routing configuration, 38 FCoE FC zone renaming, 63 FCoE FC tracert configuration, 78, 79...
  • Page 102 FCoE NPV mode, 9 FCoE dynamic fabric building configuration, 30 FCoE static fabric building configuration, 28 FCoE fabric address assignment, 82 FCoE VSAN configuration, 33, 35 FCoE fabric configuration enable/disable, 22 FCoE well-known fabric addresses, 82 FCoE fabric domain ID assignment, 20 VFC interfaces and FIP configuration, 12, 16 FCoE fabric FC address assignment, 21 setting...
  • Page 103 FCoE NPV downlink-to-uplink interface mapping FKA advertisement period, 14 configuration, 70 VFC interface FCoE NPV mode, 9 FKA advertisement period, 14 FCoE NPV uplink, 68 VFC interfaces and FIP FCoE NPV uplink interface, 68 configuration, 12, 16 FCoE NPV uplink interface configuration, 69 displaying, 16 FCoE static fabric building configuration, 28 maintaining, 16...
  • Page 104 FC routing configuration, 38 FCoE NPV configuration, 68, 69, 71 FC SAN, 1 FCoE NPV disruptive load balancing, 69 FC tracert configuration, 78, 79 FCoE NPV downlink, 68 FC triggering zone set distribution, 62 FCoE NPV downlink interface, 68 FC zone alias configuration, 60 FCoE NPV downlink-to-uplink interface mapping, FC zone configuration, 53, 59, 60, 64 FC zone copying, 63...

This manual is also suitable for:

5900 series

Table of Contents