Diagnosing a Remote Replication Connection Problem
$DEV_NAME $FRU_NAME, has been selected.
To prepare for this service action, perform the following:
Note: The Reserve function is not used in this procedure in order to execute the Remote Communications Test used below.
The remote volume name will be needed to execute the Remote Communications Test used in this procedure. If it is not known, return to the Web Console by selecting the Console button from the top left side of the Storage Automated Diagnostic Environment main screen.
At the Web Console screen select the Sun StorEdge Configuration Services link under the Storage category on the left.
At the Array Summary screen under the Name column select the array name link for the remote/secondary tray.
At the Volume Summary screen note the volume name. It can be identified as "Replicated" under the Type column.
Verify the controller "State" and "Status".
a) The controller "State" should be "Enable" and the "Status" should be "OK".
From the index on the left-side of the screen select the corresponding controller tray that is part of the Remote Replication Set and verify the "State" and "Status" of its controllers.
If any of the controllers do not have a "State" of "Enable" and a "Status" of "OK" check for associated alarms and if necessary proceed to the controller removal/replacement procedures. If necessary contact your Sun Service provider.
Verify that the Remote Replication links are functional.
Run the Communication Check test.a) From the Diagnostics table select the Remote Peer Communication Check text button.
b) Select the Run Test button at the top left of the table.
c) From the Test Setup screen enter the Remote Volume Name (this is the name of the mirror volume on the remote mirror array ).
d) From the Test Setup screen the Sample size can be changed from the default value if desired.
e) Select the Run Button from the right side of the screen.
f) From the Execute Diagnostic pop-up screen select the OK button or hit Return/Enter.
After the test has completed check the Test Overview table for a "Completed Successfully" or a "Failed" status. Based on the test return information proceed to one of the following sections.
Inspect the cables for physical damage at all connection points.
Reseat the cables at connection points if necessary.
Inspect the SFP transceivers at all connection points.
Reseat the SFP transceivers at all connection points if necessary.
Return to the Web Console by selecting the Console button from the top left side of the screen.
At the Web Console screen select the Sun StorEdge Configuration Services link under the Storage category on the left.
At the Array Summary screen under the Name column select the appropriate array name link.
At the Volume Summary screen select the Administration tab from above.
At the General Setup screen select the Licensing tab from above.
At the Licensable Feature Summary screen under the Feature column locate "Replication Sets" to verify the following:
a) Verify that the Remote Replication feature is enabled (True).
b) Verify that the quantity licensed and quantity in use are correct.
If at this point the problem has not been identified or still exists contact your next level of support.
After this service action has been completed verify that the Remote Replication links are now functional.
Run the Communication Check test.a) From the Diagnostics table select the Remote Peer Communication Check text button.
b) Select the Run Test button at the top left of the table.
c) From the Test Setup screen enter the Remote Volume Name (this is the name of the mirror volume on the remote mirror array ).
d) From the Test Setup screen the Sample size can be changed from the default value if desired.
e) Select the Run Button from the right side of the screen.
f) From the Execute Diagnostic pop-up screen select the OK button or hit Return/Enter.
All Alarms will need to be deleted: Delete Alarms.
a) From the left side of the screen select the "check mark" box to select all alarms.
b) Select the Delete button to delete all of the alarms.
Note: Be sure to delete any associated alarms from all other monitoring applications.