Configure forwarding options for server-based flexible management


If you use server-based flexible management, the management server maintains queues of messages, message operations, and action responses to forward to other management servers. There is one queue for all management servers that support HTTPS communication. If you have older management servers that support only DCE communication, there is additional queue for each of these servers.

You can configure options for these queues using the Server Configuration dialog.

To configure forwarding options for server-based flexible management

  1. In the console tree, right-click Operations Manager, and then click ConfigurearrowServer.... The Server Configuration dialog appears.
  2. Click Namespaces, and then click Server-based Flexible Management.

  3. Select the Expert mode check box. The full list of values appears.
  4. Configure the queue sizes and retry intervals. The following table lists the values to configure.

    Value Description
    Forwarding queue size warning threshold When the size of a queue exceeds this threshold, the management server creates a warning event in the event log. Specify a warning threshold in megabytes. The default is 40 MB.
    Forwarding queue size maximum When the size of a queue exceeds this threshold, the management server creates an error event in the event log. The management server does not add to the queue until the queue size falls below the queue maximum setting. The destination management server or management servers for this queue do not receive messages, message operations, or action responses that occur while the queue size exceeds this threshold. Specify a queue size maximum in megabytes. The default is 50 MB.
    Forwarding retry interval This value specifies the number of seconds to wait before trying to reconnect to an unreachable management server. Specify an interval in seconds. The default is 60 seconds.
  5. Note NOTE:
    The management server creates entries in the event log that relate to queue sizes and unreachable management servers. You can monitor event logs on the management server with the self-manager policy VP_SM-Server_EventLogEntries.

  6. Optional. Configure the message operations that you want this management server to forward and accept. The following table lists the values to configure.

    Operations to be forwarded This setting configures which types of message operations to forward to other management servers. For example, you can configure the management server not to forward message acknowledgements. You configure this setting with a bit mask consisting of the possible values below:

    1 Acknowledge
    2 Unacknowledge
    4 Own
    8 Disown
    16 Severity change
    32 Message counter change
    64 Annotation change
    128 Text change
    256 Action response
    512 Action state change

    Add all the operations that you want the server to forward. The default is 1023, which means that the management server forwards all operations.

    Forwarded operations to be accepted This setting configures which types of message operations to accept from other management servers. For example, you can configure the management server not to accept message acknowledgements. You configure this setting with a bit mask consisting of the possible values below:

    1 Acknowledge
    2 Unacknowledge
    4 Own
    8 Disown
    16 Severity change
    32 Message counter change
    64 Annotation change
    128 Text change
    256 Action response
    512 Action state change

    Add all the operations that you want the server to accept. The default is 1023, which means that the management server accepts all operations.

  7. Click Apply.

Related Topics:

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.