Hi,

I have been given the task of looking after HP SIM and all it entails and unfortunately our current environment had not been documented in the least. I was told to update our HP SIM setup from 7.1 to 7.2 so I built a test environment and this worked fine and for each option seemed at least to take the settings from the previous version of the component. However after all going well the upgrade bombed out at the VCRM update saying the service couldn’t be stopped correctly and installation had failed. I rebooted and did the VCRM part of the upgrade on its own.

This “seemed” to go OK but it didn’t seem to have stored the previous location of the repository (So I pointed to it) and it had not kept the versions of OS and schedule settings so I took a guess at what we would need on this. This then finished OK.

Today I checked a couple of remote servers that previously worked to list what new drivers are required and they are not showing up what is available and it says the VCRM is “busy”

When I look in my repository all the old files seem to be there (well it’s like 30GB but don’t know what it should be) but 12 hours on I am getting a stream of “MNF” files been written? Is it possible the repository is building itself from scratch? I am reading through the documentation but wondering if I should wait for these to stop first? Even though they are tiny these are currently writing at once a minute.

Any help appreciated!..

Can anybody confirm that the Disk FW level information is missing in VCA7.2.2.0  ???

When I de-install VCA 7.2.2.0 and i install VCA 7.2.0.0 then the disk fw info is visible again.

I would like to automatically feed some information from HP SIM (Serial Number, Server Name, IP Address) into an external system.

What options do I have for setting up automatic feeds with SIM?

Hi all, I used HPSIM to set up domain accounts on iLo logins and i wish to remove the local accounts that were previously created. Problem is i cant find anywhere on how to do this?

We have been informed by our information security team that our servers are failing scans due to "SSL Server Allows Anonymous Authentication Vulnerability". I have attempted to enable SSLv2 but each time I enter "smhconfig –s false", I receive an error stating "smhconfig: invalid options character: s". If I enter the long option "smhconfig --disable-sslv2=false", the error returned is "smhconfig: invalid option: --disable-sslv2=false".

I am running SMH 7.2, installed from SPP 2013.02.0.

Has anyone else run into this?

Thanks,

Neal

I need to move our implementation of SIM 7.2 to new hardware, and I can't find an easy method of doing this.  Is my only option to start from scratch?  I have thousands of servers being monitored, and I hate the idea of starting over.  There has to be some method of moving to new hardware, right?

Hey guys,

I'm running into some trouble when I want to use the "Configure or Repair Agents" function. When I run this function on a target server the task always fails with the error:

"No valid working sign-in credentials were found for the system in HP SIM. Check the Sign-in credentials by going to 'Options->Security->Credentials->System Credentials'."

In HP SIM I'm logged in as Administrator and when I configure the task I select "Use Sign-In credentials" to run the task. So I don't get the problem here...

Any suggestions?

Regards

simli27

+

System

-

Provider

[ Name]

sshd

-

EventID

0

[ Qualifiers]

0

Level

2

Task

0

Keywords

0x80000000000000

-

TimeCreated

[ SystemTime]

2013-12-02T10:00:37.000000000Z

EventRecordID

13672

Channel

Application

Computer

SIMSERVER.administration.eriecountygov.org

-

Security

[ UserID]

S-1-5-21-746137067-682003330-725345543-2653

-

EventData

sshd: PID 3392: error: Could not load host key: /etc/ssh_host_ecdsa_key

Hi all,

I am trying to install a SSL certificate on the HP SIM homepage... I have seen many forum posts around SSL certificates, but believe these relate to the SSH certificate that is paired with SIM and the management agents themselves.

I have an internal root certificate authority in my Active Directory environment. I just want to stop the SSL warning each time I browse to my SIM server (https://localhost:50000).

Can anyone guide me in the right location?

Regards,

Christian

Hi,

I have 17 D2D devices which I have been asked to monitor using HPSIM 7.2. They are 2502i's 2504i's 4324's and 4210's. I have added the MIB's I have created a new object type and followed all the documentation and during discovery all but 3 have shown correctly.

I am having an issue with the 4210 because HPSIM doesnt recognise the device type and I cannot find any MIBS for it or looking at the documentation I cant see what is required to get it to work. but also I have 2x 2504i's that dont work, now the MIBS say they are for 2504i's but when I log onto these they say they are HP StorageWorks D2D2504i - G02-E where all the other 2504i's say they are HP StorageWorks D2D2504i - G02 only. I cannot find out what the difference is between the G02 and the G02-E but that is what appears to be making insight not be able to tell what it is. All software versions are 2.2.18 and I have been told the same software source code was used on got versions of hardware with no issues seen.

Has anyone else had this issue? or could anyone else tell me something to try? I am using SNMP and SSH for discovery. and an example failure is below.

********* Significant issues and overall target discovery/identification
          status:
Major:    The system cannot be identified properly for HP SIM to manage;
          unable to get one or more of the following: model, serial number or
          unique identifier (UUID). For management processors, verify the
          system is running the latest firmware. For Linux based operating
          systems, you must have dmidecode installed, enable the
          PermitRootLogin and PasswordAuthentication in sshd, and use root
          sign-in credential. For HP-UX, verify the sign-in credential. For
          Windows, check if WMIMapper is configured correctly on the CMS and
          verify the sign-in credential.
Critical: The system(s) can not be identified by WBEM, SNMP or SSH

Thanks

Hi,

Ive just set up an HPSIM 7.2 console for windows servers and what I have found is when the system state of a device changes (Hard disk failure, network failure, Array battery etc) the all servers view changes under the HS column but that event doesnt show up in the System status uncleared events at the same time, so its very difficult for me to see at a glance any new events or failures in the console. I have 900 devices currently in there so its impossible to check each one every day to see if there has been a change or failure.

Can anyone tell me how I can rectify this? We had an old 6.3 console and this worked fine but not on the new one.

We do get status changes to the uncleared event status counts but they only seem to be system inaccessible and accessible messages and internal HP messages like failed login attempts or data collection timeouts.

Can anyone suggest anything to try and this makes a daily easy task quite difficult.

Thanks In Advance

Hi,

I am getting issue with HP SIM.
I am not able to get data from a server.

SMH is working fine on the server
SIM server name has been added in SNMP settings

Please find the below logs:

********* Significant issues and overall target discovery/identification
          status:
Major:    The system cannot be identified properly for HP SIM to manage;
          unable to get one or more of the following: model, serial number or
          unique identifier (UUID). For management processors, verify the
          system is running the latest firmware. For Linux based operating
          systems, you must have dmidecode installed, enable the
          PermitRootLogin and PasswordAuthentication in sshd, and use root
          sign-in credential. For HP-UX, verify the sign-in credential. For
          Windows, check if WMIMapper is configured correctly on the CMS and
          verify the sign-in credential.
Normal:   Identification status is only available for servers, workstations,
          or desktops, where monitoring is enabled.

********* Additional results (listed for information only):

        * Starting identification process...
        * Checking for known running web servers...
        * Checking for SNMP protocol support on system...
Normal:   The system did not respond to SNMP. Verify security settings and
          community strings in Options->Security->Credentials->System
          Credentials
        * Running HP ProLiant management agent identification...
Normal:   The system does not support SNMP.
        * Running SNMP base cluster identification using common cluster
          MIB...
Normal:   SNMP is not supported or globally disabled, skipping SNMP cluster
          identification.
        * Checking for WBEM protocol support on system...
Minor:    This system does not have any SMI-S CIMOMs installed. No storage
          systems will be found on this system.
Minor:    The Central Management System (CMS) cannot communicate with the
          CIMOM locally installed on the managed system using the WBEM
          protocol, Identification will try to identify Windows systems using
          the WMI Mapper as proxy; for Linux and HP-UX systems, check
          credentials by going to Options->Security->Credentials->System
          Credentials. For Linux systems also check if the HP WBEM provider
          is installed.
        * Running WBEM rules based identification...
Minor:    Identification cannot get computer system hardware data from the
          WBEM / WMI providers.
        * Running Virtual Machine (VM) Host (non HP Integrity VM Host)
          Identification...
Normal:   The system is not a VM Host (non HP Integrity VM Host), or WBEM
          credentials may not be specified so skipping VM Identification.
        * Running Storage identification...
        * Did not detect the WBEM protocol support on this system. SMI
          storage identification will be skipped.
        * Storage identification completed.
        * Running HP NetServer identification...
Normal:   The system does not support SNMP.
        * Running HP-UX SNMP identification...
Normal:   The system does not support SNMP.
        * Running OA Identifier which will discover systems in an enclosure
          if the automatic enclosure discovery option for OA is enabled...
Normal:   The system is not an Onboard Administrator, skipping automatic
          discovery of systems in the enclosure.
        * Running XMLReply Identifier which will discover systems in a
          rack/enclosure if the automatic discovery option for the container
          node is enabled...
        * Running iLO Identifier which will discover the server if the
          automatic server discovery option for iLO is enabled...
Minor:    The system responds to the HTTP request but cannot get the XML
          output. It is normal for servers not to get the XML data.
        * Running p-Class Identifier...
Normal:   The system is not a p-Class so skipping p-Class identification.
        * Running IPMI protocol identification...
Normal:   IPMI protocol not detected so skipping IPMI Identification.
        * Running SSH Protocol identification...
Minor:    The system(s) do not have Secure Shell (SSH) installed or it is not
          running on the managed system(s).
        * Running SSH Identification...
Normal:   SSH Protocol is not enabled so skipping SSH Identification.
        * Running WS-Man identification...
Minor:    The system did not respond to WS-Management (WS-Man) request.
        * Running Monarch OA Identification...
Normal:   The system is not a monarch OA so skipping monarch OA
          identification.
        * Checking for System Management Homepage and other HP web agents...
Normal:   The system is not a server, storage or desktop. Skipping the check
          for System Management Homepage.
        * Running HP Serviceguard Identification...
        * Running SNMP System Type manager ...
Normal:   The system does not support SNMP.
        * Running SNMP subtypes identification...
        * Resolving DNS names...
Normal:   The fully qualified domain name was successfully resolved for the
          system.
        * Checking if the Node is a Virtual Center...
Normal:   Skipping MxVirtualCenter Identifier.
        * Running Virtual Machine Management (VMM) Plug-in Identification...
        * Building system relationships...
Minor:    System Management Homepage (SMH) is not installed or is not
          responding on the system(s).
        * Running system Manage Communication diagnosis...
        * System identification finished on system.


Kindly Help.

Hi..  I hope someone can help me with this.. our HP Sim 7.2 on windows 2k8 R2  is running high on memory..

btw its on a VM  .. we allocated 8GB ram and it is currently consuming 7.5GB constantly...

DISK i/o is also very high... the machine is pretty much bogged down.. and when i log into the server everything is soo slow... just to open up any windows its very very sluggish...

anyone know why   MXDOMAINMGR is using about 5GB of ram

and  SQLSERVER process is consuming about 2GB of ram...

I am new at this so  I am trying to figure out whats causing these 2 process to eat up all the memory and causing the machine to also have high  Disk I/O

any help , pointers or advice on how to go about this would be greatly appreciated..

Thank you.

I needed to get access to the HP Power Manager but unfortunately, the password was lost and we did not wanted to reinstall the software because we were not sure, if the settings would be kept but we needed them for sure.

Here are the instructions on how to reset the HP Power Manager password and how to create a new administratior, if required.

Notes

Please back up the file you are asked to edit before saving it.

The instructions were created for Version 4.3 of the software. Others might work too.

Resetting to the default password

Follow these instructions, if you lost the password and need access to the software again.

1. Stop the HP Power Manager Service
2. Open C:\Program Files (x86)\HP\Power Manager\DevManBE.ini in a text editor, that works with linux linebreaks (notepad++ for example)
3. In the [User_admin] section, set Password to T4vup76t
4. Start the HP Power Manager Service
5. You can now log in using the default credentials (admin/admin)

Create a new administrator

Follow these instructions if you do not want to tamper with the default "admin" user.

1. Stop the HP Power Manager Service
2. Open C:\Program Files (x86)\HP\Power Manager\DevManBE.ini in a text editor, that works with linux linebreaks (notepad++ for example)
3. In the [Users] section, add the Line User_X=Y where X is an unused number from 1 to 9 and Y your new username.
   X should be the first unused number, do not make any gaps in the numbering. If you already edited the users once with the web interface, all values might already be present, in this case, choose an empty one to edit instead of adding a new one.
4. Add these 3 lines at the bottom of the file (set Y to the user name you have chosen in step 3):
   [User_Y]
   Password=T4vup76t
   Admin=1
5. Save the file and start the HP Power Manager Service.
6. Log in using the newly created user.

Hi all,

I am confusing how to install hp insight control power management on HPSIM:

+ Is hp insight control power management free?

+ where i can download hp insight control power management for LINUX, WINDOWS ( i only see for HPUX on software.hp.com website)?

+ How can integrate hp insight control power management into HPSIM?

Anyone could help me?

Many thanks,

nampnx

P.S. This thread has been moved from ITRC HP SIM Tools and Scripts Forum to ITRC HP Systems Insight Manager Forum. - Hp Forum Moderator

Hello,

This new fonctionnality (Microsoft Failover adapter) on 2008 microsoft servers gives a new IP in 169.254.XXX.XXX to any node servers and of course SIM gets this IP.

It's a pity because after the discover physical esxi and gather all my VM machines on this esxi, SIM tries to make a ping on 169.254.XXX => so he gets an error.

My fisrt idea was to short my network card as first one but it's seems not possible.

Also SIM get this IP only as primary IP : then no way to switch IP in system properties.

I guess some of you have already managed this problem that's why i am coming to you asking your help.

Thank you in advance for any answers or ideas.

Hello,

after upgrading three sim servers to the latest 7.2.2 also the VCRM was updated to this version.

The SIM servers are virtual machines with 16 GB memory and 4 cpu running on Windows 2008 R2 SP1.

Two are running with a local sql installation because of less clients.

One has a remote sql DB.

Now on all three servers we see extremly memory usage for the VCRM, which was not observed with the older version 7.2.0.

The memory usage goes up to 15 GB memory, in conjunction with the mxdoaminmgr with about 1,8 GB memory absolute slow down of the server.

We are receiving such events:

Log Name:      System

Source:        Microsoft-Windows-Resource-Exhaustion-Detector

Date:          09.12.2013 10:20:20

Event ID:      2004

Task Category: Resource Exhaustion Diagnosis Events

Level:         Warning

Keywords:      Events related to exhaustion of system commit limit (virtual memory).

User:          SYSTEM

Computer:      sim-server

Description:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: cpqsrhmo.exe (1228) consumed 15086669824 bytes, mxdomainmgr.exe (3084) consumed 1800044544 bytes, and mxdtf.exe (1500) consumed 219762688 bytes.

Because this behaviour is on three servers since the upgrade i fear we have a bug in the VCRM 7.2.2.

Restarting the VCRM takes also a tremendous time to finish.

What could be the reason for that?

(newbie question) Just need to clarify the support position.

Currently have the CMS at 7.2.0 and majority of agents at 6.3 (some lower level on older boxes tho).

Tracked down the support matrix;

http://h18006.www1.hp.com/products/servers/management/hpsim/supportmatrix.html

This lists the 6.3 versions as out of support as of '03/31/2013'

Does this mean that my 6.3 agents are out of support?

Or, as the CMS is 7.2, then they are support (providing they can communicate of course).

Thanks, Thomas

Hi guys,

I have got another question or problem.

During the validation process that the VCRM starts automatically the VCRM deletes some servers from its repository.

Example:

Before the validation there are 79 VCA's connected to the VCRM and after the validation finished there are only 50 VCA's connected to the VCRM.

There shouldn't be any problems with the VCA's itself but I don't know why VCRM disconnects them. Is this a known issue and can anyone provide me some solutions?

Many thanks!

Regards

simli27

I recently upgraded from SIM 7.1 to 7.2. Since then SIM cannot see the contents of the VCRM, so I cannot setup my baselines. When I go to Options-Software/Firmware-Version Control Repository. SIM sees the repository and shows that it is trusted, but I keep getting

"Error retrieving repository. Ensure the Version Control Repository Manager (VCRM) is installed and running. Be sure a trust relationship is established with the repository device. Finally, the VCRM may not respond if it is in the process of updating its catalog. In this case simply try again later"

I have been fighting with this for over a week and no changed.  I have deleted and reinstalled the certificate. Rebooted the server and still nothing. Both SIM and VCRM are on the same server, the server is physical and the OS is Win Server 2008R2

Any Help is appreciated!

Thanks