OID reference
1.3.6.1.4.1.72.9.5.3.1.1.4
This object determines what action is to be performed on a particular entry. A value causes the entry to be added to the table, while a value of invalid causes the entry to be deleted.
Identification
{1 3 6 1 4 1 72 9 5 3 1 1 4}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it.
| Value | Name | Source variants |
|---|---|---|
| 1 | valid | 1 |
| 2 | invalid | 1 |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In RETIX-LOCAL-BRIDGE-MIB, the row index accessPolicyIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.72.9.5.3.1.1.4.<accessPolicyIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: accessPolicyIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.72.9.5.3.1.1.4
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Available source records contain 2 distinct definitions; some records may not include a definition.
snmpAccessPolicyType OBJECT-TYPE
SYNTAX INTEGER {
valid (1),
invalid (2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION "This object determines what action is to be performed
on a particular entry. A value causes the entry to be added to the
table, while a value of invalid causes the entry to be deleted."
::= { snmpAccessPolicyEntry 4 }snmpAccessPolicyType OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION ""
::= { snmpAccessPolicyEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This object determines what action is to be performed on a particular entry. A value causes the entry to be added to the table, while a value of invalid causes the entry to be deleted.
Retix Local Bridge MIB in the historical IETF archive
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: snmpAccessPolicyType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"snmpAccessPolicyType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"valid",
"(",
"1",
")",
",",
"invalid",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This object determines what action is to be performed on a particular entry. A value causes the entry to be added to the table, while a value of invalid causes the entry to be deleted.\"",
"::=",
"{",
"snmpAccessPolicyEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"valid",
1
],
[
"invalid",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This object determines what action is to be performed on a particular entry. A value causes the entry to be added to the table, while a value of invalid causes the entry to be deleted."
],
null,
null,
null,
null
]
}Module: RETIX-LOCAL-BRIDGE-MIB
See published definition above
{'RFC1065-SMI': ['mgmt', 'OBJECT-TYPE', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: Historical Retix Local Bridge MIB version 2.0 (1993), preserved in a mirror of the IETF private MIB archive. The archive does not make this vendor file an IETF standard; applicability is limited to the products named in the file. The original omits imports for enterprises, system and interfaces. These three standard roots are supplied from RFC 1065 and RFC 1066 for this exact reviewed file only.
· Download Retix Local Bridge MIB version 2.0 — historical IETF archiveRelated source files and packages:
Status in source: mandatory.
Names: snmpAccessPolicyType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"snmpAccessPolicyType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"\"",
"::=",
"{",
"snmpAccessPolicyEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
""
],
null,
null,
null,
null
]
}Module: RETIX-LOCAL-ROUTER-MIB
See published definition above
{'RFC1065-SMI': ['mgmt', 'OBJECT-TYPE', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: Historical Retix Local Bridge/Router MIB version 1.0, dated 12 January 1993, preserved in a mirror of the IETF private MIB archive. The archive does not make this vendor file an IETF standard. Its DESCRIPTION clauses are empty. It uses the standard internet root without importing it; this root is supplied from RFC 1065 for this exact reviewed file only.
· Download Retix Local Router MIB version 1.0 — historical IETF archiveRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.72.9.5.3.1.1.1 | accessPolicyIndex | 0 | 0 | |
| 1.3.6.1.4.1.72.9.5.3.1.1.2 | communityName | 0 | 0 | |
| 1.3.6.1.4.1.72.9.5.3.1.1.3 | accessMode | 0 | 0 |