Oh yes, Thanks, In fact the CX is working very well but the 2 hosts are showing "Unmanaged" (one has host agent unreachable) and the monitor side shows only one host. Eveything was OK at the beginning but due to LUNZ disks we deregistered and registered and so on and the problem occurred. What can be the cause of the problem and how to solve it. Thanks Regards Consty
Can the "unreachable" hosts ping the Clarrion ? they need to be able to reach each other ! Think about default gateways, vlans, routing, that sort of things.
When Agent first starts it tries to use the first bound NIC on the server. If you server has more than one NIC, it may be trying to use a different NIC. You can force Agent to use a specific NIC by creating a file called agentID.txt. This cotains two entries, the first line is the name of the server and the second line is the IP address of the NIC you use to talk to the Management Server on the array (the management ports).
A host ID is a unique identifier generated by the operating system that Navisphere uses to identify hosts. On UNIX, the host ID is stored in the HostIDFile.txt file, which is created by the Navisphere Host Agent. On Windows, the host ID is stored only in the registry. The Windows Navisphere Agent does not create a special file. If a UNIX or Windows or NetWare host is cloned after the first unique Host ID is generated, multiple hosts will have the same ID and Navisphere will assume that they are the same host.
Note: The HostIdFile.txt is in /etc/log directory for AIX, HP-UX, and Solaris, in /usr/ssm/etc/log for IRIX, and in /var/log for Linux. On NetWare, the Host ID file is called NavHstId.txt and is in the sys:\etc directory. On Windows, the host ID is a registry entry. For information on host ID in a Windows cluster, see solution emc63224 ("How do I configure Navisphere Agent in a Windows NT or Windows 2000 clustered environment?").
The purpose agentID.txt file is to instruct Host Agent what hostname/IP address to use so that it matches the one that the client uses. The file can be used to override the default hostname/IP address and must be created manually. The fully qualified hostname must be on the first line of the file, and the host's dot-notation IP address must be on the second line. Comments are allowed in the file on lines following these two lines only. Lines are only visible if they are properly terminated. Adding a blank line after the first two lines ensures this. Lines may be empty, in which case the corresponding value defaults to what it would have been in the absence of this file. One way to get a host's IP address to enter into this file is to "ping" the hostname from the client computer.
The location of the agentID.txt file depends on the host type and the existence (or lack thereof) of an environment variable as follows:
If environment variable EV_AGENTID_DIRECTORY is defined and is not zero length, its value is used. Otherwise, for Windows only, if the location of the agent configuration file can be found in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\EMC\Agent\1.0\ConfigPath), its value will be used.
Otherwise, directory ¿\¿ is used for Windows, ¿/¿ for UNIX systems, and ¿sys:\¿ for NetWare.
For Windows hosts
Since Windows Agents do not create missing host IDs, it is best to correct these identifiers before a newly-cloned host is attached to any array. However, if you see duplicate host names (or only one registered host name) because you already attached and attempted to register a cloned host with the array, do the following:
Unplug the fiber cables from the host whose name doesn't appear as registered with the array.
Deregister the initiator records on the CLARiiON array for the problem host. Stop the Navisphere Agent service on that host and delete the following registry key:
Restart the Navisphere Host agent service. When Navisphere agent restarts a new unique HostID key should be generated and the host should register with the correct host name/ipaddress (provided the host name and ipaddress were already changed via sysprep or some other utility if they cloned the host).
Warning! Improperly editing the registry can render your system inoperable.
For UNIX hosts
Problems in Navisphere software can arise primarily from the inconsistent use of host ID, IP address, and/or hostname as unique keys for certain objects. The inconsistencies causing the problems can arise under certain circumstances when a client creates or changes an initiator record, or when a host Agent pushes changes to initiator records -- as is usually the case the first time a host Agent writes an initiator record. These problems most often occur when any of the three attributes is changed. However, problems can also arise when all changes being made are correct. Sometimes re-starting Navisphere software (client, SP agent, and/or Management Server) is required.
On cloned systems, you must pay special attention to both the HostIDFile.txt (wherever it resides) and the agentID.txt file. Preferably, on non-Windows hosts, the hostIDFile.txt and the agentID.txt file should be removed from a cloned image before the image is used. Clone the image.
Mount this new image as a regular disk.
Stop the agent.
Delete the HostID file from this cloned image and change the host name and IP address to new ones for this cloned image.
If you have the file AgentID.txt, make sure it only has the correct host name and IP address of the host (that is, you have to edit that file). This file is not created by the agent.
Boot the cloned image.
When the Agent starts again, it will create a new HostID file. At this point, you should be able to connect the cloned host to the SAN.
kelleg
4 Operator
•
4.5K Posts
0
August 20th, 2008 15:00
glen
Consty
2 Intern
•
232 Posts
0
August 26th, 2008 13:00
In fact the CX is working very well but the 2 hosts are showing "Unmanaged"
(one has host agent unreachable) and the monitor side shows only one host.
Eveything was OK at the beginning but due to LUNZ disks we deregistered and registered and so on and the problem occurred.
What can be the cause of the problem and how to solve it.
Thanks
Regards
Consty
RRR
4 Operator
•
5.7K Posts
0
August 31st, 2008 13:00
kelleg
4 Operator
•
4.5K Posts
0
September 3rd, 2008 10:00
When Agent first starts it tries to use the first bound NIC on the server. If you server has more than one NIC, it may be trying to use a different NIC. You can force Agent to use a specific NIC by creating a file called agentID.txt. This cotains two entries, the first line is the name of the server and the second line is the IP address of the NIC you use to talk to the Management Server on the array (the management ports).
A host ID is a unique identifier generated by the operating system that Navisphere uses to identify hosts. On UNIX, the host ID is stored in the HostIDFile.txt file, which is created by the Navisphere Host Agent. On Windows, the host ID is stored only in the registry. The Windows Navisphere Agent does not create a special file. If a UNIX or Windows or NetWare host is cloned after the first unique Host ID is generated, multiple hosts will have the same ID and Navisphere will assume that they are the same host.
Note: The HostIdFile.txt is in /etc/log directory for AIX, HP-UX, and Solaris, in /usr/ssm/etc/log for IRIX, and in /var/log for Linux. On NetWare, the Host ID file is called NavHstId.txt and is in the sys:\etc directory. On Windows, the host ID is a registry entry. For information on host ID in a Windows cluster, see solution emc63224 ("How do I configure Navisphere Agent in a Windows NT or Windows 2000 clustered environment?").
The purpose agentID.txt file is to instruct Host Agent what hostname/IP address to use so that it matches the one that the client uses. The file can be used to override the default hostname/IP address and must be created manually. The fully qualified hostname must be on the first line of the file, and the host's dot-notation IP address must be on the second line. Comments are allowed in the file on lines following these two lines only. Lines are only visible if they are properly terminated. Adding a blank line after the first two lines ensures this. Lines may be empty, in which case the corresponding value defaults to what it would have been in the absence of this file. One way to get a host's IP address to enter into this file is to "ping" the hostname from the client computer.
The location of the agentID.txt file depends on the host type and the existence (or lack thereof) of an environment variable as follows:
If environment variable EV_AGENTID_DIRECTORY is defined and is not zero length, its value is used. Otherwise, for Windows only, if the location of the agent configuration file can be found in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\EMC\Agent\1.0\ConfigPath), its value will be used.
Otherwise, directory ¿\¿ is used for Windows, ¿/¿ for UNIX systems, and ¿sys:\¿ for NetWare.
For Windows hosts
Since Windows Agents do not create missing host IDs, it is best to correct these identifiers before a newly-cloned host is attached to any array. However, if you see duplicate host names (or only one registered host name) because you already attached and attempted to register a cloned host with the array, do the following:
Unplug the fiber cables from the host whose name doesn't appear as registered with the array.
Deregister the initiator records on the CLARiiON array for the problem host.
Stop the Navisphere Agent service on that host and delete the following registry key:
HKEY_LOCAL_MACHINE -> SOFTWARE -> EMC -> Agent -> 1.0 > HostID
Reconnect the fiber cables.
Restart the Navisphere Host agent service. When Navisphere agent restarts a new unique HostID key should be generated and the host should register with the correct host name/ipaddress (provided the host name and ipaddress were already changed via sysprep or some other utility if they cloned the host).
Warning! Improperly editing the registry can render your system inoperable.
For UNIX hosts
Problems in Navisphere software can arise primarily from the inconsistent use of host ID, IP address, and/or hostname as unique keys for certain objects. The inconsistencies causing the problems can arise under certain circumstances when a client creates or changes an initiator record, or when a host Agent pushes changes to initiator records -- as is usually the case the first time a host Agent writes an initiator record. These problems most often occur when any of the three attributes is changed. However, problems can also arise when all changes being made are correct. Sometimes re-starting Navisphere software (client, SP agent, and/or Management Server) is required.
On cloned systems, you must pay special attention to both the HostIDFile.txt (wherever it resides) and the agentID.txt file. Preferably, on non-Windows hosts, the hostIDFile.txt and the agentID.txt file should be removed from a cloned image before the image is used. Clone the image.
Mount this new image as a regular disk.
Stop the agent.
Delete the HostID file from this cloned image and change the host name and IP address to new ones for this cloned image.
If you have the file AgentID.txt, make sure it only has the correct host name and IP address of the host (that is, you have to edit that file). This file is not created by the agent.
Boot the cloned image.
When the Agent starts again, it will create a new HostID file. At this point, you should be able to connect the cloned host to the SAN.
glen