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

Fabric OS FCIP Administrator’s Guide 15

53-1002748-01

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

port.

Configuring VLAN tags with crossports

Add entries with crossport addresses to the VLAN tag table, as in the following example. This

example allows VE ports 12 through 21 to use the configured local IP interface with this VLAN tag.

portcfg vlantag 8/xge0 add 192.168.11.20 200 1 --crossport

portcfg vlantag 8/xge0 add 192.168.11.20 200 1 –x

Delete the VLAN tag using the delete option instead of the add option for the portcfg vlantag

command.

portcfg vlantag 8/xge0 delete 192.168.11.20 200 1 –x

Display VLAN tag configuration using the portshow vlantag command:

portshow vlantag 8/xge0

NOTE

To tag Class-F traffic or data path traffic, use the -v, - -vlan-tagging option for the fcipcircuit create or

fcipcircuit modify command. The portcfg vlantag command is primarily used for ping and traceroute

operation and not for tunnels and circuits.

For more information on managing VLAN tags, refer to “Managing the VLAN tag table” on page 28.

For more information on using Fabric OS commands, optional arguments, and command output

refer to the Fabric OS Command Reference Manual.

Using ping with crossports

You can ping crossport addresses 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.

portcmd --ping 8/xge0 -s 192.168.11.20 -d 1.1.1.1 --crossport

portcmd --ping 8/xge0 -s 192.168.11.20 -d 1.1.1.1 –x

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.

For more information on using ping, refer to “Using ping to test a connection” on page 68.