HP Systems Insight Manager 7.0 Command Line Guide
HP Systems Insight Manager 7.0 Command Line Guide
HP Systems Insight Manager 7.0 Command Line Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Prerequisites<br />
Return value<br />
1. You must be a member of the local Windows Administrators group.<br />
2. The server has <strong>HP</strong> <strong>Insight</strong> Control Suite 6.0 or later installed, which includes <strong>HP</strong> SIM 6.0 or<br />
later. All <strong>HP</strong> <strong>Insight</strong> Control software that were installed on source server must be installed on<br />
target server as well.<br />
3. Stop the <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> service and all other <strong>HP</strong> <strong>Insight</strong> Control software before<br />
running import function.<br />
4. The CMS must be a clean installation and have no prior configurations.<br />
5. All OS and database-level user credentials on source CMS must be created on target CMS.<br />
6. See “SQL Server database settings” for more information if a remote database is used for<br />
import.<br />
IMPORTANT: This tool truncates all data from the concerned databases before it actually imports<br />
the data. <strong>HP</strong> recommends that you take a snapshot of all databases before proceeding with import.<br />
The snapshot can be taken in the following means - by running mxexport on the server, on any<br />
user specific database backup method. If import fails. the database can be recovered from the<br />
snapshot.<br />
No return value.<br />
Note: If one <strong>HP</strong> <strong>Insight</strong> Control software fails during import, the entire import function fails.<br />
Supported platforms<br />
All versions of <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> supported Windows operating systems.<br />
All versions of <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> supported SQL server local or remote database.<br />
Post-migration steps<br />
Examples<br />
1. <strong>HP</strong> recommends running the Configure or Repair Agent settings on the target CMS against<br />
the discovered systems. The options chosen should include to reset the trap, indication<br />
destinations as well as reconfigure any certificates used by the System Management<br />
Homepage,iLO or Onboard Administrator for Single sign-on. See “Configure and repair<br />
agents” for more details.<br />
2. After migrating to <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> 6.0, sign in to <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong>, and run<br />
the Daily System Identification task to ensure that all your associations are updated correctly.<br />
To run the daily identification task:<br />
1. Select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks page<br />
appears.<br />
2. Select the Daily Identification task.<br />
3. Click Run Now.<br />
Example 1<br />
To import data with out specifying a file name and password, enter<br />
mximport<br />
.<br />
Example 2<br />
To import data by specifying a password, enter<br />
50 <strong>Command</strong> descriptions
Change language