Tag Archives: Server Group;Ranking

ARSystem BMC Remedy

Disabling some options from the Configuration tab in Admin tool is failing

Problem

Any attempt to select or deselect the following options from Configuration tab in Admin tool is failing:

  • Disable Archive
  • Disable Admin Operations
  • Disable Escalations

The error message generated is:

“This configuration setting is not allowed when the server is a member of a server group : 142 (ARERR 3324).”

Solution

Reference configuration manual for ARServer for these three options:

“If the Server Groups check box is selected, this setting is ignored. Server groups can be configured in the AR System Server Group Operation Ranking form to make sure that only one server performs the operation.”

If the Server Group Member box on the Configuration tab in Admin tool is checked, any attempt to select or deselect operations controlled by Server Group configuration will generate ARERR 3324 error message:

“This configuration setting is not allowed when the server is a member of a server group : 142 (ARERR 3324).”

The operations on the Configuration tab in Admin tool which are controlled by Server Group configuration are:

  • Disable Archive
  • Disable Admin Operations
  • Disable Escalations

When a server is a member of a server group, the Configuration tab settings for these operations are “reporting only” information. Before the server group feature was added to ARServer, these settings on the Configuration tab controlled how the server behaved and still work the same way for non-server group environments.

In a server group environment, however, they are not read to determine the server’s behavior. Instead, they reflect the current conditions on the server when the server determines what should be enabled or disabled using the ranking information in the Server Group Operation Ranking form.

In a non-server group environment, selecting or deselecting one of these options from the Configuration tab in the Admin tool will add an entry to the ar.conf / ar.cfg file:

  • Disable-Admin-Ops: T (or) F
  • Disable-Escalations: T (or) F
  • Disable-Archive: T (or) F

At startup of a server in a non-server group environment, these entries in ar.conf / ar.cfg file are visible on the Configuration tab for each operation with either a check (when set to True) or blank (when set to False).

At startup of a server in a server group environment, these entries in ar.conf / ar.cfg file are not relevant.

The ranking information in the Server Group Operation Ranking form will be reflected on the Configuration tab for each operation with either a check (when this server is not primary server for the operation) or blank (when this server is primary server for the operation).

When a server group is configured, there will be five entries to the ar.conf file for operations corresponding to entries in the Server Group Operation Ranking form and reflecting the ranking order for each server in server group for each operation.

The operation will be suspended (set to True ) for every server in the server group except for the server designated as primary for that operation:

  • Approval-Server-Suspended: T (or) F
  • Assignment-Engine-Suspended: T (or) F
  • Business-Rules-Engine-Suspended: T (or) F
  • CMDB-Service-Suspended: T (or) F
  • Reconciliation-Engine-Suspended: T (or) F

At startup the Email Engine and/or Flashboards engine will read the ar.conf / ar.cfg file and know whether it should start in suspended mode (set to True).

The Email Engine and Flashboards are different than the other managed server group operations in that they do not read the server’s configuration file for startup status. At startup, the Email Engine and Flashboards will send an ARGetServerInfo() API call to the server to determine their status.

The startup will be in suspended mode if the ARServer is not primary for that operation. If there is a change in status after startup, the ARServer signals them by running a Java agent program and tell it to suspend or resume operations:

  • EmailAdminAgent.jar and FlashboardAgent.jar.

There will be no status value in any configuration file these two operations for either ARServer or the Email Engine or Flashboard configuration files. Instead, the state is handled with real-time checks and signals.

 

7.1.x 7.6.04 ARSystem

Email Failover in a Server Group Environment

Problem

Email failover testing in a Server Group environment – When we shutdown the email engine on the primary server the server designated as backup didn’t detect that the email engine failed.

Solution

The detection process for any of the ranked services defined in the AR System Server Group Operation Ranking form is based on whether or not the arserver has died.  So to test the failover of the email server you must stop the arserver process also.

Another aspect to the failover scenario for email is that the email engine needs to be running on all servers in the server group.  When the Email Engine starts up, it finds out from arserver whether or not it should be active or suspended.  If a server detects that it should now take over email duties, it simply sends an RMI request (Remote Method Invocation) to the Email Engine to tell it to change state from Suspended to Started.