HP Matrix Operating Environment 7.3 Update 1 Release Notes

a. Use the Systems Insight Manager menu selection Options→Discovery..., or
b. Use the Systems Insight Manager command: mxnode -a <ip-address>
-w
where <ip-address> is the IP address that was assigned to the Integrity blade
after provisioning.
Add the root login of the Integrity blade using the Systems Insight Manager
menu selection Options→Security→Credentials→System Credentials....
3. Set up an SSH connection between the CMS and the Integrity blade by entering
the command: mxagentconfig -a -n <ip-address> -u root -p <root
password>
4. If the IP address was discovered on the primary CMS in a federated CMS
environment (in step 2 above), manually delete the managed node.
Use the Systems Insight Manager command: mxnode -r <ip-address>
Suggested action
If you did not perform the preceding steps before you started a delete request for the
Integrity service, the automatic delete service will not succeed completely. In that case,
you must clean up the logical server associated with the Integrity blade and manually
erase the disk. The logical server should be in an operable state.
1. Power on the server blade. (The blade was powered off when delete service request
completed or failed.)
2. Perform steps 2 and 3 in the preceding section, if you did not do so before starting
the delete service request.
3. To erase the disk, enter the following command from the CMS where the discovery
was executed (in step 2 in the preceding section):
mxexec -t "Ignite Erase Disks" -n <ip-address>
4. If the IP address was discovered on the primary CMS in a federated CMS
environment (in step 2 in the preceding section), manually delete the Systems Insight
Manager node.
Use the Systems Insight Manager command: mxnode -r <ip-address>
Service creation fails for physical requests when Windows Server OS is selected
Matrix OE infrastructure orchestration service creation fails when a physical template
with Windows Server OS is selected. This failure occurs when infrastructure orchestration
times out waiting for Insight Control server deployment to complete installation of Insight
Management Agents on the target server.
Suggested action
When a request fails, infrastructure orchestration automatically retries the request and
a new server is provisioned with the requested service. The original server is moved to
the maintenance pool and can be cleaned and moved back to a valid server pool. If
the failure is observed frequently, the following steps can be followed to disable the
installation of Insight Management WBEM providers. Insight Management SNMP agents
continue to provide management capabilities when WBEM providers are not installed.
1. Edit the install.cmd file, found under the <Insight Software
installation>\rdp\deployment server\hpfeatures\hpagents-ws\
components folder.
2. Remove the following two lines:
call :installsc wbem%PROCESSOR_ARCHITECTURE%
if %cpresult% geq 1 set /a cpresults=cpresults+1
31