Google+

Archive

Posts Tagged ‘EMC’

Clariion CX, CX3, CX4 – Allocate LUNs to attached Host – Operating System

December 16th, 2008 No comments

The following steps only roughly outline how to make a LUN disk available to the operating system. The process is operating system dependent. This procedure assumes that you have already created a LUN.

Note: See the Navisphere Manager online help by clicking Help in Navisphere Manager.

Microsoft Windows

1. Open Navisphere Manager . Click the Help button and look for “Preparing LUNs to receive data.” See the procedures for Microsoft Windows.

2. Write a signature to the disk and upgrade it to a dynamic disk.

3. Create either partitions for a basic disk or volumes for a dynamic disk.

Linux

1. Open Navisphere Manager . Click Help and look for “Preparing LUNs to receive data.” See the procedures for Linux.

2. Partition the virtual disk.

3. Create and mount filesystems on the partitions.



Novell NetWare

1. Open Navisphere Manager . Click Help and look for “Preparing virtual disks to receive data.” See the procedures for NetWare.

2. Create NetWare partitions on the virtual disks.

3. Create and mount volumes.

Clariion CX, CX3, CX4 – How to Create a RAID Group

December 16th, 2008 No comments

The following steps briefly outline how to create a RAID Group:

Note: For detailed information about RAID groups, click Help in Navisphere Manager,

1. Open Navisphere Manager

2. In the Enterprise Storage dialog box, click the Storage tab to display a tree view of the Storage Systems.

3. Double-click the Storage system icon to open the storage system tree.

4. Click on the Create RAID Group… option.

5. RIght-click the RAID Groups icon to display a list of options available for RAID Groups.

6. The Create RAID Group dialog box opens.

7. Click Help in the dialog box to display descriptions of each property in the dialog box.

Clariion CX, CX3, CX4 – How to Create a LUN

December 16th, 2008 No comments

The following steps briefly outline how to create, or bind, a new LUN:

Note For detailed information on creating a RAID group, click Help in Navisphere Manager.

Note Binding a LUN can take a long time based on the size of the drives or LUNs you are trying to Bind!

Open Navisphere Manager

1. In the Enterprise Storage dialog box, click the Storage tab to display a tree view of the Storage Systems

2. Double-click the Storage system icon to open the storage system tree.

3. Right-click the storage-system icon, then click Bind LUN.

4. In the Bind LUN dialog box, enter the appropriate data into the dialog box, and follow the instructions as they appear. For help, click the Help button in the dialog box.

5. For detailed information about LUNs, click the Help button in Navisphere Manager.

Clariion CX, CX3, CX4 – Creating the Navisphere Agent File, agentID.txt

December 16th, 2008 No comments

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:

AIX

/etc/log/HostIdFile.txt

HP-UX

/etc/log/HostIdFile.txt

Linux

/var/log/HostIdFile.txt

Solaris

/etc/log/HostIdFile.txt

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:

AIX

/etc/log/HostIdFile.txt

HP-UX

/etc/log/HostIdFile.txt

Linux

/var/log/HostIdFile.txt

Solaris

/etc/log/HostIdFile.txt

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.