Increasing the time-out for the hp sim connector, Re-installing the hp sim connector, Changed) – HP Storage Essentials Enterprise Edition Software User Manual
Page 727
HP Storage Essentials SRM 6.0 User Guide 689
1.
Enter the following at the command prompt, where mycomputer is the shortened DNS name of
the machine:
nslookup mycomputer
The fully qualified domain name and IP address is displayed, as shown in the following
example:
Server: server.yourcompany.net
Address: 192.168.135.52
Name: mycomputer.domain.my.net
Address: 192.92.12.131
2.
Open the following file in a text editor, such as Microsoft Notepad:
C:\windows\srmwiz.ini
3.
Assign the fully qualified domain name to the FQDN property in the srmwiz.ini file and save
the file.
4.
Do one of the following:
• Rerun the installation wizard (Start the Storage Essentials installation wizard (double-click
setup.exe in the srm directory or re-insert the Storage Essentials CD in the CD–ROM drive of
the Storage Essentials server)
• Run connector.exe.
Re-installing the HP SIM Connector
(If Your HP SIM User Name or Password is Incorrect or was Changed)
If you enter the credentials for the HP SIM server incorrectly, you must re-install the SIM Connector
component to provide the correct credentials:
1.
Put the Storage Essentials CD-ROM in the CD-ROM drive of the management server.
The Welcome screen is displayed. The installer determines that all components are installed on
the system and will go directly to the HP Systems Insight Manager Service Account Credentials
screen.
2.
Make your changes and click Next. The installer re-installs the HP SIM Connector.
Increasing the time-out for the HP SIM Connector
The HP SIM Connector times out if HP-SIM is not fully running in five minutes after system startup. HP
SIM may take longer than five minutes to start if HP-SIM has just been upgraded where there are
many events in the HP-SIM database, for example. You may increase the five minute time-out by
changing connector-time-out-minute in
%JBOSS4_DIST%\server\appiq\conf\hp-config.xml
on the management server: