OID reference
1.3.6.1.4.1.3902.1015.32.7
This field is designed for Deutsche Telekom. By using the DHCP relay agent function the device must be able to create the CID and the RID as described in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier. Access-Node-Identifier which is required by Deutsche Telekom consists of two IDs:Access-Node-ID1 and A…
Identification
{1 3 6 1 4 1 3902 1015 32 7}
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.
zxAnPortIdAccessNodeSlaveId OBJECT-TYPE
SYNTAX DisplayString ( SIZE ( 1 .. 50 ) )
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This field is designed for Deutsche Telekom.
By using the DHCP relay agent function the device
must be able to create the CID and the RID as described
in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier.
Access-Node-Identifier which is required by Deutsche Telekom
consists of two IDs:Access-Node-ID1 and Access-Node-ID2.
This field indicates Access-Node-ID2."
DEFVAL { "" }
::= { zxAnPortLocatingMib 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This field is designed for Deutsche Telekom. By using the DHCP relay agent function the device must be able to create the CID and the RID as described in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier. Access-Node-Identifier which is required by Deutsche Telekom consists of two IDs:Access-Node-ID1 and Access-Node-ID2. This field indicates Access-Node-ID2.
ZTE MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: zxAnPortIdAccessNodeSlaveId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnPortIdAccessNodeSlaveId",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"(",
"SIZE",
"(",
"1",
".",
".",
"50",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This field is designed for Deutsche Telekom. By using the DHCP relay agent function the device must be able to create the CID and the RID as described in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier. Access-Node-Identifier which is required by Deutsche Telekom consists of two IDs:Access-Node-ID1 and Access-Node-ID2. This field indicates Access-Node-ID2.\"",
"DEFVAL",
"{",
[
"literal",
"2222"
],
"}",
"::=",
"{",
"zxAnPortLocatingMib",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"DisplayString",
[
"octetStringSubType",
[
[
1,
50
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This field is designed for Deutsche Telekom. By using the DHCP relay agent function the device must be able to create the CID and the RID as described in BBF TR-101 and TR-156.The CID contains Access-Node-Identifier. Access-Node-Identifier which is required by Deutsche Telekom consists of two IDs:Access-Node-ID1 and Access-Node-ID2. This field indicates Access-Node-ID2."
],
null,
null,
null,
[
"DEFVAL",
"\"\""
]
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-PORT-LOCATING-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'Integer32'], 'ZTE-AN-TC-MIB': ['ZxAnIfindex', 'zxAn']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1015.32.1 | zxAnPortIdAccessNodeName | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.2 | zxAnPortIdAccessNodeIdType | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.3 | zxAnPortIdRack | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.4 | zxAnPortIdShelf | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.5 | zxAnPortLocatingCircuitIdSyntaxEnable | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.6 | zxAnPortLocatingAccessLoopEncapsulationEnable | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.8 | zxAnPortIdDhcpV4AccessLoopChar | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.9 | zxAnPortIdPppoeAccessLoopChar | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.32.20 | zxAnPortLocatingTable | 1 | 9 | |
| 1.3.6.1.4.1.3902.1015.32.21 | zxAnDhcpMib | 8 | 25 | |
| 1.3.6.1.4.1.3902.1015.32.22 | zxAnPortLocatingCircuitIdSyntaxTable | 1 | 8 | |
| 1.3.6.1.4.1.3902.1015.32.25 | zxAnVlanPortLocatingObjects | 2 | 5 | |
| 1.3.6.1.4.1.3902.1015.32.40 | zxAnPppoePlusMib | 2 | 7 | |
| 1.3.6.1.4.1.3902.1015.32.45 | zxAnPortLocatingNdpMib | 2 | 14 |