Brocade FCIP/FCR Implementation - switchsanguru.comswitchsanguru.com/images/Telcom_Kickoff_Presentation_Compatibility... · Brocade FCIP/FCR Implementation MAJOR TELCOM COMPANY

Brocade FCIP/FCR

ImplementationImplementationMAJOR TELCOM COMPANYJoe Holbrook

BCFP, BCSD, BCSM

September 04, 2007

Legal Disclaimer

All or some of the products detailed in this presentation may still be under development and

certain specifications, including but not limited to, release dates, prices, and product features,

may change. The products may not function as intended and a production version of the

products may never be released. Even if a production version is released, it may be materially

different from the pre-release version discussed in this presentation.

NOTHING IN THIS PRESENTATION SHALL BE DEEMED TO CREATE A WARRANTY OF

ANY KIND, EITHER EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING

BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR

® 2007 Brocade Communications Systems, Inc.

All rights reserved.2

BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR

A PARTICULAR PURPOSE, OR NONINFRINGEMENT OF THIRD PARTY RIGHTS WITH

RESPECT TO ANY PRODUCTS AND SERVICES REFERENCED HEREIN.

Brocade, the Brocade B-weave logo, McDATA, Fabric OS, File Lifecycle Manager, MyView,

Secure Fabric OS, SilkWorm, and StorageX are registered trademarks and the Brocade B-wing

symbol and Tapestry are trademarks of Brocade Communications Systems, Inc. or its

subsidiaries, in the United States and/or in other countries. FICON is a registered trademark of

IBM Corporation in the U.S. and other countries. All other brands, products, or service names

are or may be trademarks or service marks of, and are used to identify, products or services of

their respective owners.

7500 NOTES

7500 Overview



7500 Front



7500 Back



FCIP/FCR NOTES

Example Configuration Overview



FCIP/FCR

Once the switch (SW7500) is configured, the switchShow command displays 32 Fibre Channel ports (port numbers 0 through 31) and 2 GbE ports.

The first 16 Fibre Channel ports are physical ports on the SilkWorm 7500, Ports 16-23 are virtual ports associated with the GE0



7500, Ports 16-23 are virtual ports associated with the GE0 physical GbE link and ports 24-31 are virtual ports associated with GE1 physical GbE link. The GbE ports are displayed as ge0 and ge1 and are not assigned port numbers or area numbers.

FCIP/FCR

NOTE: Fabrics connected through FCIP merge if the ports are configured as VE_Ports, and do not merge if they are configured as VEX_Ports.

If VE_Ports are used in a Fibre Channel Routing Services backbone fabric configuration, then the backbone fabric merges but the EX_Port attached to edge fabrics do not merge.



the EX_Port attached to edge fabrics do not merge.

FCIP/FCR

NOTE: The port types for FCIP tunneling are either VE_Port or VEX_Port. An FCIP tunnel using VE_Ports will merge the two fabrics.

An FCIP tunnel using a VEX_Port will not merge the fabrics.

A VEX_Port can connect only to a VE_Port.

The IP encapsulation of the Fibre Channel frame on one port and



The IP encapsulation of the Fibre Channel frame on one port and the reconstruction of Fibre Channel frames on the other port is transparent to the initiator and target.

FCIP/FCR

NOTE: If using FCIP in your FC-FC Routing configuration, you must first configure FCIP tunnels.

Once a tunnel is created, it defaults to a disabled state. Then configure the VE_Port or VEX_Port. After the appropriate ports are configured, enable the tunnel.



BROCADE FCR/FCIP

Secure Fabric OS, Management Server Platform services, and interopmode are not supported in the backbone fabric.

FOS 5.2 and above support FC-FC connections to McDATA Fabrics. Fabric OS v5.2.0 furnishes the FC router with the ability to connect to McDATA fabrics in both McDATA Open or McDATA Fabric mode.



BROCADE FCR/FCIP

Ensure fabric OS is at v5.1 or later.

Fabric OS 5.2 or later is required if connecting to McDATA Fabrics



Information Needed

Customer SuppliedCustomer Supplied

Pre Implementation Information Gathering

Lets Document the following

Switchname

IP Addresses

Subnet



Subnet

Netmask

MTU size (Jumbo Packets?)

FCR LSAN Zoning

Configure Switch

Configure Term

Configure the Port Settings parameters as follows:

—Bits per second – 9600

—Data bits - 8

—Parity - None



—Parity - None

—Stop bits - 1

—Flow control – None

Configure Management LAN

a. View Current Management Interface Settings

i. ipaddrshow to view current configuration

1. Ethernet IP Address:

2. Ethernet Subnetmask:

3. Fibre Channel IP Address:

4. Fibre Channel Subnetmask:

5. Gateway Address:

b. Set IP for Management Interface



i. ipaddrset and follow prompts

1. IP Address

2. Subnetmask

3. Fibre Channel IP Address

4. Fibre Channel Subnetmask

5. Gateway IP Address

c. Reboot Switch

Set Switchname

When naming your routers it is important to name them in a consistent and easy to replicate manner.

switchname “name”



Verify Firmware

Firmware needs to be v5.1 and above

a. version to display current firmware version running on switch

b. firmwareshow – Display firmware in both memory partitions



c. check OEM recommended level & TSB’s to determine if upgrade is necessary

Configure Domain ID and Fabric Params

a. switchdisable to disable switch in order to make fabric parameter changes

b. configure

i Note: Ctrl-D at any time to accept remaining settings without completing all prompts.

c. Yes or Y to configure fabric parameters

d. Domain ID



e. WAN_TOV

ii. Accept Default of 1000ms

iii. If timeouts/errors occur on tunnel this can be modified/updated

f. Insistent Domain ID (OPTIONAL)

g. switchenable

Optional Settings

Time Server

a. tsclockserver xxx.xxx.xxx.xxx

b. verify settings using tsclockserver

Time Zone

a. tsTimeZone [houroffset [, minuteoffset]]



a. tsTimeZone [houroffset [, minuteoffset]]

i. For Pacific Standard Time, enter tsTimeZone -8,0

ii. For Mountain Standard Time, enter tsTimeZone -7,0

iii. For Central Standard Time, enter tsTimeZone -6,0

iv. For Mountain Standard Time, enter tsTimeZone -5,0

Optional Settings

Syslog Server

a. syslogdipadd xxx.xxx.xxx.xxx to add a new syslog server

b. syslogdipshow to view configured syslog servers



Optional Settings

Syslog Server

a. syslogdipadd xxx.xxx.xxx.xxx to add a new syslog server

b. syslogdipshow to view configured syslog servers



Install FCIP License

a. licenseshow (record info)

b. validate licenses active with packet of licenses purchased

i. If licenses are missing we need

1. transaction key (from paper packet)



1. transaction key (from paper packet)

2. WWN (from switchshow)

ii. If we have a license key proceed to activate license

c. licenseadd “key”

d. licenseremove “key”

Configupload

a. configupload (Follow Prompts for the following information)

i. Protocol (ftp or scp)

ii. Server Name or IP Address

iii. User Name



iv. File Name

v. Password

b. Verify File was uploaded to FTP server

Verify Switch Status

a. switchStatusShow

i. Verifies overall switch status

b. portShow “port number”

i. Verifies port status on per port basis

c. fanShow



i. Verifies overall Fan status

d. psShow

i. Verifies overall Power Supply Status

e. tempShow

i. Verifies Temperature Sensor Status

Configure FCIP Ports


VERIFY SETTINGS

SW7500:admin> portcfg ge0 or portcfg ge1

Usage: portCfg <action> [Slot/]Port[-Range] <Args>

Range: Specify a range of port in the same slot to apply

Action:



rscnsupr -- RSCN suppression

ipif -- IP Interface

iproute -- IP Routes

fciptunnel -- FCIP Tunnel

arp -- ARP Entry

Args: Action specific arguments


a. Portcfgshow ge0 (To view current configuration of GbE 0)

b. Portcfgshow ge1 (To view current configuration of GbE 1)




Licenseshow

Verify Persistently disabled

a. Switchshow to validate that ports 16 – 31 are disabled (These are FCIP Tunnel Virtual Ports)

b. Verify ge0 & ge1 are Disabled



b. Verify ge0 & ge1 are Disabled

Configure FCIP Portsc. The Tunnel Ports associated to each GbE interface are shown below

Port GbE Interface Tunnel Number

==============================

16 GbE 0 TUNNEL 0

17 GbE 0 TUNNEL 1

18 GbE 0 TUNNEL 2

19 GbE 0 TUNNEL 3

20 GbE 0 TUNNEL 4

21 GbE 0 TUNNEL 5

22 GbE 0 TUNNEL 6

23 GbE 0 TUNNEL 7



24 GbE 1 TUNNEL 0

25 GbE 1 TUNNEL 1

26 GbE 1 TUNNEL 2

27 GbE 1 TUNNEL 3

28 GbE 1 TUNNEL 4

29 GbE 1 TUNNEL 5

30 GbE 1 TUNNEL 6

31 GbE 1 TUNNEL 7

ge0 id 1G No_Sync Disabled

ge1 id 1G No_Sync Disabled


Define Switch_A

a. Portshow ipif ge0 / ge1 To View Current IP, Netmask & MTU settings

b. To Add IP Tunnels to ge0

i. portcfg ipif ge0 create 192.168.101.10 255.255.255.0 1500 (UP TO 8 PER EACH GE

PORT CAN BE CREATED)

1. IP = 192.168.101.10



2. NetMask = 255.255.255.0

3. MTU = 1500

ii. portcfg ipif ge0 create 192.168.101.11 255.255.255.0 1500

1. IP = 192.168.101.11

2. NetMask = 255.255.255.0

3. MTU = 1500


c. To Add IP Tunnels to ge1

i. portcfg ipif ge1 create 192.168.101.20 255.255.255.0 1500 (UP TO 8 PER EACH GE

PORT CAN BE CREATED)

1. IP = 192.168.101.20

2. NetMask = 255.255.255.0



3. MTU = 1500


1. IP = 192.168.101.21

2. NetMask = 255.255.255.0

3. MTU = 1500


d. portshow ipif ge0 / ge1 to view / ensure settings are correct

Port: ge0

Interface IP Address NetMask MTU

----------------------------------------------------------

0 192.168.101.10 255.255.255.0 1500

1 192.168.101.11 255.255.255.0 1500

Port: ge1




----------------------------------------------------------

0 192.168.101.20 255.255.255.0 1500

1 192.168.101.21 255.255.255.0 1500

e. To Delete a defined IP

i. portcfg ipif ge0 / ge1 delete xxx.xxx.xxx.xxx where x’s = IP address


Configure Remote Switch_B

a. portshow ipif ge0 / ge1 To View Current IP, Netmask & MTU settings

b. To Define IP Tunnel Configuration to ge0

i. portcfg ipif ge0 create 192.168.101.200 255.255.255.0 1500 (UP TO 8 PER EACH



GE PORT CAN BE CONFIGURED)

1. IP = 192.168.101.200

2. NetMask = 255.255.255.0

3. MTU = 1500



1. IP = 192.168.101.201

2. NetMask = 255.255.255.0

3. MTU = 1500




c. To Define IP Tunnel Configuration to ge1

i. portcfg ipif ge1 create 192.168.101.210 255.255.255.0 1500 (UP TO 8 PER EACH GE PORT CAN BE CONFIGURED)

1. IP = 192.168.101.210

2. NetMask = 255.255.255.0

3. MTU = 1500



3. MTU = 1500


1. IP = 192.168.101.211

2. NetMask = 255.255.255.0

3. MTU = 1500


d. portshow ipif ge0 / ge1 to view / ensure settings are correct

Port: ge0


----------------------------------------------------------

0 192.168.101.200 255.255.255.0 1500

1 192.168.101.201 255.255.255.0 1500



Port: ge1


----------------------------------------------------------

0 192.168.101.210 255.255.255.0 1500

1 192.168.101.211 255.255.255.0 1500

ENABLE FCIP Ports

Add Routes (optional)

Enable GE Ports!!

a. Switchshow to view all ports



b. portenable ge0 on both local & remote routers

c. portenable ge1 on both local & remote routers

d. switchshow to verity ports are enabled

Verify FCIP Ports

Verify Connectivity (We will need to this both ways) This verification is used to ping the destination IP address from one of the source IP interfaces on the GbE ports to ensure Ethernet IP-IP connectivity. This verification also ensures that data packets can be sent to the remote interfaces

a. portcmd ping ge0 –s 192.168.101.10 –d 192.168.101.200



-s Source

-d Destination

Verify FCIP Ports

COMMAND EXAMPLE OUTPUT

SW7500_D11:admin> portcmd ping ge0 -s 192.168.101.10 -d 192.168.101.200

Pinging 192.168.101.200 from ip interface 192.168.101.10 on 0/0 with 40 bytes of data

Reply from 192.168.101.200: bytes=40 rtt=0ms






Ping Statistics for 192.168.101.200:

Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss)

Min RTT = 0ms, Max RTT = 0ms Average = 0ms

Configure FCIP Tunnels

After you have verified licensing and connectivity between your source and destination IP interfaces, you can configure FCIP tunnels. As you your tunnel configurations, be aware that uncommitted rate tunnels use a minimum of 1000 Kbps, up to a maximum of available uncommitted bandwidth on the GbE port.

The total bandwidth available on a GbE port is 1 Gbps. You can configure tunnels as bidirectional entities with different commit rates in



configure tunnels as bidirectional entities with different commit rates in both directions.


a. portcfg fciptunnel ge0 create 1 192.168.101.200 192.168.101.10 500000

i. if only half of the tunnel is ours or we need to throttle the tunnel we can modify the settings here using a different value than 500000

ii. NOTE This example (We are using ½ of the full 1G tunnel for this tunnel and the other ½ for the 2nd one being created in b below)

b. portcfg fciptunnel ge0 create 2 192.168.101.201 192.168.101.11 500000




i. if only half of the tunnel is ours or we need to throttle the tunnel we can modify thesettings here using a different value than 500000

ii. NOTE (We are using ½ of the full 1G tunnel for this tunnel and the other ½ for the2nd one being created in b below)


c. portshow fciptunnel ge0 all (To View Created Tunnels, Output Below)

i. Notice that the tunnel is Inactive until the Remote side is configured.

SW7500_D11:admin> portshow fciptunnel ge0 all

Port: ge0

-------------------------------------------

Tunnel ID 1

Remote IP Addr 192.168.101.200

Local IP Addr 192.168.101.10



Remote WWN Not Configured

Local WWN 10:00:00:05:1e:37:8c:35

Compression off

Committed Rate 500000 Kbps (0.50000 Gbps)

SACK on

Min Retransmit Time 100

Keepalive Timeout 10

Command Truncated!!!


CONFIGURE LOCAL FCIP TUNNELS (GE1 Optional)






i. Notice that the tunnel is Inactive.


Port: ge1


Configure Remote FCIP Tunnel GE0






i. Notice that the tunnel is Inactive


Configure Remote FCIP Tunnel GE1 (optional)






ii. Notice that the tunnel is Inactive.


NOTE:

Create as many tunnel ID’s as necessary. Maximum of 8 Tunnels per GbE port. You cannot use more than the avail max of 1G per physical link.



Verify FCIP Tunnels

a. Portshow fciptunnel ge0 all

i. Notice that the tunnel is now Active


Port: ge0

-------------------------------------------

Tunnel ID 1

Remote IP Addr 192.168.101.200

Local IP Addr 192.168.101.10



Remote WWN Not Configured

Local WWN 10:00:00:05:1e:37:8c:35

Compression off

Committed Rate 100000 Kbps (0.100000 Gbps)

SACK on

Min Retransmit Time 100

Keepalive Timeout 10

Max Retransmissions 8

Status : Inactive

Persistentenable FCIP Tunnels

Persistentenable

portCfgPersistentEnable {port}



Verify Ports

switchshow to verify VE port(s) are online

16 16 -- -- Offline Disabled (Persistent)

17 17 -- -- Online VE-Port 10:00:00:05:1e:37:8d:c1 "SW7500_D12" (downstream)

18 18 -- -- Online VE-Port 10:00:00:05:1e:37:8d:c1 "SW7500_D12"









25 25 -- -- Online VE-Port 10:00:00:05:1e:37:8d:c1 "SW7500_D12"

26 26 -- -- Online VE-Port 10:00:00:05:1e:37:8d:c1 "SW7500_D12“

Configuration Overview



Configure LSANS AND ZONING

s




Create a zone with the same members (e.g., HBA in fabric A, storage port in fabric B) coded with the PWWN of the device.

The zone must use the naming convention “LSAN_ZONENAME” or “lsan_zonename” Note that the name of the zone to the right of the underscore character can be anything you want, as long as the above convention is used.



It is administratively easier if the zone name is the same in each edge fabric, though this is not required as long as the members of the zone are identical.


An LSAN consists of zones in two or more edge or backbone fabrics that contain the same device(s).

LSANs essentially provide selective device connectivity between fabrics without forcing you to merge those fabrics. The SilkWorm 7500, 48000 with a FR4-18i blade, and AP7420 Multiprotocol Router provide

multiple mechanisms for you to manage interfabric device connectivity



multiple mechanisms for you to manage interfabric device connectivity through extensions to existing switch management interfaces. You can define and manage LSANs using Brocade Advanced Zoning or Brocade Fabric Manager.

Zones are locally defined. Names and memberships, with the exception of hosts and targets exported from one fabric to another, do not need to be coordinated with other fabrics.


Zones that contain hosts and targets that are shared between the two fabrics need to be explicitly coordinated. Although an LSAN is managed using the same tools as any other zone on the edge fabric, two behaviors distinguish an LSAN from a conventional zone:

• A required naming convention. The name of an LSAN begins with the prefix “LSAN_”. The LSAN name is letter case insensitive; for example, lsan_ is equivalent to LSAN_, Lsan_, and so on.



lsan_ is equivalent to LSAN_, Lsan_, and so on.

• Members must be identified by their port WWN because PIDs are not necessarily unique across fabrics. The names of the zones need not be explicitly the same, and membership lists of the zones need not be in the same order.


NOTE:

If you are managing other switches in a fabric, it is recommended that you run the defZone –show command on your Fabric OS v5.1.0 switches as a precaution. Default zoning behavior in Fabric OS v5.1.0

operates differently compared to other Fabric OS versions (for example, versions 2.x, 3.x 4.x and 5.0.1). For example, if you issue the defZone --



versions 2.x, 3.x 4.x and 5.0.1). For example, if you issue the defZone --noaccess command on a Fabric OS v5.1.0 switch, then default zoning configurations will be created on each switch in the fabric (v2.x, v3.x, v4.x or v5.0.1 switches). Fabric OS v5.1.0 switches do not indicate that a default configuration is enabled when you use the cfgShow or cfgActvShow commands.


a. nsshow to list the WWN of the host. The port WWN must be used for LSANs

i. Record Host port WWN

b. Create The LSAN Zone

i. zoneCreate “lsan_ZoneName”, “WWN”

ii. Creates LSAN_Zone & adds Host



c. Add Target member(s) to the LSAN Zone

i. zoneAdd “lsan_ZoneName”, “WWN”

ii. Adds Target to Zone


d. Create the LSAN Zone Configuration

i. cfgCreate “Zone_Cfg”, “lsan_Zone Name”

e. Verify that the Created LSAN Zones are correct

i. cfgShow

f. Enable the LSAN Zone Configuration



f. Enable the LSAN Zone Configuration

i. cfgenable “zone_cfg”


g. Complete Steps A – F on the 2nd Fabric

Configuration Second Fabric as previous




b. lsanZoneShow –s

i. Displays the LSAN

c. fcrPhyDevShow

i. Displays the physical devices in the LSAN



i. Displays the physical devices in the LSAN

d. fcrProxyDevShow

i. Displays the Proxy Devices in the LSAN

Verify LSANS AND ZONING

Run the command lsanzoneshow –s on each router. The PWWN for the zoned device physically present in the edge fabric will show up in the output with the comment “Exist”, while the PWWN for the device presented to the edge fabric through the router will show up with the comment “Imported”.

Note that the Exist/Imported relationship to the associated PWWN will be opposite on each router.



be opposite on each router.

Verify that the host can see assigned storage

WAN Analysis

Introduced in Fabric OS v5.2.0, WAN analysis tools are designed to estimate the end-to-end IP path performance characteristics between a pair of Brocade FCIP port endpoints. WAN tools include the following commands and options:

• portCmd ipPerf—Characterizes end-to-end IP path performance between a pair of Brocade FCIP ports.



You can use the WAN tool ipPerf only on the FR4-18i or SilkWorm 7500 FCIP ports running Fabric OS v5.2.0 or later software.

• portShow fcipTunnel—Displays performance statistics generated from the WAN analysis.

Perf Terminology

s



Brocade Services OfferingsUnmatched Expertise for Ongoing Customer Needs

Professional Services and Support:

• Assess

• Design

• Implement



• Maintain

• Support

Documents

Brocade FCIP/FCR Implementation - switchsanguru.comswitchsanguru.com/images/Telcom_Kickoff_Presentation_Compatibility... · Brocade FCIP/FCR Implementation MAJOR TELCOM COMPANY