Deployment Guide

SNMPv2-SMI::enterprises.6027.3.2.1.1.6.1.3.1107755009.1 = INTEGER: 2 (Tagged 1 or Untagged 2)
dot3aCommonAggFdbStatus
SNMPv2-SMI::enterprises.6027.3.2.1.1.6.1.4.1107755009.1 = INTEGER: 1 << Status active, 2 –
status inactive
If you learn the MAC address for the LAG, the LAG status also displays.
dot3aCurAggVlanId
SNMPv2-SMI::enterprises.6027.3.2.1.1.4.1.1.1.0.0.0.0.0.1.1 = INTEGER: 1
dot3aCurAggMacAddr
SNMPv2-SMI::enterprises.6027.3.2.1.1.4.1.2.1.0.0.0.0.0.1.1 = Hex-STRING: 00 00 00 00 00 01
dot3aCurAggIndex
SNMPv2-SMI::enterprises.6027.3.2.1.1.4.1.3.1.0.0.0.0.0.1.1 = INTEGER: 1
dot3aCurAggStatus
SNMPv2-SMI::enterprises.6027.3.2.1.1.4.1.4.1.0.0.0.0.0.1.1 = INTEGER: 1
<< Status active, 2 –
status
inactive
For L3 LAG, you do not have this support.
SNMPv2-MIB::sysUpTime.0 = Timeticks: (8500842) 23:36:48.42
SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown
IF-MIB::ifIndex.33865785 = INTEGER: 33865785
SNMPv2-SMI::enterprises.6027.3.1.1.4.1.2 = STRING: "OSTATE_DN: Changed interface state to down:
Tengig 0/1"
2010-02-10 14:22:39 10.16.130.4 [10.16.130.4]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (8500842) 23:36:48.42
SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkDown
IF-MIB::ifIndex.1107755009 = INTEGER: 1107755009
SNMPv2-SMI::enterprises.6027.3.1.1.4.1.2 = STRING:
"OSTATE_DN: Changed interface state to down:
Po 1"
2010-02-10 14:22:40 10.16.130.4 [10.16.130.4]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (8500932) 23:36:49.32 SNMPv2-MIB::snmpTrapOID.0 = OID:
IF-MIB::linkUp IF-MIB::ifIndex.33865785 = INTEGER: 33865785 SNMPv2-SMI::enterprises.
6027.3.1.1.4.1.2 =
STRING: "OSTATE_UP: Changed interface state to up: Tengig 0/1"
2010-02-10 14:22:40 10.16.130.4 [10.16.130.4]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (8500934) 23:36:49.34 SNMPv2-MIB::snmpTrapOID.0 = OID:
IF-MIB::linkUp IF-MIB::ifIndex.1107755009 = INTEGER: 1107755009
SNMPv2-SMI::enterprises.6027.3.1.1.4.1.2 = STRING: "
OSTATE_UP: Changed interface state to up:
Po 1"
Entity MIBS
The Entity MIB provides a mechanism for presenting hierarchies of physical entities using SNMP tables. The Entity MIB contains the
following groups, which describe the physical elements and logical elements of a managed system. The following tables are implemented for
the Aggregator.
• Physical Entity: A physical entity or physical component represents an identiable physical resource within a managed system. Zero or
more logical entities may utilize a physical resource at any given time. Determining which physical components are represented by an
agent in the EntPhysicalTable is an implementation-specic matter. Typically, physical resources (for example, communications ports,
backplanes, sensors, daughter-cards, power supplies, and the overall chassis), which you can manage via functions associated with one
or more logical entities, are included in the MIB.
• Containment Tree: Each physical component may be modeled as contained within another physical component. A containment-tree is
the conceptual sequence of entPhysicalIndex values that uniquely species the exact physical location of a physical component within
the managed system. It is generated by following and recording each entPhysicalContainedIn instance up the tree towards the root,
until a value of zero indicating no further containment is found.
Example of Sample Entity MIBS outputs
Dell#show inventory optional-module
Unit Slot Expected Inserted Next Boot Status/Power(On/Off)
------------------------------------------------------------------------
1 0 SFP+ SFP+ AUTO Good/On
Simple Network Management Protocol (SNMP)
225