A.05.70 HP Insight Remote Support Advanced Managed Systems Configuration Guide (October 2011, 5900-1726)

Managed Systems Configuration Guide
Chapter 11: Integrity Superdome 2 Server Configuration
list has been populated to use the WS-Man protocol that was discovered by HP SIM. The protocol
name identified here should also be defined on the WEBES Manage Protocol page. Only the Active
OA will be monitored by WEBES. Should the active OA fail, the subscription that WEBES
establishes to it will be passed to the standby OA as the failover occurs.
4. On the Managed Entity Properties page for the Active OA, verify WEBES populated the following
fields:
n System Subtype – Superdome 2 Onboard Administrator
n Verify entitlement values have been populated as were entered into HP SIM during prior steps.
5. If the System Subtype is incorrect, try rediscovering the OA in HP SIM. If the entitlement values are
not set or the System Subtype value is different, go back to HP SIM to correct them. If you manually
update these fields in WEBES your entry will be overwritten by the values WEBES extracts from the
HP SIM database the next time WEBES does a refresh.
Note: WEBES subscribes to the OA that is active at the time of HP SIM discovery and uses the
subscription to listen for events. If an OA failover occurs, WEBES continues to monitor the active
subscription once it is passed by the Active OA to the Standby OA while graphically continuing to
show that it is actively monitoring the previously configured Active OA (even though that OA has
failed).
However, if the subscription WEBES made to the OA is deleted, as may the case when a Superdome
2 firmware update is performed (the subscription is stored on the OA and may be deleted as part of the
firmware update process), then the subscriptions to the OA may need to be reestablished upon
completion of the firmware update. It is recommended that the rediscovery process be re-run in HP
SIM to recreate its event subscriptions to the OA, and upon completion of that process that the WS-
Man protocol should be de-configured from the WEBES Managed Entity page for that OA, that change
saved, and then re-added and saved to force WEBES to re-subscribe to the Active OA for event
monitoring.
Note: An SD2 32s configuration consists of two enclosures joined into a single server complex. Each
enclosure has a primary and a standby OA that manages and monitors that enclosure. Only one of the
two active OAs in the SD2 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 SD2 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(es), 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.
HP Insight Remote Support Advanced (A.05.70)Page 65 of 199