Viewing servers in Central Monitoring Administration

From the Servers drawer, you can see all the Child Servers that are registered with Central Monitoring Administration. For more information about how to register a child server, see Enabling and configuring Central Monitoring Administration.

A registered Child Server with associated Integration Services enables policy actions on the following components:

  • Connected BMC PATROL Agents with matching conditions
  • Monitor instances discovered by those agents
  • Devices monitored by those agents

To cross-launch the operator console for child servers from Central Monitoring Administration

  1. In the title bar of Central Monitoring Administration, click the down-arrow on Launch Infrastructure Management Server Operations Consolelaunchtochild.gif. 

    A list of child servers associated with the central server displays.

     

  2. Select the child server for which you want to launch the Operations Console. 

    The Operations Console launches in a separate window with the Events view displayed.

    Note

    If you block the HTTP port for the Child Server and try to cross-launch to same Child Server using Central Monitoring Administration, the cross launch does not work. Therefore, you need to re-register the Child Server for cross-launching.

To display the FQDN of the Child Servers

To display the FQDN in the cross-launch list of Child Servers, perform the following steps:

  1. In the <installation directory>\pw\custom\conf\pronet.conf file, add the following line:

    useFQDNForChildServer=true

  2. From Central Monitoring Administration, register the Child Server using the following command:

    pw cmadmin registerChildServer -ChildHost=<Child Server FQDN Hostname> -ChildUser=<childUser> -ChildPasswd=<childPassword> -force

If you have registered a Child Server using the FQDN, you can deregister it using the following command from Central Monitoring Administration:

pw cmadmin deregisterChildServer -ChildHost=<Child Server FQDN Hostname> -ChildUser=<childUser> -ChildPasswd=<childPassword>

You can use the pw cmadmin deregisterChildServer command to also deregister the Central Server. To deregister the Central Server, specify the FQDN host name, user name, and password of the Central Server.

To view details for registered Child Servers, Integration Service, and BMC PATROL Agents

  1. In the navigation pane of Central Monitoring Administration, select the Servers drawer to see the registered child servers.
  2. Select the Child Servers view to see the following details for each registered Child Server:
    • Host name
    • Platform
    • Infrastructure Management Server version
  3. Select a child server host name to see the following details for each BMC PATROL Agent:
    • Integration Service connected to the PATROL Agent along with the connection status. The tool tip on the Integration Service name displays the name of the Integration Service, Integration Service host name and the port.
    • PATROL Agents linked to the Integration Service along with the connection status. The tool tip on the PATROL Agent displays the agent host name and port.
    • Additional information ico_addinfo.png about the agent, like mark for delete ico_markForDel.gif, blackout ico_blackout.gif, and agents that are not policy manageable exclamation.png.  
    • Policy applied status on the agents, along with the tool tip that displays the applied policy names and time. See Identifying policy applied status.
    • Tag
    • IP address
    • Operating system
    • BMC PATROL Agent version
    • Tenant
    • Tools menu ico_single_wrench.gif for the BMC PATROL Agents. See Using the tools menu.

 

Note

If the IP address for PATROL Agent displays the loopback address of localhost, perform the following steps to display the actual IP address of the computer that has PATROL agent installed:

  1. Access the hosts file on the computer that has PATROL agent installed.

    • (Windows)

    C:\Windows\System32\drivers\etc\

    • (Solaris or Unix) 

    /etc/hosts

  2. Edit the value for IP address to include actual IP of the computer. 

Identifying policy applied status

Central Monitoring Administration indicates the following policy applied status. The tool tip provides additional information about the status, such as:

  • The list of policy names with its status
  • The time when the policy was applied

Note

Only BMC PATROL Agents that have successfully established communication with Central Monitoring Administration are displayed as connected to an Integration Service.

Policy Status

Description

Tool tip

ico_success.JPG

 

Displayed when:

  • the matching policy or policies were successfully applied to the PATROL Agent
  • all matching policies were deleted and as a result, configuration from PATROL agent was deleted
  • a PATROL Agent was registered with Central Monitoring Administration but PATROL Agent does not have matching policy in Central Monitoring Administration
  • The following policies were considered for application and successfully applied at TIME_STAMP Policy_Name1, Policy_Name2
  • No matching policies hence configuration cleaned up successfully
  • No matching policies hence configuration cleaned up successfully

ico_fail.JPG

Displayed when:

  • all matching policies were failed to apply on a PATROL Agent
  • all policies were not successfully applied (one or more policies were successfully applied but one or more policies failed to apply.)
  • policies were successfully applied previously to a PATROL Agent but now the policies are deleted and the configuration cleanup at the PATROL Agent end failed. The result is that configuration on the PATROL agent is not deleted even if the policies were deleted.
  • policies deleted but configuration cleanup at PATROL Agent failed.
  • The following policies could not be applied at TIME_STAMP Policy_Name1, Policy_Name2
  • The following policies could not be applied at TIME_STAMP Policy_Name1, Policy_Name2
    The following policies were considered for application and successfully applied at TIME_STAMP Policy_Name1, Policy_Name2
  • No matching policies and configuration cleaned up failed at TIME_STAMP
    The following policies were considered for application and successfully applied at TIME_STAMP Policy_Name1, Policy_Name2
  • No matching policies and configuration cleanup failed

ico_unknown.JPG

 

Displayed when there is no response from the PATROL Agent or from the Integration Service about policy applied status. The unknown status appears when:

  • the policy application status unknown for the matching policies.
  • policies were deleted but status of configuration cleanup at PATROL agent end is unknown
  • a PATROL Agent was registered with Central Monitoring Administration but PATROL Agent does not have matching policy in Central Monitoring Administration
  • The status of application of the following policies is unknown
    Policy_Name1, Policy_Name2
  • No matching policies and status of configuration cleanup is unknown
  • No matching policies and status of configuration cleanup is unknown

ico_initial.JPG

Displayed when:

  • There is no information from the Integration Service about policy applied status. This appears when policy might or might not have applied. When you upgrade, this is the initial policy application status for all PATROL Agents, because there is no information about whether the policies were applied or not.
  • A PATROL Agent is not being policy managed.
  • Information on policies applied is not available yet.
  • Agent is currently not managed by policies. The configuration was cleaned up successfully or no policies were applied.

Identifying the connection status

You can identify the connection status of the following components:

To identify the child server connection status

You can see a list of child servers associated to Central Monitoring Administration and its connection status. When you click the Servers drawer in Central Monitoring Administration, the list of child servers appears and the Connected.JPG  and Disconnected.JPG icons next to the child server names indicate whether the child server is connected or disconnected, respectively.

Note

If the child server version is lower than the Central Monitoring Administration version, a warning icon appears.

To identify the Integration Service connection status

You can identify the connection status between the Child server and Integration Service. When you click the Servers drawer in Central Monitoring Administration, the Integration Service column on the right pane indicates the Integration Service status.

Integration Service versions 8.6, 9.5, and 9.6

Icon

Status

IS_green.png

Connected

IS_red.png

Disconnected

unknownIS.jpeg

Unknown - the child server is disconnected from Central Monitoring Administration

Integration Service version 9.0

Icon

Status

IS_green.png

Both Child server with Integration Service and Central Monitoring Administration with Integration Service are connected

IS_red.png

Both Child server with Integration Service and Central Monitoring Administration with Integration Service are disconnected

IS_yellow.png

One of the connections is broken. For more information, see the tooltip

Note

Even if the Child Server is disconnected from Central Monitoring Administration, you can still see the status of Integration Service based on the connection status of Central Monitoring Administration and the Proxy Server. There is no unknown status for Integration Service version 9.0.

To identify the PATROL Agent connection status

You can identify the connection status between Integration Service and PATROL Agent. When you click the Servers drawer in Central Monitoring Administration, the page that appears on the right side of the screen contains the Connected.JPG and Disconnected.JPG icons under the Agent column to indicate whether the PATROL Agent is connected or disconnected with the Integration Service, respectively.

After upgrading an Integration Service to version 9.6, the associated 9.0 BMC PATROL Agents show as connected. Once the Integration Service is upgraded to version 9.6, the 9.0 instances stop polling data, but the status is displayed for the previous two days.

BMC PATROL Agents version 9.0 are not compatible with Integration Services later than version 9.0.

As a best practice, upgrade both the Integration Service and BMC PATROL Agents to the latest version.

The Additional Informationico_addinfo.png column displays the PATROL Agent status:

Icon

Status

ico_markForDel.gif

Agent is marked for delete

ico_blackout.png

Agent is marked for blackout

exclamation.png

Agent is not policy manageable

During a PATROL Agent blackout period, if you remove policy management through Central Monitoring Administration, both the blackout ico_blackout.png and non-policy managed agent exclamation.png icons are displayed together.

When the blackout configuration is removed from the PATROL agent, the blackout icon disappears after a short delay.

Using the tools menu

The tools menu ico_tools.jpg appears for each PATROL Agent in the Servers drawer. Depending on the connection status of the PATROL Agent with the Integration Service, the menu displays the following options:

  • When connected — Sync Instance Information, Query Agent, and Use policy management or Remove policy management
  • When disconnected — Delete Agent

Managing PATROL agents from Central Monitoring Administration

By default, Central Monitoring Administration manages the PATROL agent(s) configuration.

To change this behavior, perform the following steps:

  1. Click the tools menu ico_tools.jpgfor the PATROL agent you want to manage.
  2. To not manage the PATROL agent from Central Monitoring Administration, click Remove policy management.
    The exclamation.pngexclamation.pngicon appears under the ico_addinfo.pngcolumn to indicate that the PATROL agent is not being managed by Central Monitoring Administration.
  3. To manage the PATROL agent from Central Monitoring Administration, click Use policy management.
  4. To manage multiple PATROL agents, select the agents (press and hold Ctrl while clicking the PATROL agents name) and click the Agent tools menu ico_tools.jpgat the top row.
    Select Use policy management or Remove policy management.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*