PRVT-PORTS-AGGREGATION-MIB
AI MIB Summary
The PRVT-PORTS-AGGREGATION-MIB enables the monitoring and configuration of static and dynamic link aggregation groups (LAGs) on IP switches, specifically tracking member port status, aggregation state transitions, and bundle operational parameters.
The Ports Aggregation MIB module for managing switch or ipSwitch static and dynamic port aggregation.
Main OID:
prvtPortsAggregationMib.1.3.6.1.4.1.5205.2.106
44
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
44 total| Object Name |
|---|
prvtPortsAggregationMibThe Ports Aggregation MIB module for managing switch or ipSwitch
static and dynamic port aggregation. MODULE-IDENTITY .1.3.6.1.4.1.5205.2.106 |
IMPORTSThe Ports Aggregation MIB module for managing switch or ipSwitch
static and dynamic port aggregation. NOTIFICATION-TYPE .1.3.6.1.4.1.5205.2.106 |
portsAggregation OBJECT IDENTIFIER .1.3.6.1.4.1.5205.2.106.1 |
maxAggregatorIdThe maximum allowed aggregator ID for this unit.ro Integer32 .1.3.6.1.4.1.5205.2.106.1.1 |
aggregationLacpSystemPriorityThe LACP system priority.rw Integer32 .1.3.6.1.4.1.5205.2.106.1.2 |
portsAggregationTableThis table contains the status of all the trunks in the system
It can contain two major types: static and dynamic trunks. SEQUENCE OF PortsAggregationEntry .1.3.6.1.4.1.5205.2.106.1.3 |
portsAggregationEntryPorts aggregation entry. PortsAggregationEntry .1.3.6.1.4.1.5205.2.106.1.3.1 |
aggregatorIdThe internal trunk ID. Integer32 .1.3.6.1.4.1.5205.2.106.1.3.1.1 |
aggregatorIfIndexThe interface index from MIB-II ifTable.ro Integer32 .1.3.6.1.4.1.5205.2.106.1.3.1.2 |
aggregatorTypeThis variable describes the trunk type.ro Enumeration .1.3.6.1.4.1.5205.2.106.1.3.1.3 |
aggregatorNameThe aggregator's name.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.5205.2.106.1.3.1.4 |
aggregatorPortsMembersThe ports that are members of this trunk.ro PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.5205.2.106.1.3.1.5 |
aggregatorPortsActiveThe active ports that are members of this trunk.ro PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.5205.2.106.1.3.1.6 |
aggregatorL2DropEventsThe total number of events in which packets
were dropped by the probe due to lack of resources.
Note that this number is not necessarily the number of
packets dropped; it is just the number of times this
condition has been detected.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.7 |
aggregatorL2OctetsThe total number of octets of data (including
those in bad packets) received on the
network (excluding framing bits but including
FCS octets).
This object can be used as a reasonable estimate of
Ethernet utilization. If greater precision is
desired, the etherStatsPkts and etherStatsOctets
objects should be sampled before and after a common
interval. The differences in the sampled values are
Pkts and Octets, respectively, and the number of
seconds in the interval is Interval. These values
are used to calculate the Utilization as follows:
Pkts * (9.6 + 6.4) + (Octets * .8)
Utilization =
Interval * 10,000
The result of this equation is the Ethernet segment utilization
which is the percent utilization of the ethernet
segment on a 0 to 100 percent scale.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.8 |
aggregatorL2PktsThe total number of packets (including bad packets,
broadcast packets, and multicast packets) received.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.9 |
aggregatorL2BroadcastPktsThe total number of good packets received that were
directed to the broadcast address. Note that this
does not include multicast packets.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.10 |
aggregatorL2MulticastPktsThe total number of good packets received that were
directed to a multicast address. Note that this
number does not include packets directed to the
broadcast address.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.11 |
aggregatorL2CRCAlignErrorsThe total number of packets received that
had a length (excluding framing bits, but
including FCS octets) of between 64 and 1518
octets, inclusive, but had either a bad
Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with
a non-integral number of octets (Alignment Error).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.12 |
aggregatorL2UndersizePktsThe total number of packets received that were
less than 64 octets long (excluding framing bits,
but including FCS octets) and were otherwise well
formed.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.13 |
aggregatorL2OversizePktsThe total number of packets received that were
longer than 1518 octets (excluding framing bits,
but including FCS octets) and were otherwise
well formed.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.14 |
aggregatorL2FragmentsThe total number of packets received that were less
than 64 octets in length (excluding framing bits but
including FCS octets) and had either a bad Frame
Check Sequence (FCS) with an integral number of
octets (FCS Error) or a bad FCS with a non-integral
number of octets (Alignment Error).
Note that it is entirely normal for
etherStatsFragments to increment. This is because
it counts both runts (which are normal occurrences
due to collisions) and noise hits.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.15 |
aggregatorL2JabbersThe total number of packets received that were
longer than 1518 octets (excluding framing bits,
but including FCS octets), and had either a bad
Frame Check Sequence (FCS) with an integral number
of octets (FCS Error) or a bad FCS with a
non-integral number of octets (Alignment Error).
Note that this definition of jabber is different
from the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition in which any
packet exceeds 20 ms. The allowed range to detect
jabber is between 20 ms and 150 ms.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.16 |
aggregatorL2CollisionsThe best estimate of the total number of collisions
on this Ethernet segment.
The value returned will depend on the RMON probe's location.
Sections 8.2.1.3 (10BASE-5) and 10.3.1.3 (10BASE-2) of
IEEE standard 802.3 states that a station must detect a collision in
the receive mode if three or more stations are
transmitting simultaneously. A repeater port must
detect a collision when two or more stations are
transmitting simultaneously. Thus a probe placed on
a repeater port could record more collisions than a
probe connected to a station on the same segment
would.
Probe location plays a much smaller role when
considering 10BASE-T. Section 14.2.1.4 (10BASE-T) of IEEE
standard 802.3 defines a collision as the
simultaneous presence of signals on the DO and RD
circuits (transmitting and receiving at the same
time). A 10BASE-T station can only detect
collisions when it is transmitting. Thus probes
placed on a station and a repeater, should report
the same number of collisions.
Note also that an RMON probe inside a repeater
should ideally report collisions between the
repeater and one or more other hosts (transmit
collisions as defined by IEEE 802.3k) plus receiver
collisions observed on any coaxial segments to which
the repeater is connected.ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.17 |
aggregatorL2Pkts64OctetsThe total number of packets (including bad
packets) received that were 64 octets in length
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.18 |
aggregatorL2Pkts65to127OctetsThe total number of packets (including bad
packets) received that were between
65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.19 |
aggregatorL2Pkts128to255OctetsThe total number of packets (including bad
packets) received that were between
128 and 255 octets in length inclusive
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.20 |
aggregatorL2Pkts256to511OctetsThe total number of packets (including bad
packets) received that were between
256 and 511 octets in length inclusive
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.21 |
aggregatorL2Pkts512to1023OctetsThe total number of packets (including bad
packets) received that were between
512 and 1023 octets in length inclusive
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.22 |
aggregatorL2Pkts1024to1518OctetsThe total number of packets (including bad
packets) received that were between
1024 and 1518 octets in length inclusive
(excluding framing bits but including FCS octets).ro Counter32 .1.3.6.1.4.1.5205.2.106.1.3.1.23 |
aggregationLacpSystemEnableThis value enable/disable the LACP system globalyrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.5205.2.106.1.4 |
portsAggregationConfig OBJECT IDENTIFIER .1.3.6.1.4.1.5205.2.106.2 |
portsAggregationConfigTableThis table contains only the static (created by management) port trunk configuration. SEQUENCE OF PortsAggregationConfigEntry .1.3.6.1.4.1.5205.2.106.2.1 |
portsAggregationConfigEntryPort aggregation config entry. PortsAggregationConfigEntry .1.3.6.1.4.1.5205.2.106.2.1.1 |
staticAggregationIDA number representing the aggregation group that this port belongs to.
0 means that this port does not belong to any static group.rw Integer32 .1.3.6.1.4.1.5205.2.106.2.1.1.1 |
dynamicAggregationIDA number representing the aggregation group that this port belongs to.
0 means that this port does not belong to any dynamic groupro Integer32 .1.3.6.1.4.1.5205.2.106.2.1.1.2 |
aggregationTypeSpecifies the aggregation type of the interface - disable(1) if the port does not belong to a group,
static(2) if the port belongs to a static group, and protocol-802-1adAcive(3) or protocol-802-1adPassive(4)
if the interface is part of a dynamic group.rw Enumeration .1.3.6.1.4.1.5205.2.106.2.1.1.3 |
aggregationLacpPortPriorityLACP priority for a portrw Integer32 .1.3.6.1.4.1.5205.2.106.2.1.1.4 |
aggregationLacpPortKeyLACP identification key for a portrw Integer32 .1.3.6.1.4.1.5205.2.106.2.1.1.5 |
portsAggregationTraps OBJECT IDENTIFIER .1.3.6.1.4.1.5205.2.106.3 |
lagMemberLinkUpThis notification is generated when lag link becomes
up.
The first ifIndex indicates the id of the trunk
interface.
The second one shows the port member with link status change NOTIFICATION-TYPE .1.3.6.1.4.1.5205.2.106.3.1 |
lagMemberLinkDownThis notification is generated when lag link becomes
down.
The first ifIndex indicates the id of the trunk
interface.
The second one shows the port member with link status change NOTIFICATION-TYPE .1.3.6.1.4.1.5205.2.106.3.2 |
lagMemberAddThis notification is generated when a new port is added to
a lag link.
The first ifIndex indicates the id of the trunk
interface.
The second one shows the added port member NOTIFICATION-TYPE .1.3.6.1.4.1.5205.2.106.3.3 |
lagMemberRemoveThis notification is generated when a port is removed from
a lag.
The first ifIndex indicates the id of the trunk
interface.
The second one shows the removed port member NOTIFICATION-TYPE .1.3.6.1.4.1.5205.2.106.3.4 |