486 Configuring and monitoring FCIP extension services
Deleting an FCIP tunnel
1.
Connect to the switch and log in using an account assigned to the admin role.
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 IP interface (IPIF)
The following command deletes an IP interface.
portcfg ipif [slot/]ge0|ge1 delete ipaddr
Deleting an IProute
The following command deletes an IP route for a specified IPv4 address.
portcfg iproute [slot/]ge0|ge1 delete dest_IPv4_addr netmask
For an IPv6 address:
portcfg iproute [slot/]ge0|ge1 delete IPv6_addr/prefix_len
Managing the VLAN tag table
The VLAN tag table is used by ingress processing to filter inbound VLAN tagged frames. If a VLAN tagged
frame is received from the network and there is no entry in the VLAN tag table for the VLAN ID, the frame
is discarded.
The table is used to determine how to tag a frame that is not already tagged. To tag frames destined for a
specific host address, you must create an entry with an exact matching destination address in the table.
Only frames destined for that address are tagged with the associated VLAN ID. To tag frames destined for
a specific network, you must create a destination address entry for the network. For example; if a
destination address of 192.168.100.0 is specified, all frames destined for the 192.168.100.0 network are
tagged with the associated VLAN ID, assuming a network mask of 255.255.255.0. If an entry contains a
destination address of 0.0.0.0, all frames are tagged with the associated VLAN ID. If frames are already
VLAN tagged, those tags take precedence over entries in this table.
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.
1.
Connect to the switch and log in using an account assigned to the admin role.
2.
Enter the
portCfg vlantag
command 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 [dst_IP_addr]
where:
ipif_addr
The locally defined IP address.
vlan_id
The VLAN tag used for this tag (range 1-4094).
L2CoS
Layer 2 class of service (range 0-7)
dst_IP_addr
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.
Summary of Contents for A7533A - Brocade 4Gb SAN Switch Base
Page 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Page 24: ...24 ...
Page 99: ...Fabric OS 6 2 administrator guide 99 ...
Page 100: ...100 Managing user accounts ...
Page 118: ...116 Configuring standard security features ...
Page 164: ...162 Configuring advanced security features ...
Page 234: ...232 Installing and maintaining firmware ...
Page 268: ...266 Administering advanced zoning ...
Page 284: ...282 Configuring Enterprise class platforms ...
Page 292: ...290 Routing traffic ...
Page 294: ...292 Interoperability for merged SANs ...
Page 302: ...300 Configuring the Distributed Management Server ...
Page 334: ...332 iSCSI gateway service ...
Page 340: ...338 Administering NPIV ...
Page 407: ...Fabric OS 6 2 administrator guide 405 ...
Page 408: ...406 Using the FC FC routing service ...
Page 438: ...434 Administering extended fabrics ...
Page 460: ...456 Administering ISL trunking ...
Page 516: ...512 FICON fabrics ...
Page 526: ...522 Configuring and monitoring FICON Extension Services ...
Page 540: ...536 Configuring the PID format ...
Page 544: ...540 Understanding legacy password behavior ...
Page 546: ...542 Mixed fabric configurations for non merge SANs ...
Page 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Page 558: ...554 Inband Management ...
Page 572: ...568 ...