HP 5920 & 5900 Switch Series

Transcription

1 HP 5920 & 5900 Switch Series FCoE Configuration Guide Part number: Software version: Release2207 Document version: 6W

2 Legal and notice information Copyright 2012 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 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. 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

3 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 FCoE 4 Basic concepts 5 How FCoE works 6 FCoE modes 8 FCF mode 8 NPV mode 9 Protocols and standards 9 FCoE configuration guidelines 11 FCoE features supported by different FCoE modes 11 Configuring an FCoE mode for a switch 11 Configuring VFC interfaces and FIP 12 VFC interfaces and FIP configuration task list 12 Configuring a VFC interface 12 Enabling FCoE for a VLAN and mapping a VSAN to the VLAN 13 Configuration restrictions and guidelines 13 Configuration procedure 13 Configuring the FC-MAP value 13 Configuring the FKA advertisement period value 14 Role of the FKA advertisement period value 14 Configuration restrictions and guidelines 14 Configuring the FCF priority 15 Configuring the system FCF priority 15 Configuring the VFC interface FCF priority 16 Displaying and maintaining VFC interfaces and FIP 16 VFC interfaces and FIP configuration example 16 Network requirements 16 Configuration procedure 17 Setting up a fabric 19 Overview 19 Principal switch selection 19 Domain ID assignment 20 FC address assignment 21 Fabric setup configuration task list 21 Building a fabric statically 21 Building a fabric dynamically 22 Enabling or disabling the fabric configuration function 22 Setting a fabric name 23 Setting the switch priority 23 Configuring the allowed domain ID list 24 i

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 Configuring the fabric timers in VSAN view 26 Configuring the fabric reconfiguration 26 Configuring the auto fabric reconfiguration function 27 Manually initiating the fabric reconfiguration 27 Configuring a VFC interface to reject incoming RCF requests 27 Displaying and maintaining a fabric 27 Static fabric building configuration example 28 Network requirements 28 Configuration procedure 28 Verifying the configurations 29 Dynamic fabric building configuration example 30 Network requirements 30 Configuration procedure 30 Verifying the configurations 31 Configuring VSAN 33 Overview 33 VSAN fundamentals 33 Creating a VSAN 34 Configuring a trunk VSAN 34 Displaying and maintaining VSAN 35 VSAN configuration example 35 Network requirements 35 Configuration considerations 35 Configuration procedure 36 Verifying the configurations 37 Configuring FC routing and forwarding 38 Overview 38 Routing table and FIB table 38 Direct routes 39 Static routes 39 FSPF routes 40 Configuring static routes for FC 41 Configuration restrictions and guidelines 41 Configuration procedure 41 Configuring FSPF 41 FSPF configuration task list 42 Enabling FSPF 42 Configuring the shortest SPF calculation interval 42 Configuring the minimum LSR receiving interval 43 Configuring the minimum LSR refresh interval 43 Configuring the FSPF cost for an interface 43 Configuring the hello interval for an interface 44 Configuring the dead interval for an interface 44 Configuring the LSR retransmission interval for interfaces 44 Disabling FSPF for an interface 45 Configuring FSPF GR 45 Displaying and maintaining FC routing and forwarding 46 Static FC routing configuration example 46 Network requirements 46 ii

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 Zone database 53 Distributing zones 55 Zone merge 57 Access control 59 FC zone configuration task list 59 Configuring zone aliases 60 Configuring zones 60 Configuring zone sets 61 Configuring the default zone policy 61 Configuring zone distribution and merge types 61 Activating a zone set and distributing it to the entire fabric 62 Triggering a complete distribution 62 Renaming zone aliases, zones, and zone sets 63 Copying zone aliases, zones, and zone sets 63 Deleting the zone database 63 Displaying and maintaining FC zones 64 FC zone configuration example 64 Network requirements 64 Configuration considerations 65 Configuration procedure 65 Verifying the configurations 66 Configuring NPV 68 Overview 68 Downlink interface and downlink 68 Uplink interface and uplink 68 Downlink-to-uplink interface mappings 69 Disruptive load balancing 69 NPV configuration task list 69 Configuring uplink interfaces and downlink interfaces 69 Configuring uplink interfaces 69 Configuring downlink interfaces 70 Configuring downlink-to-uplink interface mappings 70 Initiating a disruptive load-balancing process 71 Displaying and maintaining NPV 71 NPV configuration example 71 Network requirements 71 Configuration procedure 72 Verifying the configurations 73 Configuring FC ping 75 Overview 75 Configuration procedure 75 FC ping configuration example 75 Network requirements 75 Configuration procedure 75 Verifying the configurations 77 iii

6 Configuring FC tracert 78 Overview 78 Configuration procedure 79 FC tracert configuration example 79 Network requirements 79 Configuration procedure 79 Appendixes 82 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 Websites 84 Conventions 85 Index 87 iv

7 FCoE overview Storage area network FC SAN 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. Most SANs use Fibre Channel (FC) or Ethernet to interconnect devices. An FC SAN uses the FC protocol suite for communication, and an Ethernet SAN uses the TCP/IP protocol suite for communication. This document covers only the FC SAN. As shown in Figure 1, an FC SAN connects the data sending and receiving entities (network servers and disk devices) with fibers or copper wires in the following ways: Directly connects a server and a disk device, as shown in the point-to-point connection. Connects servers and disk devices to an FCF switched fabric, as shown in the switched fabric. In a switched fabric, the servers and disk devices are called "nodes." A fabric uses 24-bit addressing and supports thousands of devices. Figure 1 FC SAN networking NOTE: An FC SAN refers to a network comprising FCF switches and nodes. A fabric refers to a transmission network comprising FCF switches. 1

8 FC protocol The servers, FCF switches, and disk devices in an FC SAN must all support FC. Basic concepts WWN FC address 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. The FC protocol accesses communication entities in a SAN through FC addresses. An FC address is also known as an "FC_ID." Figure 2 shows the structure of an FC address. The FC address is 24 bits long and is divided into these 8-bit fields: Domain_ID, Area_ID, and Port_ID. A domain represents a switch and all N_Ports connected to the switch. A Domain_ID, which is in the range of 1 to 239, uniquely identifies an FCF switch. One or more N_Ports on the same node can be assigned to an area, which is identified by an Area_ID. The Port_ID field identifies an N_Port. Figure 2 Structure of an FC address Interface modes A Domain_ID can uniquely identify an FCF switch. Different FCF 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. FCF switches use Domain_IDs to route messages between each other. The FC protocol standardizes the FC address usage. For more information, see "Appendixes." In a switched fabric, nodes and FCF switches communicate through interfaces of different modes. 2

9 Figure 3 Port modes 1. The interface on a node is called an "N_Port." 2. 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. For more information about NP_Port, see "Configuring NPV." E_Ports connect FCF switches to form a fabric, and F_Ports connect the nodes to FCF switches in the fabric. Communication flow FCF switches provide data transmission services. Through FCF switches, a server sends instructions and data to disk devices and reads data from disk devices. 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. 1. The server and the disk device use the fabric login (FLOGI) protocol to register with the FCF switches, which then assign FC addresses to each directly-connected node. 2. The registered server and disk device send name service registration requests to their respective access FCF switches to register name service information, including their WWNs and FC addresses. Finally, each FCF switch in the fabric stores the name service information for all nodes. 3. To access a disk device, the server needs to send a name service query request to its directly-connected FCF switch to obtain the list of disk devices in the fabric and their WWNs and FC addresses. 3

10 4. 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. 5. 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. The next-hop FCF switch forwards the FC frame in the same way, until the FCF switch at the last hop forwards the FC frame to the destination disk device. NOTE: A FIB table is generated by the FCF switch through calculation based on the FC routing protocol or configured static routes. VSAN FC zone FCoE In actual applications, the data is insecure because the data of all users is transmitted in the same FC SAN. You can divide one physical FC SAN into multiple Virtual Storage Area Networks (VSANs). In this manner, VSANs are separated from one another and provide independent services, enhancing adaptability and security of the network and offering more effective services for users. For more information about VSAN, see "Configuring VSAN." With VSAN, one physical SAN is divided into multiple logical SANs. 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. This creates data security risks. 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." A data center using the FC SAN technology usually comprises separate local area networks (LANs) and SANs. LANs carry traditional Ethernet/IP services, and SANs carry network storage services. To provide services for LANs and use SANs for storage simultaneously, the servers must use independent Ethernet adapters and FC adapters. In addition, the IP switches and the FCF switches are also independent and have independent network connections. Such a network needs many switches, network adapters, and cables, and it brings high investments and maintenance costs and low scalability. FCoE was introduced to solve this problem. FCoE is a protocol that carries FC over Ethernet. In an FCoE solution, the server uses an FCoE-capable Ethernet adapter, and the FCoE switch (FCoE forwarder) integrates the functions of both the traditional IP switch and FCF switch. FCoE reduces the number of network adapters, switches, and cables, and the network operation and maintenance workload. In all, FCoE reduces the total cost. 4

11 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. The links between the server and the FCF switch and between FCF switches can transmit both Ethernet frames and FC frames. For more information about FCoE, see "Configuring FCoE." Basic concepts As shown in Figure 6, the links between the FCF switch and the ENode (nodes that can transport FC over Ethernet, such as servers and disk devices) and between FCF switches can be used for receiving and sending both Ethernet frames and FC frames. 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. 5

12 FIP protocol FCoE frames 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. FCoE initialization protocol (FIP) is an FCoE control protocol that establishes and maintains virtual links. FIP establishes a virtual link between the VFC interface of an FCF switch and the VN interface of an ENode or between VFC interfaces of two FCF switches to provide a physical infrastructure for transmitting FC frames over Ethernet. To transmit an FC frame over an Ethernet link, you must encapsulate the FC frame in an FCoE frame by adding an Ethernet frame header to the FC frame. An FCoE frame uses Ethernet II encapsulation, which has the following fields in the Ethernet header: EtherType 0x8906. Destination MAC address/source MAC address For a switch, it is the FCoE MAC address of the switch (which can be displayed by using the display fcoe command). For a node, it is the fabric provided MAC address (FPMA) of the node. As shown in Figure 7, an FPMA is composed of the FC-MAP as the 24 most significant bits and the FC ID of the VN interface as the 24 least significant bits. The FC-MAP takes the value of the switch FC-MAP, 0x0EFC00 by default and confiugrable by using the fcoe fcmap command. Figure 7 FPMA composition How FCoE works Figure 8 Block diagrams of the ENode and the FCF switch ENode FCF VN interface Virtual link VFC interface FC layer Ethernet layer FC layer Ethernet layer Ethernet interface Ethernet interface 6

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 How FIP works 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. After the virtual link is established, the FCF switch encapsulates the FC frame in an FCoE frame and sends it out. After receiving the FCoE frame, the FCF switch removes its Ethernet header to send the original FC frame to the upper layer for processing. FIP sets up and maintains virtual links between a VFC interface and a VN interface or between VFC interfaces. Two categories of packets are used in FIP: Discovery Solicitation and Discovery Advertisement. There are two types of Discovery Advertisement: Solicited Discovery Advertisement A reply for a Discovery Solicitation. Unsolicited Discovery Advertisement Periodically sent. The following example shows how a virtual link is set up between an FCF switch and an ENode. Figure 9 FIP operation FCF 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 9, the following workflow is used to set up a virtual link: 1. The ENode sends a Discovery Solicitation containing its FCoE MAC address. 2. After receiving the Discovery Solicitation, the FCF switch acts differently depending on whether the receiving VFC interface is bound to the FCoE MAC address: If it is not bound, the switch learns the FCoE MAC address and replies with a solicited Discovery Advertisement, whose fcf priority field carries the FCF priority of the VFC interface. 7

14 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. 3. The FCF switch periodically sends unsolicited Discovery Advertisements, whose fcf priority field carries the FCF priority of the system. The sending interval is specified by using the fcoe fka-adv-period command and defaults to 8 seconds. 4. After receiving the Discovery Advertisements, the ENode determines the FCF switch with the highest priority according to the fcf priority field and sends a FLOGI request frame to that switch for login. 5. After receiving the FLOGI request frame, the FCF checks whether the source MAC address matches its learned or bound FCoE MAC address. If they match, it sends a FLOGI LS_ACC, which indicates the setup of the virtual link. Otherwise, it discards the FLOGI frame. 6. The FCF switch also periodically sends unsolicited Discovery Advertisements to maintain established virtual links. If the ENode fails to receive an unsolicited Discovery Advertisement within a period 2.5 times the interval specified by the fcoe fka-adv-period command, it deletes the virtual link. FCoE modes FCF mode The switch supports the following FCoE modes: 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 Virtualizer (NPV) switch. Its VFC interfaces support F mode (F_Port) and NP mode (NP_Port). An FCoE-capable switch can operate in the following modes: FCF mode When the switch operates in this mode, it can connect to the E_Port on another FCF switch through its E_Port, or connect to the N_Port on a node or the NP_Port on an NPV switch through its F_Port. NPV mode When the switch operates in this mode, it can connect to the N_Port on a node through its F_Port or to the F_Port on an FCF switch through its NP_Port. Non-FCoE mode When the switch operates in this mode, it is a standard switch and does not provide any FCoE capabilities. An FCF switch encapsulates FC frames in Ethernet frames and uses FCoE virtual links to simulate physical FC links. Therefore, it provides standard FC switching capabilities and features on a lossless Ethernet network. 8

15 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. Each FCF switch is assigned a domain ID. Each FC SAN supports a maximum number of 239 domain IDs, so an FC SAN cannot have more than 239 FCF switches. NPV mode An FC SAN needs a large number of edge switches that connect directly to nodes. N_Port Virtualization (NPV) switches are developed to expand the number of switches in an FC SAN. Figure 11 NPV network diagram As shown in Figure 11, 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. In this manner, the NPV switch forwards traffic from its connected nodes to the core switch. The NPV switch appears as an FCF switch to nodes and as a node to the core switch. For more information about NPV, see "Configuring NPV." Protocols and standards FC-FS-3, Fibre Channel - Framing and Signaling - 3 9

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 10

17 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. You can choose to configure different features based on the FCoE mode of a switch. Table 1 FCoE functions supported by different FCoE modes FCoE feature FCoE mode FCF mode NPV mode Configuring VFC interfaces and FIP Setting up a fabric Supported Supported Supported Only the following function is supported: "Configuring the fabric timers." Configuring VSAN Supported Supported Configuring FC routing and forwarding Supported Only the following functions are supported: Displaying FC routing table information Displaying FC FIB table information Display FC Exchange table information Configuring FC zones Supported Not supported Configuring NPV Not supported Supported Configuring FC ping Supported Not supported Configuring FC tracert Supported Not supported Configuring an FCoE mode for a switch An FCoE-capable switch can operate in FCF mode, NPV mode, or non-fcoe mode. The switch can only convert from non-fcoe mode to one FCoE mode, or vice versa, and it cannot convert directly among the two FCoE modes. To convert among the two FCoE modes, first convert the switch to non-fcoe mode. After converting the switch to non-fcoe mode, FCoE-related configurations in the original FCoE mode are cleared. To configure an FCoE mode for a switch: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure an FCoE mode for the switch. fcoe-mode { fcf npv } By default, a switch operates in non-fcoe mode. 11

18 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 Configuring a VFC interface Step Command Remarks 1. Enter system view. system-view N/A 2. Create a VFC interface and enter its view. 3. Configure the VFC interface mode. 4. Bind the VFC interface to the specified Ethernet interface. 5. Assign the VFC interface to the specified VSAN as a trunk interface. 6. (Optional.) Configure a description for the VFC interface. interface vfc interface-number fc mode { e f np } bind interface interface-type interface-number [ mac mac-address ] port trunk vsan vsan-id description text N/A By default, a VFC interface operates in F mode. When an FCF switch operates in FCF mode, VFC interfaces support E and F modes. When an FCF switch operates in NPV mode, FC interfaces support F and NP modes. By default, no Ethernet interface is bound to a VFC interface. The VFC interface sends and receives packets through the Ethernet interface bound to it. By default, a VFC interface is not assigned to any VSAN as a trunk interface. You can assign a VFC interface to a nonexistent VSAN as a trunk interface and then create the VSAN. By default, the description of an interface is Interface name Interface, for example, Vfc1 Interface. 12

19 Step Command Remarks 7. (Optional.) Restore the default settings for the VFC interface. default 8. Bring up the VFC interface. undo shutdown By default, a VFC interface is up. N/A 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. You should enable FCoE for a VLAN and map a VSAN to the VLAN, so that the packets from the VSAN are tagged with the VLAN tag and transmitted within the VLAN. Configuration restrictions and guidelines Follow these restrictions and guidelines when you configure this feature: FCoE cannot be enabled for VLAN 1. VSANs are mapped to VLANs on a one-to-one basis. You must enable FCoE for the same VLAN and map this VLAN to the same VSAN on the two ends. Make sure the Ethernet interface bound to the VFC interface allows the FCoE-capable VLAN. After you enable FCoE for a VLAN, the following changes apply to the VLAN: An FCoE-capable VLAN allows only FCoE traffic. All member ports in an FCoE-capable VLAN are isolated. For this reason, a Layer 2 protocol enabled in the FCoE-capable VLAN runs based on the port isolation topology. Configuration procedure To enable FCoE for the specified VLAN and map this VLAN to the specified VSAN: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VLAN view. vlan vlan-id N/A 3. Enable FCoE for the specified VLAN and map this VLAN to the specified VSAN. fcoe enable [ vsan vsan-id ] By default, FCoE for a VLAN is disabled. Make sure that the VSAN to be mapped has been created. 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. 13

20 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 Remarks 1. Enter system view. system-view N/A 2. Configure an FC-MAP value. fcoe fcmap fc-map The default setting is 0x0EFC00. Configuring the FKA advertisement period value Role of the FKA advertisement period value The FKA advertisement period value functions as follows: After setting up a virtual link with a peer switch, a switch sends unsolicited Discovery Advertisements every FKA advertisement period on its VFC interfaces in E mode to maintain the established virtual link. The FKA advertisement period value is carried in unsolicited Discovery Advertisements. After receiving an unsolicited Discovery Advertisement, the peer switch maintains the status of the virtual link and records the FKA advertisement period value. If the peer switch fails to receive an unsolicited Discovery Advertisement within 2.5 FKA advertisement periods, it deletes the virtual link. After setting up a virtual link with a peer ENode, a switch sends unsolicited Discovery Advertisements every FKA advertisement period on its VFC interfaces in F mode to maintain the established virtual link. The FKA advertisement period value is carried in unsolicited Discovery Advertisements. After receiving an unsolicited Discovery Advertisement, the peer ENode maintains the status of the virtual link and records the FKA advertisement period value. If the peer ENode fails to receive an unsolicited Discovery Advertisement within 2.5 FKA advertisement periods, it deletes the virtual link. In addition, the ENode sends keepalive frames to the switch every FKA advertisement period value (this value is obtained from unsolicited Discovery Advertisements received from the switch). After receiving a keepalive frame, the switch maintains the status of the virtual link. If the switch fails to receive a keepalive frame within 2.5 FKA advertisement periods, it deletes the virtual link. The same as ENodes, VFC interfaces in NP mode use the FKA advertisement period value learned from the peer switch instead of that configured on the local switch. Configuration restrictions and guidelines When you configure the FKA advertisement period value, follow these restrictions and guidelines: As specified in FC-BB-5, the upper limit of the FKA advertisement period value is 90 seconds. The switch allows a maximum FKA advertisement period value of 600 seconds. When the switch interoperates with servers, storage devices, or other vendors' switches, you cannot configure the 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 14

21 recommends that you increase the FKA advertisement period to a value between 60 and 90 seconds to avoid service interruption if there are many configurations on the switch. For more information about ISSU, see Fundamentals Configuration Guide. Use values greater than 90 in the case of an ISSU reboot on a switch operating in standalone mode or in IRF mode but without subordinate switches. In this case, the switch cannot send unsolicited 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. To ensure service continuity during an active/standby switchover or ISSU reboot on an NPV switch, you must also adjust the FKA advertisement period value on the upstream FCF switch. This is because the FKA advertisement period value configured on the NPV switch affects only its VFC interfaces in F mode and connected ENodes, and its VFC interfaces in NP mode use the FKA advertisement period value learned from the upstream FCF switch. FCoE traffic will be interrupted during an ISSU reboot on an access FCF switch or NPV switch operating in standalone mode or in IRF mode but without subordinate switches. This is because an access FCF switch or NPV switch will connect to servers, storage devices, or other vendor's switches and its FKA advertisement period cannot be longer than 90 seconds. An ISSU reboot on a switch operating in standalone mode or in IRF mode but without subordinate switches takes a longer time than 225 (2.5*90) seconds. Therefore, FCoE traffic will be interrupted during the ISSU reboot because the virtual link is deleted after the peer fails to receive an unsolicited Discovery Advertisement within 225 seconds. To configure an FKA advertisement period value: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure an FKA advertisement period value. fcoe fka-adv-period fka-adv-period The default setting is 8 seconds. 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: The VFC interface FCF priority is used in the fcf priority field in an unsolicited Discovery Advertisement. The system FCF priority is used in the fcf priority field in a solicited Discovery Advertisement. An ENode selects the FCF switch with the highest priority from the FCF switches sending Discovery Advertisements and sends a FLOGI request to it for login. The FCF priority is effective only on a VFC interface connected to an ENode (VFC interface in F mode). Configuring the system FCF priority Step Command Remarks 1. Enter system view. system-view N/A 15

22 Step Command Remarks 2. Configure the system FCF priority. fcoe global fcf-priority priority The default setting is 128. The configuration takes effect on all VFC interfaces in F mode. Configuring the VFC interface FCF priority Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. 3. Configure the FCF priority for the VFC interface. interface vfc interface-number fcoe fcf-priority priority N/A The default setting is 128. The configuration takes effect on a VFC interface only when it operates in F mode. Displaying and maintaining VFC interfaces and FIP Execute display commands in any view. Task Display VFC interface information. Display FCoE global configuration. Command display interface [ vfc [ interface-number ] ] [ brief [ description ] ] display fcoe Clear the statistics for VFC interfaces. reset counters interface [ vfc [ number ] ] VFC interfaces and FIP configuration example Network requirements As shown in Figure 12, use the FCoE solution in a data center combining a LAN and a SAN to reduce the number of devices, network adapters, and cables. 16

23 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. 1. Configure Switch A: # Create VSAN 10 and configure Switch A to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 10 [SwitchA-vsan10] quit # Create interface VFC 1, bind it to interface Ten-GigabitEthernet 1/0/1, and assign it to VSAN 10 as a trunk port. [SwitchA] interface vfc 1 [SwitchA-Vfc1] bind interface ten-gigabitethernet1/0/1 [SwitchA-Vfc1] port trunk vsan 10 [SwitchA-Vfc1] quit # Create interface VFC 2, configure it to operate in E mode, bind it to interface Ten-GigabitEthernet 1/0/2, and assign it to VSAN 10 as a trunk port. [SwitchA] interface vfc 2 [SwitchA-Vfc2] fc mode e [SwitchA-Vfc2] bind interface ten-gigabitethernet1/0/2 [SwitchA-Vfc2] port trunk vsan 10 [SwitchA-Vfc2] 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 [SwitchA-Ten-GigabitEthernet1/0/1] quit # Configure interface Ten-GigabitEthernet 1/0/2 to allow VLAN

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 Configure Switch B: # Create VSAN 10 and configure Switch B to operate in FCF mode. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 10 [SwitchB-vsan10] quit # Create interface VFC 1, configure it to operate in E mode, bind it to interface Ten-GigabitEthernet 1/0/2, and assign it to VSAN 10 as a trunk port. [SwitchB] interface vfc 1 [SwitchB-Vfc1] fc mode e [SwitchB-Vfc1] bind interface ten-gigabitethernet1/0/2 [SwitchB-Vfc1] port trunk vsan 10 [SwitchB-Vfc1] quit # Configure interface Ten-GigabitEthernet 1/0/2 to allow VLAN 20. [SwitchB] interface ten-gigabitethernet1/0/2 [SwitchB-Ten-GigabitEthernet1/0/2] port link-type trunk [SwitchB-Ten-GigabitEthernet1/0/2] port trunk permit vlan 20 [SwitchB-Ten-GigabitEthernet1/0/2] quit # Enable FCoE for VLAN 20 and map it to VSAN 10. [SwitchB] vlan 20 [SwitchB-vlan20] fcoe enable vsan 10 18

25 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 switch assigns FC addresses to the N_Ports connected to it. The static mode avoids network flappings, but it is applicable only to simple, small-sized networks. Dynamic mode A principal switch is automatically elected to assign domain IDs to all switches in the network, and then each switch assigns FC addresses to the N_Ports connected to it. The dynamic mode enables centralized network management and is applicable to large-sized networks. Figure 13 Fabric setup workflows The following section details each process in the fabric setup workflows. Principal switch selection During the dynamic fabric building process, it is the principal switch that assigns domain IDs to all switches in the network. The switch with the highest priority is selected as the principal switch. When multiple switches have the same priority, the switch with the smallest WWN wins. The principal switch selection process is as follows: 1. When the principal switch selection starts, each switch considers itself as the principal switch, records itself in the principal switch information, and starts the Principal Switch Selection Timer (PSST), which is 10 seconds. 2. Before the PSST times out, the switches exchange packets carrying the principal switch information to select a principal switch. On receiving such a packet, a switch compares the priority and WWN of the principal switch carried in the packet against those locally recorded. If the priority carried in the packet is higher, or the priority in the packet is the same and the WWN is smaller, the switch 19

26 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. 3. When the PSST times out, if the locally-recorded principal switch information is the local switch, the switch becomes the principal switch. After the principal switch is selected, the WWN of the principal switch becomes the fabric name. NOTE: During the principal switch selection process, if a switch receives a packet that updates the principal switch information, the switch must record the E_Port receiving the packet. The link relevant to this E_Port is called the "upstream principal link." Domain ID assignment A domain represents a switch and all N_Ports connected to the switch. Each domain must have a domain ID. An FCF switch can automatically assign domain IDs. Alternatively, you can manually configure static domain IDs. If you manually configure static domain IDs, you must assign a unique domain ID to each switch in the fabric. If domain IDs are dynamically assigned, the fabric configuration process is performed to select a principal switch and assign domain IDs. After the principal switch is selected, the principal switch assigns domain IDs to all switches in the fabric. After the fabric configuration process, each switch has a unique domain ID. The dynamic domain ID assignment process is as follows: 1. The principal switch assigns a domain ID to itself. If the principal switch has been configured with a desired domain ID, the principal switch assigns the domain ID to itself. Otherwise, the principal switch assigns the smallest available domain ID to itself. After the principal switch assigns a domain ID to itself, it notifies its downstream switches to request domain IDs from it. 2. After a downstream switch receives the notification, it starts to request a domain ID from the principal switch. If the downstream switch is configured with a desired domain ID, it requests the desired domain ID from the principal switch. 3. After the principal switch receives the domain ID request from the downstream switch, it assigns a domain ID to it and notifies the downstream switch. The principal switch assigns domain IDs following these rules: If the downstream switch requests a desired domain ID that is available, the principal switch assigns the domain ID to the downstream switch. If the downstream switch does not request a desired domain ID or the desired domain ID is not available, the principal switch assigns the smallest available domain ID to the downstream switch. If all available domain IDs have been assigned, the principal switch notifies the downstream switch that no domain ID can be assigned to it. 4. After the downstream switch receives the domain ID assignment notification from the principal switch, it works following these rules: 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 20

27 downstream switch that no domain ID can be assigned, the downstream switch isolates its upstream principal link and brings down the relevant interface. For more information about domain ID types, see "Configuring a domain ID for a switch." Otherwise, the downstream accepts the domain ID assigned by the principal switch and notifies the nearby downstream switch to request a domain ID from the principal switch. 5. Repeat steps 2 through 4 until all downstream switches have been assigned domain IDs. NOTE: During the dynamic domain ID assignment process, if a switch receives the domain ID request on an E_Port, the switch must record the E_Port. The link relevant to this E_Port is called the "downstream principal link." FC address assignment After a switch obtains a domain ID, it can assign FC addresses to N_Ports directly connected. The Domain_ID field in the FC address is the domain ID of the switch, and it does not need assignment. The switch assigns the Area_IDs and Port_IDs following these guidelines: If you bind the WWN of an N_Port to an FC address, the switch assigns the bound FC address to the N_Port. If the N_Port itself has a desired FC address, the switch assigns the desired FC address, if available. If the N_Port itself does not have a desired FC address or the desired FC address is unavailable, the switch assigns the smallest available 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. Building a fabric statically Tasks at a glance (Required.) Configuring VFC interfaces and FIP (Required.) Enabling or disabling the fabric configuration function (Required.) Setting a fabric name (Optional.) Configuring the allowed domain (Required.) Configuring a domain ID for a switch (Optional.) Configuring the mapping between the N_Port WWN and the FC address Remarks N/A To statically build a fabric, you must disable the fabric configuration function. When statically building a fabric, you must manually configure the fabric name, and make sure all switches in the fabric are configured with the same fabric name. N/A When statically building a fabric, you must manually configure a domain ID for each switch. N/A 21

28 Tasks at a glance (Optional.) Configuring the fabric timers Remarks N/A Building a fabric dynamically Tasks at a glance (Required.) Configuring VFC interfaces and FIP (Required.) Enabling or disabling the fabric configuration function (Optional.) Setting the switch priority (Optional.) Configuring the allowed domain (Optional.) Configuring a domain ID for a switch (Optional.) Configuring the mapping between the N_Port WWN and the FC address (Optional.) Configuring the fabric timers (Optional.) Configuring the fabric reconfiguration (Optional.) Configuring a VFC interface to reject incoming RCF requests Remarks N/A To dynamically build a fabric, you must enable the fabric configuration function. Principal switch selection relies on the switch priority. N/A When dynamically building a fabric, you can configure desired domain IDs for switches. N/A N/A N/A N/A Enabling or disabling the fabric configuration function After being enabled with the fabric configuration function, FCF switches exchange messages to select the principal switch. Then the principal switch dynamically assigns domain IDs to all switches in the fabric. Therefore, to dynamically build a fabric, you must enable the fabric configuration function on switches. To statically set up a fabric, you must disable the fabric configuration function on switches and manually configure domain IDs for the switches. To enable or disable the fabric configuration function: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Enable the fabric configuration function. 4. Disable the fabric configuration function. domain configure enable undo domain configure enable Enable or disable the function for all switches in the VSAN as required. By default, the fabric configuration function is enabled. 22

29 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 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure a fabric name. fabric-name name By default, the fabric name is null. If the user does not configure a fabric name, the switch WWN is used as the fabric name after FCoE is enabled. Setting the switch priority The priority value for FCF switches is in the range of 1 to 254. The smaller the value, the higher the priority. The FCF switch with the highest priority will be elected as the principal switch. The priority is configured on a per-vsan basis, and one FCF switch may have different priorities in different VSANs. In a stable fabric, the configured priority does not take effect immediately. Therefore, the running priority of a switch might be different from the configured priority. To validate the configured priority, use the domain restart disruptive command to perform a disruptive reconfiguration. After a disruptive reconfiguration, the running priority could still be different from the configured priority. See the following possibilities on the principal and a non-principal switch, depending on the configured priority value, as shown in Table 2. Table 2 Configured priority and running priority mappings Configured priority 2 > 2 Running priority Principal switch Same as the configured priority. Non-principal switch 3. Principal switch 2. Non-principal switch Same as the configured priority. To set the switch priority: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure a priority value for the switch. priority value By default, the priority value of a switch is

30 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. If the allowed domain ID list configured does not include any of the already assigned domain IDs or manually configured domain IDs, the configuration will fail. Non-principal switch The manually configured domain ID must be within the allowed domain ID list. Otherwise, the configuration will fail. The principal switch must assign the switch a domain ID within the allowed domain ID list. Otherwise, the switch refuses the assigned domain ID and isolates its interface connected to the principal switch. 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: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure the allowed domain IDs for the switch. allowed-domain-id domain-id-list By default, the allowed domain IDs are 1 to 239. Configuring a domain ID for a switch In different scenarios, the configured domain ID has different meanings. In a statically built fabric, the configured domain ID is the actual domain ID of the switch. In a dynamically built fabric, the configured domain ID is desired by the switch but may not be the actual domain ID. To statically build a fabric, you must manually configure a domain ID for each switch. To dynamically build a fabric, you can configure a desired domain ID for a switch, but the domain ID assigned to the switch may not be the desired one. The configured domain ID can be of a static or preferred type. In a statically built fabric, the two types make no difference. In a dynamically built fabric, when a non-principal switch fails to obtain the desired domain ID from the principal switch, the non-principal switch can use another domain ID assigned by the principal 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 Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 24

31 Step Command Remarks 3. Configure a domain ID for the switch. domain-id domain-id { preferred static } By default, the domain ID of a switch is 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. The WWN of an N_Port can be bound to only one FC address, and vice versa. The N-Port here indicates an N_Port on a node or an NP_Port on an NPV switch. To bind the WWN of an N_Port to an FC address: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Bind the WWN of an N_Port to an FC address. wwn wwn-value area-port-id area-port-id-value By default, no binding is configured. Configuring the fabric timers The fabric operation involves the following timers: Distributed service timeout period Error detection timeout period Resource allocation timeout period For more information about these timers, see FC-related protocols and standards. You can configure fabric timers by using one of the following ways: Configure the timers in system view, and the configuration takes effect for all VSANs. 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 1. Enter system view. system-view N/A 2. Configure the global distributed service timeout period. fc timer distributed-services value By default, the distributed service timeout period is 5000 milliseconds. 25

32 Step Command Remarks 3. Configure the global error detection timeout period. 4. Configure the global resource allocation timeout period. fc timer error-detect value fc timer resource-allocation value By default, the error detection timeout period is 2000 milliseconds. By default, the resource allocation timeout period is milliseconds. Configuring the fabric timers in VSAN view Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure the distributed service timeout period for the VSAN. 4. Configure the error detection timeout period for the VSAN. 5. Configure the resource allocation timeout period for the VSAN. timer distributed-services value timer error-detect value timer resource-allocation value By default, the distributed service timeout period is 5000 milliseconds. By default, the error detection timeout period is 2000 milliseconds. By default, the resource allocation timeout period is milliseconds. Configuring the fabric reconfiguration IMPORTANT: The fabric reconfiguration function takes effects only when the fabric configuration function is enabled. The fabric reconfiguration occurs in the case of a network reconstruction (for example, two fabrics are merged) or external intervention (for example, the administrator uses a command to initiate reconfiguration). The fabric reconfiguration triggers principal switch selection, domain ID assignment, and FC address assignment throughout the fabric. The fabric reconfiguration includes the following categories: 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. During the reconfiguration procedure, each switch tries to save the last running data for its domain ID to remain unchanged. Thus, data transmission in the fabric is not disrupted. Depending on the triggering conditions, the fabric reconfiguration falls into auto reconfiguration and manual reconfiguration. When two fabrics are merged: The switches automatically perform a disruptive reconfiguration if the domain ID lists overlap. 26

33 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. When the principal switch in a fabric is down, the system automatically performs a non-disruptive reconfiguration. Configuring the auto fabric reconfiguration function Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Enable the auto fabric reconfiguration function. domain auto-reconfigure enable By default, the auto fabric reconfiguration function is disabled. Manually initiating the fabric reconfiguration Step Command 1. Enter system view. system-view 2. Enter VSAN view. vsan vsan-id 3. Initiate the fabric reconfiguration. domain restart [ disruptive ] Configuring a VFC interface to reject incoming RCF requests In a stable fabric, to avoid unnecessary disruptive reconfigurations, you can configure a VFC interface to reject the RCF requests received from a specific VSAN by replying with a reject message. With this feature, the interface on which an RCF request is received is isolated. To configure a VFC interface to reject the received RCF requests: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. interface vfc interface-number N/A 3. Configure the VFC interface to reject the received RCF requests. fc domain rcf-reject vsan vsan-id By default, a VFC interface does not reject the received RCF requests. Displaying and maintaining a fabric Execute display commands in any view. 27

34 Task Display the domain information of the specified VSAN. Display the list of domain IDs dynamically allocated in the specified VSAN. Display fabric timers. Command display fc domain [ vsan vsan-id ] display fc domain-list [ vsan vsan-id ] display fc timer [ distributed-services error-detect resource allocation ] [ vsan vsan-id ] Display node login information. display fc login [ vsan vsan-id ] [ count ] Display the SCR table for an N_Port. display fc scr-table [ vsan vsan-id ] Display name service database information. display fc name-service database [ vsan vsan-id [ fcid fcid ] ] [ verbose ] Display ESS negotiation results. display fc ess [ vsan vsan-id ] Static fabric building configuration example Network requirements As shown in Figure 14, use the static approach to build a fabric. Figure 14 Network diagram Configuration procedure 1. Configure Switch A: # Disable the fabric configuration function and configure Switch A to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 1 [SwitchA-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 1. [SwitchA-vsan1] domain-id 1 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y 2. Configure Switch B: # Disable the fabric configuration function and configure Switch B to operate in FCF mode. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 1 28

35 [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 1. Verify the configurations on Switch A. [SwitchA-vsan1] display fc domain vsan 1 Domain Information of VSAN 1: Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1A:1A Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 1 Configuration information: Domain configure: Disabled Domain auto-reconfigure: Disabled Fabric name: 11:11:11:11:11:11:11:11 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 Verify the configurations on Switch B. [SwitchB-vsan1] display fc domain vsan 1 Domain Information of VSAN 1: Running time information: State: Stable Switch WWN: 48:33:43:2d:46:43:1B:1B Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 2 Configuration information: Domain configure: Disabled Domain auto-reconfigure: Disabled Fabric name: 11:11:11:11:11:11:11:11 Priority: 128 Domain ID: 2 (static) 29

36 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. Figure 15 Network diagram Configuration procedure 1. Configure Switch A: # Enable the fabric configuration function (optional, because this function is enabled by default), and configure Switch A to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Enable FCoE for VLAN 10 and map it to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit # Configure the domain ID as 11. [SwitchA-vsan1] domain-id 11 preferred Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchA-vsan1] quit # Create interface VFC 1, bind it to interface Ten-GigabitEthernet 4/0/2, configure it to operate in E mode, and assign it to VSAN 1 as a trunk port. [SwitchA] interface Vfc 1 [SwitchA-Vfc1] bind interface ten-gigabitethernet4/0/2 30

37 [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.) 2. 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. (Details not shown.) # Enable the fabric configuration function (optional, because this function is enabled by default), and configure Switch B to operate in FCF mode. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] vsan 1 [SwitchB-vsan1] domain configure enable # Set the priority value to 1, so that Switch B can be selected as the principal switch. [SwitchB-vsan1] priority 1 3. Configure Switch C: # Enable the fabric configuration function (optional, because this function is enabled by default), and configure Switch C to operate in FCF mode. <SwitchC> system-view [SwitchB] fcoe-mode fcf [SwitchC] vsan 1 [SwitchC-vsan1] domain configure enable # Configure the domain ID as 13. [SwitchC-vsan1] domain-id 13 preferred Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y 4. Configure Switch D: # Enable the fabric configuration function (optional, because this function is enabled by default), and configure Switch D to operate in FCF mode. <SwitchD> system-view [SwitchD] fcoe-mode fcf [SwitchD] vsan 1 [SwitchD-vsan1] domain configure enable # Configure the domain ID as 14. [SwitchD-vsan1] domain-id 14 preferred Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y Verifying the configurations 1. Verify the configurations on Switch A: # Display the domain information of VSAN 1. [SwitchA-vsan1] display fc domain vsan 1 Domain Information of VSAN 1: 31

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 Vfc 1 Downstream Vfc 2 The output shows that the domain configuration is complete and that the principal switch assigns domain ID 11 to Switch A. # Display the domain ID list of VSAN 1. [SwitchA-vsan1] display fc domain-list vsan 1 Domain list of VSAN 1: Number of domains: 4 Domain ID WWN 0x01(1) 48:33:43:2d:46:43:1B:1B [Principal] 0x0b(11) 48:33:43:2d:46:43:1A:1A [Local] 0x0d(13) 48:33:43:2d:46:43:1C:1C 0x0e(14) 48:33:43:2d:46:43:1D:1D The output shows that Switch B becomes the principal switch and assigns the smallest domain ID 1 to itself. 32

39 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. The VSAN technology delivers the following benefits: Improved security VSANs are isolated from each other. Improved adaptability Each VSAN independently runs and provides services. Different VSANs can use the same address space so that network capacity is improved. Flexibility You can assign interfaces to different VSANs without changing the physical connections of the SAN. VSAN fundamentals VFC interfaces can only work as trunk ports. A trunk port can belong to multiple VSANs. Trunk VSAN in an FC network The trunk VSAN technology implements logical isolation among VSANs. The trunk VSAN works as follows: The trunk VSAN adds a Virtual Fabric Tagging Header (VFT_Header, also known as VSAN tag) to the FC frames. The VFT_Header contains a VF_ID (also known as "VSAN ID") field to indicate the VSAN of the FC frames. In this way, FC frames within different VF_IDs are contained in their respective VSANs, and different VSANs cannot communicate with each other. VSAN tags are added to and removed from an FC frame during transmission. A switch supports multiple VSANs one physical interface, thus reducing physical connections and implementing logical isolation in a physically connected SAN. Figure 16 shows a typical trunk VSAN. The F_Ports in blue on switches are configured as trunk ports and assigned to VSAN 1, and the F_Ports in purple are configured as trunk ports and assigned to VSAN 2. The E_Ports are configured with trunk VSANs 1 and 2. When servers read the disks, the N_Ports of different servers send FC frames without VFT_Headers to the F_Ports on FC switch Switch A. Switch A searches for the outgoing interfaces in the FIB table of the VSAN that each F_Port belongs to. These F_Ports use the same E_Port as the outgoing interface. When the frames are forwarded out of the E_Port, they are tagged with the VFT_Header of VSAN 1 and VSAN 2 and travel across multiple VSAN-capable switches to the E_Port of FC switch Switch B. According to the VFT_Headers, Switch B searches for the outgoing interfaces in the FIB tables of the VSANs, and forwards them to the F_Ports. Then, the F_Ports remove the VFT_Headers and send the frames to the N_Ports of different disk devices. The frames from the disk devices to the server are processed in the same way and finally reach the servers. 33

40 Figure 16 Trunk VSAN network VSAN 1 VSAN 1 Server A N_Port FC Fabric N_Port Disk A F_Port F_Port F_Port E_Port E_Port F_Port Server B FC switch A FC switch 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. The trunk VSAN technology reduces the number of physical connections, actually implementing logical isolation in a physical network. Trunk VSAN in an FCoE network FCoE carries FC over Ethernet. In an FCoE network, VSANs in FC need to be mapped to VLANs as configured by the user, and the FIB table for a VSAN is also stored to the relevant VLAN. FCoE packets use VLAN_Header in replace of VFT_Header in FC packets and are forwarded based on the VLAN ID in VLAN_Header. A VFC interface can only work as a trunk port, and the bound Ethernet interface must also be configured as a trunk port and has the same trunk VLAN list as the VFC interface. In this manner, an FCoE packet transmitted from a VFC can use the VLAN ID in VLAN_Header to identify the VLAN to which it belongs. Creating a VSAN Initially, only the default VSAN (VSAN 1) exists. You cannot create or delete VSAN 1. You can create VSANs 2 to To create a VSAN: Step Command Remarks 1. Enter system view. system-view N/A 2. Create a VSAN and enter VSAN view. vsan vsan-id By default, only the default VSAN (VSAN 1) exists. Configuring a trunk VSAN A VFC interface can be assigned to multiple VSANs as a trunk port. If you assign an interface to VSANs as a trunk port multiple times, the final trunk VSAN list is the set of all the VSANs to which you have assigned the interface. To assign a VFC interface to the specified VSANs as a trunk port: 34

41 Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. interface vfc interface-number N/A 3. Assign the VFC interface to the specified VSANs as a trunk port so that the interface allows the specified VSANs to pass through. port trunk vsan vsan-id-list By default, a VFC interface does not belong to any VSAN as a trunk port. When you assign a VFC interface to a VSAN as a trunk port, the VSAN may not exist. Displaying and maintaining VSAN Execute display commands in any view. Task Display the member ports of the VSAN. Command display vsan [ vsan-id ] port-member VSAN configuration example Network requirements As shown in Figure 17, configure the SAN to satisfy the following requirements: 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 17 Network diagram Configuration considerations To satisfy these requirements, divide the SAN into two VSANs, VSAN 10 and VSAN 20. Each VSAN contains a server and disk devices that can exchange data. 35

42 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 mode, and assign the three interfaces as trunk ports to VSAN 10 or VSAN 20. Configure the interfaces connecting Switch A and Switch B to operate in E mode, configure the trunk mode as on for the two interfaces, and assign the interfaces to VSANs 10 and 20 as trunk ports, so that the link between the two FCF switches can send and receive the frames of the two VSANs at the same time. Configuration procedure 1. Configure Switch A: # Configure Switch A to operate in FCF mode, create VSAN 10, enable FCoE for VLAN 10, and map VLAN 10 to VSAN 10. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 10 [SwitchA-vsan10] quit [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 10 [SwitchA-vlan10] quit # Create VSAN 20, enable FCoE for VLAN 20, and map VLAN 20 to VSAN 20. [SwitchA] vsan 20 [SwitchA-vsan20] quit [SwitchA] vlan 20 [SwitchA-vlan20] fcoe enable vsan 20 [SwitchA-vlan20] quit # Create interface VFC 102 (downlink interface), bind it to interface Ten-GigabitEthernet 1/0/2, configure it to operate in F mode, and assign it to VSAN 10 as a trunk port. [SwitchA] interface Vfc 102 [SwitchA-Vfc102] fc mode f [SwitchA-Vfc102] bind interface Ten-GigabitEthernet1/0/2 [SwitchA-Vfc102] port trunk vsan 10 [SwitchA-Vfc102] quit # Create interface VFC 101 (downlink interface), bind it to interface Ten-GigabitEthernet 1/0/1, configure it to operate in F mode, and assign it to VSAN 20 as a trunk port. [SwitchA] interface Vfc 101 [SwitchA-Vfc101] fc mode f [SwitchA-Vfc102] bind interface Ten-GigabitEthernet1/0/1 [SwitchA-Vfc101] port trunk vsan 20 [SwitchA-Vfc101] quit # Create interface VFC 100 (uplink interface), bind it to interface Ten-GigabitEthernet 1/0/3, configure it to operate in E mode, and assign it to VSANs 10 and 20 as a trunk port. [SwitchA] interface Vfc 100 [SwitchA-Vfc102] bind interface Ten-GigabitEthernet1/0/3 [SwitchA-Vfc100] fc mode e [SwitchA-Vfc100] port trunk vsan

43 2. Configure Switch B in the same way as you configure Switch A. (Details not shown.) Verifying the configurations 1. 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: Trunk Ports: Vfc 100 Vfc 102 VSAN 20: Access Ports: Trunk Ports: Vfc 100 Vfc Verify the configurations on Switch B. The output on Switch B is the same as that on Switch A. 37

44 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. Routing provides the path information that guides the forwarding of packets. Routing table and FIB table An FCF switch determines the best routes by using its routing table and sends those routes to the FIB table, which guides packet forwarding. An FCF switch maintains one routing table and one FIB table for each VSAN. Routing table contents The routing table saves the routes discovered by various routing protocols. Routes in a routing table fall into the following types: Direct routes Routes discovered by link layer protocols Static routes Routes manually configured by the administrator FSPF routes Routes discovered by the Fabric Shortest Path First (FSPF) protocol To display summary information about a routing table, use the display fc routing-table command as follows: <Sysname> display fc routing-table vsan 1 Routing Table: VSAN 1 Destinations : 6 Routes : 6 Destination/mask Protocol Preference Cost Interface 0x020000/8 FSPF Vfc100 0x120000/8 STATIC 10 0 Vfc200 0xfffc01/24 DIRECT 0 0 InLoop0 0xfffffa/24 DIRECT 0 0 InLoop0 0xfffffc/24 DIRECT 0 0 InLoop0 0xfffffd/24 DIRECT 0 0 InLoop0... A route entry includes the following key items: Destination Destination address of an FC frame. mask Together with the destination address, specifies the destination node or the domain address of an FCF switch. A logical AND operation between the destination address and the network mask yields the domain address of the destination node or FCF switch. For example, if the destination address is 0x and the mask is 0xFF0000, the domain address of the destination node or FCF switch is 0x 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. 38

45 FIB table contents 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. The optimal route is the one with the highest priority (smallest preference value). Cost Cost of the route. For routes to the same destination and with the same preference, the route with the lowest cost is the optimal one. The cost of direct routes is 0. The costs of static routes and FSPF routes are configurable. Interface Specifies the interface through which a matching FC frame is to be forwarded out of the FCF switch. Each entry in the FIB table specifies which physical interface a packet destined for a certain destination node or FCF switch should go out through to reach the next hop (the next FCF switch) or the directly-connected destination node. To display FIB table information, use the display fc fib command as follows: <Sysname> display fc fib vsan 1 FC FIB information in VSAN 1: Destination count: 2 FIB entry count: 2 Destination/Mask 0xff0101/24 Interface InLoop0 The key items Destination, Mask, and Interface in an FIB table have the same meanings as those in a routing table. Direct routes The sources of direct routes include well-known addresses and the FC addresses that the local switch assigns to directly-connected N_Ports. The well-known addresses are usually used to access FCF switches. For usage of common well-known addresses, see "Appendix B Well-known fabric addresses." All well-known addresses are added to the routing table as the destination addresses of direct routes. In such a direct route, the destination address is a well-known address, the mask is 0xFFFFFF, and the outgoing interface is InLoop0. 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. Static routes Static routes are manually configured by the administrator. After you configure a static route, an FC frame to the specified destination is forwarded along the path specified by the administrator. In a simple network, static routes are enough for implementing network connectivity. By properly setting and using static routes, you can improve network performance and guarantee bandwidth for critical network applications. 39

46 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. When you configure multiple equal-cost static routes to the same destination but with different outgoing interfaces, equal-cost routes are generated. FSPF routes Basic concepts As a route selection protocol based on link states, FSPF can automatically calculate the best path between any two switches in a fabric. FSPF has the following characteristics: Can be used for any topology. Supports equal-cost routes. Performs topology calculations on a per-vsan basis. Runs only on E_Ports and provides a loop-free topology. Provides a topology database on each switch to track the state of all links. Uses the Dijkstra algorithm to calculate routes. Provides fast convergence in the event of topology changes. LSDB The link state database (LSDB) is used to store global topology information for switches and link state information of all switches in link state records (LSRs). LSR An LSR describes information about all link states between a switch and its directly connected switches. Each LSR generated by a switch is called an LSR instance. LSRs generated by all switches comprise the LSDB. An LSR contains one or more pieces of link state information, including the following: FSPF packet types LSR hold time. Domain ID of the switch advertising the LSR. LSR instance number. Every time an LSR is updated, the instance number increments by 1. 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. The route selection algorithm uses this value to determine the best route. The interface cost is configurable. The following protocol packets are used in FSPF: Hello packets Sent periodically to discover and maintain FSPF neighbors. Link state update (LSU) Advertises local link state information in LSRs to the neighboring switches. Link state acknowledgment (LSA) Acknowledges the received LSR. 40

47 How FSPF works After receiving an LSU, a switch needs to acknowledge its LSR with an LSA. Otherwise, the neighboring switch retransmits the LSR. FSPF works as follows: 1. The switch periodically sends hello packets to establish neighbor relationships with other switches. 2. After establishing neighbor relationships, the switches synchronize LSDBs by exchanging all LSRs in their respective LSDBs. A switch carries LSRs in LSUs and acknowledges received LSRs with LSAs. 3. After the synchronization is complete, the LSDB in each switch contains LSRs of all switches in the fabric. 4. The switch uses the Dijkstra algorithm to calculate the shortest paths to other switches based on the local LSDB. Then, it determines the outgoing interfaces and generates an FSPF routing table. 5. When the network topology or link state changes, the switch floods a new LSR to its neighboring switches. After receiving the LSR, the neighboring switches add it to their LSDBs and flood it to their respective neighbors. In this way, all switches in the fabric receive that LSR. 6. Local LSDB updating results in SPF calculation. The calculated shortest path tree list is updated to the FSPF routing table. Configuring static routes for FC Configuration restrictions and guidelines The destination address of a static FC route is in the range of to EFFFFF (hexadecimal). You cannot configure a route with a well-known address as the destination address. The outgoing interface of a static FC route can only be a VFC interface. If you configure two routes with the same destination address, mask, and outgoing interface, but with different costs, the route configured later applies. The maximum number of static routes allowed in a VSAN is 256. Configuration procedure To configure a static FC route: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure a static FC route. fc route-static fcid { mask mask-length } interface-type interface-number [ cost cost-value ] By default, no static FC route exists. Configuring FSPF FSPF is enabled by default. Generally, you do not need to make special configurations. You can change FSPF parameters on a per-vsan or per-interface basis as needed. 41

48 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: Configuring the FSPF cost Configuring the hello interval Configuring the dead interval Configuring the LSR retransmission interval for interfaces Disabling FSPF for an interface (Optional.) Configuring FSPF GR in system view: Configuring the GR Restarter Configuring the GR Helper Enabling FSPF FSPF-related functions can work in a VSAN only after you enable FSPF for the VSAN. To enable FSPF: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Enable FSPF for the VSAN. fspf enable By default, FSPF is enabled after a VSAN is created. Configuring the shortest SPF calculation interval When the LSDB changes, SPF calculations occur and consume CPU resources. To prevent frequent SPF calculations from overconsuming the CPU, you can configure the shortest SPF calculation interval. The shortest SPF calculation interval defines the minimum interval between two consecutive SPF calculations. A smaller value means that FSPF responds faster to fabric changes by recalculating routes in a VSAN, but it requires more CPU resources. To configure the shortest SPF calculation interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure the shortest SPF calculation interval. fspf spf-hold-time value The default setting is 0 second. 42

49 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 Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure the minimum LSR receiving interval. fspf min-ls-arrival value The default setting is 1 second. Configuring the minimum LSR refresh interval The minimum LSR refresh interval specifies the interval at which LSRs are refreshed. To reduce SPF calculations and LSR flooding in a fabric caused by frequent LSR refreshing, the switch cannot refresh local LSRs within this interval. To configure the minimum LSR refresh interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure the minimum LSR refresh interval. fspf min-ls-interval value The default setting is 5 seconds. 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. To configure the interface FSPF cost: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. 3. Configure the FSPF cost for the VFC interface in a specified VSAN. interface vfc interface-number fspf cost value vsan vsan-id N/A The default setting is

50 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. To configure the interface hello interval: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. interface vfc interface-number N/A 3. Configure the hello interval for the VFC interface in a specified VSAN. fspf hello-interval value vsan vsan-id The default setting is 20 seconds. Configuring the dead interval for an interface After two switches establish a neighbor relationship, they send hello packets at the hello interval to each other to maintain the neighbor relationship. The dead interval specifies the interval during which at least one hello packet must be received from a neighbor before the neighbor is considered to be nonexistent and is removed. 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 1. Enter system view. system-view N/A 2. Enter VFC interface view. interface vfc interface-number N/A 3. Configure the dead interval for the VFC interface in a specified VSAN. fspf dead-interval value vsan vsan-id The default setting is 80 seconds. Configuring the LSR retransmission interval for interfaces The LSR retransmission interval specifies the time to wait for an LSR acknowledgement from the neighbor before retransmitting the LSR. To configure the LSR retransmission interval: Step Command Remarks 1. Enter system view. system-view N/A 44

51 Step Command Remarks 2. Enter VFC interface view. interface vfc interface-number N/A 3. Configure the LSR retransmission interval for the VFC interface in a specified VSAN. fspf retransmit-interval value vsan vsan-id The default setting is 5 seconds. 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. To disable FSPF on an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. interface vfc interface-number N/A 3. Enable FSPF for the VFC interface in a specified VSAN. fspf silent vsan vsan-id By default, FSPF is enabled on all VFC interfaces. 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 GR Helper The GR Restarter's neighboring device that assists in the GR process Configuring the GR Restarter Step Command Remarks 1. Enter system view. system-view N/A 2. Enable FSPF GR. fspf graceful-restart By default, FSPF GR is disabled. 3. Configure the maximum interval for FSPF GR. fspf graceful-restart interval interval-value The default setting is 120 seconds. Configuring the GR Helper Step Command Remarks 1. Enter system view. system-view N/A 2. Enable FSPF GR Helper. fspf graceful-restart helper By default, FSPF GR Helper is enabled. 45

52 Displaying and maintaining FC routing and forwarding Execute display commands in any view. Task Display FC routing table information. Display FC FIB table information. Display FC Exchange table information Command display fc routing-table [ vsan vsan-id ] [ statistics verbose ] display fc routing-table vsan vsan-id fc-id [ mask mask-length ] [ verbose ] display fc fib [ fcid [ mask-length ] ] vsan vsan- id display fc exchange { link protocol } [ slot slot-number ] display fc exchange link verbose [ slot slot-number ] [ exid exid ] Display FSPF neighbor information. display fspf neighbor [ vsan vsan-id ] Display link state database information. display fspf lsdb [ vsan vsan-id ] Display FSPF GR state information. display fspf graceful-restart [ vsan vsan-id ] Display FSPF statistics. display fspf statistics [ vsan vsan-id ] Clear FSPF statistics. reset fspf counters [ vsan vsan-id ] Static FC routing configuration example Network requirements As shown in Figure 18, configure static routes to enable any two FCF switches to communicate with each other. Figure 18 Network diagram Switch B Domain ID: 2 VFC200 XGE1/0/2 VFC201 XGE1/0/3 VFC100 XGE1/0/1 VFC300 XGE1/0/3 Switch A Switch C Domain ID: 1 Domain ID: 3 46

53 Configuration procedure 1. 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 # Enable the fabric configuration function. [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Configure the domain ID as 1. [SwitchA-vsan1] domain-id 1 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchA-vsan1] quit # Enable FCoE for VLAN 10 and bind VLAN 10 to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit # Configure two static routes. [SwitchA-vsan1] fc route-static Vfc100 [SwitchA-vsan1] fc route-static Vfc Configure Switch B: # Configure Switch B to operate in FCF mode and bind interfaces VFC 200 and VFC 201 to interfaces Ten-GigabitEthernet 1/0/2 and Ten-GigabitEthernet 1/0/3, respectively. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchB] interface Vfc 200 [SwitchB-Vfc200] bind interface Ten-GigabitEthernet1/0/2 [SwitchB-Vfc200] fc mode e [SwitchB-Vfc200] port trunk vsan 1 [SwitchB-Vfc200] quit [SwitchB] interface Vfc 201 [SwitchB-Vfc201] bind interface Ten-GigabitEthernet1/0/3 [SwitchB-Vfc201] fc mode e [SwitchB-Vfc201] port trunk vsan 1 [SwitchB-Vfc201] quit # Enable the fabric configuration function. [SwitchB] vsan 1 [SwitchB-vsan1] domain configure enable # Configure the domain ID as 2. 47

54 [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. [SwitchB-vsan1] fc route-static Vfc200 [SwitchB-vsan1] fc route-static Vfc Configure Switch C: # Configure Switch C to operate in FCF mode and bind interface VFC 300 to interface Ten-GigabitEthernet 1/0/3. <SwitchC> system-view [SwitchC] fcoe-mode fcf [SwitchC] interface Vfc 300 [SwitchC-Vfc300] bind interface Ten-GigabitEthernet1/0/3 [SwitchC-Vfc300] fc mode e [SwitchC-Vfc300] port trunk vsan 1 [SwitchC-Vfc300] quit # Enable the fabric configuration function. [SwitchC] vsan 1 [SwitchC-vsan1] domain configure enable # Configure the domain ID as 3. [SwitchC-vsan1] domain-id 3 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchC-vsan1] quit # Enable FCoE for VLAN 10 and bind VLAN 10 to VSAN 1. [SwitchC] vlan 10 [SwitchC-vlan10] fcoe enable vsan 1 [SwitchC-vlan10] quit # Configure two static routes. [SwitchC-vsan1] fc route-static Vfc300 [SwitchC-vsan1] fc route-static Vfc300 Verifying the configurations # Display the FC routing table in VSAN 1 on Switch A. [SwitchA-vsan1] display fc routing-table vsan 1 Routing Table: VSAN 1 Destinations : 6 Routes : 6 Destination/mask Protocol Preference Cost Interface 0x020000/8 STATIC 10 0 Vfc100 0x030000/8 STATIC 10 0 Vfc100 0xfffc01/24 DIRECT 0 0 InLoop0 48

55 0xfffffa/24 DIRECT 0 0 InLoop0 0xfffffc/24 DIRECT 0 0 InLoop0 0xfffffd/24 DIRECT 0 0 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 STATIC 10 0 Vfc200 0x030000/8 STATIC 10 0 Vfc201 0xfffc02/24 DIRECT 0 0 InLoop0 0xfffffa/24 DIRECT 0 0 InLoop0 0xfffffc/24 DIRECT 0 0 InLoop0 0xfffffd/24 DIRECT 0 0 InLoop0 # Display the FC routing table in VSAN 1 on Switch C. [SwitchC-vsan1] display fc routing-table vsan 1 Routing Table: VSAN 1 Destinations : 6 Routes : 6 Destination/mask Protocol Preference Cost Interface 0x010000/8 STATIC 10 0 Vfc300 0x020000/8 STATIC 10 0 Vfc301 0xfffc03/24 DIRECT 0 0 InLoop0 0xfffffa/24 DIRECT 0 0 InLoop0 0xfffffc/24 DIRECT 0 0 InLoop0 0xfffffd/24 DIRECT 0 0 InLoop0 # On Switch A, use the fcping command to ping Switch C and check whether Switch C is reachable. [SwitchA-vsan1] fcping fcid fffc03 vsan 1 FCPING fcid 0xfffc03: 128 data bytes, press CTRL_C to break Reply from 0xfffc03: bytes = 128 time = 23 ms Reply from 0xfffc03: bytes = 128 time = 9 ms Reply from 0xfffc03: bytes = 128 time = 19 ms Reply from 0xfffc03: bytes = 128 time = 14 ms Reply from 0xfffc03: bytes = 128 time = 25 ms --- 0xfffc03 fcping statistics packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 9/18/25 ms The output shows that Switch A can reach Switch C. FSPF configuration example Network requirements As shown in Figure 19, configure FSPF to enable the two FCF switches to communicate with each other. 49

56 Figure 19 Network diagram Configuration procedure 1. 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 # Enable the fabric configuration function. [SwitchA] vsan 2 [SwitchA-vsan2] domain configure enable # Configure the domain ID as 1. [SwitchA-vsan2] domain-id 1 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchA-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 # Enable FSPF globally. [SwitchA-vsan2] fspf enable [SwitchA-vsan2] quit # Enable FSPF for interface VFC 100. [SwitchA] interface Vfc 100 [[SwitchA-Vfc100] port trunk vsan 2 [SwitchA-Vfc100] undo fspf silent vsan 2 2. Configure Switch B: # Configure Switch B to operate in FCF mode and bind interface VFC 100 to interface Ten-GigabitEthernet 1/0/1. <SwitchB> system-view [SwitchB] 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 50

57 # 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 # Enable FSPF globally. [SwitchB-vsan2] fspf enable [SwitchB-vsan2] quit # Enable FSPF for interface VFC 100. [SwitchB] interface Vfc 100 [SwitchB-Vfc 100] port trunk vsan 2 [SwitchB-Vfc 100] undo fspf silent vsan 2 Verifying the configurations # Display FSPF neighbor information on Switch A. [SwitchA-Vfc 100] display fspf neighbor FSPF neighbor information of VSAN 2(01): Interface NbrDomain IfIndex NbrIfIndex Dead Time State Vfc x68 0x68 00:01:06 Full # Display information about the FC routing table on Switch A. [SwitchA-Vfc 100] display fc routing-table vsan 2 Routing Table: VSAN 2 Destinations : 5 Routes : 5 Destination/mask Protocol Preference Cost Interface 0x020000/8 FSPF Vfc 100 0xfffc01/24 DIRECT 0 0 InLoop0 0xfffffa/24 DIRECT 0 0 InLoop0 0xfffffc/24 DIRECT 0 0 InLoop0 0xfffffd/24 DIRECT 0 0 InLoop0 # On Switch A, use the fcping command to ping Switch B and check whether Switch B is reachable. [SwitchA-Vfc 100] fcping fcid fffc02 vsan 2 FCPING fcid 0xfffc02: 128 data bytes, press CTRL_C to break. Reply from 0xfffc02: bytes = 128 time = ms Reply from 0xfffc02: bytes = 128 time = ms Reply from 0xfffc02: bytes = 128 time = ms Reply from 0xfffc02: bytes = 128 time = ms Reply from 0xfffc02: bytes = 128 time = ms --- 0xfffc02 fcping statistics

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. 52

59 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. This creates data security risks. 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. Zone database To control access among N_Ports, you can divide N_Ports into different zones as needed, which comprise a zone set. The same N-Ports can form multiple zone sets according to different zone division policies. These zones and zone sets comprise a zone database. Zone database structure The zone database is organized into three levels: zone set, zone, and zone member. Figure 20 Zone database structure In the zone database structure: A zone set is a set of zones. A zone is a set of zone members, which are N_Ports. Zone membership can be identified by the port WWN (pwwn) or FC address of an N_Port. 53

60 Active zone set 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. Each VSAN can have multiple zone sets, but only one zone set can be effective at a time. It is called the "active zone set." Access control over N_Ports is subject to the active zone set. To ensure consistent access control over N_Ports on a fabric-wide basis, you must specify the active zone set by using a command on a local device and distribute it to the entire fabric. When you activate a zone set, a copy of the zone set at the time of activation is created and is called the active zone set. After that, modifications to the zone set do not take effect on the copy until the copy is reactivated. Figure 21 shows the relationship between active and full zone sets. Figure 21 Active and full zone sets 54

61 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. Otherwise, the default zone is not in the active zone set and does not participate in access control among the N_Ports. Distributing zones Distributing zones indicates that a device distributes its active zone set or zone database to all the other devices in the same fabric. The distributing device is called a "manager switch," and all the other devices are called "managed switches." The following distribution types are provided: Complete distribution Distributes both the active zone set and zone database. Incomplete distribution Distributes only the active zone set. Methods of triggering a distribution Trigger a distribution by using one of the following methods: Activate a zone set as the active zone set on a switch by using the zoneset activate command. At the time of activation, the active zone set is distributed to all the other switches. This method determines whether to carry the zone database according to the configured distribution type. Distribute the active zone set and zone database directly by using the zoneset distribute command on a switch. This method performs a complete distribution irrespective of the configured distribution type. Managed switches replace their respective active zone sets or zone databases with the received data, regardless of the distribution types configured on them. For example, if a managed switch receives the active zone set and zone database, it replaces its local active zone set and zone database with them regardless of whether its distribution type is complete distribution. Zone distribution process The manager switch completes data synchronization with each managed switch by using the following packets: Acquire Change Authorization (ACA) Stage Fabric Configuration Update (SFC) Update Fabric Configuration (UFC) Release Change Authorization (RCA) These types of packets implement locking, data synchronization, submission, and unlocking processes, respectively. These processes make sure only one device distributes data as the manager switch when multiple users trigger a data distribution by using commands on different devices at the same time. 55

62 Figure 22 Distribution process The distribution process is as follows: 1. 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. After sending the ACA request, the manager switch enters the locked state. After receiving the ACA request, a managed switch compares its list of domain IDs with that in the packet. If they are consistent, the fabric is in stable state [1]. In this case, the managed switch is prepared for synchronization, replies with an ACC (acknowledgement) packet, and enters the change authorization state (locked). If the managed switch has been in change authorization state or cannot process the ACA request for some reason, it replies with an RJT (reject) packet. 2. The manager switch starts data synchronization by sending an SFC request only after receiving ACC requests from all managed switches. Otherwise, it notifies managed switches to release the change authorization state by sending an RCA request [2]. 3. The manager switch sends an SFC request to all managed switches. The SFC request carries data to be synchronized, including the active zone set and zone database information. After receiving the SFC request with zone database information, the managed switch determines whether the total number of zones, zone sets, and zone aliases exceeds the limit after its local zone database is replaced. If not, it replies with an ACC packet. Otherwise, it replies with an RJT packet. 4. The manager switch notifies managed switches by sending a UFC request to replace their local data with the received data only after receiving ACC packets from all managed switches. Otherwise, it notifies managed switches to release the change authorization state by sending an RCA request. 5. After receiving the UFC request, the managed switch updates its local zone database. It replies with an ACC packet for a successful update and with an RJT packet for a failed update. 6. The manager switch notifies managed switches by sending an RCA request to release the change authorization state after receiving ACC packets from all managed switches. 56

63 7. After receiving the RCA request, the managed switch releases its change authorization state and replies with an ACC packet. 8. 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 eliminating unreachable routes. You need to pay special attention to this in the case of using static routes. Otherwise, data cannot be correctly distributed. [2] If the managed switch replies with neither an ACC packet nor an RJT packet because of its abnormal state, the manager switch cannot be released from its locked state. To prevent this situation, the manager switch starts a packet retransmission mechanism, transmitting up to three ACA requests. In this case, if no reply is received, the manager switch releases its locked state. If the manager switch becomes abnormal after sending an ACA request, the managed switch will be in locked state but cannot receive subsequent packets. Similarly, the managed switch releases its locked state after waiting for a period of time. Zone merge When two fabrics are merged, both the active zone set and zone database might exist in each fabric. In this case, zone configuration information needs to be merged. The following merge types are provided: Complete merge Merges both the active zone sets and zone databases. Incomplete merge Merges only the active zone sets. The merge-originating switch checks its local merge type. If it is configured with complete merge, it sends packets with both the active zone set and zone database. Otherwise, it sends packets with only the active zone set. NOTE: The merge-originating switch determines the data to be merged according to its locally configured merge type, while the merged switches merge all received data, regardless of the their merge types. The pwwn is a preferred choice over FC addresses to identify zone members, because FC addresses might change at fabric merge and the merge result might not be as expected by users. Zone merge process When a switch discovers a new neighbor (the link layer module discovers neighbors and notifies the zone module), it starts a merge process with the neighbor. If the data changes after merging, the switch sends the changed data to neighbor switches until all switches in the fabric update their data. During the merge, the switch sends Merge Request Resource Allocation (MRRA) requests to negotiate the size of data transmitted and then Merge Request (MR) packets containing data to be merged to neighbor switches. 57

64 Figure 23 Zone merge process between two switches The zone merge process is as follows: 1. Switch A and Switch B are new neighbors to each other. Suppose that Switch A first initiates a merge to Switch B: a. Switch A sends an MRRA request carrying the size of its data to be merged to Switch B. b. After receiving the MRRA request, Switch B determines whether to accept the merge according to its local data size. If the size of the data to be merged is acceptable, it replies with an ACC packet. Otherwise, it replies with an RJT packet. c. After receiving the ACC packet, Switch A sends an MR request containing its zone data to Switch B. d. After receiving the MR request, Switch B obtains the zone data and merges it with its local zone data. Then, it replies with an ACC packet for a successful merge or with an RJT packet containing the cause of failure for a failed merge. 2. After the merge process initiated by Switch A is complete, Switch B ends the merge process with Switch A if its local data is exactly the same as or a subset of that of Switch A. Otherwise, Switch B initiates a merge process with Switch A, which is similar to that initiated by Switch A to Switch B as shown in steps 5, 6, 7, and 8 in Figure After the merge process initiated by Switch A is complete, Switch B synchronizes changes in its local database arising from the merge to the entire fabric by initiating a merge process to all its neighbors. 4. Two 1-way merge processes can ensure data consistency between Switch A and Switch B. 58

65 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 The databases contain zone sets with the same name, but zones in these zone sets have different names. The databases contain zone sets with different names. The databases contain zones or zone aliases with different names. The databases contain zones or zone aliases with the same name but different member ports. Successful Successful Successful Failed The union of the local database and neighbor database. Zone sets with the same name are merged. The union of the local database and neighbor database. All zone sets with different names are retained. The union of the local database and neighbor database. All zone sets or zone aliases with different names are retained. Both databases remain unchanged. Empty Contain data Successful Contain data Empty Successful The neighbor database overwrites the local database. The local database overwrites the neighbor database. NOTE: If two switches have active zone sets with different names, the larger name obtained by comparison of strings serves as the name of the active zone set after merging. Access control If a server wants to access a disk through the name service, the server needs to determine whether the server and the disk are in one zone of the active zone set. Members in the same zone can access each other. Otherwise, they cannot access each other. FC zone configuration task list Tasks at a glance (Optional.) Configuring zone aliases (Required.) Configuring zones (Required.) Configuring zone sets (Required.) Configuring the default zone policy (Required.) Configuring zone distribution and merge types 59

66 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: You cannot modify zone configurations during zone distribution or merge. In a fabric, only one manager switch can initiate distribution at a time. The next distribution can be initiated only after the previous one is complete. Configuring zone aliases You can configure a maximum of 256 zone aliases for all VSANs on a switch. You can specify N_Ports as members of a zone alias by using their FC addresses or pwwns. These N_Ports can be indirectly connected to the switch. To configure a zone alias: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Create a zone alias and enter its view. 4. Add a member to the zone alias. zone-alias name zone-alias-name member { fcid fcid pwwn pwwn } If the zone alias has been created, enter its view directly. By default, no member exists in a zone alias. Configuring zones You can configure a maximum of 512 zones for all VSANs on a switch. You can specify N_Ports as members of a zone by using their FC addresses, pwwns, or zone aliases. These N_Ports can be indirectly connected to the switch. An N_Port can belong to more than one zone. To configure a zone: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Create a zone and enter its view. 4. Add a member to the zone. zone name zone-name member { fcid fcid pwwn pwwn zone-alias zone-alias-name } If the zone has been created, enter its view directly. By default, no member exists in a zone. 60

67 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 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Create a zone set and enter its view. 4. Add a zone to the zone set. zoneset name zoneset-name member zone-name If the zone set has been created, enter its view directly. By default, no zone exists in a zone set. Configuring the default zone policy Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Permit traffic between default zone members. 4. Deny traffic between default zone members. zone default-zone permit undo zone default-zone permit Use one of the commands. By default, default zone members are not permitted to access each other. Configuring zone distribution and merge types Complete distribution (or merge) distributes (or merges) both the active zone set and zone database. Incomplete distribution (or merge) distributes (or merges) only the active zone set. The configured distribution type applies to distribution operations triggered by the zoneset activate command instead of the zoneset distribute command. The configured merge type applies to all merge operations. To configure zone distribution and merge types: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Configure zone distribution and merge types as complete distribution and complete merge. zoneset distribute full The default setting is incomplete distribution and incomplete merge. 61

68 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. When distributing the active zone set to the entire fabric, the switch determines whether to carry zone database information according to the distribution type specified by the zoneset distribute full command. The modifications to the active zone set do not take effect until reactivation. Only one active zone set can exist in a VSAN. To activate a zone set and distribute it to the entire fabric: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Activate the specified zone set as the active zone set and distribute it to the entire fabric. zoneset activate name zoneset-name The zone set to be activated must have been created and must consist of at least one N_Port member. NOTE: Active zone set information will not contain the alias names of zone members. If a zone in the active zone set has members with a zone alias, the non-overlapping N_Port members in the zone alias are directly added to the zone. You can display zone members by zone by using the display zoneset active command. Triggering a complete distribution Use the zoneset distribute command to trigger a complete distribution, which distributes both the active zone set and zone database. After activating a zone set as the active zone set by using the zoneset activate command, you can modify the database configuration. With the zoneset distribute command, you can distribute the active zone set and the modified database to the entire fabric without changing the active zone set. To activate a complete distribution: Step Command 1. Enter system view. system-view 2. Enter VSAN view. vsan vsan-id 3. Activate a complete distribution. zoneset distribute 62

69 Renaming zone aliases, zones, and zone sets Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Rename a zone alias. zone-alias rename old-name new-name The zone alias to be renamed must have been created, and the new zone alias must not have been created. 4. Rename a zone. zone rename old-name new-name 5. Rename a zone set. zoneset rename old-name new-name The zone to be renamed must have been created, and the new zone must not have been created. The zone set to be renamed must have been created, and the new zone set must not have been created. Copying zone aliases, zones, and zone sets You can create a zone alias, zone, or zone set by copying an existing one. They have the same name but different contents. To copy a zone alias, zone, and zone set: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 3. Copy an existing zone alias to create a new zone alias. 4. Copy an existing zone to create a new zone. 5. Copy an existing zone set to create a new zone set. zone-alias clone src-name dest-name zone clone src-name dest-name zoneset clone src-name dest-name The source zone alias must have been created, and the destination zone alias must not have been created. The source zone must have been created, and the destination zone must not have been created. The source zone set must have been created, and the destination zone set must not have been created. 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: 63

70 Step Command 1. Enter system view. system-view 2. Enter VSAN view. vsan vsan-id 3. Delete the zone database. delete zone database all Displaying and maintaining FC zones Execute display commands in any view. Task Display zone alias information. Command display zone-alias [ [ name zone-alias-name ] vsan vsan-id ] Display zone information. display zone [ [ name zone-name ] vsan vsan-id ] Display zone set information. display zoneset [ [ name zoneset-name ] vsan vsan-id ] Display information about the active zone set. display zoneset active [ vsan vsan-id ] Display information about a zone member (including the zone and zone alias to which the zone member belongs and the zone to which the zone alias belongs). Display the running status and configuration of an FC zone. display zone member { fcid fcid pwwn pwwn zone-alias zone-alias-name } [ vsan vsan-id ] display zone status [ vsan vsan-id ] FC zone configuration example Network requirements As shown in Figure 24, all nodes have registered with the switches. Access control is specified for VSAN 1 as follows: Server A does not access any disk but might need to subsequently. Server B can access Disks A, B, and C. Server C can access Disks B and C. Servers cannot access each other. 64

71 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. Configure Switch A and distribute the full zone database to Switch B: Create zone alias Alias 1, which consists of Disks B and C, to simplify the configuration. Create zone set Zoneset 1, which consists of Zones 1, 2, and 3, and activate it. Configuration procedure Configure Switch A only. For how to configure physical-to-virtual interface bindings and VLAN-to-VSAN mappings, see "Configuring a VFC interface" and "Enabling FCoE for a VLAN and mapping a VSAN to the VLAN." # Configure Switch A to operate in FCF mode, create zone alias Alias 1, and add pwwn 22:33:44:55:66:77:88:99 (Disk B) and FC address (Disk C) as its members. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 1 [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 [SwitchA-vsan1-zone-alias-Alias1] quit # Create Zone 1 and specify FC ID as its member. Create Zone 2 and specify FC ID and pwwn 11:22:33:44:55:66:77:88, whose zone aliases are Alias 1, as its members. Create Zone 3 and specify FC ID , whose zone alias is Alias 1, as its member. [SwitchA-vsan1] zone name Zone1 65

72 [SwitchA-vsan1-zone-Zone1] member fcid [SwitchA-vsan1-zone-Zone1] quit [SwitchA-vsan1] zone name Zone2 [SwitchA-vsan1-zone-Zone2] member fcid [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 [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 [SwitchA-vsan1-zoneset-Zoneset1] member Zone3 [SwitchA-vsan1-zoneset-Zoneset1] quit # Configure zone distribution and merge types as complete distribution and complete merge. [SwitchA-vsan1] zoneset distribute full # Activate a zone set as the active zone set, and distribute it to the entire fabric. [SwitchA-vsan1] zoneset activate name Zoneset1 Verifying the configurations All verification tasks are performed on Switch B. # Display zone set information for VSAN 1. <SwitchB> display zoneset vsan 1 VSAN 1: zoneset name Zoneset1 zone name Zone1 fcid 0x zone name Zone2 fcid 0x pwwn 11:22:33:44:55:66:77:88 zone-alias Alias1 fcid 0x pwwn 22:33:44:55:66:77:88:99 zone name Zone3 fcid 0x zone-alias Alias1 fcid 0x 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 0x

73 pwwn 11:22:33:44:55:66:77:88 zone-alias Alias1 fcid 0x pwwn 22:33:44:55:66:77:88:99 # Display the zone or zone alias to which (FC ID type) belongs. <SwitchB> display zone member fcid fcid 0x VSAN 1: zone-alias Alias1 zone Zone2 zone Zone3 # Display information about the active zone set in VSAN 1. <SwitchB> display zoneset active vsan 1 VSAN 1: zoneset name Zoneset1 zone name Zone1 *fcid 0x zone name Zone2 *fcid 0x *fcid 0x *fcid 0x [pwwn 22:33:44:55:66:77:88:99] *fcid 0x [pwwn 11:22:33:44:55:66:77:88] zone name Zone3 *fcid 0x *fcid 0x *fcid 0x [pwwn 22:33:44:55:66:77:88:99] 67

74 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. It can only be a VFC interface, which must be configured to operate in F mode. A downlink is a link from an NPV switch to its node. Each downlink interface is uniquely mapped to an operational uplink interface, through which all traffic from the nodes connected to the downlink interface is forwarded to the core switch. Uplink interface and uplink An uplink interface, also known as an external interface, is the interface through which an NPV switch connects to the core switch. It can be a VFC interface, which must be configured to operate in NP mode. An uplink is a link from an NPV switch to the core switch. After the uplink is operational, the NPV switch sends a fabric login (FLOGI) packet to the core switch for registration, which assigns the uplink interface (NP_Port) an FC address. Then, the NPV switch registers itself with the name server on the core switch. The NPV switch forwards traffic (including FLOGI packets) from a node to the core switch through the mapped uplink interface and passes response packets from the core switch to nodes through the downlink interface. 68

75 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. When automatic mapping cannot meet requirements (for example, when a downlink interface must be connected to a fabric through a specified uplink interface), you can manually map the downlink interface to a specified uplink interface or a set of uplink interfaces. After you configure the mapping, the downlink interface can be mapped to only the configured uplink interfaces. In other words, if none of the configured uplink interfaces is operational, the downlink interface cannot be operational. A configured mapping selects the uplink interface with the minimum load from configured uplink interfaces and then maps the downlink interface to it. After a mapping is established, all traffic from the downlink interface is forwarded through the uplink interface. Disruptive load balancing When a new uplink interface becomes operational, the NPV switch does not perform a remapping for load balancing. In the event of remapping, the NPV switch reinitializes the downlink interface so that the nodes connected to the downlink interface register with the core switch again. This causes traffic interruption to the nodes. You can trigger a remapping by using commands for better load balancing. In this case, the NPV switch reinitializes all downlink interfaces. NPV configuration task list Tasks at a glance (Required.) Configuring the switch to operate in NPV mode (Required.) Configuring uplink interfaces and downlink interfaces (Optional.) Configuring downlink-to-uplink interface mappings (Optional.) Initiating a disruptive load-balancing process Remarks See "Configuring an FCoE mode for a switch." N/A N/A N/A Configuring uplink interfaces and downlink interfaces After configuring the switch to operate in NPV mode, configure the uplink interfaces and downlink interfaces. Configuring uplink interfaces Uplink interfaces must be VFC interfaces in NP mode. 69

76 To configure an uplink interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. 3. Configure the VFC interface to operate in NP mode. interface vfc interface-number fc mode np This interface is connected to the core switch. By default, a VFC interface on an NPV switch operates in F mode. Configuring downlink interfaces Downlink interfaces must be VFC interfaces in F mode. To configure a downlink interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VFC interface view. 3. Configure the VFC interface to operate in F mode. interface vfc interface-number fc mode f This interface is connected to a node. By default, a VFC interface on an NPV switch operates in F mode. Configuring downlink-to-uplink interface mappings CAUTION: If an uplink interface mapped by a downlink interface is not in the configured mappings, the switch initializes the downlink interface, resulting in traffic interruption. NPV switches automatically map downlink interfaces to uplink interfaces. When automatic mapping cannot meet requirements, for example, when a downlink interface must be connected to a fabric through a specified uplink interface, you can manually map the downlink interface to a specified uplink interface or a set of uplink interfaces. After you configure the mapping, the downlink interface can be mapped to only the configured uplink interfaces. If none of the configured uplink interfaces is operational, the downlink interface cannot be operational. A configured mapping selects the uplink interface with the minimum load from configured uplink interfaces and then maps the downlink interface to it. To configure uplink and downlink mapping: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter VSAN view. vsan vsan-id N/A 70

77 Step Command Remarks 3. Configure a downlink-to-uplink interface mapping. npv traffic-map server-interface interface-type interface-number external-interface interface-type interface-number By default, no mapping is configured. 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. If interfaces in a VSAN are not distributed evenly, you can use this feature to force all nodes in the VSAN to relog in to the core switch. To initiate a disruptive load-balancing process: Step Command 1. Enter system view. system-view 2. Enter VSAN view. vsan vsan-id 3. Initiate a disruptive load-balancing process. npv load-balance disruptive Displaying and maintaining NPV Execute display commands in any view. Task Display the nodes on downlink interfaces and their mapped uplink interfaces. Display the traffic mapping information. Command display npv login [ vsan vsan-id ] [ interface interface-type interface-number ] display npv traffic-map [ vsan vsan-id ] [ interface interface-type interface-number ] Display status information. display npv status [ vsan vsan-id ] NPV configuration example Network requirements As shown in Figure 26, configure Switch A (edge switch) as an NPV switch to expand the network. 71

78 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 [SwitchA-Ten-GigabitEthernet1/0/1] quit # Configure interface Ten-GigabitEthernet 1/0/2 to allow VLAN 20. [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 # Configure interface Ten-GigabitEthernet 1/0/3 to allow VLAN 20. [SwitchA] interface Ten-GigabitEthernet1/0/3 [SwitchA-Ten-GigabitEthernet1/0/3] port link-type trunk [SwitchA-Ten-GigabitEthernet1/0/3] port trunk permit vlan 20 [SwitchA-Ten-GigabitEthernet1/0/3] quit # Create interface VFC 1, bind it to interface Ten-GigabitEthernet 1/0/1, and configure it to allow VSAN 10. [SwitchA] interface vfc 1 [SwitchA-Vfc1] bind interface Ten-GigabitEthernet1/0/1 [SwitchA-Vfc1] port trunk vsan 10 # Configure the uplink interface. [SwitchA-vfc1] fc mode np 72

79 [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 [SwitchA-Vfc3] port trunk vsan 10 [SwitchA-Vfc3] quit # Configure the downlink interface. [SwitchA] interface vfc 2 [SwitchA-vfc 2] fc mode f [SwitchA-vfc 2] quit [SwitchA] interface vfc 3 [SwitchA-vfc 3] fc mode f [SwitchA-vfc 3] quit # Enable FCoE for VLAN 20 and map it to VSAN 10. [SwitchA] vlan 20 [SwitchA-vlan20] fcoe enable vsan 10 [SwitchA-vlan20] quit Verifying the configurations # Display the nodes on downlink interfaces and their mapped uplink interfaces. [SwitchA] display npv login Server External Interface VSAN FCID Port WWN Node WWN Interface Vfc2 1 0x :00:00:15:40:94:00:00 20:00:00:15:40:94:00:00 Vfc1 Vfc3 1 0x :00:00:42:40:94:00:01 20:00:00:42:40:94:00:01 Vfc1 # Display the status of Switch A. [SwitchA] display npv status External Interfaces: Interface: Vfc1 VSAN tagging mode: Tagging VSAN State FCID 1 Up 0x Number of External Interfaces: 1 Server Interfaces: Interface: Vfc2 VSAN tagging mode: Tagging VSAN State 1 Up Interface: Vfc3 VSAN tagging mode: Tagging VSAN State 73

80 1 Up 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 74

81 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. If the destination is reachable, the source device determines the link quality based on the number of echo requests sent and the number of replies received, and it determines the distance between the source and destination based on the round-trip time of FC ping packets. A switch supports the following FC ping operations: FC ping an N_Port from the switch Use the fcping command on the switch to ping an N_Port at the remote end. The destination address of the FC ping operation is the FC address of the N_Port. FC ping a switch from the current switch The destination address is the domain controller address FFFCxx of the destination switch, where xx is the domain ID of the destination switch. Configuration procedure Task Command Remarks Check whether a specified destination address is reachable. fcping [ -c count -t timeout ] * fcid fcid vsan vsan-id Available in any view. To abort the FC ping operation during the execution of the command, press Ctrl+C. FC ping configuration example Network requirements As shown in Figure 27, check whether Switch A and Switch B can reach each other. Figure 27 Network diagram Configuration procedure 1. Configure Switch A: 75

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 [SwitchA-Vfc100] port trunk vsan 10 [SwitchA-Vfc100] quit # Enable the fabric configuration function. [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Configure the domain ID as 1. [SwitchA-vsan1] domain-id 1 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y [SwitchA-vsan1] quit # Enable FCoE for VLAN 10 and map it to VSAN 1. [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 [SwitchA-vlan10] quit # Configure a static route. [SwitchA-vsan1] fc route-static Vfc Configure Switch B: # Configure Switch B to operate in FCF mode. Create interface VFC 200, 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. <SwitchB> system-view [SwitchB] fcoe-mode fcf [SwitchA] interface Vfc 200 [SwitchA-Vfc200] bind interface Ten-GigabitEthernet1/0/2 [SwitchA-Vfc200] fc mode f [SwitchA-Vfc200] port trunk vsan 1 [SwitchA-Vfc200] quit # Enable the fabric configuration function. [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 [SwitchA-vsan1] quit # Enable FCoE for VLAN 10 and map it to VSAN 1. <SwitchA> system-view [SwitchA] vlan 10 [SwitchA-vlan10] fcoe enable vsan 1 76

83 [SwitchA-vlan10] quit # Configure a static route. [SwitchB-vsan1] fc route-static 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. Reply from 0xfffc02: bytes = 128 time = 23 ms Reply from 0xfffc02: bytes = 128 time = 9 ms Reply from 0xfffc02: bytes = 128 time = 19 ms Reply from 0xfffc02: bytes = 128 time = 14 ms Reply from 0xfffc02: bytes = 128 time = 25 ms --- 0xfffc02 fcping statistics packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 9/18/25 ms 77

84 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 destination sends the Switch Trace Route (STR) packet to its next hop until the STR packet reaches the destination switch. (If the destination of FC tracert is a node, the destination switch refers to the FCF switch directly connected to the node.) Each switch adds its uplink path information (including its WWN and domain ID) to the STR packet. After the STR packet reaches the destination switch, the downlink process starts. Downlink process In this process, beginning from the destination switch, each switch along the path to the source switch sends the STR packet to its next hop until the STR packet reaches the source switch. Each switch adds its downlink path information (with the same content as the uplink path information) to the STR packet. When the source switch receives the STR packet, the FC tracert process ends. The source outputs information (in the STR packet) about all uplink and downlink switches along the path. If an FCF switch fails to forward the STR packet, the switch sets an error reason in the packet and sends the packet (containing information about switches the packet has passed through) directly to the source switch. Figure 28 shows the FC tracert process. Figure 28 FC tracert flowchart Source switch Switch A Intermediate switch Switch B Destination switch Switch C STR Request STR ACC STR Request STR ACC STR Request STR Request STR ACC STR ACC The following describes the process of an FC tracert operation from Switch A to Switch C. 1. Uplink process: 78

85 a. 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. b. Switch B adds its uplink path information to the received STR packet and sends it to the destination switch, Switch C. After receiving the packet, Switch C replies with an STR ACC packet to Switch B. c. Switch C adds its uplink path information to the received packet, completing the collection of uplink path information. 2. Downlink process: a. Switch C sends the STR request packet to Switch A hop by hop in the same way as in the uplink process. b. After receiving the STR request packet with a downlink flag, Switch A outputs information about all uplink and downlink switches. Configuration procedure Task Command Remarks Detect bidirectional routing information between source and destination. fctracert [ -t timeout ] fcid fcid vsan vsan-id Available in any view. To abort the FC tracert operation during the execution of the command, press Ctrl+C. FC tracert configuration example Network requirements As shown in Figure 29, detect bidirectional routing information between Switch A and Switch C, and identify the faulty node (if any). Figure 29 Network diagram Configuration procedure 1. Configure Switch A: # Enable the fabric configuration function and configure Switch A to operate in FCF mode. <SwitchA> system-view [SwitchA] fcoe-mode fcf [SwitchA] vsan 1 [SwitchA-vsan1] domain configure enable # Configure the domain ID as 1. 79

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 2. Configure Switch B: # Enable the fabric configuration function and configure Switch B to operate in FCF mode. <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 # Enable FSPF globally. [SwitchB-vsan1] fspf enable 3. Configure Switch C: # Enable the fabric configuration function. <SwitchC> system-view [SwitchC] vsan 1 [SwitchC-vsan1] domain configure enable # Configure the domain ID as 3. [SwitchC-vsan1] domain-id 3 static Non-disruptive reconfiguration or isolating the switch may be performed. Continu e? [Y/N]:y # Enable FSPF globally. [SwitchC-vsan1] fspf enable 4. On Switch A, use the fcping command to ping Switch C and check whether Switch C is reachable. [SwitchA-vsan1] fcping fcid fffc03 vsan 1 FCPING fcid 0xfffc03: 128 data bytes, press CTRL_C to break. Request time out Request time out Request time out Request time out Request time out --- 0xfffc03 fcping statistics packet(s) transmitted 0 packet(s) received % packet loss The output shows that Switch A cannot reach Switch C. 5. Use the fctracert command to identify the faulty node. [SwitchA-vsan1] fctracert fcid fffc03 vsan 1 Route present for: 0xfffc03, press CTRL_C to break 20:00:00:0b:46:00:02:82(0xfffc01) 80

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. 81

88 Appendixes Appendix A Fabric address assignment Table 4 Fabric address assignment FC_ID 0x x x00FFFF 0x xEFFFFF 0xF xFFF9FF 0xFFFA00 0xFFFA0F 0xFFFA10 0xFFFA1F 0xFFFA20 0xFFFAFF 0xFFFB00 0xFFFBFF 0xFFFC00 0xFFFC01 0xFFFCEF 0xFFFCF0 0xFFFFEF 0xFFFFF0 0xFFFFFC 0xFFFFFD 0xFFFFFE 0xFFFFFF Description Undefined (when an N_Port uses FLOGI to request for an address, an all-zero FC ID is used). Reserved. N_Port address. Reserved. Reserved for internal loopback. Reserved for external loopback. Reserved. Reserved for multicast. Reserved. Domain controller addresses. Reserved. Well-known addresses. Fabric controller address, representing all E_Ports. F_Port controller address, representing all F_Ports. Broadcast address. Appendix B Well-known fabric addresses Table 5 Purposes of well-known fabric addresses FC_ID 0xFFFFF0 0xFFFFF1 0xFFFFF3 0xFFFFF4 0xFFFFF5 0xFFFFF6 0xFFFFF7 0xFFFFF8 0xFFFFF9 Description N_Port controller, representing all N_Ports. Reserved. Event services. Multicast server. Clock synchronization services. Security key distribution services. Alias services. Reserved. 82

89 FC_ID 0xFFFFFA 0xFFFFFB 0xFFFFFC Description Management services. Time services. Path services (name services). 83

90 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: After registering, you will receive notification of product enhancements, new driver versions, firmware updates, and other product resources. Related information Documents Websites To find related documents, browse to the Manuals page of the HP Business Support Center website: For related documentation, navigate to the Networking section, and select a networking category. For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms. HP.com HP Networking HP manuals HP download drivers and software HP software depot HP Education 84

91 Conventions This section describes the conventions used in this documentation set. Command conventions Convention Boldface Italic Description Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. [ ] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x y... } [ x y... ] { x y... } * [ x y... ] * &<1-n> Braces enclose a set of required syntax choices separated by vertical bars, from which you select one. Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none. Asterisk-marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one. Asterisk-marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none. The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times. # A line that starts with a pound (#) sign is comments. GUI conventions Convention Boldface Description Window names, button names, field names, and menu items are in bold text. For example, the New User window appears; click OK. > Multi-level menus are separated by angle brackets. For example, File > Create > Folder. Symbols Convention WARNING CAUTION IMPORTANT NOTE TIP Description An alert that calls attention to important information that if not understood or followed can result in personal injury. An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that contains additional or supplementary information. An alert that provides helpful information. 85

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. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. 86

93 Index access FC access control, 59 activating FCoE FC zone set, 62 active FC zone database active zone set, 54 address FC (FCoE), 2 FC direct routes, 39 FC FSPF configuration, 41 FC FSPF routes, 40 FC static route configuration, 41, 46 FC static routes, 39 FCoE fabric address assignment, 82 FCoE fabric FC address assignment, 21 FCoE FC forwarding configuration, 38 FCoE FC routing configuration, 38 FCoE well-known fabric addresses, 82 allowed domain ID list configuration, 24 assigning fabric domain ID, 20 fabric FC address, 21 FCoE fabric address, 82 configuring allowed domain ID list, 24 fabric auto reconfiguration, 27 fabric reconfiguration, 26 fabric timer in system view, 25 fabric timer in VSAN view, 26 FC FSPF, 41, 49 FC FSPF GR, 45 FC FSPF GR Helper, 45 FC FSPF GR Restarter, 45 FC FSPF interface cost, 43 FC FSPF interface dead interval, 44 FC FSPF interface hello interval, 44 FC FSPF interface LSR retransmission interval, 44 FC FSPF min LSR receiving interval, 43 FC FSPF min LSR refresh interval, 43 FC FSPF shortest SPF calculation interval, 42 FC static route, 41, 46 FCoE dynamic fabric build, 30 FCoE fabric distributed service timeout timer, 25 FCoE fabric error detection timeout timer, 25 FCoE fabric N_Port-WWN-to-FC address mapping, 25 FCoE fabric resource allocation timeout timer, 25 FCoE fabric switch domain IDs, 24 FCoE FC default zone policy, 61 FCoE FC forwarding, 38 FCoE FC ping, 75 FCoE FC routing, 38 FCoE FC tracert, 78, 79 FCoE FC zone aliases, 60 FCoE FC zone distribution, 61 FCoE FC zone merge types, 61 FCoE FC zone sets, 61 FCoE FC zones, 53, 59, 60, 64 FCoE FCF priority, 15 FCoE FC-MAP value, 13 FCoE FKA advertisement period value, 14 FCoE mode for switch, 11 FCoE static fabric build, 28 FCoE system FCF priority, 15 FCoE VFC interface, 12 FCoE VFC interface FCF priority, 16 NPV, 68, 69, 71 NPV downlink interface, 69, 70 NPV downlink-to-uplink interface mapping, 70 NPV uplink interface, 69 trunk VSAN, 34 VFC interfaces and FIP, 12, 16 VSAN, 33, 35 copying FCoE FC zone sets, 63 FCoE FC zones, 63 creating VSAN, 34 dead interval configuration, 44 default FC zone database default zone, 55 FCoE FC default zone policy configuration, 61 FCoE VFC interface F mode, 5 deleting FCoE FC zone database, 63 device FCoE communication flow, 3 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric configuration enable/disable, 22 87

94 FCoE fabric N_Port-WWN-to-FC address mapping configuration, 25 FCoE fabric name setting, 23 FCoE fabric principal switch selection, 19 FCoE fabric setup, 19, 21 FCoE fabric switch domain ID configuration, 24 FCoE fabric switch priority setting, 23 FCoE FC zone, 4 FCoE feature support by FCoE modes, 11 FCoE FIP operation, 7 FCoE for VLAN enable, 13 FCoE frames, 6 FCoE interface modes, 2 FCoE NPV configuration, 68, 69, 71 FCoE NPV disruptive load balancing, 69 FCoE NPV disruptive load balancing process initiation, 71 FCoE NPV downlink, 68 FCoE NPV downlink interface, 68 FCoE NPV downlink interface configuration, 69, 70 FCoE NPV downlink-to-uplink interface mapping, 69 FCoE NPV downlink-to-uplink interface mapping configuration, 70 FCoE NPV mode, 9 FCoE NPV uplink, 68 FCoE NPV uplink interface, 68 FCoE NPV uplink interface configuration, 69 FCoE static fabric building configuration, 28 FCoE VFC interface, 5 FCoE VFC interface configuration, 12 FCoE VN interface, 5 FCoE VSAN, 4 FCoE VSAN configuration, 33, 35 FCoE VSAN to VLAN mapping, 13 VFC interfaces and FIP configuration, 12, 16 direct FC direct routes, 38, 39 disabling FC FSPF for interface, 45 FCoE fabric configuration, 22 displaying fabric, 27 FC forwarding, 46 FC routing, 46 FC zones, 64 NPV, 71 VFC interfaces and FIP, 16 VSAN, 35 disruptive FCoE load balancing process initiation, 71 NPV load balancing, 69 distributed service timeout timer, 25 distributing FCoE FC zone set to fabric, 62 domain FCoE fabric domain ID assignment, 20 downlink-to-uplink interface mapping FCoE, 70 NPV, 69 dynamic FCoE fabric dynamic mode, 19, 21 FCoE static fabric building configuration, 30 enabling FC FSPF, 42 FCoE fabric configuration, 22 FCoE for VLAN, 13 error detection timeout timer, 25 Ethernet FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric setup, 19, 21 FCoE FC forwarding configuration, 38 FCoE FC ping configuration, 75 FCoE FC routing configuration, 38 FCoE FC tracert configuration, 78, 79 FCoE FC zone configuration, 53, 59, 64 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE feature support by FCoE modes, 11 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE frames, 6 FCoE NPV configuration, 68, 69, 71 FCoE NPV mode, 9 FCoE operation, 6 FCoE static fabric building configuration, 28 FCoE system FCF priority configuration, 15 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VSAN configuration, 33, 35 FCoE VSAN to VLAN mapping, 13 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 fabric auto reconfiguration, 27 displaying, 27 disruptive reconfiguration, 26 distributed service timeout timer, 25 88

95 domain ID assignment, 20 dynamic fabric building configuration, 30 error detection timeout timer, 25 FC access control, 59 FC address assignment, 21 FC interface configuration, 22 FC zone distribution, 55 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FCoE fabric address assignment, 82 FCoE FC zone set distribution to fabric, 62 FCoE well-known fabric addresses, 82 manually initiating reconfiguration, 27 N_Port-WWN-to-FC address mapping configuration, 25 name setting, 23 non-disruptive reconfiguration, 26 principal switch selection, 19 resource allocation timeout timer, 25 setup, 19, 21 static fabric building configuration, 28 switch domain ID configuration, 24 switch priority setting, 23 timer configuration in system view, 25 timer configuration in VSAN view, 26 VFC interface RCF request rejection, 27 Fabric Shortest Path First. Use FSPF FC access control, 59 complete zone distribution, 55 complete zone merge, 57 displaying FC zones, 64 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE FKA advertisement period value configuration, 14 FCoE frames, 6 FCoE system FCF priority configuration, 15 FCoE VFC interface FCF priority configuration, 16 FIB table, 38 FIB table contents, 39 incomplete zone distribution, 55 incomplete zone merge, 57 routing table, 38 routing table contents, 38 zone database, 53 zone database active zone set, 54 zone database default zone, 55 zone database structure, 53 zone distribution, 55 zone distribution process, 55 zone distribution triggering methods, 55 zone merge, 57 zone merge process, 57 zone merge rules, 59 FC frame FCF mode, 8 procedure of receiving and sending FC frame, 7 FC-MAP FCoE frame, 6 FCoE basic concepts, 2, 5 communication flow, 3 configuring allowed domain ID list, 24 configuring FCoE mode for switch, 11 description, 4 dynamic fabric building configuration, 30 fabric address assignment, 82 fabric configuration enable/disable, 22 fabric domain ID assignment, 20 fabric FC address assignment, 21 fabric N_Port-WWN-to-FC address mapping configuration, 25 fabric name setting, 23 fabric principal switch selection, 19 fabric setup, 19, 21 fabric switch domain ID configuration, 24 fabric switch priority setting, 23 fabric timer configuration, 25 FC access control, 59 FC address, 2 FC default zone policy configuration, 61 FC direct routes, 39 FC forwarding configuration, 38 FC FSPF configuration, 41, 42, 49 FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 FC FSPF interface cost configuration, 43 FC FSPF interface dead interval configuration, 44 FC FSPF interface disable, 45 FC FSPF interface hello interval configuration, 44 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 FC FSPF packet types, 40 FC FSPF routes, 40 89

96 FC FSPF shortest SPF calculation interval configuration, 42 FC ping configuration, 75 FC protocol, 2 FC routing configuration, 38 FC SAN, 1 FC static route configuration, 41, 46 FC static routes, 39 FC tracert configuration, 78, 79 FC triggering zone set distribution, 62 FC zone, 4 FC zone alias configuration, 60 FC zone configuration, 53, 59, 60, 64 FC zone copying, 63 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone database deletion, 63 FC zone distribution, 55 FC zone distribution configuration, 61 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FC zone merge type configuration, 61 FC zone renaming, 63 FC zone set activation, 62 FC zone set configuration, 61 FC zone set copying, 63 FC zone set distribution to fabric, 62 FC zone set renaming, 63 FCF mode, 8 feature support by FCoE modes, 11 FIP, 6 FIP operation, 7 how it works, 6 interface modes, 2 mode, 8 NPV configuration, 68, 69, 71 NPV disruptive load balancing, 69 NPV disruptive load balancing process initiation, 71 NPV downlink, 68 NPV downlink configuration, 69, 70 NPV downlink interface, 68 NPV downlink-to-uplink interface mapping, 69 NPV downlink-to-uplink interface mapping configuration, 70 NPV mode, 9 NPV uplink, 68 NPV uplink interface, 68 NPV uplink interface configuration, 69 procedure of receiving and sending FC frame, 7 protocols and standards, 9 static fabric building configuration, 28 VFC interface, 5 VN interface, 5 VSAN, 4 VSAN configuration, 33, 35 VSAN fundamentals, 33 well-known fabric addresses, 82 WWN, 2 FCoE frame fabric provided MAC address. Use FPMA FC-MAP, 6 FCoE MAC address, 6 VN interface, 6 FCoE MAC address FCoE frame, 6 FCoE mode configuration, 11 FIB FC FIB table, 38 FC routing table, 38 FIB table FCoE FC forwarding configuration, 38 FCoE FC routing configuration, 38 Fibre Channel over Ethernet. Use FCoE FIP FCoE FIP discovery advertisement, 7 FCoE FIP discovery solicitation, 7 FCoE FIP solicited discovery advertisement, 7 FCoE FIP unsolicited discovery advertisement, 7 FCoE operation, 6 how it works, 7 virtual link, 6 FKA advertisement period, 14 unsolicited discovery advertisement, 14 forwarding FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 FCoE FC forwarding configuration, 38 FSPF configuration, 41 disabling FSPF for interface, 45 enabling, 42 FC FSPF configuration, 49 FC FSPF LSA packet type, 40 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF routes, 38, 40 GR Helper configuration, 45 90

97 GR Restarter configuration, 45 how it works, 41 interface cost configuration, 43 interface dead interval configuration, 44 interface hello interval configuration, 44 interface LSR retransmission interval configuration, 44 min LSR receiving interval configuration, 43 min LSR refresh interval configuration, 43 shortest SPF calculation interval configuration, 42 GR FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 Graceful Restart. Use GR hello FC FSPF interface hello interval configuration, 44 initiating manual fabric reconfiguration, 27 NPV disruptive load balancing process, 71 interval FC FSPF interface cost configuration, 43 FC FSPF interface dead interval configuration, 44 FC FSPF interface hello interval configuration, 44 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 FC FSPF shortest SPF calculation interval configuration, 42 link FC FSPF interface cost configuration, 43 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSA packet type, 40 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 load balancing FCoE NPV disruptive load balancing, 69 FCoE NPV disruptive load balancing process initiation, 71 LSA FC FSPF LSA packet type, 40 LSDB FC FSPF LSDB, 40 LSR FC FSPF interface cost configuration, 43 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 maintaining VFC interfaces and FIP, 16 mapping FCoE FC-MAP value configuration, 13 FCoE NPV downlink-to-uplink interface mapping, 69 FCoE NPV downlink-to-uplink interface mapping configuration, 70 FCoE VSAN to VLAN, 13 FCoE VSAN to VLAN mapping, 13 merge FC complete zone merge, 57 FC incomplete zone merge, 57 FC zone merge process, 57 FC zone merge rules, 59 FCoE FC zone merge type configuration, 61 mode FCoE dynamic fabric build configuration, 30 FCoE fabric dynamic mode, 19, 21 FCoE fabric static mode, 19, 21 FCoE feature support by FCoE modes, 11 FCoE interface modes, 2 FCoE static fabric build configuration, 28 FCoE VFC interface E mode, 5 FCoE VFC interface F mode, 5 FCoE VFC interface NP mode, 5 N_Port Virtualizer. Use NPV network FC access control, 59 FC direct routes, 39 FC FSPF configuration, 41 FC FSPF enable, 42 FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 FC FSPF interface cost configuration, 43 FC FSPF interface dead interval configuration, 44 FC FSPF interface disable, 45 FC FSPF interface hello interval configuration, 44 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 91

98 FC FSPF packet type, 40 FC FSPF routes, 40 FC FSPF shortest SPF calculation interval configuration, 42 FC protocol, 2 FC SAN, 1 FC static route configuration, 41 FC static routes, 39 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone distribution, 55 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FCoE communication flow, 3 FCoE description, 4 FCoE fabric configuration enable/disable, 22 FCoE fabric domain ID assignment, 20 FCoE fabric FC address assignment, 21 FCoE fabric N_Port-WWN-to-FC address mapping configuration, 25 FCoE fabric name setting, 23 FCoE fabric principal switch selection, 19 FCoE fabric switch domain ID configuration, 24 FCoE fabric switch priority setting, 23 FCoE fabric timer configuration, 25 FCoE FC default zone policy configuration, 61 FCoE FC triggering zone set distribution, 62 FCoE FC zone, 4 FCoE FC zone alias configuration, 60 FCoE FC zone configuration, 60 FCoE FC zone copying, 63 FCoE FC zone database deletion, 63 FCoE FC zone distribution configuration, 61 FCoE FC zone merge type configuration, 61 FCoE FC zone renaming, 63 FCoE FC zone set activation, 62 FCoE FC zone set configuration, 61 FCoE FC zone set copying, 63 FCoE FC zone set distribution to fabric, 62 FCoE FC zone set renaming, 63 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE FIP, 6 FCoE FIP operation, 7 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE frames, 6 FCoE interface modes, 2 FCoE NPV disruptive load balancing, 69 FCoE NPV disruptive load balancing process initiation, 71 FCoE NPV downlink, 68 FCoE NPV downlink interface, 68 FCoE NPV downlink interface configuration, 69, 70 FCoE NPV downlink-to-uplink interface mapping, 69 FCoE NPV downlink-to-uplink interface mapping interface configuration, 70 FCoE NPV mode, 9 FCoE NPV uplink, 68 FCoE NPV uplink interface, 68 FCoE NPV uplink interface configuration, 69 FCoE system FCF priority configuration, 15 FCoE trunk VSAN, 33 FCoE trunk VSAN configuration, 34 FCoE VFC interface, 5 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VN interface, 5 FCoE VSAN, 4 FCoE VSAN creation, 34 FCoE VSAN fundamentals, 33 FCoE VSAN to VLAN mapping, 13 zone database, 53 network management FC FSPF configuration, 49 FC static route configuration, 46 FCoE basic concepts, 2 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric setup, 19, 21 FCoE FC forwarding configuration, 38 FCoE FC ping configuration, 75 FCoE FC routing configuration, 38 FCoE FC tracert configuration, 78, 79 FCoE FC zone configuration, 53, 59, 64 FCoE feature support by FCoE modes, 11 FCoE NPV configuration, 68, 69, 71 FCoE operation, 6 FCoE static fabric building configuration, 28 FCoE VSAN configuration, 33, 35 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 node FCoE FIP, 6 FCoE FIP operation, 7 FCoE frames, 6 92

99 FCoE VFC interface, 5 FCoE VN interface, 5 NPV configuration, 68, 69, 71 displaying, 71 disruptive load balancing, 69 disruptive load balancing process initiation, 71 downlink, 68 downlink interface, 68 downlink interface configuration, 69, 70 downlink-to-uplink interface mapping, 69 downlink-to-uplink interface mapping interface configuration, 70 FCoE feature support by FCoE modes, 11 uplink, 68 uplink interface, 68 uplink interface configuration, 69 NPV mode FC SAN, 9 packet FC FSPF interface dead interval configuration, 44 FC FSPF interface hello interval configuration, 44 FC FSPF LSA packet type, 40 FCoE FC forwarding configuration, 38 FCoE FC routing configuration, 38 FCoE FIP discovery advertisement, 7 FCoE FIP discovery solicitation, 7 FCoE FIP solicited discovery advertisement, 7 FCoE FIP unsolicited discovery advertisement, 7 PFMA FCoE frame, 6 ping FCoE FC ping configuration, 75 policy FCoE FC default zone policy configuration, 61 port FC access control, 59 FC address, 2 FC direct routes, 39 FC FSPF configuration, 41 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF routes, 40 FC static route configuration, 41, 46 FC static routes, 39 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone distribution, 55 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric setup, 19, 21 FCoE FC zone, 4 FCoE feature support by FCoE modes, 11 FCoE interface modes, 2 FCoE NPV configuration, 68, 69, 71 FCoE NPV mode, 9 FCoE static fabric building configuration, 28 FCoE trunk VSAN, 33 FCoE trunk VSAN configuration, 34 FCoE VSAN configuration, 33, 35 FCoE VSAN creation, 34 FCoE VSAN fundamentals, 33 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 zone database, 53 priority FCoE fabric switch priority setting, 23 FCoE FCF priority configuration, 15 FCoE system FCF priority configuration, 15 FCoE VFC interface FCF priority configuration, 16 procedure activating FCoE FC zone set, 62 configuring allowed domain ID list, 24 configuring fabric auto reconfiguration, 27 configuring fabric reconfiguration, 26 configuring fabric timer in system view, 25 configuring fabric timer in VSAN view, 26 configuring fabric VFC interface RCF request rejection, 27 configuring FC FSPF, 41, 49 configuring FC FSPF GR, 45 configuring FC FSPF GR Helper, 45 configuring FC FSPF GR Restarter, 45 configuring FC FSPF interface cost, 43 configuring FC FSPF interface dead interval, 44 configuring FC FSPF interface hello interval, 44 configuring FC FSPF interface LSR retransmission interval, 44 configuring FC FSPF min LSR receiving interval, 43 configuring FC FSPF min LSR refresh interval, 43 configuring FC FSPF shortest SPF calculation interval, 42 configuring FC static route, 41, 46 configuring FCoE dynamic fabric build, 30 configuring FCoE fabric distributed service timeout timer, 25 93

100 configuring FCoE fabric error detection timeout timer, 25 configuring FCoE fabric N_Port-WWN-to-FC address mapping, 25 configuring FCoE fabric resource allocation timeout timer, 25 configuring FCoE fabric switch domain IDs, 24 configuring FCoE FC default zone policy, 61 configuring FCoE FC ping, 75 configuring FCoE FC tracert, 78, 79 configuring FCoE FC zone aliases, 60 configuring FCoE FC zone distribution, 61 configuring FCoE FC zone merge type, 61 configuring FCoE FC zone sets, 61 configuring FCoE FC zones, 59, 60, 64 configuring FCoE FCF priority, 15 configuring FCoE FC-MAP value, 13 configuring FCoE FKA advertisement period value, 14 configuring FCoE mode for switch, 11 configuring FCoE static fabric build, 28 configuring FCoE system FCF priority, 15 configuring FCoE VFC interface, 12 configuring FCoE VFC interface FCF priority, 16 configuring NPV, 69, 71 configuring NPV downlink interface, 69, 70 configuring NPV downlink-to-uplink interface mapping, 70 configuring NPV uplink interface, 69 configuring trunk VSAN, 34 configuring VFC interfaces and FIP, 12, 16 configuring VSAN, 35 copying FCoE FC zone sets, 63 copying FCoE FC zones, 63 creating VSAN, 34 deleting FCoE FC zone database, 63 disabling FC FSPF for interface, 45 disabling FCoE fabric configuration, 22 displaying fabric, 27 displaying FC zones, 64 displaying NPV, 71 displaying VFC interfaces and FIP, 16 displaying VSAN, 35 distributing FCoE FC zone set to fabric, 62 enabling FC FSPF, 42 enabling FCoE fabric configuration, 22 enabling FCoE for VLAN, 13 initiating fabric manual reconfiguration, 27 initiating NPV disruptive load balancing process, 71 maintaining FC forwarding, 46 maintaining FC routing, 46 maintaining VFC interfaces and FIP, 16 mapping FCoE VSAN to VLAN, 13 renaming FCoE FC zone sets, 63 renaming FCoE FC zones, 63 setting FCoE fabric name, 23 setting FCoE fabric switch priority, 23 triggering FCoE FC zone distribution, 62 protocols and standards FC protocol, 2 FCoE, 9 FIP (FCoE initialization protocol), 6 renaming FCoE FC zone sets, 63 FCoE FC zones, 63 resource allocation timeout timer, 25 Role FKA advertisement period, 14 routing FC access control, 59 FC direct routes, 38, 39 FC FIB table, 38 FC FIB table contents, 39 FC FSPF configuration, 41, 49 FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 FC FSPF interface cost configuration, 43 FC FSPF interface dead interval configuration, 44 FC FSPF interface hello interval configuration, 44 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 FC FSPF packet types, 40 FC FSPF routes, 38, 40 FC FSPF shortest SPF calculation interval configuration, 42 FC routing table, 38 FC routing table contents, 38 FC static route configuration, 41, 46 FC static routes, 38, 39 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone distribution, 55 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 94

101 FC zone merge rules, 59 FCoE FC default zone policy configuration, 61 FCoE FC forwarding configuration, 38 FCoE FC ping configuration, 75 FCoE FC routing configuration, 38 FCoE FC tracert configuration, 78, 79 FCoE FC triggering zone set distribution, 62 FCoE FC zone alias configuration, 60 FCoE FC zone configuration, 53, 59, 60, 64 FCoE FC zone copying, 63 FCoE FC zone database deletion, 63 FCoE FC zone distribution configuration, 61 FCoE FC zone merge type configuration, 61 FCoE FC zone renaming, 63 FCoE FC zone set activation, 62 FCoE FC zone set configuration, 61 FCoE FC zone set copying, 63 FCoE FC zone set distribution to fabric, 62 FCoE FC zone set renaming, 63 zone database, 53 rule FC zone merge rules, 59 SAN FC address, 2 FC protocol, 2 FC SAN, 1 FCoE basic concepts, 2 FCoE communication flow, 3 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric configuration enable/disable, 22 FCoE fabric domain ID assignment, 20 FCoE fabric FC address assignment, 21 FCoE fabric N_Port-WWN-to-FC address mapping configuration, 25 FCoE fabric name setting, 23 FCoE fabric principal switch selection, 19 FCoE fabric setup, 19, 21 FCoE fabric switch domain ID configuration, 24 FCoE fabric switch priority setting, 23 FCoE fabric timer configuration, 25 FCoE FC default zone policy configuration, 61 FCoE FC forwarding configuration, 38 FCoE FC ping configuration, 75 FCoE FC routing configuration, 38 FCoE FC tracert configuration, 78, 79 FCoE FC triggering zone set distribution, 62 FCoE FC zone, 4 FCoE FC zone alias configuration, 60 FCoE FC zone configuration, 53, 59, 60, 64 FCoE FC zone copying, 63 FCoE FC zone database deletion, 63 FCoE FC zone distribution configuration, 61 FCoE FC zone merge type configuration, 61 FCoE FC zone renaming, 63 FCoE FC zone set activation, 62 FCoE FC zone set configuration, 61 FCoE FC zone set copying, 63 FCoE FC zone set distribution to fabric, 62 FCoE FC zone set renaming, 63 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE feature support by FCoE modes, 11 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE interface modes, 2 FCoE NPV configuration, 68, 69, 71 FCoE NPV disruptive load balancing, 69 FCoE NPV downlink, 68 FCoE NPV downlink interface, 68 FCoE NPV downlink-to-uplink interface mapping, 69 FCoE NPV mode, 9 FCoE NPV uplink, 68 FCoE NPV uplink interface, 68 FCoE static fabric building configuration, 28 FCoE system FCF priority configuration, 15 FCoE trunk VSAN, 33 FCoE trunk VSAN mode configuration, 34 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VSAN, 4 FCoE VSAN configuration, 33, 35 FCoE VSAN creation, 34 FCoE VSAN fundamentals, 33 FCoE VSAN to VLAN mapping, 13 FCoE well-known fabric addresses, 82 FCoE WWN, 2 VFC interfaces and FIP configuration, 12, 16 selecting fabric principal switch, 19 server FC SAN, 1 FCoE communication flow, 3 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric setup, 19, 21 FCoE FC zone, 4 FCoE feature support by FCoE modes, 11 FCoE NPV configuration, 68, 69, 71 95

102 FCoE NPV mode, 9 FCoE static fabric building configuration, 28 FCoE VSAN configuration, 33, 35 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 setting fabric setup, 19, 21 FCoE fabric name, 23 FCoE fabric switch priority, 23 static FC static route configuration, 41, 46 FC static routes, 38, 39 FCoE fabric static mode, 19, 21 FCoE static fabric building configuration, 28 storage area network. See SAN, VSAN switching FC access control, 59 FC address, 2 FC direct routes, 39 FC FSPF configuration, 41, 49 FC FSPF GR Helper configuration, 45 FC FSPF GR Restarter configuration, 45 FC FSPF interface cost configuration, 43 FC FSPF interface dead interval configuration, 44 FC FSPF interface hello interval configuration, 44 FC FSPF interface LSR retransmission interval configuration, 44 FC FSPF LSDB, 40 FC FSPF LSR, 40 FC FSPF min LSR receiving interval configuration, 43 FC FSPF min LSR refresh interval configuration, 43 FC FSPF packet types, 40 FC FSPF routes, 40 FC FSPF shortest SPF calculation interval configuration, 42 FC protocol, 2 FC SAN, 1 FC static route configuration, 41, 46 FC static routes, 39 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone distribution, 55 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FCoE basic concepts, 2 FCoE communication flow, 3 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric configuration enable/disable, 22 FCoE fabric domain ID assignment, 20 FCoE fabric FC address assignment, 21 FCoE fabric N_Port-WWN-to-FC address mapping configuration, 25 FCoE fabric name setting, 23 FCoE fabric principal switch selection, 19 FCoE fabric setup, 19, 21 FCoE fabric switch domain ID configuration, 24 FCoE fabric switch priority setting, 23 FCoE FC default zone policy configuration, 61 FCoE FC forwarding configuration, 38 FCoE FC ping configuration, 75 FCoE FC routing configuration, 38 FCoE FC tracert configuration, 78, 79 FCoE FC triggering zone set distribution, 62 FCoE FC zone, 4 FCoE FC zone alias configuration, 60 FCoE FC zone configuration, 53, 59, 60, 64 FCoE FC zone copying, 63 FCoE FC zone database deletion, 63 FCoE FC zone distribution configuration, 61 FCoE FC zone merge type configuration, 61 FCoE FC zone renaming, 63 FCoE FC zone set activation, 62 FCoE FC zone set configuration, 61 FCoE FC zone set copying, 63 FCoE FC zone set distribution to fabric, 62 FCoE FC zone set renaming, 63 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE feature support by FCoE modes, 11 FCoE FIP operation, 7 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE frames, 6 FCoE interface modes, 2 FCoE NPV configuration, 68, 69, 71 FCoE NPV disruptive load balancing, 69 FCoE NPV disruptive load balancing process initiation, 71 FCoE NPV downlink, 68 FCoE NPV downlink interface, 68 FCoE NPV downlink interface configuration, 69, 70 FCoE NPV downlink-to-uplink interface mapping, 69 96

103 FCoE NPV downlink-to-uplink interface mapping configuration, 70 FCoE NPV mode, 9 FCoE NPV uplink, 68 FCoE NPV uplink interface, 68 FCoE NPV uplink interface configuration, 69 FCoE static fabric building configuration, 28 FCoE system FCF priority configuration, 15 FCoE trunk VSAN configuration, 34 FCoE VFC interface, 5 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VN interface, 5 FCoE VSAN, 4 FCoE VSAN configuration, 33, 35 FCoE VSAN creation, 34 FCoE VSAN to VLAN mapping, 13 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 zone database, 53 table FC cost routing table entry, 38 FC destination FIB table entry, 39 FC destination routing table entry, 38 FC FIB table, 38 FC FIB table contents, 39 FC interface FIB table entry, 39 FC interface routing table entry, 38 FC mask FIB table entry, 39 FC mask routing table entry, 38 FC preference routing table entry, 38 FC routing table, 38 FC routing table contents, 38 timer FCoE fabric distributed service timeout timer, 25 FCoE fabric error detection timeout timer, 25 FCoE fabric resource allocation timeout timer, 25 tracert FCoE FC tracert configuration, 78, 79 triggering FCoE FC zone set distribution, 62 trunk FCoE trunk VSAN, 33 FCoE trunk VSAN configuration, 34 type FC direct routes, 38 FC FSPF LSA packet type, 40 FC FSPF routes, 38 FC static routes, 38 FCoE FC zone merge type configuration, 61 unsolicited discovery advertisement FKA advertisement period, 14 VFC interface FKA advertisement period, 14 VFC interfaces and FIP configuration, 12, 16 displaying, 16 maintaining, 16 virtual link FIP, 6 FKA advertisement period, 14 unsolicited discovery advertisement, 14 virtualization FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric setup, 19, 21 FCoE FC ping configuration, 75 FCoE FC tracert configuration, 78, 79 FCoE FC zone configuration, 53, 59, 64 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE feature support by FCoE modes, 11 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE NPV configuration, 68, 69, 71 FCoE NPV mode, 9 FCoE static fabric building configuration, 28 FCoE system FCF priority configuration, 15 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VSAN configuration, 33, 35 FCoE VSAN to VLAN mapping, 13 FCoE well-known fabric addresses, 82 VFC interfaces and FIP configuration, 12, 16 VLAN FCoE for VLAN enable, 13 FCoE VSAN to VLAN mapping, 13 VN interface FCoE frame, 6 VSAN configuration, 33, 35 configuring allowed domain ID list, 24 creation, 34 displaying, 35 FC access control, 59 FC address, 2 FC default zone policy configuration, 61 FC forwarding configuration, 38 FC ping configuration, 75 FC protocol, 2 97

104 FC routing configuration, 38 FC SAN, 1 FC tracert configuration, 78, 79 FC triggering zone set distribution, 62 FC zone alias configuration, 60 FC zone configuration, 53, 59, 60, 64 FC zone copying, 63 FC zone database, 53 FC zone database active zone set, 54 FC zone database default zone, 55 FC zone database deletion, 63 FC zone distribution, 55 FC zone distribution configuration, 61 FC zone distribution process, 55 FC zone distribution triggering methods, 55 FC zone merge process, 57 FC zone merge rules, 59 FC zone merge type configuration, 61 FC zone renaming, 63 FC zone set activation, 62 FC zone set configuration, 61 FC zone set copying, 63 FC zone set distribution to fabric, 62 FC zone set renaming, 63 FCoE, 4 FCoE basic concepts, 2 FCoE communication flow, 3 FCoE description, 4 FCoE dynamic fabric building configuration, 30 FCoE fabric address assignment, 82 FCoE fabric configuration enable/disable, 22 FCoE fabric domain ID assignment, 20 FCoE fabric FC address assignment, 21 FCoE fabric N_Port-WWN-to-FC address mapping configuration, 25 FCoE fabric name setting, 23 FCoE fabric principal switch selection, 19 FCoE fabric setup, 19, 21 FCoE fabric switch domain ID configuration, 24 FCoE fabric switch priority setting, 23 FCoE fabric timer configuration, 25 FCoE FC zone, 4 FCoE FCF priority configuration, 15 FCoE FC-MAP value configuration, 13 FCoE feature support by FCoE modes, 11 FCoE FKA advertisement period value configuration, 14 FCoE for VLAN enable, 13 FCoE interface modes, 2 FCoE NPV configuration, 68, 69, 71 FCoE NPV disruptive load balancing, 69 FCoE NPV downlink, 68 FCoE NPV downlink interface, 68 FCoE NPV downlink-to-uplink interface mapping, 69 FCoE NPV mode, 9 FCoE NPV uplink, 68 FCoE NPV uplink interface, 68 FCoE static fabric building configuration, 28 FCoE system FCF priority configuration, 15 FCoE VFC interface configuration, 12 FCoE VFC interface FCF priority configuration, 16 FCoE VSAN to VLAN mapping, 13 FCoE well-known fabric addresses, 82 FCoE WWN, 2 fundamentals, 33 trunk configuration, 34 trunk VSAN, 33 VFC interfaces and FIP configuration, 12, 16 zone database, 53 well-known fabric addresses (FCoE), 82 WWN (FCoE), 2 zone database, 53 database structure, 53 database structure active zone set, 54 database structure default zone, 55 distribution, 55 distribution process, 55 distribution triggering methods, 55 FCoE FC default zone policy configuration, 61 FCoE FC triggering zone set distribution, 62 FCoE FC zone, 4 FCoE FC zone alias configuration, 60 FCoE FC zone configuration, 53, 59, 60, 64 FCoE FC zone copying, 63 FCoE FC zone database deletion, 63 FCoE FC zone distribution configuration, 61 FCoE FC zone merge type configuration, 61 FCoE FC zone renaming, 63 FCoE FC zone set activation, 62 FCoE FC zone set configuration, 61 FCoE FC zone set copying, 63 FCoE FC zone set distribution to fabric, 62 FCoE FC zone set renaming, 63 merge process, 57 merge rules, 59 98