1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. 6125XLG
  6. Configuration manual

HP 6125XLG Configuration Manual

Blade switch fcoe configuration guide
Hide thumbs Also See for 6125XLG:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
HP 6125XLG Blade Switch
FCoE

Configuration Guide

Part number: 5998-3726
Software version: Release 2306
Document version: 6W100-20130912

Advertisement

Table of Contents
loading

Related Manuals for HP 6125XLG

Summary of Contents for HP 6125XLG

  • Page 1: Configuration Guide

    HP 6125XLG Blade Switch FCoE Configuration Guide Part number: 5998-3726 Software version: Release 2306 Document version: 6W100-20130912...
  • Page 2 HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • 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 the fabric timers ········································································································································ 27   Configuring the fabric timers in system view ······································································································ 28   Configuring the fabric timers in VSAN view ······································································································ 28   Configuring the fabric reconfiguration ························································································································ 28   Configuring the auto fabric reconfiguration function ························································································ 29  ...
  • Page 5 Static FC routing configuration example ····················································································································· 63   Network requirements ··········································································································································· 63   Configuration procedure ······································································································································ 63   Verifying the configurations ································································································································· 66   FSPF configuration example ·········································································································································· 67   Network requirements ··········································································································································· 67   Configuration procedure ······································································································································ 67   Verifying the configurations ·································································································································...
  • Page 6 Configuration procedure ······································································································································ 96   Verifying the configurations ································································································································· 97   Configuring FC tracert ··············································································································································· 99   Overview ········································································································································································· 99   Configuration procedure ············································································································································· 100   FC tracert configuration example ······························································································································· 100   Network requirements ········································································································································· 100   Configuration procedure ···································································································································· 100  ...

  • Page 7: Fcoe Overview

    FCoE overview The switch supports FCoE only when operating in advanced mode (the default). For more information about system operating modes, see Fundamentals Configuration Guide. HP recommends that you set the delay for the IRF ports to report a link down event as 0 on IRF member devices connected into a ring topology.

  • Page 8: Fc Protocol

    Figure 1 FC SAN networking (1) Point-to-point connection (2) Switched fabric Disk Server FC switch Fabric Server Disk NOTE: • An FC SAN refers to a network comprising FC switches and nodes. A fabric refers to a transmission network comprising FC switches. •...

  • Page 9: Communication Flow

    Figure 2 Structure of an FC address A Domain_ID can uniquely identify an FC switch. Different FC switches in the same fabric have different Domain_IDs. An FC address can uniquely identify an N_Port on a node. Different N_Ports on the same node have different FC addresses.

  • Page 10: Vsan

    Figure 4 FC SAN communication model The following takes a server accessing a disk device as an example to see how data communication occurs in an FC SAN. The server and the disk device use the fabric login (FLOGI) protocol to register with the FC switches, which then assign FC addresses to each directly-connected node.

  • Page 11: Fcoe

    Zoning can solve the preceding problem by dividing a VSAN into zones and adding N_Ports to different zones for different purposes. In this manner, N_Ports in different zones are separated to implement access control. For more information about FC zones, see "Configuring FC zones."...
  • Page 12 Figure 6 FCoE network diagram VFC interface and VN interface A virtual fiber channel (VFC) interface is a logical interface manually created on the FCF switch to simulate the function of a physical FC interface. To use a VFC interface, bind it to a physical Ethernet interface. You can connect either an ENode or an FCF switch to a VFC interface.

  • Page 13: How Fcoe Works

    Figure 7 FPMA composition How FCoE works Figure 8 Block diagrams of the ENode and the FCF switch ENode Virtual link VN interface VFC interface FC layer FC layer Ethernet Ethernet layer layer Ethernet Ethernet interface interface 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...

  • Page 14: Fcoe Modes

    Figure 9 FIP operation ENode (1) Send Discovery Solicitation Learn FCoE MAC address (2) Send solicited Discovery Advertisement (3) Send solicited Discovery Advertisements periodically (4) Send FLOGI request Check FCoE MAC address (5) Send FLOGI LS_ACC (6) Send solicited Discovery Advertisements periodically As shown in Figure...

  • Page 15: Fcf Mode

    FCF mode—A switch operating in this mode is called an FCF switch. Its VFC interfaces support E • mode (E_Port) and F mode (F_Port). NPV mode—A switch operating in this mode is called an N_Port Virtualization (NPV) switch. Its • VFC interfaces support F mode (F_Port) and NP mode (NP_Port).

  • Page 16: Protocols And Standards

    Figure 11 NPV network diagram As shown in Figure 1 1, the NPV switch resides between nodes and the core switch on the edge of the fabric. The core switch is a switch operating in FCF mode. The NPV switch is connected to the nodes through its F_Ports and to the core switch through its NP_Port.

  • Page 17: Configuring An Fcoe Mode

    Configuring an FCoE mode The switch supports FCoE only when operating in advanced mode. For more information about system operating modes, see Fundamentals Configuration Guide. FCoE features supported in 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 Step Command Remarks Display the FCoE mode of This command can be executed in any display fcoe-mode the switch. view.

  • Page 19: 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 20: 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 can allow multiple VLANs.

  • Page 21: Configuring The Fc-Map Value

    Configuring the FC-MAP value The FC-MAP value identifies an FCoE network. Switches in the same FCoE network must have the same FC-MAP value. IMPORTANT: After FC-MAP values are configured, VFC interfaces perform a renegotiation. The same FC-MAP value is required for two VFC interfaces to negotiate successfully. To configure an FC-MAP value: Step Command...

  • Page 22: Configuring The Fcf Priority

    Step Command Remarks Enter system view. system-view Configure an FKA fcoe fka-adv-period advertisement period The default setting is 8 seconds. fka-adv-period value. Configuring the FCF priority The FCF priority includes the VFC interface FCF priority and the system FCF priority, which are used in the following scenarios: •...

  • Page 23: Vfc Interfaces And Fip Configuration Example

    Task Command display interface [ vfc [ interface-number ] ] [ brief Display VFC interface information. [ description ] ] Display FCoE global configuration. display fcoe Clear the statistics for VFC interfaces. reset counters interface [ vfc [ number ] ] VFC interfaces and FIP configuration example Network requirements As shown in...
  • Page 24 [SwitchA] fcoe-mode fcf [SwitchA] vsan 10 [SwitchA-vsan10] quit # Enable LLDP globally. [SwitchA] lldp global enable # Enable LLDP on interface Ten-GigabitEthernet 1/1/5, and enable the interface to advertise DCBX TLVs. [SwitchA] interface ten-gigabitethernet 1/1/5 [SwitchA-Ten-GigabitEthernet1/1/5] lldp enable [SwitchA-Ten-GigabitEthernet1/1/5] lldp tlv-enable dot1-tlv dcbx [SwitchA-Ten-GigabitEthernet1/1/5] quit # Create an Ethernet frame header ACL numbered 4000, and configure two rules to match FCoE frames (protocol type 0x8906) and FIP frames (protocol type 0x8914).
  • Page 25 # Enable interface Ten-GigabitEthernet 1/1/5 to automatically negotiate with its peer to decide whether to enable PFC, enable PFC for 802.1p priority 3, and configure Ten-GigabitEthernet 1/1/5 to trust the 802.1p priority carried in packets. [SwitchA-Ten-GigabitEthernet1/1/5] priority-flow-control auto [SwitchA-Ten-GigabitEthernet1/1/5] priority-flow-control no-drop dot1p 3 [SwitchA-Ten-GigabitEthernet1/1/5] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/1/5] quit # Create interface VFC 1, bind it to interface Ten-GigabitEthernet 1/1/5, and assign it to VSAN...
  • Page 26 # Create interface VFC 2, and configure it to operate in E mode. [SwitchB] interface vfc 2 [SwitchB-Vfc2] fc mode e # Bind interface VFC 2 to interface Ten-GigabitEthernet 1/1/6, and assign it to VSAN 10 as a trunk port. [SwitchB-Vfc2] bind interface ten-gigabitethernet 1/1/6 [SwitchB-Vfc2] port trunk vsan 10 [SwitchB-Vfc2] quit...

  • Page 27: 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: Static mode—You must manually assign domain IDs to all switches in the network, and then each •...

  • Page 28: Domain Id Assignment

    in the packet is higher, or the priority in the packet is the same and the WWN is smaller, the switch 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.

  • Page 29: Fc Address Assignment

    If the downstream switch has been configured with a static domain ID and the static domain ID is different from the one assigned by the principal switch, or if the principal switch notifies the downstream switch that no domain ID can be assigned, the downstream switch isolates its upstream principal link and brings down the relevant interface.

  • Page 30: Building A Fabric Dynamically

    Tasks at a glance Remarks When statically building a fabric, you must (Required.) Configuring a domain ID for a switch manually configure a domain ID for each switch. (Optional.) Configuring the mapping between the N_Port WWN and the FC address (Optional.) Configuring the fabric timers (Optional.)

  • Page 31: Setting A Fabric Name

    Step Command Remarks Enter VSAN view. vsan vsan-id Enable the fabric configuration domain configure enable Enable or disable the function for all function. switches in the VSAN as required. Disable the fabric By default, the fabric configuration function configuration is enabled. undo domain configure enable function.

  • Page 32: Configuring The Allowed Domain Id List

    To set the switch priority: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Configure a priority By default, the priority value of a priority value value for the switch. switch is 128. Configuring the allowed domain ID list Configuring the allowed domain ID list has an effect on switches as follows: Principal switch—Can only assign domains IDs within the allowed domain ID list.

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

    switch if the preferred type is configured. The non-principal switch will isolate the upstream link and refuse other domain IDs assigned by the principal switch if the static type is configured. HP recommends that you configure domain IDs of the same type for all switches in a VSAN. To configure a domain ID for a switch: Step Command...

  • Page 34: Configuring The Fabric Timers In System View

    Configure the timers in VSAN view, and the configuration takes effect for only the VSAN. • If you perform the configuration in both system view and VSAN view, the configuration made in VSAN view applies to the VSAN. Configuring the fabric timers in system view Step Command Remarks...

  • Page 35: Configuring The Auto Fabric Reconfiguration Function

    Disruptive reconfiguration—Floods the Reconfigure Fabric (RCF) frames throughout the fabric, and • notifies all switches to perform a disruptive reconfiguration. During the reconfiguration procedure, each switch clears all data for renegotiation, and data transmission in the fabric is disrupted. • Non-disruptive reconfiguration—Floods the Build Fabric (BF) frames throughout the fabric, and notifies all switches to perform a non-disruptive reconfiguration.

  • Page 36: Configuring And Obtaining Fc4 Information Of Nodes

    Step Command Remarks Enter system view. system-view Enter VFC interface view. interface vfc interface-number Configure the VFC By default, a VFC interface does interface to reject the fc domain rcf-reject vsan vsan-id not reject the received RCF received RCF requests. requests.

  • Page 37: Configuring The Default Fc4 Information For A Node

    Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Enable auto discovery of By default, auto discovery of fc name-service auto-discovery SCSI-FCP information. SCSI-FCP information is enabled. Configuring the default FC4 information for a node If a node does not register FC4 information and the switch fails to obtain SCSI-FCP information from the node, the switch records the default FC4 information in the name service database for that node.

  • Page 38: Static Fabric Building Configuration Example

    Static fabric building configuration example Network requirements As shown in Figure 14, use the static method to build a fabric. Figure 14 Network diagram Configuration procedure Configure Switch A: # Configure Switch A to operate in advanced mode, save the configuration, and reboot Switch A. (Skip this step if the switch is operating in advanced mode.) <SwitchA>...
  • Page 39 [SwitchA] acl number 4000 [SwitchA-acl-ethernetframe-4000] rule permit type 8906 ffff [SwitchA-acl-ethernetframe-4000] rule permit type 8914 ffff [SwitchA-acl-ethernetframe-4000] quit # Create a class named app_c with the logic OR operator, and specify ACL 4000 as the match criterion. [SwitchA] traffic classifier app_c operator or [SwitchA-classifier-app_c] if-match acl 4000 [SwitchA-classifier-app_c] quit # Create a behavior named app_b, and configure the action of marking packets with 802.1p...
  • Page 40 # Assign interface Ten-GigabitEthernet 1/1/5 to VLAN 10 as a trunk port. [SwitchA] interface ten-gigabitethernet 1/1/5 [SwitchA-Ten-GigabitEthernet1/1/5] port link-type trunk [SwitchA-Ten-GigabitEthernet1/1/5] port trunk permit vlan 10 [SwitchA-Ten-GigabitEthernet1/1/5] quit # Create interface VFC 2, and configure it to operate in E mode. [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode e # Bind interface VFC 2 to interface Ten-GigabitEthernet 1/1/6, and assign it to VSAN 1 as a trunk...
  • Page 41 # Enable LLDP on interface Ten-GigabitEthernet 1/1/5, and enable the interface to advertise DCBX TLVs. [SwitchB] interface ten-gigabitethernet 1/1/5 [SwitchB-Ten-GigabitEthernet1/1/5] lldp enable [SwitchB-Ten-GigabitEthernet1/1/5] lldp tlv-enable dot1-tlv dcbx [SwitchB-Ten-GigabitEthernet1/1/5] quit # Create an Ethernet frame header ACL numbered 4000, and configure two rules to match FCoE frames (protocol type 0x8906) and FIP frames (protocol type 0x8914).

  • Page 42: Verifying The Configurations

    [SwitchB-Ten-GigabitEthernet1/1/5] quit # Create interface VFC 1, configure it to operate in F mode, bind it to interface Ten-GigabitEthernet 1/1/5, and assign it to VSAN 1 as a trunk port. [SwitchB] interface vfc 1 [SwitchB-Vfc1] fc mode f [SwitchB-Vfc1] bind interface ten-gigabitethernet 1/1/5 [SwitchB-Vfc1] port trunk vsan 1 [SwitchB-Vfc1] quit # Assign interface Ten-GigabitEthernet 1/1/5 to VLAN 10 as a trunk port.

  • Page 43: Dynamic Fabric Building Configuration Example

    Priority: 128 Domain ID: 1 (static) 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 A is 1. Verify the configurations on Switch B. [SwitchB] display fc domain vsan 1 Domain Information of VSAN 1: Running time information:...

  • Page 44: Configuration Procedure

    Figure 15 Network diagram Configuration procedure Configure Switch A: # Configure Switch A to operate in advanced mode, save the configuration, and reboot Switch A. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] 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.
  • Page 45 [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode e # Bind interface VFC 2 to interface Ten-GigabitEthernet 1/1/6, and assign it to VSAN 1 as a trunk port. [SwitchA-Vfc2] bind interface ten-gigabitethernet 1/1/6 [SwitchA-Vfc2] port trunk vsan 1 [SwitchA-Vfc2] quit # Assign interface Ten-GigabitEthernet 1/1/6 to VLAN 10 as a trunk port. [SwitchA] interface ten-gigabitethernet 1/1/6 [SwitchA-Ten-GigabitEthernet1/1/6] port link-type trunk [SwitchA-Ten-GigabitEthernet1/1/6] port trunk permit vlan 10...
  • Page 46 # Create interface VFC 2, and configure it to operate in E mode. [SwitchB] interface vfc 2 [SwitchB-Vfc2] fc mode e # Bind interface VFC 2 to interface Ten-GigabitEthernet 1/1/6, and assign it to VSAN 1 as a trunk port. [SwitchB-Vfc2] bind interface ten-gigabitethernet 1/1/6 [SwitchB-Vfc2] port trunk vsan 1 [SwitchB-Vfc2] quit...
  • Page 47 Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchC-vsan1] quit # Enable LLDP globally. [SwitchC] lldp global enable # Enable LLDP on interface Ten-GigabitEthernet 1/1/7, and enable the interface to advertise DCBX TLVs. [SwitchC] interface ten-gigabitethernet 1/1/7 [SwitchC-Ten-GigabitEthernet1/1/7] lldp enable [SwitchC-Ten-GigabitEthernet1/1/7] lldp tlv-enable dot1-tlv dcbx [SwitchC-Ten-GigabitEthernet1/1/7] quit...
  • Page 48 # Enable interface Ten-GigabitEthernet 1/1/7 to automatically negotiate with its peer to decide whether to enable PFC, enable PFC for 802.1p priority 3, and configure Ten-GigabitEthernet 1/1/7 to trust the 802.1p priority carried in packets. [SwitchC-Ten-GigabitEthernet1/1/7] priority-flow-control auto [SwitchC-Ten-GigabitEthernet1/1/7] priority-flow-control no-drop dot1p 3 [SwitchC-Ten-GigabitEthernet1/1/7] qos trust dot1p [SwitchC-Ten-GigabitEthernet1/1/7] quit # Create interface VFC 1, and configure it to operate in E mode.
  • Page 49 # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchC] vlan 10 [SwitchC-vlan10] fcoe enable vsan 1 [SwitchC-vlan10] quit Configure Switch D: # Configure Switch D to operate in advanced mode, save the configuration, and reboot Switch D. (Skip this step if the switch is operating in advanced mode.) <SwitchD>...
  • Page 50 # Create a QoS policy named plcy, and associate the class app_c with the behavior app_b in the QoS policy, specifying that the class-behavior association applies only to DCBX. [SwitchD] qos policy plcy [SwitchD-qospolicy-plcy] classifier app_c behavior app_b mode dcbx [SwitchD-qospolicy-plcy] quit # Apply the QoS policy plcy to the outbound direction of interface Ten-GigabitEthernet 1/1/6.

  • Page 51: Verifying The Configurations

    # Assign interface Ten-GigabitEthernet 1/1/6 to VLAN 10 as a trunk port. [SwitchD] interface ten-gigabitethernet 1/1/6 [SwitchD-Ten-GigabitEthernet1/1/6] port link-type trunk [SwitchD-Ten-GigabitEthernet1/1/6] port trunk permit vlan 10 [SwitchD-Ten-GigabitEthernet1/1/6] quit # Enable FCoE for VLAN 10 and map VLAN 10 to VSAN 1. [SwitchD] vlan 10 [SwitchD-vlan10] fcoe enable vsan 1 [SwitchD-vlan10] quit...
  • Page 52 The output shows that Switch B becomes the principal switch and assigns the smallest domain ID 1 to itself.

  • Page 53: Configuring Vsan

    Configuring VSAN 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 54: Creating A Vsan

    Creating a VSAN Initially, only the default VSAN (VSAN 1) exists. You cannot create or delete VSAN 1. You can create VSANs 2 to 3839. On a device, you can create up to 16 VSANs, including the default VSAN. To create a VSAN: Step Command Remarks...

  • Page 55: Configuration Considerations

    Server A can read and write only the data of Disk A and Disk B. • • Server B can read and write only the data of Disk C. Figure 16 Network diagram Configuration considerations To meet these requirements, divide the SAN into two VSANs, VSAN 10 and VSAN 20. Each VSAN •...
  • Page 56 [SwitchA-vsan10] quit [SwitchA] vsan 20 [SwitchA-vsan20] quit # Enable LLDP globally. [SwitchA] lldp global enable # Enable LLDP on interfaces Ten-GigabitEthernet 1/1/5 and Ten-GigabitEthernet 1/1/6, and enable the interfaces to advertise DCBX TLVs. [SwitchA] interface ten-gigabitethernet 1/1/5 [SwitchA-Ten-GigabitEthernet1/1/5] lldp enable [SwitchA-Ten-GigabitEthernet1/1/5] lldp tlv-enable dot1-tlv dcbx [SwitchA-Ten-GigabitEthernet1/1/5] quit [SwitchA] interface ten-gigabitethernet 1/1/6...
  • Page 57 [SwitchA-maptbl-out-dot1p-lp] import 3 export 3 [SwitchA-maptbl-out-dot1p-lp] quit # Enable byte-count WRR on Ten-GigabitEthernet 1/1/5 and Ten-GigabitEthernet 1/1/6, and configure queue 3 to use SP queuing. [SwitchA] interface ten-gigabitethernet 1/1/5 [SwitchA-Ten-GigabitEthernet1/1/5] qos wrr byte-count [SwitchA-Ten-GigabitEthernet1/1/5] qos wrr 3 group sp [SwitchA-Ten-GigabitEthernet1/1/5] quit [SwitchA] interface ten-gigabitethernet 1/1/6 [SwitchA-Ten-GigabitEthernet1/1/6] qos wrr byte-count [SwitchA-Ten-GigabitEthernet1/1/6] qos wrr 3 group sp...

  • Page 58: Verifying The Configurations

    [SwitchA] interface ten-gigabitethernet 1/1/6 [SwitchA-Ten-GigabitEthernet1/1/6] port link-type trunk [SwitchA-Ten-GigabitEthernet1/1/6] port trunk permit vlan 20 [SwitchA-Ten-GigabitEthernet1/1/6] quit # Create interface VFC 4, and configure it to operate in E mode. [SwitchA] interface vfc 4 [SwitchA-Vfc4] fc mode e # Bind interface VFC 4 to interface Ten-GigabitEthernet 1/1/8, and assign it to VSANs 10 and 20 as a trunk port.
  • Page 59 The output on Switch B is the same as that on Switch A.

  • Page 60: 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 61: Direct Routes

    FCF switch is 0x010000. A network mask is made up of a certain number of consecutive 1s. It can be expressed in hexadecimal format or by the number of 1s. Protocol—Protocol type: • DIRECT—Direct routes. STATIC—Static routes. FSPF—FSPF routes. Preference—There might be direct routes, static routes, and FSPF routes to the same destination. All •...

  • Page 62: Static Routes

    When an FCF switch assigns FC addresses to the directly connected N_Ports, the FCF switch also • adds the direct routes of these addresses to the routing table. In such a direct route, the destination address is an assigned FC address, the mask is 0xFFFFFF, and the outgoing interface is the VFC interface connected to the N_Port.

  • Page 63: Configuring Static Routes For Fc

    Link ID, which identifies a link and includes the domain ID of the switch at the peer end of the link. Source interface and destination interface of the link. Link type, for example, point-to-point connection. Cost for packet transmission over the link. Each link has a different cost. The smaller the cost, the better the link.

  • Page 64: Configuration Procedure

    Configuration procedure To configure a static FC route: Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id fc route-static fcid { mask | mask-length } Configure a static FC interface-type interface-number [ cost By default, no static FC route exists. route.

  • Page 65: Configuring The Shortest Spf Calculation Interval

    Step Command Remarks Enter VSAN view. vsan vsan-id By default, FSPF is enabled after a VSAN is Enable FSPF for the VSAN. fspf enable created. Configuring the shortest SPF calculation interval When the LSDB changes, SPF calculations occur, which consume CPU resources. To prevent frequent SPF calculations from consuming too many CPU resources, you can configure the shortest SPF calculation interval.

  • Page 66: Configuring The Fspf Cost For An Interface

    Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id Configure the minimum fspf min-ls-interval value The default setting is 5 seconds. LSR refresh interval. Configuring the FSPF cost for an interface Each link has a different cost. The route selection algorithm uses this value to determine the best route. The smaller the interface FSPF cost, the smaller the link cost.

  • Page 67: Configuring The Lsr Retransmission Interval For Interfaces

    NOTE: The configured dead interval must be greater than the hello interval and must be the same at the two ends of the link. To configure the interface dead interval: Step Command Remarks Enter system view. system-view Enter VFC interface view. interface vfc interface-number Configure the dead interval for fspf dead-interval value vsan...

  • Page 68: Configuring Fspf Gr

    Configuring FSPF GR FSPF Graceful Restart (GR) enables nonstop forwarding of traffic by backing up FSPF configuration information during a protocol restart (for example, the FSPF process restart triggered by the process command) or active/standby switchover. GR involves the following roles: GR restarter—GR-capable device where a protocol restart or active/standby switchover occurs •...

  • Page 69: Static Fc Routing Configuration Example

    Task Command Clear FSPF statistics. reset fspf counters [ vsan vsan-id ] Static FC routing configuration example Network requirements As shown in Figure 17, configure static routes to enable any two FCF switches to communicate with each other. Figure 17 Network diagram Switch B Domain ID: 2 VFC2...
  • Page 70 # Create interface VFC 1, and configure it to operate in E mode. [SwitchA] interface vfc 1 [SwitchA-Vfc1] fc mode e # Bind interface VFC 1 to interface Ten-GigabitEthernet 1/1/5, and assign it to VSAN 1 as a trunk port. [SwitchA-Vfc1] bind interface ten-gigabitethernet 1/1/5 [SwitchA-Vfc1] port trunk vsan 1 [SwitchA-Vfc1] quit...
  • Page 71 [SwitchB-Vfc1] bind interface ten-gigabitethernet 1/1/5 [SwitchB-Vfc1] port trunk vsan 1 [SwitchB-Vfc1] quit # Assign interface Ten-GigabitEthernet 1/1/5 to VLAN 10 as a trunk port. [SwitchB] interface ten-gigabitethernet 1/1/5 [SwitchB-Ten-GigabitEthernet1/1/5] port link-type trunk [SwitchB-Ten-GigabitEthernet1/1/5] port trunk permit vlan 10 [SwitchB-Ten-GigabitEthernet1/1/5] quit # Create interface VFC 2, and configure it to operate in E mode.

  • Page 72: Verifying The Configurations

    Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchC-vsan1] quit # Create interface VFC 2, and configure it to operate in E mode. [SwitchC] interface vfc 2 [SwitchC-Vfc2] fc mode e # Bind interface VFC 2 to interface Ten-GigabitEthernet 1/1/6, and assign it to VSAN 1 as a trunk port.

  • Page 73: 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 C. [SwitchC] display fc routing-table vsan 1 Routing Table: VSAN 1 Destinations : 6 Routes : 6 Destination/mask Protocol Preference Cost Interface 0x010000/8...
  • Page 74 # Configure Switch A to operate in advanced mode, save the configuration, and reboot Switch A. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] 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.

  • Page 75: Verifying The Configurations

    The system working mode is changed, please save the configuration and reboot the system to make it effective. # Configure Switch B to operate in FCF mode. Enable the fabric configuration function in VSAN <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 2 [SwitchB-vsan2] domain configure enable # Configure the domain ID as 2.
  • Page 76 Routing Table: VSAN 2 Destinations : 5 Routes : 5 Destination/mask Protocol Preference Cost Interface 0x020000/8 FSPF Vfc1 0xfffc01/24 DIRECT InLoop0 0xfffffa/24 DIRECT InLoop0 0xfffffc/24 DIRECT InLoop0 0xfffffd/24 DIRECT InLoop0 # On Switch A, use the fcping command to ping Switch B and check whether Switch B is reachable. [SwitchA] fcping fcid fffc02 vsan 2 FCPING fcid 0xfffc02: 128 data bytes, press CTRL_C to break.

  • Page 77: 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 78 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 79: 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 80 Figure 21 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 81: 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 82 Figure 22 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 83: 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 84: Configuring Zone Aliases

    Tasks at a glance (Required.) Configuring the default zone policy (Required.) Configuring zone distribution and merge types (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.)

  • Page 85: Configuring Zone Sets

    Step Command Remarks Create a zone and enter If the zone has been created, enter zone name zone-name its view. its view directly. Add a member to the member { fcid fcid | pwwn pwwn | By default, no member exists in a zone.

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

    Step Command Remarks Enter VSAN view. vsan vsan-id Configure zone distribution and merge The default setting is incomplete types as complete zoneset distribute full distribution and incomplete merge. distribution and complete merge. 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.

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

    Step Command Enter system view. system-view Enter VSAN view. vsan vsan-id Activate a complete distribution. zoneset distribute 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.

  • Page 88: Deleting The Zone Database

    Deleting the zone database You can delete the zone database for the specified VSAN, including all zone sets, zones, and zone aliases, but not the active zone set. To delete the zone database: Step Command Enter system view. system-view Enter VSAN view. vsan vsan-id Delete the zone database.

  • Page 89: Configuration Considerations

    Figure 23 Network diagram Disk A Server A PWWN: Zone 1 FC_ID: 11:22:33:44:55:66:77:88 010001 (FC_ID:020006) Switch A Switch B Disk B Server B PWWN: FC_ID: 22:33:44:55:66:77:88:99 010002 (FC_ID:020005) Zone 2 Alias 1 Server C Disk C Zone 3 FC_ID: FC_ID: 010003 020004 Configuration considerations...

  • Page 90: Verifying The Configurations

    [SwitchA] fcoe-mode fcf [SwitchA] vsan 1 # Create a zone alias Alias1, and add pWWN 22:33:44:55:66:77:88:99 (Disk B) and FC address 020004 (Disk C) as its members. [SwitchA-vsan1] zone-alias name Alias1 [SwitchA-vsan1-zone-alias-Alias1] member pwwn 22:33:44:55:66:77:88:99 [SwitchA-vsan1-zone-alias-Alias1] member fcid 020004 [SwitchA-vsan1-zone-alias-Alias1] quit # Create a zone Zone1 and specify FC ID 010001 as its member.
  • Page 91 zone-alias Alias1 fcid 0x020004 pwwn 22:33:44:55:66:77:88:99 zone name Zone3 fcid 0x010003 zone-alias Alias1 fcid 0x020004 pwwn 22:33:44:55:66:77:88:99 # Display information about Zone 2 in VSAN 1. <SwitchB> display zone name Zone2 vsan 1 VSAN 1: zone name Zone2 fcid 0x010002 pwwn 11:22:33:44:55:66:77:88 zone-alias Alias1 fcid 0x020004...

  • Page 92: 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 24 shows a typical NPV network diagram. Figure 24 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 93: 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 94: Configuring Uplink Interfaces

    Configuring uplink interfaces Uplink interfaces must be VFC interfaces in NP mode. 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...

  • Page 95: Initiating A Disruptive Load-Balancing Process

    Step Command Remarks Enter system view. system-view Enter VSAN view. vsan vsan-id 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 96: Configuration Procedure

    Figure 25 Network diagram Configuration procedure Configuring Switch A # Configure Switch A to operate in advanced mode, save the configuration, and reboot Switch A. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] 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.
  • Page 97 # Create a class named app_c with the logic OR operator, and specify ACL 4000 as the match criterion. [SwitchA] traffic classifier app_c operator or [SwitchA-classifier-app_c] if-match acl 4000 [SwitchA-classifier-app_c] quit # Create a behavior named app_b, and configure the action of marking packets with 802.1p priority 3. [SwitchA] traffic behavior app_b [SwitchA-behavior-app_b] remark dot1p 3 [SwitchA-behavior-app_b] quit...
  • Page 98 [SwitchA-Ten-GigabitEthernet1/1/6] qos trust dot1p [SwitchA-Ten-GigabitEthernet1/1/6] quit # Create interface VFC 1, bind it to interface Ten-GigabitEthernet 1/1/5, and assign it to VSAN 1 as a trunk port. [SwitchA] interface vfc 1 [SwitchA-Vfc1] bind interface ten-gigabitethernet 1/1/5 [SwitchA-Vfc1] port trunk vsan 1 [SwitchA-Vfc1] quit # Configure Ten-GigabitEthernet 1/1/5 to allow VLAN 10.

  • Page 99: Verifying The Configurations

    [SwitchA-Vfc1] fc mode f [SwitchA-Vfc1] quit [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode f [SwitchA-Vfc2] quit Configuring Switch B # Configure Switch B to operate in advanced mode, save the configuration, and reboot Switch B. (Skip this step if the switch is operating in advanced mode.) <SwitchB>...
  • Page 100 External Interfaces: Interface: Vfc3 VSAN tagging mode: Tagging VSAN State FCID 0x010000 Number of External Interfaces: 1 Server Interfaces: Interface: Vfc1 VSAN tagging mode: Tagging VSAN State Interface: Vfc2 VSAN tagging mode: Tagging VSAN State Number of Server Interfaces: 2 # Display the traffic mapping information.

  • Page 101: 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 102: Configuration Procedure

    Configuration procedure Configure Switch A: # Configure Switch A to operate in advanced mode, save the configuration, and reboot Switch A. (Skip this step if the switch is operating in advanced mode.) <SwitchA> system-view [SwitchA] 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.

  • Page 103: Verifying The Configurations

    [SwitchB] 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. # Configure Switch B to operate in FCF mode, and enable the fabric configuration function in VSAN 1 (optional, because this function is enabled by default).
  • Page 104 Reply from 0xfffc02: bytes = 128 time = 14 ms Reply from 0xfffc02: bytes = 128 time = 25 ms --- 0xfffc02 fcping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 9/18/25 ms...

  • Page 105: 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 106: Configuration Procedure

    Uplink process: 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 107 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. # Configure Switch A to operate in FCF mode, and enable the fabric configuration function in VSAN 1.
  • Page 108 <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 1 [SwitchB-vsan1] domain configure enable # 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 # Disable FSPF globally. [SwitchB-vsan1] undo fspf enable # Configure a static route.
  • Page 109 <SwitchC> system-view [SwitchC] 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. # Configure Switch C to operate in FCF mode, and enable the fabric configuration function in VSAN 1.
  • Page 110 100.00% packet loss The output shows that Switch A cannot reach Switch C. Use the fctracert command to identify the faulty node. [SwitchA] fctracert fcid fffc03 vsan 1 Route present for: 0xfffc03, press CTRL_C to break 20:00:00:0b:46:00:02:82(0xfffc01) 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.

  • Page 111: 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 112 FC_ID Description 0xFFFFF9 Reserved. 0xFFFFFA Management services. 0xFFFFFB Time services. 0xFFFFFC Path services (name services).

  • Page 113: Support And Other Resources

    Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers • Technical support registration number (if applicable) • • Product serial numbers Error messages •...

  • Page 114: 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 115 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 116: Index

    Index FC FSPF SPF calculation shortest interval configuration, access control configuring FCoE FC zone, default FC4 information, activating FC fabric timer (system view), FCoE FC zone set, FC fabric timer (VSAN view), active FC FSPF GR, FC zone database active zone set, FC FSPF GR helper, address FC FSPF GR restarter,...
  • Page 117 FCoE FC-MAP value, FCoE NPV disruptive load balancing, FCoE FKA advertisement period value, FCoE NPV downlink, FCoE FSPF, FCoE NPV downlink interface, 86, 87, FCoE mode, FCoE NPV downlink-to-uplink interface mapping, 87, FCoE mode for switch, FCoE NPV uplink, FCoE trunk VSAN, FCoE NPV uplink interface, 86, 87, FCoE VFC interface, FCoE overview,...
  • Page 118 enabling FCoE fabric principal switch selection, auto discovery of SCSI-FCP information, FCoE fabric reconfiguration, FC FSPF, FCoE fabric static build, FCoE fabric configuration, FCoE fabric switch domain ID configuration, FCoE for VLAN, FCoE fabric switch priority setting, encapsulating FCoE FC zone set distribution, FCoE frames, FCoE mode, error...
  • Page 119 fabric dynamic building configuration, FC static routes, fabric FC address assignment, FC tracert configuration, 99, fabric mode, FC zone, fabric N_Port-WWN-to-FC address FC zone alias configuration, mapping, FC zone configuration, 71, 77, 78, fabric name setting, FC zone database, 71, fabric principal switch selection, FC zone database deletion, fabric reconfiguration,...
  • Page 120 trunk VSAN configuration, interface LSR retransmission interval, VFC interface, LSR receiving minimum interval, VFC interface configuration, LSR refresh minimum interval, VFC interface FCF priority configuration, SPF calculation shortest interval configuration, VFC interface/FIP configuration, 13, VN interface, Graceful Restart VSAN, FC FSPF GR helper configuration, VSAN configuration, 47, FC FSPF GR restarter configuration, VSAN creation,...
  • Page 121 FCoE frame transmission, FC FSPF interface LSR retransmission interval, maintaining FC FSPF LSR receiving minimum interval, FC forwarding, FC FSPF LSR refresh minimum interval, FC routing, FC FSPF routes, VFC interface/FIP, FC FSPF SPF calculation shortest interval configuration, manual FCoE fabric reconfiguration, FC SAN, mapping FC static routes,...
  • Page 122 FCoE FKA advertisement period value, FCoE VN interface, FCoE for VLAN enable, non-disruptive FCoE fabric reconfiguration, FCoE frames, non-FCoE mode (FCoE), FCoE NPV disruptive load balancing, 87, FCoE NPV downlink, configuration, 86, 87, FCoE NPV downlink interface, 86, 87, displaying, FCoE NPV downlink-to-uplink interface disruptive load balancing, mapping,...
  • Page 123 configuring fabric timer (system view), configuring FCoE VFC interface FCF priority, configuring fabric timer (VSAN view), configuring FCoE VFC interface/FIP, 13, configuring FC FSPF GR, configuring FCoE VSAN, configuring FC FSPF GR helper, configuring NPV, 87, configuring FC FSPF GR restarter, configuring NPV downlink interface, 87, configuring FC FSPF interface cost, configuring NPV downlink-to-uplink interface...
  • Page 124 FCoE, FCoE FSPF configuration, FIP (FCoE initialization protocol), rule FC zone merge rules, RCF request rejection, rejecting RCF request, renaming FC SAN, FCoE FC zone aliases, FCoE fabric dynamic building configuration, FCoE FC zone sets, FCoE fabric setup, 21, FCoE FC zones, FCoE fabric static building configuration, resource FCoE FC forwarding configuration,...
  • Page 125 FC static routes, FC interface routing table entry, FCoE fabric static building configuration, FC mask FIB table entry, FCoE fabric static mode, FC mask routing table entry, FCoE FC static route configuration, FC preference routing table entry, storage FC routing table, area network.
  • Page 126 FCoE NPV configuration, 86, 87, FCoE allowed domain ID list, FCoE overview, FCoE fabric dynamic building configuration, FCoE VFC interface/FIP configuration, 13, FCoE fabric setup, 21, FCoE VSAN configuration, 47, FCoE fabric static building configuration, FCoE well-known fabric addresses, FCoE FC zone, VLAN FCoE for VLAN enable, FCoE for VLAN enable,...
  • Page 127 FCoE FC zone distribution, FCoE FC zone merge type, FCoE FC zone set activation, FCoE FC zone set configuration, FCoE FC zone set distribution triggering, FCoE FC zone set fabric distribution, FCoE FC zone-related copying, FCoE FC zone-related renaming,...

Table of Contents