Host Resources: Verify Connectivity
A number of utilities can be used to verify connectivity to the hosts for which you want to collect data.
Host Resources: Check Host Connectivity Using Standard SSH
StorageConsole uses SSH to communicate with devices to run SSH commands. Sometimes, a connectivity issue is simply an incorrect path to a host.
Note: Use the following SSH commands before attempting to collect data.
To check host connectivity using standard SSH:
1. Check that the connection to a Host is successful, using the credentials provided.
[user@host ~] ssh <user>@<host> ls
Similarly, if you are using Telnet, check your host access via Telnet and run sudo commands, as shown in the following step.
2. In access-controlled environments such as sudo, a sudo user must be set up. Ensure that the sudo user can run the commands required for the host operating system platform.
To verify sudo access:
[user@host ~] ssh <sudouser>@<host> “sudo <command>”
If this command results in errors, such as
command not found, set up the paths correctly and re-run this command. See
“Checking Paths for SSH” on page 128.
3. Paths should be set correctly for the commands to run.
Checking Paths for SSH
If you find messages in the metadata.log file that indicate that some of the commands are not found, then most likely the reason for it is the paths have not been set properly.
StorageConsole uses a non-interactive login shell to execute ssh commands on devices.
1. Check the environment setting for the shell by running the command.
[user@host ~] ssh <user>@<host> “env”
Check the PATH shown in the output and make sure that it contains the path to all the commands required for StorageConsole for the OS platform of the host.
Sample PATH for each of the host operating system platforms:
Linux: /bin:/sbin:/usr/bin:/usr/sbin
Solaris: /usr/xpg4/bin:/usr/sbin:/usr/bin
AIX: /usr/bin:/usr/sbin
HPUX: /usr/bin:/usr/sbin:/opt/fcms/bin:/sbin
Note: Since Veritas Volume Manager is supported, its path needs to be included in the PATH env variable.
2. In sudo environments, make sure that the sudo path is also in the PATH shown in the output of the above command.
Environment Setting for bash users:
1. Define all your settings in the file: ~/.bashrc
2. Make sure that the file ~/.bash_profile only contains the line: source ~/.bashrc
Host Resources: Check Host Connectivity
This APTARE-provided utility displays information on the connection status of a list of host names, IP addresses, or a range of IP addresses.
Usage:
chkHostConnection.{sh|bat} HostAddresses userId password [domain <domain>] [exclude <excludeHostAddresses>] [wmiserver <wmiserver>] [cto <connectTimeout>] [sto socketTimeout>] [accessCmd=accessControlCommand>]
HostAddresses | The hosts to verify. It can be hostname, IP address, or range of IP addresses, or a comma-separated list of them. |
domain | The Domain for the Windows hosts |
excludeHostAddresses | The hosts to be excluded from the HostAddresses list. It can be hostname, IP address, or range of IP addresses, or a comma separated list of them. |
wmiserver | Name of the WMI Proxy Server |
cto | Connection time-out in milliseconds |
sto | Socket time-out in milliseconds |
accessCmd | An access control command such as sudo |
Result:
For each host, the status of the connection is listed.
Connectivity Check Server List: [172.16.1.10, 172.16.1.12, APTAREaix1]
172.16.1.10 ............. SUCCESS
172.16.1.12 ............. SUCCESS
Host Resources: Check Host Connectivity for the Host Resources Configuration File
This APTARE-provided utility provides information on the connection status of a list of Host Addresses that are provided in the Host Resource Configuration file.
Usage:
chkHostConnection.{sh|bat} file <HostResourceFile> [wmiserver <wmiserver>] [cto <connectTimeout>] [sto <socketTimeout>]
HostResourceFile | The file should be located under the home directory:
/mbs/conf/hostresourceconf |
wmiserver | Name of the WMI Proxy Server |
cto | Connection time-out in milliseconds |
sto | Socket time-out in milliseconds |
Result: For each host, the status of the connection is listed.
Connectivity Check Server List: [172.16.1.10, 172.16.1.12, aptareaix1]
172.16.1.10 ............. SUCCESS
172.16.1.12 ............. SUCCESS