HP Systems Insight Manager - Manual (Page 141)

The message /tmp/Acmd42947.bat[26]: /usr/dt/bin/dtterm: not found might appear when
running the following tools on HP-UX 11.31:
•
Retrieve Bastille Configuration file
•
Deploy Bastille Configuration
•
Consolidated Logging Wizard
•
Configuration Synchronization Wizard
Solution: To eliminate this problem:
Procedure B-16 Issue when running tools on HP-UX 11.31
1. Remove the above tools using the CLI command mxtool -r -t <tool name>.
2. Edit the tool definition XML files, replacing instances of dtterm and hpterm with xterm. The
above-mentioned tools can be found in the following TDef files:
security_patch_check.xml
clog_windows.xml
3. Add the tools again using mxtool -a -f <TDef file name>
4. Run the tool.
-------------------------------------------------------------
If a user is created with the operator template, then the user is automatically given authorizations to run any
CMS tool created with the Run as option set to root/Administrator.
Solution: To avoid granting users access to CMS tools, when creating new users, the operator template must
not be used and authorization must be configured separately. Note that only Systems Insight Manager
administrators can create CMS tools.
Upgrade
If you are upgrading to Systems Insight Manager 5.3 on Windows 2008 64-bit, first verify that OpenSSH
3.7.1 is not stuck in a
starting state. If it is, select End Process for the cygrunsrv.exe process and any
sshd.exe processes using the Windows Task Manager.
-------------------------------------------------------------
If Systems Insight Manager is installed on a Windows XP system with MSDE as the database, you must
manually upgrade MSDE to SQL Server 2005 to upgrade the Windows XP system to Windows Vista.
-------------------------------------------------------------
If you upgrade to Windows Vista on a Systems Insight Manager server running Windows XP, you might no
longer be able to browse into Systems Insight Manager. HP recommends turning off the Windows Vista User
Account Control features, and you might/ need to change the privileges of the SIMinstalldir\config
directory to get Systems Insight Manager running again.
UUID
All server hardware has what is called a UUID available to the operating system through the ROM BIOS.
This UUID is use to uniquely identify the hardware regardless of the operating system running on it. While
there is a standard way to decode and format/display this value, not all operating system vendors have
complied with that standard. For software that did not follow the standard, Systems Insight Manager converts
this value and displays it in the standard way. This can result in some differences if the UUID is viewed
through a given operating system tool such as dmidecode.
The SMBIOS stores the 16 bytes of System UUID as:
00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
Dmidecode displays:
00010203-0405-0607-0809-101112131415
UniqueIdentifier in SIM
03020100-0504-0706-0809-101112131415
Virtual identifiers
A new feature of virtual connect is to enable server profiles to have virtual identifiers, such as serial numbers
and unique identifiers. These identifiers then move with the profile across server hardware. There are a
Upgrade 141