OID reference
1.3.6.1.4.1.29601.2.41.1.4
This Object is used to configure the port on which the DHCPv6 relay agent will listen on. This is in order to facilitate DHCPv6 relay to coexist with the DHCPv6 server which can listen on a different port.
Identification
{1 3 6 1 4 1 29601 2 41 1 4}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.29601.2.41.1.4.0
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.
fsDhcp6RlyListenPort OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This Object is used to configure the port on which the
DHCPv6 relay agent will listen on. This is in order to facilitate
DHCPv6 relay to coexist with the DHCPv6 server which can listen on a
different port."
DEFVAL { 547 }
::= { fsDhcp6RlySystem 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This Object is used to configure the port on which the DHCPv6 relay agent will listen on. This is in order to facilitate DHCPv6 relay to coexist with the DHCPv6 server which can listen on a different port.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: fsDhcp6RlyListenPort
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsDhcp6RlyListenPort",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"1",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This Object is used to configure the port on which the DHCPv6 relay agent will listen on. This is in order to facilitate DHCPv6 relay to coexist with the DHCPv6 server which can listen on a different port.\"",
"DEFVAL",
"{",
"547",
"}",
"::=",
"{",
"fsDhcp6RlySystem",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
1,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This Object is used to configure the port on which the DHCPv6 relay agent will listen on. This is in order to facilitate DHCPv6 relay to coexist with the DHCPv6 server which can listen on a different port."
],
null,
null,
null,
[
"DEFVAL",
547
]
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-DHCPv6-RELAY-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'enterprises', 'NOTIFICATION-TYPE']}Related source files and packages:
Module: ARICENT-DHCPv6-RELAY-MIB
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'enterprises', 'NOTIFICATION-TYPE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.29601.2.41.1.1 | fsDhcp6RlyDebugTrace | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.2 | fsDhcp6RlyTrapAdminControl | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.3 | fsDhcp6RlySysLogAdminStatus | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.5 | fsDhcp6RlyClientTransmitPort | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.6 | fsDhcp6RlyServerTransmitPort | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.7 | fsDhcp6RlyOption37Control | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.41.1.8 | fsDhcp6RlyPDRouteControl | 0 | 0 |