VCRM binding to wrong IP address

[Glen Nason]

I have installed HP SIM on a server with multiple IP addresses on one NIC, let's call them ServernameA and B.

I login to ServernameA to use HP SIM and everything is functional except VCRM -- for some reason VCRM has attached itself to ServernameB.

In HP SIM on ServernameA, it does not recognize any VCRM on the network. Through using ActivePorts I discovered that VCRM service ports (2301, 2381) are listening on ServernameB's IP address.

When I configure the Version Control Agents on clients to connect to ServernameA, they cannot find it because it is binded to ServernameB.

I have tried rerunning Discovery and System Identification, but ServernameB's IP is already detected under ServernameA and it will not create a server entry for ServernameB.

I want to change the binding for VCRM so it is accessbile on ServernameA like everything else in HP SIM.

How to fix?

[Rich Purvis · Accepted solution]

What version of the System Mangement Homepage do you have runnning? This sounds like an IP binding issue fixed in the latest release, which can be found here:
http://h18023.www1.hp.com/support/files/server/us/download/23560.html

-Rich

[Glen Nason]

It worked -- Thanks.