CMS showing up with localhost adress ?

[Mikael Rönnbäck]

I've started running into a small problem as of SP5 for SIM, from time to time SIM detects itself not as the servers IP adress (143.x.x.x) but instead as 127.0.0.1 (i.e. localhost)

All other functions are working normally and a restart of the SIM service will get the correct adress back, meaning the 143.x.x.x adress will be first in the list if you look at the details on the server where the CMS runs, and 127.0.0.1 will be second/last.

Since a restart of the service solved that part at first I did not intend to bother about it however I do have another problem related to it that won't go away even with a restart: If you look at the views in SIM the VC Agent for the server where the CMS runs is also listed at adress 127.0.0.1
This is more annoying since it will then show up as not configured in SIM, whereas if you go directly to the servers homepage and from there access the VC Agent it works perfectly.

So it must be an error stored in the SIM database, but how can I correct it, any other server would just have been able to delete and re-discover but you're not allowed to delete the CMS so what other ways are there to fix this ?

[LukaS_9]

Hi,
I know you cannot delete the CMS and also its nPar and complex.
If you can, try to re-inizialize SIM, but all the SIM data will be lost (not VSE data):

1. mxstop
2. check mx processes (ps -ef|grep -i mx)
3. mxinitconfig -r
4. mxinitconfig -a
5. mxuser -lt (should return the list of SIM users...2/3 minutes)


If you don't want to loose SIM data, take a look of this doc:
http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_5_changing_the_SystemName.pdf

hope this can help
luca

[Mikael Rönnbäck]

Thanks for the though though I'd rather not loose all data. :)

I've already tried using the info in the PDF, and it works fine using the section regarding changing IP adress, and just update the CMS where IP=127.0.0.1 to the actual server IP. It requires a restart of SIM but then works fine.
Unfortunately not for long, I'm not sure what triggers it, if its a scheduled discovery or data collection but after 1-2 days of running SIM will once again return to using localhost/127.0.0.1 as its IP adress again. So no luck there.

[Aravindh Rajaram]

Make sure you dont have any hosts file entry that resolves back your CMS host name to 127.0.0.1. Also, do you have multiple NIC's on the server that hosts SIM?

[Mikael Rönnbäck]

Well, the default hosts file on Windows always contains the entry

127.0.0.1 localhost

as far as I know, apart from that there's nothing in it and the server only has one single NIC, although the NIC has two IP adresses (none of which is 127.0.0.1)

[Albert Austin]

Hi,

Just wanted to confirm that I too am facing this exact same issue you are facing. Anybody got any solution?

Albert

[Mikael Rönnbäck]

So far I've come up with no answers, but I'll update this thread if I get any answers outside the forum.

[Charles Greck]

I had a similar behavior and solved the problem by reconfiguring The Version Control Repository Trusted mode in HP SIM.

Option- Version Control Repository - Configure - Trusted mode

[Mikael Rönnbäck]

Hmm, it's certainly worth a try, what did you choose for configuration, I'm currently at trust by name, should I maybe change to trust by cert ?

[Mikael Rönnbäck]

Thank you so much ! Finally it is working again, I changed the trust mode from Trust by Name to Trust by Cert, then did a data collection in SIM. And then the CMS finds itself as the proper IP instead of the localhost adress, even though the data collection caused a crasch in SIM and after a service restart SIM seems to be rather slower than before, but at least it works so its a step in the right direction.