Modifying parameter properties


Follow these guidelines when you modify parameter properties:

  1. Make changes in one account by using the parameter property dialog boxes.
  2. Test the account until you are satisfied that the changes operate as expected.
  3. Export the modified parameter changes to PATROL Configuration Manager.
  4. Deploy the modified parameter changes to other accounts by using PATROL Configuration Manager.

This method takes advantage of the validations performed by the KM, and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.

To modify parameter properties for an account by using a PATROL console

  1. Navigate to the parameter properties for the parameter you want to change:
    • In the PATROL Console for UNIX, click Attributes and then click Application Classes to open a list of the application classes. Select an application class, then click Attributes and then click Parameters to open the list of parameters provided by the selected application class.
    • In PATROL Console for Microsoft Windows, select the KM tree tab. Then expand the appropriate application class > Global > Parameters.
  2. To access the parameter properties:
    • (Windows) Right-click the parameter and select Properties.
    • (UNIX) Click the parameter.
  3. To activate or deactivate a parameter, perform one of these actions:
    • (Windows) Select the General tab and select or clear Active.
    • (UNIX) Double-click the parameter and select or clear Active.
  4. To change the interval between polling cycles, perform one of these actions:
    • (Windows) Select the Scheduling tab and change the polling time.
    • (UNIX) Click the parameter and change the polling time.
  5. To change the alarm thresholds or disable the alarms, perform one of these actions:
    • (Windows) Select the Alarm Ranges tab and make changes. Then set actions on the Border Actions, Alarm1 Actions, and Alarm2 Actions tabs.
    • (UNIX) Click Alarm Ranges, and then double-click Border, Alarm1, or Alarm2, and make changes.
  6. Save the configuration by selecting File > Save Configuration.
  7. Test the changes on the account to make sure that the changes are working as you expected.
  8. Convert the parameters in the account to a RuleSet in PATROL Configuration Manager.
     You can convert the parameters in the account to a RuleSet in PATROL Configuration Manager by using one of the following menu commands:
    • KM Commands > Create Global Parameters > Create Rulesets > Select Knowledge Modules menu command from the AS_CHANGESPRING application class
    • KM Commands > Event Management > Parameter Settings > Status Flags > Set for Instances or Classes menu command from the Host icon
       For more information, see the PATROL Configuration Manager User Guide at PDFs

      Warning

      Note

      PATROL Configuration Manager rules that represent each parameter contain the _ANYINST_ designation for the instance name. The _ANYINST_ designation allows you to apply these changes to any agent host name without adding a specific agent host name to the rule for each parameter.

  9. Drag the RuleSet to any agent host name where you want the changes applied. 

    Warning

    Note

    The following rule is created when you move the parameters to a RuleSet in BMC PATROL

    Configuration Manager: /AS/EVENTSPRING/PARAM_SETTINGS/STATUSFLAGS/paramSettingsStatusFlag” = { REPLACE = “2” }

    This rule forces the account to apply parameter changes as soon as you apply them to an account or agent host name. If you do not want the changes to take place immediately, change 2 to 1, or remove this rule and reinitialize the agent for the account when you are ready to apply the changes. For more information, see the PATROL Configuration Manager User Guide at PDF product guides.

 

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

BMC PATROL for Cisco Nexus 1.1