OID reference
1.3.6.1.4.1.72.14.10.19.1.10
This parameter is used to indicate whether the entry is to be added or removed from the ipxIfSecurityTable. If the value is valid(1) then this indicates that this is a request to add this entry to the table. A value of valid(1) is always returned to a GetRequest in the case where the entry exists.
Identification
{1 3 6 1 4 1 72 14 10 19 1 10}
| Value | Name |
|---|---|
| 1 | valid |
| 2 | invalid |
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-RX7000-MIB, the row index consists of these components in order:
ipxIfSecurityAccessListNum (INTEGER): one numeric subidentifier for the non-negative value.ipxIfSecurityIndex (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.72.14.10.19.1.10.<ipxIfSecurityAccessListNum>.<ipxIfSecurityIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.72.14.10.19.1.10
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.
The displayed source records contain one distinct definition. Compare its source records.
ipxIfSecurityEntryType OBJECT-TYPE
SYNTAX INTEGER {
valid (1),
invalid (2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This parameter is used to indicate whether the entry is to
be added or removed from the ipxIfSecurityTable. If the value
is valid(1) then this indicates that this is a request to
add this entry to the table. A value of valid(1) is always
returned to a GetRequest in the case where the entry exists."
::= { ipxIfSecurityEntry 10 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This parameter is used to indicate whether the entry is to be added or removed from the ipxIfSecurityTable. If the value is valid(1) then this indicates that this is a request to add this entry to the table. A value of valid(1) is always returned to a GetRequest in the case where the entry exists.
Retix RX7000 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: ipxIfSecurityEntryType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ipxIfSecurityEntryType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"valid",
"(",
"1",
")",
",",
"invalid",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This parameter is used to indicate whether the entry is to be added or removed from the ipxIfSecurityTable. If the value is valid(1) then this indicates that this is a request to add this entry to the table. A value of valid(1) is always returned to a GetRequest in the case where the entry exists.\"",
"::=",
"{",
"ipxIfSecurityEntry",
"10",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"valid",
1
],
[
"invalid",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This parameter is used to indicate whether the entry is to be added or removed from the ipxIfSecurityTable. If the value is valid(1) then this indicates that this is a request to add this entry to the table. A value of valid(1) is always returned to a GetRequest in the case where the entry exists."
],
null,
null,
null,
null
]
}Module: RETIX-RX7000-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['mgmt', 'experimental', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: This is a historical Retix version 3.2 MIB dated 26 July 1995, preserved in a mirror of the IETF private MIB archive. It covers the product and software releases named in the file; the archive does not make it an IETF standard. The author states that the file includes draft MIBs. Its enterprises symbol is used without an IMPORTS declaration; its standard value is supplied from RFC 1155 for this exact reviewed file only.
· Download Retix RX7000 MIB version 3.2 — historical IETF archiveRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.72.14.10.19.1.1 | ipxIfSecurityAccessListNum | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.2 | ipxIfSecurityIndex | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.3 | ipxIfSecuritySrcNwkNum | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.4 | ipxIfSecuritySrcHost | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.5 | ipxIfSecurityDestNwkNum | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.6 | ipxIfSecurityDestHost | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.7 | ipxIfSecurityDestSocket | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.8 | ipxIfSecurityAction | 0 | 0 | |
| 1.3.6.1.4.1.72.14.10.19.1.9 | ipxIfSecurityOperator | 0 | 0 |