Centralized Monitoring

You can use Operations Sentinel running on the Enterprise or Department Operations Sentinel servers to view alerts for any anomalies in your Dorado system environment, instead of monitoring the Fabric Manager and OS 2200 Server Management Control (OS2200-SMC) user interfaces on separate displays.

Forwarding events from the Dorado local Operations Server (running Operations Sentinel Basic Edition) to the Enterprise or Department Operations Sentinel server is not required because the Operations Server and the Fabric Management Platform are both on the customer Operations LAN and can be monitored directly by the Enterprise or Department Operations Sentinel server. For more information refer to ClearPath Enterprise Servers Operations Sentinel Console Help (3850 8255).

Operations Sentinel Windows Resource Monitor monitors event IDs mentioned in the following table and reports to Operations Sentinel Server on Operations Server. It monitors the Windows Event Log for Call Home and SMC entries.

EventID

SMC Alert messages

1007

%1: The partition is being deactivated because SysCon is not active.

1009

%1: Partition state has changed to Stopped; not Startable.

1043

%1: Unable to recover this partition. SysCon is no longer running.

1060

%1: Failed to find an available boot path.

1066

%1: Connection or other failure with s-Par WS-Management interface.%n%2%3

1067

Standby host %1 is not responding. SMC will not be able to Switch Active Host.

10029

%1: Interface %2 network connection to BMC is not responding.

1092

Unable to access network. Network adapters or LAN may be defective.

1094

All access to the alternate Operations Server has been lost.

1099

The standby Operations Server is taking over as the master Operations Server.

1100

A heartbeat was lost between the standby Operations Server and the Master Operations Server.

1101

The standby Operations Server has lost connection to the master Operations Server.

1338

Server authentication certificate '%1' binding to Internet Information Service (IIS) Default Web Site's HTTPS protocol expires on %2 (%3 days, %4 hours). The OS 2200 Server Management Control (SMC) Web pages will become inaccessible when the certificate expires. Contact your system Administrator to get a new certificate installed.

1339

No server authentication certificate binding to Internet Information Service (IIS) Default Web Site's HTTPS protocol. You must have a certificate binding or OS 2200 Server Management Control (SMC) Web pages will not display. Contact your system Administrator to set up a certificate binding.

10001

%1: %2 : SAIL heartbeat lost heartbeat. Taking a Kernel dump.

10002

%1: %2 : SAIL heartbeat lost heartbeat. Rebooting SAIL.

10003

%1: %2 : SAIL heartbeat lost heartbeat. Stopping SAIL.

10004

%1: %2 : Sail heartbeat lost heartbeat.

10006

%1: The heartbeat between the host OS and the SMC software has been lost. This may mean that the host OS is no longer executing. The selected heartbeat attributes will be used to determine a course of action.

10008

%1: The 2200 emulation environment has experienced a problem. Initiating a dump of SysCon.

10019

%1: The partition is being deactivated because SysCon has aborted.

10020

%1: The partition has stopped due to an IAR Halt. IAR Code 1 is %2.

10021

%1: Interface %2 network connection %3 is not responding.

10024

%1: Connection or other failure with s-Par WS-Management interface.%n%2%3

10031

%1: Maximum number of reboots exceeded.

10036

%1: Attempt to connect to SysCon failed. SysCon is no longer running.

1097

Attempt to send heartbeat to standby operations server failed.

10037

%1: SysCon is in the process taking a core dump and terminating.

10046

%1: A problem has been experienced stopping the OS 2200 partition. Initiating a dump of SysCon.

10047

%1: Initiating a Kernel Crash Dump based upon the specified IAR Halt SCF Action code indicating one is needed for diagnostics.

101

Critical Call Home event.

102

Error Call Home event.

103

Warning Call Home event.