Server Management - Systems Insight Manager
1833776 Members
2260 Online
110063 Solutions
New Discussion

Re: SIM C04.00.00 CMS Doesn't trust itself???

 
Gil Gomes
New Member

SIM C04.00.00 CMS Doesn't trust itself???

I've been through many versions of HP TopTools as well as Compaq Insight Manager 7 SP2. I'm now attempting to get the new SIM up and running and have had much more enjoyable times in my dentist's chair...

I have a number of servers on this network and now find that I need to install OpenSSH in order to properly use all of the functionality of this product. (This, of course, takes a reboot...) Anyhoo...

I've installed OpenSSH on a 2003 client and a 2000 client. We're in the middle of seguing into Active Directory and currently have two domains... The 2003 box is an AD server on the new domain (leachandgarner.net) The 2000 box is an app server on the old domain (leach).
CMS is running on an XP Pro box.

One problem I'm having pertains to VCR. No matter which box I look at, including the CMS, it tells me it isn't trusted. I can find no detail in any event log... It's odd that the OpenSSH install went through without an issue.

I also have a question pertaining to Automatic event handling. I assume this needs OpenSSH running properly in order to function correctly. I'm seeing all kinds of flakey behaviour at this point. If I drop the 2000 box it sees it and reacts accordingly. If I unplug one of the NICS on the 2003 box... Nada...

These may be stupid questions... and if so... please humor me. I'm a little burnt out on this product already. Actually I'm a little burnt out on HP software in general... (urp!)

Thanx...
-Gil Gomes
Manager of Network Operations
Leach & Garner Company


6 REPLIES 6
Jadrice Toussaint
Honored Contributor

Re: SIM C04.00.00 CMS Doesn't trust itself???

Hi -

The trust relationship issue has nothing to do with openssh. Login to each client management console or perform this via a template. http://servername:2301 then click on the settings tab then options. Go down to trust mode. This is where you need to check your trust relationship between the clients and the SIM server. if you do a trust by name, make sure you enter the FQDN of the SIM server in other words, blah.blah.com.

As far as openssh, it is only necessary to install openssh on managed clients if the SIM server is going to execute remote commands on them.
Joseph Madden
Regular Advisor

Re: SIM C04.00.00 CMS Doesn't trust itself???

Jadrice,

I must be blind, but when I go to http://myserver:2301 - I don't see the 'settings' tab you refer to. I get a pop-up message that gives me a 'security alert' pop-up. I can view the certificate - but there again I don't see either a 'settings' tab or anything referring to trust mode?

I would appreciate any insight on this :)

Thanks
Joe
David Claypool
Honored Contributor

Re: SIM C04.00.00 CMS Doesn't trust itself???

The first piece of info that will probably help is how OpenSSH is used. Its presence on the central management server (CMS) is for the express purpose of running custom commands. This is the equivalent of the IM7 feature called "Application Launch." hpSIM holds a key to call OpenSSH on the same box that lets it execute commands at the command line.

On systems other than the CMS, OpenSSH is used to implement the distributed task functionality by which a command is not executed at the CMS but at the remote node. Somewhat confusing, this is what is used by the Tools-->Command Line Tools-->Windows commands to run commands remotely.

OpenSSH does not have to be present on any system other than the CMS to provide all of the functionality present in IM7.

The trust method used by the Insight agents and VCRM is a completely different mechanism and can be based on Trust All, Trust by Name or Trust by Certificate. In the past, when IM7 was installed, it by default installed the agents and VCRM on the same station and synchronized the certificate automatically. Unfortunately, this is not the case with hpSIM. When it lands the VCRM, it is an unconfigured (read no trust relationship or password configured) component. If it is being added to a system with Insight agents already there, it won't overwrite the settings and will be able to be configured post-install. As you installed on an XP Pro system, the Insight agents werent' there and so you have an "unusable" VCRM until the component is configured and re-installed.
Joseph Madden
Regular Advisor

Re: SIM C04.00.00 CMS Doesn't trust itself???

David,

I get the OpenSSh thing - and am through the that.

I am still missing a couple of your other points - but first of all my environment:

I installed HPSIM on a w2k server with sql server 2000 - not XP Pro

I keep reading about setting trust level to 'Trust All' etc - but can't see in the HPSIM app where I set that - the way I read your message it sounds like I need to set that at the agent level - but don't see any 'agent gui' that has those type of settings - I have found HP Management Agents GUI in the control panel - but that doesn't contain it - so I must be really not seeing something?

Thank you for response,

Joe
Joseph Madden
Regular Advisor

Re: SIM C04.00.00 CMS Doesn't trust itself???

OK David,

I am moving forward, 'in' management agent UI, and see the settings/trust things you are referencing - I need to finish reading the trust documentation.

But I appreciate your help.

Thanks
Joe
David Claypool
Honored Contributor

Re: SIM C04.00.00 CMS Doesn't trust itself???

Follow-up on setting VCRM login passwords on an XP Pro box (or anything that is non-ProLiant)...

The VCRM 'smart component,' CP003929.EXE, unfortunately appears to not be as smart as some other components. It can't be pre-configured with trust relationship and passwords.

If you have installed hpSIM on a non-ProLiant and wish to have the VCRM resident on the same system, you need to install (or re-install) VCRM using the following steps:

1. Execute CP003929.EXE and at the first dialog box, DON'T choose [Install], choose [Extract]
2. Once you have extracted to a directory (the same or a different one), go to that directory and execute CPQSETUP.EXE. Choose the [Install] button at this point.
3. Answer the prompts for repository directory and automatic updates. The third option box that you get to will be to set the passwords for Administrator, Operator and Other.
4. After that, you will be prompted for the trust method and you can choose Certificate, Name or All. On the subsequent screen you will be able to supply the certificate or name of the system to trust (nothing is required for Trust All)