Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMplsPsType",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"4",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP. 3. In the shared mesh architecture type, possible sharing of protection capacity between disjoint link, node, or SRG failures in the network is achieved while guaranteeing recovery from a single failure. For each link in the network, it keeps track of all the working paths whose traffic will be switched onto it after a given failure. By keeping track of this, it only needs to reserve the maximum of the protection capacity required to protect a single failure in the network. 4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously onto two possibly disjoint routed LSPs to the sink of the protection domain. Each pair of duplicate transmitted packets is assigned the same identifier(sequence number) but distinct from the other pairs of duplicate packets. At the sink of the protection domain, packet level selection mechanism is employed to select one of the two possibly received copies of each packet. The following list provides principles for MPLS protection architectures and mechanisms development. 1: 1:1 protection switching; 2: 1+1 protection switching; 3: shared mesh protection swiching; 4: packet 1+1 protection switching.\"",
"::=",
"{",
"fsMplsPsEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The MPLS PS architecture can be a 1+1 type, a 1:1 type, a shared mesh type, or a packet 1+1 type. 1. In the 1+1 architecture type, a protection LSP is dedicated to each working LSP with the working LSP bridged onto the protection LSP at the source of the protection domain. 2. In the 1:1 architecture type, a protection LSP is dedicated to each working LSP. 3. In the shared mesh architecture type, possible sharing of protection capacity between disjoint link, node, or SRG failures in the network is achieved while guaranteeing recovery from a single failure. For each link in the network, it keeps track of all the working paths whose traffic will be switched onto it after a given failure. By keeping track of this, it only needs to reserve the maximum of the protection capacity required to protect a single failure in the network. 4. In the packet 1+1 architecture type, the traffic is transmitted simultaneously onto two possibly disjoint routed LSPs to the sink of the protection domain. Each pair of duplicate transmitted packets is assigned the same identifier(sequence number) but distinct from the other pairs of duplicate packets. At the sink of the protection domain, packet level selection mechanism is employed to select one of the two possibly received copies of each packet. The following list provides principles for MPLS protection architectures and mechanisms development. 1: 1:1 protection switching; 2: 1+1 protection switching; 3: shared mesh protection swiching; 4: packet 1+1 protection switching."
],
null,
null,
null,
null
]
}