Status in source: current.
Names: vlanTLSMode
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vlanTLSMode",
"OBJECT-TYPE",
"SYNTAX",
"VlanTLSMode",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\" This object implements transparent LAN service (TLS) by using a S-Tag (Service Provider tag) to tunnel the customer traffic over a service provider network. The CPE can operate in normal or S-Tag mode. In normal mode, CPE device operates according to the IEEE 802.1Q or 802.1D specifications. In S-TAG mode, the CPE device operates as follows: 1) The CPE's TPID (tag protocol ID) must be provisioned. 2) A S-Tag frame consists of a VLAN ID and a TPID that matches the CPE's provisioned TPID. 3) When the CPE adds a S-TAG, the S-Tag's VLAN ID will be taken from the CPE's default PVID and the TPID will be taken from the CPE's provisioned TPID. 4) The CPE device supports a TLS-Bridge. The ports on this bridge can be either S-TAG or TLS members. S-Tag port - The input frames from the service provider port may or may not have a S-TAG. The CPE will compare the tagged frame's TPID against the provisioned S-TAG TPID. If there is a match, the CPE will bridge the frame based on the VLAN ID in the S-Tag. If there is not a match, the frame is forwarded to the CPU. TLS port - The CPE will add a S-Tag to all input frames from this port regardless of whether the frames have a 802.1Q tag or not. The CPE will bridge the frames based on the VLAN ID in the S-Tag. Only a VLAN-tagged or untagged frames are expected from the ingress of a TLS (customer) port. \"",
"::=",
"{",
"layer2BridgingGlobalObjects",
"1",
"}"
],
"syntax_tree": [
[
"row",
"VlanTLSMode"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object implements transparent LAN service (TLS) by using a S-Tag (Service Provider tag) to tunnel the customer traffic over a service provider network. The CPE can operate in normal or S-Tag mode. In normal mode, CPE device operates according to the IEEE 802.1Q or 802.1D specifications. In S-TAG mode, the CPE device operates as follows: 1) The CPE's TPID (tag protocol ID) must be provisioned. 2) A S-Tag frame consists of a VLAN ID and a TPID that matches the CPE's provisioned TPID. 3) When the CPE adds a S-TAG, the S-Tag's VLAN ID will be taken from the CPE's default PVID and the TPID will be taken from the CPE's provisioned TPID. 4) The CPE device supports a TLS-Bridge. The ports on this bridge can be either S-TAG or TLS members. S-Tag port - The input frames from the service provider port may or may not have a S-TAG. The CPE will compare the tagged frame's TPID against the provisioned S-TAG TPID. If there is a match, the CPE will bridge the frame based on the VLAN ID in the S-Tag. If there is not a match, the frame is forwarded to the CPU. TLS port - The CPE will add a S-Tag to all input frames from this port regardless of whether the frames have a 802.1Q tag or not. The CPE will bridge the frames based on the VLAN ID in the S-Tag. Only a VLAN-tagged or untagged frames are expected from the ingress of a TLS (customer) port."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: ZHNLAYER2BRIDGING
See published definition above
Module imports
{'Zhone': ['zhoneWtn'], 'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'Zhone-TC': ['ZhoneRowStatus'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'MacAddress', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32', 'IpAddress'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
Related source files and packages: