An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points.
Sources for this description
ZTE MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.3902.1004.26.1.1.1
An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points.
Identification
{1 3 6 1 4 1 3902 1004 26 1 1 1}
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.
zxDslAtmVcxEntry OBJECT-TYPE
SYNTAX zxDslAtmVcxEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the ATM VC Cross Connect table.
This entry is used to model a bi-directional ATM
VC cross-connect cross-connecting two end points.
"
INDEX {
zxDslAtmVcxUserSideIfIndex,
zxDslAtmVcxUserSideVpi,
zxDslAtmVcxUserSideVci,
zxDslAtmVcxWanSideIfIndex,
zxDslAtmVcxWanSideVpi,
zxDslAtmVcxWanSideVci }
::= { zxDslAtmVcxTable 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points.
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: zxDslAtmVcxEntry
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxDslAtmVcxEntry",
"OBJECT-TYPE",
"SYNTAX",
"zxDslAtmVcxEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points. \"",
"INDEX",
"{",
"zxDslAtmVcxUserSideIfIndex",
",",
"zxDslAtmVcxUserSideVpi",
",",
"zxDslAtmVcxUserSideVci",
",",
"zxDslAtmVcxWanSideIfIndex",
",",
"zxDslAtmVcxWanSideVpi",
",",
"zxDslAtmVcxWanSideVci",
"}",
"::=",
"{",
"zxDslAtmVcxTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"zxDslAtmVcxEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points."
],
null,
null,
[
"INDEX",
[
[
0,
"zxDslAtmVcxUserSideIfIndex"
],
[
0,
"zxDslAtmVcxUserSideVpi"
],
[
0,
"zxDslAtmVcxUserSideVci"
],
[
0,
"zxDslAtmVcxWanSideIfIndex"
],
[
0,
"zxDslAtmVcxWanSideVpi"
],
[
0,
"zxDslAtmVcxWanSideVci"
]
]
],
null
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-DSL-ATM-MIB
See published definition above
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'TimeTicks', 'Counter32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1004.26.1.1.1.1 | zxDslAtmVcxUserSideIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.2 | zxDslAtmVcxUserSideVpi | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.3 | zxDslAtmVcxUserSideVci | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.4 | zxDslAtmVcxWanSideIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.5 | zxDslAtmVcxWanSideVpi | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.6 | zxDslAtmVcxWanSideVci | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.7 | zxDslAtmVcxAdminStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.8 | zxDslAtmVcxOperStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.26.1.1.1.9 | zxDslAtmVcxRowStatus | 0 | 0 |