HP XP P9000 Command View Advanced Edition Suite Software 7.5.0-00 Installation and Configuration Guide (TB581-96344, July 2013)

When IBM XL C/C++ Enterprise Edition V8 for AIX Runtime version 8.0.0.3 to 8.0.0.5 is applied,
the overwrite installation of the Device Manager agent hangs if either:
the Hitachi Dynamic Link Manager installed is version 5.8 through 5.9
the Device Manager agent installed is version 5.0 through 5.1.03
When you use the Device Manager agent, upgrade IBM XL C/C++ Enterprise Edition V8 for AIX
Runtime to version 8.0.0.6 or later, or apply the APAR IY87291 patch.
Before you install the Device Manager agent in AIX, verify the IBM XL C/C++ Enterprise Edition V8
for AIX Runtime version by running # lslpp -L xlC.aix50.rte
AIX includes the Stack Execution Disable (SED) function that protects systems from attacks that use
a buffer overflow. If the SED mode is set to all, change the mode before installing the Device
Manager agent by running # sedmgr -m {select|off|setidfiles}
NOTE:
To return the SED mode to all after installing the Device Manager agent, exclude the Java process
used by the Device Manager agent from the SED protection targets. For details, see the
HP P9000
Command View Advanced Edition Suite Software Administrator Guide
.
Host prerequisites for Linux
Do not install Device Manager agents in Linux environments when symbolic links exist for the following
directories:
/opt
/opt/HDVM and its subdirectories
/var
/var/opt
/var/opt/HBaseAgent and its subdirectories
/var/opt/HDVM and its subdirectories
/var/tmp
Allowing communication with Linux firewalls
If you are installing on a Linux system that has a firewall, the firewall may prevent communication
between the Device Manager agent and the Device Manager server.
1. Disable iptables by running iptables stop on the Linux host.
2. Do one of the following:
Configure the host not to start iptables when Linux starts.
Configure iptables to release the port in use.
Host prerequisites for HP-UX
When installing the Device Manager agent in an HP-UX environment, you must consider the following:
Verify that the swagentd daemon is running.
If necessary, start the daemon process by executing:
/usr/sbin/swagentd
Installation and Configuration Guide 49