InfoScale™ Operations Manager 9.0 Installation and Configuration Guide
- Section I. Installing and configuring Arctera InfoScale Operations Manager
- Planning your Arctera InfoScale Operations Manager installation
- Downloading Arctera InfoScale Operations Manager 9.0
- Typical Arctera InfoScale Operations Manager deployment configuration
- System requirements
- Installing, upgrading, and uninstalling Arctera InfoScale Operations Manager
- About installing Management Server
- About installing managed host
- About upgrading the Management Server
- About backing up and restoring Arctera InfoScale Operations Manager data
- About upgrading managed hosts to Arctera InfoScale Operations Manager 9.0
- Configuring Arctera InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring an existing Arctera InfoScale Operations Manager installation in high availability environment
- Configuring a new Arctera InfoScale Operations Manager installation in high availability environment
- Configuring Management Server in one-to-one DR environment
- Configuring Arctera InfoScale Operations Manager in high availability and disaster recovery environment
- About upgrading the high availability configurations
- About upgrading the high availability and disaster recovery configurations
- Configuring the high availability feature in Arctera InfoScale Operations Manager
- Installing and uninstalling Arctera InfoScale Operations Manager add-ons
- Uploading a Arctera InfoScale Operations Manager add-on to the repository
- Installing a Arctera InfoScale Operations Manager add-on
- Uninstalling a Arctera InfoScale Operations Manager add-on
- Removing a Arctera InfoScale Operations Manager add-on from the repository
- Canceling deployment request for a Arctera InfoScale Operations Manager add-on
- Installing a Arctera InfoScale Operations Manager add-on on a specific managed host
- Uninstalling a Arctera InfoScale Operations Manager add-on from a specific managed host
- Planning your Arctera InfoScale Operations Manager installation
- Section II. Setting up the Management Server environment
- Basic Arctera InfoScale Operations Manager tasks
- Adding and managing hosts
- Overview of host discovery
- Overview of agentless discovery
- About installing OpenSSH on a UNIX host
- Adding the managed hosts to Management Server using an agent configuration
- Adding the managed hosts to Management Server using an agentless configuration
- Adding Agentless hosts to the Management Server using Profile
- Editing the agentless host configuration
- Setting up user access
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication on Management Server
- Configuring LDAP using CLI
- Setting up fault monitoring
- Creating rules in the Management Server perspective
- Editing rules in the Management Server perspective
- Deleting rules in the Management Server perspective
- Enabling rules in the Management Server perspective
- Disabling rules in the Management Server perspective
- Suppressing faults in the Management Server perspective
- Suppressing a fault definition in the Management Server perspective
- Setting up virtualization environment discovery
- Setting up near real-time discovery of VMware events
- Requirements for discovering the Solaris zones
- Adding a virtualization server
- Editing a virtualization discovery configuration
- Refreshing a virtualization discovery configuration
- Deploying hot fixes, packages, and patches
- Installing a Arctera InfoScale Operations Manager hot fix, package, or patch
- Configuring Management Server settings
- Configuring SNMP trap settings for alert notifications
- Setting up extended attributes
- Viewing information on the Management Server environment
- Appendix A. Troubleshooting
- Management Server (MS)
- Managed host (MH)
- Management Server (MS)
Migrating the managed hosts to 2048-bit certificate
You need to run the at_migration.pl
Perl script on Management Server to migrate the Management Server domain (all the managed hosts reporting to Management Server) to 2048-bit certificate.
In case any managed host is not reporting to Management Server or any managed host fails to migrate when the script is run, you need to manually migrate that particular host by running the script on the host.
Note:
All those managed hosts that fail to migrate after running the script, may not be able to communicate with Management server unless they are manually migrated to 2048-bit certificates.
To migrate the managed hosts to 2048-bit certificate
- On your Management Server, run the
at_migration.pl
Perl script.On Linux Management Server:
/opt/VRTSsfmh/util/at_migration.pl --migrate
On Windows Management Server:
C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe "C:\Program Files\Veritas\VRTSsfmh\util\at_migration.pl" --migrate
- The script displays the following information:
Number of managed hosts that have host package version 7.0 or later, and are reporting to Management Server.
Number of managed hosts that are not reachable from management Server.
Number of managed hosts that have host package version lower than 7.0.
You need to confirm if you want to continue with the migration, or you want to perform the migration only after updating the managed host packages or fixing the communication issue. Enter n to cancel the migration or y to continue with the migration process without fixing any of the above mentioned issues.
- Once the migration of eligible managed hosts is complete, verify the list of managed hosts that are not yet migrated to 2048-bit and are still on 1024-bit certificates.
On Linux Management Server:
/opt/VRTSsfmh/util/at_migration.pl --list_1024_hosts
On Windows Management Server:
C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe "C:\Program Files\Veritas\VRTSsfmh\util\at_migration.pl" --list_1024_hosts
- On the managed hosts that are still on 1024-bit, run the
at_migration.pl
script to manually migrate them to 2048-bit.On Linux/UNIX hosts:
/opt/VRTSsfmh/util/at_migration.pl --import_credentials --xml_filename=Path_to_xml_file --cs_hostname=ms_hostname --sfm_password=db_password
On Windows hosts:
C:\Program Files\Veritas\VRTSsfmh\bin\perl.exe "C:\Program Files\Veritas\VRTSsfmh\util\at_migration.pl" --import_credentials --xml_filename=Path_to_xml_file --cs_hostname=ms_hostname --sfm_password=db_password
where,
Path_to_xml_file is the path to the xml file that is generated when you run the
at_migration.pl
script on Management Server. Copy this file to the managed host where you need to run the script to manually migrate the host.ms_hostname is the hostname of Management Server. In case of HA environment, it should be IP address of Management Server.
db_password is the encrypted database password of Management Server. Run the following command to get this password:
On Linux Management Server:
/opt/VRTSsfmh/bin/xdbadm -g -u habdbsync -c /var/opt/VRTSsfmcs/conf
On Windows Management Server:
"C:\Program Files\Veritas\VRTSsfmh\bin\xdbadm.exe" -g -u habdbsync -c "c:\ProgramData\Symantec\VRTSsfmcs\conf"
Note:
Migration to 2048-bit certificates is not supported on a Windows Management Server that is configured in high availability environment.