PRVT-PORTS-AGGREGATION-MIB

File: PRVT-PORTS-AGGREGATION-MIB.mib (18867 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC RFC1213-MIB
Q-BRIDGE-MIB PRVT-SWITCH-MIB

Imported symbols

NOTIFICATION-TYPE MODULE-IDENTITY OBJECT-TYPE
Counter32 Integer32 DisplayString
TruthValue ifIndex ifAdminStatus
ifOperStatus PortList switch
configL2IfaceUnit configL2IfaceSlot configL2IfacePort

Defined Types

PortsAggregationEntry  
SEQUENCE    
  aggregatorId Integer32
  aggregatorIfIndex Integer32
  aggregatorType INTEGER
  aggregatorName DisplayString
  aggregatorPortsMembers PortList
  aggregatorPortsActive PortList
  aggregatorL2DropEvents Counter32
  aggregatorL2Octets Counter32
  aggregatorL2Pkts Counter32
  aggregatorL2BroadcastPkts Counter32
  aggregatorL2MulticastPkts Counter32
  aggregatorL2CRCAlignErrors Counter32
  aggregatorL2UndersizePkts Counter32
  aggregatorL2OversizePkts Counter32
  aggregatorL2Fragments Counter32
  aggregatorL2Jabbers Counter32
  aggregatorL2Collisions Counter32
  aggregatorL2Pkts64Octets Counter32
  aggregatorL2Pkts65to127Octets Counter32
  aggregatorL2Pkts128to255Octets Counter32
  aggregatorL2Pkts256to511Octets Counter32
  aggregatorL2Pkts512to1023Octets Counter32
  aggregatorL2Pkts1024to1518Octets Counter32

PortsAggregationConfigEntry  
SEQUENCE    
  staticAggregationID Integer32
  dynamicAggregationID Integer32
  aggregationType INTEGER
  aggregationLacpPortPriority Integer32
  aggregationLacpPortKey Integer32

Defined Values

prvtPortsAggregationMib 1.3.6.1.4.1.738.1.5.106
The Ports Aggregation MIB module for managing switch or ipSwitch static and dynamic port aggregation.
MODULE-IDENTITY    

portsAggregation 1.3.6.1.4.1.738.1.5.106.1
OBJECT IDENTIFIER    

portsAggregationConfig 1.3.6.1.4.1.738.1.5.106.2
OBJECT IDENTIFIER    

portsAggregationTraps 1.3.6.1.4.1.738.1.5.106.3
OBJECT IDENTIFIER    

maxAggregatorId 1.3.6.1.4.1.738.1.5.106.1.1
The maximum allowed aggregator ID for this unit.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

aggregationLacpSystemPriority 1.3.6.1.4.1.738.1.5.106.1.2
The LACP system priority.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 1..65535  

portsAggregationTable 1.3.6.1.4.1.738.1.5.106.1.3
This table contains the status of all the trunks in the system It can contain two major types: static and dynamic trunks.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PortsAggregationEntry

portsAggregationEntry 1.3.6.1.4.1.738.1.5.106.1.3.1
Ports aggregation entry.
Status: current Access: not-accessible
OBJECT-TYPE    
  PortsAggregationEntry  

aggregatorId 1.3.6.1.4.1.738.1.5.106.1.3.1.1
The internal trunk ID.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..255  

aggregatorIfIndex 1.3.6.1.4.1.738.1.5.106.1.3.1.2
The interface index from MIB-II ifTable.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

aggregatorType 1.3.6.1.4.1.738.1.5.106.1.3.1.3
This variable describes the trunk type.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER staticTrunk(1), protocol-802-1ad(2)  

aggregatorName 1.3.6.1.4.1.738.1.5.106.1.3.1.4
The aggregator's name.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString  

aggregatorPortsMembers 1.3.6.1.4.1.738.1.5.106.1.3.1.5
The ports that are members of this trunk.
Status: current Access: read-only
OBJECT-TYPE    
  PortList  

aggregatorPortsActive 1.3.6.1.4.1.738.1.5.106.1.3.1.6
The active ports that are members of this trunk.
Status: current Access: read-only
OBJECT-TYPE    
  PortList  

aggregatorL2DropEvents 1.3.6.1.4.1.738.1.5.106.1.3.1.7
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.8
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts 1.3.6.1.4.1.738.1.5.106.1.3.1.9
The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2BroadcastPkts 1.3.6.1.4.1.738.1.5.106.1.3.1.10
The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2MulticastPkts 1.3.6.1.4.1.738.1.5.106.1.3.1.11
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2CRCAlignErrors 1.3.6.1.4.1.738.1.5.106.1.3.1.12
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2UndersizePkts 1.3.6.1.4.1.738.1.5.106.1.3.1.13
The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2OversizePkts 1.3.6.1.4.1.738.1.5.106.1.3.1.14
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Fragments 1.3.6.1.4.1.738.1.5.106.1.3.1.15
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Jabbers 1.3.6.1.4.1.738.1.5.106.1.3.1.16
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Collisions 1.3.6.1.4.1.738.1.5.106.1.3.1.17
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts64Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.18
The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts65to127Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.19
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts128to255Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.20
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts256to511Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.21
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts512to1023Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.22
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregatorL2Pkts1024to1518Octets 1.3.6.1.4.1.738.1.5.106.1.3.1.23
The 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).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

aggregationLacpSystemEnable 1.3.6.1.4.1.738.1.5.106.1.4
This value enable/disable the LACP system globaly
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

portsAggregationConfigTable 1.3.6.1.4.1.738.1.5.106.2.1
This table contains only the static (created by management) port trunk configuration.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    PortsAggregationConfigEntry

portsAggregationConfigEntry 1.3.6.1.4.1.738.1.5.106.2.1.1
Port aggregation config entry.
Status: current Access: not-accessible
OBJECT-TYPE    
  PortsAggregationConfigEntry  

staticAggregationID 1.3.6.1.4.1.738.1.5.106.2.1.1.1
A number representing the aggregation group that this port belongs to. 0 means that this port does not belong to any static group.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

dynamicAggregationID 1.3.6.1.4.1.738.1.5.106.2.1.1.2
A number representing the aggregation group that this port belongs to. 0 means that this port does not belong to any dynamic group
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

aggregationType 1.3.6.1.4.1.738.1.5.106.2.1.1.3
Specifies 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER disable(1), static(2), protocol-802-1adAcive(3), protocol-802-1adPassive(4)  

aggregationLacpPortPriority 1.3.6.1.4.1.738.1.5.106.2.1.1.4
LACP priority for a port
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 1..65535  

aggregationLacpPortKey 1.3.6.1.4.1.738.1.5.106.2.1.1.5
LACP identification key for a port
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 1..65535  

lagMemberLinkUp 1.3.6.1.4.1.738.1.5.106.3.1
This 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
Status: current Access: read-write
NOTIFICATION-TYPE    

lagMemberLinkDown 1.3.6.1.4.1.738.1.5.106.3.2
This 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
Status: current Access: read-write
NOTIFICATION-TYPE    

lagMemberAdd 1.3.6.1.4.1.738.1.5.106.3.3
This 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
Status: current Access: read-write
NOTIFICATION-TYPE    

lagMemberRemove 1.3.6.1.4.1.738.1.5.106.3.4
This 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
Status: current Access: read-write
NOTIFICATION-TYPE