Install HP SIM/SNMP Agent on Citrix XenServer 6

1. Go to and support & drivers. Search for your hardwares drivers, for example HP ProLiant DL380 G7. When selecting operating system select Citrix XenServer 6.x. Dowload “HP SNMP Agents for Citrix XenServer “. The file that you download is named hp-agents-xs.iso.

2. Upload hp-agents-xs.iso to your XenServer host. For example via FileZilla:
Address: XenServers IP-address och hostname.
Username: root
Password: <root password>
Port: 22

Create a folder named iso in /. Upload hp-agents-xs.iso to the iso folder.

3. Mount the iso image on the XenServer host.
# mkdir -p /mnt/iso
# mount -o loop /iso/hp-agents-xs.iso /mnt/iso

4. Install the HP SNMP Agent n the XenServer host.
# cd /mnt/iso
# ./

5. Unmount the iso image on the XenServer host.
# cd /
# umount /mnt/iso

6. Delete the iso image.
# rm -rf /iso

7. Delelte the iso mount point.
# rm -rf /mnt/iso

8. Logon to HP SIM and discover the IP-address or hostname of the XenServer host.





One response to “Install HP SIM/SNMP Agent on Citrix XenServer 6”

  1. mark fischer Avatar

    would you be so kind as to amend you article to contain some updated information.
    Wiht the release of XenServer 6.0.2 it has a a security change bug and requires that the follwing be done to enable the HP SIM snmp and Agents V9.0 to install correctly.
    1. In a XenServer Pool the HP agents MUST be installed on the XenServer pool master before the XenServer pool slaves. Thi is due to the XenServer pool master in 6.0.2 is now replicating /ect/passwd file to all XenServer pool slaves.

    Thre is a bug in the ISO for 6.0.2 that changes the security on the root folder, this prevents the HP SIM SNMP agents to run the HP System Management Homepage. to fix this you need to log in to the console as root and excute the command CHMOD 755 /.

    The folloing is the extract from the HP case number raised on this issue and the response form Citrix Support for the Poll Master Pasword issue.

    HP Case Number 4640135534-463
    From: Singh, Deepali (CPR&Q GCC – ISS/Software) []
    Sent: Tue 29/05/2012 3:22 PM
    To: Mark Fischer
    Subject: RE: 4640135534-463

    Hi Mark,

    I have been in contact with the XenServer Engineer and he has advised that the permission on “/” can be changed to 755 without any detrimental effects.

    As it turns out it is supposed to be 755 however the XenServer 6.0.2 hotfix 002 changed the permission to 700. A minor code update to rectify this will most likely be included in the next hotfix release.

    Kind regards,


    From: Mark Fischer []
    Sent: Tuesday, June 05, 2012 3:32 AM
    To: Pullaganti, Sudhakar (CPR&Q GCC – ISS/Software); Singh, Deepali (CPR&Q GCC – ISS/Software)
    Subject: Re: HP Case Number 4640135534-463

    Update from Citrix appears to have resolved the issue.
    The pool master is over writing the pool slaves /etc/passwd file.
    I have installed the Agents on the Pool Master and will commence on the pool slaves.

    I would strongly recommend that HP release a urgent Tech article to advise end users of these issues.

    1. That for the agents to be installed on Citrix Xenserver 6.0.2 that the root folder needs to have its security changed by chmod 755 /

    2. That for the agents to be installed on Citrix Xenserver 6.0.2 the first installation has to be on the pool master, this is to ensure that the account required to run the agents is deployed to the other pool slaves via the Citrix Xenserver 6.0.2 pool master passwd file replication process.

    The following is a Update and correction from CTX Tech Support following their repro testing.

    I’ve tried reproducing the “does passwd get copied from master when joining a pool or rebooting a slave?” – and I must correct myself – the passwd file does get overwritten with the one from the pool master.
    In addition, the password file will be resynchronised on the reboot of the slave as well.
    So if you are attempting to add user manually with useradd command, you need to start from the master.
    In fact, once you add the user to the master, you can then reboot the slave and the user will be present in the new passwd file.
    Kind regards,
    Mark Starikov
    Support Engineer

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.