BAY-STACK-LLDP-X-AVAYA-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BAY-STACK-LLDP-X-AVAYA-MIB

Organization: Nortel Ltd.

Last Updated: 2015-02-24

Category: Vendor: Avaya

Description: Defines Avaya-proprietary LLDP extensions for IP phone auto-configuration 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-X-AVAYA-MIB?

BAY-STACK-LLDP-X-AVAYA-MIB is an Avaya/Nortel proprietary extension to the standard LLDP-MIB and LLDP-EXT-MED framework, adding vendor-specific TLVs used mainly for Avaya IP telephony auto-configuration and, in later revisions, Fabric Attach (FA) network auto-provisioning. Its bsLldpXAvayaPortConfigTable augments the standard lldpPortConfigEntry with a bsLldpXAvayaPortConfigTLVsTxEnable bitmap controlling which Avaya TLVs (PoE conservation level, call server, file server, 802.1Q framing, Fabric Attach element type, and FA I-SID/VLAN assignments) are transmitted on a port. Local device data is captured in tables such as bsLldpXAvayaLocPortTable (PoE conservation level and dot1Q framing requested toward the connected IP phone, via bsLldpXAvayaLocPortPoeConsLevelRequest and bsLldpXAvayaLocPortDot1QFramingRequest) and bsLldpXAvayaLocCallServerTable (up to eight call-server InetAddress entries advertised to Avaya endpoints). It depends on LLDP-MIB for local/remote port indexing (lldpLocPortNum, lldpRemIndex, etc.) and INET-ADDRESS-MIB for address typing, and on SYNOPTICS-ROOT-MIB for its Bay Networks-heritage registration point. It is deployed on Avaya (formerly Nortel/Bay Networks) Ethernet Routing Switches to auto-configure attached Avaya IP phones and, more recently, Fabric Attach-capable edge devices, and administrators can download the BAY-STACK-LLDP-X-AVAYA-MIB file to load it into their MIB browser to verify call-server TLV advertisement across phone-facing ports.

IPNetwork Monitor allows you to monitor SNMP objects defined in BAY-STACK-LLDP-X-AVAYA-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 (formerly Nortel/Bay Networks) Ethernet Routing Switches

Monitoring Examples

An operator checks bsLldpXAvayaPortConfigTLVsTxEnable on a phone-facing port to confirm the callServer bit is set, then reviews bsLldpXAvayaLocCallServerTable to verify the advertised call-server addresses match the current telephony server; a port missing the callServer bit or advertising a stale call-server address would explain IP phones failing to auto-register.

What Can Be Monitored

  • per-port Avaya TLV transmission enable bitmap
  • PoE conservation level advertised to IP phones
  • 802.1Q framing mode requested from IP phones
  • advertised call-server IP addresses
  • Fabric Attach element type / I-SID-VLAN assignment TLVs
Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressPrefixLength
InetAddressType

From LLDP-MIB

lldpLocPortNumOBJECT-TYPE
lldpPortConfigEntryOBJECT-TYPE
lldpRemIndexOBJECT-TYPE
lldpRemLocalPortNumOBJECT-TYPE
lldpRemTimeMarkOBJECT-TYPE

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SYNOPTICS-ROOT-MIB

bayStackMibsOBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using bsLldpXAvayaLocFaService OID:

Select an Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bsLldpXAvayaLocFaService into the Find box to locate it in the OID tree, then select it and click OK. Exports the status of the Fabric Attach service. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'enabled', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Avaya vendor-specific LLDP extensions for Fabric Attach and device discovery capabilities.

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-X-AVAYA-MIB