Status in source: current.
Names: cienaCesPbtTunnelReversionHoldTime
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"cienaCesPbtTunnelReversionHoldTime",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"UNITS",
[
"literal",
"226d696c6c697365636f6e647322"
],
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Protection of the transport mechanism in PBB-TE is achieved using redundant tunnels. A protected PBB-TE tunnel is backed up by a standby PBB-TE tunnel serving the same destination. The former is marked as the primary tunnel and the latter as the backup tunnel. Protection switching in PBB-TE requires both the ingress and egress nodes to have matching configurations. Upon the failure of the primary tunnel, traffic is moved over to the backup tunnel at the tunnel ingress. Tunnel reversion signifies the restoration of traffic from this backup tunnel (now active) to the primary (now standby) after the primary tunnel is restored. Two common methods are used - automatic and manual. In automatic reversion, the traffic is automatically reverted back to the primary after it is restored. The manual method, on the other hand, requires the operator to explicitly revert the traffic back to the primary. Manual reversion allows the network operator to perform the task when the impact to the service is minimal and to schedule it. It also prevents flip-flopping between the two tunnels if the primary is not entirely stable. This object represents the hold time before data traffic on the backup tunnel automatically reverts to the primary tunnel.\"",
"DEFVAL",
"{",
"3000",
"}",
"::=",
"{",
"cienaCesPbtGlobalAttrs",
"5",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
[
"UNITS",
"milliseconds"
],
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Protection of the transport mechanism in PBB-TE is achieved using redundant tunnels. A protected PBB-TE tunnel is backed up by a standby PBB-TE tunnel serving the same destination. The former is marked as the primary tunnel and the latter as the backup tunnel. Protection switching in PBB-TE requires both the ingress and egress nodes to have matching configurations. Upon the failure of the primary tunnel, traffic is moved over to the backup tunnel at the tunnel ingress. Tunnel reversion signifies the restoration of traffic from this backup tunnel (now active) to the primary (now standby) after the primary tunnel is restored. Two common methods are used - automatic and manual. In automatic reversion, the traffic is automatically reverted back to the primary after it is restored. The manual method, on the other hand, requires the operator to explicitly revert the traffic back to the primary. Manual reversion allows the network operator to perform the task when the impact to the service is minimal and to schedule it. It also prevents flip-flopping between the two tunnels if the primary is not entirely stable. This object represents the hold time before data traffic on the backup tunnel automatically reverts to the primary tunnel."
],
null,
null,
null,
[
"DEFVAL",
3000
]
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: CIENA-CES-PBT-MIB
See published definition above
Module imports
{'CIENA-TC': ['CienaGlobalState'], 'CIENA-SMI': ['cienaCesConfig', 'cienaCesNotifications'], 'SNMPv2-TC': ['TruthValue', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['Unsigned32', 'Counter32', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'MODULE-IDENTITY'], 'SNMPv2-CONF': ['NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CIENA-GLOBAL-MIB': ['cienaGlobalSeverity', 'cienaGlobalMacAddress']}
· Download CIENA-CES-PBT-MIB
Related source files and packages: