 |
» |
|
|
|
There
are two components you need to configure before using hp
ldc: the HP LDControl server and the HP LDControl daemon. First, bring up the LDControl page by doing the following: Start the HP server. Type the following:
/opt/hpldc/admserv/start-admin Start a browser that supports frames, is Java-enabled,
and supports JDK 1.1. Go to the URL http://hostname:8282 where hostname is the name of the system on which you are running the
HP server. Reload this page if you have visited it prior to this installation. Enter the following administration user (server)
ID and password: User ID: hpadmin
Password: Enter the password you configured
when you ran /opt/hpldc/admserv/setup after installation. The HP LDControl page displays.
Configuring a System with More than One LAN Card | |
If the system on which you are running the web server has
more than one LAN card, you must set the snmp-server host and real parameters in Cisco LocalDirector. Do the following: On the system with multiple LAN cards,
run netstat -rn and check the routing table information. Use the IP
address associated with the Cisco LocalDirector gateway to configure
the snmp-server host parameter of Cisco LocalDirector. On the system with multiple LAN cards, run
nslookup local_hostname and use this IP address to configure the real parameter of Cisco LocalDirector.
Refer to Cisco LocalDirector's manuals for information
on setting these parameters. Troubleshooting the HP LD Controller | |
If an error occurs, check the following two log files for
error messages, causes, and recommended actions: /var/opt/hpldc/ldc.log /var/opt/hpldc/webstone.log
Problems Accessing the HP LD ControllerTable 6-3 Browser Error Message and Action | Error Message | Action |
|---|
| Applet ConfApplet can't start. | The browser that you are using to administer
the system must support JDK 1.1 in order to run hpldc.
Two browsers that support JDK 1.1 are Netscape Navigator 4.06 and
Microsoft Internet Explorer 4.0. |
If the HP LDControl daemon dies, check for the following error
messages in the /var/opt/hpldc/ldc.log file. Complete the listed actions for the specified
messages Table 6-4 HP LDControl Daemon Error Log Messages and Actions | Error Message | Action |
|---|
| Cannot open file filename. | Check that the file filename exists and that the HP LDControl daemon has write
permission to its directory. | | Server might be down. Initial weight set to
0. Exiting. | 1. Make sure the web server is running on the
system. Restart/Start the web server and then restart the HP LDControl daemon.
2.
Check the parameters in the file /etc/hpldc/webstone/conf/server-list.
3. In /etc/passwd, check for the following entry:
webstone:trKI3jiXvewTw:33:1::/tmp:/sbin/sh
If this entry does not exist,
add it to the file.
4. If the web server is running,
make sure it is using a non-SSL port. The HP LDControl daemon must
use a non-SSL port to generate the initial weight. | | Cannot send weight to LocalDirector. | 1. The snmp-server host parameter must be set on the system running Cisco
LocalDirector. Refer to Cisco LocalDirector's manual for
more information on setting this parameter.
2.
Check that LDHostname is set to the system running Cisco LocalDirector
in the /etc/opt/hpldc/conf/ldc.conf file. |
Problems With HP LocalDirector Controller and Cisco
LocalDirector | |
To verify that the HP LDC agent (
ldc_agt) is up and running, type the following:
ps -efa|grep ldc_agt If ldc_agt is not running, start ldc_agt to
see if it solves the problem. Refer to “Starting and Stopping the HP LDControl
Daemon”. If ldc_agt stops running a few minutes
after you have started it, dynamic weighting may be turned off (see
Step 3b). Look at the log file /var/opt/hpldc/ldc.log for
error messages that may indicate the problem. Look at the entries in /etc/opt/hpldc/conf/ldc.conf for
the following: Make sure the value of LDHostname is
configured to the name of the Cisco LocalDirector. Use ping to test the network connectivity to the Cisco LocalDirector:
ping <LD_hostname>
where
<LD_hostname> is the value
of LDHostname. Look at the value of DynamicWeight. If DynamicWeight is set to "off," the
HP LDC agent sends the Initial weight to Cisco LocalDirector and
then stops running, since there are no on-going dynamic weight adjustments.
In the 'off" mode, it is normal for the HP LDC
agent to stop running a few minutes after it has been started. If DynamicWeight is set to "on," the
HP LDC agent sends the Initial weight to Cisco LocalDirector and
then continues to run so it can monitor the system and dynamically
change the weight if needed. In the "on" mode,
the HP LDC agent should always be running. Verify the value of InitialWeight. Compare
the value of InitialWeight in ldc.conf with
the number stored in /var/opt/hpldc/weight.
They should be identical. If they
match, you are ready to run the snmp_test program. Go
to step 4. If they do not match, HP LDC
might have trouble in getting the initial weight. Check the error
entries in ldc.log again and refer to “Troubleshooting the HP LD Controller ”.
If everything looks normal, you are ready to run
the snmp_test tool. The snmp_test program
tests the SNMP connectivity between the HP LocalDirector Controller
and Cisco's Local Director. It checks if both SNMP_get and SNMP_set are working. Before running the program, read the README.snmp_test. If the snmp_test runs successfully
without any errors, the SNMP connectivity between HP LocalDirector
Controller and Cisco's LocalDirector is working. The problem
may be on the Cisco side. Refer to Cisco LocalDirector's
manuals for troubleshooting information. If snmp_test finds errors, record the
errors and look up these errors in “Troubleshooting the HP LD Controller ”.
|
Printable version
