Brocade Fabric OS FCIP Administrator's Guide v7.1.0 (53-1002748-01, March 2013)

38 Fabric OS FCIP Administrator’s Guide
53-1002748-01
Configuration steps
2
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.
For the FX8-24 blade, set the GbE or XGE port operating mode.
Assign IP addresses to the GbE or XGE ports using the portCfg ipif command.
Create one or more IP routes using the portCfg iproute command.
Test the IP connection using the portCmd --ping command.
NOTE
When using VLANS, VLAN tagging ensures that test traffic traverses the same path as real FCIP
traffic. A VLAN tag entry for both the local and remote sides of the route must exist prior to
issuing the portCmd --ping command. Refer to “Managing the VLAN tag table” on page 28 for
details.
Create FCIP tunnels and FCIP circuits, and enable or disable features.
Persistently enable the VE_Ports.
Configuration hierarchy
FCIP configuration must be done in the following order:
1. Create an IP interface (ipif) by assigning an IP address, netmask, and an MTU size to a port.
2. Create IP routes to a port.
3. Create an FCIP tunnel.
4. Create FCIP circuits (after circuit 0).
Setting VE_Ports to persistently disabled state
It is strongly recommended to persistently disable VE_Ports while tunnel configuration is in
progress. This will prevent unwanted fabric merges from occurring until the FCIP tunnel is fully
configured. 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.
1. Enter the portCfgShow command to view ports that are persistently disabled.
2. Enter the portCfgPersistentDisable command to disable any VE_Ports that you will use in the
FCIP tunnel configuration.
Disabling ports when fmsmode is enabled
If you enter portCfgPersistentDisable and receive “command not allowed in fmsmode” or
“command not found” messages, fmsmode may be enabled. You cannot use
portCfgPersistentEnable or portCfgPersistentDisable commands with fmsmode enabled. Use
portdisable and portenable commands instead.