HP 3PAR Operating System Software - Manual (Page 34)

1. Issue the controlport rcip mtu command:
# controlport rcip mtu 9000 <N:S:P>
where <N:S:P> represents the location of the GigE port, expressed as node:slot:port,
and the MTU value specified is the same value returned by the cli checkrclink command
for Max MTU.
2. Repeat the command for all remote-copy GigE ports on each storage system.
3. From a storage system, use the controlport rcip ping command to verify that the
network supports the increased MTU size:
# controlport rcip ping -s 8972 -pf <IP_address> <N:S:P>
where:
•
8972 —Test packet size
•
<IP_address> —IP address on the target system to ping
•
<N:S:P> —Interface from which to ping
4. Use the controlport rcip ping command for each interface on each system in the
configuration.
NOTE: Because of the spanning tree protocol and MAC address learning, you might need
to ping each system several times before the server updates all tables and the ping succeeds.
Solution Problem
The pings do not
succeed. 1. Issue another set of pings without specifying a size:
controlport rcip ping -pf <IP_address> <N:S:P>
If this ping command succeeds, the network does not support 9000-byte MTU.
2. Revert to 1500 MTU:
controlport rcip mtu 1500 <N:S:P>
3. Proceed to “Setting Up the Remote Copy Servers” (page 39) .
5. After MTU has been verified, use the following commands to bring the ports up or down:
# controlport rcip state up <N:S:P>
# controlport rcip state down <N:S:P>
Setting Up Remote Copy over Fibre Channel
RCFC Remote-Copy Pair Worksheet
Figure 12 (page 35) illustrates the initial remote-copy pair in an RCFC configuration.
34 Setting the Transport Layer