BAY-STACK-LLDP-EXT-MED-MIB

All MIBs › BAY-STACK-LLDP-EXT-MED-MIB

Organization: Nortel Ltd.

Last Updated: 2009-03-30

Category: Vendor: Avaya

Description: Extends LLDP with LLDP-MED TLVs for network policy and location on Avaya/Nortel ERS switches.

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 BAY-STACK-LLDP-EXT-MED-MIB?

BAY-STACK-LLDP-EXT-MED-MIB is an Avaya/Nortel Ethernet Routing Switch (ERS) extension to the standard LLDP-MED protocol, adding vendor-specific local media-policy TLVs. It exposes a table of media policy entries covering application type, VLAN ID, Layer 2 priority, DSCP value, and tagging/unknown-policy flags, along with related notifications. Monitoring this data reveals the software-level network-policy configuration being advertised to connected endpoints such as VoIP phones - confirming whether the correct VLAN, priority, and DSCP policy is being applied per application type. It is explicitly built as an extension of the standard LLDP-MED MIB (based on IEEE 802.1AB and the TIA-1057 LLDP-MED specification). It is deployed on enterprise LAN switch ports connecting VoIP phones or other media endpoints that rely on auto-provisioned VLAN/QoS policy, and a BAY-STACK-LLDP-EXT-MED-MIB download is available for administrators who need to load it directly into a MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BAY-STACK-LLDP-EXT-MED-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

Avaya/Nortel Ethernet Routing Switches (ERS)

Monitoring Examples

An administrator reviews bsLldpXMedLocMediaPolicyTable/bsLldpXMedLocMediaPolicyEntry for a switch port, checking bsLldpXMedLocMediaPolicyVlanID, bsLldpXMedLocMediaPolicyPriority, and bsLldpXMedLocMediaPolicyDscp for the entry matching bsLldpXMedLocMediaPolicyAppType (e.g., voice). An entry whose bsLldpXMedLocMediaPolicyRowStatus is not active, or whose VLAN/DSCP values are wrong, would explain a VoIP phone failing to land on the correct voice VLAN or QoS class.

What Can Be Monitored

media policy VLAN ID
media policy priority/DSCP
policy row status
application type mapping

Imported Objects

From DIFFSERV-DSCP-TC

Dscp

From LLDP-EXT-MED-MIB

PolicyAppType

From LLDP-MIB

lldpLocPortNum

OBJECT-TYPE

From Q-BRIDGE-MIB

VlanIdOrAnyOrNone

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
TruthValue

From SYNOPTICS-ROOT-MIB

bayStackMibs

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
bayStackLldpExtMedMib	1.3.6.1.4.1.45.5.33			This MIB module is an extension to the standard LLDP-EXT-MED MIB.
bsLldpExtMedNotifications	1.3.6.1.4.1.45.5.33.0
bsLldpExtMedObjects	1.3.6.1.4.1.45.5.33.1
bsLldpXMedLocMediaPolicyTable	1.3.6.1.4.1.45.5.33.1.1		not-accessible	This table contains one row per policy type per port of media policy information (as a part of the MED organizational extension) on the local system known to this agent.
bsLldpXMedLocMediaPolicyEntry	1.3.6.1.4.1.45.5.33.1.1.1		not-accessible	Information about a particular policy on a specific port component.
POL bsLldpXMedLocMediaPolicyAppType	1.3.6.1.4.1.45.5.33.1.1.1.1	PolicyAppType	not-accessible	The media type that defines the primary function of the application for the policy advertised by an endpoint.
VLA bsLldpXMedLocMediaPolicyVlanID	1.3.6.1.4.1.45.5.33.1.1.1.2	VlanIdOrAnyOrNone	read-create	An extension of the VLAN Identifier for the port, as defined in IEEE 802.1P-1998. A value of 1 through 4094 is used to define a valid PVID. A value of 0 shall be used if the device is using priority tagged frames, meaning that only the 802.1p priority level is significant and the default VID of the ingress port is being used instead. A value of 4095 is reserved for implementation use.
I32 bsLldpXMedLocMediaPolicyPriority	1.3.6.1.4.1.45.5.33.1.1.1.3	Integer32	read-create	This object contains the value of the 802.1p priority which is associated with the given port on the local system.
DSC bsLldpXMedLocMediaPolicyDscp	1.3.6.1.4.1.45.5.33.1.1.1.4	Dscp	read-create	This object contains the value of the Differentiated Service Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475 which is associated with the given port on the local system.
T/F bsLldpXMedLocMediaPolicyUnknown	1.3.6.1.4.1.45.5.33.1.1.1.5	TruthValue	read-create	A value of 'true' indicates that the network policy for the specified application type is currently unknown. In this case, the VLAN ID, the layer 2 priority and the DSCP value fields are ignored. A value of 'false' indicates that this network policy is defined
T/F bsLldpXMedLocMediaPolicyTagged	1.3.6.1.4.1.45.5.33.1.1.1.6	TruthValue	read-create	A value of 'true' indicates that the application is using a tagged VLAN. A value of 'false' indicates that for the specific application the device either is using an untagged VLAN or does not support port based VLAN operation. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value has relevance
ROW bsLldpXMedLocMediaPolicyRowStatus	1.3.6.1.4.1.45.5.33.1.1.1.7	RowStatus	read-create	This object is used to create/delete entries in this table. Note that all columns in an entry must be set before an entry can be made valid. Also note that while an entry is valid, any column in the entry may be modified.

RFC description

Bay Networks Stack LLDP Media Endpoint Devices (LLDP-MED) extension MIB. Manages LLDP-MED discovery and configuration for voice/data endpoints on Bay switch stacks.

Start monitoring Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) 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 BAY-STACK-LLDP-EXT-MED-MIB

What Is BAY-STACK-LLDP-EXT-MED-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description