Home/Catalog/BAY-STACK-ADAC-MIB

BAY-STACK-ADAC-MIB

AI MIB Summary

The BAY-STACK-ADAC-MIB facilitates the automated discovery and dynamic configuration of Avaya IP telephony endpoints within Avaya Ethernet Routing Switch (ERS) environments. It exposes management objects that enable network devices to detect connected Avaya phones, retrieve their specific configuration parameters, and provision them without manual intervention.

Avaya Auto-Discovery/Auto-Configuration of Avaya IP Phones MIB Copyright 2014 Avaya. All rights reserved. This Avaya SNMP Management Information Base Specification embodies Avaya confidential and proprietary intellectual property. Avaya retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Avaya makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
Main OID:
bayStackAdacMib.bayStackMibs.9
34
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

34 total
Object Name
bayStackAdacMibAvaya Auto-Discovery/Auto-Configuration of Avaya IP Phones MIB Copyright 2014 Avaya. All rights reserved. This Avaya SNMP Management Information Base Specification embodies Avaya confidential and proprietary intellectual property. Avaya retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Avaya makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
MODULE-IDENTITY
.bayStackMibs.9
IMPORTSAvaya Auto-Discovery/Auto-Configuration of Avaya IP Phones MIB Copyright 2014 Avaya. All rights reserved. This Avaya SNMP Management Information Base Specification embodies Avaya confidential and proprietary intellectual property. Avaya retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Avaya makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
Unknown
.bayStackMibs.9
bsAdacNotifications
OBJECT IDENTIFIER
.bayStackMibs.9.0
bsAdacPortConfigNotificationThis notification indicates if the Auto-Configuration is applied or not on the port. It will be sent on every status change.
NOTIFICATION-TYPE
.bayStackMibs.9.0.1
bsAdacPortOperDisabledNotificationThis notification indicates if a port having bsAdacPortAdminEnable set to true(1) changes its bsAdacPortOperEnable from true(1) to false(2) due to some condition such as reaching the maximum number of devices supported per port.
NOTIFICATION-TYPE
.bayStackMibs.9.0.2
bsAdacObjects
OBJECT IDENTIFIER
.bayStackMibs.9.1
bsAdacScalars
OBJECT IDENTIFIER
.bayStackMibs.9.1.1
bsAdacAdminEnableThis object is used to administratively enable or disable ADAC. A value of true(1) means ADAC should be enabled, while a value of false(2) means ADAC should be disabled. Note that ADAC might remain operationally disabled due to other conditions (such as missing Uplink and Call Server ports). To determine whether ADAC is operationally enabled, see bsAdacOperEnable.rw
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.1.2
bsAdacOperatingModeThis operating mode must be set depending on how the IP Phones are configured to send frames (tagged/untagged) and on the desired level of complexity for auto-configuration. A value of untaggedFramesBasic(1) means that the IP Phones are configured to send untagged frames and no Voice-VLAN will be created (only apply QoS). A value of untaggedFramesAdvanced(2) means that the IP Phones are configured to send untagged frames and the Voice-VLAN will be created too, beside applying QoS. A value of taggedFrames(3) means that the IP Phones are configured to send tagged frames; the Voice-VLAN will be created and QoS will be applied accordingly. This object cannot take the value untaggedFramesAdvanced(2) or taggedFrames(3) if bsAdacVoiceVlan has the value 0, or if both bsAdacCallServerPort and bsAdacUplinkPort have the value 0.rw
Enumeration
.bayStackMibs.9.1.1.3
bsAdacCallServerPortThe port on which the Call Server is connected. This value is used only when the current operating mode is either untaggedFramesAdvanced(2) or taggedFrames(3). It may not be changed to 0 if the current operating mode is one of these values. Note that an implementation should support either bsAdacCallServerPort and bsAdacUplinkPort, or bsAdacCallServerPortList and bsAdacUplinkPortList, but not both.rw
InterfaceIndexOrZero (IF-MIB)
.bayStackMibs.9.1.1.4
bsAdacUplinkPortThe uplink port is used usually when the Call Server is not connected directly to the current module/stack. This value is used only when the current operating mode is either untaggedFramesAdvanced(2) or taggedFrames(3). It may not be changed to 0 if the current operating mode is one of these values. Note that an implementation should support either bsAdacCallServerPort and bsAdacUplinkPort, or bsAdacCallServerPortList and bsAdacUplinkPortList, but not both.rw
InterfaceIndexOrZero (IF-MIB)
.bayStackMibs.9.1.1.5
bsAdacVoiceVlanA value that uniquely identifies the Voice Virtual LAN associated with ADAC. This value it is used only when the current operating mode is untaggedFramesAdvanced(2) or taggedFrames(3). It may not be changed to 0 if the current operating mode is one of these values.rw
VlanIdOrNone (Q-BRIDGE-MIB)
.bayStackMibs.9.1.1.6
bsAdacNotificationControlEnableThis object controls whether port status changes will result in generation of a bsAdacPortConfigNotification. The value true(1) means that the notifications will be generated. The value false(2) means that they will not be generated.rw
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.1.7
bsAdacMacAddrRangeControlThis object always returns none(1) when retrieved. When set to clearTable(2), it will delete all entries from the bsAdacMacAddrRangeTable. When set to defaultTable(3), it will delete all entries from the bsAdacMacAddrRangeTable and replace them with factory default entries.rw
Enumeration
.bayStackMibs.9.1.1.8
bsAdacOperEnableThis object indicates whether ADAC is operationally enabled. A value of true(1) indicates that it is enabled, while a value of false(2) indicates that it is disabled. Note a value of false(2) for this object and a value of true(1) for bsAdacAdminEnable indicates that ADAC is not operational due to some condition such as missing Uplink and Call Server ports.ro
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.1.9
bsAdacCallServerPortListThe ports on which the Call Server is connected. This value is used only when the current operating mode is either untaggedFramesAdvanced(2) or taggedFrames(3). It may not be changed to an empty set of ports if the current operating mode is one of these values. Note that an implementation should support either bsAdacCallServerPort and bsAdacUplinkPort, or bsAdacCallServerPortList and bsAdacUplinkPortList, but not both.rw
PortList (Q-BRIDGE-MIB)
.bayStackMibs.9.1.1.10
bsAdacUplinkPortListThe uplink ports are used usually when the Call Server is not connected directly to the current module/stack. This value is used only when the current operating mode is either untaggedFramesAdvanced(2) or taggedFrames(3). It may not be changed to an empty set of ports if the current operating mode is one of these values. Note that an implementation should support either bsAdacCallServerPort and bsAdacUplinkPort, or bsAdacCallServerPortList and bsAdacUplinkPortList, but not both.rw
PortList (Q-BRIDGE-MIB)
.bayStackMibs.9.1.1.11
bsAdacUplinkTypeThe ADAC uplink type. A value of port(1) means that the ADAC uplink is the clasical port type uplink. bsAdacUplinkPortList will be used to specify the actual uplink ports list. A value of spbm(2) means that the uplink is over SPBM. With this we inform ADAC that instead of a classical uplink-port it will use an I-SID that will have to be associated by the user with the ADAC Voice-VLAN. When setting the ADAC uplink over SPBM, all the currently set uplink ports will be removed.rw
Enumeration
.bayStackMibs.9.1.1.12
bsAdacPortTableA table of objects that display and control the port attributes of ADAC.
SEQUENCE OF BsAdacPortEntry
.bayStackMibs.9.1.2
bsAdacPortEntryA set of objects that display and control the port attributes of ADAC.
BsAdacPortEntry
.bayStackMibs.9.1.2.1
bsAdacPortIndexAn index value that uniquely identifies a port. This value is similar to ifIndex in MIB2.
InterfaceIndex (IF-MIB)
.bayStackMibs.9.1.2.1.1
bsAdacPortAdminEnabletrue (1) Auto-Detection (and implicitly Auto-Configuration) of Avaya IP Phones is enabled on this interface. false (2) Auto-Detection (and implicitly Auto-Configuration) of Avaya IP Phones is disabled on this interface.rw
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.2.1.2
bsAdacPortConfigStatusDescribes the Auto-Configuration status for the port. A value of configApplied(1) means that the ADAC configuration is applied for this port. A value of configNotApplied(2) means that the ADAC configuration is not applied for this port.ro
Enumeration
.bayStackMibs.9.1.2.1.3
bsAdacPortTaggedFramesPvidThis is the PVID value that Auto-Configuration will try to apply for ports which have Auto-Detection enabled (bsAdacPortAdminEnable is set to true(1)), and which are running in Tagged-Frames operational mode (bsAdacOperatingMode is set to taggedFrames(3)). A value of 0 means that the Auto-Configuration will not change the PVID of the respective port. If the VLAN with the ID equal with this PVID does not exist when Auto-Configuration is applied to a port, then Auto-Configuration won't change the port's PVID (it will ignore the current value of this object, and treat it as if its value is currently 0).rw
Integer32
.bayStackMibs.9.1.2.1.4
bsAdacPortTaggedFramesTaggingThis is the tagging value that Auto-Configuration will apply for ports which have Auto-Detection enabled (bsAdacPortAdminEnable is set to true(1)), and which are running in Tagged-Frames operational mode (bsAdacOperatingMode is set to taggedFrames(3)). A value of tagAll(1) means that the Telephony ports will have the tagging enabled on all frames. A value of tagPvidOnly(2) means that the Telephony ports will have the tagging enabled on frames matching the PVID of the port. A value of untagPvidOnly(3) means that the Telephony ports will have the tagging disabled on frames matching the PVID of the port. A value of noChange(4) means that the Auto-Configuration will not change the tagging of the respective port.rw
Enumeration
.bayStackMibs.9.1.2.1.5
bsAdacPortTypeDescribes how ADAC classifies this port. A value of telephony(1) means that the Auto-Detection is enabled for this port (bsAdacPortAdminEnable is set to true(1)). A value of callServer(2) means that the port is configured as Call Server. A value of uplink(3) means that the port is either configured as Uplink or it's part of the same trunk as the current set Uplink port. A value of other(4) means that the port has none of the types above.ro
Enumeration
.bayStackMibs.9.1.2.1.6
bsAdacPortOperEnableThis object indicates whether Auto-Detection is operationally enabled on port. A value of true(1) indicates that it is enabled, while a value of false(2) indicates that it is disabled. Note a value of false(2) for this object and a value of true(1) for bsAdacPortAdminEnable indicates that Auto-Detection (and implicitly Auto-Configuration) is not operational due to some condition such as reaching the maximum number of devices supported per port.ro
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.2.1.7
bsAdacPortMacDetectionEnabletrue (1) Auto-Detection of Avaya IP Phones based on MAC Address is enabled on this interface. false (2) Auto-Detection of Avaya IP Phones based on MAC Address is disabled on this interface. It cannot be set to false(2) if no other supported detection mechanism is enabled on port.rw
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.2.1.8
bsAdacPortLldpDetectionEnabletrue (1) Auto-Detection of Avaya IP Phones based on 802.1ab is enabled on this interface. false (2) Auto-Detection of Avaya IP Phones based on 802.1ab is disabled on this interface. It cannot be set to false(2) if no other supported detection mechanism is enabled on port.rw
TruthValue (SNMPv2-TC)
.bayStackMibs.9.1.2.1.9
bsAdacMacAddrRangeTableA table of objects that display and control the attributes of the MAC Address ranges supported by ADAC. Overlapping ranges are not allowed and the attempts to create an entry that overlaps an existing entry will fail.
SEQUENCE OF BsAdacMacAddrRangeEntry
.bayStackMibs.9.1.3
bsAdacMacAddrRangeEntryA set of objects that display and control the attributes of the MAC Address ranges supported by ADAC.
BsAdacMacAddrRangeEntry
.bayStackMibs.9.1.3.1
bsAdacMacAddrRangeLowEndIndexThe low end of the MAC Address range.
MacAddress (SNMPv2-TC)
.bayStackMibs.9.1.3.1.1
bsAdacMacAddrRangeHighEndIndexThe high end of the MAC Address range.
MacAddress (SNMPv2-TC)
.bayStackMibs.9.1.3.1.2
bsAdacMacAddrRangeRowStatusThis is used to control creation/deletion of entries in this table.rw
RowStatus (SNMPv2-TC)
.bayStackMibs.9.1.3.1.3
BAY-STACK-ADAC-MIB - SNMP MIB Reference | MIBs Explorer