ALCATEL-IND1-VLAN-STACKING-MIB

All MIBs › ALCATEL-IND1-VLAN-STACKING-MIB

Organization: Alcatel-Lucent

Last Updated: 2007-04-03

Category: VLAN and Bridging, Vendor: Alcatel-Lucent

Description: Alcatel OmniSwitch VLAN stacking (QinQ) MIB for managing provider-edge 802.1ad double-tagged service VLANs.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ALCATEL-IND1-VLAN-STACKING-MIB?

ALCATEL-IND1-VLAN-STACKING-MIB is an Alcatel-Lucent OmniSwitch MIB for VLAN Stacking (QinQ, 802.1ad double-tagging), used on provider-edge switches to map customer traffic on access ports into service VLANs (SVLANs) for transport across a provider network. It exposes per-port configuration such as port type (access/network), VLAN TPID, default SVLAN assignment, and BPDU handling, alongside per-port-per-SVLAN mapping tables. As primarily a configuration MIB it doesn't expose hardware environmentals or CPU/memory, but administrators can monitor operational parameters such as lookup-miss counts and row status to detect misconfigured or inactive stacking ports and abnormal BPDU handling across the customer/provider boundary. It builds on the standard 802.1ad double-tagging concept and interoperates with the underlying bridge/VLAN MIBs for actual frame forwarding. It is deployed on Alcatel-Lucent OmniSwitch platforms at network edges providing metro Ethernet/QinQ services. Engineers can download the ALCATEL-IND1-VLAN-STACKING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ALCATEL-IND1-VLAN-STACKING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Alcatel-Lucent OmniSwitch

Monitoring Examples

alaVstkPortTable/alaVstkPortEntry exposes alaVstkPortType (access vs. network port) and alaVstkPortDefaultSvlan, letting an admin verify a customer access port is correctly stacking into the intended service VLAN. alaVstkPortLookupMiss increments when frames arrive that don't match a configured SVLAN mapping - a rising count indicates misconfigured customer tags or a provisioning mismatch. alaVstkPortAcceptFrameType and alaVstkPortBpduTreatment reveal whether a port is dropping unexpected frame types or mishandling spanning-tree BPDUs across the stacked boundary, and alaVstkPortRowStatus shows whether a given stacking configuration row is currently active.

What Can Be Monitored

port stacking type (access/network)
default SVLAN assignment
VLAN lookup-miss count
BPDU treatment mode
frame acceptance type
port row status

Imported Objects

From ALCATEL-IND1-BASE

softentIND1VlanStackingMgt

OBJECT-IDENTITY

From IF-MIB

InterfaceIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
alcatelIND1VLANStackingMIB	1.3.6.1.4.1.6486.801.1.2.1.37.1			The parameters for configuration of the VLAN Stacking feature, including the association between ports and svlans. The right to make changes in specification and other information contained in this document without prior notice is reserved. No liability shall be assumed for any incidental, indirect, special, or consequential damages whatsoever arising from or related to this document or the information contained herein. Vendors, end-users, and other interested parties are granted non-exclusive license to use this specification in connection with management of the products for which it is intended to be used. Copyright (C) 1995-2006 Alcatel-Lucent ALL RIGHTS RESERVED WORLDWIDE
alcatelIND1VLANStackingMIBObjects	1.3.6.1.4.1.6486.801.1.2.1.37.1.1			Branch For VLAN Stacking Managed Objects.
alaVlanStackingPort	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1
alaVstkPortTable	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1		not-accessible	A table that contains port-specific information for the VLAN Stacking feature. An entry in this table is created when a port is configured with VLAN stacking capability, OR when a port is configured with a specific vendor ethertype, a particular bridge protocol action.
alaVstkPortEntry	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1		not-accessible	A VLAN Stacking port entry.
NUM alaVstkPortNumber	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.1	InterfaceIndex	read-only	The port ifindex of the port for which this entry contains VLAN Stacking management information.
INT alaVstkPortType	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.2	INTEGER	read-write	The type of this VLAN Stacking port. User-customer (1) is a VLAN Stacking user port connected to customer network. User-provider (2) is a VLAN Stacking user port used to run provider management traffic. Network (2) indicates a network facing port.
I32 alaVstkPortVendorTpid	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.3	Integer32	read-write	The TPID for this port. It is used for the incoming data traffic parsing and it is substituted to the 802.1Q standard Tpid for the outgoing data traffic. This is used for compatibility with other vendor equipment. The default value is the standard value 0x88a8.
INT alaVstkPortBpduTreatment	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.4	INTEGER	read-write	The customer bpdu treatment for this port. It defines the type of processing applied to the user's bridge protocol data unit. The bridge protocol treatment (flooded) floods any user's bridge protocol data unit to all user ports and network ports on the same SVLAN. The bridge protocol (dropped) drops any user's bridge protocol data unit.
INT alaVstkPortAcceptFrameType	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.5	INTEGER	read-write	The acceptable frame types on this port.
INT alaVstkPortLookupMiss	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.6	INTEGER	read-write	Treatment of tagged packets upon vlan lookup miss. Drop (1) means that on lookup miss the packets will be dropped. Default (2) means that on lookup miss the default SVLAN for that port will be used to tunnel the packets. This is significant only for user port.
INT alaVstkPortDefaultSvlan	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.7	INTEGER	read-write	The default svlan of this port.
ROW alaVstkPortRowStatus	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.8	RowStatus	read-write	The status of this table entry. The supported value supported for set are createAndGo (4) and destroy(6), to create or remove a vlan-stacking port.
INT alaVstkPortLegacyStpBpdu	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.1.1.1.9	INTEGER	read-write	The legacy STP BPDU treatment for this port. It defines the type of processing applied to STP legacy BPDUs on network ports. Legacy BPDU refer to conventional/customer BPDUs with MAC address 01:80:c2:00:00:00 and its processing on network ports can be enabled/disabled by this object.By default the value is disabled i.e provider MAC BPDU with MAC address 01:80:c2:00:00:08 would be processed at network ports.
alaVlanStackingSvlanPort	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2
alaVstkSvlanPortTable	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1		not-accessible	A table that contains svlan/ipmvlan-port association for the VLAN Stacking feature.
alaVstkSvlanPortEntry	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1		not-accessible	The svlan/ipmvlan-port association.
INT alaVstkSvlanPortSvlanNumber	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1.1	INTEGER	read-only	Number identifying the svlan/ipmvlan.
NUM alaVstkSvlanPortPortNumber	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1.2	InterfaceIndex	read-only	The port ifindex of the port associated to the svlan/ipmvlan.
INT alaVstkSvlanPortCvlanNumber	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1.3	INTEGER	read-only	The customer vlan id associated to the svlan/ipmvlan.
INT alaVstkSvlanPortMode	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1.4	INTEGER	read-write	The vlan stacking mode: double tagging (1) or vlan translation/mapping (2). Only translation mode is valid in case of IPM Vlans
ROW alaVstkSvlanPortRowStatus	1.3.6.1.4.1.6486.801.1.2.1.37.1.1.2.1.1.5	RowStatus	read-write	The status of this table entry. The supported value for set are createAndGo (4) and destroy(6), to add or remove an svlan-port association.
alcatelIND1VLANStackingMIBConformance	1.3.6.1.4.1.6486.801.1.2.1.37.1.2			Branch For VLAN Stacking Conformance Information.
alcatelIND1VLANStackingMIBGroups	1.3.6.1.4.1.6486.801.1.2.1.37.1.2.1			Branch For VLAN Stacking Units Of Conformance.
vlanStackingPortGroup	1.3.6.1.4.1.6486.801.1.2.1.37.1.2.1.1			Collection of objects for management of VLAN Stacking Ports.
vlanStackingSvlanPortGroup	1.3.6.1.4.1.6486.801.1.2.1.37.1.2.1.2			Collection of objects for svlan-port associations.
alcatelIND1VLANStackingMIBCompliances	1.3.6.1.4.1.6486.801.1.2.1.37.1.2.2			Branch For VLAN Stacking Compliance Statements.
alcatelIND1VLANStackingMIBCompliance	1.3.6.1.4.1.6486.801.1.2.1.37.1.2.2.1			Compliance statement for VLAN Stacking.

RFC description

Configures VLAN stacking and port-to-SVLAN associations on Alcatel switches.

Start monitoring Alcatel-Lucent Enterprise OmniSwitch switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ALCATEL-IND1-VLAN-STACKING-MIB

What Is ALCATEL-IND1-VLAN-STACKING-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description