OID reference
1.3.6.1.4.1.4526.17.209.1.1.3
Contains the Rule management channel type as described in RlSecSdChannelType. secure-xml-snmp and insecure-xml-snmp management channels have no include-encrypted capability thus their rlSecSdRulePermitRead and rlSecSdRuleRead can have only RlSecSdAccessType values of exclude or include-decrypted.
Identification
{1 3 6 1 4 1 4526 17 209 1 1 3}
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.
rlSecSdRuleChannel OBJECT-TYPE
SYNTAX RlSecSdChannelType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Contains the Rule management channel type as described in RlSecSdChannelType.
secure-xml-snmp and insecure-xml-snmp management channels have no include-encrypted capability
thus their rlSecSdRulePermitRead and rlSecSdRuleRead can have only RlSecSdAccessType values of
exclude or include-decrypted."
::= { rlSecSdRulesEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Contains the Rule management channel type as described in RlSecSdChannelType. secure-xml-snmp and insecure-xml-snmp management channels have no include-encrypted capability thus their rlSecSdRulePermitRead and rlSecSdRuleRead can have only RlSecSdAccessType values of exclude or include-decrypted.
NETGEAR MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rlSecSdRuleChannel
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlSecSdRuleChannel",
"OBJECT-TYPE",
"SYNTAX",
"RlSecSdChannelType",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Contains the Rule management channel type as described in RlSecSdChannelType. secure-xml-snmp and insecure-xml-snmp management channels have no include-encrypted capability thus their rlSecSdRulePermitRead and rlSecSdRuleRead can have only RlSecSdAccessType values of exclude or include-decrypted.\"",
"::=",
"{",
"rlSecSdRulesEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"RlSecSdChannelType"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Contains the Rule management channel type as described in RlSecSdChannelType. secure-xml-snmp and insecure-xml-snmp management channels have no include-encrypted capability thus their rlSecSdRulePermitRead and rlSecSdRuleRead can have only RlSecSdAccessType values of exclude or include-decrypted."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. NETGEAR support.
Module: NETGEAR-RADLAN-SECSD-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['OBJECT-TYPE'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'NETGEAR-RADLAN-MIB': ['rnd']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4526.17.209.1.1.1 | rlSecSdRuleUser | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.2 | rlSecSdRuleUserName | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.4 | rlSecSdRuleRead | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.5 | rlSecSdRulePermitRead | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.6 | rlSecSdRuleIsDefault | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.7 | rlSecSdRuleOwner | 0 | 0 | |
| 1.3.6.1.4.1.4526.17.209.1.1.8 | rlSecSdRuleStatus | 0 | 0 |