Enterprise Volume Manager (Multi-OS) Version 2.0D Network Administration Guide

6–8 Enterprise Volume Manager (Multi-OS) Network Administration Guide
Troubleshooting
Given the wide variety of possible network configurations, the default methods used
by EVM to establish this communications interface may not always work properly.
Assuming that the EVM host agent is installed and running properly, an EVM host
agent connectivity problem is likely if the EVM host agent computer:
• Does not show up in the EVM Resource page
• Shows up in the EVM Resource page, but does not display any volume
information
EVM Host Agent Computer Not on Resources Page
Most likely, the EVM host agent computer cannot communicate with the Management
Appliance (EVM server) using the network name entered during the EVM host agent
installation. Use the following general procedure to resolve this problem:
1. Using ping, nslookup, or another network utility, determine the name or Internet
Protocol (IP) address of the Management Appliance on which the EVM server is
installed.
2. Stop the EVM service on the EVM host agent.
3. Open the sb.ini file in the ..\Enterprise Volume Manager\bin directory.
4. Change the APPL_NAME field to the name determined in step 1.
5. Save the file.
6. Restart the EVM service.
EVM Host Agent Computer Does Not Display Volume Information
For this problem, the EVM host agent is able to communicate with the Management
Appliance (EVM server), but the EVM server is unable to communicate with the
EVM host agent. By default, the EVM server uses the NetBios name of the EVM host
agent computer. In some cases, the Management Appliance (EVM server) may be
unable to resolve the EVM host agent computer using this name.
EVM provides two alternate methods that should resolve the problem in nearly all
cases. In the sb.ini file on the EVM host agent computer, there are two optional fields:
NEWHOSTNAME and SHOWFQDN. By default, both are set to zero. The two methods
include the following:
1. Set the SHOWFQDN field to 1 to allow the EVM server to use the Fully Qualified
Domain Name of the EVM host agent computer. If the problem persists, try the
next method.