Brocade Communications Systems StoreFabric SN6500B Administrator's Manual
  1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Switch
  5. StoreFabric SN6500B
  6. Administrator's manual
Brocade Communications Systems StoreFabric SN6500B Administrator's Manual

Brocade Communications Systems StoreFabric SN6500B Administrator's Manual

Brocade fabric os fcip administrator's guide v7.1.0 (53-1002748-01, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Administrator's Manual
53-1002748-01
®
14 December 2012
Fabric OS FCIP
Administrator's Guide
Supporting Fabric OS v7.1.0

Advertisement

Table of Contents
loading

Related Manuals for Brocade Communications Systems StoreFabric SN6500B

Summary of Contents for Brocade Communications Systems StoreFabric SN6500B

  • Page 1 53-1002748-01 ® 14 December 2012 Fabric OS FCIP Administrator’s Guide Supporting Fabric OS v7.1.0...
  • Page 2 Copyright © 2009-2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
  • Page 3 Document History Title Publication number Summary of changes Date Fabric OS FCIP Administrator’s Guide 53-1001349-01 New document. July 2009 Fabric OS FCIP Administrator’s Guide 53-1001349-02 Various changes and October 2009 corrections. Fabric OS FCIP Administrator’s Guide 53-1001755-01 New document for Fabric OS January 2010 version 6.3.1.
  • Page 4 Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 5: Table Of Contents

    Contents About This Document How this document is organized ......ix Supported hardware and software ......ix What’s new in this document .
  • Page 6 FCIP Trunking..........16 Design for redundancy and fault tolerance .
  • Page 7 Modifying an FCIP tunnel ........54 Modifying an FCIP circuit ........54 Deleting an IP interface .
  • Page 8 viii Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 9: About This Document

    About This Document • How this document is organized ........ix •...

  • Page 10: What's New In This Document

    What’s new in this document Major new additions or deletions in this document support the following: • General Removed all mention of FR4-18i blade since it is not supported as of this release. • Preface. Removed FR4-18i from “Supported hardware and software” on page ix.

  • Page 11: Document Conventions

    • Chapter 3 Removed chapter 3 from previous release, titled “FCIP on the FR4-18i blade.” Chapter 3 now becomes “FCIP Management and Troubleshooting.” Removed “portCmd --ipperf” under “WAN performance analysis tools” on page 66 since this is a tool specific to FR4-18i blade. Also, the command in last bullet in this section was changed to portShow fcipTunnel --perf.

  • Page 12: Command Syntax Conventions

    Command syntax conventions Command syntax in this manual follows these conventions: command Commands are printed in bold. option, option Command options are printed in bold. argument, arg Arguments. Optional element. variable Variables are printed in italics. In the help pages, variables are underlined or enclosed in angled brackets <...

  • Page 13: Key Terms

    Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. “Brocade resources” on page xiii for instructions on accessing MyBrocade. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.org/education/dictionary Notice to the reader This document may contain references to the trademarks of the following corporations.

  • Page 14: Getting Technical Help

    http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website: http://www.fibrechannel.org Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1.

  • Page 15: Document Feedback

    Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.com Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
  • Page 16 Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 17: Fcip Overview

    Chapter FCIP Overview • FCIP platforms and supported features......1 • FCIP concepts .

  • Page 18: Fcip Concepts

    FCIP concepts TABLE 1 FCIP capabilities by platform (Continued) Capabilities 7800 switch FX8-24 blade • Enforcement 802.1P - VLAN tagging FICON extension • FICON emulation • IBM z/OS Global Mirror (formerly eXtended Remote Copy or XRC) acceleration • Tape read acceleration •...

  • Page 19: Ip Wan Network Considerations

    IP WAN network considerations FC-IP FC-IP FC-2 FC-2 FC-1 FC-1 LINK LINK FC-0 FC-0 To Fibre Channel To Fibre Channel FCIP Tunnel FIGURE 1 FCIP tunnel concept and TCP/IP layers Each FCIP tunnel is assigned to a single VE_Port and supports a single circuit. The circuit provides the link for traffic between the source and destination IP addresses on either end of the tunnel.
  • Page 20 IP WAN network considerations Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 21: Fcip On The 7800 Switch And Fx8-24 Blade

    Chapter FCIP on the 7800 Switch and FX8-24 Blade In this chapter • 7800 switch hardware overview........6 •...

  • Page 22: 7800 Switch Hardware Overview

    7800 switch hardware overview 7800 switch hardware overview Figure 2 shows the FC ports and GbE ports on the 7800 switch. There are 16 FC ports, numbered 0 through 15. The FC ports can operate at 1, 2, 4, or 8 Gbps. There are six GbE ports, numbered 0 through 5.

  • Page 23: 7800 Switch License Options

    7800 switch license options 7800 switch license options Some of the capabilities of the Brocade 7800 switch require the following feature licenses, as described in Table • The Advanced FICON Acceleration License enables all FICON emulation features: FICON Tape Read Pipelining FICON Tape Write Pipelining FICON IBM z/OS Global Mirror (formerly eXtended Remote Copy or XRC) Emulation FICON Teradata Emulation...

  • Page 24: Ve_Ports And Fcip Tunnels On The 7800 Switch

    FX8-24 blade hardware overview VE_Ports and FCIP tunnels on the 7800 switch A 7800 switch can support eight VE_Ports. VE_Ports are numbered from 16 through 23. Each FCIP tunnel is identified with a VE_Port number. Up to eight FCIP tunnels can be created. The 7800 switch supports VEX_Ports to avoid the need to merge fabrics.
  • Page 25 FX8-24 blade hardware overview 10GbE ports (Labeled xge0 and xge1 FC ports 0 through 5 on the sticker.) GbE ports 0 through 3 Power LED GbE ports 4 through 9 Status LED FC ports 6 through 11 FIGURE 3 FX8-24 blade FC and GbE ports Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 26: Removing Fx8-24 Blades

    FX8-24 blade license options Removing FX8-24 blades ATTENTION If you are permanently removing a blade from a DCX, DCX-4S, DCX 8510-8, or DCX 8510-4 chassis to relocate to another slot in the chassis or you are removing the blade from the chassis entirely, you must follow these procedures before removing the blade.

  • Page 27: Ve_Ports And Fcip Tunnels On The Fx8-24 Blade

    FX8-24 blade license options VE_Ports and FCIP tunnels on the FX8-24 blade An FX8-24 blade can support 20 VE_Ports, and therefore 20 FCIP tunnels. There are two VE_Port groups, numbered 12 through 21 and 22 through 31. Each FCIP tunnel is associated with a specific VE_Port.

  • Page 28: 10 Gbe Port Considerations

    FX8-24 blade license options 10 GbE port considerations Enhanced 10GbE port operation is different than 1 GbE port operation and requires special considerations when configuring circuits, tunnels, failover operations, and bandwidth. Multigigabit circuits For each 10 GbE port, you can configure multigigabit circuits. For example, a single 10 Gbps circuit or two 5 Gbps circuits can be configured per port.
  • Page 29 FX8-24 blade license options Back-end bandwidth Back-end port bandwidth allocation is calculated as follows: • Back-end bandwidths are always rounded up to the nearest 1 Gbps. For example, 1.5 Gbps actually consumes 2 Gbps of back-end bandwidth. • Each VE_Port group is allocated 10 Gbps of back-end bandwidth (10 Gbps for the VE_Port 12-21 group and 10 Gbps for the VE_Port 22-31 group).
  • Page 30 FX8-24 blade license options portcfg ipif 8/xge0 create 192.168.11.20 255.255.255.0 1500 –x Delete the crossport address using the delete option instead of the create option for the portcfg ipif command. portcfg ipif 8/xge0 delete 192.168.11.20 255.255.255.0 1500 –x NOTE If the crossport or x option is not specified and the address is on the crossport, the command will fail with an unknown IP address.
  • Page 31 FX8-24 blade license options For more information on configuring an IP route, refer to “Configuring an IP route” on page 41. For more information on using Fabric OS commands, optional arguments, and command output refer to the Fabric OS Command Reference Manual. NOTE If an XGE port has both regular and crossport addresses configured on it, and they use the same IP route, then two routes will need to be configured—a regular route and an identical route on the cross...

  • Page 32: Fcip Trunking

    FCIP Trunking Using traceroute with crossports You can trace a route to a crossport address, as in the following example. Note that if the crossport or x options are not specified and the address is on the crossport, the portcmd command will fail with an unknown IP address.The command will also fail if the x option is specified and the address is not on the crossport.

  • Page 33: Design For Redundancy And Fault Tolerance

    FCIP Trunking IP Router IP Router 10.0.0.1 10.0.1.1 FCIP Circuits FCIP Circuits 10.0.0.2 10.0.1.2 10.0.0.3 10.0.1.3 10.0.0.4 10.0.1.4 10.0.0.5 10.0.1.5 FCIP Tunnel FIGURE 4 FCIP tunnel and FCIP circuits Design for redundancy and fault tolerance Multiple FCIP tunnels can be defined between pairs of 7800 switches or FX8-24 blades, but doing so defeats the benefits of a multiple circuit FCIP tunnel.

  • Page 34: Fcip Circuits

    FCIP Trunking • When configuring tunnels to support large numbers of devices, consider memory limitations of the Brocade 7800 switch and FX8-24 blade if you are enabling any type of emulation feature, such as FCP or FICON. If too many devices are present or activated at one time, emulation operations can be negatively impacted.

  • Page 35: Fcip Circuit Failover Capabilities

    FCIP Trunking A limit of 10 FCIP circuits can be configured on a single 10 GbE port. A limit of 20 FCIP circuits can be configured per VE port group (12 through 21 or 22 through 31) when using a 10G port. For the 20 circuits, 10 are configured on local ports and 10 on crossports For a FX8-24 blade with a VE_Port group on a 10GbE port, the sum of the maximum committed rates of that group's circuits cannot exceed 10 Gbps.
  • Page 36 FCIP Trunking Circuit 1 - Metric 0 - Active 7800 7800 Circuit 2 - Metric 1 - Standby FIGURE 6 Failover to a higher metric standby circuit 10GbE Lossless Link Loss Circuit failover is supported between 10GbE circuits on FX8-24 blades when both 10GbE ports are on the same logical switch and are operating in 10 Gbps mode.
  • Page 37 FCIP Trunking Active-active configuration The following examples shows an active-active configuration in which two circuits are configured with the same metric, one circuit going over xge0 and the other circuit going over the crossport using xge1 as the external port. The metric values of both the circuits are the same (default value), so both circuits send data.

  • Page 38: Failover In Ti Zones

    FCIP Trunking 5. Display local and crossport interface details for xge0. portshow ipif 8/xge0 NOTE If the source and destination addresses are on different subnets, you must configure IP routes to the destination addresses. Refer to “Configuring an IP route” on page 41.

  • Page 39: Adaptive Rate Limiting

    Adaptive Rate Limiting Adaptive Rate Limiting Adaptive Rate Limiting (ARL) is performed on FCIP circuits to change the rate in which the FCIP tunnel transmits data through the IP network. ARL uses information from the TCP connections to determine and adjust the rate limit for the FCIP circuit dynamically. This allows FCIP connections to utilize the maximum available bandwidth while providing a minimum bandwidth guarantee.
  • Page 40 PP-TCP-QoS priorities over an FCIP trunk • QoS medium - The default value is 30 percent of the available bandwidth. • QoS low - The default value is 20 percent of the available bandwidth. QoS priority is based on the VC (Virtual Circuit) that carries data into the FCIP Engine. For example, if data enters on a high VC, it is placed on a high TCP connection;...

  • Page 41: Qos, Dscp, And Vlans

    QoS, DSCP, and VLANs • QoS priority settings must be the same on each end of the tunnel. NOTE Priorities are enforced only when there is congestion on the network. If there is no congestion, all traffic is handled at the same priority. Following are some examples of setting QoS priority levels on VE_Port 12: •...

  • Page 42: Vlans And Layer 2 Quality Of Service

    QoS, DSCP, and VLANs DSCP settings are useful only if IP routers are configured to enforce QoS policies uniformly within the network. IP routers use the DSCP value as an index into a Per Hop Behavior (PHB) table. Control connections and data connections can be configured with different DSCP values. Before configuring DSCP settings, determine if the IP network you are using implements PHB, and consult with the WAN administrator to determine the appropriate DSCP values.

  • Page 43: Dscp And Vlan Support On Fcip Circuits

    QoS, DSCP, and VLANs TABLE 4 Default mapping of DSCP priorities to L2CoS priorities (Continued) DSCP priority/bits L2CoS priority/bits Assigned to: 59 / 111011 4 / 100 High QoS 63 / 111111 0 / 000 Reserved DSCP and VLAN support on FCIP circuits When VLAN tag is created on an FCIP circuit, all traffic over that circuit will use the specified VLAN.

  • Page 44: Managing The Vlan Tag Table

    QoS, DSCP, and VLANs The following example creates an additional FCIP circuit with a different VLAN tag. switch:admin> portcfg fcipcircuit 16 create 1 192.168.2.21 192.168.2.11 100000 -v 200 Operation Succeeded The following example shows the fcipcircuit modify command that changes the VLAN tag and L2CoS levels for circuit 0.

  • Page 45: Compression Options

    Compression options The following example adds an entry that tags all frames from IP address 192.168.10.1 destined for IP address 192.168.20.1 with a VLAN ID of 100, and a L2CoS value of 3. switch:admin> portcfg vlantag 8/ge0 add 192.168.10.1 100 3 192.168.20.1 The following example adds an entry that tags al frames from a crossport with local address 192.168.11.20, VLAN ID of 200, and a LSCoS value of 1.

  • Page 46: Ipsec Implementation Over Fcip Tunnels

    IPsec implementation over FCIP tunnels IPsec implementation over FCIP tunnels Internet Protocol security (IPsec) uses cryptographic security to ensure private, secure communications over Internet Protocol networks. IPsec supports network-level data integrity, data confidentiality, data origin authentication, and replay protection. It helps secure your SAN against network-based attacks from untrusted computers.

  • Page 47: Enabling Ipsec And Ike Policies

    IPsec implementation over FCIP tunnels • IKEv2 uses UDP port 500 to communicate between the peer switches or blades. • All IKEv2 traffic is protected using AES-GCM-ESP encryption. • Authentication requires the generation and configuration of 32-byte pre-shared secrets for each tunnel.

  • Page 48: Open Systems Tape Pipelining

    Open Systems Tape Pipelining portcfg fciptunnel 17 create 192.168.0.91 192.168.0.81 50000 -x 0 -d c0 -i -K12345678901234567890123456789012 -l portcfg fcipcircuit 17 create 1 192.168.1.91 192.168.1.81 50000 -x 0 portcfg fcipcircuit 17 create 2 192.168.2.91 192.168.2.81 50000 -x 0 portcfg fcipcircuit 17 create 3 192.168.3.91 192.168.3.81 50000 -x 0 portcfg fcipcircuit 17 create 4 192.168.4.91 192.168.4.81 50000 -x 0 portcfg fcipcircuit 17 create 5 192.168.5.91 192.168.5.81 50000 -x 0 Open Systems Tape Pipelining...
  • Page 49 Open Systems Tape Pipelining FCIP tunnel FW=1, TA=1 FC SAN FC SAN Connection can be VE-VE or VEX-VE 172.0.1.2 FIGURE 8 Single tunnel, Fastwrite and OSTP enabled FC SAN FCIP tunnel 1 FC SAN FW=1, TA=1 FC SAN FIGURE 9 Multiple tunnels to multiple ports, Fastwrite and OSTP enabled on a per-tunnel/per-port basis Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 50: Support For Ipv6 Addressing

    Support for IPv6 addressing In some cases, traffic isolation zoning (TIZ) or VF LS/LF configurations may be used to control the routing of SID/DID pairs to individual tunnels. This provides deterministic flows between the switches and allows the use of ECMP. Refer to the Fabric OS Administrator’s Guide for more information about TIZ.

  • Page 51: Ipv6 With Embedded Ipv4 Addresses

    Memory use limitations for large-device tunnel configurations • The Neighbor Discovery ICMPv6 Solicitations and Advertisements are transmitted to the Layer 2 Ethernet multicast MAC address derived from the IPv6 source address (RFC 2464). • ICMPv6 message types in RFC 4443 and ICMPv6 message types used for Neighbor Discovery are supported.

  • Page 52: Control Blocks Created During Fcp Traffic Flow

    Memory use limitations for large-device tunnel configurations Control blocks created during FCP traffic flow For FICON traffic flows, FCIP tunnel processing creates control block structures based upon the SID/DID pairs called a FICON device port, path block (FDPB). If any FICON emulation feature is enabled, additional control blocks are created for each SID/DID pair, LPAR number (FCHB structure), LCU Number (FCUB structure) and for each individual FICON device address on those LCUs (FDCB structure).

  • Page 53: Configuration Preparation

    Configuration preparation NOTE The 7800 is expected to support no more than about 120,000 extended device images (FICON or FCP). A single FX8-24 DP is expected to support no more than 160,000 extended device images. Configuration preparation Before you begin to configure FCIP, do the following: •...

  • Page 54: Configuration Steps

    Configuration steps Configuration steps The following is a list of the major steps for configuring FCIP on the 7800 switch or FX8-24 blade: • Persistently disable VE_Ports. • If required, configure VEX_Ports. • For the 7800 switch, set the media type for GbE ports 0 and 1. •...

  • Page 55: Configuring Vex_Ports

    Configuration steps You can determine if fmsmode is enabled by using the ficoncupshow fmsmode command. Configuring VEX_Ports If you are going to use a VEX_Port in your tunnel configuration, use the portCfgVEXPort command to configure the port as a VEX_Port. VEX_Ports can be used to avoid merging fabrics over distance in FCIP implementations.

  • Page 56: Setting The Gbe Port Operating Mode (Fx8-24 Blade Only)

    Configuration steps Port ge1 is configured in optical mode Setting the GbE port operating mode (FX8-24 blade only) The GbE ports on an FX8-24 blade can operate in one of three ways: • 1 Gbps mode. GbE ports 0 through 9 may be enabled as GbE ports, with the XGE ports disabled.

  • Page 57: Configuring An Ip Route

    Configuration steps The following command creates an IP interface for port ge0 on the Brocade 7800 switch. switch:admin> portcfg ipif ge0 create 192.168.1.78 255.255.255.0 1500 Use the following command to display current configuration details for all interfaces. portshow ipf all NOTE For full details on syntax and using this command, refer to the Fabric OS Command Reference Manual.

  • Page 58: Validating Ip Connectivity

    Configuration steps Storage Brocade DCX-4S with FX8-24 Blade Server Gateway Gateway 192.168.1.1 192.168.11.1 Brocade 7800 VE_Port VE_Port 192.168.1.24 192.168.11.78 FIGURE 11 Configuring an IP route For information on configuring IP routes using crossport addresses, refer to “Configuring IP routes with crossports” on page 14.
  • Page 59 Configuration steps The following command creates the 7800 end of the tunnel. VE_Port 16 is specified. Circuit parameters are included to create circuit 0 on the 7800. The circuit parameters must match up correctly with the circuit parameters on the FX8-24 end of the circuit. The FX8-24 destination address is specified first, followed by the 7800 switch source address.
  • Page 60 Configuration steps TABLE 7 Tunnel options Option Arguments Disruptive Description Compression Short option: -c Enables compression on an FCIP tunnel. Compression is set by the portCfg Long option: --compression fciptunnel create or modify command, and Operands: 0|1|2|3|4| applies to traffic over all circuits in the tunnel.
  • Page 61 Configuration steps TABLE 7 Tunnel options (Continued) Option Arguments Disruptive Description Remote FC WWN Short Option: -n This is a fabric security feature that allows you to only allow the FCIP tunnel to come Long Option: --remote-wwn up when the correct remote WWN is entered.
  • Page 62 Configuration steps TABLE 8 Circuit options Option Argument Disruptive Description Committed rate committed rate This option may be used on a portcfg fciptunnel create command or on the portcfg fcipcircuit create command to set a Create behavior: Sets the committed rate for an FCIP circuit. When minimum and maximum this option is used on the portcfg committed rate to the value...
  • Page 63 Configuration steps TABLE 8 Circuit options (Continued) Option Argument Disruptive Description Selective Short option: -s Disables or enables selective acknowledgement acknowledgement. Selective Long option: --sack acknowledgement allows a receiver to Operands (modify only): 0|1 acknowledge multiple lost packets with a single ACK response.
  • Page 64 Configuration steps TABLE 8 Circuit options (Continued) Option Argument Disruptive Description Specify connection type Short option: -C Allows you to specify which side of the Long option: circuit is the listener or initiator. If this is --connection-type not specified, the initiator or listener are Operands: automatically selected based on the lower default|listener|initiator...

  • Page 65: Creating Additional Fcip Circuits

    Configuration steps Creating additional FCIP circuits If the Advanced Extension (FTR_AE) license is enabled, additional FCIP circuits can be created and added to an FCIP tunnel (VE_Port) using the portCfg fcipcircuit create command. The following examples add a circuit to the tunnel in the basic sample configuration (refer to Figure 12 page 43).

  • Page 66: Enabling Persistently Disabled Ports

    Creating a multicircuit tunnel (example) Enabling persistently disabled ports It is strongly recommended to disable ports while they are being configured to prevent unwanted fabric merges. 1. Connect to the switch and log in using an account assigned to the admin role. 2.
  • Page 67 Creating a multicircuit tunnel (example) • “Creating an FCIP tunnel” on page 42 • “Creating additional FCIP circuits” on page 49 To create a tunnel between two switches or blades, you must first understand the IP network infrastructure between the sites. Each circuit requires a pair of IP interface addresses (either IPv4 or IPv6).
  • Page 68 Creating a multicircuit tunnel (example) Site B portcfg fciptunnel 16 create --ficon -c 1 • To use this tunnel for FCP with Fastwrite and Open Systems Tape Pipelining traffic, and hardware compression, create it using the following commands. Site A portcfg fciptunnel 16 create --fastwrite --tape-pipelining -c 1 Site B portcfg fciptunnel 16 create --fastwrite --tape-pipelining -c 1...
  • Page 69 Creating a multicircuit tunnel (example) Site B portcfg fcipcircuit 16 create 0 192.168.0.63 192.168.0.64 -b 1000000 -B 1000000 portcfg fcipcircuit 16 create 1 192.168.1.63 192.168.1.64 -b 1000000 -B 1000000 portcfg fcipcircuit 16 create 2 192.168.2.63 192.168.2.64 -b 1000000 -B 1000000 portcfg fcipcircuit 16 create 3 192.168.3.63 192.168.3.64 -b 1000000 -B 1000000 portcfg fcipcircuit 16 create 4 192.168.4.63 192.168.4.64 -b 1000000 -B...

  • Page 70: Modifying An Fcip Tunnel

    Modifying an FCIP tunnel Modifying an FCIP tunnel FCIP tunnel characteristics and options can be modified as needed, using the portCfg fcipTunnel command with the modify option. The command syntax is as follows: portCfg fciptunnel ve_port modify <options> Where: ve_port Each tunnel is assigned to a specific VE_Port.

  • Page 71: Deleting An Ip Interface

    Deleting an IP interface Deleting an IP interface You can delete an IP interface using the portcfg ipif command with the delete option. The command syntax is as follows: portcfg ipif [slot/]ge n delete ipaddr For full details on syntax and using this command, refer to the Fabric OS Command Reference Manual.

  • Page 72: Deleting An Fcip Circuit

    Deleting an FCIP circuit Deleting an FCIP circuit You can delete individual FCIP circuits using the portCfg fcipcircuit command with the delete option. The command syntax is as follows: portcfg fcipcircuit ve_port delete circuit_id For full details on syntax and using this command, refer to the Fabric OS Command Reference Manual.
  • Page 73 Virtual Fabrics • Logical switch 1 has VE17, which has a circuit over GbE0 • Logical switch 2 has VE18, which also has a circuit over GbE0 All of the committed-rate restrictions and bandwidth sharing of the GbE ports for ARL remain the same for shared ports in the logical switches.
  • Page 74 Virtual Fabrics Fabric OS FCIP Administrator’s Guide 53-1002748-01...

  • Page 75: Fcip Management And Troubleshooting

    Chapter FCIP Management and Troubleshooting In this chapter • Inband management..........59 •...

  • Page 76: Ip Routing

    Inband management IP routing The inband management interfaces are separate from the existing IP interfaces currently used for FCIP. These interfaces exist on the CP and are added and maintained on the CP routing table to ensure end-to-end connectivity. Because this routing table will be shared among all devices on the CP, including the management interface, precautions must be taken to ensure that proper connectivity is maintained.
  • Page 77 Inband management 7800 L1 Configure the inband management interfaces. portcfg mgmtif ge0 create 192.168.3.10 255.255.255.0 7800 R1 Configure the inband management interfaces. portcfg mgmtif ge0 create 192.168.3.20 255.255.255.0 Management station Access the Brocade 7800 switches through the external inband management station. telnet 192.168.3.10 Management station on a different subnet example The example configuration in...
  • Page 78 Inband management 7800 L1 1. Configure the inband management interfaces. portcfg mgmtif ge0 create 192.168.1.10 255.255.255.0 2. Configure the inband management route for the management station. portcfg mgmtroute ge0 create 192.168.3.0 255.255.255.0 192.168.1.250 7800 R1 1. Configure the inband management interfaces. portcfg mgmtif ge0 create 192.168.2.20 255.255.255.0 2.
  • Page 79 Inband management Management Router C Workstation 192.168.3.250 172.0.1.3 192.168.3.30 192.168.3.31 Router A Router B 172.0.1.0 Subnet 172.0.1.1 172.0.1.2 192.168.1.250 192.168.4.250 192.168.1.10 192.168.2.20 192.168.4.10 192.168.5.21 7800 L1 7800 R1 10.1.1.10 10.1.2.20 FIGURE 16 Redundant connection to management station 7800 L1 1. Configure the inband management interfaces. portcfg mgmtif ge0 create 192.168.1.10 255.255.255.0 portcfg mgmtif ge1 create 192.168.4.10 255.255.255.0 2.

  • Page 80: Vlan Tagging Support

    Inband management route add 192.168.5.0 netmask 255.255.255.0 gw 192.168.3.250 2. Access the 7800 switches through the external inband management interfaces. telnet 192.168.1.10 VLAN tagging support To add VLAN tag entries to the VLAN tag table for inband management interfaces, use the --mgmt or -m option with the portcfg vlantag command.
  • Page 81 Inband management For this example, you must configure the following: • On the management station: IP address 10.1.1.1/24 (defined) IP route to 192.168.3.20/32 via 10.1.1.10 • On the 7800 L1: CP Management address 10.1.1.10/24 Inband management address 192.168.3.10/24 IP filter forward rule with destination IP address 192.168.3.20 •...

  • Page 82: Wan Performance Analysis Tools

    WAN performance analysis tools WAN performance analysis tools WAN analysis tools are designed to test connections, trace routes, and estimate the end-to-end IP path performance characteristics between a pair of Brocade FCIP port endpoints. These tools are available as options on the portCmd command. The following options are available: •...
  • Page 83 WAN performance analysis tools 0 ge0 ---4--s 1h21m34s 0.00 0.00 500/500 1 ge1 ---4--s 1h21m43s 0.00 0.00 500/500 ------------------------------------------------------------------------------- Flags: tunnel: c=compression m=moderate compression a=aggressive compression A=Auto compression f=fastwrite t=Tapepipelining F=FICON T=TPerf i=IPSec l=IPSec Legacy Flags: circuit: s=sack v=VLAN Tagged x=crossport 4=IPv4 6=IPv6 T=Test(CPerf) L=Listener I=Initiator The previous display shows VE_Port 16 as up, but a switchshow command for that same VE _Port will show the following:...

  • Page 84: Using Ping To Test A Connection

    WAN performance analysis tools Using ping to test a connection The portCmd ping command tests the connection between the IP address of a local Ethernet port and a destination IP address. If you want to use this command to test a VLAN connection when you do not have an active FCIP tunnel, you must manually add entries to the VLAN tag table on both the local and remote sides of the route, using portCfg vlantag command.

  • Page 85: Portshow Command Usage

    Portshow command usage Portshow command usage Use the portshow command to display port operational information on Brocade 7800 switches, and FX8-24 blades. The Fabric OS Command Reference Manual provides complete descriptions of portshow command syntax and options. The following sections identify a few specific outputs that may be useful for maintenance and troubleshooting.

  • Page 86: Displaying Performance Statistics

    Portshow command usage Displaying performance statistics Display a summary of performance statistics for tunnels and circuits using the circuit, perf, and summary options as in the following example. switch:admin> portshow fciptunnel all --circuit --perf --summary For details of command syntax and output examples, refer to the Fabric OS Command Reference Manual.

  • Page 87: Displaying Fcip Tunnel Performance

    Portshow command usage Displaying FCIP tunnel performance The following example will display performance statistics for tunnel associated with port 17 on a 7800 switch. switch:admin> portshow fciptunnel 17 --perf For details of command syntax and output examples, refer to the Fabric OS Command Reference Manual.

  • Page 88: Displaying Tcp Statistics For Circuits

    Portshow command usage Displaying TCP statistics for circuits The following example displays TCP statistics for circuits associated with VE_Port 12 of a FX8-24 blade. switch:admin>portshow fcipcircuit 3/12 --tcp You can reset statistics counters to zero to display only new statistics with the --tcp option from the time you issue the reset using the following command.

  • Page 89: Fcip Tunnel Issues

    FCIP tunnel issues For details of command syntax and output examples, refer to the Fabric OS Command Reference Manual. FCIP tunnel issues The following are common FCIP tunnel issues and recommended actions for you to follow to fix the issue. Symptom FCIP tunnel does not come Online.

  • Page 90: Fcip Links

    FCIP links Get a GE Ethernet sniffer trace. Rule out all possible blocking factors. Routers and firewalls that are in the data path must be configured to pass FCIP traffic (TCP port 3225) and IPsec traffic, if IPsec is used (UDP port 500).

  • Page 91: Gathering Additional Information

    FCIP links • If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the edge fabric. • Because of an IPsec RASLog limitation, you may not be able to determine an incorrect configuration that causes an IPsec tunnel to not become active.

  • Page 92: Ftrace Concepts

    FTRACE concepts FTRACE concepts FTRACE is a support tool used primarily by your switch support provider. FTRACE can be used in a manner similar to that of a channel protocol analyzer. FTRACE may be used to troubleshoot problems using a Telnet session rather than sending an analyzer or technical support personnel to the site.

  • Page 93: Index

    Index Numerics 10GbE lossless failover extended interswitch link (XISL) 7800 switch configuring a GbE port configuring an IP route creating and FCIP circuit failover in TI zones FCIP configuring VEX_Ports DSCP Adaptive Rate Limiting (ARL) gathering additional information L2CoS persistently disabled ports QoS implementation testing a connection tracing a route...
  • Page 94 GbE port mode on the FX8-24 blade configuring priority percentages QoS SID/DID priorities QoS implementation in FCIP QoS priorities per FCIP circuit inband management configuring IP addresses and routes IP routing and subnets VLAN tagging support IPsec sharing GbE ports limitations for 7800 and FX8-24 NAT limitation for 7800 and FX8-24 tperf...

This manual is also suitable for:

DcxDcx 8510-8Dcx-4s7800Dcx 8510-4

Table of Contents