476 Configuring and monitoring FCIP extension services
Creating IP interfaces and routes
The IP network connection between two HP StorageWorks 400 Multi-Protocol Routers or two FR4-18i
blades or one HP StorageWorks 400 Multi-Protocol Router and one FR4-18i blade is configured by
defining IP interfaces for origin and destination virtual ports, and then defining one or more IP routes to
connect them.
1.
Define the IP interface of each virtual port, using the
portCfg
command. You can define up to eight IP
interfaces per GbE port. The command syntax is as follows.
portCfg ipif [slot/]ge0|ge1 create src_ipaddr mtu_size
where:
slot
The number of a slot in an HP StorageWorks 4/256 SAN Director and HP StorageWorks DC
SAN Backbone Director and HP StorageWorks DC04 SAN Director platforms that contains an
FR4-18i blade. This parameter does not apply to the stand-alone HP StorageWorks 400
Multi-Protocol Router.
ge0|ge1
The Ethernet port used by the tunnel (ge0 or ge1).
src_ipaddr
The source IP address in either IPv6 or IPv4 format:
src_IPv6_addr/[prefix_len]
Specifies the source IPv6 address of the virtual port if IPv6 is used. The address must be an IPv6
global, Unicast address. As an option, specify the prefix length. This is used for IPv6 addresses
instead of a netmask. If prefix_len is not specified, the prefix length learned from the Neighbor
Discovery protocol will be used.
src_IPv4_addr netmask
Specifies the source IPv4 address of the virtual port, if IPv4 is used. If an IPv4 address is used,
the subnet mask must be specified as well (in a.b.c.d. format.)
mtu_size
The maximum transmission unit size. The range allowed is 1260 to 2348 B. HP recommends
that you set the value to 1500 B, which is the normal value in an Ethernet network. Some
networks support jumbo packets (packets larger than 1500 B). If the network you are using
supports jumbo packets, a value of 2348 can improve performance.
By default, the virtual ports will automatically become VE_Ports.
2.
Define IP routes on a GbE port. After defining the IP interface of the remote switch, you can define
destination routes on an interface. You can specify a maximum of 32 routes per GbE port. The
command syntax is as follows.
portCfg iproute [slot/]ge0|ge1 create dest_ipaddr gateway_router [metric]
where:
slot
The number of a slot in an HP StorageWorks 4/256 SAN Director, an HP StorageWorks DC
SAN Backbone Director or HP StorageWorks DC04 SAN Director Switch enterprise-class
platform that contains an FR4-18i blade. This parameter does not apply to the stand-alone HP
StorageWorks 400 Multi-Protocol Router.
ge0|ge1
The Ethernet port used by the tunnel (ge0 or ge1).
dest_ipaddr
The source IP address in either IPv6 or IPv4 format:
dest_IPv6_addr/[prefix_len]
The destination IPv6 address of the virtual port, if IPv6 is used. The address must be an IPv6
global, unicast address. As an option, specify the prefix length. This is used for IPv6 addresses
instead of a netmask. If prefix_len is not specified, the prefix length learned from the Neighbor
Discovery protocol will be used.
dest_IPv4_addr netmask
The destination IPv4 address of the virtual port, if IPv4 is used. If an IPv4 address is used, the
subnet mask must be specified as well. Use a.b.c.d. format.
gateway_router
The IP address of an IP router that can route packets to the destination virtual port IP address.
The gateway address must be on the same IP subnet as one of the port IP addresses.
metric
The link metric associated with the route. Valid values are 0-255. The default value is 0. A low
value encourages the use of the route, and a high value discourages the use of a route.
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 ...