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-1001766-01...
What’s new in this document This manual applies to FCIP support in Fabric OS version 6.4.0 and later releases. New features include support for IPSec, support for VLAN and DSCP tagging, and support for VEX ports on the FX8-24 blade. Document conventions This section describes text formatting conventions and important notice formats used in this document.
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 <...
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. These trademarks are the properties of their respective companies and corporations. These references are made for informational purposes only.
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. General Information • Switch model • Switch operating system version •...
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.
Adaptive Rate Limiting Yes, but not on 10 GbE ports. 10GbE ports FC ports up to 8 Gbps Yes (1, 2, 4, 8 Yes (1, 2, 4, 8 No (1, 2, 4 Gbps) No (1, 2, 4 Gbps) Gbps)
FCIP concepts FCIP concepts Fibre Channel over IP (FCIP) enables you to use existing IP wide area network (WAN) infrastructure to connect Fibre Channel SANs. FCIP supports applications such as remote data replication (RDR), centralized SAN backup, and data migration over very long distances that are impractical or very costly using native Fibre Channel connections.
Page 18
IP WAN network considerations Fabric OS FCIP Administrator’s Guide 53-1001766-01...
FC ports and GbE ports on the 7800 switch. There are sixteen FC ports, numbered 0 through 15. The FC ports can operate at 1, 2, 4, or 8 Gbps. There are six GbE ports. Ports 0 and 1 are available as either RJ-45 ports or SFP ports. Only six total GbE ports may be used.
7800 switch license options VE_Ports and FCIP tunnels on the 7800 switch A 7800 switch can support eight VE_Ports. VE_Ports are numbered from 16 to 23. Each FCIP tunnel is identified with a VE_port number. Up to eight FCIP tunnels may be created. The 7800 switch supports VEX_ports to avoid the need to merge fabrics.
FC ports, GbE port, and 10GbE ports on the FX8-24 blade. There are twelve FC ports, numbered 0 through 11. The FC ports can operate at 1, 2, 4, or 8 Gbps. There are ten GbE ports, numbered 0 through 9. Ports XGE0 and XGE1 are 10GbE ports.
Page 23
FX8-24 blade hardware overview FIGURE 3 FX8-24 blade FC and GbE ports 10GbE ports. (labeled XGE0 and XGE1 on the sticker). GbE ports 0 through 3. GbE ports 4 through 9. FC ports 6 through 11. FC ports 0 through 5. Fabric OS FCIP Administrator’s Guide 53-1001766-01...
FX8-24 blade licensing options FX8-24 blade licensing options Some of the capabilities of the FX8-24 blade require slot-based feature licenses. These include the following: • 10GbE support. • Advanced FICON acceleration. • The IR license is required for FCR. The IR license is required to configure VEX_ports. •...
FCIP trunking 10.0.0.2 10.0.1.2 10.0.0.3 10.0.1.3 10.0.0.4 10.0.1.4 FCIP Tunnel 10.0.0.5 10.0.1.5 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 concept of a multiple circuit FCIP tunnel.
FCIP trunking • In a scenario where a FCIP tunnel has multiple circuits of different metrics, circuits with higher metrics are treated as standby circuits, and are not used until all lower metric circuits fail. Refer to “FCIP circuit failover capabilities” for a more detailed description.
FCIP trunking Figure 6, circuit 1 is assigned a metric of 0, and circuit 2 is assigned a metric of 1. Both circuits are in the same FCIP tunnel. In this case, circuit 2 is a standby that is not used unless there are no lowest metric circuits available.
Adaptive Rate Limiting Adaptive Rate Limiting Adaptive Rate Limiting (ARL) is performed on FCIP tunnel 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.
QoS SID/DID priorities over an FCIP trunk QoS SID/DID priorities over an FCIP trunk QoS SID/DID traffic prioritization is a capability of Brocade Fabric OS Adaptive Networking licensed feature. This feature allows you to prioritize FC traffic flows between initiators and targets. Each circuit has four internal TCP connections that manage QoS SID/DID priorities over an FCIP tunnel, as illustrated in Figure...
QOS, DSCP, and VLANs QOS, DSCP, and VLANs Quality of Service (QoS) refers to policies for handling differences in data traffic. These policies are based on data characteristics and delivery requirements. For example, ordinary data traffic is tolerant of delays and dropped packets, but voice and video data are not. QoS policies provide a framework for accommodating these differences in data as it passes through a network.
QOS, DSCP, and VLANs TABLE 2 Default Mapping of DSCP priorities to L2Cos Priorities (Continued) DSCP priority/bits L2CoS priority/bits Assigned to: 11 / 001011 3 / 011 Medium QoS 15 / 001111 3 / 011 Medium QoS 19 / 010011 3 / 011 Medium QoS 23 / 010111...
Page 32
0. Parameters are the same for both the create and modify options. switch:admin> portcfg fcipcircuit 16 modify 0 --dscp-f 32 --dscp-h 16 --dscp-m 8 --dscp-l 4 Operation Succeeded The following example shows the use of the portshow command to display the tunnel and circuit values.
Remote IP: 192.168.2.21 Local IP: 192.168.2.11 Metric: 0 Min Comm Rt: 100000 Max Comm Rt: 100000 SACK: On Min Retrans Time: 100 Max Retransmits: 8 Keepalive Timeout: 10000 Path MTU Disc: 0 VLAN ID: 200 L2CoS: F: 0 H: 0 M:...
This option supports up to 8 Gbps of FC traffic. The third option is software only compression option that provides a more aggressive algorithm. This option supports up to 2.5 Gbps of FC traffic.
IPSec implementation over FCIP tunnels • Jumbo frames are not supported for IPsec. • There is no RAS message support for IPsec. • IPsec can only be configured on IPv4 based tunnels. IPSec for the 7800 and FX8-24 blade AES-GCM-ESP is used as a single, pre-defined mode of operation for protecting all TCP traffic over an FCIP tunnel.
Figure 9. In both cases, there are no multiple equal-cost paths. In Figure 8, there is a single tunnel with Fastwrite and OSTP enabled. In Figure 9, there are multiple tunnels, but none of them create a multiple equal-cost path.
Support for IPv6 Addressing FIGURE 9 Multiple tunnels to multiple ports, Fastwrite and OSTP enabled on a per-tunnel/per-port basis In some cases, traffic isolation zoning TI or LS/LF configurations may be used to control the routing of SID/DID pairs to individual tunnels and provide deterministic flows between the switches, allowing the use of multiple equal cost tunnels.
Support for IPv6 Addressing • The IPv6 8-bit Traffic class field will be defined by the configured Differentiated Services field for IPv6 (RFC 2474). The configuration of this will be done on the FCIP circuit using the Differentiate Services Code Point (DSCP) parameters to fill the 6-bit DSCP field.
Configuration preparation Configuration preparation Before you begin to configure FCIP, do the following: • Determine the amount of bandwidth that will be required for the RDR, FICON or tape application to be deployed. • The WAN link has been provisioned and tested for integrity. •...
Configuration steps Setting VE_ports to persistently disabled state VE_Ports used on an FCIP tunnel must be persistently disabled before you can configure FCIP tunnels. You must change their state from persistently enabled to persistently disabled. Once the FCIP tunnels have been fully configured on both ends of the tunnel, you can persistently enable the ports.
Enables the GbE ports 0 through 9 and XGE0 (XGE1 is disabled). <slot_number> Specifies the slot number for the FX8-24 blade The following example enables GbE ports 0 through 9 on an FX8-24 blade in slot 8. Ports XGE0 and XGE1 are disabled. switch:admin> bladecfggemode --set 1g –slot 8 You can use the bladecfggemode --show command to display the GbE port mode for the FX8-24 blade in slot 8, as shown in the following example.
This is done using the portCfg ipif create command. The following examples create the addressing needed for the basic sample configuration in Figure The following command creates an IP interface for port ge0 on the FX8-24 blade in slot 8 of the Brocade DCX-4S. switch:admin> portcfg ipif 8/ge0 create 192.168.1.24 255.255.255.0 1500 The following command creates an IP interface for port ge0 on the Brocade 7800 switch.
The following command creates an IP route to destination network 192.168.11.0 for port ge0 on the FX8-24 blade in slot 8 of the Brocade DCX-4S. The route is through local gateway 192.168.1.1. switch:admin> portcfg iproute 8/ge0 create 192.168.11.0 255.255.255.0 192.168.1.1 The following command creates an IP route to destination network 192.168.1.0 for port ge0 on the...
FX8-24 source address. ARL minimum and maximum committed rates are specified for circuit 0. switch:admin> portcfg fciptunnel 8/12 create 192.168.11.78 192.168.1.24 -b 15500 -B 1000000 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.
Page 46
This option supports up to 8 Gbps of FC traffic. A value of 3 enables a software only compression option that provides a more aggressive algorithm. This option supports up to 2.5 Gbps of FC traffic.
Page 47
This option is used to toggle the option off and on. Keep alive timeout The keep-alive timeout in seconds. The range of valid values is 8 through 7,200 sec and the default is 10. Fabric OS FCIP Administrator’s Guide 53-1001766-01...
Page 48
Configuration steps TABLE 5 Circuit options Option Argument Disruptive Description Minimum retransmit The minimum retransmit time, in time milliseconds. The range of valid values is 20 through 5,000 ms and the default is 100 ms. failover/standby metric You can configure standby circuits by assigning a metric.
Figure 12). The following command creates circuit 1 on the FX8-24 end of the tunnel. switch:admin> portcfg fcipcircuit 8/12 create 1 192.168.11.79 192.168.1.25 -b 15500 -B 1000000 The following command creates circuit 1 on the 7800 end of the tunnel.
Configuration steps Enabling persistently disabled ports Ports must be disabled while they are being configured. Before an FCIP tunnel can be used, the associated ports must be persistently enabled. 1. Connect to the switch and log in using an account assigned to the admin role. 2.
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.
Deleting an IP route Deleting an IP route You can delete an IP route to a gateway destination IP address using the portcfg iproute with the delete option. The command syntax is as follows: portcfg iproute ge<n> delete dest_IPv4_addr netmask Deleting an FCIP tunnel When you delete an FCIP tunnel, you also delete all associated FCIP circuits.
The 7500 switch and FR4-18i blade The 7500 switch and FR4-18i blade Fabric OS supports SAN extension between Brocade 7500 switches, or between FR4-18i blades installed on Brocade 48000 directors or Brocade DCX Data Center Backbone directors. The Brocade 7500 and the FR4-18i blade both have 16 physical Fibre Channel ports and 2 physical GbE ports as illustrated in Figure 13 Figure...
GbE interface. Each GbE interface can support up to eight FCIP tunnels which are represented as eight virtual ports on ge0 and 8 virtual ports on ge1. The mapping of tunnels on ge0 and ge1 to virtual port numbers is represented in...
1 virtual port per GE interface. Each GbE interface can support up to 8 FCIP tunnels which are represented as 8 virtual ports on ge0 and 8 virtual ports on ge1. The mapping of tunnels on ge0 and ge1 to virtual port numbers is represented in...
FCIP Design Considerations for the 7500 switch and FR4-18i blade Fibre Fibre Channel Channel initiator initiator Office Data Center FC SAN FC SAN IP WAN VE_Port Network VE_Port Brocade Brocade 7500 7500 VE_Port VE_Port Brocade Brocade Office 48000 48000 FC SAN with FR4-18i with FR4-18i Office...
FCIP services license FCIP services license Most of the FCIP extension services described in this chapter require the Brocade High Performance . Use the licenseShow command to verify the license is present on Extension over FCIP/FC license the hardware used on both ends of the FCIP tunnel. QoS implementation over FCIP Quality of Service (QoS) refers to policies for handling differences in data traffic.
The following table shows the default mapping of DSCP priorities to L2Cos priorities per tunnel ID. This may be helpful when consulting with the network administrator. These values may be modified per FCIP tunnel. TABLE 8 Default Mapping of DSCP priorities to L2Cos Priorities Virtual CIrcuit (VC)
Page 60
IPSec implementation over FCIP IPsec uses some terms that you should be familiar with before beginning your configuration. These are standard terms, but are included here for your convenience. TABLE 9 IPsec terminology Term Definition Advanced Encryption Standard. FIPS 197 endorses the Rijndael encryption algorithm as the approved AES for use by US Government organizations and others to protect sensitive information.
IPSec implementation over FCIP • Secure Tunnels cannot be defined with VLAN Tagged connections. IPsec configuration IPsec requires predefined configurations for IKE and IPsec. You can enable IPsec only when these configurations are well-defined and properly created in advance. The following describes the sequence of events that invokes the IPsec protocol. 1.
IPSec implementation over FCIP IKE Policy 10 ----------------------------------------- Authentication Algorithm: MD5 Encryption: 3DES Perfect Forward Secrecy: on Diffie-Hellman Group: 1 SA Life (seconds): 28800 Operation Succeeded Displaying IKE and IPsec policy settings 1. Connect to the switch and log in using an account assigned to the admin role. 2.
1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the portShow fcipTunnel command. The following example shows the portShow fcipTunnel command used to display IPsec information for tunnel 3: switch:admin> portshow fciptunnel 8/ge0 3 -ipsec Port: ge0 ------------------------------------------- Tunnel ID 3 Remote IP Addr 192.175.5.200...
Virtual Fabrics and FCIP Virtual Fabrics and FCIP Any GigE_Port and all of its associated FCIP tunnels on a chassis can be assigned to any Logical Switch. As with the current Fabric OS, the port types supported by FCIP are either VE_ or VEX_Port. When a GigE port is moved to a logical switch, all eight VE_ and VEX_Ports are automatically moved.
Options for enhancing tape I/O performance Options for enhancing tape I/O performance There are two options available for enhancing open systems SCSI tape write I/O performance: • FCIP Fastwrite and Open Systems Tape Pipelining (OSTP) • FC Fastwrite FCIP Fastwrite and OSTP are implemented together. FC Fastwrite is an FC-FC routing alternative that disables the local Ethernet ports (ge0 and ge1), making it impossible to configure FCIP Fastwrite and OSTP and FC Fastwrite on the same 7500 or FC4-18i blade.
Options for enhancing tape I/O performance TABLE 12 Using FCIP Fastwrite and OSTP (Continued) FCIP Fastwrite OSTP Class 3 traffic is accelerated with Fastwrite. Class 3 traffic is accelerated between host and sequential device. With sequential devices (tape drives), there are 1024 initiator-tape (IT) pairs per GbE port, but 2048 initiator-tape-LUN (ITL) pairs per GbE port.
Options for enhancing tape I/O performance FIGURE 17 Multiple tunnels to multiple ports, Fastwrite and OSTP enabled on a per-tunnel/per-port basis Unsupported configurations for Fastwrite and OSTP The following configurations are not supported with Fastwrite and OSTP. These configurations use multiple equal-cost paths.
Page 69
Options for enhancing tape I/O performance VE-VE or VEX-VEX FIGURE 18 Unsupported configurations with Fastwrite and OSTP Fabric OS FCIP Administrator’s Guide 53-1001766-01...
If you are implementing VLAN tagging, create a static ARP entry for the IP interface using the portCfg arp command. Refer to “Creating IP interfaces and routes” for specific instructions. 8. Test the IP connection using the portCmd ping command. Refer to “Creating IP interfaces and routes”...
Specify 1 to enable or 2 to disable negotiate fabric parameters. The following example configures a port as a VEX_Port for slot number 8 in port number 18, enables admin, and specifies fabric ID 2 and preferred domain ID 220: switch:admin>...
Creating IP interfaces and routes Creating IP interfaces and routes The IP network connection between two Brocade 7500 Extension switches or two FC4-18i blades or one Brocade 7500 Extension switch and one FC4-18i blade is configured by defining IP interfaces for origin and destination virtual ports, and then defining one or more IP routes to connect them.
Page 73
Creating IP interfaces and routes The destination IPv6 address of the virtual port, if IPv6 is used. The address must be an IPv6 global, unicast address. Optionally specify the prefix length. This is used for IPv6 addresses instead of a netmask. If prefix_len is not specified, the prefix length learned from the Neighbor Discovery protocol will be used.
Page 74
Creating IP interfaces and routes The following example shows two routes being added to an interface: switch:admin06> portcfg iproute 8/ge0 create 192.168.11.0 255.255.255.0 192.168.100.1 1 switch:admin06> portcfg iproute 8/ge0 create 192.168.12.0 255.255.255.0 192.168.100.1 1 The following example verifies that the two routes have been successfully created: switch:admin06>...
Creating an FCIP tunnel -q type-of-service The DiffServ QoS. The default is 0 (zero). The value must be an integer in the range from 0 through 255. -t ttl The time to live. The default value is 100. -v vlan tag The vlan tag for a VLAN tagged IP connection.
Page 76
-n remote_wwn The remote-side FC entity WWN. -k timeout The keep-alive timeout in seconds. The range of valid values is 8 through 7,200 sec and the default is 10. If OSTP is enabled both the default and minimum values are 80 sec.
2 class of service of 3 for control traffic, and a layer 2 class of service of 7 for data traffic. portcfg fciptunnel 8/ge0 create 2 192.168.10.1 192.168.20.1 0 -v 100 -p 3 -P 7 Example of creating an FCIP tunnel with FastWrite and OSTP enabled switch:admin>...
Page 78
Tape Pipelining on Committed Rate 200000 Kbps (0.200000 Gbps) SACK on Min Retransmit Time 100 Keepalive Timeout 10 Max Retransmissions 8 VC QoS Mapping off DSCP Marking (Control): 0, DSCP Marking (Data): 0 VLAN Tagging Not Configured TCP Byte Streaming off...
FCIP tunnels now appear in the fabric as VE_Ports. 3. Verify that the VE_Port or VEX_Port is online, use the switchShow command to view and verify that the FCIP tunnel is online. switch:admin06> portenable 8/18 switch:admin06> portenable 8/19 switch:admin06> switchshow switchName:switch switchType:42.2...
Page 80
4. Enter the portCfgShow command to verify the port is persistently enabled as shown below: switch:admin06> portcfgpersistentenable 8/16 switch:admin06> portcfgpersistentenable 8/17 switch:admin06> portcfgpersistentenable 8/18 switch:admin06> portcfgpersistentenable 8/19 switch:admin06> portcfgshow Ports of Slot 8 9 10 11 12 13 14 15 -----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-- Speed AN AN AN AN...
Fastwrite. -k timeout The keep-alive timeout on the existing FCIP tunnel. The range of valid values is 8 through 7200 seconds. If OSTP is enabled, the default and minimum value is 80 seconds. -m time The minimum retransmit time for the existing FCIP tunnel. The range of valid values is 20 through 5000 milliseconds.
Range is 0-7. Default is 0. -bstr 0|1 Enables (1)/Disables (0) TCP Byte Streaming. The following example shows two FCIP tunnels created on slot 8, port ge0; the first with an uncommitted bandwidth (0), and the second with a committed bandwidth of 10000 bps: switch:admin>...
2. Enter the portCfg fciptunnel command to delete FCIP tunnels. The command syntax is as follows. portcfg fciptunnel [slot/]ge0|ge1 delete tunnel_id The following example shows two tunnels deleted on slot 8, port ge0: switch:admin> portcfg fciptunnel 8/ge0 delete 6 switch:admin> portcfg fciptunnel 8/ge0 delete 7 Deleting an IProute The following command deletes an IP route for a specified IPv4 address.
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 L2 CoS value of 3. switch:admin> portcfg vlantag 8/ge0 add 192.168.10.1 100 3 7 192.168.20.1 Fabric OS FCIP Administrator’s Guide...
Chapter FCIP Management and Troubleshooting In this chapter • WAN performance analysis tools ........71 •...
Page 86
WAN performance analysis tools Tperf will test single and multiple circuit tunnels. Tperf also tests the different priority connections that are provided by an FCIP Tunnel. When a Tperf--enabled tunnel is operative, it is not an active VE port. Fabrics will not merge over an operative FCIP Tperf tunnel. To determine if the Tperf tunnel is up, issue the following command: switch:admin>...
Page 87
WAN performance analysis tools -time Specifies the duration of the Tperf traffic flow in seconds. If a duration is not specified, the process continues to run until it is terminated with Ctrl + C. -unidirectional Generates traffic in one direction only. The default is round-trip. -random Specifies a random protocol data unit (PDU) size between 1 and the size of the send request, as set by -size.
Page 88
WAN performance analysis tools ********************************************************************** ********************************************************************** Tunnel ID: 16 High Priority Medium Priority Low Priority bytes tx 4288640 3669640 2828040 bytes rx 1088456832 931354632 717756552 PDUs tx 107216 91741 70701 PDUs rx 107216 91741 70701 bad CRC headers rx bad CRC payloads rx out of seq PDUs rx flow control count packet loss (%)
WAN performance analysis tools The ipperf option NOTE The ipperf option is for 7500 switches and FR4-18i blades. It does not work with 7800 switches and FX8-24 blades. The ipperf option allows you to specify the slot and port information for displaying performance statistics for a pair of ports.
1. Configure the receiver test endpoint using the CP CLI. The syntax for invoking the receiver test endpoint using ipperf for slot8, port ge0 on an FR4-18i is as follows: portcmd --ipperf 8/ge0 -s 192.168.255.10 -d 192.168.255.100 -R Fabric OS FCIP Administrator’s Guide 53-1001766-01...
Page 91
FR4-18i is as follows: portcmd --ipperf 8/ge0 -s 192.168.255.100 -d 192.168.255.10 –S The following example shows the results of the performance analysis for slot 8, port ge0: ipperf to 192.41.70.43 from IP interface 192.41.70.42 on 0/1:3227 Sampling frequency(30s) Total time(30s) BW:112.73MBps WBW:55.57MBps Loss(%):0.00 Delay(ms):23 PMTU:1500 Sampling frequency(30s) Total time(60s) BW:112.77MBps WBW:83.61MBps Loss(%):0.00...
The following example tests the connection between IP addresses 192.168.10.1 and 192.168.20.1 over VLAN 10 with an layer 2 class of service of 3. portcmd --ping 8/ge0 -s 192.168.10.1 -d 192.168.20.1 -v 10 -c 3 Fabric OS FCIP Administrator’s Guide...
0 and 7. The default is 0. This operand is optional with the -v option (7500 switch and FR4-18i blade only). The following example traces the route between IP addresses 192.168.10.1 and 192.168.20.1 over VLAN 10. portcmd --traceroute 8/ge0 -s 192.168.10.1 -d 192.168.20.1 -v 10 Fabric OS FCIP Administrator’s Guide 53-1001766-01...
Portshow command usage Portshow command usage The portshow command can be used to display operational information for 7800 switches, FX8-24 blades, 7500 switches, and FR4-18i blades. The Fabric OS Command Reference Manual and the man pages provide 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 96
Portshow command usage 0 ge0 Disable ----s 0.00 0.00 200/1000 1 ge1 Disable ----s 0.00 0.00 200/1000 2 ge5 Disable ----s 0.00 0.00 200/1000 3 ge4 Disable ----s 0.00 0.00 200/1000 ------------------------------------------------------------------------------- Flags: tunnel: c=compression f=fastwrite t=Tapepipelining F=FICON T=TPerf circuit: s=sack Displaying FCIP tunnel information (7800 switch and FX8-24 blade) The following example shows general tunnel information for a 7800 switch.
Page 97
Metric: 0 Min Comm Rt: 150000 Max Comm Rt: 150000 SACK: On Min Retrans Time: 100 Max Retransmits: 8 Keepalive Timeout: 5000 Path MTU Disc: 0 VLAN ID: 0 L2CoS: F: 0 H: 0 M: 0 L: 0 DSCP: F: 0 H: 0 M: 0 L: 0...
Page 98
Metric: 0 Min Comm Rt: 150000 Max Comm Rt: 150000 SACK: On Min Retrans Time: 100 Max Retransmits: 8 Keepalive Timeout: 5000 Path MTU Disc: 0 VLAN ID: 0 L2CoS: F: 0 H: 0 M: 0 L: 0 DSCP: F: 0 H: 0 M: 0 L: 0...
Page 99
Metric: 0 Min Comm Rt: 150000 Max Comm Rt: 150000 SACK: On Min Retrans Time: 100 Max Retransmits: 8 Keepalive Timeout: 5000 Path MTU Disc: 0 VLAN ID: 0 L2CoS: F: 0 H: 0 M: 0 L: 0 DSCP: F: 0 H: 0 M: 0 L: 0...
Metric: 0 Min Comm Rt: 150000 Max Comm Rt: 150000 SACK: On Min Retrans Time: 100 Max Retransmits: 8 Keepalive Timeout: 5000 Path MTU Disc: 0 VLAN ID: 0 L2CoS: F: 0 H: 0 M: 0 L: 0 DSCP: F: 0 H: 0 M: 0 L: 0...
Page 103
-perf or -params options. The command syntax is as follows. portShow fciptunnel [Slot]/ge0|ge1 all|tunnel ID -perf -params The following example shows the portCmd fcipTunnel with the -perf option to display performance characteristics of tunnel 0. switch:admin06> portshow fciptunnel 8/ge0 all —perf Slot: 8 Port: ge0 ------------------------------------------- Tunnel ID 0 Remote IP Addr 192.175.4.200...
Page 104
556200 Bps 30s avg, 491394 Bps lifetime avg The following example shows the portCmd fcipTunnel with the parameters options to display the parameters of tunnel 0: switch:admin06> portshow fciptunnel 8/ge0 0 —params Slot: 8 Port: ge0 ------------------------------------------- Tunnel ID 0 Remote IP Addr 192.175.4.200...
Page 105
Portshow command usage timeout 10 s Data transfer TCP connection: Local 192.175.4.100:4140, Remote 192.175.4.200:3226 Performance stats: 12899612 output packets 34508 pkt/s 30s avg, 30495 pkt/s lifetime avg 14499127648 output Bytes 38787792 Bps 30s avg, 34276897 Bps lifetime avg 0 packets lost (retransmits) 0.00% loss rate 30s avg 6495624 input packets 17381 pkt/s 30s avg, 15356 pkt/s lifetime avg...
FCIP tunnel issues FCIP tunnel issues The following are common FCIP tunnel issues and recommended actions for you to follow to fix the issue. NOTE The portshow -perf and - params options can be applied only to the 7500 switch and FR4-18i blade. Symptom FCIP tunnel does not come Online.
Page 107
Tape Pipelining off Committed Rate 1000000 Kbps (1.000000 Gbps) SACK on Min Retransmit Time 100 Keepalive Timeout 10 Max Retransmissions 8 VC QoS Mapping off DSCP Marking (Control): 0, DSCP Marking (Data): 0 VLAN Tagging Not Configured TCP Byte Streaming off...
Gather this information for both data and management TCP connections. 8. Run tperf for 7800 switches and FX8-24 blades, or ipperf for 7500 switches and FR4-18i blades to gather WAN performance data.
FCIP links Gathering additional information The following commands should be executed and their data collected before a supportsave is run. A supportsave can take 10 minutes or more to run, and some of the information is time critical. NOTE The portshow -perf and - params options can be applied only to the 7500 switch and FR4-18i blade. •...
The tunnel number (0 - 7). Creates an FTRACE configuration. -a 1|0 Enables or disables auto check out. -b value Number of buffers (range 0 to 8). -e 1|0 Enable or disable FTRACE. -i value Display mask value (range 0 to FFFFFFFF).
*-Bit 10 [0x00000400]: CpRX - Frame Received From CP *-Bit 9 [0x00000200]: CpSX - Frame Sent To CP -Bit 8 [0x00000100]: ToP - Sent To Peer *-Bit 7 [0x00000080]: Tfx - Emulation FC Frame From Peer *-Bit 6 [0x00000040]: Rfx - Emulation FC Received Frame...
FTRACE concepts Example of capturing an FTRACE on a tunnel This process defines how to capture an FTRACE buffer for a 7800 switch or FR4-18i blade, save it, and then enter the supportSave command that includes that data. NOTE For the 7800 and FX8-24, any triggered or checked out and current non-empty trace buffers are captured in a supportSave automatically.
Page 114
FTRACE concepts Write Progress: 5964096 of 16000320 bytes sent Write Progress: 6799680 of 16000320 bytes sent Write Progress: 7078208 of 16000320 bytes sent Write Progress: 7700800 of 16000320 bytes sent Write Progress: 8520000 of 16000320 bytes sent Write Progress: 9355584 of 16000320 bytes sent Write Progress: 10174784 of 16000320 bytes sent Write Progress: 10338624 of 16000320 bytes sent Write Progress: 10846528 of 16000320 bytes sent...
Page 115
Index Numerics FCIP configuration guidelines configuring VEX_Ports 7500 switch and FR4-18i blade creating a tunnel 7800 switch creating interfaces configuring a GbE port creating routes configuring an IP route DSCP creating an FCIP tunnel Fastwrite creating and FCIP circuit gathering additional information IP compression IPsec changeable parameters IPsec configuration...
Page 116
tape read and write acceleration tperf tunnel goes on- and offline gathering FCIP information GbE port mode on the FX8-24 blade VE_Ports VEX_Port Virtual Fabrics ipperf FCIP IPsec FCIP FCIP changeable parameters FCIP configuration FCIP fixed parameters WAN analysis tools License requirements 7800 switch FX8-24 blade...