HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

As the failure occurs, the following error may be seen in the HP SIM log mxdomainmgr.0.log:
9/13/11 4:26:58 PM An error occurred during a workload repository
operation. java.rmi.ConnectIOException: Exception creating connection
to: CPVC-MTRX01.support.local; nested exception is:
java.net.SocketException: No buffer space available (maximum connections
reached?): connect (4 occurrences)
Suggested actions
Reboot the CMS. Microsoft has released a Hot Fix that prevents the error and messages from
occurring while attempting to open a new socket connection. See the Knowledge Base Article
2577795, Kernel sockets leak on a multiprocessor computer that is running Windows Server 2008
R2 or Windows 7 at the following website:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2577795
The Hot Fix that corrects the issue is included in the article with the process to apply the Hot Fix:
For more information, see Customer Advisory c03026061, HP Insight Dynamics - The HP Insight
Dynamics Fails Due to “Socket Exception No Buffer Space Available Error” When Installed on HP
ProLiant Servers Running Windows Server 2008 R2 or Windows Server 2008 R2 SP1 at the
following website:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03026061
Server blade serial number is not added on ESX or Hyper-V managed nodes
Issue
After HP SIM discovery, the blade's serial number is not added on the VMware ESX or Hyper-V
nodes.
Possible cause
HP SIM does not have the enclosure and blade bay information to associate it to ESX or Hyper-V
nodes.
Suggested action
1. Discover the enclosure which is supporting the blade.
2. After discovery, go to HP SIM / All systems page and check if the bay was associated correctly.
3. If the problem persists, select the blade which does not have the serial number and start an
identify request. From HP SIM, select Options→Identify Systems.
Insight Control virtual machine management registration for ESX or Hyper-V nodes fail
Issue
Insight Control virtual machine management registration for ESX or Hyper-V nodes fail.
Possible cause
• For ESX, VMware vCenter settings are not configured in HP SIM.
• For Hyper-V, WMI proxy services are not running on Hyper-V.
Troubleshooting procedures 143