lmpNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The LMP notification rate depends on the size of the network,
the type of links, the network configuration, the
reliability of the network, etc.
When designing this MIB, care has been taken to minimize the
amount of notifications generated for LMP purposes. Wherever
possible, notifications are state driven, meaning the
notifications are sent only when the system changes state.
The only notifications that are repeated and could cause a
problem as far as congestion is concerned are the ones
associated with data link verification.
Without any considerations to handling of these
notifications, a problem may arise if the number of data
links is high. Since the data link verification notifications
can happen only once per data link per link verification
interval, the notification rate should be sustainable if one
chooses an appropriate link verification interval for a given
network configuration. For instance, a network of 100 nodes
with 5 links of 128 wavelengths each and a link verification
of 1 minute with no more than 10% of the links failed at any
given time would have 1 notification per second sent from
each node, or 100 notifications per second for the whole
network. The rest of the notifications are negligible
compared to this number.
To alleviate the congestion problem, the
lmpNotificationMaxRate object can be used to implement a
throttling mechanism. It is also possible to enable/disable
certain type of notifications.
This variable indicates the maximum number of
notifications issued per minute. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period, or may
queue them until an appropriate time. A value of 0
means no throttling is applied and events may be
notified at the rate at which they occur.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot."
View at oid-info.com
The LMP notification rate depends on the size of the network,
the type of links, the network configuration, the
reliability of the network, etc.
When this MIB was designed, care was taken to minimize the
amount of notifications generated for LMP purposes. Wherever
possible, notifications are state driven, meaning that the
notifications are sent only when the system changes state.
The only notifications that are repeated and that could cause a
problem as far as congestion is concerned are the ones
associated with data link verification.
Without any considerations to handling of these
notifications, a problem may arise if the number of data
links is high. Since the data link verification notifications
can happen only once per data link per link verification
interval, the notification rate should be sustainable if one
chooses an appropriate link verification interval for a given
network configuration. For instance, a network of 100 nodes
with 5 links of 128 wavelengths each and a link verification
of 1 minute, where no more than 10% of the links failed at any
given time, would have 1 notification per second sent from
each node, or 100 notifications per second for the whole
network. The rest of the notifications are negligible
compared to this number.
To alleviate the congestion problem, the
lmpNotificationMaxRate object can be used to implement a
throttling mechanism. It is also possible to enable/disable
certain type of notifications.
This variable indicates the maximum number of
notifications issued per minute. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period or may
queue them until an appropriate time. A value of 0
means that no throttling is applied and events may be
notified at the rate at which they occur.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot.
Parsed from file LMP-MIB.mib
Module: LMP-MIB
Automatically extracted from RFC4327
lmpNotificationMaxRate OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "The LMP notification rate depends on the size of the network, the type of links, the network configuration, the reliability of the network, etc. When this MIB was designed, care was taken to minimize the amount of notifications generated for LMP purposes. Wherever possible, notifications are state driven, meaning that the notifications are sent only when the system changes state. The only notifications that are repeated and that could cause a problem as far as congestion is concerned are the ones associated with data link verification. Without any considerations to handling of these notifications, a problem may arise if the number of data links is high. Since the data link verification notifications can happen only once per data link per link verification interval, the notification rate should be sustainable if one chooses an appropriate link verification interval for a given network configuration. For instance, a network of 100 nodes with 5 links of 128 wavelengths each and a link verification of 1 minute, where no more than 10% of the links failed at any given time, would have 1 notification per second sent from each node, or 100 notifications per second for the whole network. The rest of the notifications are negligible compared to this number. To alleviate the congestion problem, the lmpNotificationMaxRate object can be used to implement a throttling mechanism. It is also possible to enable/disable certain type of notifications. This variable indicates the maximum number of notifications issued per minute. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period or may queue them until an appropriate time. A value of 0 means that no throttling is applied and events may be notified at the rate at which they occur. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot." ::= { lmpObjects 18 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.227.1.18.0 | lmpNotificationMaxRate | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.227.1.1 | lmpAdminStatus | 1 | 1 | The desired operational status of LMP on the node. Implementations should save the value of this object in persistent memory so t… |
| 1.3.6.1.2.1.10.227.1.2 | lmpOperStatus | 1 | 1 | The actual operational status of LMP on the node. |
| 1.3.6.1.2.1.10.227.1.3 | lmpNbrTable | 1 | 9 | This table specifies the neighbor node(s) to which control channels may be established. |
| 1.3.6.1.2.1.10.227.1.4 | lmpCcHelloIntervalDefault | 1 | 1 | This object specifies the default value for the HelloInterval parameter used in the Hello protocol keep-alive phase. It indicate… |
| 1.3.6.1.2.1.10.227.1.5 | lmpCcHelloIntervalDefaultMin | 1 | 1 | This object specifies the default minimum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloInt… |
| 1.3.6.1.2.1.10.227.1.6 | lmpCcHelloIntervalDefaultMax | 1 | 1 | This object specifies the default maximum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloInt… |
| 1.3.6.1.2.1.10.227.1.7 | lmpCcHelloDeadIntervalDefault | 1 | 1 | This object specifies the default HelloDeadInterval parameter to use in the Hello protocol keep-alive phase. It indicates how lo… |
| 1.3.6.1.2.1.10.227.1.8 | lmpCcHelloDeadIntervalDefaultMin | 1 | 1 | This object specifies the default minimum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHell… |
| 1.3.6.1.2.1.10.227.1.9 | lmpCcHelloDeadIntervalDefaultMax | 1 | 1 | This object specifies the default maximum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHell… |
| 1.3.6.1.2.1.10.227.1.10 | lmpControlChannelTable | 1 | 23 | This table specifies LMP control channel information. |
| 1.3.6.1.2.1.10.227.1.11 | lmpControlChannelPerfTable | 1 | 54 | This table specifies LMP control channel performance counters. |
| 1.3.6.1.2.1.10.227.1.12 | lmpTeLinkTable | 1 | 8 | This table specifies the LMP-specific TE link information. Overall TE link information is kept in three separate tables: ifTable … |
| 1.3.6.1.2.1.10.227.1.13 | lmpGlobalLinkVerificationInterval | 1 | 1 | This object indicates how often the link verification procedure is executed. The interval is in milliseconds. A value of 0 is us… |
| 1.3.6.1.2.1.10.227.1.14 | lmpLinkVerificationTable | 1 | 9 | This table specifies TE link information associated with the LMP verification procedure. |
| 1.3.6.1.2.1.10.227.1.15 | lmpTeLinkPerfTable | 1 | 41 | This table specifies LMP TE link performance counters. |
| 1.3.6.1.2.1.10.227.1.16 | lmpDataLinkTable | 1 | 11 | This table specifies the data-bearing links managed by the LMP. |
| 1.3.6.1.2.1.10.227.1.17 | lmpDataLinkPerfTable | 1 | 8 | This table specifies the data-bearing links LMP performance counters. |
| 1.3.6.1.2.1.10.227.1.19 | lmpLinkPropertyNotificationsEnabled | 1 | 1 | If this object is true(1), then it enables the generation of lmpTeLinkPropertyMismatch and lmpDataLinkPropertyMismatch notificati… |
| 1.3.6.1.2.1.10.227.1.20 | lmpUnprotectedNotificationsEnabled | 1 | 1 | If this object is true(1), then it enables the generation of lmpUnprotected notifications; otherwise, these notifications are not… |
| 1.3.6.1.2.1.10.227.1.21 | lmpCcUpDownNotificationsEnabled | 1 | 1 | If this object is true(1), then it enables the generation of lmpControlChannelUp and lmpControlChannelDown notifications; otherwi… |
| 1.3.6.1.2.1.10.227.1.22 | lmpTeLinkNotificationsEnabled | 1 | 1 | If this object is true(1), then it enables the generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded notifications; otherwise,… |
| 1.3.6.1.2.1.10.227.1.23 | lmpDataLinkNotificationsEnabled | 1 | 1 | If this object is true(1), then it enables the generation of lmpDataLinkVerificationFailure notification; otherwise, these notifi… |