HP StorageWorks Data Replication Manager HSG80 ACS Version 8.7P Configuration Guide (AA-RPHZF-TE, March 2004)

Configuring a Standard Data Replication Manager Solution
142 Data Replication Manager HSG80 ACS Version 8.7P Configuration Guide
I 3. Verify that the host has logged into the fabric:
SHOW CONNECTIONS
You should see a display similar to that in Example Display 50.
Example Display 50
Connection Unit
Name Operating system Controller Port Address Status Offset
!NEWCON00 WINNT THIS 1 210013 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn . . . . ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
!NEWCON01 WINNT OTHER 1 200013 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn . . . . ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
Rename the Host Connections
To better identify which hosts you are working with, HP recommends that you rename the host
connections using a meaningful connection name for each. Each HBA appears as a
connection. An HBA can be identified by its WWN, which you recorded when you installed
the HBAs, and which appears in the connection description.
Initially, each connection is named !NEWCONxx. It is much easier to track connections if the
connection names are meaningful, like “HostA1.” We suggest that you use the worksheet in
Figure 19 on page 76 when renaming your hosts.
Note: If you use scripting to automate failover and failback operations, do not use dashes (hyphens)
as separators in your naming convention—use underscores instead. Dashes are not allowed by the
Perl scripting language.
I 1. When you have completed the worksheet, rename the connections:
RENAME !NEWCON01 InitiatorHostConnectionNamex
RENAME !NEWCON02 InitiatorHostConnectionNamey
Example: rename !NEWCONxx HostA1
Example: rename !NEWCONxx HostA2
I 2. Set the operating system for each connection to Solaris:
SET InitiatorHostConnectionNamex OPERATING_SYSTEM = SUN
Example: set HostA1 operating_system = sun
I 3. When you have finished renaming your host connections, verify your new settings:
SHOW CONNECTIONS
You should see a display similar to that in Example Display 51.