A.05.80 HP Insight Remote Support Advanced Managed Systems Configuration Guide (June 2013)

Managed Systems Configuration Guide
Chapter 11: Integrity Superdome 2 Server Configuration
Only one of the two active OAs in the Superdome 2 32s complex is the Monarch OA for the complex,
and only it generates the WS-Man event indications produced by the Error Analysis Engine. As is the
case with Superdome 2 16s complex configurations, WEBES will only subscribe to the complex
Monarch OA for WS-Man event indications and WEBES will only display the Monarch OA on its
Managed Entity page.
Important: WEBES uses the fully qualified domain name of the CMS server in the WS-Man
subscriptions it creates on the Superdome 2 OA. If the OA network interface is not configured with the
DNS server address, the OA cannot perform the DNS lookup to enable it to send the WS-Man
indications to WEBES when an event occurs. Despite WEBES being properly configured on the
CMS, WEBES will not be able to receive and process WS-Man indications from the OA. To enable a
Standby OA to continue send indications to WEBES across its WS-Man subscription after a failover
has occurred, it too must have all its network values including DNS configured.
Therefore, when configuring the Superdome 2 OA for monitoring by Insight Remote Support
Advanced, both the active and standby OA’s network settings should be verified to ensure all values
are correctly populated including the IP addresses for the DNS servers.
Generating Test Events
Superdome 2 Firmware version 2.2.27 or later supports the capability for an administrator to connect to the
OA and generate a WS-Man test indication. Use the following procedure to generate a WS-Man test
indication:
1. Telnet or SSH to the OA CLI interface and log on as administrator.
2. Enter the test wsman command.
HP Insight Remote Support Advanced (A.05.80)Page 67 of 204