If you have a multi homed host and are running:

· IBM AIX,

· HP-UX,

· Linux,

· Solaris,

· VMware ESX Server (2.5.0 or later), or

· Microsoft Windows

you must create a parameter file for Navisphere Agent, named agentID.txt.

About the agentID.txt file

This file, agentID.txt (case sensitive), ensures that the Navisphere Agent binds to the correct HBA/NIC for registration and therefore registers the host with the correct storage system. The agentID.txt file must contain the following two lines:

Line1: Fully-qualified hostname of the host

Line 2: IP address of the HBA/NIC port that you want Navisphere Agent to use

For example, if your host is named host28 on the domain mydomain.com and your host contains two HBAs/NICs, HBA/NIC1 with IP address 192.111.222.2 and HBA/NIC2 with IP address 192.111.222.3, and you want the Navisphere Agent to use NIC 2, you would configure agentID.txt as follows:

host28.mydomain.com

192.111.222.3

To create the agentID.txt file, continue with the appropriate procedure for your operating system:

· IBM AIX, HP-UX, Linux, or Solaris

· VMware ESX Server 2.5.0 and later

· Microsoft Windows

For IBM AIX, HP-UX, Linux, and Solaris

1. Using a text editor that does not add special formatting, create or edit a file named agentID.txt in either / (root) or in a directory of your choice.

2. Add the hostname and IP address lines as described above. This file should contain only these two lines, without formatting.

3. Save the agentID.txt file.

4. If you created the agentID.txt file in a directory other than root, for Navisphere Agent to restart after a system reboot using the correct path to the agentID.txt file, set the environment variable EV_AGENTID_DIRECTORY to point to the directory where you created agentID.txt.

5. If a HostIdFile.txt file is present in the directory shown for your operating system, delete or rename it. The HostIdFile.txt file is located in the following directory for your operating system:

6. Stop and then restart the Navisphere Agent.

NOTE: Navisphere may take some time to update, however, it should update within 10 minutes.

7. Once the Navisphere Agent has restarted, verify that Navisphere Agent is using the IP address that is entered in the agentID.txt file. To do this, check the new HostIdFile.txt file. You should see the IP address that is entered in the agentID.txt file.

The HostIdFile.txt file is in the following directory for your operating system:

For VMware ESX Server 2.5.0 and later

1. Confirm that Navisphere agent is not installed.

2. Using a text editor that does not add special formatting, create or edit a file named agentID.txt in either / (root) or in a directory of your choice.

3. Add the hostname and IP address lines as described above. This file should contain only these two lines, without formatting.

4. Save the agentID.txt file.

5. If you created the agentID.txt file in a directory other than root, for subsequent Agent restarts to use the correct path to the agentID.txt file, set the environment variable EV_AGENTID_DIRECTORY to point to the directory where you created agentID.txt.

6. If a HostIdFile.txt file is present in the /var/log/ directory, delete or rename it.

7. Reboot the VMWARE ESX server.

8. Install and start Navisphere Agent and confirm that it has started.

NOTE: Before installing Navisphere Agent, refer to the EMC Support Matrix and confirm that you are installing the correct version.

NOTE: If necessary, you can restart the Navisphere Agent

NOTE: Navisphere may take some time to update, however, it should update within 10 minutes.

9. Once the Navisphere Agent has restarted, verify that Navisphere Agent is using the IP address that is entered in the agentID.txt file. To do this, check the new HostIdFile.txt file which is located in the /var/log/ directory. You should see the IP address that is entered in the agentID.txt file.

For Microsoft Windows

1. Using a text editor that does not add special formatting, create a file named agentID.txt in the directory C:/ProgramFiles/EMC/Navisphere Agent.

2. Add the hostname and IP address lines as described above. This file should contain only these two lines, without formatting.

3. Save the agentID.txt file.

4. If a HostIdFile.txt file is present in the C:/ProgramFiles/EMC/Navisphere Agent directory, delete or rename it.

5. Restart the Navisphere Agent

NOTE: Navisphere may take some time to update, however, it should update within 10 minutes.

6. Once the Navisphere Agent has restarted, verify that Navisphere Agent is using the correct IP address that is entered in the agentID.txt file. Either:

· In Navisphere Manager, verify that the host IP address is the same as the IP address that you you entered in the agentID.txt file. If the address is the same, the agentID.txt file is configured correctly.

· Check the new HostIdFile.txt file. You should see the IP address that is entered in the agentID.txt file.

You can change the storage system password in Navisphere Manager as follows:

1. Open Navisphere Manager

2. Click Tools > Security > Change Password.

3. In the Change Password window, enter the old (
current) password in the Old Password text box.

4. Enter the new password in the New Password text box and then enter it again in the Confirm New Password text box.

5. Click OK to apply the new password or Cancel to keep the current password.

6. In the confirmation popup, click either Yes to change the password or No to cancel the change and retain your current (old) password.

Note: If you click Yes, you will briefly see “The operation successfully completed” and then you will be disconnected. You will need to log back in using the new password.

When you initially install a new storage system, you must run the Navisphere Storage System Initialization Utility which prompts you to configure IP addresses for the SPs and set up accounts to log in to the SPs. You use these IP addresses when you connect and log into Navisphere Manager.

For an existing storage system that has been installed, initialized, configured, and possibly used, you must use Navisphere Manager to change the IP address of an SP. This FAQ outlines how to change the IP address of an SP on an existing storage system.

IMPORTANT: Before you change the IP address of an SP, if the storage system is on a domain, you must remove that storage system from the domain. When you enter a new IP address and accept the acknowledgments to change the address, you will be disconnected and the SP will reboot. You will then need to log onto the SP using the new address and add the storage system to a domain. If the storage system was the domain Master, when you re-connect, you will need to either recreate the domain and become master or else join another domain.

Dont forget to create the PPP Dialup Connection before attempting to login to the SP, otherwise it will fail

1. Open Navisphere Manager.

2. If the storage system is in a domain, remove it from the domain.

3. Under the Storage tab, click and expand the icon for the storage system that you want to modify.

4. Right-click the SP whose IP address you want to change and select Properties.

5. Click the Network tab.

6. Enter the new IP address in the IP Address field.

7. Click Apply to apply the change.

Note: If you have not removed the SP from the domain, you will see a prompt that strongly suggests that you cancel the operation and remove the SP from the domain before changing the SP’s IP address. Click either Yes to continue or No to cancel the address change.

8. At the confirmation prompt, click Yes to continue or No to cancel the IP address change.

9. At the second confirmation prompt, click Yes to continue or No to cancel the IP address change.

Note: Either Navisphere Manager will fail over to the unchanged SP, or the Navisphere Manager session will disconnect. In either case, the changed SP will reboot and will be available at the new IP address.

10. If Navisphere manager did not fail over to the unchanged SP, log into Navisphere Manager on either SP, noting that the changed SP has the new address.

11. Add the storage system to an existing domain or if necessary, create a new domain with the SP as master. See Help in Navisphere Manager.

Note: For further information on using Navisphere Manager, click Help in Navisphere Manager.

This article outlines how to add storage capacity to your storage system. You may have already performed some of the steps. See the appropriate procedure for your operating system.

Microsoft Windows

1. If needed, add new drives to the storage system.

2. If needed, create a hot spare using Navisphere Manager.

3. If needed, create an additional RAID group on the drives using Navisphere Manager.

4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.

5. Assign the new LUNs to the server using Navisphere Manager.

6. Verify that the new LUNs were assigned to the server using Navisphere Manager.

7. On the server, verify that the server has access to the LUNs:

a. On the Windows desktop, right-click My Computer and click Manage.

b. In the left pane of the Computer Management dialog box, double-click on the storage icon.

c. Click Disk Management.

d. Verify that the LUNs that you added are listed in the right pane.

8. Start or restart the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.

9. On the server, start PowerPath and verify that PowerPath sees all of the paths to the LUN.

Linux

1. If needed, add new drives to the storage system.

2. If needed, create a hot spare using Navisphere Manager.

3. If needed, create an additional RAID group on the drives using Navisphere Manager.

4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.

5. Assign the new LUNs to the server using Navisphere Manager.

6. Verify that the LUNs were assigned to the server using Navisphere Manager.

7. On the server, verify that all LUNS have entries in the /proc/scsi/scsi/ directory.

8. On the server, verify that each LUN has an entry in the appropriate HBA file:

· For QLogic HBAs, the entry is in proc/scsi/qlaxxx/hba_number

· For Emulex HBAs, the entry is in /proc/scsi/lpfc/hba_number

9. On the server, verify that the failover software recognizes all of the paths to the LUNs.

For example, for PowerPath, verify that PowerPath recognizes all of the paths to the LUNs using the powermt command: powermt display dev=all class=clariion

10. Partition the LUN and then create and mount a file system to make the LUN available to the operating system.

11. Run the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.

12. Save the failover configuration.

For example, for PowerPath, save the PowerPath configuration using the powermt save command.

13. On the server, verify that the server and failover software sees all of the paths to the LUN.V

For example, for PowerPath, verify the configuration using the powermt display command.

Novell NetWare

1. If needed, add new drives to the storage system.

2. If needed, create a hot spare using Navisphere Manager.

3. If needed, create an additional RAID group using Navisphere Manager.

4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.

5. Assign the new LUNs to the server using Navisphere Manager.

6. Verify that the new LUNs were assigned to the server using Navisphere Manager.

7. On the server, verify that the PowerPath failover software recognizes all of the paths to the LUNs. Use the powermt command:

powermt display dev=all class=clariion

7. Create NSS or NWFS partitions or volumes on the LUNs.

8. Make the LUNs available to the operating system; on the LUNs create and mount NetWare NWFS volumes or NetWare NSS partitions or volumes.

9. Restart Navisphere Agent.

10. Save the PowerPath failover configuration using the powermt save command.