2.1.00 features

This topic contains information about enhancements and changes made in PATROL for Light Weight Protocols 2.1.00.

Tip

For information about issues corrected in this release, see Known and corrected issues.

What's new

Support for user defined location in file-based configuration

PATROL for Light Weight Protocols now supports user-defined location (can be another filesystem) for file-based configuration instead of the default location (hardcoded location). For more information, see File-based configuration.

Support for enabling or disabling monitoring of monitor types and instances

PATROL for Light Weight Protocols allows you to include or exclude the monitor types and instances from monitoring in SNMP KM. For more information, see Configuring in SNMP.

Support for file-based configuration on multiple PATROL Agents

PATROL for Light Weight Protocols now supports file-based configuration on multiple PATROL Agent processes running on the same computer with different home directories and different ports. For more information, see File-based configuration.

Support for adding multiple IP addresses to a configured device

In PATROL for Light Weight Protocols, you can add multiple IP addresses to a configured device. The configured device acts as a container and contains multiple IP addresses.

Support for RHEL 7.2

The PING KM now supports Red Hat Enterprise Linux version 7.2 (zSeries, x86_64). For more information, see System requirements.

What's changed

Updated parameters unit

The following table displays the updated parameters unit:

Monitor typeParameterExisting unitNew unit
PSM_Root

_ConfigurationStatus

0 - Not OK, 1 - OK

0 - OK, 1 - Not OK
PSM_Root_MonitorStatus

0 - Not OK, 1 - OK

0 - OK, 1 - Not OK
PSM_Root_MonitorStatus

0 - Not OK, 1 - OK

0 - OK, 1 - Not OK
PPM_HostAvailability

0 - Down, 1 - Up

0 - OK, 1 - Not OK
PPM_DeviceAvailability

0 - Down, 1 - Up

0 - OK, 1 - Not OK

Updated thresholds of the parameters (present in the preceding table)

Make the following changes in your respective environments:

  • TrueSight Operations Management:
    • Check the events generated on your system by clicking on the Events tab under Monitoring in the TrueSight console. 
       
    • Update the thresholds of parameters that are in false alarm state due to the change in their unit.

  • PATROL console:
    • Check the events generated on your system by clicking on the Event Manager in the PATROL console

    • Update the thresholds of parameters that are in false alarm state due to the change in their unit.

  • PATROL Central operator console:
    • Check the events generated on your system by clicking on the Event Manager in the console
       
    • Update the thresholds of parameters that are in false alarm state due to the change in their unit.

Was this page helpful? Yes No Submitting... Thank you

Comments