AGGREGATED-EXT-MIB

All MIBs › AGGREGATED-EXT-MIB

Organization: Lucent Technologies

Last Updated: 240701

Category: Network Interfaces

Description: Extends aggregated link management with additional LAG/LACP configuration and status objects beyond the base IEEE standard.

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 AGGREGATED-EXT-MIB?

AGGREGATED-EXT-MIB is described as a vendor extension to link aggregation (LAG/LACP) management, but the objects actually registered under it in the source data span a broader set of device-management functions bundled into one 'extension' MIB tree. Alongside any aggregation-related extensions, it carries objects for device/serial identification, firmware or configuration file-transfer administration, and per-trunk H.323/SIP DS1 voice gateway identifiers. Its hardware/software status value comes chiefly from the file-transfer objects (old/new file, host, port, result, and reason), which let an admin confirm whether a firmware or configuration update completed successfully or failed with a specific cause. It is meant to extend the base IEEE 802.3ad link aggregation MIB, though the concrete objects available suggest it also touches unrelated device-identity and voice-trunk functionality on the same platform. It would be deployed on a multi-service access or voice gateway device that combines link aggregation, firmware management, and H.323/SIP voice trunking in a single chassis. Administrators typically start with an AGGREGATED-EXT-MIB download from the platform vendor before compiling this file-transfer, identity, and voice-trunk data into their SNMP management system.

IPNetwork Monitor allows you to monitor SNMP objects defined in AGGREGATED-EXT-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

Multi-service access/voice gateway with link aggregation support

Monitoring Examples

Objects such as pepName, devName, and snName identify the network element and its serial identity; oldFile/newFile/host/port/minutes/result/reason together describe a firmware or configuration file-transfer operation, letting an admin confirm whether a scheduled software download completed successfully or failed with a specific reason code; h323DS1/h323DS2 and sipDS1 expose per-trunk identifiers for H.323 and SIP-signaled DS1 spans on a voice gateway.

What Can Be Monitored

firmware/file transfer result and reason
device/serial identification
H.323 DS1 trunk assignment
SIP DS1 trunk assignment
file transfer duration

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
IpAddress
enterprises

From RFC1213-MIB

DisplayString

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
ObjectName
snmpModules

From SNMPv2-TC

RowStatus
TestAndIncr
TimeStamp
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
cdrDeviceServer	1.3.6.1.4.1.1751.1.1198.7
cdrDS1	1.3.6.1.4.1.1751.1.1198.7.1
cdrDS2	1.3.6.1.4.1.1751.1.1198.7.2
INT code	1.3.6.1.4.1.1751.1.1198.10.2.2	INTEGER	accessible-for-notify
STR comment	1.3.6.1.4.1.1751.1.1198.10.2.6	DisplayString	accessible-for-notify
INT cpuUsage	1.3.6.1.4.1.1751.1.1198.10.3.9	INTEGER	accessible-for-notify	CPU usage percentage
INT csID	1.3.6.1.4.1.1751.1.1198.10.2.3	INTEGER	accessible-for-notify
STR csType	1.3.6.1.4.1.1751.1.1198.10.2.4	DisplayString	accessible-for-notify
INT curSize	1.3.6.1.4.1.1751.1.1198.10.3.5	INTEGER	accessible-for-notify	Gateway type
STR deviceType	1.3.6.1.4.1.1751.1.1198.10.1.16	DisplayString	accessible-for-notify	This is either CC, H323, SS7 or EBGen (the various modules in SARAS)
STR devName	1.3.6.1.4.1.1751.1.1198.10.1.2	DisplayString	accessible-for-notify	Name of the deviceServer the action has occurred on.
STR disk	1.3.6.1.4.1.1751.1.1198.10.3.4	DisplayString	accessible-for-notify	Gateway type
STR domain	1.3.6.1.4.1.1751.1.1198.10.1.17	DisplayString	accessible-for-notify	Name of the domain the action has occurred on.
excel	1.3.6.1.4.1.1751.1.67
excel1	1.3.6.1.4.1.1751.1.67.1
excel2	1.3.6.1.4.1.1751.1.67.2
excel3	1.3.6.1.4.1.1751.1.67.3
excel4	1.3.6.1.4.1.1751.1.67.4
fcDeviceServer	1.3.6.1.4.1.1751.1.1198.9
fcDS1	1.3.6.1.4.1.1751.1.1198.9.1
fcDS2	1.3.6.1.4.1.1751.1.1198.9.2
fcTrapVariables	1.3.6.1.4.1.1751.1.1198.10.4
STR file	1.3.6.1.4.1.1751.1.1198.10.1.3	DisplayString	accessible-for-notify	Name of the file the action has occurred on.
STR group	1.3.6.1.4.1.1751.1.1198.10.1.18	DisplayString	accessible-for-notify	Name of the group the action has occurred on.
STR gwID	1.3.6.1.4.1.1751.1.1198.10.2.7	DisplayString	accessible-for-notify	Gateway ID
IP gwIP	1.3.6.1.4.1.1751.1.1198.10.2.10	IpAddress	accessible-for-notify	Gateway ip address
INT gwType	1.3.6.1.4.1.1751.1.1198.10.2.11	INTEGER	accessible-for-notify	Gateway type
h323DeviceServer	1.3.6.1.4.1.1751.1.1198.3
h323DS1	1.3.6.1.4.1.1751.1.1198.3.1
h323DS2	1.3.6.1.4.1.1751.1.1198.3.2
h323TrapVariables	1.3.6.1.4.1.1751.1.1198.10.2
STR host	1.3.6.1.4.1.1751.1.1198.10.1.4	DisplayString	accessible-for-notify	Name of the host the action has occurred on.
STR lastAggNode	1.3.6.1.4.1.1751.1.1198.100	DisplayString	read-only	This is a flag variable, kept to indicate the end of aggregated mib during a snmpwalk. It always returns the following string: Reached the End of Aggregated MIB
INT load	1.3.6.1.4.1.1751.1.1198.10.3.3	INTEGER	accessible-for-notify	Gateway type
lucent	1.3.6.1.4.1.1751
mantraAdmin	1.3.6.1.4.1.1751.1.1198.99
mantraTraps	1.3.6.1.4.1.1751.1.1198.99.0
mantraTrapVars	1.3.6.1.4.1.1751.1.1198.10.1
STR mateHost	1.3.6.1.4.1.1751.1.1198.10.1.14	DisplayString	accessible-for-notify	Name of the host the action has occurred on.
INT matePort	1.3.6.1.4.1.1751.1.1198.10.1.15	INTEGER	accessible-for-notify	Port number associated with the pep the action has occurred on.
INT maxSize	1.3.6.1.4.1.1751.1.1198.10.3.6	INTEGER	accessible-for-notify	Gateway type
INT memUsage	1.3.6.1.4.1.1751.1.1198.10.3.10	INTEGER	accessible-for-notify	CPU usage percentage
STR minutes	1.3.6.1.4.1.1751.1.1198.10.1.8	DisplayString	accessible-for-notify	Name of the file the action has occurred on.
INT moduleID	1.3.6.1.4.1.1751.1.1198.10.2.8	INTEGER	accessible-for-notify	Gateway ID
STR myHost	1.3.6.1.4.1.1751.1.1198.10.1.12	DisplayString	accessible-for-notify	Name of the host the action has occurred on.
INT myPort	1.3.6.1.4.1.1751.1.1198.10.1.13	INTEGER	accessible-for-notify	Port number associated with the pep the action has occurred on.
STR name	1.3.6.1.4.1.1751.1.1198.10.1.19	DisplayString	accessible-for-notify	Name of the process the action has occurred on.
STR newFile	1.3.6.1.4.1.1751.1.1198.10.1.7	DisplayString	accessible-for-notify	Name of the file the action has occurred on.
STR oldFile	1.3.6.1.4.1.1751.1.1198.10.1.6	DisplayString	accessible-for-notify	Name of the file the action has occurred on.
STR pepName	1.3.6.1.4.1.1751.1.1198.10.1.1	DisplayString	accessible-for-notify	Name of the pep the action has occurred on.
INT percent	1.3.6.1.4.1.1751.1.1198.10.2.9	INTEGER	accessible-for-notify	Gateway ID
INT percentage	1.3.6.1.4.1.1751.1.1198.10.3.1	INTEGER	accessible-for-notify	Gateway type
INT port	1.3.6.1.4.1.1751.1.1198.10.1.5	INTEGER	accessible-for-notify	Port number associated with the pep the action has occurred on.
INT processID	1.3.6.1.4.1.1751.1.1198.10.3.8	INTEGER	accessible-for-notify	processID
STR processName	1.3.6.1.4.1.1751.1.1198.10.3.7	DisplayString	accessible-for-notify	Gateway type
products	1.3.6.1.4.1.1751.1
psaxDeviceServer	1.3.6.1.4.1.1751.1.1198.6
psaxDS1	1.3.6.1.4.1.1751.1.1198.6.1
psaxDS2	1.3.6.1.4.1.1751.1.1198.6.2
STR reason	1.3.6.1.4.1.1751.1.1198.10.1.10	DisplayString	accessible-for-notify	The reason the action was taken.
STR registrationStatus	1.3.6.1.4.1.1751.1.1198.10.2.5	DisplayString	accessible-for-notify
resourceMonitor	1.3.6.1.4.1.1751.1.1198.4
STR result	1.3.6.1.4.1.1751.1.1198.10.1.9	DisplayString	accessible-for-notify	Result of the action taken.
rm1	1.3.6.1.4.1.1751.1.1198.4.1
rm2	1.3.6.1.4.1.1751.1.1198.4.2
rm3	1.3.6.1.4.1.1751.1.1198.4.3
rm4	1.3.6.1.4.1.1751.1.1198.4.4
rmTrapVariables	1.3.6.1.4.1.1751.1.1198.10.3
INT runStatus	1.3.6.1.4.1.1751.1.1198.10.1.20	INTEGER	accessible-for-notify	A short summary of the status of the mantra software modules.
STR sbProducerHost	1.3.6.1.4.1.1751.1.1198.10.4.1	DisplayString	accessible-for-notify	Socket based producer host name
INT sbProducerPort	1.3.6.1.4.1.1751.1.1198.10.4.2	INTEGER	accessible-for-notify	Socket based producer name
sipDeviceServer	1.3.6.1.4.1.1751.1.1198.5
sipDS1	1.3.6.1.4.1.1751.1.1198.5.1
sipDS2	1.3.6.1.4.1.1751.1.1198.5.2
STR snName	1.3.6.1.4.1.1751.1.1198.10.1.11	DisplayString	accessible-for-notify	The reason the action was taken.
softSwitch	1.3.6.1.4.1.1751.1.1198			The MIB module for entities implementing the xxxx protocol.
softswitchTraps	1.3.6.1.4.1.1751.1.1198.10
spinsDeviceServer	1.3.6.1.4.1.1751.1.1198.8
spinsDS1	1.3.6.1.4.1.1751.1.1198.8.1
spinsDS2	1.3.6.1.4.1.1751.1.1198.8.2
INT status	1.3.6.1.4.1.1751.1.1198.10.3.2	INTEGER	accessible-for-notify	Gateway type
STR timeOccurred	1.3.6.1.4.1.1751.1.1198.10.2.1	DisplayString	accessible-for-notify
STR unknownDeviceTrapContents	1.3.6.1.4.1.1751.1.1198.98	DisplayString	read-only	This is a string field (just to have a legal oid) for traps generated neither from SS7 nor from the CC.

FAQ

What is AGGREGATED-EXT-MIB used for on a multi-service access/voice gateway?
Although framed as a link-aggregation (LAG/LACP) extension, the objects it actually registers cover a broader set of functions bundled together: device/serial identification, firmware or configuration file-transfer administration (old/new file, host, port, result, reason), and per-trunk H.323/SIP DS1 voice gateway identifiers. Its main hardware/software-status value is confirming whether a firmware or configuration update completed successfully or failed with a specific reason.

How would I use AGGREGATED-EXT-MIB to confirm a firmware update succeeded?
You'd poll its file-transfer result and reason objects after initiating an update -- these report whether the old-to-new firmware or configuration file transfer completed successfully or failed with a specific reason, alongside device/serial identification and the H.323/SIP DS1 trunk assignments configured on the same voice gateway platform.

RFC description

Extension MIB for managed object aggregation based on RFC 4498.

Start monitoring Lucent Technologies networking equipment 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 AGGREGATED-EXT-MIB

What Is AGGREGATED-EXT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

FAQ

RFC description