lmpNotificationMaxRate
LMP-MIB ·
.1.3.6.1.2.1.10.227.1.18
Object
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.
Context
- MIB
- LMP-MIB
- OID
.1.3.6.1.2.1.10.227.1.18- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- lmpObjects
- Siblings
- 22
Syntax
SNMPv2-SMIUnsigned32
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| lmpAdminStatus The desired operational status of LMP on the node.
Implementations should save the value of this object in
persistent memory so that it survives restarts or reboot. | scalar | Enumeration | .1.3.6.1.2.1.10.227.1.1 |
| lmpControlChannelTable This table specifies LMP control channel information. | table | - | .1.3.6.1.2.1.10.227.1.10 |
| lmpControlChannelPerfTable This table specifies LMP control channel performance
counters. | table | - | .1.3.6.1.2.1.10.227.1.11 |
| lmpTeLinkTable This table specifies the LMP-specific TE link information.
Overall TE link information is kept in three separate tables:
ifTable for interface-specific information, lmpTeLinkTable… | table | - | .1.3.6.1.2.1.10.227.1.12 |
| lmpGlobalLinkVerificationInterval This object indicates how often the link verification
procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link
verification procedur… | scalar | milliseconds SNMPv2-SMIUnsigned32 | .1.3.6.1.2.1.10.227.1.13 |
| lmpLinkVerificationTable This table specifies TE link information associated with the
LMP verification procedure. | table | - | .1.3.6.1.2.1.10.227.1.14 |
| lmpTeLinkPerfTable This table specifies LMP TE link performance counters. | table | - | .1.3.6.1.2.1.10.227.1.15 |
| lmpDataLinkTable This table specifies the data-bearing links managed by the
LMP. | table | - | .1.3.6.1.2.1.10.227.1.16 |
| lmpDataLinkPerfTable This table specifies the data-bearing links LMP performance
counters. | table | - | .1.3.6.1.2.1.10.227.1.17 |
| lmpLinkPropertyNotificationsEnabled If this object is true(1), then it enables the
generation of lmpTeLinkPropertyMismatch
and lmpDataLinkPropertyMismatch notifications;
otherwise, these notifications are not emitte… | scalar | SNMPv2-TCTruthValue | .1.3.6.1.2.1.10.227.1.19 |
| lmpOperStatus The actual operational status of LMP on the node. | scalar | Enumeration | .1.3.6.1.2.1.10.227.1.2 |
| lmpUnprotectedNotificationsEnabled If this object is true(1), then it enables the
generation of lmpUnprotected notifications;
otherwise, these notifications are not emitted.
Implementations should save the value of… | scalar | SNMPv2-TCTruthValue | .1.3.6.1.2.1.10.227.1.20 |
| lmpCcUpDownNotificationsEnabled If this object is true(1), then it enables the generation of
lmpControlChannelUp and lmpControlChannelDown notifications;
otherwise, these notifications are not emitted.
Implement… | scalar | SNMPv2-TCTruthValue | .1.3.6.1.2.1.10.227.1.21 |
| lmpTeLinkNotificationsEnabled If this object is true(1), then it enables the
generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded
notifications; otherwise, these notifications are not emitted.
Implementati… | scalar | SNMPv2-TCTruthValue | .1.3.6.1.2.1.10.227.1.22 |
| lmpDataLinkNotificationsEnabled If this object is true(1), then it enables the
generation of lmpDataLinkVerificationFailure
notification; otherwise, these notifications are not emitted.
Implementations should sa… | scalar | SNMPv2-TCTruthValue | .1.3.6.1.2.1.10.227.1.23 |
| lmpNbrTable This table specifies the neighbor node(s) to which control
channels may be established. | table | - | .1.3.6.1.2.1.10.227.1.3 |
| lmpCcHelloIntervalDefault This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It
indicates how frequently LMP Hello messages will be sent. … | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.4 |
| lmpCcHelloIntervalDefaultMin This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin. Implementations should save the
value o… | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.5 |
| lmpCcHelloIntervalDefaultMax This object specifies the default maximum value for the
HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMax. Implementations should save the
value o… | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.6 |
| lmpCcHelloDeadIntervalDefault This object specifies the default HelloDeadInterval parameter
to use in the Hello protocol keep-alive phase. It indicates
how long a device should wait before declaring the contr… | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.7 |
| lmpCcHelloDeadIntervalDefaultMin This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin. Implementations should save
the… | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.8 |
| lmpCcHelloDeadIntervalDefaultMax This object specifies the default maximum value for the
HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMax. Implementations should save the… | scalar | LmpInterval | .1.3.6.1.2.1.10.227.1.9 |