Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Managed Objects for jnxSoamPmNotifications Table

    The jnxSoamPmNotifications table, whose object identifier is {jnxSoamPmMib 0}, contains the objects listed in the following table.

    Table 1: jjnxSoamPmNotifications Table

    Object

    Object ID

    Description

    jnxSoamLmSessionStartStopAlarm

    jnxSoamPmNotifications 1

    A jnxSoamLmSessionStartStopAlarm notification is sent when the state of jnxSoamLmCfgSessionStatus changes.

    The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID jnxSoamLmCfgSessionStatus, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and jnxSoamLmCfgIndex.

    An agent is not to generate more than one jnxSoamLmSessionStartStopAlarm 'notification-event' in a given time interval per LM session as specified by the jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.

    If additional operational state changes occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are be suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.

    jnxSoamDmSessionStartStopAlarm

    jnxSoamPmNotifications 2

    A jnxSoamDmSessionStartStopAlarm notification is sent when the state of jnxSoamDmCfgSessionStatus changes.

    The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the individual PM session reporting the start/stop by the indices in the OID jnxSoamDmCfgSessionStatus, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and jnxSoamLmCfgIndex.

    An agent is not to generate more than one jnxSoamDmSessionStartStopAlarm 'notification-event' in a given time interval per DM session as specified by the jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.

    If additional operational state changes occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are be suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any operational state changes occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.

    jnxSoamPmThresholdCrossingAlarm

    jnxSoamPmNotifications 3

    "An jnxSoamPmThresholdCrossingAlarm notification is sent if the following conditions are met for a particular type. For an aboveAlarm, the following five conditions must be satisfied:

    1. Measurement of the parameter is enabled via jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing.
    2. The parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable; and c) the threshold crossing type of bPmThresholdAboveAlarm is enabled.
    3. The measured value of the parameter exceeds the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdAboveAlarm.
    4. No previous jnxSoamPmThresholdCrossingAlarm notifications with type aboveAlarm have been sent relating to the same threshold in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable and the same parameter, during this Measurement Interval.

    For a setAlarm, the following five conditions must be met:

    1. Measurement of the parameter is enabled using jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing.
    2. The parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable.
    3. The threshold crossing type of bPmThresholdSetClearAlarm is enabled.
    4. The measured value of the parameter exceeds the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm for the Measurement Interval.
    5. The previous measured value did not exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm.

    For a clearAlarm, the following five conditions must be met:

    1. Measurement of the parameter is enabled using jnxSoamLmCfgMeasurementEnable for a LM crossing or jnxSoamDmCfgMeasurementEnable for a DM crossing.
    2. The parameter threshold is configured in the jnxSoamLmThresholdCfgTable or jnxSoamDmThresholdCfgTable.
    3. The threshold crossing type of bPmThresholdSetClearAlarm is enabled.
    4. The measured value of the parameter did not exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm for the Measurement Interval.
    5. The previous measured value did exceed the value configured in the jnxSoamLmThresholdCfgTable for a LM crossing entry or jnxSoamDmThresholdCfgTable for a DM crossing entry for a type of bPmThresholdSetClearAlarm.

    In the case of thresholds applied to a maximum or average measurement counter, the previous measured value is the value of the counter at the end of the preceding Measurement Interval. In the case of thresholds applied to the last measured value, it is the previous measured value. The management entity that receives the notification can identify the system from the network source address of the notification, and can identify the LM or DM session reporting the threshold crossing by the indices in the jnxSoamPmNotificationCfgThresholdId object, including dot1agCfmMdIndex, dot1agCfmMaIndex, dot1agCfmMepIdentifier, and the jnxSoamLmCfgIndex or jnxSoamDmCfgIndex.

    An agent is not to generate more than one jnxSoamLmThresholdCrossingAlarm 'notification-event' of a given type per LM or DM session as specified by jnxSoamPmNotificationCfgAlarmInterval. A 'notification-event' is the transmission of a single notification to a list of notification destinations.

    If additional threshold crossing events occur within the jnxSoamPmNotificationCfgAlarmInterval period, then notification generation for these changes are suppressed by the agent until the current alarm interval expires. At the end of an alarm interval period, one notification-event is generated if any threshold crossing events occurred since the start of the alarm interval period. In such a case, another alarm interval period is started right away.

    Modified: 2017-09-13