Configuring SIM Notification Registry parameters in the cell

You can create a new or edit an existing Notification Registry Internal instance in the cell to create or modify the notification events. You can configure a Notification Registry Internal instance in the cell using the Administrator console of the TrueSight Infrastructure Management.

To configure a Notification Registry Internal instance

  1. Open the Administrator console of the Infrastructure Management Server.
  2. On the Administration tab, and click Dynamic Data Editor .
  3. Select the cell where you want to modify the Notification Registry Internal  instance.
  4. Navigate to Data > Cell Data, and click Notification Registry Internal as shown in the following image:
  5. Right-click and select one of the following:
    1. New if you want to create a new Notification Registry Internal instance in the cell.
    2. Edit to modify an existing Notification Registry Internal instance in the cell.
    3. Delete to delete an existing Notification Registry Internal instance in the cell.
  6. If you are creating a new instance or editing an existing instance, refer the following table to set the registry parameters of the Notification Registry Internal instance.

    ParameterDescription
    Client DataAllows you to define a rule set for the SIM notification events that your client is registered to receive. For example, if you set this parameter to IBRSD, the rule could search for the text IBRSD in the client_data field to determine whether it is a state change requested by IBRSD. 
    ClientsA comma-separated list of clients where the notification must be sent. The clients in the list must be defined in mcell.dir. By default, the cell name is listed as the client in mcell.dir. Do not change the mcell.dir file if you are sending events internally.
    Requested Notifications

    It is a comma-separated list of SIM notification events:

    • COMPONENT_CHANGE: When the component's status is changed
    • COMPONENT_DELETE: When the component is deleted
    • COMPONENT_OVERWRITE: When component's status is updated
    • RELATIONSHIP_CHANGE: When the component CI relationship is changed
    • RELATIONSHIP_DELETE: When the component CI relationship is deleted
    Notification Mode

    Specifies how the slot values that have not changed are reported in the SIM notification event:

    • DELTA: The slots whose values do not change are reported with their default values. The default value is an empty string for symbolic values and -1 for numeric values. See the .baroc class definition of the SIM notification event for the default slot values.
    • FULL: The current values of all slots are reported, including those that have not changed.
    Notifications at Registration

    Notifies the cell whether to send the current component state at the moment of registration:

    • YES: Notifies the cell to send the current component state at the moment of registration.
    • NO: Notifies the cell not to send the current component state at the moment of registration.
    Asset FilterSpecify a class name. The state change notifications are generated only for the configuration items of the specified class or a subclass.
    Causal Event Notification Mode

    Set one of the following values:

    • FULL: Notifies the cell to send all the CI event notifications.
    • DELTA: Notifies the cell to send only the CI causal event notifications.
    • NONE: Notifies the cell not to send any CI event notifications.
    Impact Status Propagation
    • YES: Every CI status change is propagated to the top-level CI in the service model.
    • NO: CI status change that is lower than the current CI status change is only propagated to the top-level CI in the service model.
    Severity Notification Mode

    Important Information

    This parameter is supported only if you have TrueSight Infrastructure Management server version 11.3.02 and later, and a non-cluster setup.

    You can set one of the following values:

    • YES
    • NO

    For details about how incidents are created based on the Severity Notification Mode, see To enable the severity notification mode.

  7. Click OK to save the changes.

To enable the severity notification mode

The Severity Notification Mode parameter can be set to one of the following values:

  • YES: Additional incidents and outages are created whenever the Severity value changes. Additional incident events are created when there is a transition from higher severity to lower severity, even though the IBRSD policy rules do not match the severity criteria. For example, if the policy rule states that an incident should be created when the severity status is Critical, additional incidents are being created when the severity transitions from Critical to Major, Major to Minor etc.
  • NO: This ensures that new incidents and outages are not created whenever the policy criteria does not match the CI status. 

    Note

    Following is an exception when you set the Severity Notification Mode to NO:

    If you receive a lower severity event when an incident is already existing for a higher severity event, a new incident will be created for this lower severity event only when the higher severity event is closed. For example, if there is an incident created for a Critical severity event, and after a while you receive a Major severity event, a new incident will be created for this Major severity event only when the incident for the Critical severity event is closed.

The following example use cases illustrate the incident creation pattern when you set Severity Notification Mode to Yes/No. Consider the BMC_BusinessService with computer system configuration items (CIs) C1 and C2 as shown in the following screenshot:

The table lists various use cases when the Severity Notification Mode is set to YES/NO:

Severity Notification Mode = YES

Policy statusOutage resultsIncident results
Use case 1: Incident policy status = Unavailable
C1 Impact status = CriticalOutages for C1 and BMC_BusinessService are generated
  • Causal and infrastructure incidents for C1 are generated
  • Impacted incident is generated for the BMC_BusinessService
C2 Impact status = MajorOutage for C2 is generated

Causal and infrastructure incidents for C2 are generated

Close the Critical incident on C1Outage for C1 is restored

Causal and infrastructure incidents for C1 are resolved

Close the Major incident on C2Outage for C2 is restored
  • Causal and infrastructure incidents for C2 are resolved
  • Impacted incident is resolved for the BMC_BusinessService
Use case 2: Incident Policy status = Unavailable
C1 Impact status = CriticalOutages for C1 and BMC_BusinessService are generated
  • Causal and infrastructure incidents for C1 are generated
  • Impacted incident is generated for the BMC_BusinessService
C1 Impact status = MajorNo outages are generatedInfrastructure incident for C1 is generated
Close the Critical incident on C1No impact

New Infrastructure incident for C1 is generated

Close the Major incident on C1Outages for C1 and BMC_BusinessService are restored
  • Infrastructure and causal incidents for C1 are resolved
  • Impacted incident is resolved for the BMC_BusinessService

Severity Notification Mode = NO

Policy statusOutage resultsIncident results
Use case 1: Incident Policy status = Unavailable
C1 Impact status = CriticalOutages for C1 and BMC_BusinessService are generated
  • Causal and infrastructure incidents for C1 are generated
  • Impacted incident is generated for the BMC_BusinessService
C2 Impact status = MajorNo outage is generatedNo incident is generated
Close the Critical incident on C1Outages for C1 and BMC_BusinessService are restored
  • Causal and infrastructure incidents for C1 are resolved
  • Impacted incident is resolved for the BMC_BusinessService
Close the Major incident on C2No impactNo impact
Use case 2: Incident Policy status = Unavailable
C1 Impact status = CriticalOutages for C1 and BMC_BusinessService are generated
  • Causal and infrastructure incidents for C1 are generated
  • Impacted incident is generated for the BMC_BusinessService
C1 Impact status = MajorNo outages are generatedNo incidents are generated
Close the Critical incident on C1Outages for C1 and BMC_BusinessService are restored
  • Causal and infrastructure incidents for C1 are resolved
  • Impacted incident is resolved for the BMC_BusinessService
Close the Major incident on C1No impactNo impact
Use case 3: Incident Policy status = Impacted
C1 Impact status = Minor

No impact

No Impact 
C2 Impact status = Major

Outages for C2 and BMC_BusinessService are generated

  • Causal and infrastructure incidents for C2 are generated
  • Impacted incident is generated for the BMC_BusinessService
Close the Major incident on C2Outages for C2 and BMC_BusinessService are restored
  • Causal and infrastructure incidents for C2 are resolved
  • Impacted incident is resolved for the BMC_BusinessService
Close the Minor incident on C1No Impact

No Impact 


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

Comments