Noticed in Virtual Center that 3 of 4 ESX hosts in a cluster were reporting alarams for health sensors. Closer insepction shows they were all getting whacky measurements for the 6  temperature sensors it is able to see from IPMI. They were reproting results like 0 degrees and -108 degrees and 115 degrees, whereas the working server is reporting 38 degrees, 40 degrees, etc.

Logged on to the System Management Homepage (i.e. the Linux/ESX HP Insight Agents are installed on these servers) and for the ones reporting broken results in VC, the temperature and fan information states were all Unknown. Looks like both Virtual Center and the HP agents are getting bad information from the hardware.

SSH’d to each ESX host and restarted SNMP and the HP agents:

service snmpd stop
service hpasm stop
service snmpd start
service hpasm start


The service startup process should be all green and if so, just reset the sensors in Virtual Centre and refresh HP SMH, everything should now be happy.

Access to the CRS Supervisor Desktop application is not managed by proxy to CUCM users. Instead, users are managed by Cisco Desktop Administrator which is installed on the server. So if a password reset is required, this is where it’s done.

Open the Administrator application, expand the Call Center icon, expand Supervisors. Locate the user and click Properties. Enter the new password.

If the user is not listed, it means they haven’t been as a Supervisor for any CSQ in the administration web interface. Open the web interface (should be http://<server>/appadmin), log in with and Administrator user (e.g. crsadmin) and go to Tools -> User Management -> Supervisor. Add the user.

To assign the new user as a Supervisor of a Team, go to Subsystems -> RmCm -> Teams. Select the team you are after. You can have only one Primary Supervisor but multiple Secondary Supervisors. Teams can be assigned to more than one CSQ.

Have been trying to get ESXi 3.5 (U3 or U4) installed on a HP ProLiant DL160 G5 with P400 storage controller. Read through this and some other information:

http://communities.vmware.com/message/1186946 [communities.vmware.com]

Following changes made to the server:

• Enabled Intel Virtualization in the RBSU CPU setup
• Set the SATA HDD mode to AHCI

Installation is fine (using the HP Installable version of ESXi 3.5 U4), the server boots, stays up for around 2 minutes then PSOD’s with error type 14. Confirmed that ESXi is able to monitor the health of the storage controller (P400) and the disks which is a good start.

Reinstalled using the generic ESXi 3.5 U4 installable version, works perfect. Seems the HP management agents don’t play nice with certain components of the DL160 hardware (same story here [communities.vmware.com]). Without the HP agents, VI Client can no longer monitor the health of the P400 storage controller or the disks attached to it. Server can be added to HP SIM v5.03 and the hardware model and ESXi version are detected correctly as are the virtual machines running on the host.

So, it is for good reason that the DL160 is not on VMware’s HCL [vmare.com]

Music on hold multicast from a router’s flash will not play an audio file unless that audio file exists prior to the multicast moh command being issued:

call-manager-fallback
 multicast moh ...

The command needs to be re-entered or the router reloaded before the audio will be streamed multicast.