Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dsliteNATBindMappingAddressPooling",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"arbitrary",
"(",
"0",
")",
",",
"paired",
"(",
"1",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Type of address pooling behavior that was used to create this mapping. arbitrary(0) pooling behavior means that the NAT instance may create the new port mapping using any address in the pool that has a free port for the protocol concerned. paired(1) pooling behavior, the behavior RECOMMENDED by RFC 4787, REQ-2 means that once a given internal address has been mapped to a particular address in a particular pool, further mappings of the same internal address to that pool will reuse the previously assigned pool member address.\"",
"REFERENCE",
"\"Pooling behavior: Section 4.1 of RFC 4787.\"",
"::=",
"{",
"dsliteNATBindEntry",
"14",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"arbitrary",
0
],
[
"paired",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Type of address pooling behavior that was used to create this mapping. arbitrary(0) pooling behavior means that the NAT instance may create the new port mapping using any address in the pool that has a free port for the protocol concerned. paired(1) pooling behavior, the behavior RECOMMENDED by RFC 4787, REQ-2 means that once a given internal address has been mapped to a particular address in a particular pool, further mappings of the same internal address to that pool will reuse the previously assigned pool member address."
],
[
"REFERENCE",
"Pooling behavior: Section 4.1 of RFC 4787."
],
null,
null,
null
]
}