Destination system peer link configuration issues, Problem – HP 3PAR Operating System Software User Manual
Page 18
Verify the source system has 2 separate nodes cabled to the switch fabric, and that each of the
nodes is zoned to a separate node on the destination system.
Destination System Peer Link Configuration Issues
Problem
Degraded. Occurs when any of the peer ports is not in a ready state.
Solution
Use showport to find the detailed status of the port and correct any issues.
Problem
Invalid Configuration. Occurs when the total number of peer ports is not two.
Solution 1
When the ports connection mode is not set to peer this message is not a problem. The port may
not yet be configured on the source system.
Solution 2
Use showport –peer CLI command to verify there are at least two connections between the
destination system and the hosts. The two connections must be to different nodes on the destination
system.
Solution 3
When the two peer ports are configured on the same node, use the showport –peer CLI
command to verify there are at least two connections between the destination system and the hosts.
The two connections must be to different nodes on the destination.
Solution 4
Verify the link status is OK. From the Main Menu, select option 2 ==> Analyze Migration Links.
Then select option 1 ==> Analyze Destination Array Peer Ports from the Analyze Migration Links
Menu.
Solution 5
Use the showport CLI command on the destination system to verify the port configuration is
correct. Use the controlport CLI command to change the port settings.
Solution 6
Use the showport CLI command on the destination system to verify the peer port connection type
for all ports is set to point. Use the controlport CLI command to set the peer port connection
type to point.
Problem
Invalid Zoning.
Cause 1
When the peer ports have multiple source system devices connected.
Solution 1
Rezone the switch fabric to ensure that the destination system peer ports are only zoned to the
ports on the source system you are migrating the data from.
Cause 2
When any of the peer ports has no source system device connected.
Solution 2
Rezone the switch fabric so that the source system host ports are zoned to the peer ports on the
destination system.
18
Troubleshooting the Peer Motion Manager Software