HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.x administrator guide (5697 - Page 406

NOTE: If you do not specify a destination IP address, the destination address defaults to 0.0.0.0, and all frames are tagged with the associated VLAN tag. FCIP and ipPerf create and maintain entries in the VLAN tag table through their own configuration procedures. Manual entries are needed on both the local and remote sides for portcmd ping and portcmd traceroute commands when they are used to test and trace routes across a VLAN when no FCIP tunnel is active. The following The portCfg vlantag command is used to add or delete entries in the VLAN tag table. The syntax for the portCfg vlantag command is as follows: portcfg vlantag add|delete ipif_addr vlan_id L2CoS dest_IP_addr Where: pif_addr vlan_id L2CoS dest_IP_addr The locally defined IP address. The VLAN tag used for this tag (range 1-4094). Layer 2 class of service (range 0-7) The destination IP address. All frames destined for this IP address will be tagged with the specified vlan_id and L2 CoS. If a destination IP address is not specified, all frames not already tagged will be tagged. 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. portcfg vlantag 8/ge0 add 192.168.10.1 100 3 7 192.168.20.1 Troubleshooting FCIP links The following list contains information for troubleshooting FCIP links: • When deleting FCIP links, you must delete them in the exact reverse order they were created. That is, delete first the tunnels, then the IP interfaces, and finally the port configuration. The IP route information is removed automatically at this point. • IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots without first deleting configurations, errors can be seen when trying to reuse these IP addresses. • The portCmd ping command only verifies physical connectivity. This command does not verify that you have configured the ports correctly for FCIP tunnels. • One port can be included in multiple tunnels, but each tunnel must have at least one port that is unique to that tunnel. • Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a VE_Port. • When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and the backbone fabric will use VEX_Ports for a single tunnel. • 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. • Due to an IPSec RASLog limitation, you may not be able to determine an incorrect configuration that causes an IPSec tunnel to not become active. This misconfiguration can occur on either end of the tunnel. As a result, you must correctly match the encryption method, authentication algorithm, and other configurations on each end of the tunnel. 406 Configuring and monitoring FCIP extension services