.1.0,LLDP-MIB::std,,,,,,
.1.0.8802,LLDP-MIB::iso8802,,,,,,
.1.0.8802.1,LLDP-MIB::ieee802dot1,,,,,,
.1.0.8802.1.1,LLDP-MIB::ieee802dot1mibs,,,,,,
.1.0.8802.1.1.2,LLDP-MIB::lldpMIB,,,,,,Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components. Copyright (C) IEEE (2005). This version of this MIB module is published as subclause 12.1 of IEEE Std 802.1AB-2005; see the standard itself for full legal notices.
.1.0.8802.1.1.2.0,LLDP-MIB::lldpNotifications,,,,,,
.1.0.8802.1.1.2.0.0,LLDP-MIB::lldpNotificationPrefix,,,,,,
.1.0.8802.1.1.2.0.0.1,LLDP-MIB::lldpRemTablesChange,,,,,,A lldpRemTablesChange notification is sent when the value of lldpStatsRemTableLastChangeTime changes. It can be utilized by an NMS to trigger LLDP remote systems table maintenance polls. Note that transmission of lldpRemTablesChange notifications are throttled by the agent, as specified by the 'lldpNotificationInterval' object.
.1.0.8802.1.1.2.1,LLDP-MIB::lldpObjects,,,,,,
.1.0.8802.1.1.2.1.1,LLDP-MIB::lldpConfiguration,,,,,,
.1.0.8802.1.1.2.1.1.1,LLDP-MIB::lldpMessageTxInterval,Integer32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent. The default value for lldpMessageTxInterval object is 30 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.2,LLDP-MIB::lldpMessageTxHoldMultiplier,Integer32,read-write,,current,,The time-to-live value expressed as a multiple of the lldpMessageTxInterval object. The actual time-to-live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpMessageTxInterval * lldpMessageTxHoldMultiplier)) For example, if the value of lldpMessageTxInterval is '30', and the value of lldpMessageTxHoldMultiplier is '4', then the value '120' is encoded in the TTL field in the LLDP header. The default value for lldpMessageTxHoldMultiplier object is 4. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.3,LLDP-MIB::lldpReinitDelay,Integer32,read-write,,current,,The lldpReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization will be attempted. The default value for lldpReintDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.4,LLDP-MIB::lldpTxDelay,Integer32,read-write,,current,,The lldpTxDelay indicates the delay (in units of seconds) between successive LLDP frame transmissions  initiated by value/status changes in the LLDP local systems MIB. The recommended value for the lldpTxDelay is set by the following formula: 1 <= lldpTxDelay <= (0.25 * lldpMessageTxInterval) The default value for lldpTxDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.5,LLDP-MIB::lldpNotificationInterval,Integer32,read-write,,current,,This object controls the transmission of LLDP notifications. the agent must not generate more than one lldpRemTablesChange notification-event in the indicated period, where a 'notification-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional changes in lldpRemoteSystemsData object groups occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of lldpStatsRemTableLastChangeTime to detect any missed lldpRemTablesChange notification-events, e.g. due to throttling or transmission loss. If notification transmission is enabled for particular ports, the suggested default throttling period is 5 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.6,LLDP-MIB::lldpPortConfigTable,,not-accessible,,current,,The table that controls LLDP frame transmission on individual ports.
.1.0.8802.1.1.2.1.1.6.1,LLDP-MIB::lldpPortConfigEntry,,not-accessible,lldpPortConfigPortNum,current,,LLDP configuration information for a particular port. This configuration parameter controls the transmission and the reception of LLDP frames on those ports whose rows are created in this table.
.1.0.8802.1.1.2.1.1.6.1.1,LLDP-MIB::lldpPortConfigPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpPortConfigTable.
.1.0.8802.1.1.2.1.1.6.1.2,LLDP-MIB::lldpPortConfigAdminStatus,INTEGER,read-write,,current,txOnly(1):rxOnly(2):txAndRx(3):disabled(4),The administratively desired status of the local LLDP agent. If the associated lldpPortConfigAdminStatus object has a value of 'txOnly(1)', then LLDP agent will transmit LLDP frames on this port and it will not store any information about the remote systems connected.  If the associated lldpPortConfigAdminStatus object has a value of 'rxOnly(2)', then the LLDP agent will receive, but it will not transmit LLDP frames on this port. If the associated lldpPortConfigAdminStatus object has a value of 'txAndRx(3)', then the LLDP agent will transmit and receive LLDP frames on this port. If the associated lldpPortConfigAdminStatus object has a value of 'disabled(4)', then LLDP agent will not transmit or receive LLDP frames on this port. If there is remote systems information which is received on this port and stored in other tables, before the port's lldpPortConfigAdminStatus becomes disabled, then the information will naturally age out.
.1.0.8802.1.1.2.1.1.6.1.3,LLDP-MIB::lldpPortConfigNotificationEnable,INTEGER,read-write,,current,true(1):false(2),The lldpPortConfigNotificationEnable controls, on a per port basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.0.8802.1.1.2.1.1.6.1.4,LLDP-MIB::lldpPortConfigTLVsTxEnable,BITS,read-write,,current,portDesc(0):sysName(1):sysDesc(2):sysCap(3),The lldpPortConfigTLVsTxEnable, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. It should be noted that the organizationally-specific TLVs are excluded from the lldpTLVsTxEnable bitmap.  LLDP Organization Specific Information Extension MIBs should have similar configuration object to control transmission of their organizationally defined TLVs. The bit 'portDesc(0)' indicates that LLDP agent should transmit 'Port Description TLV'. The bit 'sysName(1)' indicates that LLDP agent should transmit 'System Name TLV'. The bit 'sysDesc(2)' indicates that LLDP agent should transmit 'System Description TLV'. The bit 'sysCap(3)' indicates that LLDP agent should transmit 'System Capabilities TLV'. There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object, lldpConfigManAddrTable. The default value for lldpPortConfigTLVsTxEnable object is empty set, which means no enumerated values are set. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.7,LLDP-MIB::lldpConfigManAddrTable,,not-accessible,,current,,The table that controls selection of LLDP management address TLV instances to be transmitted on individual ports.
.1.0.8802.1.1.2.1.1.7.1,LLDP-MIB::lldpConfigManAddrEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the local system management address instance will be transmitted. This configuration object augments the lldpLocManAddrEntry, therefore it is only present along with the management address instance contained in the associated lldpLocManAddrEntry entry. Each active lldpConfigManAddrEntry must be restored from non-volatile and re-created (along with the corresponding lldpLocManAddrEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.7.1.1,LLDP-MIB::lldpConfigManAddrPortsTxEnable,OCTET,read-write,,current,,A set of ports that are identified by a PortList, in which each port is represented as a bit. The corresponding local system management address instance will be transmitted on the member ports of the lldpManAddrPortsTxEnable.  The default value for lldpConfigManAddrPortsTxEnable object is empty binary string, which means no ports are specified for advertising indicated management address instance.
.1.0.8802.1.1.2.1.2,LLDP-MIB::lldpStatistics,,,,,,
.1.0.8802.1.1.2.1.2.1,LLDP-MIB::lldpStatsRemTablesLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted in the in tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems. An NMS can use this object to reduce polling of the lldpRemoteSystemsData objects.
.1.0.8802.1.1.2.1.2.2,LLDP-MIB::lldpStatsRemTablesInserts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
.1.0.8802.1.1.2.1.2.3,LLDP-MIB::lldpStatsRemTablesDeletes,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects. This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.
.1.0.8802.1.1.2.1.2.4,LLDP-MIB::lldpStatsRemTablesDrops,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.
.1.0.8802.1.1.2.1.2.5,LLDP-MIB::lldpStatsRemTablesAgeouts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial aging, similar to deletion case, is not allowed, and thus, should not change the value of this counter.
.1.0.8802.1.1.2.1.2.6,LLDP-MIB::lldpStatsTxPortTable,,not-accessible,,current,,A table containing LLDP transmission statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.0.8802.1.1.2.1.2.6.1,LLDP-MIB::lldpStatsTxPortEntry,,not-accessible,lldpStatsTxPortNum,current,,LLDP frame transmission statistics for a particular port.  The port must be contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port.
.1.0.8802.1.1.2.1.2.6.1.1,LLDP-MIB::lldpStatsTxPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.
.1.0.8802.1.1.2.1.2.6.1.2,LLDP-MIB::lldpStatsTxPortFramesTotal,Counter32,read-only,,current,,The number of LLDP frames transmitted by this LLDP agent on the indicated port.
.1.0.8802.1.1.2.1.2.7,LLDP-MIB::lldpStatsRxPortTable,,not-accessible,,current,,A table containing LLDP reception statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.0.8802.1.1.2.1.2.7.1,LLDP-MIB::lldpStatsRxPortEntry,,not-accessible,lldpStatsRxPortNum,current,,LLDP frame reception statistics for a particular port. The port must be contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port.
.1.0.8802.1.1.2.1.2.7.1.1,LLDP-MIB::lldpStatsRxPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.
.1.0.8802.1.1.2.1.2.7.1.2,LLDP-MIB::lldpStatsRxPortFramesDiscardedTotal,Counter32,read-only,,current,,The number of LLDP frames received by this LLDP agent on the indicated port, and then discarded for any reason. This counter can provide an indication that LLDP header formating problems may exist with the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP agent in the receiving system.
.1.0.8802.1.1.2.1.2.7.1.3,LLDP-MIB::lldpStatsRxPortFramesErrors,Counter32,read-only,,current,,The number of invalid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.0.8802.1.1.2.1.2.7.1.4,LLDP-MIB::lldpStatsRxPortFramesTotal,Counter32,read-only,,current,,The number of valid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.0.8802.1.1.2.1.2.7.1.5,LLDP-MIB::lldpStatsRxPortTLVsDiscardedTotal,Counter32,read-only,,current,,The number of LLDP TLVs discarded for any reason by this LLDP agent on the indicated port.
.1.0.8802.1.1.2.1.2.7.1.6,LLDP-MIB::lldpStatsRxPortTLVsUnrecognizedTotal,Counter32,read-only,,current,,The number of LLDP TLVs received on the given port that are not recognized by this LLDP agent on the indicated port.  An unrecognized TLV is referred to as the TLV whose type value is in the range of reserved TLV types (000 1001 - 111 1110) in Table 9.1 of IEEE Std 802.1AB-2005. An unrecognized TLV may be a basic management TLV from a later LLDP version.
.1.0.8802.1.1.2.1.2.7.1.7,LLDP-MIB::lldpStatsRxPortAgeoutsTotal,Gauge32,read-only,,current,,The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter is similar to lldpStatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only. This counter should be set to zero during agent initialization and its value should not be saved in non-volatile storage. When a port's admin status changes from 'disabled' to 'rxOnly', 'txOnly' or 'txAndRx', the counter associated with the same port should reset to 0. The agent should also flush all remote system information associated with the same port. This counter should be incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial aging is not allowed, and thus, should not change the value of this counter.
.1.0.8802.1.1.2.1.3,LLDP-MIB::lldpLocalSystemData,,,,,,
.1.0.8802.1.1.2.1.3.1,LLDP-MIB::lldpLocChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the local system.
.1.0.8802.1.1.2.1.3.2,LLDP-MIB::lldpLocChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the local system.
.1.0.8802.1.1.2.1.3.3,LLDP-MIB::lldpLocSysName,OCTET,read-only,,current,,The string value used to identify the system name of the local system. If the local agent supports IETF RFC 3418, lldpLocSysName object should have the same value of sysName object.
.1.0.8802.1.1.2.1.3.4,LLDP-MIB::lldpLocSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the local system. If the local agent supports IETF RFC 3418, lldpLocSysDesc object should have the same value of sysDesc object.
.1.0.8802.1.1.2.1.3.5,LLDP-MIB::lldpLocSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are supported on the local system.
.1.0.8802.1.1.2.1.3.6,LLDP-MIB::lldpLocSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are enabled on the local system.
.1.0.8802.1.1.2.1.3.7,LLDP-MIB::lldpLocPortTable,,not-accessible,,current,,This table contains one or more rows per port information associated with the local system known to this agent.
.1.0.8802.1.1.2.1.3.7.1,LLDP-MIB::lldpLocPortEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port component. Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.3.7.1.1,LLDP-MIB::lldpLocPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.  The value of this object is used as a port index to the lldpLocPortTable.
.1.0.8802.1.1.2.1.3.7.1.2,LLDP-MIB::lldpLocPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpLocPortId' object.
.1.0.8802.1.1.2.1.3.7.1.3,LLDP-MIB::lldpLocPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with a given port in the local system.
.1.0.8802.1.1.2.1.3.7.1.4,LLDP-MIB::lldpLocPortDesc,OCTET,read-only,,current,,The string value used to identify the 802 LAN station's port description associated with the local system. If the local agent supports IETF RFC 2863, lldpLocPortDesc object should have the same value of ifDescr object.
.1.0.8802.1.1.2.1.3.8,LLDP-MIB::lldpLocManAddrTable,,not-accessible,,current,,This table contains management address information on the local system known to this agent.
.1.0.8802.1.1.2.1.3.8.1,LLDP-MIB::lldpLocManAddrEntry,,not-accessible,lldpLocManAddrSubtype:lldpLocManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the system identified by a particular lldpLocChassisId. Each management address should have distinct 'management address type' (lldpLocManAddrSubtype) and 'management address' (lldpLocManAddr.) Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.3.8.1.1,LLDP-MIB::lldpLocManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object.
.1.0.8802.1.1.2.1.3.8.1.2,LLDP-MIB::lldpLocManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the local system. The purpose of this address is to contact the management entity.
.1.0.8802.1.1.2.1.3.8.1.3,LLDP-MIB::lldpLocManAddrLen,Integer32,read-only,,current,,The total length of the management address subtype and the management address fields in LLDPDUs transmitted by the local LLDP agent. The management address length field is needed so that the receiving systems that do not implement SNMP will not be required to implement an iana family numbers/address length equivalency table in order to decode the management adress.
.1.0.8802.1.1.2.1.3.8.1.4,LLDP-MIB::lldpLocManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the local system.
.1.0.8802.1.1.2.1.3.8.1.5,LLDP-MIB::lldpLocManAddrIfId,Integer32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the local system.
.1.0.8802.1.1.2.1.3.8.1.6,LLDP-MIB::lldpLocManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the local system agent.
.1.0.8802.1.1.2.1.4,LLDP-MIB::lldpRemoteSystemsData,,,,,,
.1.0.8802.1.1.2.1.4.1,LLDP-MIB::lldpRemTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1.  Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables. if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll. if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.) lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes.
.1.0.8802.1.1.2.1.4.1.1,LLDP-MIB::lldpRemEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active.
.1.0.8802.1.1.2.1.4.1.1.1,LLDP-MIB::lldpRemTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention in IETF RFC 2021 and  http://www.ietf.org/IESG/Implementations/RFC2021-Implementation.txt to see how TimeFilter works.
.1.0.8802.1.1.2.1.4.1.1.2,LLDP-MIB::lldpRemLocalPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The lldpRemLocalPortNum identifies the port on which the remote system information is received. The value of this object is used as a port index to the lldpRemTable.
.1.0.8802.1.1.2.1.4.1.1.3,LLDP-MIB::lldpRemIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemIndex will wrap between reboots.
.1.0.8802.1.1.2.1.4.1.1.4,LLDP-MIB::lldpRemChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.5,LLDP-MIB::lldpRemChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.6,LLDP-MIB::lldpRemPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpRemPortId' object.
.1.0.8802.1.1.2.1.4.1.1.7,LLDP-MIB::lldpRemPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.8,LLDP-MIB::lldpRemPortDesc,OCTET,read-only,,current,,The string value used to identify the description of the given port associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.9,LLDP-MIB::lldpRemSysName,OCTET,read-only,,current,,The string value used to identify the system name of the remote system.
.1.0.8802.1.1.2.1.4.1.1.10,LLDP-MIB::lldpRemSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the remote system.
.1.0.8802.1.1.2.1.4.1.1.11,LLDP-MIB::lldpRemSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are supported on the remote system.
.1.0.8802.1.1.2.1.4.1.1.12,LLDP-MIB::lldpRemSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are enabled on the remote system.
.1.0.8802.1.1.2.1.4.2,LLDP-MIB::lldpRemManAddrTable,,not-accessible,,current,,This table contains one or more rows per management address information on the remote system learned on a particular port contained in the local chassis known to this agent.
.1.0.8802.1.1.2.1.4.2.1,LLDP-MIB::lldpRemManAddrEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemManAddrSubtype:lldpRemManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the remote system identified by a particular lldpRemIndex whose information is received on lldpRemLocalPortNum of the local system. Each management address should have distinct 'management address type' (lldpRemManAddrSubtype) and 'management address' (lldpRemManAddr.) Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.4.2.1.1,LLDP-MIB::lldpRemManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpRemManagmentAddr' object.
.1.0.8802.1.1.2.1.4.2.1.2,LLDP-MIB::lldpRemManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the remote system. The purpose of this address is to contact the management entity.
.1.0.8802.1.1.2.1.4.2.1.3,LLDP-MIB::lldpRemManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the remote system.
.1.0.8802.1.1.2.1.4.2.1.4,LLDP-MIB::lldpRemManAddrIfId,Integer32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the remote system.
.1.0.8802.1.1.2.1.4.2.1.5,LLDP-MIB::lldpRemManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the remote system agent.
.1.0.8802.1.1.2.1.4.3,LLDP-MIB::lldpRemUnknownTLVTable,,not-accessible,,current,,This table contains information about an incoming TLV which is not recognized by the receiving LLDP agent. The TLV may be from a later version of the basic management set. This table should only contain TLVs that are found in a single LLDP frame. Entries in this table, associated with an MAC service access point (MSAP, the access point for MAC services provided to the LCC sublayer, defined in IEEE 100, which is also identified with a particular lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with most recently received unrecognized TLV from the same MSAP, or they will naturally age out when the rxInfoTTL timer (associated with the MSAP) expires.
.1.0.8802.1.1.2.1.4.3.1,LLDP-MIB::lldpRemUnknownTLVEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemUnknownTLVType,current,,Information about an unrecognized TLV received from a physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active.
.1.0.8802.1.1.2.1.4.3.1.1,LLDP-MIB::lldpRemUnknownTLVType,Integer32,not-accessible,,current,,This object represents the value extracted from the type field of the TLV.
.1.0.8802.1.1.2.1.4.3.1.2,LLDP-MIB::lldpRemUnknownTLVInfo,OCTET,read-only,,current,,This object represents the value extracted from the value field of the TLV.
.1.0.8802.1.1.2.1.4.4,LLDP-MIB::lldpRemOrgDefInfoTable,,not-accessible,,current,,This table contains one or more rows per physical network connection which advertises the organizationally defined information. Note that this table contains one or more rows of organizationally defined information that is not recognized by the local agent. If the local system is capable of recognizing any organizationally defined information, appropriate extension MIBs from the organization should be used for information retrieval.
.1.0.8802.1.1.2.1.4.4.1,LLDP-MIB::lldpRemOrgDefInfoEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemOrgDefInfoOUI:lldpRemOrgDefInfoSubtype:lldpRemOrgDefInfoIndex,current,,Information about the unrecognized organizationally defined information advertised by the remote system. The lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex, lldpRemOrgDefInfoOUI, lldpRemOrgDefInfoSubtype, and lldpRemOrgDefInfoIndex are indexes to this table. If there is an lldpRemOrgDefInfoEntry associated with a particular remote system identified by the lldpRemLocalPortNum and lldpRemIndex, there must be an lldpRemEntry associated with the same instance (i.e, using same indexes.) When the lldpRemEntry for the same index is removed from the lldpRemTable, the associated lldpRemOrgDefInfoEntry should be removed from the lldpRemOrgDefInfoTable. Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.4.4.1.1,LLDP-MIB::lldpRemOrgDefInfoOUI,OCTET,not-accessible,,current,,The Organizationally Unique Identifier (OUI), as defined in IEEE std 802-2001, is a 24 bit (three octets) globally unique assigned number referenced by various standards, of the information received from the remote system.
.1.0.8802.1.1.2.1.4.4.1.2,LLDP-MIB::lldpRemOrgDefInfoSubtype,Integer32,not-accessible,,current,,The integer value used to identify the subtype of the organizationally defined information received from the remote system. The subtype value is required to identify different instances of organizationally defined information that could not be retrieved without a unique identifier that indicates the particular type of information contained in the information string.
.1.0.8802.1.1.2.1.4.4.1.3,LLDP-MIB::lldpRemOrgDefInfoIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular unrecognized organizationally defined information instance, unique only for the lldpRemOrgDefInfoOUI and lldpRemOrgDefInfoSubtype from the same remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemOrgDefInfoIndex will wrap between reboots.
.1.0.8802.1.1.2.1.4.4.1.4,LLDP-MIB::lldpRemOrgDefInfo,OCTET,read-only,,current,,The string value used to identify the organizationally defined information of the remote system. The encoding for this object should be as defined for SnmpAdminString TC.
.1.0.8802.1.1.2.1.5,LLDP-MIB::lldpExtensions,,,,,,
.1.0.8802.1.1.2.2,LLDP-MIB::lldpConformance,,,,,,
.1.0.8802.1.1.2.2.1,LLDP-MIB::lldpCompliances,,,,,,
.1.0.8802.1.1.2.2.1.1,LLDP-MIB::lldpCompliance,,,,,,The compliance statement for SNMP entities which implement the LLDP MIB.
.1.0.8802.1.1.2.2.2,LLDP-MIB::lldpGroups,,,,,,
.1.0.8802.1.1.2.2.2.1,LLDP-MIB::lldpConfigGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP.
.1.0.8802.1.1.2.2.2.2,LLDP-MIB::lldpConfigRxGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.3,LLDP-MIB::lldpConfigTxGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.4,LLDP-MIB::lldpStatsRxGroup,,,,,,The collection of objects which are used to represent LLDP reception statistics. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.5,LLDP-MIB::lldpStatsTxGroup,,,,,,The collection of objects which are used to represent LLDP transmission statistics. This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.6,LLDP-MIB::lldpLocSysGroup,,,,,,The collection of objects which are used to represent LLDP Local System Information.   This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.7,LLDP-MIB::lldpRemSysGroup,,,,,,The collection of objects which are used to represent LLDP Remote Systems Information. The objects represent the information associated with the basic TLV set. Please note that even the agent doesn't implement some of the optional TLVs, it shall recognize all the optional TLV information that the remote system may advertise.  This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.8,LLDP-MIB::lldpNotificationsGroup,,,,,,The collection of notifications used to indicate LLDP MIB data consistency and general status information. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.3,SNMPv2-SMI::org,,,,,,
.1.3.6,SNMPv2-SMI::dod,,,,,,
.1.3.6.1,SNMPv2-SMI::internet,,,,,,
.1.3.6.1.1,SNMPv2-SMI::directory,,,,,,
.1.3.6.1.2,SNMPv2-SMI::mgmt,,,,,,
.1.3.6.1.2.1,SNMPv2-SMI::mib-2,,,,,,
.1.3.6.1.2.1.1,SNMPv2-MIB::system,,,,,,
.1.3.6.1.2.1.1.1,SNMPv2-MIB::sysDescr,OCTET,read-only,,current,,A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software.
.1.3.6.1.2.1.1.2,SNMPv2-MIB::sysObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.424242, it could assign the identifier 1.3.6.1.4.1.424242.1.1 to its `Fred Router'.
.1.3.6.1.2.1.1.3,SNMPv2-MIB::sysUpTime,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the network management portion of the system was last re-initialized.
.1.3.6.1.2.1.1.4,SNMPv2-MIB::sysContact,OCTET,read-write,,current,,The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.
.1.3.6.1.2.1.1.5,SNMPv2-MIB::sysName,OCTET,read-write,,current,,An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.
.1.3.6.1.2.1.1.6,SNMPv2-MIB::sysLocation,OCTET,read-write,,current,,The physical location of this node (e.g., 'telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.
.1.3.6.1.2.1.1.7,SNMPv2-MIB::sysServices,INTEGER,read-only,,current,,A value which indicates the set of services that this entity may potentially offer. The value is a sum. This sum initially takes the value zero. Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., supports the IP) 4 end-to-end (e.g., supports the TCP) 7 applications (e.g., supports the SMTP) For systems including OSI protocols, layers 5 and 6 may also be counted.
.1.3.6.1.2.1.1.8,SNMPv2-MIB::sysORLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent change in state or value of any instance of sysORID.
.1.3.6.1.2.1.1.9,SNMPv2-MIB::sysORTable,,not-accessible,,current,,The (conceptual) table listing the capabilities of the local SNMP application acting as a command responder with respect to various MIB modules. SNMP entities having dynamically-configurable support of MIB modules will have a dynamically-varying number of conceptual rows.
.1.3.6.1.2.1.1.9.1,SNMPv2-MIB::sysOREntry,,not-accessible,sysORIndex,current,,An entry (conceptual row) in the sysORTable.
.1.3.6.1.2.1.1.9.1.1,SNMPv2-MIB::sysORIndex,INTEGER,not-accessible,,current,,The auxiliary variable used for identifying instances of the columnar objects in the sysORTable.
.1.3.6.1.2.1.1.9.1.2,SNMPv2-MIB::sysORID,OBJECT,read-only,,current,,An authoritative identification of a capabilities statement with respect to various MIB modules supported by the local SNMP application acting as a command responder.
.1.3.6.1.2.1.1.9.1.3,SNMPv2-MIB::sysORDescr,OCTET,read-only,,current,,A textual description of the capabilities identified by the corresponding instance of sysORID.
.1.3.6.1.2.1.1.9.1.4,SNMPv2-MIB::sysORUpTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time this conceptual row was last instantiated.
.1.3.6.1.2.1.2,IF-MIB::interfaces,,,,,,
.1.3.6.1.2.1.2.1,IF-MIB::ifNumber,Integer32,read-only,,current,,The number of network interfaces (regardless of their current state) present on this system.
.1.3.6.1.2.1.2.2,IF-MIB::ifTable,,not-accessible,,current,,A list of interface entries. The number of entries is given by the value of ifNumber.
.1.3.6.1.2.1.2.2.1,IF-MIB::ifEntry,,not-accessible,ifIndex,current,,An entry containing management information applicable to a particular interface.
.1.3.6.1.2.1.2.2.1.1,IF-MIB::ifIndex,Integer32,read-only,,current,,A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
.1.3.6.1.2.1.2.2.1.2,IF-MIB::ifDescr,OCTET,read-only,,current,,A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.
.1.3.6.1.2.1.2.2.1.3,IF-MIB::ifType,INTEGER,read-only,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.
.1.3.6.1.2.1.2.2.1.4,IF-MIB::ifMtu,Integer32,read-only,,current,,The size of the largest packet which can be sent/received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.
.1.3.6.1.2.1.2.2.1.5,IF-MIB::ifSpeed,Gauge32,read-only,,current,,An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interace's speed. For a sub-layer which has no concept of bandwidth, this object should be zero.
.1.3.6.1.2.1.2.2.1.6,IF-MIB::ifPhysAddress,OCTET,read-only,,current,,The interface's address at its protocol sub-layer. For example, for an 802.x interface, this object normally contains a MAC address. The interface's media-specific MIB must define the bit and byte ordering and the format of the value of this object. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length.
.1.3.6.1.2.1.2.2.1.7,IF-MIB::ifAdminStatus,INTEGER,read-write,,current,up(1):down(2):testing(3),The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
.1.3.6.1.2.1.2.2.1.8,IF-MIB::ifOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):unknown(4):dormant(5):notPresent(6):lowerLayerDown(7),The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components.
.1.3.6.1.2.1.2.2.1.9,IF-MIB::ifLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.2.2.1.10,IF-MIB::ifInOctets,Counter32,read-only,,current,,The total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.11,IF-MIB::ifInUcastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.12,IF-MIB::ifInNUcastPkts,Counter32,read-only,,deprecated,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This object is deprecated in favour of ifInMulticastPkts and ifInBroadcastPkts.
.1.3.6.1.2.1.2.2.1.13,IF-MIB::ifInDiscards,Counter32,read-only,,current,,The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.14,IF-MIB::ifInErrors,Counter32,read-only,,current,,For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character- oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.15,IF-MIB::ifInUnknownProtos,Counter32,read-only,,current,,For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing the number of transmission units received via the interface which were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will always be 0. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.16,IF-MIB::ifOutOctets,Counter32,read-only,,current,,The total number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.17,IF-MIB::ifOutUcastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.18,IF-MIB::ifOutNUcastPkts,Counter32,read-only,,deprecated,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This object is deprecated in favour of ifOutMulticastPkts and ifOutBroadcastPkts.
.1.3.6.1.2.1.2.2.1.19,IF-MIB::ifOutDiscards,Counter32,read-only,,current,,The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.20,IF-MIB::ifOutErrors,Counter32,read-only,,current,,For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.21,IF-MIB::ifOutQLen,Gauge32,read-only,,deprecated,,The length of the output packet queue (in packets).
.1.3.6.1.2.1.2.2.1.22,IF-MIB::ifSpecific,OBJECT,read-only,,deprecated,,A reference to MIB definitions specific to the particular media being used to realize the interface. It is recommended that this value point to an instance of a MIB object in the media-specific MIB, i.e., that this object have the semantics associated with the InstancePointer textual convention defined in RFC 2579. In fact, it is recommended that the media-specific MIB specify what value ifSpecific should/can take for values of ifType. If no MIB definitions specific to the particular media are available, the value should be set to the OBJECT IDENTIFIER { 0 0 }.
.1.3.6.1.2.1.3,RFC1213-MIB::at,,,,,,
.1.3.6.1.2.1.3.1,RFC1213-MIB::atTable,,not-accessible,,deprecated,,The Address Translation tables contain the NetworkAddress to `physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries.
.1.3.6.1.2.1.3.1.1,RFC1213-MIB::atEntry,,not-accessible,atIfIndex:atNetAddress,deprecated,,Each entry contains one NetworkAddress to `physical' address equivalence.
.1.3.6.1.2.1.3.1.1.1,RFC1213-MIB::atIfIndex,INTEGER,read-write,,deprecated,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.3.1.1.2,RFC1213-MIB::atPhysAddress,OCTET,read-write,,deprecated,,The media-dependent `physical' address. Setting this object to a null string (one of zero length) has the effect of invaliding the corresponding entry in the atTable object. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atPhysAddress object.
.1.3.6.1.2.1.3.1.1.3,RFC1213-MIB::atNetAddress,NetworkAddress,read-write,,deprecated,,The NetworkAddress (e.g., the IP address) corresponding to the media-dependent `physical' address.
.1.3.6.1.2.1.4,RFC1213-MIB::ip,,,,,,
.1.3.6.1.2.1.4.1,RFC1213-MIB::ipForwarding,INTEGER,read-write,,mandatory,forwarding(1):not-forwarding(2),The indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value.
.1.3.6.1.2.1.4.2,RFC1213-MIB::ipDefaultTTL,INTEGER,read-write,,mandatory,,The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
.1.3.6.1.2.1.4.3,RFC1213-MIB::ipInReceives,Counter32,read-only,,mandatory,,The total number of input datagrams received from interfaces, including those received in error.
.1.3.6.1.2.1.4.4,RFC1213-MIB::ipInHdrErrors,Counter32,read-only,,mandatory,,The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
.1.3.6.1.2.1.4.5,RFC1213-MIB::ipInAddrErrors,Counter32,read-only,,mandatory,,The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
.1.3.6.1.2.1.4.6,RFC1213-MIB::ipForwDatagrams,Counter32,read-only,,mandatory,,The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.
.1.3.6.1.2.1.4.7,RFC1213-MIB::ipInUnknownProtos,Counter32,read-only,,mandatory,,The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
.1.3.6.1.2.1.4.8,RFC1213-MIB::ipInDiscards,Counter32,read-only,,mandatory,,The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
.1.3.6.1.2.1.4.9,RFC1213-MIB::ipInDelivers,Counter32,read-only,,mandatory,,The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
.1.3.6.1.2.1.4.10,RFC1213-MIB::ipOutRequests,Counter32,read-only,,mandatory,,The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
.1.3.6.1.2.1.4.11,RFC1213-MIB::ipOutDiscards,Counter32,read-only,,mandatory,,The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
.1.3.6.1.2.1.4.12,RFC1213-MIB::ipOutNoRoutes,Counter32,read-only,,mandatory,,The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down.
.1.3.6.1.2.1.4.13,RFC1213-MIB::ipReasmTimeout,INTEGER,read-only,,mandatory,,The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
.1.3.6.1.2.1.4.14,RFC1213-MIB::ipReasmReqds,Counter32,read-only,,mandatory,,The number of IP fragments received which needed to be reassembled at this entity.
.1.3.6.1.2.1.4.15,RFC1213-MIB::ipReasmOKs,Counter32,read-only,,mandatory,,The number of IP datagrams successfully re- assembled.
.1.3.6.1.2.1.4.16,RFC1213-MIB::ipReasmFails,Counter32,read-only,,mandatory,,The number of failures detected by the IP re- assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
.1.3.6.1.2.1.4.17,RFC1213-MIB::ipFragOKs,Counter32,read-only,,mandatory,,The number of IP datagrams that have been successfully fragmented at this entity.
.1.3.6.1.2.1.4.18,RFC1213-MIB::ipFragFails,Counter32,read-only,,mandatory,,The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
.1.3.6.1.2.1.4.19,RFC1213-MIB::ipFragCreates,Counter32,read-only,,mandatory,,The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
.1.3.6.1.2.1.4.20,RFC1213-MIB::ipAddrTable,,not-accessible,,mandatory,,The table of addressing information relevant to this entity's IP addresses.
.1.3.6.1.2.1.4.20.1,RFC1213-MIB::ipAddrEntry,,not-accessible,ipAdEntAddr,mandatory,,The addressing information for one of this entity's IP addresses.
.1.3.6.1.2.1.4.20.1.1,RFC1213-MIB::ipAdEntAddr,IpAddress,read-only,,mandatory,,The IP address to which this entry's addressing information pertains.
.1.3.6.1.2.1.4.20.1.2,RFC1213-MIB::ipAdEntIfIndex,INTEGER,read-only,,mandatory,,The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.20.1.3,RFC1213-MIB::ipAdEntNetMask,IpAddress,read-only,,mandatory,,The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.
.1.3.6.1.2.1.4.20.1.4,RFC1213-MIB::ipAdEntBcastAddr,INTEGER,read-only,,mandatory,,The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface.
.1.3.6.1.2.1.4.20.1.5,RFC1213-MIB::ipAdEntReasmMaxSize,INTEGER,read-only,,mandatory,,The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.
.1.3.6.1.2.1.4.21,RFC1213-MIB::ipRouteTable,,not-accessible,,mandatory,,This entity's IP Routing table.
.1.3.6.1.2.1.4.21.1,RFC1213-MIB::ipRouteEntry,,not-accessible,ipRouteDest,mandatory,,A route to a particular destination.
.1.3.6.1.2.1.4.21.1.1,RFC1213-MIB::ipRouteDest,IpAddress,read-write,,mandatory,,The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the table- access mechanisms defined by the network management protocol in use.
.1.3.6.1.2.1.4.21.1.2,RFC1213-MIB::ipRouteIfIndex,INTEGER,read-write,,mandatory,,The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.21.1.3,RFC1213-MIB::ipRouteMetric1,INTEGER,read-write,,mandatory,,The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.4,RFC1213-MIB::ipRouteMetric2,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.5,RFC1213-MIB::ipRouteMetric3,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.6,RFC1213-MIB::ipRouteMetric4,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.7,RFC1213-MIB::ipRouteNextHop,IpAddress,read-write,,mandatory,,The IP address of the next hop of this route. (In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)
.1.3.6.1.2.1.4.21.1.8,RFC1213-MIB::ipRouteType,INTEGER,read-write,,mandatory,other(1):invalid(2):direct(3):indirect(4),The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP architecture. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipRouteType object.
.1.3.6.1.2.1.4.21.1.9,RFC1213-MIB::ipRouteProto,INTEGER,read-only,,mandatory,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):is-is(9):es-is(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.4.21.1.10,RFC1213-MIB::ipRouteAge,INTEGER,read-write,,mandatory,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.4.21.1.11,RFC1213-MIB::ipRouteMask,IpAddress,read-write,,mandatory,,Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of: mask network 255.0.0.0 class-A 255.255.0.0 class-B 255.255.255.0 class-C If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism.
.1.3.6.1.2.1.4.21.1.12,RFC1213-MIB::ipRouteMetric5,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.13,RFC1213-MIB::ipRouteInfo,OBJECT,read-only,,mandatory,,A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
.1.3.6.1.2.1.4.22,RFC1213-MIB::ipNetToMediaTable,,not-accessible,,mandatory,,The IP Address Translation table used for mapping from IP addresses to physical addresses.
.1.3.6.1.2.1.4.22.1,RFC1213-MIB::ipNetToMediaEntry,,not-accessible,ipNetToMediaIfIndex:ipNetToMediaNetAddress,mandatory,,Each entry contains one IpAddress to `physical' address equivalence.
.1.3.6.1.2.1.4.22.1.1,RFC1213-MIB::ipNetToMediaIfIndex,INTEGER,read-write,,mandatory,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.22.1.2,RFC1213-MIB::ipNetToMediaPhysAddress,OCTET,read-write,,mandatory,,The media-dependent `physical' address.
.1.3.6.1.2.1.4.22.1.3,RFC1213-MIB::ipNetToMediaNetAddress,IpAddress,read-write,,mandatory,,The IpAddress corresponding to the media- dependent `physical' address.
.1.3.6.1.2.1.4.22.1.4,RFC1213-MIB::ipNetToMediaType,INTEGER,read-write,,mandatory,other(1):invalid(2):dynamic(3):static(4),The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToMediaType object.
.1.3.6.1.2.1.4.23,RFC1213-MIB::ipRoutingDiscards,Counter32,read-only,,mandatory,,The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
.1.3.6.1.2.1.5,RFC1213-MIB::icmp,,,,,,
.1.3.6.1.2.1.5.1,RFC1213-MIB::icmpInMsgs,Counter32,read-only,,mandatory,,The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
.1.3.6.1.2.1.5.2,RFC1213-MIB::icmpInErrors,Counter32,read-only,,mandatory,,The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
.1.3.6.1.2.1.5.3,RFC1213-MIB::icmpInDestUnreachs,Counter32,read-only,,mandatory,,The number of ICMP Destination Unreachable messages received.
.1.3.6.1.2.1.5.4,RFC1213-MIB::icmpInTimeExcds,Counter32,read-only,,mandatory,,The number of ICMP Time Exceeded messages received.
.1.3.6.1.2.1.5.5,RFC1213-MIB::icmpInParmProbs,Counter32,read-only,,mandatory,,The number of ICMP Parameter Problem messages received.
.1.3.6.1.2.1.5.6,RFC1213-MIB::icmpInSrcQuenchs,Counter32,read-only,,mandatory,,The number of ICMP Source Quench messages received.
.1.3.6.1.2.1.5.7,RFC1213-MIB::icmpInRedirects,Counter32,read-only,,mandatory,,The number of ICMP Redirect messages received.
.1.3.6.1.2.1.5.8,RFC1213-MIB::icmpInEchos,Counter32,read-only,,mandatory,,The number of ICMP Echo (request) messages received.
.1.3.6.1.2.1.5.9,RFC1213-MIB::icmpInEchoReps,Counter32,read-only,,mandatory,,The number of ICMP Echo Reply messages received.
.1.3.6.1.2.1.5.10,RFC1213-MIB::icmpInTimestamps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp (request) messages received.
.1.3.6.1.2.1.5.11,RFC1213-MIB::icmpInTimestampReps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp Reply messages received.
.1.3.6.1.2.1.5.12,RFC1213-MIB::icmpInAddrMasks,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Request messages received.
.1.3.6.1.2.1.5.13,RFC1213-MIB::icmpInAddrMaskReps,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Reply messages received.
.1.3.6.1.2.1.5.14,RFC1213-MIB::icmpOutMsgs,Counter32,read-only,,mandatory,,The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
.1.3.6.1.2.1.5.15,RFC1213-MIB::icmpOutErrors,Counter32,read-only,,mandatory,,The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
.1.3.6.1.2.1.5.16,RFC1213-MIB::icmpOutDestUnreachs,Counter32,read-only,,mandatory,,The number of ICMP Destination Unreachable messages sent.
.1.3.6.1.2.1.5.17,RFC1213-MIB::icmpOutTimeExcds,Counter32,read-only,,mandatory,,The number of ICMP Time Exceeded messages sent.
.1.3.6.1.2.1.5.18,RFC1213-MIB::icmpOutParmProbs,Counter32,read-only,,mandatory,,The number of ICMP Parameter Problem messages sent.
.1.3.6.1.2.1.5.19,RFC1213-MIB::icmpOutSrcQuenchs,Counter32,read-only,,mandatory,,The number of ICMP Source Quench messages sent.
.1.3.6.1.2.1.5.20,RFC1213-MIB::icmpOutRedirects,Counter32,read-only,,mandatory,,The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.
.1.3.6.1.2.1.5.21,RFC1213-MIB::icmpOutEchos,Counter32,read-only,,mandatory,,The number of ICMP Echo (request) messages sent.
.1.3.6.1.2.1.5.22,RFC1213-MIB::icmpOutEchoReps,Counter32,read-only,,mandatory,,The number of ICMP Echo Reply messages sent.
.1.3.6.1.2.1.5.23,RFC1213-MIB::icmpOutTimestamps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp (request) messages sent.
.1.3.6.1.2.1.5.24,RFC1213-MIB::icmpOutTimestampReps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp Reply messages sent.
.1.3.6.1.2.1.5.25,RFC1213-MIB::icmpOutAddrMasks,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Request messages sent.
.1.3.6.1.2.1.5.26,RFC1213-MIB::icmpOutAddrMaskReps,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Reply messages sent.
.1.3.6.1.2.1.6,RFC1213-MIB::tcp,,,,,,
.1.3.6.1.2.1.6.1,RFC1213-MIB::tcpRtoAlgorithm,INTEGER,read-only,,mandatory,other(1):constant(2):rsre(3):vanj(4),The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
.1.3.6.1.2.1.6.2,RFC1213-MIB::tcpRtoMin,INTEGER,read-only,,mandatory,,The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
.1.3.6.1.2.1.6.3,RFC1213-MIB::tcpRtoMax,INTEGER,read-only,,mandatory,,The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
.1.3.6.1.2.1.6.4,RFC1213-MIB::tcpMaxConn,INTEGER,read-only,,mandatory,,The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
.1.3.6.1.2.1.6.5,RFC1213-MIB::tcpActiveOpens,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
.1.3.6.1.2.1.6.6,RFC1213-MIB::tcpPassiveOpens,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
.1.3.6.1.2.1.6.7,RFC1213-MIB::tcpAttemptFails,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
.1.3.6.1.2.1.6.8,RFC1213-MIB::tcpEstabResets,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
.1.3.6.1.2.1.6.9,RFC1213-MIB::tcpCurrEstab,Gauge32,read-only,,mandatory,,The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
.1.3.6.1.2.1.6.10,RFC1213-MIB::tcpInSegs,Counter32,read-only,,mandatory,,The total number of segments received, including those received in error. This count includes segments received on currently established connections.
.1.3.6.1.2.1.6.11,RFC1213-MIB::tcpOutSegs,Counter32,read-only,,mandatory,,The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
.1.3.6.1.2.1.6.12,RFC1213-MIB::tcpRetransSegs,Counter32,read-only,,mandatory,,The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
.1.3.6.1.2.1.6.13,RFC1213-MIB::tcpConnTable,,not-accessible,,mandatory,,A table containing TCP connection-specific information.
.1.3.6.1.2.1.6.13.1,RFC1213-MIB::tcpConnEntry,,not-accessible,tcpConnLocalAddress:tcpConnLocalPort:tcpConnRemAddress:tcpConnRemPort,mandatory,,Information about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
.1.3.6.1.2.1.6.13.1.1,RFC1213-MIB::tcpConnState,INTEGER,read-write,,mandatory,closed(1):listen(2):synSent(3):synReceived(4):established(5):finWait1(6):finWait2(7):closeWait(8):lastAck(9):closing(10):timeWait(11):deleteTCB(12),The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
.1.3.6.1.2.1.6.13.1.2,RFC1213-MIB::tcpConnLocalAddress,IpAddress,read-only,,mandatory,,The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.
.1.3.6.1.2.1.6.13.1.3,RFC1213-MIB::tcpConnLocalPort,INTEGER,read-only,,mandatory,,The local port number for this TCP connection.
.1.3.6.1.2.1.6.13.1.4,RFC1213-MIB::tcpConnRemAddress,IpAddress,read-only,,mandatory,,The remote IP address for this TCP connection.
.1.3.6.1.2.1.6.13.1.5,RFC1213-MIB::tcpConnRemPort,INTEGER,read-only,,mandatory,,The remote port number for this TCP connection.
.1.3.6.1.2.1.6.14,RFC1213-MIB::tcpInErrs,Counter32,read-only,,mandatory,,The total number of segments received in error (e.g., bad TCP checksums).
.1.3.6.1.2.1.6.15,RFC1213-MIB::tcpOutRsts,Counter32,read-only,,mandatory,,The number of TCP segments sent containing the RST flag.
.1.3.6.1.2.1.7,RFC1213-MIB::udp,,,,,,
.1.3.6.1.2.1.7.1,RFC1213-MIB::udpInDatagrams,Counter32,read-only,,mandatory,,The total number of UDP datagrams delivered to UDP users.
.1.3.6.1.2.1.7.2,RFC1213-MIB::udpNoPorts,Counter32,read-only,,mandatory,,The total number of received UDP datagrams for which there was no application at the destination port.
.1.3.6.1.2.1.7.3,RFC1213-MIB::udpInErrors,Counter32,read-only,,mandatory,,The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
.1.3.6.1.2.1.7.4,RFC1213-MIB::udpOutDatagrams,Counter32,read-only,,mandatory,,The total number of UDP datagrams sent from this entity.
.1.3.6.1.2.1.7.5,RFC1213-MIB::udpTable,,not-accessible,,mandatory,,A table containing UDP listener information.
.1.3.6.1.2.1.7.5.1,RFC1213-MIB::udpEntry,,not-accessible,udpLocalAddress:udpLocalPort,mandatory,,Information about a particular current UDP listener.
.1.3.6.1.2.1.7.5.1.1,RFC1213-MIB::udpLocalAddress,IpAddress,read-only,,mandatory,,The local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.
.1.3.6.1.2.1.7.5.1.2,RFC1213-MIB::udpLocalPort,INTEGER,read-only,,mandatory,,The local port number for this UDP listener.
.1.3.6.1.2.1.8,RFC1213-MIB::egp,,,,,,
.1.3.6.1.2.1.8.1,RFC1213-MIB::egpInMsgs,Counter32,read-only,,mandatory,,The number of EGP messages received without error.
.1.3.6.1.2.1.8.2,RFC1213-MIB::egpInErrors,Counter32,read-only,,mandatory,,The number of EGP messages received that proved to be in error.
.1.3.6.1.2.1.8.3,RFC1213-MIB::egpOutMsgs,Counter32,read-only,,mandatory,,The total number of locally generated EGP messages.
.1.3.6.1.2.1.8.4,RFC1213-MIB::egpOutErrors,Counter32,read-only,,mandatory,,The number of locally generated EGP messages not sent due to resource limitations within an EGP entity.
.1.3.6.1.2.1.8.5,RFC1213-MIB::egpNeighTable,,not-accessible,,mandatory,,The EGP neighbor table.
.1.3.6.1.2.1.8.5.1,RFC1213-MIB::egpNeighEntry,,not-accessible,egpNeighAddr,mandatory,,Information about this entity's relationship with a particular EGP neighbor.
.1.3.6.1.2.1.8.5.1.1,RFC1213-MIB::egpNeighState,INTEGER,read-only,,mandatory,idle(1):acquisition(2):down(3):up(4):cease(5),The EGP state of the local system with respect to this entry's EGP neighbor. Each EGP state is represented by a value that is one greater than the numerical value associated with said state in RFC 904.
.1.3.6.1.2.1.8.5.1.2,RFC1213-MIB::egpNeighAddr,IpAddress,read-only,,mandatory,,The IP address of this entry's EGP neighbor.
.1.3.6.1.2.1.8.5.1.3,RFC1213-MIB::egpNeighAs,INTEGER,read-only,,mandatory,,The autonomous system of this EGP peer. Zero should be specified if the autonomous system number of the neighbor is not yet known.
.1.3.6.1.2.1.8.5.1.4,RFC1213-MIB::egpNeighInMsgs,Counter32,read-only,,mandatory,,The number of EGP messages received without error from this EGP peer.
.1.3.6.1.2.1.8.5.1.5,RFC1213-MIB::egpNeighInErrs,Counter32,read-only,,mandatory,,The number of EGP messages received from this EGP peer that proved to be in error (e.g., bad EGP checksum).
.1.3.6.1.2.1.8.5.1.6,RFC1213-MIB::egpNeighOutMsgs,Counter32,read-only,,mandatory,,The number of locally generated EGP messages to this EGP peer.
.1.3.6.1.2.1.8.5.1.7,RFC1213-MIB::egpNeighOutErrs,Counter32,read-only,,mandatory,,The number of locally generated EGP messages not sent to this EGP peer due to resource limitations within an EGP entity.
.1.3.6.1.2.1.8.5.1.8,RFC1213-MIB::egpNeighInErrMsgs,Counter32,read-only,,mandatory,,The number of EGP-defined error messages received from this EGP peer.
.1.3.6.1.2.1.8.5.1.9,RFC1213-MIB::egpNeighOutErrMsgs,Counter32,read-only,,mandatory,,The number of EGP-defined error messages sent to this EGP peer.
.1.3.6.1.2.1.8.5.1.10,RFC1213-MIB::egpNeighStateUps,Counter32,read-only,,mandatory,,The number of EGP state transitions to the UP state with this EGP peer.
.1.3.6.1.2.1.8.5.1.11,RFC1213-MIB::egpNeighStateDowns,Counter32,read-only,,mandatory,,The number of EGP state transitions from the UP state to any other state with this EGP peer.
.1.3.6.1.2.1.8.5.1.12,RFC1213-MIB::egpNeighIntervalHello,INTEGER,read-only,,mandatory,,The interval between EGP Hello command retransmissions (in hundredths of a second). This represents the t1 timer as defined in RFC 904.
.1.3.6.1.2.1.8.5.1.13,RFC1213-MIB::egpNeighIntervalPoll,INTEGER,read-only,,mandatory,,The interval between EGP poll command retransmissions (in hundredths of a second). This represents the t3 timer as defined in RFC 904.
.1.3.6.1.2.1.8.5.1.14,RFC1213-MIB::egpNeighMode,INTEGER,read-only,,mandatory,active(1):passive(2),The polling mode of this EGP entity, either passive or active.
.1.3.6.1.2.1.8.5.1.15,RFC1213-MIB::egpNeighEventTrigger,INTEGER,read-write,,mandatory,start(1):stop(2),A control variable used to trigger operator- initiated Start and Stop events. When read, this variable always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set since the last initialization of the network management subsystem on the node, it returns a value of `stop'. When set, this variable causes a Start or Stop event on the specified neighbor, as specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to the Idle state until a Start event occurs, either via egpNeighEventTrigger or otherwise.
.1.3.6.1.2.1.8.6,RFC1213-MIB::egpAs,INTEGER,read-only,,mandatory,,The autonomous system number of this EGP entity.
.1.3.6.1.2.1.10,SNMPv2-SMI::transmission,,,,,,
.1.3.6.1.2.1.11,SNMPv2-MIB::snmp,,,,,,
.1.3.6.1.2.1.11.1,SNMPv2-MIB::snmpInPkts,Counter32,read-only,,current,,The total number of messages delivered to the SNMP entity from the transport service.
.1.3.6.1.2.1.11.2,SNMPv2-MIB::snmpOutPkts,Counter32,read-only,,obsolete,,The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
.1.3.6.1.2.1.11.3,SNMPv2-MIB::snmpInBadVersions,Counter32,read-only,,current,,The total number of SNMP messages which were delivered to the SNMP entity and were for an unsupported SNMP version.
.1.3.6.1.2.1.11.4,SNMPv2-MIB::snmpInBadCommunityNames,Counter32,read-only,,current,,The total number of community-based SNMP messages (for example, SNMPv1) delivered to the SNMP entity which used an SNMP community name not known to said entity. Also, implementations which authenticate community-based SNMP messages using check(s) in addition to matching the community name (for example, by also checking whether the message originated from a transport address allowed to use a specified community name) MAY include in this value the number of messages which failed the additional check(s). It is strongly RECOMMENDED that the documentation for any security model which is used to authenticate community-based SNMP messages specify the precise conditions that contribute to this value.
.1.3.6.1.2.1.11.5,SNMPv2-MIB::snmpInBadCommunityUses,Counter32,read-only,,current,,The total number of community-based SNMP messages (for example, SNMPv1) delivered to the SNMP entity which represented an SNMP operation that was not allowed for the SNMP community named in the message. The precise conditions under which this counter is incremented (if at all) depend on how the SNMP entity implements its access control mechanism and how its applications interact with that access control mechanism. It is strongly RECOMMENDED that the documentation for any access control mechanism which is used to control access to and visibility of MIB instrumentation specify the precise conditions that contribute to this value.
.1.3.6.1.2.1.11.6,SNMPv2-MIB::snmpInASNParseErrs,Counter32,read-only,,current,,The total number of ASN.1 or BER errors encountered by the SNMP entity when decoding received SNMP messages.
.1.3.6.1.2.1.11.8,SNMPv2-MIB::snmpInTooBigs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `tooBig'.
.1.3.6.1.2.1.11.9,SNMPv2-MIB::snmpInNoSuchNames,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `noSuchName'.
.1.3.6.1.2.1.11.10,SNMPv2-MIB::snmpInBadValues,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `badValue'.
.1.3.6.1.2.1.11.11,SNMPv2-MIB::snmpInReadOnlys,Counter32,read-only,,obsolete,,The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.
.1.3.6.1.2.1.11.12,SNMPv2-MIB::snmpInGenErrs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `genErr'.
.1.3.6.1.2.1.11.13,SNMPv2-MIB::snmpInTotalReqVars,Counter32,read-only,,obsolete,,The total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
.1.3.6.1.2.1.11.14,SNMPv2-MIB::snmpInTotalSetVars,Counter32,read-only,,obsolete,,The total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs.
.1.3.6.1.2.1.11.15,SNMPv2-MIB::snmpInGetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.16,SNMPv2-MIB::snmpInGetNexts,Counter32,read-only,,obsolete,,The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.17,SNMPv2-MIB::snmpInSetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.18,SNMPv2-MIB::snmpInGetResponses,Counter32,read-only,,obsolete,,The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.19,SNMPv2-MIB::snmpInTraps,Counter32,read-only,,obsolete,,The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.20,SNMPv2-MIB::snmpOutTooBigs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `tooBig.'
.1.3.6.1.2.1.11.21,SNMPv2-MIB::snmpOutNoSuchNames,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status was `noSuchName'.
.1.3.6.1.2.1.11.22,SNMPv2-MIB::snmpOutBadValues,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `badValue'.
.1.3.6.1.2.1.11.24,SNMPv2-MIB::snmpOutGenErrs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `genErr'.
.1.3.6.1.2.1.11.25,SNMPv2-MIB::snmpOutGetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.26,SNMPv2-MIB::snmpOutGetNexts,Counter32,read-only,,obsolete,,The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.27,SNMPv2-MIB::snmpOutSetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.28,SNMPv2-MIB::snmpOutGetResponses,Counter32,read-only,,obsolete,,The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.29,SNMPv2-MIB::snmpOutTraps,Counter32,read-only,,obsolete,,The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.30,SNMPv2-MIB::snmpEnableAuthenTraps,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant across re-initializations of the network management system.
.1.3.6.1.2.1.11.31,SNMPv2-MIB::snmpSilentDrops,Counter32,read-only,,current,,The total number of Confirmed Class PDUs (such as GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs) delivered to the SNMP entity which were silently dropped because the size of a reply containing an alternate Response Class PDU (such as a Response-PDU) with an empty variable-bindings field was greater than either a local constraint or the maximum message size associated with the originator of the request.
.1.3.6.1.2.1.11.32,SNMPv2-MIB::snmpProxyDrops,Counter32,read-only,,current,,The total number of Confirmed Class PDUs (such as GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs) delivered to the SNMP entity which were silently dropped because the transmission of the (possibly translated) message to a proxy target failed in a manner (other than a time-out) such that no Response Class PDU (such as a Response-PDU) could be returned.
.1.3.6.1.2.1.16,RMON-MIB::rmon,,,,,,
.1.3.6.1.2.1.16.0,RMON-MIB::rmonEventsV2,,,,,,Definition point for RMON notifications.
.1.3.6.1.2.1.16.0.1,RMON-MIB::risingAlarm,,,,,,The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.
.1.3.6.1.2.1.16.0.2,RMON-MIB::fallingAlarm,,,,,,The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.
.1.3.6.1.2.1.16.1,RMON-MIB::statistics,,,,,,
.1.3.6.1.2.1.16.1.1,RMON-MIB::etherStatsTable,,not-accessible,,current,,A list of Ethernet statistics entries.
.1.3.6.1.2.1.16.1.1.1,RMON-MIB::etherStatsEntry,,not-accessible,etherStatsIndex,current,,A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1
.1.3.6.1.2.1.16.1.1.1.1,RMON-MIB::etherStatsIndex,Integer32,read-only,,current,,The value of this object uniquely identifies this etherStats entry.
.1.3.6.1.2.1.16.1.1.1.2,RMON-MIB::etherStatsDataSource,OBJECT,read-create,,current,,This object identifies the source of the data that this etherStats entry is configured to analyze. This source can be any ethernet interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated etherStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.1.1.3,RMON-MIB::etherStatsDropEvents,Counter32,read-only,,current,,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.
.1.3.6.1.2.1.16.1.1.1.4,RMON-MIB::etherStatsOctets,Counter32,read-only,,current,,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 10-Megabit 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 value Utilization which is the percent utilization of the ethernet segment on a scale of 0 to 100 percent.
.1.3.6.1.2.1.16.1.1.1.5,RMON-MIB::etherStatsPkts,Counter32,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
.1.3.6.1.2.1.16.1.1.1.6,RMON-MIB::etherStatsBroadcastPkts,Counter32,read-only,,current,,The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
.1.3.6.1.2.1.16.1.1.1.7,RMON-MIB::etherStatsMulticastPkts,Counter32,read-only,,current,,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.
.1.3.6.1.2.1.16.1.1.1.8,RMON-MIB::etherStatsCRCAlignErrors,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.9,RMON-MIB::etherStatsUndersizePkts,Counter32,read-only,,current,,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.
.1.3.6.1.2.1.16.1.1.1.10,RMON-MIB::etherStatsOversizePkts,Counter32,read-only,,current,,The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
.1.3.6.1.2.1.16.1.1.1.11,RMON-MIB::etherStatsFragments,Counter32,read-only,,current,,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.
.1.3.6.1.2.1.16.1.1.1.12,RMON-MIB::etherStatsJabbers,Counter32,read-only,,current,,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 than 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 where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
.1.3.6.1.2.1.16.1.1.1.13,RMON-MIB::etherStatsCollisions,Counter32,read-only,,current,,The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 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. 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 coax segments to which the repeater is connected.
.1.3.6.1.2.1.16.1.1.1.14,RMON-MIB::etherStatsPkts64Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.15,RMON-MIB::etherStatsPkts65to127Octets,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.16,RMON-MIB::etherStatsPkts128to255Octets,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.17,RMON-MIB::etherStatsPkts256to511Octets,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.18,RMON-MIB::etherStatsPkts512to1023Octets,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.19,RMON-MIB::etherStatsPkts1024to1518Octets,Counter32,read-only,,current,,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).
.1.3.6.1.2.1.16.1.1.1.20,RMON-MIB::etherStatsOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.1.1.21,RMON-MIB::etherStatsStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this etherStats entry.
.1.3.6.1.2.1.16.1.2,TOKEN-RING-RMON-MIB::tokenRingMLStatsTable,,not-accessible,,mandatory,,A list of Mac-Layer Token Ring statistics entries.
.1.3.6.1.2.1.16.1.2.1,TOKEN-RING-RMON-MIB::tokenRingMLStatsEntry,,not-accessible,tokenRingMLStatsIndex,mandatory,,A collection of Mac-Layer statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.1.2.1.1,TOKEN-RING-RMON-MIB::tokenRingMLStatsIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies this tokenRingMLStats entry.
.1.3.6.1.2.1.16.1.2.1.2,TOKEN-RING-RMON-MIB::tokenRingMLStatsDataSource,OBJECT,read-write,,mandatory,,This object identifies the source of the data that this tokenRingMLStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [3], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all error reports on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingMLStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.2.1.3,TOKEN-RING-RMON-MIB::tokenRingMLStatsDropEvents,Counter32,read-only,,mandatory,,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. This value is the same as the corresponding tokenRingPStatsDropEvents.
.1.3.6.1.2.1.16.1.2.1.4,TOKEN-RING-RMON-MIB::tokenRingMLStatsMacOctets,Counter32,read-only,,mandatory,,The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.2.1.5,TOKEN-RING-RMON-MIB::tokenRingMLStatsMacPkts,Counter32,read-only,,mandatory,,The total number of MAC packets (excluding packets that were not good frames) received.
.1.3.6.1.2.1.16.1.2.1.6,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPurgeEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the ring purge state from normal ring state. The ring purge state that comes in response to the claim token or beacon state is not counted.
.1.3.6.1.2.1.16.1.2.1.7,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPurgePkts,Counter32,read-only,,mandatory,,The total number of ring purge MAC packets detected by probe.
.1.3.6.1.2.1.16.1.2.1.8,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) from a non-beaconing state. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
.1.3.6.1.2.1.16.1.2.1.9,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconTime,INTEGER,read-only,,mandatory,,The total amount of time that the ring has been in the beaconing state.
.1.3.6.1.2.1.16.1.2.1.10,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconPkts,Counter32,read-only,,mandatory,,The total number of beacon MAC packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.11,TOKEN-RING-RMON-MIB::tokenRingMLStatsClaimTokenEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the claim token state from normal ring state or ring purge state. The claim token state that comes in response to a beacon state is not counted.
.1.3.6.1.2.1.16.1.2.1.12,TOKEN-RING-RMON-MIB::tokenRingMLStatsClaimTokenPkts,Counter32,read-only,,mandatory,,The total number of claim token MAC packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.13,TOKEN-RING-RMON-MIB::tokenRingMLStatsNAUNChanges,Counter32,read-only,,mandatory,,The total number of NAUN changes detected by the probe.
.1.3.6.1.2.1.16.1.2.1.14,TOKEN-RING-RMON-MIB::tokenRingMLStatsLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.15,TOKEN-RING-RMON-MIB::tokenRingMLStatsInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.16,TOKEN-RING-RMON-MIB::tokenRingMLStatsBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.17,TOKEN-RING-RMON-MIB::tokenRingMLStatsACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.18,TOKEN-RING-RMON-MIB::tokenRingMLStatsAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.19,TOKEN-RING-RMON-MIB::tokenRingMLStatsLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.20,TOKEN-RING-RMON-MIB::tokenRingMLStatsCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.21,TOKEN-RING-RMON-MIB::tokenRingMLStatsFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.22,TOKEN-RING-RMON-MIB::tokenRingMLStatsFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.23,TOKEN-RING-RMON-MIB::tokenRingMLStatsTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.24,TOKEN-RING-RMON-MIB::tokenRingMLStatsSoftErrorReports,Counter32,read-only,,mandatory,,The total number of soft error report frames detected by the probe.
.1.3.6.1.2.1.16.1.2.1.25,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPollEvents,Counter32,read-only,,mandatory,,The total number of ring poll events detected by the probe (i.e. the number of ring polls initiated by the active monitor that were detected).
.1.3.6.1.2.1.16.1.2.1.26,TOKEN-RING-RMON-MIB::tokenRingMLStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.2.1.27,TOKEN-RING-RMON-MIB::tokenRingMLStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this tokenRingMLStats entry.
.1.3.6.1.2.1.16.1.3,TOKEN-RING-RMON-MIB::tokenRingPStatsTable,,not-accessible,,mandatory,,A list of promiscuous Token Ring statistics entries.
.1.3.6.1.2.1.16.1.3.1,TOKEN-RING-RMON-MIB::tokenRingPStatsEntry,,not-accessible,tokenRingPStatsIndex,mandatory,,A collection of promiscuous statistics kept for non-MAC packets on a particular Token Ring interface.
.1.3.6.1.2.1.16.1.3.1.1,TOKEN-RING-RMON-MIB::tokenRingPStatsIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies this tokenRingPStats entry.
.1.3.6.1.2.1.16.1.3.1.2,TOKEN-RING-RMON-MIB::tokenRingPStatsDataSource,OBJECT,read-write,,mandatory,,This object identifies the source of the data that this tokenRingPStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [3], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all non-MAC packets on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingPStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.3.1.3,TOKEN-RING-RMON-MIB::tokenRingPStatsDropEvents,Counter32,read-only,,mandatory,,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. This value is the same as the corresponding tokenRingMLStatsDropEvents
.1.3.6.1.2.1.16.1.3.1.4,TOKEN-RING-RMON-MIB::tokenRingPStatsDataOctets,Counter32,read-only,,mandatory,,The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets.
.1.3.6.1.2.1.16.1.3.1.5,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts,Counter32,read-only,,mandatory,,The total number of non-MAC packets in good frames. received.
.1.3.6.1.2.1.16.1.3.1.6,TOKEN-RING-RMON-MIB::tokenRingPStatsDataBroadcastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
.1.3.6.1.2.1.16.1.3.1.7,TOKEN-RING-RMON-MIB::tokenRingPStatsDataMulticastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.1.3.1.8,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts18to63Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.9,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts64to127Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.10,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts128to255Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.11,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts256to511Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.12,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts512to1023Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.13,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts1024to2047Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.14,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts2048to4095Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.15,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts4096to8191Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.16,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts8192to18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.17,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPktsGreaterThan18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.18,TOKEN-RING-RMON-MIB::tokenRingPStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.3.1.19,TOKEN-RING-RMON-MIB::tokenRingPStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this tokenRingPStats entry.
.1.3.6.1.2.1.16.1.4,RMON2-MIB::etherStats2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.4.1,RMON2-MIB::etherStats2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.4.1.1,RMON2-MIB::etherStatsDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.4.1.2,RMON2-MIB::etherStatsCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.1.5,RMON2-MIB::tokenRingMLStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.1.5.1,RMON2-MIB::tokenRingMLStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.5.1.1,RMON2-MIB::tokenRingMLStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.5.1.2,RMON2-MIB::tokenRingMLStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.1.6,RMON2-MIB::tokenRingPStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.1.6.1,RMON2-MIB::tokenRingPStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.6.1.1,RMON2-MIB::tokenRingPStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.6.1.2,RMON2-MIB::tokenRingPStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.2,RMON-MIB::history,,,,,,
.1.3.6.1.2.1.16.2.1,RMON-MIB::historyControlTable,,not-accessible,,current,,A list of history control entries.
.1.3.6.1.2.1.16.2.1.1,RMON-MIB::historyControlEntry,,not-accessible,historyControlIndex,current,,A list of parameters that set up a periodic sampling of statistics. As an example, an instance of the historyControlInterval object might be named historyControlInterval.2
.1.3.6.1.2.1.16.2.1.1.1,RMON-MIB::historyControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the historyControl table. Each such entry defines a set of samples at a particular interval for an interface on the device.
.1.3.6.1.2.1.16.2.1.1.2,RMON-MIB::historyControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data for which historical data was collected and placed in a media-specific table on behalf of this historyControlEntry. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated historyControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.2.1.1.3,RMON-MIB::historyControlBucketsRequested,Integer32,read-create,,current,,The requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry. When this object is created or modified, the probe should set historyControlBucketsGranted as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.2.1.1.4,RMON-MIB::historyControlBucketsGranted,Integer32,read-only,,current,,The number of discrete sampling intervals over which data shall be saved in the part of the media-specific table associated with this historyControlEntry. When the associated historyControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated historyControlBucketsRequested object. There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the media-specific table. When the number of buckets reaches the value of this object and a new bucket is to be added to the media-specific table, the oldest bucket associated with this historyControlEntry shall be deleted by the agent so that the new bucket can be added. When the value of this object changes to a value less than the current value, entries are deleted from the media-specific table associated with this historyControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated media- specific entries may be allowed to grow.
.1.3.6.1.2.1.16.2.1.1.5,RMON-MIB::historyControlInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the historyControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the etherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated historyControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.2.1.1.6,RMON-MIB::historyControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.2.1.1.7,RMON-MIB::historyControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this historyControl entry. Each instance of the media-specific table associated with this historyControlEntry will be deleted by the agent if this historyControlEntry is not equal to valid(1).
.1.3.6.1.2.1.16.2.2,RMON-MIB::etherHistoryTable,,not-accessible,,current,,A list of Ethernet history entries.
.1.3.6.1.2.1.16.2.2.1,RMON-MIB::etherHistoryEntry,,not-accessible,etherHistoryIndex:etherHistorySampleIndex,current,,An historical sample of Ethernet statistics on a particular Ethernet interface. This sample is associated with the historyControlEntry which set up the parameters for a regular collection of these samples. As an example, an instance of the etherHistoryPkts object might be named etherHistoryPkts.2.89
.1.3.6.1.2.1.16.2.2.1.1,RMON-MIB::etherHistoryIndex,Integer32,read-only,,current,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.2.1.2,RMON-MIB::etherHistorySampleIndex,Integer32,read-only,,current,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.2.1.3,RMON-MIB::etherHistoryIntervalStart,TimeTicks,read-only,,current,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.2.1.4,RMON-MIB::etherHistoryDropEvents,Counter32,read-only,,current,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.2.1.5,RMON-MIB::etherHistoryOctets,Counter32,read-only,,current,,The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.2.2.1.6,RMON-MIB::etherHistoryPkts,Counter32,read-only,,current,,The number of packets (including bad packets) received during this sampling interval.
.1.3.6.1.2.1.16.2.2.1.7,RMON-MIB::etherHistoryBroadcastPkts,Counter32,read-only,,current,,The number of good packets received during this sampling interval that were directed to the broadcast address.
.1.3.6.1.2.1.16.2.2.1.8,RMON-MIB::etherHistoryMulticastPkts,Counter32,read-only,,current,,The number of good packets received during this sampling interval that were directed to a multicast address. Note that this number does not include packets addressed to the broadcast address.
.1.3.6.1.2.1.16.2.2.1.9,RMON-MIB::etherHistoryCRCAlignErrors,Counter32,read-only,,current,,The number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) 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).
.1.3.6.1.2.1.16.2.2.1.10,RMON-MIB::etherHistoryUndersizePkts,Counter32,read-only,,current,,The number of packets received during this sampling interval that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.
.1.3.6.1.2.1.16.2.2.1.11,RMON-MIB::etherHistoryOversizePkts,Counter32,read-only,,current,,The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed.
.1.3.6.1.2.1.16.2.2.1.12,RMON-MIB::etherHistoryFragments,Counter32,read-only,,current,,The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS octets) 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 etherHistoryFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
.1.3.6.1.2.1.16.2.2.1.13,RMON-MIB::etherHistoryJabbers,Counter32,read-only,,current,,The number of packets received during this sampling interval 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 than 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 where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
.1.3.6.1.2.1.16.2.2.1.14,RMON-MIB::etherHistoryCollisions,Counter32,read-only,,current,,The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 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. 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 coax segments to which the repeater is connected.
.1.3.6.1.2.1.16.2.2.1.15,RMON-MIB::etherHistoryUtilization,Integer32,read-only,,current,,The best estimate of the mean physical layer network utilization on this interface during this sampling interval, in hundredths of a percent.
.1.3.6.1.2.1.16.2.3,TOKEN-RING-RMON-MIB::tokenRingMLHistoryTable,,not-accessible,,mandatory,,A list of Mac-Layer Token Ring statistics entries.
.1.3.6.1.2.1.16.2.3.1,TOKEN-RING-RMON-MIB::tokenRingMLHistoryEntry,,not-accessible,tokenRingMLHistoryIndex:tokenRingMLHistorySampleIndex,mandatory,,A collection of Mac-Layer statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.2.3.1.1,TOKEN-RING-RMON-MIB::tokenRingMLHistoryIndex,INTEGER,read-only,,mandatory,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.3.1.2,TOKEN-RING-RMON-MIB::tokenRingMLHistorySampleIndex,INTEGER,read-only,,mandatory,,An index that uniquely identifies the particular Mac-Layer sample this entry represents among all Mac-Layer samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.3.1.3,TOKEN-RING-RMON-MIB::tokenRingMLHistoryIntervalStart,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.3.1.4,TOKEN-RING-RMON-MIB::tokenRingMLHistoryDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.3.1.5,TOKEN-RING-RMON-MIB::tokenRingMLHistoryMacOctets,Counter32,read-only,,mandatory,,The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network during this sampling interval (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.2.3.1.6,TOKEN-RING-RMON-MIB::tokenRingMLHistoryMacPkts,Counter32,read-only,,mandatory,,The total number of MAC packets (excluding those that were not good frames) received during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.7,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPurgeEvents,Counter32,read-only,,mandatory,,The total number of times that the ring entered the ring purge state from normal ring state during this sampling interval. The ring purge state that comes from the claim token or beacon state is not counted.
.1.3.6.1.2.1.16.2.3.1.8,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPurgePkts,Counter32,read-only,,mandatory,,The total number of Ring Purge MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.9,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) during this sampling interval. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
.1.3.6.1.2.1.16.2.3.1.10,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconTime,INTEGER,read-only,,mandatory,,The amount of time that the ring has been in the beaconing state during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.11,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconPkts,Counter32,read-only,,mandatory,,The total number of beacon MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.12,TOKEN-RING-RMON-MIB::tokenRingMLHistoryClaimTokenEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the claim token state from normal ring state or ring purge state during this sampling interval. The claim token state that comes from the beacon state is not counted.
.1.3.6.1.2.1.16.2.3.1.13,TOKEN-RING-RMON-MIB::tokenRingMLHistoryClaimTokenPkts,Counter32,read-only,,mandatory,,The total number of claim token MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.14,TOKEN-RING-RMON-MIB::tokenRingMLHistoryNAUNChanges,Counter32,read-only,,mandatory,,The total number of NAUN changes detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.15,TOKEN-RING-RMON-MIB::tokenRingMLHistoryLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.16,TOKEN-RING-RMON-MIB::tokenRingMLHistoryInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.17,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.18,TOKEN-RING-RMON-MIB::tokenRingMLHistoryACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.19,TOKEN-RING-RMON-MIB::tokenRingMLHistoryAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.20,TOKEN-RING-RMON-MIB::tokenRingMLHistoryLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.21,TOKEN-RING-RMON-MIB::tokenRingMLHistoryCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.22,TOKEN-RING-RMON-MIB::tokenRingMLHistoryFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.23,TOKEN-RING-RMON-MIB::tokenRingMLHistoryFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.24,TOKEN-RING-RMON-MIB::tokenRingMLHistoryTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.25,TOKEN-RING-RMON-MIB::tokenRingMLHistorySoftErrorReports,Counter32,read-only,,mandatory,,The total number of soft error report frames detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.26,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPollEvents,Counter32,read-only,,mandatory,,The total number of ring poll events detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.27,TOKEN-RING-RMON-MIB::tokenRingMLHistoryActiveStations,INTEGER,read-only,,mandatory,,The maximum number of active stations on the ring detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.4,TOKEN-RING-RMON-MIB::tokenRingPHistoryTable,,not-accessible,,mandatory,,A list of promiscuous Token Ring statistics entries.
.1.3.6.1.2.1.16.2.4.1,TOKEN-RING-RMON-MIB::tokenRingPHistoryEntry,,not-accessible,tokenRingPHistoryIndex:tokenRingPHistorySampleIndex,mandatory,,A collection of promiscuous statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.2.4.1.1,TOKEN-RING-RMON-MIB::tokenRingPHistoryIndex,INTEGER,read-only,,mandatory,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.4.1.2,TOKEN-RING-RMON-MIB::tokenRingPHistorySampleIndex,INTEGER,read-only,,mandatory,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.4.1.3,TOKEN-RING-RMON-MIB::tokenRingPHistoryIntervalStart,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.4.1.4,TOKEN-RING-RMON-MIB::tokenRingPHistoryDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.4.1.5,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataOctets,Counter32,read-only,,mandatory,,The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets during this sampling interval.
.1.3.6.1.2.1.16.2.4.1.6,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval.
.1.3.6.1.2.1.16.2.4.1.7,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataBroadcastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
.1.3.6.1.2.1.16.2.4.1.8,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataMulticastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.2.4.1.9,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts18to63Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.10,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts64to127Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.11,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts128to255Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.12,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts256to511Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.13,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts512to1023Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.14,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts1024to2047Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.15,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts2048to4095Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.16,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts4096to8191Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.17,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts8192to18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.18,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPktsGreaterThan18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.5,RMON2-MIB::historyControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.2.5.1,RMON2-MIB::historyControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.2.5.1.1,RMON2-MIB::historyControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.3,RMON-MIB::alarm,,,,,,
.1.3.6.1.2.1.16.3.1,RMON-MIB::alarmTable,,not-accessible,,current,,A list of alarm entries.
.1.3.6.1.2.1.16.3.1.1,RMON-MIB::alarmEntry,,not-accessible,alarmIndex,current,,A list of parameters that set up a periodic checking for alarm conditions. For example, an instance of the alarmValue object might be named alarmValue.8
.1.3.6.1.2.1.16.3.1.1.1,RMON-MIB::alarmIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.
.1.3.6.1.2.1.16.3.1.1.2,RMON-MIB::alarmInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be taken in the case of deltaValue sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2^31 - 1 during a single sampling interval. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.3,RMON-MIB::alarmVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. If at any time the variable name of an established alarmEntry is no longer available in the selected MIB view, the probe must change the status of this alarmEntry to invalid(4). This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.4,RMON-MIB::alarmSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is absoluteValue(1), the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.5,RMON-MIB::alarmValue,Integer32,read-only,,current,,The value of the statistic during the last sampling period. For example, if the sample type is deltaValue, this value will be the difference between the samples at the beginning and end of the period. If the sample type is absoluteValue, this value will be the sampled value at the end of the period. This is the value that is compared with the rising and falling thresholds. The value during the current sampling period is not made available until the period is completed and will remain available until the next period completes.
.1.3.6.1.2.1.16.3.1.1.6,RMON-MIB::alarmStartupAlarm,INTEGER,read-create,,current,risingAlarm(1):fallingAlarm(2):risingOrFallingAlarm(3),The alarm that may be sent when this entry is first set to valid. If the first sample after this entry becomes valid is greater than or equal to the risingThreshold and alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the fallingThreshold and alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.7,RMON-MIB::alarmRisingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the alarmFallingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.8,RMON-MIB::alarmFallingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the alarmRisingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.9,RMON-MIB::alarmRisingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.10,RMON-MIB::alarmFallingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.11,RMON-MIB::alarmOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.3.1.1.12,RMON-MIB::alarmStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this alarm entry.
.1.3.6.1.2.1.16.4,RMON-MIB::hosts,,,,,,
.1.3.6.1.2.1.16.4.1,RMON-MIB::hostControlTable,,not-accessible,,current,,A list of host table control entries.
.1.3.6.1.2.1.16.4.1.1,RMON-MIB::hostControlEntry,,not-accessible,hostControlIndex,current,,A list of parameters that set up the discovery of hosts on a particular interface and the collection of statistics about these hosts. For example, an instance of the hostControlTableSize object might be named hostControlTableSize.1
.1.3.6.1.2.1.16.4.1.1.1,RMON-MIB::hostControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostControl table. Each such entry defines a function that discovers hosts on a particular interface and places statistics about them in the hostTable and the hostTimeTable on behalf of this hostControlEntry.
.1.3.6.1.2.1.16.4.1.1.2,RMON-MIB::hostControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data for this instance of the host function. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated hostControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.4.1.1.3,RMON-MIB::hostControlTableSize,Integer32,read-only,,current,,The number of hostEntries in the hostTable and the hostTimeTable associated with this hostControlEntry.
.1.3.6.1.2.1.16.4.1.1.4,RMON-MIB::hostControlLastDeleteTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last entry was deleted from the portion of the hostTable associated with this hostControlEntry. If no deletions have occurred, this value shall be zero.
.1.3.6.1.2.1.16.4.1.1.5,RMON-MIB::hostControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.4.1.1.6,RMON-MIB::hostControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this hostControl entry. If this object is not equal to valid(1), all associated entries in the hostTable, hostTimeTable, and the hostTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.4.2,RMON-MIB::hostTable,,not-accessible,,current,,A list of host entries.
.1.3.6.1.2.1.16.4.2.1,RMON-MIB::hostEntry,,not-accessible,hostIndex:hostAddress,current,,A collection of statistics for a particular host that has been discovered on an interface of this device. For example, an instance of the hostOutBroadcastPkts object might be named hostOutBroadcastPkts.1.6.8.0.32.27.3.176
.1.3.6.1.2.1.16.4.2.1.1,RMON-MIB::hostAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.4.2.1.2,RMON-MIB::hostCreationOrder,Integer32,read-only,,current,,An index that defines the relative ordering of the creation time of hosts captured for a particular hostControlEntry. This index shall be between 1 and N, where N is the value of the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later. It is important to note that the order for a particular entry may change as an (earlier) entry is deleted from the table. Because this order may change, management stations should make use of the hostControlLastDeleteTime variable in the hostControlEntry associated with the relevant portion of the hostTable. By observing this variable, the management station may detect the circumstances where a previous association between a value of hostCreationOrder and a hostEntry may no longer hold.
.1.3.6.1.2.1.16.4.2.1.3,RMON-MIB::hostIndex,Integer32,read-only,,current,,The set of collected host statistics of which this entry is a part. The set of hosts identified by a particular value of this index is associated with the hostControlEntry as identified by the same value of hostControlIndex.
.1.3.6.1.2.1.16.4.2.1.4,RMON-MIB::hostInPkts,Counter32,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.5,RMON-MIB::hostOutPkts,Counter32,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.6,RMON-MIB::hostInOctets,Counter32,read-only,,current,,The number of octets transmitted to this address since it was added to the hostTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.2.1.7,RMON-MIB::hostOutOctets,Counter32,read-only,,current,,The number of octets transmitted by this address since it was added to the hostTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.4.2.1.8,RMON-MIB::hostOutErrors,Counter32,read-only,,current,,The number of bad packets transmitted by this address since this host was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.9,RMON-MIB::hostOutBroadcastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to the broadcast address since this host was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.10,RMON-MIB::hostOutMulticastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to a multicast address since this host was added to the hostTable. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.4.3,RMON-MIB::hostTimeTable,,not-accessible,,current,,A list of time-ordered host table entries.
.1.3.6.1.2.1.16.4.3.1,RMON-MIB::hostTimeEntry,,not-accessible,hostTimeIndex:hostTimeCreationOrder,current,,A collection of statistics for a particular host that has been discovered on an interface of this device. This collection includes the relative ordering of the creation time of this object. For example, an instance of the hostTimeOutBroadcastPkts object might be named hostTimeOutBroadcastPkts.1.687
.1.3.6.1.2.1.16.4.3.1.1,RMON-MIB::hostTimeAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.4.3.1.2,RMON-MIB::hostTimeCreationOrder,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTime table among those entries associated with the same hostControlEntry. This index shall be between 1 and N, where N is the value of the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later. Thus the management station has the ability to learn of new entries added to this table without downloading the entire table. It is important to note that the index for a particular entry may change as an (earlier) entry is deleted from the table. Because this order may change, management stations should make use of the hostControlLastDeleteTime variable in the hostControlEntry associated with the relevant portion of the hostTimeTable. By observing this variable, the management station may detect the circumstances where a download of the table may have missed entries, and where a previous association between a value of hostTimeCreationOrder and a hostTimeEntry may no longer hold.
.1.3.6.1.2.1.16.4.3.1.3,RMON-MIB::hostTimeIndex,Integer32,read-only,,current,,The set of collected host statistics of which this entry is a part. The set of hosts identified by a particular value of this index is associated with the hostControlEntry as identified by the same value of hostControlIndex.
.1.3.6.1.2.1.16.4.3.1.4,RMON-MIB::hostTimeInPkts,Counter32,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.5,RMON-MIB::hostTimeOutPkts,Counter32,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.6,RMON-MIB::hostTimeInOctets,Counter32,read-only,,current,,The number of octets transmitted to this address since it was added to the hostTimeTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.3.1.7,RMON-MIB::hostTimeOutOctets,Counter32,read-only,,current,,The number of octets transmitted by this address since it was added to the hostTimeTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.4.3.1.8,RMON-MIB::hostTimeOutErrors,Counter32,read-only,,current,,The number of bad packets transmitted by this address since this host was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.9,RMON-MIB::hostTimeOutBroadcastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to the broadcast address since this host was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.10,RMON-MIB::hostTimeOutMulticastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to a multicast address since this host was added to the hostTimeTable. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.4.4,RMON2-MIB::hostControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.4.4.1,RMON2-MIB::hostControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.4.4.1.1,RMON2-MIB::hostControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.4.4.1.2,RMON2-MIB::hostControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.5,RMON-MIB::hostTopN,,,,,,
.1.3.6.1.2.1.16.5.1,RMON-MIB::hostTopNControlTable,,not-accessible,,current,,A list of top N host control entries.
.1.3.6.1.2.1.16.5.1.1,RMON-MIB::hostTopNControlEntry,,not-accessible,hostTopNControlIndex,current,,A set of parameters that control the creation of a report of the top N hosts according to several metrics. For example, an instance of the hostTopNDuration object might be named hostTopNDuration.3
.1.3.6.1.2.1.16.5.1.1.1,RMON-MIB::hostTopNControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTopNControl table. Each such entry defines one top N report prepared for one interface.
.1.3.6.1.2.1.16.5.1.1.2,RMON-MIB::hostTopNHostIndex,Integer32,read-create,,current,,The host table for which a top N report will be prepared on behalf of this entry. The host table identified by a particular value of this index is associated with the same host table as identified by the same value of hostIndex. This object may not be modified if the associated hostTopNStatus object is equal to valid(1).
.1.3.6.1.2.1.16.5.1.1.3,RMON-MIB::hostTopNRateBase,INTEGER,read-create,,current,hostTopNInPkts(1):hostTopNOutPkts(2):hostTopNInOctets(3):hostTopNOutOctets(4):hostTopNOutErrors(5):hostTopNOutBroadcastPkts(6):hostTopNOutMulticastPkts(7),The variable for each host that the hostTopNRate variable is based upon. This object may not be modified if the associated hostTopNStatus object is equal to valid(1).
.1.3.6.1.2.1.16.5.1.1.4,RMON-MIB::hostTopNTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated hostTopNDuration object. When this object is set to a non-zero value, any associated hostTopNEntries shall be made inaccessible by the monitor. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated hostTopNEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the hostTopNTable. Thus, the hostTopN table needs to be created only at the end of the collection interval.
.1.3.6.1.2.1.16.5.1.1.5,RMON-MIB::hostTopNDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval. When the associated hostTopNTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the hostTopNTimeRemaining is set. This value shall be zero if no reports have been requested for this hostTopNControlEntry.
.1.3.6.1.2.1.16.5.1.1.6,RMON-MIB::hostTopNRequestedSize,Integer32,read-create,,current,,The maximum number of hosts requested for the top N table. When this object is created or modified, the probe should set hostTopNGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.5.1.1.7,RMON-MIB::hostTopNGrantedSize,Integer32,read-only,,current,,The maximum number of hosts in the top N table. When the associated hostTopNRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated hostTopNRequestedSize object. Hosts with the highest value of hostTopNRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more hosts.
.1.3.6.1.2.1.16.5.1.1.8,RMON-MIB::hostTopNStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated hostTopNTimeRemaining object was modified to start the requested report.
.1.3.6.1.2.1.16.5.1.1.9,RMON-MIB::hostTopNOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.5.1.1.10,RMON-MIB::hostTopNStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this hostTopNControl entry. If this object is not equal to valid(1), all associated hostTopNEntries shall be deleted by the agent.
.1.3.6.1.2.1.16.5.2,RMON-MIB::hostTopNTable,,not-accessible,,current,,A list of top N host entries.
.1.3.6.1.2.1.16.5.2.1,RMON-MIB::hostTopNEntry,,not-accessible,hostTopNReport:hostTopNIndex,current,,A set of statistics for a host that is part of a top N report. For example, an instance of the hostTopNRate object might be named hostTopNRate.3.10
.1.3.6.1.2.1.16.5.2.1.1,RMON-MIB::hostTopNReport,Integer32,read-only,,current,,This object identifies the top N report of which this entry is a part. The set of hosts identified by a particular value of this object is part of the same report as identified by the same value of the hostTopNControlIndex object.
.1.3.6.1.2.1.16.5.2.1.2,RMON-MIB::hostTopNIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTopN table among those in the same report. This index is between 1 and N, where N is the number of entries in this table. Increasing values of hostTopNIndex shall be assigned to entries with decreasing values of hostTopNRate until index N is assigned to the entry with the lowest value of hostTopNRate or there are no more hostTopNEntries.
.1.3.6.1.2.1.16.5.2.1.3,RMON-MIB::hostTopNAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.5.2.1.4,RMON-MIB::hostTopNRate,Integer32,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this host's instance of the object selected by hostTopNRateBase.
.1.3.6.1.2.1.16.6,RMON-MIB::matrix,,,,,,
.1.3.6.1.2.1.16.6.1,RMON-MIB::matrixControlTable,,not-accessible,,current,,A list of information entries for the traffic matrix on each interface.
.1.3.6.1.2.1.16.6.1.1,RMON-MIB::matrixControlEntry,,not-accessible,matrixControlIndex,current,,Information about a traffic matrix on a particular interface. For example, an instance of the matrixControlLastDeleteTime object might be named matrixControlLastDeleteTime.1
.1.3.6.1.2.1.16.6.1.1.1,RMON-MIB::matrixControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the matrixControl table. Each such entry defines a function that discovers conversations on a particular interface and places statistics about them in the matrixSDTable and the matrixDSTable on behalf of this matrixControlEntry.
.1.3.6.1.2.1.16.6.1.1.2,RMON-MIB::matrixControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data from which this entry creates a traffic matrix. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated matrixControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.6.1.1.3,RMON-MIB::matrixControlTableSize,Integer32,read-only,,current,,The number of matrixSDEntries in the matrixSDTable for this interface. This must also be the value of the number of entries in the matrixDSTable for this interface.
.1.3.6.1.2.1.16.6.1.1.4,RMON-MIB::matrixControlLastDeleteTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last entry was deleted from the portion of the matrixSDTable or matrixDSTable associated with this matrixControlEntry. If no deletions have occurred, this value shall be zero.
.1.3.6.1.2.1.16.6.1.1.5,RMON-MIB::matrixControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.6.1.1.6,RMON-MIB::matrixControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this matrixControl entry. If this object is not equal to valid(1), all associated entries in the matrixSDTable and the matrixDSTable shall be deleted by the agent.
.1.3.6.1.2.1.16.6.2,RMON-MIB::matrixSDTable,,not-accessible,,current,,A list of traffic matrix entries indexed by source and destination MAC address.
.1.3.6.1.2.1.16.6.2.1,RMON-MIB::matrixSDEntry,,not-accessible,matrixSDIndex:matrixSDSourceAddress:matrixSDDestAddress,current,,A collection of statistics for communications between two addresses on a particular interface. For example, an instance of the matrixSDPkts object might be named matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113
.1.3.6.1.2.1.16.6.2.1.1,RMON-MIB::matrixSDSourceAddress,OCTET,read-only,,current,,The source physical address.
.1.3.6.1.2.1.16.6.2.1.2,RMON-MIB::matrixSDDestAddress,OCTET,read-only,,current,,The destination physical address.
.1.3.6.1.2.1.16.6.2.1.3,RMON-MIB::matrixSDIndex,Integer32,read-only,,current,,The set of collected matrix statistics of which this entry is a part. The set of matrix statistics identified by a particular value of this index is associated with the same matrixControlEntry as identified by the same value of matrixControlIndex.
.1.3.6.1.2.1.16.6.2.1.4,RMON-MIB::matrixSDPkts,Counter32,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.2.1.5,RMON-MIB::matrixSDOctets,Counter32,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.2.1.6,RMON-MIB::matrixSDErrors,Counter32,read-only,,current,,The number of bad packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.3,RMON-MIB::matrixDSTable,,not-accessible,,current,,A list of traffic matrix entries indexed by destination and source MAC address.
.1.3.6.1.2.1.16.6.3.1,RMON-MIB::matrixDSEntry,,not-accessible,matrixDSIndex:matrixDSDestAddress:matrixDSSourceAddress,current,,A collection of statistics for communications between two addresses on a particular interface. For example, an instance of the matrixSDPkts object might be named matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176
.1.3.6.1.2.1.16.6.3.1.1,RMON-MIB::matrixDSSourceAddress,OCTET,read-only,,current,,The source physical address.
.1.3.6.1.2.1.16.6.3.1.2,RMON-MIB::matrixDSDestAddress,OCTET,read-only,,current,,The destination physical address.
.1.3.6.1.2.1.16.6.3.1.3,RMON-MIB::matrixDSIndex,Integer32,read-only,,current,,The set of collected matrix statistics of which this entry is a part. The set of matrix statistics identified by a particular value of this index is associated with the same matrixControlEntry as identified by the same value of matrixControlIndex.
.1.3.6.1.2.1.16.6.3.1.4,RMON-MIB::matrixDSPkts,Counter32,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.3.1.5,RMON-MIB::matrixDSOctets,Counter32,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.3.1.6,RMON-MIB::matrixDSErrors,Counter32,read-only,,current,,The number of bad packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.4,RMON2-MIB::matrixControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.6.4.1,RMON2-MIB::matrixControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.6.4.1.1,RMON2-MIB::matrixControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.6.4.1.2,RMON2-MIB::matrixControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.7,RMON-MIB::filter,,,,,,
.1.3.6.1.2.1.16.7.1,RMON-MIB::filterTable,,not-accessible,,current,,A list of packet filter entries.
.1.3.6.1.2.1.16.7.1.1,RMON-MIB::filterEntry,,not-accessible,filterIndex,current,,A set of parameters for a packet filter applied on a particular interface. As an example, an instance of the filterPktData object might be named filterPktData.12
.1.3.6.1.2.1.16.7.1.1.1,RMON-MIB::filterIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the filter table. Each such entry defines one filter that is to be applied to every packet received on an interface.
.1.3.6.1.2.1.16.7.1.1.2,RMON-MIB::filterChannelIndex,Integer32,read-create,,current,,This object identifies the channel of which this filter is a part. The filters identified by a particular value of this object are associated with the same channel as identified by the same value of the channelIndex object.
.1.3.6.1.2.1.16.7.1.1.3,RMON-MIB::filterPktDataOffset,Integer32,read-create,,current,,The offset from the beginning of each packet where a match of packet data will be attempted. This offset is measured from the point in the physical layer packet after the framing bits, if any. For example, in an Ethernet frame, this point is at the beginning of the destination MAC address. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.4,RMON-MIB::filterPktData,OCTET,read-create,,current,,The data that is to be matched with the input packet. For each packet received, this filter and the accompanying filterPktDataMask and filterPktDataNotMask will be adjusted for the offset. The only bits relevant to this match algorithm are those that have the corresponding filterPktDataMask bit equal to one. The following three rules are then applied to every packet: (1) If the packet is too short and does not have data corresponding to part of the filterPktData, the packet will fail this data match. (2) For each relevant bit from the packet with the corresponding filterPktDataNotMask bit set to zero, if the bit from the packet is not equal to the corresponding bit from the filterPktData, then the packet will fail this data match. (3) If for every relevant bit from the packet with the corresponding filterPktDataNotMask bit set to one, the bit from the packet is equal to the corresponding bit from the filterPktData, then the packet will fail this data match. Any packets that have not failed any of the three matches above have passed this data match. In particular, a zero length filter will match any packet. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.5,RMON-MIB::filterPktDataMask,OCTET,read-create,,current,,The mask that is applied to the match process. After adjusting this mask for the offset, only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the match algorithm. The offset is applied to filterPktDataMask in the same way it is applied to the filter. For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the length of the filterPktData object. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.6,RMON-MIB::filterPktDataNotMask,OCTET,read-create,,current,,The inversion mask that is applied to the match process. After adjusting this mask for the offset, those relevant bits in the received packet that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktData object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet that correspond to bits set in this mask must be different to its corresponding bit in the filterPktData object. For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the length of the filterPktData object. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.7,RMON-MIB::filterPktStatus,Integer32,read-create,,current,,The status that is to be matched with the input packet. The only bits relevant to this match algorithm are those that have the corresponding filterPktStatusMask bit equal to one. The following two rules are then applied to every packet: (1) For each relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to zero, if the bit from the packet status is not equal to the corresponding bit from the filterPktStatus, then the packet will fail this status match. (2) If for every relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to one, the bit from the packet status is equal to the corresponding bit from the filterPktStatus, then the packet will fail this status match. Any packets that have not failed either of the two matches above have passed this status match. In particular, a zero length status filter will match any packet's status. The value of the packet status is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum. The errors and the bits that represent them are dependent on the media type of the interface that this channel is receiving packets from. The errors defined for a packet captured off of an Ethernet interface are as follows: bit # Error 0 Packet is longer than 1518 octets 1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2). As this MIB is expanded to new media types, this object will have other media-specific errors defined. For the purposes of this status matching algorithm, if the packet status is longer than this filterPktStatus object, this object is conceptually extended with '0' bits until it reaches the size of the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.8,RMON-MIB::filterPktStatusMask,Integer32,read-create,,current,,The mask that is applied to the status match process. Only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the status match algorithm. For the purposes of the matching algorithm, if the associated filterPktStatus object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the size of the filterPktStatus. In addition, if a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the size of the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.9,RMON-MIB::filterPktStatusNotMask,Integer32,read-create,,current,,The inversion mask that is applied to the status match process. Those relevant bits in the received packet status that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktStatus object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet status that correspond to bits set in this mask must be different to its corresponding bit in the filterPktStatus object for the packet to be accepted. For the purposes of the matching algorithm, if the associated filterPktStatus object or a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the longer of the lengths of the filterPktStatus object and the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.10,RMON-MIB::filterOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.7.1.1.11,RMON-MIB::filterStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this filter entry.
.1.3.6.1.2.1.16.7.2,RMON-MIB::channelTable,,not-accessible,,current,,A list of packet channel entries.
.1.3.6.1.2.1.16.7.2.1,RMON-MIB::channelEntry,,not-accessible,channelIndex,current,,A set of parameters for a packet channel applied on a particular interface. As an example, an instance of the channelMatches object might be named channelMatches.3
.1.3.6.1.2.1.16.7.2.1.1,RMON-MIB::channelIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the channel table. Each such entry defines one channel, a logical data and event stream. It is suggested that before creating a channel, an application should scan all instances of the filterChannelIndex object to make sure that there are no pre-existing filters that would be inadvertently be linked to the channel.
.1.3.6.1.2.1.16.7.2.1.2,RMON-MIB::channelIfIndex,Integer32,read-create,,current,,The value of this object uniquely identifies the interface on this remote network monitoring device to which the associated filters are applied to allow data into this channel. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in RFC 2233 [17]. The filters in this group are applied to all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.3,RMON-MIB::channelAcceptType,INTEGER,read-create,,current,acceptMatched(1):acceptFailed(2),This object controls the action of the filters associated with this channel. If this object is equal to acceptMatched(1), packets will be accepted to this channel if they are accepted by both the packet data and packet status matches of an associated filter. If this object is equal to acceptFailed(2), packets will be accepted to this channel only if they fail either the packet data match or the packet status match of each of the associated filters. In particular, a channel with no associated filters will match no packets if set to acceptMatched(1) case and will match all packets in the acceptFailed(2) case. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.4,RMON-MIB::channelDataControl,INTEGER,read-create,,current,on(1):off(2),This object controls the flow of data through this channel. If this object is on(1), data, status and events flow through this channel. If this object is off(2), data, status and events will not flow through this channel.
.1.3.6.1.2.1.16.7.2.1.5,RMON-MIB::channelTurnOnEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to turn the associated channelDataControl from off to on when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOnEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.6,RMON-MIB::channelTurnOffEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to turn the associated channelDataControl from on to off when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOffEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.7,RMON-MIB::channelEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to be generated when the associated channelDataControl is on and a packet is matched. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.8,RMON-MIB::channelEventStatus,INTEGER,read-create,,current,eventReady(1):eventFired(2):eventAlwaysReady(3),The event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
.1.3.6.1.2.1.16.7.2.1.9,RMON-MIB::channelMatches,Counter32,read-only,,current,,The number of times this channel has matched a packet. Note that this object is updated even when channelDataControl is set to off.
.1.3.6.1.2.1.16.7.2.1.10,RMON-MIB::channelDescription,OCTET,read-create,,current,,A comment describing this channel.
.1.3.6.1.2.1.16.7.2.1.11,RMON-MIB::channelOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.7.2.1.12,RMON-MIB::channelStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this channel entry.
.1.3.6.1.2.1.16.7.3,RMON2-MIB::channel2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.7.3.1,RMON2-MIB::channel2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.7.3.1.1,RMON2-MIB::channelDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.7.3.1.2,RMON2-MIB::channelCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.7.4,RMON2-MIB::filter2Table,,not-accessible,,current,,Provides a variable-length packet filter feature to the RMON-1 filter table.
.1.3.6.1.2.1.16.7.4.1,RMON2-MIB::filter2Entry,,not-accessible,,current,,Provides a variable-length packet filter feature to the RMON-1 filter table.
.1.3.6.1.2.1.16.7.4.1.1,RMON2-MIB::filterProtocolDirDataLocalIndex,Integer32,read-create,,current,,When this object is set to a non-zero value, the filter that it is associated with performs the following operations on every packet: 1) If the packet doesn't match the protocol directory entry identified by this object, discard the packet and exit (i.e., discard the packet if it is not of the identified protocol). 2) If the associated filterProtocolDirLocalIndex is non-zero and the packet doesn't match the protocol directory entry identified by that object, discard the packet and exit. 3) If the packet matches, perform the regular filter algorithm as if the beginning of this named protocol is the beginning of the packet, potentially applying the filterOffset value to move further into the packet.
.1.3.6.1.2.1.16.7.4.1.2,RMON2-MIB::filterProtocolDirLocalIndex,Integer32,read-create,,current,,When this object is set to a non-zero value, the filter that it is associated with will discard the packet if the packet doesn't match this protocol directory entry.
.1.3.6.1.2.1.16.8,RMON-MIB::capture,,,,,,
.1.3.6.1.2.1.16.8.1,RMON-MIB::bufferControlTable,,not-accessible,,current,,A list of buffers control entries.
.1.3.6.1.2.1.16.8.1.1,RMON-MIB::bufferControlEntry,,not-accessible,bufferControlIndex,current,,A set of parameters that control the collection of a stream of packets that have matched filters. As an example, an instance of the bufferControlCaptureSliceSize object might be named bufferControlCaptureSliceSize.3
.1.3.6.1.2.1.16.8.1.1.1,RMON-MIB::bufferControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the bufferControl table. The value of this index shall never be zero. Each such entry defines one set of packets that is captured and controlled by one or more filters.
.1.3.6.1.2.1.16.8.1.1.2,RMON-MIB::bufferControlChannelIndex,Integer32,read-create,,current,,An index that identifies the channel that is the source of packets for this bufferControl table. The channel identified by a particular value of this index is the same as identified by the same value of the channelIndex object. This object may not be modified if the associated bufferControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.8.1.1.3,RMON-MIB::bufferControlFullStatus,INTEGER,read-only,,current,spaceAvailable(1):full(2),This object shows whether the buffer has room to accept new packets or if it is full. If the status is spaceAvailable(1), the buffer is accepting new packets normally. If the status is full(2) and the associated bufferControlFullAction object is wrapWhenFull, the buffer is accepting new packets by deleting enough of the oldest packets to make room for new ones as they arrive. Otherwise, if the status is full(2) and the bufferControlFullAction object is lockWhenFull, then the buffer has stopped collecting packets. When this object is set to full(2) the probe must not later set it to spaceAvailable(1) except in the case of a significant gain in resources such as an increase of bufferControlOctetsGranted. In particular, the wrap-mode action of deleting old packets to make room for newly arrived packets must not affect the value of this object.
.1.3.6.1.2.1.16.8.1.1.4,RMON-MIB::bufferControlFullAction,INTEGER,read-create,,current,lockWhenFull(1):wrapWhenFull(2),Controls the action of the buffer when it reaches the full status. When in the lockWhenFull(1) state and a packet is added to the buffer that fills the buffer, the bufferControlFullStatus will be set to full(2) and this buffer will stop capturing packets.
.1.3.6.1.2.1.16.8.1.1.5,RMON-MIB::bufferControlCaptureSliceSize,Integer32,read-create,,current,,The maximum number of octets of each packet that will be saved in this capture buffer. For example, if a 1500 octet packet is received by the probe and this object is set to 500, then only 500 octets of the packet will be stored in the associated capture buffer. If this variable is set to 0, the capture buffer will save as many octets as is possible. This object may not be modified if the associated bufferControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.8.1.1.6,RMON-MIB::bufferControlDownloadSliceSize,Integer32,read-create,,current,,The maximum number of octets of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. For example, if 500 octets of a packet have been stored in the associated capture buffer, the associated bufferControlDownloadOffset is 0, and this object is set to 100, then the captureBufferPacket object that contains the packet will contain only the first 100 octets of the packet. A prudent manager will take into account possible interoperability or fragmentation problems that may occur if the download slice size is set too large. In particular, conformant SNMP implementations are not required to accept messages whose length exceeds 484 octets, although they are encouraged to support larger datagrams whenever feasible.
.1.3.6.1.2.1.16.8.1.1.7,RMON-MIB::bufferControlDownloadOffset,Integer32,read-create,,current,,The offset of the first octet of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. For example, if 500 octets of a packet have been stored in the associated capture buffer and this object is set to 100, then the captureBufferPacket object that contains the packet will contain bytes starting 100 octets into the packet.
.1.3.6.1.2.1.16.8.1.1.8,RMON-MIB::bufferControlMaxOctetsRequested,Integer32,read-create,,current,,The requested maximum number of octets to be saved in this captureBuffer, including any implementation-specific overhead. If this variable is set to -1, the capture buffer will save as many octets as is possible. When this object is created or modified, the probe should set bufferControlMaxOctetsGranted as closely to this object as is possible for the particular probe implementation and available resources. However, if the object has the special value of -1, the probe must set bufferControlMaxOctetsGranted to -1.
.1.3.6.1.2.1.16.8.1.1.9,RMON-MIB::bufferControlMaxOctetsGranted,Integer32,read-only,,current,,The maximum number of octets that can be saved in this captureBuffer, including overhead. If this variable is -1, the capture buffer will save as many octets as possible. When the bufferControlMaxOctetsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. However, if the request object has the special value of -1, the probe must set this object to -1. The probe must not lower this value except as a result of a modification to the associated bufferControlMaxOctetsRequested object. When this maximum number of octets is reached and a new packet is to be added to this capture buffer and the corresponding bufferControlFullAction is set to wrapWhenFull(2), enough of the oldest packets associated with this capture buffer shall be deleted by the agent so that the new packet can be added. If the corresponding bufferControlFullAction is set to lockWhenFull(1), the new packet shall be discarded. In either case, the probe must set bufferControlFullStatus to full(2). When the value of this object changes to a value less than the current value, entries are deleted from the captureBufferTable associated with this bufferControlEntry. Enough of the oldest of these captureBufferEntries shall be deleted by the agent so that the number of octets used remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated captureBufferEntries may be allowed to grow.
.1.3.6.1.2.1.16.8.1.1.10,RMON-MIB::bufferControlCapturedPackets,Integer32,read-only,,current,,The number of packets currently in this captureBuffer.
.1.3.6.1.2.1.16.8.1.1.11,RMON-MIB::bufferControlTurnOnTime,TimeTicks,read-only,,current,,The value of sysUpTime when this capture buffer was first turned on.
.1.3.6.1.2.1.16.8.1.1.12,RMON-MIB::bufferControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.8.1.1.13,RMON-MIB::bufferControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this buffer Control Entry.
.1.3.6.1.2.1.16.8.2,RMON-MIB::captureBufferTable,,not-accessible,,current,,A list of packets captured off of a channel.
.1.3.6.1.2.1.16.8.2.1,RMON-MIB::captureBufferEntry,,not-accessible,captureBufferControlIndex:captureBufferIndex,current,,A packet captured off of an attached network. As an example, an instance of the captureBufferPacketData object might be named captureBufferPacketData.3.1783
.1.3.6.1.2.1.16.8.2.1.1,RMON-MIB::captureBufferControlIndex,Integer32,read-only,,current,,The index of the bufferControlEntry with which this packet is associated.
.1.3.6.1.2.1.16.8.2.1.2,RMON-MIB::captureBufferIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the captureBuffer table associated with a particular bufferControlEntry. This index will start at 1 and increase by one for each new packet added with the same captureBufferControlIndex. Should this value reach 2147483647, the next packet added with the same captureBufferControlIndex shall cause this value to wrap around to 1.
.1.3.6.1.2.1.16.8.2.1.3,RMON-MIB::captureBufferPacketID,Integer32,read-only,,current,,An index that describes the order of packets that are received on a particular interface. The packetID of a packet captured on an interface is defined to be greater than the packetID's of all packets captured previously on the same interface. As the captureBufferPacketID object has a maximum positive value of 2^31 - 1, any captureBufferPacketID object shall have the value of the associated packet's packetID mod 2^31.
.1.3.6.1.2.1.16.8.2.1.4,RMON-MIB::captureBufferPacketData,OCTET,read-only,,current,,The data inside the packet, starting at the beginning of the packet plus any offset specified in the associated bufferControlDownloadOffset, including any link level headers. The length of the data in this object is the minimum of the length of the captured packet minus the offset, the length of the associated bufferControlCaptureSliceSize minus the offset, and the associated bufferControlDownloadSliceSize. If this minimum is less than zero, this object shall have a length of zero.
.1.3.6.1.2.1.16.8.2.1.5,RMON-MIB::captureBufferPacketLength,Integer32,read-only,,current,,The actual length (off the wire) of the packet stored in this entry, including FCS octets.
.1.3.6.1.2.1.16.8.2.1.6,RMON-MIB::captureBufferPacketTime,Integer32,read-only,,current,,The number of milliseconds that had passed since this capture buffer was first turned on when this packet was captured.
.1.3.6.1.2.1.16.8.2.1.7,RMON-MIB::captureBufferPacketStatus,Integer32,read-only,,current,,A value which indicates the error status of this packet. The value of this object is defined in the same way as filterPktStatus. The value is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum. The errors defined for a packet captured off of an Ethernet interface are as follows: bit # Error 0 Packet is longer than 1518 octets 1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error 3 First packet in this capture buffer after it was detected that some packets were not processed correctly. 4 Packet's order in buffer is only approximate (May only be set for packets sent from the probe) For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2). As this MIB is expanded to new media types, this object will have other media-specific errors defined.
.1.3.6.1.2.1.16.9,RMON-MIB::event,,,,,,
.1.3.6.1.2.1.16.9.1,RMON-MIB::eventTable,,not-accessible,,current,,A list of events to be generated.
.1.3.6.1.2.1.16.9.1.1,RMON-MIB::eventEntry,,not-accessible,eventIndex,current,,A set of parameters that describe an event to be generated when certain conditions are met. As an example, an instance of the eventLastTimeSent object might be named eventLastTimeSent.6
.1.3.6.1.2.1.16.9.1.1.1,RMON-MIB::eventIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the event table. Each such entry defines one event that is to be generated when the appropriate conditions occur.
.1.3.6.1.2.1.16.9.1.1.2,RMON-MIB::eventDescription,OCTET,read-create,,current,,A comment describing this event entry.
.1.3.6.1.2.1.16.9.1.1.3,RMON-MIB::eventType,INTEGER,read-create,,current,none(1):log(2):snmptrap(3):logandtrap(4),The type of notification that the probe will make about this event. In the case of log, an entry is made in the log table for each event. In the case of snmp-trap, an SNMP trap is sent to one or more management stations.
.1.3.6.1.2.1.16.9.1.1.4,RMON-MIB::eventCommunity,OCTET,read-create,,current,,If an SNMP trap is to be sent, it will be sent to the SNMP community specified by this octet string.
.1.3.6.1.2.1.16.9.1.1.5,RMON-MIB::eventLastTimeSent,TimeTicks,read-only,,current,,The value of sysUpTime at the time this event entry last generated an event. If this entry has not generated any events, this value will be zero.
.1.3.6.1.2.1.16.9.1.1.6,RMON-MIB::eventOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it. If this object contains a string starting with 'monitor' and has associated entries in the log table, all connected management stations should retrieve those log entries, as they may have significance to all management stations connected to this device
.1.3.6.1.2.1.16.9.1.1.7,RMON-MIB::eventStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this event entry. If this object is not equal to valid(1), all associated log entries shall be deleted by the agent.
.1.3.6.1.2.1.16.9.2,RMON-MIB::logTable,,not-accessible,,current,,A list of events that have been logged.
.1.3.6.1.2.1.16.9.2.1,RMON-MIB::logEntry,,not-accessible,logEventIndex:logIndex,current,,A set of data describing an event that has been logged. For example, an instance of the logDescription object might be named logDescription.6.47
.1.3.6.1.2.1.16.9.2.1.1,RMON-MIB::logEventIndex,Integer32,read-only,,current,,The event entry that generated this log entry. The log identified by a particular value of this index is associated with the same eventEntry as identified by the same value of eventIndex.
.1.3.6.1.2.1.16.9.2.1.2,RMON-MIB::logIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the log table amongst those generated by the same eventEntries. These indexes are assigned beginning with 1 and increase by one with each new log entry. The association between values of logIndex and logEntries is fixed for the lifetime of each logEntry. The agent may choose to delete the oldest instances of logEntry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur.
.1.3.6.1.2.1.16.9.2.1.3,RMON-MIB::logTime,TimeTicks,read-only,,current,,The value of sysUpTime when this log entry was created.
.1.3.6.1.2.1.16.9.2.1.4,RMON-MIB::logDescription,OCTET,read-only,,current,,An implementation dependent description of the event that activated this log entry.
.1.3.6.1.2.1.16.10,TOKEN-RING-RMON-MIB::tokenRing,,,,,,
.1.3.6.1.2.1.16.10.1,TOKEN-RING-RMON-MIB::ringStationControlTable,,not-accessible,,mandatory,,A list of ringStation table control entries.
.1.3.6.1.2.1.16.10.1.1,TOKEN-RING-RMON-MIB::ringStationControlEntry,,not-accessible,ringStationControlIfIndex,mandatory,,A list of parameters that set up the discovery of stations on a particular interface and the collection of statistics about these stations.
.1.3.6.1.2.1.16.10.1.1.1,TOKEN-RING-RMON-MIB::ringStationControlIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device from which ringStation data is collected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB- II [3].
.1.3.6.1.2.1.16.10.1.1.2,TOKEN-RING-RMON-MIB::ringStationControlTableSize,INTEGER,read-only,,mandatory,,The number of ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.3,TOKEN-RING-RMON-MIB::ringStationControlActiveStations,INTEGER,read-only,,mandatory,,The number of active ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.4,TOKEN-RING-RMON-MIB::ringStationControlRingState,INTEGER,read-only,,mandatory,normalOperation(1):ringPurgeState(2):claimTokenState(3):beaconFrameStreamingState(4):beaconBitStreamingState(5):beaconRingSignalLossState(6):beaconSetRecoveryModeState(7),The current status of this ring.
.1.3.6.1.2.1.16.10.1.1.5,TOKEN-RING-RMON-MIB::ringStationControlBeaconSender,OCTET,read-only,,mandatory,,The address of the sender of the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.6,TOKEN-RING-RMON-MIB::ringStationControlBeaconNAUN,OCTET,read-only,,mandatory,,The address of the NAUN in the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.7,TOKEN-RING-RMON-MIB::ringStationControlActiveMonitor,OCTET,read-only,,mandatory,,The address of the Active Monitor on this segment. If this address is unknown, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.8,TOKEN-RING-RMON-MIB::ringStationControlOrderChanges,Counter32,read-only,,mandatory,,The number of add and delete events in the ringStationOrderTable optionally associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.9,TOKEN-RING-RMON-MIB::ringStationControlOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.10.1.1.10,TOKEN-RING-RMON-MIB::ringStationControlStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this ringStationControl entry. If this object is not equal to valid(1), all associated entries in the ringStationTable shall be deleted by the agent.
.1.3.6.1.2.1.16.10.2,TOKEN-RING-RMON-MIB::ringStationTable,,not-accessible,,mandatory,,A list of ring station entries. An entry will exist for each station that is now or has previously been detected as physically present on this ring.
.1.3.6.1.2.1.16.10.2.1,TOKEN-RING-RMON-MIB::ringStationEntry,,not-accessible,ringStationIfIndex:ringStationMacAddress,mandatory,,A collection of statistics for a particular station that has been discovered on a ring monitored by this device.
.1.3.6.1.2.1.16.10.2.1.1,TOKEN-RING-RMON-MIB::ringStationIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.2.1.2,TOKEN-RING-RMON-MIB::ringStationMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.2.1.3,TOKEN-RING-RMON-MIB::ringStationLastNAUN,OCTET,read-only,,mandatory,,The physical address of last known NAUN of this station.
.1.3.6.1.2.1.16.10.2.1.4,TOKEN-RING-RMON-MIB::ringStationStationStatus,INTEGER,read-only,,mandatory,active(1):inactive(2):forcedRemoval(3),The status of this station on the ring.
.1.3.6.1.2.1.16.10.2.1.5,TOKEN-RING-RMON-MIB::ringStationLastEnterTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time this station last entered the ring. If the time is unknown, this value shall be zero.
.1.3.6.1.2.1.16.10.2.1.6,TOKEN-RING-RMON-MIB::ringStationLastExitTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time the probe detected that this station last exited the ring. If the time is unknown, this value shall be zero.
.1.3.6.1.2.1.16.10.2.1.7,TOKEN-RING-RMON-MIB::ringStationDuplicateAddresses,Counter32,read-only,,mandatory,,The number of times this station experienced a duplicate address error.
.1.3.6.1.2.1.16.10.2.1.8,TOKEN-RING-RMON-MIB::ringStationInLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.9,TOKEN-RING-RMON-MIB::ringStationOutLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.10,TOKEN-RING-RMON-MIB::ringStationInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.11,TOKEN-RING-RMON-MIB::ringStationInBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.12,TOKEN-RING-RMON-MIB::ringStationOutBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.13,TOKEN-RING-RMON-MIB::ringStationACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.14,TOKEN-RING-RMON-MIB::ringStationAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.15,TOKEN-RING-RMON-MIB::ringStationLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.16,TOKEN-RING-RMON-MIB::ringStationCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.17,TOKEN-RING-RMON-MIB::ringStationFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.18,TOKEN-RING-RMON-MIB::ringStationFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.19,TOKEN-RING-RMON-MIB::ringStationTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported by this station in error reporting frames detected by the probe.
.1.3.6.1.2.1.16.10.2.1.20,TOKEN-RING-RMON-MIB::ringStationInBeaconErrors,Counter32,read-only,,mandatory,,The total number of beacon frames sent by this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.21,TOKEN-RING-RMON-MIB::ringStationOutBeaconErrors,Counter32,read-only,,mandatory,,The total number of beacon frames detected by the probe that name this station as the NAUN.
.1.3.6.1.2.1.16.10.2.1.22,TOKEN-RING-RMON-MIB::ringStationInsertions,Counter32,read-only,,mandatory,,The number of times the probe detected this station inserting onto the ring.
.1.3.6.1.2.1.16.10.3,TOKEN-RING-RMON-MIB::ringStationOrderTable,,not-accessible,,mandatory,,A list of ring station entries for stations in the ring poll, ordered by their ring-order.
.1.3.6.1.2.1.16.10.3.1,TOKEN-RING-RMON-MIB::ringStationOrderEntry,,not-accessible,ringStationOrderIfIndex:ringStationOrderOrderIndex,mandatory,,A collection of statistics for a particular station that is active on a ring monitored by this device. This table will contain information for every interface that has a ringStationControlStatus equal to valid.
.1.3.6.1.2.1.16.10.3.1.1,TOKEN-RING-RMON-MIB::ringStationOrderIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.3.1.2,TOKEN-RING-RMON-MIB::ringStationOrderOrderIndex,INTEGER,read-only,,mandatory,,This index denotes the location of this station with respect to other stations on the ring. This index is one more than the number of hops downstream that this station is from the rmon probe. The rmon probe itself gets the value one.
.1.3.6.1.2.1.16.10.3.1.3,TOKEN-RING-RMON-MIB::ringStationOrderMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.4,TOKEN-RING-RMON-MIB::ringStationConfigControlTable,,not-accessible,,mandatory,,A list of ring station configuration control entries.
.1.3.6.1.2.1.16.10.4.1,TOKEN-RING-RMON-MIB::ringStationConfigControlEntry,,not-accessible,ringStationConfigControlIfIndex:ringStationConfigControlMacAddress,mandatory,,This entry controls active management of stations by the probe. One entry exists in this table for each active station in the ringStationTable.
.1.3.6.1.2.1.16.10.4.1.1,TOKEN-RING-RMON-MIB::ringStationConfigControlIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.4.1.2,TOKEN-RING-RMON-MIB::ringStationConfigControlMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.4.1.3,TOKEN-RING-RMON-MIB::ringStationConfigControlRemove,INTEGER,read-write,,mandatory,stable(1):removing(2),Setting this object to `removing(2)' causes a Remove Station MAC frame to be sent. The agent will set this object to `stable(1)' after processing the request.
.1.3.6.1.2.1.16.10.4.1.4,TOKEN-RING-RMON-MIB::ringStationConfigControlUpdateStats,INTEGER,read-write,,mandatory,stable(1):updating(2),Setting this object to `updating(2)' causes the configuration information associate with this entry to be updated. The agent will set this object to `stable(1)' after processing the request.
.1.3.6.1.2.1.16.10.5,TOKEN-RING-RMON-MIB::ringStationConfigTable,,not-accessible,,mandatory,,A list of configuration entries for stations on a ring monitored by this probe.
.1.3.6.1.2.1.16.10.5.1,TOKEN-RING-RMON-MIB::ringStationConfigEntry,,not-accessible,ringStationConfigIfIndex:ringStationConfigMacAddress,mandatory,,A collection of statistics for a particular station that has been discovered on a ring monitored by this probe.
.1.3.6.1.2.1.16.10.5.1.1,TOKEN-RING-RMON-MIB::ringStationConfigIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.5.1.2,TOKEN-RING-RMON-MIB::ringStationConfigMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.5.1.3,TOKEN-RING-RMON-MIB::ringStationConfigUpdateTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time this configuration information was last updated (completely).
.1.3.6.1.2.1.16.10.5.1.4,TOKEN-RING-RMON-MIB::ringStationConfigLocation,OCTET,read-only,,mandatory,,The assigned physical location of this station.
.1.3.6.1.2.1.16.10.5.1.5,TOKEN-RING-RMON-MIB::ringStationConfigMicrocode,OCTET,read-only,,mandatory,,The microcode EC level of this station.
.1.3.6.1.2.1.16.10.5.1.6,TOKEN-RING-RMON-MIB::ringStationConfigGroupAddress,OCTET,read-only,,mandatory,,The low-order 4 octets of the group address recognized by this station.
.1.3.6.1.2.1.16.10.5.1.7,TOKEN-RING-RMON-MIB::ringStationConfigFunctionalAddress,OCTET,read-only,,mandatory,,the functional addresses recognized by this station.
.1.3.6.1.2.1.16.10.6,TOKEN-RING-RMON-MIB::sourceRoutingStatsTable,,not-accessible,,mandatory,,A list of source routing statistics entries.
.1.3.6.1.2.1.16.10.6.1,TOKEN-RING-RMON-MIB::sourceRoutingStatsEntry,,not-accessible,sourceRoutingStatsIfIndex,mandatory,,A collection of source routing statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.10.6.1.1,TOKEN-RING-RMON-MIB::sourceRoutingStatsIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which source routing statistics will be detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.6.1.2,TOKEN-RING-RMON-MIB::sourceRoutingStatsRingNumber,INTEGER,read-only,,mandatory,,The ring number of the ring monitored by this entry. When any object in this entry is created, the probe will attempt to discover the ring number. Only after the ring number is discovered will this object be created. After creating an object in this entry, the management station should poll this object to detect when it is created. Only after this object is created can the management station set the sourceRoutingStatsStatus entry to valid(1).
.1.3.6.1.2.1.16.10.6.1.3,TOKEN-RING-RMON-MIB::sourceRoutingStatsInFrames,Counter32,read-only,,mandatory,,The count of frames sent into this ring from another ring.
.1.3.6.1.2.1.16.10.6.1.4,TOKEN-RING-RMON-MIB::sourceRoutingStatsOutFrames,Counter32,read-only,,mandatory,,The count of frames sent from this ring to another ring.
.1.3.6.1.2.1.16.10.6.1.5,TOKEN-RING-RMON-MIB::sourceRoutingStatsThroughFrames,Counter32,read-only,,mandatory,,The count of frames sent from another ring, through this ring, to another ring.
.1.3.6.1.2.1.16.10.6.1.6,TOKEN-RING-RMON-MIB::sourceRoutingStatsAllRoutesBroadcastFrames,Counter32,read-only,,mandatory,,The total number of good frames received that were All Routes Broadcast.
.1.3.6.1.2.1.16.10.6.1.7,TOKEN-RING-RMON-MIB::sourceRoutingStatsSingleRouteBroadcastFrames,Counter32,read-only,,mandatory,,The total number of good frames received that were Single Route Broadcast.
.1.3.6.1.2.1.16.10.6.1.8,TOKEN-RING-RMON-MIB::sourceRoutingStatsInOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent into this ring from another ring.
.1.3.6.1.2.1.16.10.6.1.9,TOKEN-RING-RMON-MIB::sourceRoutingStatsOutOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent from this ring to another ring.
.1.3.6.1.2.1.16.10.6.1.10,TOKEN-RING-RMON-MIB::sourceRoutingStatsThroughOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent another ring, through this ring, to another ring.
.1.3.6.1.2.1.16.10.6.1.11,TOKEN-RING-RMON-MIB::sourceRoutingStatsAllRoutesBroadcastOctets,Counter32,read-only,,mandatory,,The total number of octets in good frames received that were All Routes Broadcast.
.1.3.6.1.2.1.16.10.6.1.12,TOKEN-RING-RMON-MIB::sourceRoutingStatsSingleRoutesBroadcastOctets,Counter32,read-only,,mandatory,,The total number of octets in good frames received that were Single Route Broadcast.
.1.3.6.1.2.1.16.10.6.1.13,TOKEN-RING-RMON-MIB::sourceRoutingStatsLocalLLCFrames,Counter32,read-only,,mandatory,,The total number of frames received who had no RIF field (or had a RIF field that only included the local ring's number) and were not All Route Broadcast Frames.
.1.3.6.1.2.1.16.10.6.1.14,TOKEN-RING-RMON-MIB::sourceRoutingStats1HopFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 1 hop, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.15,TOKEN-RING-RMON-MIB::sourceRoutingStats2HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 2 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.16,TOKEN-RING-RMON-MIB::sourceRoutingStats3HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 3 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.17,TOKEN-RING-RMON-MIB::sourceRoutingStats4HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 4 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.18,TOKEN-RING-RMON-MIB::sourceRoutingStats5HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 5 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.19,TOKEN-RING-RMON-MIB::sourceRoutingStats6HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 6 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.20,TOKEN-RING-RMON-MIB::sourceRoutingStats7HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 7 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.21,TOKEN-RING-RMON-MIB::sourceRoutingStats8HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 8 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.22,TOKEN-RING-RMON-MIB::sourceRoutingStatsMoreThan8HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had more than 8 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.23,TOKEN-RING-RMON-MIB::sourceRoutingStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.10.6.1.24,TOKEN-RING-RMON-MIB::sourceRoutingStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this sourceRoutingStats entry.
.1.3.6.1.2.1.16.10.7,RMON2-MIB::ringStationControl2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.10.7.1,RMON2-MIB::ringStationControl2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.10.7.1.1,RMON2-MIB::ringStationControlDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.10.7.1.2,RMON2-MIB::ringStationControlCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.10.8,RMON2-MIB::sourceRoutingStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.10.8.1,RMON2-MIB::sourceRoutingStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.10.8.1.1,RMON2-MIB::sourceRoutingStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.10.8.1.2,RMON2-MIB::sourceRoutingStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.11,RMON2-MIB::protocolDir,,,,,,
.1.3.6.1.2.1.16.11.1,RMON2-MIB::protocolDirLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the protocol directory was last modified, either through insertions or deletions, or through modifications of the protocolDirAddressMapConfig, protocolDirHostConfig, or protocolDirMatrixConfig.
.1.3.6.1.2.1.16.11.2,RMON2-MIB::protocolDirTable,,not-accessible,,current,,This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network-layer, transport-layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application-layer groups.
.1.3.6.1.2.1.16.11.2.1,RMON2-MIB::protocolDirEntry,,not-accessible,protocolDirID:protocolDirParameters,current,,A conceptual row in the protocolDirTable. An example of the indexing of this entry is protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0.0, which is the encoding of a length of 8, followed by 8 subids encoding the protocolDirID of 1.2048, followed by a length of 2 and the 2 subids encoding zero-valued parameters. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.11.2.1.1,RMON2-MIB::protocolDirID,OCTET,not-accessible,,current,,A unique identifier for a particular protocol. Standard identifiers will be defined in such a manner that they can often be used as specifications for new protocols - i.e., a tree-structured assignment mechanism that matches the protocol encapsulation 'tree' and that has algorithmic assignment mechanisms for certain subtrees. See RFC 2074 for more details. Despite the algorithmic mechanism, the probe will only place entries in here for those protocols it chooses to collect. In other words, it need not populate this table with all possible ethernet protocol types, nor need it create them on the fly when it sees them. Whether it does these things is a matter of product definition (cost/benefit, usability) and is up to the designer of the product. If an entry is written to this table with a protocolDirID that the agent doesn't understand, either directly or algorithmically, the SET request will be rejected with an inconsistentName or badValue (for SNMPv1) error.
.1.3.6.1.2.1.16.11.2.1.2,RMON2-MIB::protocolDirParameters,OCTET,not-accessible,,current,,A set of parameters for the associated protocolDirID. See the associated RMON2 Protocol Identifiers document for a description of the possible parameters. There will be one octet in this string for each sub-identifier in the protocolDirID, and the parameters will appear here in the same order as the associated sub-identifiers appear in the protocolDirID. Every node in the protocolDirID tree has a different, optional set of parameters defined (that is, the definition of parameters for a node is optional). The proper parameter value for each node is included in this string. Note that the inclusion of a parameter value in this string for each node is not optional. What is optional is that a node may have no parameters defined, in which case the parameter field for that node will be zero.
.1.3.6.1.2.1.16.11.2.1.3,RMON2-MIB::protocolDirLocalIndex,Integer32,read-only,,current,,The locally arbitrary but unique identifier associated with this protocolDir entry. The value for each supported protocol must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization, except that if a protocol is deleted and re-created, it must be re-created with a new value that has not been used since the last re-initialization. The specific value is meaningful only within a given SNMP entity. A protocolDirLocalIndex must not be re-used until the next agent restart in the event that the protocol directory entry is deleted.
.1.3.6.1.2.1.16.11.2.1.4,RMON2-MIB::protocolDirDescr,OCTET,read-create,,current,,A textual description of the protocol encapsulation. A probe may choose to describe only a subset of the entire encapsulation (e.g., only the highest layer). This object is intended for human consumption only. This object may not be modified if the associated protocolDirStatus object is equal to active(1).
.1.3.6.1.2.1.16.11.2.1.5,RMON2-MIB::protocolDirType,BITS,read-only,,current,extensible(0):addressRecognitionCapable(1),This object describes 2 attributes of this protocol directory entry. The presence or absence of the 'extensible' bit describes whether this protocol directory entry can be extended by the user by creating protocol directory entries that are children of this protocol. An example of an entry that will often allow extensibility is 'ip.udp'. The probe may automatically populate some children of this node, such as 'ip.udp.snmp' and 'ip.udp.dns'. A probe administrator or user may also populate additional children via remote SNMP requests that create entries in this table. When a child node is added for a protocol for which the probe has no built-in support extending a parent node (for which the probe does have built-in support), that child node is not extendable. This is termed 'limited extensibility'. When a child node is added through this extensibility mechanism, the values of protocolDirLocalIndex and protocolDirType shall be assigned by the agent. The other objects in the entry will be assigned by the manager who is creating the new entry. This object also describes whether this agent can recognize addresses for this protocol, should it be a network-level protocol. That is, while a probe may be able to recognize packets of a particular network-layer protocol and count them, it takes additional logic to be able to recognize the addresses in this protocol and to populate network-layer or application-layer tables with the addresses in this protocol. If this bit is set, the agent will recognize network-layer addresses for this protocol and populate the network- and application-layer host and matrix tables with these protocols. Note that when an entry is created, the agent will supply values for the bits that match the capabilities of the agent with respect to this protocol. Note that since row creations usually exercise the limited extensibility feature, these bits will usually be set to zero.
.1.3.6.1.2.1.16.11.2.1.6,RMON2-MIB::protocolDirAddressMapConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for address mapping for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to perform address mapping for the protocol or if this protocol is not a network-layer protocol. When an entry is created in this table by a management operation as part of the limited extensibility feature, the probe must set this value to notSupported(1), because limited extensibility of the protocolDirTable does not extend to interpreting addresses of the extended protocols. If the value of this object is notSupported(1), the probe will not perform address mapping for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports address mapping for this protocol and is configured to perform address mapping for this protocol for all addressMappingControlEntries and all interfaces. If the value of this object is supportedOff(2), the probe supports address mapping for this protocol but is configured to not perform address mapping for this protocol for any addressMappingControlEntries and all interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the addressMappingTable.
.1.3.6.1.2.1.16.11.2.1.7,RMON2-MIB::protocolDirHostConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for the network-layer and application-layer host tables for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to track the nlHostTable for this protocol or if the alHostTable is implemented but doesn't have the capability to track this protocol. Note that if the alHostTable is implemented, the probe may only support a protocol if it is supported in both the nlHostTable and the alHostTable. If the associated protocolDirType object has the addressRecognitionCapable bit set, then this is a network- layer protocol for which the probe recognizes addresses, and thus the probe will populate the nlHostTable and alHostTable with addresses it discovers for this protocol. If the value of this object is notSupported(1), the probe will not track the nlHostTable or alHostTable for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports tracking of the nlHostTable and alHostTable for this protocol and is configured to track both tables for this protocol for all control entries and all interfaces. If the value of this object is supportedOff(2), the probe supports tracking of the nlHostTable and alHostTable for this protocol but is configured to not track these tables for any control entries or interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the nlHostTable and alHostTable. Note that since each alHostEntry references 2 protocol directory entries, one for the network address and one for the type of the highest protocol recognized, an entry will only be created in that table if this value is supportedOn(3) for both protocols.
.1.3.6.1.2.1.16.11.2.1.8,RMON2-MIB::protocolDirMatrixConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for the network-layer and application-layer matrix tables for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to track the nlMatrixTables for this protocol or if the alMatrixTables are implemented but don't have the capability to track this protocol. Note that if the alMatrix tables are implemented, the probe may only support a protocol if it is supported in both of the nlMatrixTables and both of the alMatrixTables. If the associated protocolDirType object has the addressRecognitionCapable bit set, then this is a network- layer protocol for which the probe recognizes addresses, and thus the probe will populate both of the nlMatrixTables and both of the alMatrixTables with addresses it discovers for this protocol. If the value of this object is notSupported(1), the probe will not track either of the nlMatrixTables or the alMatrixTables for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports tracking of both of the nlMatrixTables and (if implemented) both of the alMatrixTables for this protocol and is configured to track these tables for this protocol for all control entries and all interfaces. If the value of this object is supportedOff(2), the probe supports tracking of both of the nlMatrixTables and (if implemented) both of the alMatrixTables for this protocol but is configured to not track these tables for this protocol for any control entries or interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the nlMatrixTables and the alMatrixTables. Note that since each alMatrixEntry references 2 protocol directory entries, one for the network address and one for the type of the highest protocol recognized, an entry will only be created in that table if this value is supportedOn(3) for both protocols.
.1.3.6.1.2.1.16.11.2.1.9,RMON2-MIB::protocolDirOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.11.2.1.10,RMON2-MIB::protocolDirStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this protocol directory entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlHostTable, nlMatrixSDTable, nlMatrixDSTable, alHostTable, alMatrixSDTable, and alMatrixDSTable shall be deleted.
.1.3.6.1.2.1.16.12,RMON2-MIB::protocolDist,,,,,,
.1.3.6.1.2.1.16.12.1,RMON2-MIB::protocolDistControlTable,,not-accessible,,current,,Controls the setup of protocol type distribution statistics tables. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of protocol statistics is available. Rationale: This table controls collection of very basic statistics for any or all of the protocols detected on a given interface. An NMS can use this table to quickly determine bandwidth allocation utilized by different protocols. A media-specific statistics collection could also be configured (e.g., etherStats, trPStats) to easily obtain total frame, octet, and droppedEvents for the same interface.
.1.3.6.1.2.1.16.12.1.1,RMON2-MIB::protocolDistControlEntry,,not-accessible,protocolDistControlIndex,current,,A conceptual row in the protocolDistControlTable. An example of the indexing of this entry is protocolDistControlDroppedFrames.7
.1.3.6.1.2.1.16.12.1.1.1,RMON2-MIB::protocolDistControlIndex,Integer32,not-accessible,,current,,A unique index for this protocolDistControlEntry.
.1.3.6.1.2.1.16.12.1.1.2,RMON2-MIB::protocolDistControlDataSource,OBJECT,read-create,,current,,The source of data for the this protocol distribution. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated protocolDistControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.12.1.1.3,RMON2-MIB::protocolDistControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.12.1.1.4,RMON2-MIB::protocolDistControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.12.1.1.5,RMON2-MIB::protocolDistControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.12.1.1.6,RMON2-MIB::protocolDistControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the protocolDistStatsTable shall be deleted.
.1.3.6.1.2.1.16.12.2,RMON2-MIB::protocolDistStatsTable,,not-accessible,,current,,An entry is made in this table for every protocol in the protocolDirTable that has been seen in at least one packet. Counters are updated in this table for every protocol type that is encountered when parsing a packet, but no counters are updated for packets with MAC-layer errors. Note that if a protocolDirEntry is deleted, all associated entries in this table are removed.
.1.3.6.1.2.1.16.12.2.1,RMON2-MIB::protocolDistStatsEntry,,not-accessible,protocolDistControlIndex:protocolDirLocalIndex,current,,A conceptual row in the protocolDistStatsTable. The index is composed of the protocolDistControlIndex of the associated protocolDistControlEntry, followed by the protocolDirLocalIndex of the associated protocol that this entry represents. In other words, the index identifies the protocol distribution an entry is a part of and the particular protocol that it represents. An example of the indexing of this entry is protocolDistStatsPkts.1.18
.1.3.6.1.2.1.16.12.2.1.1,RMON2-MIB::protocolDistStatsPkts,Gauge32,read-only,,current,,The number of packets of this protocol type received without errors. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.12.2.1.2,RMON2-MIB::protocolDistStatsOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type received since it was added to the protocolDistStatsTable (excluding framing bits, but including FCS octets), except for those octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.13,RMON2-MIB::addressMap,,,,,,
.1.3.6.1.2.1.16.13.1,RMON2-MIB::addressMapInserts,Counter32,read-only,,current,,The number of times an address mapping entry has been inserted into the addressMapTable. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. Note that the table size can be determined by subtracting addressMapDeletes from addressMapInserts.
.1.3.6.1.2.1.16.13.2,RMON2-MIB::addressMapDeletes,Counter32,read-only,,current,,The number of times an address mapping entry has been deleted from the addressMapTable (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. Note that the table size can be determined by subtracting addressMapDeletes from addressMapInserts.
.1.3.6.1.2.1.16.13.3,RMON2-MIB::addressMapMaxDesiredEntries,Integer32,read-write,,current,,The maximum number of entries that are desired in the addressMapTable. The probe will not create more than this number of entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.13.4,RMON2-MIB::addressMapControlTable,,not-accessible,,current,,A table to control the collection of mappings from network layer address to physical address to interface. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the discovery of addresses on a new interface and the placement of address mappings into the central addressMapTable. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of address mappings is available.
.1.3.6.1.2.1.16.13.4.1,RMON2-MIB::addressMapControlEntry,,not-accessible,addressMapControlIndex,current,,A conceptual row in the addressMapControlTable. An example of the indexing of this entry is addressMapControlDroppedFrames.1
.1.3.6.1.2.1.16.13.4.1.1,RMON2-MIB::addressMapControlIndex,Integer32,not-accessible,,current,,A unique index for this entry in the addressMapControlTable.
.1.3.6.1.2.1.16.13.4.1.2,RMON2-MIB::addressMapControlDataSource,OBJECT,read-create,,current,,The source of data for this addressMapControlEntry.
.1.3.6.1.2.1.16.13.4.1.3,RMON2-MIB::addressMapControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.13.4.1.4,RMON2-MIB::addressMapControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.13.4.1.5,RMON2-MIB::addressMapControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this addressMap control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the addressMapTable shall be deleted.
.1.3.6.1.2.1.16.13.5,RMON2-MIB::addressMapTable,,not-accessible,,current,,A table of mappings from network layer address to physical address to interface. The probe will add entries to this table based on the source MAC and network addresses seen in packets without MAC-level errors. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirAddressMapConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirAddressMapConfig value of supportedOff(2).
.1.3.6.1.2.1.16.13.5.1,RMON2-MIB::addressMapEntry,,not-accessible,addressMapTimeMark:protocolDirLocalIndex:addressMapNetworkAddress:addressMapSource,current,,A conceptual row in the addressMapTable. The protocolDirLocalIndex in the index identifies the network layer protocol of the addressMapNetworkAddress. An example of the indexing of this entry is addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.13.5.1.1,RMON2-MIB::addressMapTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.13.5.1.2,RMON2-MIB::addressMapNetworkAddress,OCTET,not-accessible,,current,,The network address for this relation. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.13.5.1.3,RMON2-MIB::addressMapSource,OBJECT,not-accessible,,current,,The interface or port on which the associated network address was most recently seen. If this address mapping was discovered on an interface, this object shall identify the instance of the ifIndex object, defined in [RFC2863], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. If this address mapping was discovered on a port, this object shall identify the instance of the rptrGroupPortIndex object, defined in [RFC2108], for the desired port. For example, if an entry were to receive data from group #1, port #1, this object would be set to rptrGroupPortIndex.1.1. Note that while the dataSource associated with this entry may only point to index objects, this object may at times point to repeater port objects. This situation occurs when the dataSource points to an interface that is a locally attached repeater and the agent has additional information about the source port of traffic seen on that repeater.
.1.3.6.1.2.1.16.13.5.1.4,RMON2-MIB::addressMapPhysicalAddress,OCTET,read-only,,current,,The last source physical address on which the associated network address was seen. If the protocol of the associated network address was encapsulated inside of a network-level or higher protocol, this will be the address of the next-lower protocol with the addressRecognitionCapable bit enabled and will be formatted as specified for that protocol.
.1.3.6.1.2.1.16.13.5.1.5,RMON2-MIB::addressMapLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this entry was last created or the values of the physical address changed. This can be used to help detect duplicate address problems, in which case this object will be updated frequently.
.1.3.6.1.2.1.16.14,RMON2-MIB::nlHost,,,,,,
.1.3.6.1.2.1.16.14.1,RMON2-MIB::hlHostControlTable,,not-accessible,,current,,A list of higher-layer (i.e., non-MAC) host table control entries. These entries will enable the collection of the network- and application-level host tables indexed by network addresses. Both the network- and application-level host tables are controlled by this table so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore. (Note that if an implementation stores application-layer host records in memory, it can derive network-layer host records from them.) Entries in the nlHostTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alHostTable, entries in the alHostTable will be created on behalf of each entry in this table. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of host statistics is available.
.1.3.6.1.2.1.16.14.1.1,RMON2-MIB::hlHostControlEntry,,not-accessible,hlHostControlIndex,current,,A conceptual row in the hlHostControlTable. An example of the indexing of this entry is hlHostControlNlDroppedFrames.1
.1.3.6.1.2.1.16.14.1.1.1,RMON2-MIB::hlHostControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the hlHostControlTable. Each such entry defines a function that discovers hosts on a particular interface and places statistics about them in the nlHostTable, and optionally in the alHostTable, on behalf of this hlHostControlEntry.
.1.3.6.1.2.1.16.14.1.1.2,RMON2-MIB::hlHostControlDataSource,OBJECT,read-create,,current,,The source of data for the associated host tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated hlHostControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.14.1.1.3,RMON2-MIB::hlHostControlNlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for the associated nlHost entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the nlHostTable is inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.14.1.1.4,RMON2-MIB::hlHostControlNlInserts,Counter32,read-only,,current,,The number of times an nlHost entry has been inserted into the nlHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlNlDeletes from hlHostControlNlInserts.
.1.3.6.1.2.1.16.14.1.1.5,RMON2-MIB::hlHostControlNlDeletes,Counter32,read-only,,current,,The number of times an nlHost entry has been deleted from the nlHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlNlDeletes from hlHostControlNlInserts.
.1.3.6.1.2.1.16.14.1.1.6,RMON2-MIB::hlHostControlNlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the nlHostTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlHostControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.14.1.1.7,RMON2-MIB::hlHostControlAlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for the associated alHost entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the alHostTable is not implemented or is inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.14.1.1.8,RMON2-MIB::hlHostControlAlInserts,Counter32,read-only,,current,,The number of times an alHost entry has been inserted into the alHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlAlDeletes from hlHostControlAlInserts.
.1.3.6.1.2.1.16.14.1.1.9,RMON2-MIB::hlHostControlAlDeletes,Counter32,read-only,,current,,The number of times an alHost entry has been deleted from the alHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlAlDeletes from hlHostControlAlInserts.
.1.3.6.1.2.1.16.14.1.1.10,RMON2-MIB::hlHostControlAlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the alHost table on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlHostControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.14.1.1.11,RMON2-MIB::hlHostControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.14.1.1.12,RMON2-MIB::hlHostControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this hlHostControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlHostTable and alHostTable shall be deleted.
.1.3.6.1.2.1.16.14.2,RMON2-MIB::nlHostTable,,not-accessible,,current,,A collection of statistics for a particular network layer address that has been discovered on an interface of this device. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors.
.1.3.6.1.2.1.16.14.2.1,RMON2-MIB::nlHostEntry,,not-accessible,hlHostControlIndex:nlHostTimeMark:protocolDirLocalIndex:nlHostAddress,current,,A conceptual row in the nlHostTable. The hlHostControlIndex value in the index identifies the hlHostControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network layer protocol of the nlHostAddress. An example of the indexing of this entry is nlHostOutPkts.1.783495.18.4.128.2.6.6. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.14.2.1.1,RMON2-MIB::nlHostTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.14.2.1.2,RMON2-MIB::nlHostAddress,OCTET,not-accessible,,current,,The network address for this nlHostEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.14.2.1.3,RMON2-MIB::nlHostInPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted to this address since it was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.4,RMON2-MIB::nlHostOutPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted by this address since it was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.5,RMON2-MIB::nlHostInOctets,Gauge32,read-only,,current,,The number of octets transmitted to this address since it was added to the nlHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.14.2.1.6,RMON2-MIB::nlHostOutOctets,Gauge32,read-only,,current,,The number of octets transmitted by this address since it was added to the nlHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.14.2.1.7,RMON2-MIB::nlHostOutMacNonUnicastPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted by this address that were directed to any MAC broadcast addresses or to any MAC multicast addresses since this host was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.8,RMON2-MIB::nlHostCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.15,RMON2-MIB::nlMatrix,,,,,,
.1.3.6.1.2.1.16.15.1,RMON2-MIB::hlMatrixControlTable,,not-accessible,,current,,A list of higher-layer (i.e., non-MAC) matrix control entries. These entries will enable the collection of the network- and application-level matrix tables containing conversation statistics indexed by pairs of network addresses. Both the network- and application-level matrix tables are controlled by this table so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore. (Note that if an implementation stores application-layer matrix records in memory, it can derive network-layer matrix records from them.) Entries in the nlMatrixSDTable and nlMatrixDSTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alMatrix tables, entries in the alMatrix tables will be created on behalf of each entry in this table.
.1.3.6.1.2.1.16.15.1.1,RMON2-MIB::hlMatrixControlEntry,,not-accessible,hlMatrixControlIndex,current,,A conceptual row in the hlMatrixControlTable. An example of indexing of this entry is hlMatrixControlNlDroppedFrames.1
.1.3.6.1.2.1.16.15.1.1.1,RMON2-MIB::hlMatrixControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the hlMatrixControlTable. Each such entry defines a function that discovers conversations on a particular interface and places statistics about them in the nlMatrixSDTable and the nlMatrixDSTable, and optionally the alMatrixSDTable and alMatrixDSTable, on behalf of this hlMatrixControlEntry.
.1.3.6.1.2.1.16.15.1.1.2,RMON2-MIB::hlMatrixControlDataSource,OBJECT,read-create,,current,,The source of the data for the associated matrix tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated hlMatrixControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.15.1.1.3,RMON2-MIB::hlMatrixControlNlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the nlMatrixTables are inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.15.1.1.4,RMON2-MIB::hlMatrixControlNlInserts,Counter32,read-only,,current,,The number of times an nlMatrix entry has been inserted into the nlMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the nlMatrixSDTable and nlMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the sum of then nlMatrixSDTable and nlMatrixDSTable sizes can be determined by subtracting hlMatrixControlNlDeletes from hlMatrixControlNlInserts.
.1.3.6.1.2.1.16.15.1.1.5,RMON2-MIB::hlMatrixControlNlDeletes,Counter32,read-only,,current,,The number of times an nlMatrix entry has been deleted from the nlMatrix tables (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the nlMatrixSDTable and nlMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlNlDeletes from hlMatrixControlNlInserts.
.1.3.6.1.2.1.16.15.1.1.6,RMON2-MIB::hlMatrixControlNlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the nlMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlMatrixControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.15.1.1.7,RMON2-MIB::hlMatrixControlAlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the alMatrixTables are not implemented or are inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.15.1.1.8,RMON2-MIB::hlMatrixControlAlInserts,Counter32,read-only,,current,,The number of times an alMatrix entry has been inserted into the alMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the alMatrixSDTable and alMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlAlDeletes from hlMatrixControlAlInserts.
.1.3.6.1.2.1.16.15.1.1.9,RMON2-MIB::hlMatrixControlAlDeletes,Counter32,read-only,,current,,The number of times an alMatrix entry has been deleted from the alMatrix tables. If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the alMatrixSDTable and alMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlAlDeletes from hlMatrixControlAlInserts.
.1.3.6.1.2.1.16.15.1.1.10,RMON2-MIB::hlMatrixControlAlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the alMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlMatrixControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.15.1.1.11,RMON2-MIB::hlMatrixControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.15.1.1.12,RMON2-MIB::hlMatrixControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this hlMatrixControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlMatrixSDTable, nlMatrixDSTable, alMatrixSDTable, and alMatrixDSTable shall be deleted by the agent.
.1.3.6.1.2.1.16.15.2,RMON2-MIB::nlMatrixSDTable,,not-accessible,,current,,A list of traffic matrix entries that collect statistics for conversations between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all conversations from a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixDSTable with the same source address and destination address.
.1.3.6.1.2.1.16.15.2.1,RMON2-MIB::nlMatrixSDEntry,,not-accessible,hlMatrixControlIndex:nlMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress,current,,A conceptual row in the nlMatrixSDTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixSDSourceAddress and nlMatrixSDDestAddress. An example of the indexing of this table is nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.15.2.1.1,RMON2-MIB::nlMatrixSDTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.15.2.1.2,RMON2-MIB::nlMatrixSDSourceAddress,OCTET,not-accessible,,current,,The network source address for this nlMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.2.1.3,RMON2-MIB::nlMatrixSDDestAddress,OCTET,not-accessible,,current,,The network destination address for this nlMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.2.1.4,RMON2-MIB::nlMatrixSDPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixSDTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.2.1.5,RMON2-MIB::nlMatrixSDOctets,Gauge32,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixSDTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.2.1.6,RMON2-MIB::nlMatrixSDCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.15.3,RMON2-MIB::nlMatrixDSTable,,not-accessible,,current,,A list of traffic matrix entries that collect statistics for conversations between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all conversations to a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixSDTable with the same source address and destination address.
.1.3.6.1.2.1.16.15.3.1,RMON2-MIB::nlMatrixDSEntry,,not-accessible,hlMatrixControlIndex:nlMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress,current,,A conceptual row in the nlMatrixDSTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixDSSourceAddress and nlMatrixDSDestAddress. An example of the indexing of this table is nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.15.3.1.1,RMON2-MIB::nlMatrixDSTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.15.3.1.2,RMON2-MIB::nlMatrixDSSourceAddress,OCTET,not-accessible,,current,,The network source address for this nlMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.3.1.3,RMON2-MIB::nlMatrixDSDestAddress,OCTET,not-accessible,,current,,The network destination address for this nlMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.3.1.4,RMON2-MIB::nlMatrixDSPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixDSTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.3.1.5,RMON2-MIB::nlMatrixDSOctets,Gauge32,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixDSTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.3.1.6,RMON2-MIB::nlMatrixDSCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.15.4,RMON2-MIB::nlMatrixTopNControlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.
.1.3.6.1.2.1.16.15.4.1,RMON2-MIB::nlMatrixTopNControlEntry,,not-accessible,nlMatrixTopNControlIndex,current,,A conceptual row in the nlMatrixTopNControlTable. An example of the indexing of this table is nlMatrixTopNControlDuration.3
.1.3.6.1.2.1.16.15.4.1.1,RMON2-MIB::nlMatrixTopNControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the nlMatrixTopNControlTable. Each such entry defines one topN report prepared for one interface.
.1.3.6.1.2.1.16.15.4.1.2,RMON2-MIB::nlMatrixTopNControlMatrixIndex,Integer32,read-create,,current,,The nlMatrix[SD/DS] table for which a topN report will be prepared on behalf of this entry. The nlMatrix[SD/DS] table is identified by the value of the hlMatrixControlIndex for that table - that value is used here to identify the particular table. This object may not be modified if the associated nlMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.15.4.1.3,RMON2-MIB::nlMatrixTopNControlRateBase,INTEGER,read-create,,current,nlMatrixTopNPkts(1):nlMatrixTopNOctets(2):nlMatrixTopNHighCapacityPkts(3):nlMatrixTopNHighCapacityOctets(4),The variable for each nlMatrix[SD/DS] entry that the nlMatrixTopNEntries are sorted by, as well as a control for the table that the results will be reported in. This object may not be modified if the associated nlMatrixTopNControlStatus object is equal to active(1). If this value is less than or equal to 2, when the report is prepared, entries are created in the nlMatrixTopNTable associated with this object. If this value is greater than or equal to 3, when the report is prepared, entries are created in the nlMatrixTopNHighCapacityTable associated with this object.
.1.3.6.1.2.1.16.15.4.1.4,RMON2-MIB::nlMatrixTopNControlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report and is immediately loaded into the associated nlMatrixTopNControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of nlMatrixTopNControlTimeRemaining. Thus, the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the nlMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the nlMatrixTopNTable shall be deleted. (Note that this is a different algorithm than the one used in the hostTopNTable).
.1.3.6.1.2.1.16.15.4.1.5,RMON2-MIB::nlMatrixTopNControlGeneratedReports,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.15.4.1.6,RMON2-MIB::nlMatrixTopNControlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated nlMatrixTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the nlMatrixTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this nlMatrixTopNControlEntry.
.1.3.6.1.2.1.16.15.4.1.7,RMON2-MIB::nlMatrixTopNControlRequestedSize,Integer32,read-create,,current,,The maximum number of matrix entries requested for this report. When this object is created or modified, the probe should set nlMatrixTopNControlGrantedSize as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.15.4.1.8,RMON2-MIB::nlMatrixTopNControlGrantedSize,Integer32,read-only,,current,,The maximum number of matrix entries in this report. When the associated nlMatrixTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as possible for the particular implementation and available resources. The probe must not lower this value except as a side-effect of a set to the associated nlMatrixTopNControlRequestedSize object. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, when the next topN report is generated, matrix entries with the highest value of nlMatrixTopNPktRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, when the next topN report is generated, matrix entries with the highest value of nlMatrixTopNOctetRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. It is an implementation-specific matter how entries with the same value of nlMatrixTopNPktRate or nlMatrixTopNOctetRate are sorted. It is also an implementation-specific matter as to whether zero-valued entries are available.
.1.3.6.1.2.1.16.15.4.1.9,RMON2-MIB::nlMatrixTopNControlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this topN report was last started. In other words, this is the time that the associated nlMatrixTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine whether a report was missed.
.1.3.6.1.2.1.16.15.4.1.10,RMON2-MIB::nlMatrixTopNControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.15.4.1.11,RMON2-MIB::nlMatrixTopNControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this nlMatrixTopNControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlMatrixTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.15.5,RMON2-MIB::nlMatrixTopNTable,,not-accessible,,current,,A set of statistics for those network-layer matrix entries that have counted the highest number of octets or packets.
.1.3.6.1.2.1.16.15.5.1,RMON2-MIB::nlMatrixTopNEntry,,not-accessible,nlMatrixTopNControlIndex:nlMatrixTopNIndex,current,,A conceptual row in the nlMatrixTopNTable. The nlMatrixTopNControlIndex value in the index identifies the nlMatrixTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is nlMatrixTopNPktRate.3.10
.1.3.6.1.2.1.16.15.5.1.1,RMON2-MIB::nlMatrixTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the nlMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, increasing values of nlMatrixTopNIndex shall be assigned to entries with decreasing values of nlMatrixTopNPktRate until index N is assigned or there are no more nlMatrixTopNEntries. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, increasing values of nlMatrixTopNIndex shall be assigned to entries with decreasing values of nlMatrixTopNOctetRate until index N is assigned or there are no more nlMatrixTopNEntries.
.1.3.6.1.2.1.16.15.5.1.2,RMON2-MIB::nlMatrixTopNProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network-layer protocol of this entry's network address.
.1.3.6.1.2.1.16.15.5.1.3,RMON2-MIB::nlMatrixTopNSourceAddress,OCTET,read-only,,current,,The network-layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.5.1.4,RMON2-MIB::nlMatrixTopNDestAddress,OCTET,read-only,,current,,The network-layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the nlMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.5.1.5,RMON2-MIB::nlMatrixTopNPktRate,Gauge32,read-only,,current,,The number of packets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.5.1.6,RMON2-MIB::nlMatrixTopNReversePktRate,Gauge32,read-only,,current,,The number of packets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object. (Note that the corresponding nlMatrixSDPkts object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, the sort of topN entries is based entirely on nlMatrixTopNPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.5.1.7,RMON2-MIB::nlMatrixTopNOctetRate,Gauge32,read-only,,current,,The number of octets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDOctets object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.5.1.8,RMON2-MIB::nlMatrixTopNReverseOctetRate,Gauge32,read-only,,current,,The number of octets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixDSOctets object. (Note that the corresponding nlMatrixSDOctets object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, the sort of topN entries is based entirely on nlMatrixTopNOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.16,RMON2-MIB::alHost,,,,,,
.1.3.6.1.2.1.16.16.1,RMON2-MIB::alHostTable,,not-accessible,,current,,A collection of statistics for a particular protocol from a particular network address that has been discovered on an interface of this device. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address exists in the nlHostTable and will be deleted from this table if their address is deleted from the nlHostTable.
.1.3.6.1.2.1.16.16.1.1,RMON2-MIB::alHostEntry,,not-accessible,hlHostControlIndex:alHostTimeMark:protocolDirLocalIndex:nlHostAddress:protocolDirLocalIndex,current,,A conceptual row in the alHostTable. The hlHostControlIndex value in the index identifies the hlHostControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the address. The nlHostAddress value in the index identifies the network- layer address of this entry. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing in this entry is alHostOutPkts.1.783495.18.4.128.2.6.6.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.16.1.1.1,RMON2-MIB::alHostTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.16.1.1.2,RMON2-MIB::alHostInPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted to this address since it was added to the alHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.1.1.3,RMON2-MIB::alHostOutPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted by this address since it was added to the alHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.1.1.4,RMON2-MIB::alHostInOctets,Gauge32,read-only,,current,,The number of octets transmitted to this address of this protocol type since it was added to the alHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.16.1.1.5,RMON2-MIB::alHostOutOctets,Gauge32,read-only,,current,,The number of octets transmitted by this address of this protocol type since it was added to the alHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.16.1.1.6,RMON2-MIB::alHostCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.17,RMON2-MIB::alMatrix,,,,,,
.1.3.6.1.2.1.16.17.1,RMON2-MIB::alMatrixSDTable,,not-accessible,,current,,A list of application traffic matrix entries that collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all statistics from a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixSDTable and will be deleted from this table if the address pair is deleted from the nlMatrixSDTable.
.1.3.6.1.2.1.16.17.1.1,RMON2-MIB::alMatrixSDEntry,,not-accessible,hlMatrixControlIndex:alMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress:protocolDirLocalIndex,current,,A conceptual row in the alMatrixSDTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixSDSourceAddress and nlMatrixSDDestAddress. The nlMatrixSDSourceAddress value in the index identifies the network-layer address of the source host in this conversation. The nlMatrixSDDestAddress value in the index identifies the network-layer address of the destination host in this conversation. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing of this entry is alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.17.1.1.1,RMON2-MIB::alMatrixSDTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.17.1.1.2,RMON2-MIB::alMatrixSDPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted from the source address to the destination address since this entry was added to the alMatrixSDTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.1.1.3,RMON2-MIB::alMatrixSDOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixSDTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.1.1.4,RMON2-MIB::alMatrixSDCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.17.2,RMON2-MIB::alMatrixDSTable,,not-accessible,,current,,A list of application traffic matrix entries that collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all statistics to a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixDSTable and will be deleted from this table if the address pair is deleted from the nlMatrixDSTable.
.1.3.6.1.2.1.16.17.2.1,RMON2-MIB::alMatrixDSEntry,,not-accessible,hlMatrixControlIndex:alMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress:protocolDirLocalIndex,current,,A conceptual row in the alMatrixDSTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the alMatrixDSSourceAddress and alMatrixDSDestAddress. The nlMatrixDSDestAddress value in the index identifies the network-layer address of the destination host in this conversation. The nlMatrixDSSourceAddress value in the index identifies the network-layer address of the source host in this conversation. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing of this entry is alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.17.2.1.1,RMON2-MIB::alMatrixDSTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.17.2.1.2,RMON2-MIB::alMatrixDSPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted from the source address to the destination address since this entry was added to the alMatrixDSTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.2.1.3,RMON2-MIB::alMatrixDSOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixDSTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.2.1.4,RMON2-MIB::alMatrixDSCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.17.3,RMON2-MIB::alMatrixTopNControlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.
.1.3.6.1.2.1.16.17.3.1,RMON2-MIB::alMatrixTopNControlEntry,,not-accessible,alMatrixTopNControlIndex,current,,A conceptual row in the alMatrixTopNControlTable. An example of the indexing of this table is alMatrixTopNControlDuration.3
.1.3.6.1.2.1.16.17.3.1.1,RMON2-MIB::alMatrixTopNControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the alMatrixTopNControlTable. Each such entry defines one topN report prepared for one interface.
.1.3.6.1.2.1.16.17.3.1.2,RMON2-MIB::alMatrixTopNControlMatrixIndex,Integer32,read-create,,current,,The alMatrix[SD/DS] table for which a topN report will be prepared on behalf of this entry. The alMatrix[SD/DS] table is identified by the value of the hlMatrixControlIndex for that table - that value is used here to identify the particular table. This object may not be modified if the associated alMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.17.3.1.3,RMON2-MIB::alMatrixTopNControlRateBase,INTEGER,read-create,,current,alMatrixTopNTerminalsPkts(1):alMatrixTopNTerminalsOctets(2):alMatrixTopNAllPkts(3):alMatrixTopNAllOctets(4):alMatrixTopNTerminalsHighCapacityPkts(5):alMatrixTopNTerminalsHighCapacityOctets(6):alMatrixTopNAllHighCapacityPkts(7):alMatrixTopNAllHighCapacityOctets(8),This object controls which alMatrix[SD/DS] entry that the alMatrixTopNEntries are sorted by, which view of the matrix table that will be used, as well as which table the results will be reported in. The values alMatrixTopNTerminalsPkts, alMatrixTopNTerminalsOctets, alMatrixTopNTerminalsHighCapacityPkts, and alMatrixTopNTerminalsHighCapacityOctets cause collection only from protocols that have no child protocols that are counted. The values alMatrixTopNAllPkts, alMatrixTopNAllOctets, alMatrixTopNAllHighCapacityPkts, and alMatrixTopNAllHighCapacityOctets cause collection from all alMatrix entries. This object may not be modified if the associated alMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.17.3.1.4,RMON2-MIB::alMatrixTopNControlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report and is immediately loaded into the associated alMatrixTopNControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of alMatrixTopNControlTimeRemaining. Thus, the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the alMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the alMatrixTopNTable shall be deleted. (Note that this is a different algorithm than the one used in the hostTopNTable).
.1.3.6.1.2.1.16.17.3.1.5,RMON2-MIB::alMatrixTopNControlGeneratedReports,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.17.3.1.6,RMON2-MIB::alMatrixTopNControlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated alMatrixTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the alMatrixTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this alMatrixTopNControlEntry.
.1.3.6.1.2.1.16.17.3.1.7,RMON2-MIB::alMatrixTopNControlRequestedSize,Integer32,read-create,,current,,The maximum number of matrix entries requested for this report. When this object is created or modified, the probe should set alMatrixTopNControlGrantedSize as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.17.3.1.8,RMON2-MIB::alMatrixTopNControlGrantedSize,Integer32,read-only,,current,,The maximum number of matrix entries in this report. When the associated alMatrixTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as possible for the particular implementation and available resources. The probe must not lower this value except as a side-effect of a set to the associated alMatrixTopNControlRequestedSize object. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, when the next topN report is generated, matrix entries with the highest value of alMatrixTopNPktRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, when the next topN report is generated, matrix entries with the highest value of alMatrixTopNOctetRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. It is an implementation-specific matter how entries with the same value of alMatrixTopNPktRate or alMatrixTopNOctetRate are sorted. It is also an implementation-specific matter as to whether zero-valued entries are available.
.1.3.6.1.2.1.16.17.3.1.9,RMON2-MIB::alMatrixTopNControlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this topN report was last started. In other words, this is the time that the associated alMatrixTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine whether a report was missed.
.1.3.6.1.2.1.16.17.3.1.10,RMON2-MIB::alMatrixTopNControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.17.3.1.11,RMON2-MIB::alMatrixTopNControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this alMatrixTopNControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the alMatrixTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.17.4,RMON2-MIB::alMatrixTopNTable,,not-accessible,,current,,A set of statistics for those application-layer matrix entries that have counted the highest number of octets or packets.
.1.3.6.1.2.1.16.17.4.1,RMON2-MIB::alMatrixTopNEntry,,not-accessible,alMatrixTopNControlIndex:alMatrixTopNIndex,current,,A conceptual row in the alMatrixTopNTable. The alMatrixTopNControlIndex value in the index identifies the alMatrixTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is alMatrixTopNPktRate.3.10
.1.3.6.1.2.1.16.17.4.1.1,RMON2-MIB::alMatrixTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the alMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, increasing values of alMatrixTopNIndex shall be assigned to entries with decreasing values of alMatrixTopNPktRate until index N is assigned or there are no more alMatrixTopNEntries. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, increasing values of alMatrixTopNIndex shall be assigned to entries with decreasing values of alMatrixTopNOctetRate until index N is assigned or there are no more alMatrixTopNEntries.
.1.3.6.1.2.1.16.17.4.1.2,RMON2-MIB::alMatrixTopNProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network-layer protocol of this entry's network address.
.1.3.6.1.2.1.16.17.4.1.3,RMON2-MIB::alMatrixTopNSourceAddress,OCTET,read-only,,current,,The network-layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.17.4.1.4,RMON2-MIB::alMatrixTopNDestAddress,OCTET,read-only,,current,,The network-layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.17.4.1.5,RMON2-MIB::alMatrixTopNAppProtocolDirLocalIndex,Integer32,read-only,,current,,The type of the protocol counted by this matrix entry.
.1.3.6.1.2.1.16.17.4.1.6,RMON2-MIB::alMatrixTopNPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDPkts object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.4.1.7,RMON2-MIB::alMatrixTopNReversePktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixDSPkts object. (Note that the corresponding alMatrixSDPkts object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.) Note that if the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, the sort of topN entries is based entirely on alMatrixTopNPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.17.4.1.8,RMON2-MIB::alMatrixTopNOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDOctets object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.4.1.9,RMON2-MIB::alMatrixTopNReverseOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixDSOctets object. (Note that the corresponding alMatrixSDOctets object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.) Note that if the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, the sort of topN entries is based entirely on alMatrixTopNOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.18,RMON2-MIB::usrHistory,,,,,,
.1.3.6.1.2.1.16.18.1,RMON2-MIB::usrHistoryControlTable,,not-accessible,,current,,A list of data-collection configuration entries.
.1.3.6.1.2.1.16.18.1.1,RMON2-MIB::usrHistoryControlEntry,,not-accessible,usrHistoryControlIndex,current,,A list of parameters that set up a group of user-defined MIB objects to be sampled periodically (called a bucket-group). For example, an instance of usrHistoryControlInterval might be named usrHistoryControlInterval.1
.1.3.6.1.2.1.16.18.1.1.1,RMON2-MIB::usrHistoryControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the usrHistoryControlTable. Each such entry defines a set of samples at a particular interval for a specified set of MIB instances available from the managed system.
.1.3.6.1.2.1.16.18.1.1.2,RMON2-MIB::usrHistoryControlObjects,Integer32,read-create,,current,,The number of MIB objects to be collected in the portion of usrHistoryTable associated with this usrHistoryControlEntry. This object may not be modified if the associated instance of usrHistoryControlStatus is equal to active(1).
.1.3.6.1.2.1.16.18.1.1.3,RMON2-MIB::usrHistoryControlBucketsRequested,Integer32,read-create,,current,,The requested number of discrete time intervals over which data is to be saved in the part of the usrHistoryTable associated with this usrHistoryControlEntry. When this object is created or modified, the probe should set usrHistoryControlBucketsGranted as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.18.1.1.4,RMON2-MIB::usrHistoryControlBucketsGranted,Integer32,read-only,,current,,The number of discrete sampling intervals over which data shall be saved in the part of the usrHistoryTable associated with this usrHistoryControlEntry. When the associated usrHistoryControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated usrHistoryControlBucketsRequested object. The associated usrHistoryControlBucketsRequested object should be set before or at the same time as this object to allow the probe to accurately estimate the resources required for this usrHistoryControlEntry. There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the usrHistoryTable. When the number of buckets reaches the value of this object and a new bucket is to be added to the usrHistoryTable, the oldest bucket associated with this usrHistoryControlEntry shall be deleted by the agent so that the new bucket can be added. When the value of this object changes to a value less than the current value, entries are deleted from the usrHistoryTable associated with this usrHistoryControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated usrHistory entries may be allowed to grow.
.1.3.6.1.2.1.16.18.1.1.5,RMON2-MIB::usrHistoryControlInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled for each bucket in the part of the usrHistory table associated with this usrHistoryControlEntry. Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and to set the usrHistoryControlInterval object to a value less than this interval. This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.1.1.6,RMON2-MIB::usrHistoryControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.18.1.1.7,RMON2-MIB::usrHistoryControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this variable history control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the usrHistoryTable shall be deleted.
.1.3.6.1.2.1.16.18.2,RMON2-MIB::usrHistoryObjectTable,,not-accessible,,current,,A list of data-collection configuration entries.
.1.3.6.1.2.1.16.18.2.1,RMON2-MIB::usrHistoryObjectEntry,,not-accessible,usrHistoryControlIndex:usrHistoryObjectIndex,current,,A list of MIB instances to be sampled periodically. Entries in this table are created when an associated usrHistoryControlObjects object is created. The usrHistoryControlIndex value in the index is that of the associated usrHistoryControlEntry. For example, an instance of usrHistoryObjectVariable might be usrHistoryObjectVariable.1.3
.1.3.6.1.2.1.16.18.2.1.1,RMON2-MIB::usrHistoryObjectIndex,Integer32,not-accessible,,current,,An index used to uniquely identify an entry in the usrHistoryObject table. Each such entry defines a MIB instance to be collected periodically.
.1.3.6.1.2.1.16.18.2.1.2,RMON2-MIB::usrHistoryObjectVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of Integer32 (Integer32, Counter, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the user history mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. See USM [RFC3414] and VACM [RFC3415] for more information. During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.2.1.3,RMON2-MIB::usrHistoryObjectSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable for storage in the usrHistoryTable. If the value of this object is absoluteValue(1), the value of the selected variable will be copied directly into the history bucket. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference will be stored in the history bucket. If the associated usrHistoryObjectVariable instance could not be obtained at the previous sample interval, then a delta sample is not possible, and the value of the associated usrHistoryValStatus object for this interval will be valueNotAvailable(1). This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.3,RMON2-MIB::usrHistoryTable,,not-accessible,,current,,A list of user-defined history entries.
.1.3.6.1.2.1.16.18.3.1,RMON2-MIB::usrHistoryEntry,,not-accessible,usrHistoryControlIndex:usrHistorySampleIndex:usrHistoryObjectIndex,current,,A historical sample of user-defined variables. This sample is associated with the usrHistoryControlEntry that set up the parameters for a regular collection of these samples. The usrHistoryControlIndex value in the index identifies the usrHistoryControlEntry on whose behalf this entry was created. The usrHistoryObjectIndex value in the index identifies the usrHistoryObjectEntry on whose behalf this entry was created. For example, an instance of usrHistoryAbsValue, which represents the 14th sample of a variable collected as specified by usrHistoryControlEntry.1 and usrHistoryObjectEntry.1.5, would be named usrHistoryAbsValue.1.14.5
.1.3.6.1.2.1.16.18.3.1.1,RMON2-MIB::usrHistorySampleIndex,Integer32,not-accessible,,current,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same usrHistoryControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.18.3.1.2,RMON2-MIB::usrHistoryIntervalStart,TimeTicks,read-only,,current,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require that the probe delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample that is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.18.3.1.3,RMON2-MIB::usrHistoryIntervalEnd,TimeTicks,read-only,,current,,The value of sysUpTime at the end of the interval over which this sample was measured.
.1.3.6.1.2.1.16.18.3.1.4,RMON2-MIB::usrHistoryAbsValue,Gauge32,read-only,,current,,The absolute value (i.e., unsigned value) of the user-specified statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. To obtain the true value for this sampling interval, the associated instance of usrHistoryValStatus must be checked, and usrHistoryAbsValue adjusted as necessary. If the MIB instance could not be accessed during the sampling interval, then this object will have a value of zero, and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'. The access control check prescribed in the definition of usrHistoryObjectVariable SHOULD be checked for each sampling interval. If this check determines that access should not be allowed, then this object will have a value of zero, and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'.
.1.3.6.1.2.1.16.18.3.1.5,RMON2-MIB::usrHistoryValStatus,INTEGER,read-only,,current,valueNotAvailable(1):valuePositive(2):valueNegative(3),This object indicates the validity and sign of the data in the associated instance of usrHistoryAbsValue. If the MIB instance could not be accessed during the sampling interval, then 'valueNotAvailable(1)' will be returned. If the sample is valid and the actual value of the sample is greater than or equal to zero, then 'valuePositive(2)' is returned. If the sample is valid and the actual value of the sample is less than zero, 'valueNegative(3)' will be returned. The associated instance of usrHistoryAbsValue should be multiplied by -1 to obtain the true sample value.
.1.3.6.1.2.1.16.19,RMON2-MIB::probeConfig,,,,,,
.1.3.6.1.2.1.16.19.1,RMON2-MIB::probeCapabilities,BITS,read-only,,current,etherStats(0):historyControl(1):etherHistory(2):alarm(3):hosts(4):hostTopN(5):matrix(6):filter(7):capture(8):event(9):tokenRingMLStats(10):tokenRingPStats(11):tokenRingMLHistory(12):tokenRingPHistory(13):ringStation(14):ringStationOrder(15):ringStationConfig(16):sourceRouting(17):protocolDirectory(18):protocolDistribution(19):addressMapping(20):nlHost(21):nlMatrix(22):alHost(23):alMatrix(24):usrHistory(25):probeConfig(26),An indication of the RMON MIB groups supported on at least one interface by this probe.
.1.3.6.1.2.1.16.19.2,RMON2-MIB::probeSoftwareRev,OCTET,read-only,,current,,The software revision of this device. This string will have a zero length if the revision is unknown.
.1.3.6.1.2.1.16.19.3,RMON2-MIB::probeHardwareRev,OCTET,read-only,,current,,The hardware revision of this device. This string will have a zero length if the revision is unknown.
.1.3.6.1.2.1.16.19.4,RMON2-MIB::probeDateTime,OCTET,read-write,,current,,Probe's current date and time. field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then time zone information (fields 8-10) is not present, and that if no time information is known, the null string is returned.
.1.3.6.1.2.1.16.19.5,RMON2-MIB::probeResetControl,INTEGER,read-write,,current,running(1):warmBoot(2):coldBoot(3),Setting this object to warmBoot(2) causes the device to restart the application software with current configuration parameters saved in non-volatile memory. Setting this object to coldBoot(3) causes the device to reinitialize configuration parameters in non-volatile memory to default values and to restart the application software. When the device is running normally, this variable has a value of running(1).
.1.3.6.1.2.1.16.19.6,RMON2-MIB::probeDownloadFile,OCTET,read-write,,deprecated,,The file name to be downloaded from the TFTP server when a download is next requested via this MIB. This value is set to the zero-length string when no file name has been specified. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.7,RMON2-MIB::probeDownloadTFTPServer,IpAddress,read-write,,deprecated,,The IP address of the TFTP server that contains the boot image to load when a download is next requested via this MIB. This value is set to '0.0.0.0' when no IP address has been specified. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.8,RMON2-MIB::probeDownloadAction,INTEGER,read-write,,deprecated,notDownloading(1):downloadToPROM(2):downloadToRAM(3),When this object is set to downloadToRAM(3) or downloadToPROM(2), the device will discontinue its normal operation and begin download of the image specified by probeDownloadFile from the server specified by probeDownloadTFTPServer using the TFTP protocol. If downloadToRAM(3) is specified, the new image is copied to RAM only (the old image remains unaltered in the flash EPROM). If downloadToPROM(2) is specified, the new image is written to the flash EPROM memory after its checksum has been verified to be correct. When the download process is completed, the device will warm boot to restart the newly loaded application. When the device is not downloading, this object will have a value of notDownloading(1). This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.9,RMON2-MIB::probeDownloadStatus,INTEGER,read-only,,deprecated,downloadSuccess(1):downloadStatusUnknown(2):downloadGeneralError(3):downloadNoResponseFromServer(4):downloadChecksumError(5):downloadIncompatibleImage(6):downloadTftpFileNotFound(7):downloadTftpAccessViolation(8),The status of the last download procedure, if any. This object will have a value of downloadStatusUnknown(2) if no download process has been performed. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.10,RMON2-MIB::serialConfigTable,,not-accessible,,deprecated,,A table of serial interface configuration entries. This data will be stored in non-volatile memory and preserved across probe resets or power loss. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.10.1,RMON2-MIB::serialConfigEntry,,not-accessible,ifIndex,deprecated,,A set of configuration parameters for a particular serial interface on this device. If the device has no serial interfaces, this table is empty. The index is composed of the ifIndex assigned to this serial line interface.
.1.3.6.1.2.1.16.19.10.1.1,RMON2-MIB::serialMode,INTEGER,read-create,,deprecated,direct(1):modem(2),The type of incoming connection to be expected on this serial interface.
.1.3.6.1.2.1.16.19.10.1.2,RMON2-MIB::serialProtocol,INTEGER,read-create,,deprecated,other(1):slip(2):ppp(3),The type of data link encapsulation to be used on this serial interface.
.1.3.6.1.2.1.16.19.10.1.3,RMON2-MIB::serialTimeout,Integer32,read-create,,deprecated,,This timeout value is used when the Management Station has initiated the conversation over the serial link. This variable represents the number of seconds of inactivity allowed before terminating the connection on this serial interface. Use the serialDialoutTimeout in the case where the probe has initiated the connection for the purpose of sending a trap.
.1.3.6.1.2.1.16.19.10.1.4,RMON2-MIB::serialModemInitString,OCTET,read-create,,deprecated,,A control string that controls how a modem attached to this serial interface should be initialized. The initialization is performed once during startup and again after each connection is terminated if the associated serialMode has the value of modem(2). A control string that is appropriate for a wide variety of modems is: '^s^MATE0Q0V1X4 S0=1 S2=43^M'.
.1.3.6.1.2.1.16.19.10.1.5,RMON2-MIB::serialModemHangUpString,OCTET,read-create,,deprecated,,A control string that specifies how to disconnect a modem connection on this serial interface. This object is only meaningful if the associated serialMode has the value of modem(2). A control string that is appropriate for a wide variety of modems is: '^d2^s+++^d2^sATH0^M^d2'.
.1.3.6.1.2.1.16.19.10.1.6,RMON2-MIB::serialModemConnectResp,OCTET,read-create,,deprecated,,An ASCII string containing substrings that describe the expected modem connection response code and associated bps rate. The substrings are delimited by the first character in the string, for example: /CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ CONNECT 4800/4800/CONNECT 9600/9600 will be interpreted as: response code bps rate CONNECT 300 CONNECT 1200 1200 CONNECT 2400 2400 CONNECT 4800 4800 CONNECT 9600 9600 The agent will use the information in this string to adjust the bps rate of this serial interface once a modem connection is established. A value that is appropriate for a wide variety of modems is: '/CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ CONNECT 4800/4800/CONNECT 9600/9600/CONNECT 14400/14400/ CONNECT 19200/19200/CONNECT 38400/38400/'.
.1.3.6.1.2.1.16.19.10.1.7,RMON2-MIB::serialModemNoConnectResp,OCTET,read-create,,deprecated,,An ASCII string containing response codes that may be generated by a modem to report the reason why a connection attempt has failed. The response codes are delimited by the first character in the string, for example: /NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/ If one of these response codes is received via this serial interface while attempting to make a modem connection, the agent will issue the hang up command as specified by serialModemHangUpString. A value that is appropriate for a wide variety of modems is: '/NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/'.
.1.3.6.1.2.1.16.19.10.1.8,RMON2-MIB::serialDialoutTimeout,Integer32,read-create,,deprecated,,This timeout value is used when the probe initiates the serial connection with the intention of contacting a management station. This variable represents the number of seconds of inactivity allowed before terminating the connection on this serial interface.
.1.3.6.1.2.1.16.19.10.1.9,RMON2-MIB::serialStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this serialConfigEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.11,RMON2-MIB::netConfigTable,,not-accessible,,deprecated,,A table of netConfigEntries. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.11.1,RMON2-MIB::netConfigEntry,,not-accessible,ifIndex,deprecated,,A set of configuration parameters for a particular network interface on this device. If the device has no network interface, this table is empty. The index is composed of the ifIndex assigned to the corresponding interface.
.1.3.6.1.2.1.16.19.11.1.1,RMON2-MIB::netConfigIPAddress,IpAddress,read-create,,deprecated,,The IP address of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask is 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device). If BOOTP is used, care should be taken to not send BOOTP broadcasts too frequently and to eventually send them very infrequently if no replies are received.
.1.3.6.1.2.1.16.19.11.1.2,RMON2-MIB::netConfigSubnetMask,IpAddress,read-create,,deprecated,,The subnet mask of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask is 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device). If BOOTP is used, care should be taken to not send BOOTP broadcasts too frequently and to eventually send them very infrequently if no replies are received.
.1.3.6.1.2.1.16.19.11.1.3,RMON2-MIB::netConfigStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this netConfigEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.12,RMON2-MIB::netDefaultGateway,IpAddress,read-write,,deprecated,,The IP Address of the default gateway. If this value is undefined or unknown, it shall have the value 0.0.0.0.
.1.3.6.1.2.1.16.19.13,RMON2-MIB::trapDestTable,,not-accessible,,deprecated,,A list of trap destination entries.
.1.3.6.1.2.1.16.19.13.1,RMON2-MIB::trapDestEntry,,not-accessible,trapDestIndex,deprecated,,This entry includes a destination IP address to which traps are sent for this community.
.1.3.6.1.2.1.16.19.13.1.1,RMON2-MIB::trapDestIndex,Integer32,not-accessible,,deprecated,,A value that uniquely identifies this trapDestEntry.
.1.3.6.1.2.1.16.19.13.1.2,RMON2-MIB::trapDestCommunity,OCTET,read-create,,deprecated,,A community to which this destination address belongs. This entry is associated with any eventEntries in the RMON MIB whose value of eventCommunity is equal to the value of this object. Every time an associated event entry sends a trap due to an event, that trap will be sent to each address in the trapDestTable with a trapDestCommunity equal to eventCommunity, as long as no access control mechanism precludes it (e.g., VACM). This object may not be modified if the associated trapDestStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.13.1.3,RMON2-MIB::trapDestProtocol,INTEGER,read-create,,deprecated,ip(1):ipx(2),The protocol with which this trap is to be sent.
.1.3.6.1.2.1.16.19.13.1.4,RMON2-MIB::trapDestAddress,OCTET,read-create,,deprecated,,The destination address for traps on behalf of this entry. If the associated trapDestProtocol object is equal to ip(1), the encoding of this object is the same as the snmpUDPAddress textual convention in RFC 3417, 'Transport Mappings for the Simple Network Management Protocol (SNMP)' [RFC3417]: -- for a SnmpUDPAddress of length 6: -- -- octets contents encoding -- 1-4 IP-address network-byte order -- 5-6 UDP-port network-byte order If the associated trapDestProtocol object is equal to ipx(2), the encoding of this object is the same as the snmpIPXAddress textual convention in RFC 3417, 'Transport Mappings for the Simple Network Management Protocol (SNMP)' [RFC3417]: -- for a SnmpIPXAddress of length 12: -- -- octets contents encoding -- 1-4 network-number network-byte order -- 5-10 physical-address network-byte order -- 11-12 socket-number network-byte order This object may not be modified if the associated trapDestStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.13.1.5,RMON2-MIB::trapDestOwner,OCTET,read-create,,deprecated,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.19.13.1.6,RMON2-MIB::trapDestStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this trap destination entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.14,RMON2-MIB::serialConnectionTable,,not-accessible,,deprecated,,A list of serialConnectionEntries. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.14.1,RMON2-MIB::serialConnectionEntry,,not-accessible,serialConnectIndex,deprecated,,Configuration for a SLIP link over a serial line.
.1.3.6.1.2.1.16.19.14.1.1,RMON2-MIB::serialConnectIndex,Integer32,not-accessible,,deprecated,,A value that uniquely identifies this serialConnection entry.
.1.3.6.1.2.1.16.19.14.1.2,RMON2-MIB::serialConnectDestIpAddress,IpAddress,read-create,,deprecated,,The IP Address that can be reached at the other end of this serial connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.3,RMON2-MIB::serialConnectType,INTEGER,read-create,,deprecated,direct(1):modem(2):switch(3):modemSwitch(4),The type of outgoing connection to be made. If this object has the value direct(1), then a direct serial connection is assumed. If this object has the value modem(2), then serialConnectDialString will be used to make a modem connection. If this object has the value switch(3), then serialConnectSwitchConnectSeq will be used to establish the connection over a serial data switch, and serialConnectSwitchDisconnectSeq will be used to terminate the connection. If this object has the value modem-switch(4), then a modem connection will be made first, followed by the switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.4,RMON2-MIB::serialConnectDialString,OCTET,read-create,,deprecated,,A control string that specifies how to dial the phone number in order to establish a modem connection. The string should include the dialing prefix and suffix. For example: '^s^MATD9,888-1234^M' will instruct the Probe to send a carriage return, followed by the dialing prefix 'ATD', the phone number '9,888-1234', and a carriage return as the dialing suffix. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.5,RMON2-MIB::serialConnectSwitchConnectSeq,OCTET,read-create,,deprecated,,A control string that specifies how to establish a data switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.6,RMON2-MIB::serialConnectSwitchDisconnectSeq,OCTET,read-create,,deprecated,,A control string that specifies how to terminate a data switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.7,RMON2-MIB::serialConnectSwitchResetSeq,OCTET,read-create,,deprecated,,A control string that specifies how to reset a data switch in the event of a timeout. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.8,RMON2-MIB::serialConnectOwner,OCTET,read-create,,deprecated,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.19.14.1.9,RMON2-MIB::serialConnectStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this serialConnectionEntry. If the manager attempts to set this object to active(1) when the serialConnectType is set to modem(2) or modem-switch(4) and the serialConnectDialString is a zero-length string or cannot be correctly parsed as a ConnectString, the set request will be rejected with badValue(3). If the manager attempts to set this object to active(1) when the serialConnectType is set to switch(3) or modem-switch(4) and the serialConnectSwitchConnectSeq, the serialConnectSwitchDisconnectSeq, or the serialConnectSwitchResetSeq is a zero-length string or cannot be correctly parsed as a ConnectString, the set request will be rejected with badValue(3). An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.15,SMON-MIB::smonCapabilities,BITS,read-only,,current,smonVlanStats(0):smonPrioStats(1):dataSource(2):smonUnusedBit(3):portCopy(4),An indication of the SMON MIB groups supported by this agent.
.1.3.6.1.2.1.16.20,RMON-MIB::rmonConformance,,,,,,
.1.3.6.1.2.1.16.20.1,RMON2-MIB::rmon2MIBCompliances,,,,,,
.1.3.6.1.2.1.16.20.1.1,RMON2-MIB::rmon2MIBCompliance,,,,,,Describes the requirements for conformance to the RMON2 MIB
.1.3.6.1.2.1.16.20.1.2,RMON2-MIB::rmon2MIBApplicationLayerCompliance,,,,,,Describes the requirements for conformance to the RMON2 MIB with Application-Layer Enhancements.
.1.3.6.1.2.1.16.20.2,RMON2-MIB::rmon2MIBGroups,,,,,,
.1.3.6.1.2.1.16.20.2.1,RMON2-MIB::protocolDirectoryGroup,,,,,,Lists the inventory of protocols the probe has the capability of monitoring and allows the addition, deletion, and configuration of entries in this list.
.1.3.6.1.2.1.16.20.2.2,RMON2-MIB::protocolDistributionGroup,,,,,,Collects the relative amounts of octets and packets for the different protocols detected on a network segment.
.1.3.6.1.2.1.16.20.2.3,RMON2-MIB::addressMapGroup,,,,,,Lists MAC address to network address bindings discovered by the probe and what interface they were last seen on.
.1.3.6.1.2.1.16.20.2.4,RMON2-MIB::nlHostGroup,,,,,,Counts the amount of traffic sent from and to each network address discovered by the probe. Note that while the hlHostControlTable also has objects that control an optional alHostTable, implementation of the alHostTable is not required to fully implement this group.
.1.3.6.1.2.1.16.20.2.5,RMON2-MIB::nlMatrixGroup,,,,,,Counts the amount of traffic sent between each pair of network addresses discovered by the probe. Note that while the hlMatrixControlTable also has objects that control optional alMatrixTables, implementation of the alMatrixTables is not required to fully implement this group.
.1.3.6.1.2.1.16.20.2.6,RMON2-MIB::alHostGroup,,,,,,Counts the amount of traffic, by protocol, sent from and to each network address discovered by the probe. Implementation of this group requires implementation of the Network-Layer Host Group.
.1.3.6.1.2.1.16.20.2.7,RMON2-MIB::alMatrixGroup,,,,,,Counts the amount of traffic, by protocol, sent between each pair of network addresses discovered by the probe. Implementation of this group requires implementation of the Network-Layer Matrix Group.
.1.3.6.1.2.1.16.20.2.8,RMON2-MIB::usrHistoryGroup,,,,,,The usrHistoryGroup provides user-defined collection of historical information from MIB objects on the probe.
.1.3.6.1.2.1.16.20.2.9,RMON2-MIB::probeInformationGroup,,,,,,This group describes various operating parameters of the probe and controls the local time of the probe.
.1.3.6.1.2.1.16.20.2.10,RMON2-MIB::probeConfigurationGroup,,,,,,This group controls the configuration of various operating parameters of the probe. This group is not referenced by any MODULE-COMPLIANCE macro because it is 'grandfathered' from more recent MIB review rules that would require it.
.1.3.6.1.2.1.16.20.2.11,RMON2-MIB::rmon1EnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations.
.1.3.6.1.2.1.16.20.2.12,RMON2-MIB::rmon1EthernetEnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations.
.1.3.6.1.2.1.16.20.2.13,RMON2-MIB::rmon1TokenRingEnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations. This group is not referenced by any MODULE-COMPLIANCE macro because it is 'grandfathered' from more recent MIB review rules that would require it.
.1.3.6.1.2.1.16.20.3,SMON-MIB::smonMIBCompliances,,,,,,
.1.3.6.1.2.1.16.20.3.1,SMON-MIB::smonMIBCompliance,,,,,,Describes the requirements for full conformance with the SMON MIB
.1.3.6.1.2.1.16.20.3.2,SMON-MIB::smonMIBVlanStatsCompliance,,,,,,Describes the requirements for conformance with the SMON MIB with support for VLAN Statistics. Mandatory for a SMON probe in environment where IEEE 802.1Q bridging is implemented.
.1.3.6.1.2.1.16.20.3.3,SMON-MIB::smonMIBPrioStatsCompliance,,,,,,Describes the requirements for conformance with the SMON MIB with support for priority level Statistics. Mandatory for a SMON probe in a environment where IEEE 802.1p priority-switching is implemented.
.1.3.6.1.2.1.16.20.3.4,SMON-MIB::portCopyCompliance,,,,,,Describes the requirements for conformance with the port copy functionality defined by the SMON MIB
.1.3.6.1.2.1.16.20.4,SMON-MIB::smonMIBGroups,,,,,,
.1.3.6.1.2.1.16.20.4.1,SMON-MIB::dataSourceCapsGroup,,,,,,Defines the objects that describe the capabilities of RMON data sources.
.1.3.6.1.2.1.16.20.4.2,SMON-MIB::smonVlanStatsGroup,,,,,,Defines the switch monitoring specific statistics - per VLAN Id on interfaces of 10MB or less.
.1.3.6.1.2.1.16.20.4.3,SMON-MIB::smonPrioStatsGroup,,,,,,Defines the switch monitoring specific statistics - per VLAN Id on interface.
.1.3.6.1.2.1.16.20.4.4,SMON-MIB::smonHcTo100mbGroup,,,,,,Defines the additional high capacity statistics needed to be kept on interfaces with ifSpeed greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.5,SMON-MIB::smonHc100mbPlusGroup,,,,,,Defines the additional high capacity statistics needed to be kept on interfaces with ifSpeed of more than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.6,SMON-MIB::hcVlanTo100mbGroup,,,,,,Defines the additional high capacity VLAN statistics needed to be kept on interfaces with ifSpeed greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.7,SMON-MIB::hcVlan100mbPlusGroup,,,,,,Defines the additional high capacity VLAN statistics needed to be kept on interfaces with ifSpeed of more than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.8,SMON-MIB::hcPrioTo100mbGroup,,,,,,Defines the additional high capacity VLAN priority statistics needed to be kept on interfaces with ifSpeed of greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.9,SMON-MIB::hcPrio100mbPlusGroup,,,,,,Defines the additional high capacity VLAN priority statistics needed to be kept on interfaces with ifSpeed of greater than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.10,SMON-MIB::smonVlanStatsExtGroup,,,,,,Defines the switch monitoring specific statistics for systems capable of counting non-unicast octets for a given dataSource (as described in the dataSourceRmonCaps object).
.1.3.6.1.2.1.16.20.4.11,SMON-MIB::smonInformationGroup,,,,,,An indication of the SMON capabilities supported by this agent.
.1.3.6.1.2.1.16.20.4.12,SMON-MIB::portCopyConfigGroup,,,,,,Defines the control objects for copy port operations.
.1.3.6.1.2.1.16.20.8,RMON-MIB::rmonMibModule,,,,,,Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. This MIB defines objects for managing remote network monitoring devices.
.1.3.6.1.2.1.16.20.9,RMON-MIB::rmonCompliances,,,,,,
.1.3.6.1.2.1.16.20.9.1,RMON-MIB::rmonCompliance,,,,,,The requirements for conformance to the RMON MIB. At least one of the groups in this module must be implemented to conform to the RMON MIB. Implementations of this MIB must also implement the system group of MIB-II [16] and the IF-MIB [17].
.1.3.6.1.2.1.16.20.10,RMON-MIB::rmonGroups,,,,,,
.1.3.6.1.2.1.16.20.10.1,RMON-MIB::rmonEtherStatsGroup,,,,,,The RMON Ethernet Statistics Group.
.1.3.6.1.2.1.16.20.10.2,RMON-MIB::rmonHistoryControlGroup,,,,,,The RMON History Control Group.
.1.3.6.1.2.1.16.20.10.3,RMON-MIB::rmonEthernetHistoryGroup,,,,,,The RMON Ethernet History Group.
.1.3.6.1.2.1.16.20.10.4,RMON-MIB::rmonAlarmGroup,,,,,,The RMON Alarm Group.
.1.3.6.1.2.1.16.20.10.5,RMON-MIB::rmonHostGroup,,,,,,The RMON Host Group.
.1.3.6.1.2.1.16.20.10.6,RMON-MIB::rmonHostTopNGroup,,,,,,The RMON Host Top 'N' Group.
.1.3.6.1.2.1.16.20.10.7,RMON-MIB::rmonMatrixGroup,,,,,,The RMON Matrix Group.
.1.3.6.1.2.1.16.20.10.8,RMON-MIB::rmonFilterGroup,,,,,,The RMON Filter Group.
.1.3.6.1.2.1.16.20.10.9,RMON-MIB::rmonPacketCaptureGroup,,,,,,The RMON Packet Capture Group.
.1.3.6.1.2.1.16.20.10.10,RMON-MIB::rmonEventGroup,,,,,,The RMON Event Group.
.1.3.6.1.2.1.16.20.10.11,RMON-MIB::rmonNotificationGroup,,,,,,The RMON Notification Group.
.1.3.6.1.2.1.16.22,SMON-MIB::switchRMON,,,,,,The MIB module for managing remote monitoring device implementations for Switched Networks
.1.3.6.1.2.1.16.22.1,SMON-MIB::smonMIBObjects,,,,,,
.1.3.6.1.2.1.16.22.1.1,SMON-MIB::dataSourceCaps,,,,,,
.1.3.6.1.2.1.16.22.1.1.1,SMON-MIB::dataSourceCapsTable,,not-accessible,,current,,This table describes RMON data sources and port copy capabilities. An NMS MAY use this table to discover the identity and attributes of the data sources on a given agent implementation. Similar to the probeCapabilities object, actual row-creation operations will succeed or fail based on the resources available and parameter values used in each row-creation operation. Upon restart of the RMON agent, the dataSourceTable, ifTable, and perhaps entPhysicalTable are initialized for the available dataSources. For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry the agent MUST create an associated ifEntry with a ifType value of 'propVirtual(53)'. This ifEntry will be used as the actual value in RMON control table dataSource objects. The assigned ifIndex value is copied into the associated dataSourceCapsIfIndex object. It is understood that dataSources representing VLANs may not always be instantiated immediately upon restart, but rather as VLAN usage is detected by the agent. The agent SHOULD attempt to create dataSource and interface entries for all dataSources as soon as possible.
.1.3.6.1.2.1.16.22.1.1.1.1,SMON-MIB::dataSourceCapsEntry,,not-accessible,IMPLIEDdataSourceCapsObject,current,,Entries per data source containing descriptions of data source and port copy capabilities. This table is populated by the SMON agent with one entry for each supported data source.
.1.3.6.1.2.1.16.22.1.1.1.1.1,SMON-MIB::dataSourceCapsObject,OBJECT,not-accessible,,current,,Defines an object that can be a SMON data source or a source or a destination for a port copy operation.
.1.3.6.1.2.1.16.22.1.1.1.1.2,SMON-MIB::dataSourceRmonCaps,BITS,read-only,,current,countErrFrames(0):countAllGoodFrames(1):countAnyRmonTables(2):babyGiantsCountAsGood(3), General attributes of the specified dataSource. Note that these are static attributes, which SHOULD NOT be adjusted because of current resources or configuration. The agent sets this bit for the dataSource if errored frames received on this dataSource can actually be monitored by the agent The agent clears this bit if any errored frames are not visible to the RMON data collector. The agent sets this bit for the dataSource if all good frames received on this dataSource can actually be monitored by the agent. The agent clears this bit if any good frames are not visible for RMON collection, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function. The agent sets this bit if this dataSource can actually be used in any of the implemented RMON tables, resources notwithstanding. The agent clears this bit if this dataSourceCapsEntry is present simply to identify a dataSource that may only be used as portCopySource and/or a portCopyDest, but not the source of an actual RMON data collection. The agent sets this bit if it can distinguish, for counting purposes, between true giant frames and frames that exceed Ethernet maximum frame size 1518 due to VLAN tagging ('baby giants'). Specifically, this BIT means that frames up to 1522 octets are counted as good. Agents not capable of detecting 'baby giants' will clear this bit and will view all frames less than or equal to 1518 octets as 'good frames' and all frames larger than 1518 octets as 'bad frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables. Agents capable of detecting 'baby giants' SHALL consider them as 'good frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables.
.1.3.6.1.2.1.16.22.1.1.1.1.3,SMON-MIB::dataSourceCopyCaps,BITS,read-only,,current,copySourcePort(0):copyDestPort(1):copySrcTxTraffic(2):copySrcRxTraffic(3):countDestDropEvents(4):copyErrFrames(5):copyUnalteredFrames(6):copyAllGoodFrames(7),PortCopy function capabilities of the specified dataSource. The agent sets this bit if this dataSource is capable of acting as a source of a portCopy operation. The agent clears this bit otherwise. The agent sets this bit if this dataSource is capable of acting as a destination of a portCopy operation. The agent clears this bit otherwise. If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames transmitted out this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames received on this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared. If the copyDestPort bit is set: The agent sets this bit if it is capable of incrementing portCopyDestDropEvents, when this dataSource is the target of a portCopy operation and a frame destined to this dataSource is dropped (for RMON counting purposes). Else: this BIT SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit if it is capable of copying all errored frames from this portCopy source-port, for errored frames received on this dataSource. Else: this BIT SHOULD be cleared. If the copySourcePort bit is set: The agent sets the copyUnalteredFrames bit If it is capable of copying all frames from this portCopy source-port without alteration in any way; Else: this bit SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit for the dataSource if all good frames received on this dataSource are normally capable of being copied by the agent. The agent clears this bit if any good frames are not visible for the RMON portCopy operation, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function. Else: this bit SHOULD be cleared.
.1.3.6.1.2.1.16.22.1.1.1.1.4,SMON-MIB::dataSourceCapsIfIndex,Integer32,read-only,,current,,This object contains the ifIndex value of the ifEntry associated with this smonDataSource. The agent MUST create 'propVirtual' ifEntries for each dataSourceCapsEntry of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.22.1.2,SMON-MIB::smonStats,,,,,,
.1.3.6.1.2.1.16.22.1.2.1,SMON-MIB::smonVlanStatsControlTable,,not-accessible,,current,,Controls the setup of VLAN statistics tables. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection.
.1.3.6.1.2.1.16.22.1.2.1.1,SMON-MIB::smonVlanStatsControlEntry,,not-accessible,smonVlanStatsControlIndex,current,,A conceptual row in the smonVlanStatsControlTable.
.1.3.6.1.2.1.16.22.1.2.1.1.1,SMON-MIB::smonVlanStatsControlIndex,Integer32,not-accessible,,current,,A unique arbitrary index for this smonVlanStatsControlEntry.
.1.3.6.1.2.1.16.22.1.2.1.1.2,SMON-MIB::smonVlanStatsControlDataSource,OBJECT,read-create,,current,,The source of data for this set of VLAN statistics. This object MAY NOT be modified if the associated smonVlanStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.22.1.2.1.1.3,SMON-MIB::smonVlanStatsControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.1.1.4,SMON-MIB::smonVlanStatsControlOwner,OCTET,read-create,,current,,Administratively assigned named of the owner of this entry. It usually defines the entity that created this entry and is therefore using the resources assigned to it, though there is no enforcement mechanism, nor assurance that rows created are ever used.
.1.3.6.1.2.1.16.22.1.2.1.1.5,SMON-MIB::smonVlanStatsControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the smonVlanIdStatsTable SHALL be deleted.
.1.3.6.1.2.1.16.22.1.2.2,SMON-MIB::smonVlanIdStatsTable,,not-accessible,,current,,Contains the VLAN statistics data. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection. This function applies the same rules for attributing frames to VLAN-based collections. RMON VLAN statistics are collected after the Ingress Rules defined in section 3.13 of the VLAN Specification [20] are applied. It is possible that entries in this table will be garbage-collected, based on agent resources, and VLAN configuration. Agents are encouraged to support all 4094 index values and not garbage collect this table.
.1.3.6.1.2.1.16.22.1.2.2.1,SMON-MIB::smonVlanIdStatsEntry,,not-accessible,smonVlanStatsControlIndex:smonVlanIdStatsId,current,,A conceptual row in smonVlanIdStatsTable.
.1.3.6.1.2.1.16.22.1.2.2.1.1,SMON-MIB::smonVlanIdStatsId,Integer32,not-accessible,,current,,The unique identifier of the VLAN monitored for this specific statistics collection. Tagged packets match the VID for the range between 1 and 4094. An external RMON probe MAY detect VID=0 on an Inter Switch Link, in which case the packet belongs to a VLAN determined by the PVID of the ingress port. The VLAN to which such a packet belongs can be determined only by a RMON probe internal to the switch.
.1.3.6.1.2.1.16.22.1.2.2.1.2,SMON-MIB::smonVlanIdStatsTotalPkts,Counter32,read-only,,current,,The total number of packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.3,SMON-MIB::smonVlanIdStatsTotalOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsTotalPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.4,SMON-MIB::smonVlanIdStatsTotalHCPkts,Counter64,read-only,,current,,The total number of packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.5,SMON-MIB::smonVlanIdStatsTotalOctets,Counter32,read-only,,current,,The total number of octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.6,SMON-MIB::smonVlanIdStatsTotalOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsTotalOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.7,SMON-MIB::smonVlanIdStatsTotalHCOctets,Counter64,read-only,,current,,The total number of octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.8,SMON-MIB::smonVlanIdStatsNUcastPkts,Counter32,read-only,,current,,The total number of non-unicast packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.9,SMON-MIB::smonVlanIdStatsNUcastOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsNUcastPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.10,SMON-MIB::smonVlanIdStatsNUcastHCPkts,Counter64,read-only,,current,,The total number of non-unicast packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.11,SMON-MIB::smonVlanIdStatsNUcastOctets,Counter32,read-only,,current,,The total number of non-unicast octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.12,SMON-MIB::smonVlanIdStatsNUcastOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsNUcastOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.13,SMON-MIB::smonVlanIdStatsNUcastHCOctets,Counter64,read-only,,current,,The total number of Non-unicast octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.14,SMON-MIB::smonVlanIdStatsCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.3,SMON-MIB::smonPrioStatsControlTable,,not-accessible,,current,,Controls the setup of priority statistics tables. The smonPrioStatsControlTable allows configuration of collections based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19],[20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes.
.1.3.6.1.2.1.16.22.1.2.3.1,SMON-MIB::smonPrioStatsControlEntry,,not-accessible,smonPrioStatsControlIndex,current,,A conceptual row in the smonPrioStatsControlTable.
.1.3.6.1.2.1.16.22.1.2.3.1.1,SMON-MIB::smonPrioStatsControlIndex,Integer32,not-accessible,,current,,A unique arbitrary index for this smonPrioStatsControlEntry.
.1.3.6.1.2.1.16.22.1.2.3.1.2,SMON-MIB::smonPrioStatsControlDataSource,OBJECT,read-create,,current,,The source of data for this set of VLAN statistics. This object MAY NOT be modified if the associated smonPrioStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.22.1.2.3.1.3,SMON-MIB::smonPrioStatsControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was created. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.3.1.4,SMON-MIB::smonPrioStatsControlOwner,OCTET,read-create,,current,,Administratively assigned named of the owner of this entry. It usually defines the entity that created this entry and is therefore using the resources assigned to it, though there is no enforcement mechanism, nor assurance that rows created are ever used.
.1.3.6.1.2.1.16.22.1.2.3.1.5,SMON-MIB::smonPrioStatsControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the smonPrioStatsTable SHALL be deleted.
.1.3.6.1.2.1.16.22.1.2.4,SMON-MIB::smonPrioStatsTable,,not-accessible,,current,,Contains the priority statistics. The collections are based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19], [20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes. No garbage collection is designed for this table, as there always are at most eight rows per statistical set, and the low memory requirements do not justify the implementation of such a mechanism.
.1.3.6.1.2.1.16.22.1.2.4.1,SMON-MIB::smonPrioStatsEntry,,not-accessible,smonPrioStatsControlIndex:smonPrioStatsId,current,,A conceptual row in smonPrioStatsTable.
.1.3.6.1.2.1.16.22.1.2.4.1.1,SMON-MIB::smonPrioStatsId,Integer32,not-accessible,,current,,The unique identifier of the priority level monitored for this specific statistics collection.
.1.3.6.1.2.1.16.22.1.2.4.1.2,SMON-MIB::smonPrioStatsPkts,Counter32,read-only,,current,,The total number of packets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.3,SMON-MIB::smonPrioStatsOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonPrioStatsPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.4.1.4,SMON-MIB::smonPrioStatsHCPkts,Counter64,read-only,,current,,The total number of packets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.5,SMON-MIB::smonPrioStatsOctets,Counter32,read-only,,current,,The total number of octets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.6,SMON-MIB::smonPrioStatsOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonPrioStatsOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.4.1.7,SMON-MIB::smonPrioStatsHCOctets,Counter64,read-only,,current,,The total number of octets counted on this priority level.
.1.3.6.1.2.1.16.22.1.3,SMON-MIB::portCopyConfig,,,,,,
.1.3.6.1.2.1.16.22.1.3.1,SMON-MIB::portCopyTable,,not-accessible,,current,, Port Copy provides the ability to copy all frames from a specified source to specified destination within a switch. Source and destinations MUST be ifEntries, as defined by [22]. One to one, one to many, many to one and many to many source to destination relationships may be configured. Applicable counters on the destination will increment for all packets transiting the port, be it by normal bridging/switching or due to packet copy. Note that this table manages no RMON data collection by itself, and an agent may possibly implement no RMON objects except objects related to the port copy operation defined by the portCopyCompliance conformance macro. That allows for a switch with no other embedded RMON capability to perform port copy operations to a destination port at which a different external RMON probe is connected. One to one, many to one and one to many source to destination relationships may be configured. Each row that exists in this table defines such a relationship. By disabling a row in this table the port copy relationship no longer exists. The number of entries and the types of port copies (1-1, many-1, 1-many) are implementation specific and could possibly be dynamic due to changing resource availability. In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'. The capability of an interface to be source or destination of a port copy operation is described by the 'copySourcePort(0)' and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created. Applicable counters on the destination will increment for all packets transmitted, be it by normal bridging/switching or due to packet copy.
.1.3.6.1.2.1.16.22.1.3.1.1,SMON-MIB::portCopyEntry,,not-accessible,portCopySource:portCopyDest,current,,Describes a particular port copy entry.
.1.3.6.1.2.1.16.22.1.3.1.1.1,SMON-MIB::portCopySource,Integer32,not-accessible,,current,,The ifIndex of the source which will have all packets redirected to the destination as defined by portCopyDest.
.1.3.6.1.2.1.16.22.1.3.1.1.2,SMON-MIB::portCopyDest,Integer32,not-accessible,,current,,Defines the ifIndex destination for the copy operation.
.1.3.6.1.2.1.16.22.1.3.1.1.3,SMON-MIB::portCopyDestDropEvents,Counter32,read-only,,current,,The total number of events in which port copy packets were dropped by the switch at the destination port 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. A single dropped event counter is maintained for each portCopyDest. Thus all instances associated with a given portCopyDest will have the same portCopyDestDropEvents value.
.1.3.6.1.2.1.16.22.1.3.1.1.4,SMON-MIB::portCopyDirection,INTEGER,read-create,,current,copyRxOnly(1):copyTxOnly(2):copyBoth(3),This object affects the way traffic is copied from a switch source port, for the indicated port copy operation. If this object has the value 'copyRxOnly(1)', then only traffic received on the indicated source port will be copied to the indicated destination port. If this object has the value 'copyTxOnly(2)', then only traffic transmitted out the indicated source port will be copied to the indicated destination port. If this object has the value 'copyBoth(3)', then all traffic received or transmitted on the indicated source port will be copied to the indicated destination port. The creation and deletion of instances of this object is controlled by the portCopyRowStatus object. Note that there is no guarantee that changes in the value of this object performed while the associated portCopyRowStatus object is equal to active will not cause traffic discontinuities in the packet stream.
.1.3.6.1.2.1.16.22.1.3.1.1.5,SMON-MIB::portCopyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Defines the status of the port copy entry. In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'. The capability of an interface to be source or destination of a port copy operation is described by the 'copySourcePort(0)' and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created.
.1.3.6.1.2.1.16.22.1.4,SMON-MIB::smonRegistrationPoints,,,,,,
.1.3.6.1.2.1.16.22.1.4.1,SMON-MIB::smonVlanDataSource,,,,,,
.1.3.6.1.2.1.17,BRIDGE-MIB::dot1dBridge,,,,,,The Bridge MIB module for managing devices that support IEEE 802.1D. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4188; see the RFC itself for full legal notices.
.1.3.6.1.2.1.17.0,BRIDGE-MIB::dot1dNotifications,,,,,,
.1.3.6.1.2.1.17.0.1,BRIDGE-MIB::newRoot,,,,,,The newRoot trap indicates that the sending agent has become the new root of the Spanning Tree; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer, immediately subsequent to its election. Implementation of this trap is optional.
.1.3.6.1.2.1.17.0.2,BRIDGE-MIB::topologyChange,,,,,,A topologyChange trap is sent by a bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a newRoot trap is sent for the same transition. Implementation of this trap is optional.
.1.3.6.1.2.1.17.1,BRIDGE-MIB::dot1dBase,,,,,,
.1.3.6.1.2.1.17.1.1,BRIDGE-MIB::dot1dBaseBridgeAddress,OCTET,read-only,,current,,The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be the numerically smallest MAC address of all ports that belong to this bridge. However, it is only required to be unique. When concatenated with dot1dStpPriority, a unique BridgeIdentifier is formed, which is used in the Spanning Tree Protocol.
.1.3.6.1.2.1.17.1.2,BRIDGE-MIB::dot1dBaseNumPorts,Integer32,read-only,,current,,The number of ports controlled by this bridging entity.
.1.3.6.1.2.1.17.1.3,BRIDGE-MIB::dot1dBaseType,INTEGER,read-only,,current,unknown(1):transparent-only(2):sourceroute-only(3):srt(4),Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging, this will be indicated by entries in the port table for the given type.
.1.3.6.1.2.1.17.1.4,BRIDGE-MIB::dot1dBasePortTable,,not-accessible,,current,,A table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.
.1.3.6.1.2.1.17.1.4.1,BRIDGE-MIB::dot1dBasePortEntry,,not-accessible,dot1dBasePort,current,,A list of information for each port of the bridge.
.1.3.6.1.2.1.17.1.4.1.1,BRIDGE-MIB::dot1dBasePort,Integer32,read-only,,current,,The port number of the port for which this entry contains bridge management information.
.1.3.6.1.2.1.17.1.4.1.2,BRIDGE-MIB::dot1dBasePortIfIndex,Integer32,read-only,,current,,The value of the instance of the ifIndex object, defined in IF-MIB, for the interface corresponding to this port.
.1.3.6.1.2.1.17.1.4.1.3,BRIDGE-MIB::dot1dBasePortCircuit,OBJECT,read-only,,current,,For a port that (potentially) has the same value of dot1dBasePortIfIndex as another port on the same bridge. This object contains the name of an object instance unique to this port. For example, in the case where multiple ports correspond one-to-one with multiple X.25 virtual circuits, this value might identify an (e.g., the first) object instance associated with the X.25 virtual circuit corresponding to this port. For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value { 0 0 }.
.1.3.6.1.2.1.17.1.4.1.4,BRIDGE-MIB::dot1dBasePortDelayExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due to excessive transit delay through the bridge. It is incremented by both transparent and source route bridges.
.1.3.6.1.2.1.17.1.4.1.5,BRIDGE-MIB::dot1dBasePortMtuExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source route bridges.
.1.3.6.1.2.1.17.2,BRIDGE-MIB::dot1dStp,,,,,,
.1.3.6.1.2.1.17.2.1,BRIDGE-MIB::dot1dStpProtocolSpecification,INTEGER,read-only,,current,unknown(1):decLb100(2):ieee8021d(3),An indication of what version of the Spanning Tree Protocol is being run. The value 'decLb100(2)' indicates the DEC LANbridge 100 Spanning Tree protocol. IEEE 802.1D implementations will return 'ieee8021d(3)'. If future versions of the IEEE Spanning Tree Protocol that are incompatible with the current version are released a new value will be defined.
.1.3.6.1.2.1.17.2.2,BRIDGE-MIB::dot1dStpPriority,Integer32,read-write,,current,,The value of the write-able portion of the Bridge ID (i.e., the first two octets of the (8 octet long) Bridge ID). The other (last) 6 octets of the Bridge ID are given by the value of dot1dBaseBridgeAddress. On bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-61440, in steps of 4096.
.1.3.6.1.2.1.17.2.3,BRIDGE-MIB::dot1dStpTimeSinceTopologyChange,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity. For RSTP, this reports the time since the tcWhile timer for any port on this Bridge was nonzero.
.1.3.6.1.2.1.17.2.4,BRIDGE-MIB::dot1dStpTopChanges,Counter32,read-only,,current,,The total number of topology changes detected by this bridge since the management entity was last reset or initialized.
.1.3.6.1.2.1.17.2.5,BRIDGE-MIB::dot1dStpDesignatedRoot,OCTET,read-only,,current,,The bridge identifier of the root of the spanning tree, as determined by the Spanning Tree Protocol, as executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.
.1.3.6.1.2.1.17.2.6,BRIDGE-MIB::dot1dStpRootCost,Integer32,read-only,,current,,The cost of the path to the root as seen from this bridge.
.1.3.6.1.2.1.17.2.7,BRIDGE-MIB::dot1dStpRootPort,Integer32,read-only,,current,,The port number of the port that offers the lowest cost path from this bridge to the root bridge.
.1.3.6.1.2.1.17.2.8,BRIDGE-MIB::dot1dStpMaxAge,Integer32,read-only,,current,,The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.
.1.3.6.1.2.1.17.2.9,BRIDGE-MIB::dot1dStpHelloTime,Integer32,read-only,,current,,The amount of time between the transmission of Configuration bridge PDUs by this node on any port when it is the root of the spanning tree, or trying to become so, in units of hundredths of a second. This is the actual value that this bridge is currently using.
.1.3.6.1.2.1.17.2.10,BRIDGE-MIB::dot1dStpHoldTime,Integer32,read-only,,current,,This time value determines the interval length during which no more than two Configuration bridge PDUs shall be transmitted by this node, in units of hundredths of a second.
.1.3.6.1.2.1.17.2.11,BRIDGE-MIB::dot1dStpForwardDelay,Integer32,read-only,,current,,This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used when a topology change has been detected and is underway, to age all dynamic entries in the Forwarding Database. [Note that this value is the one that this bridge is currently using, in contrast to dot1dStpBridgeForwardDelay, which is the value that this bridge and all others would start using if/when this bridge were to become the root.]
.1.3.6.1.2.1.17.2.12,BRIDGE-MIB::dot1dStpBridgeMaxAge,Integer32,read-write,,current,,The value that all bridges use for MaxAge when this bridge is acting as the root. Note that 802.1D-1998 specifies that the range for this parameter is related to the value of dot1dStpBridgeHelloTime. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.13,BRIDGE-MIB::dot1dStpBridgeHelloTime,Integer32,read-write,,current,,The value that all bridges use for HelloTime when this bridge is acting as the root. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.14,BRIDGE-MIB::dot1dStpBridgeForwardDelay,Integer32,read-write,,current,,The value that all bridges use for ForwardDelay when this bridge is acting as the root. Note that 802.1D-1998 specifies that the range for this parameter is related to the value of dot1dStpBridgeMaxAge. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.15,BRIDGE-MIB::dot1dStpPortTable,,not-accessible,,current,,A table that contains port-specific information for the Spanning Tree Protocol.
.1.3.6.1.2.1.17.2.15.1,BRIDGE-MIB::dot1dStpPortEntry,,not-accessible,dot1dStpPort,current,,A list of information maintained by every port about the Spanning Tree Protocol state for that port.
.1.3.6.1.2.1.17.2.15.1.1,BRIDGE-MIB::dot1dStpPort,Integer32,read-only,,current,,The port number of the port for which this entry contains Spanning Tree Protocol management information.
.1.3.6.1.2.1.17.2.15.1.2,BRIDGE-MIB::dot1dStpPortPriority,Integer32,read-write,,current,,The value of the priority field that is contained in the first (in network byte order) octet of the (2 octet long) Port ID. The other octet of the Port ID is given by the value of dot1dStpPort. On bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-240, in steps of 16.
.1.3.6.1.2.1.17.2.15.1.3,BRIDGE-MIB::dot1dStpPortState,INTEGER,read-only,,current,disabled(1):blocking(2):listening(3):learning(4):forwarding(5):broken(6),The port's current state, as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning, it will place that port into the broken(6) state. For ports that are disabled (see dot1dStpPortEnable), this object will have a value of disabled(1).
.1.3.6.1.2.1.17.2.15.1.4,BRIDGE-MIB::dot1dStpPortEnable,INTEGER,read-write,,current,enabled(1):disabled(2),The enabled/disabled status of the port.
.1.3.6.1.2.1.17.2.15.1.5,BRIDGE-MIB::dot1dStpPortPathCost,Integer32,read-write,,current,,The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN. New implementations should support dot1dStpPortPathCost32. If the port path costs exceeds the maximum value of this object then this object should report the maximum value, namely 65535. Applications should try to read the dot1dStpPortPathCost32 object if this object reports the maximum value.
.1.3.6.1.2.1.17.2.15.1.6,BRIDGE-MIB::dot1dStpPortDesignatedRoot,OCTET,read-only,,current,,The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached.
.1.3.6.1.2.1.17.2.15.1.7,BRIDGE-MIB::dot1dStpPortDesignatedCost,Integer32,read-only,,current,,The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs.
.1.3.6.1.2.1.17.2.15.1.8,BRIDGE-MIB::dot1dStpPortDesignatedBridge,OCTET,read-only,,current,,The Bridge Identifier of the bridge that this port considers to be the Designated Bridge for this port's segment.
.1.3.6.1.2.1.17.2.15.1.9,BRIDGE-MIB::dot1dStpPortDesignatedPort,OCTET,read-only,,current,,The Port Identifier of the port on the Designated Bridge for this port's segment.
.1.3.6.1.2.1.17.2.15.1.10,BRIDGE-MIB::dot1dStpPortForwardTransitions,Counter32,read-only,,current,,The number of times this port has transitioned from the Learning state to the Forwarding state.
.1.3.6.1.2.1.17.2.15.1.11,BRIDGE-MIB::dot1dStpPortPathCost32,Integer32,read-write,,current,,The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN. This object replaces dot1dStpPortPathCost to support IEEE 802.1t.
.1.3.6.1.2.1.17.3,BRIDGE-MIB::dot1dSr,,,,,,
.1.3.6.1.2.1.17.4,BRIDGE-MIB::dot1dTp,,,,,,
.1.3.6.1.2.1.17.4.1,BRIDGE-MIB::dot1dTpLearnedEntryDiscards,Counter32,read-only,,current,,The total number of Forwarding Database entries that have been or would have been learned, but have been discarded due to a lack of storage space in the Forwarding Database. If this counter is increasing, it indicates that the Forwarding Database is regularly becoming full (a condition that has unpleasant performance effects on the subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has been occurring but is not persistent.
.1.3.6.1.2.1.17.4.2,BRIDGE-MIB::dot1dTpAgingTime,Integer32,read-write,,current,,The timeout period in seconds for aging out dynamically-learned forwarding information. 802.1D-1998 recommends a default of 300 seconds.
.1.3.6.1.2.1.17.4.3,BRIDGE-MIB::dot1dTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.6.1.2.1.17.4.3.1,BRIDGE-MIB::dot1dTpFdbEntry,,not-accessible,dot1dTpFdbAddress,current,,Information about a specific unicast MAC address for which the bridge has some forwarding and/or filtering information.
.1.3.6.1.2.1.17.4.3.1.1,BRIDGE-MIB::dot1dTpFdbAddress,OCTET,read-only,,current,,A unicast MAC address for which the bridge has forwarding and/or filtering information.
.1.3.6.1.2.1.17.4.3.1.2,BRIDGE-MIB::dot1dTpFdbPort,Integer32,read-only,,current,,Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1dTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned, but that the bridge does have some forwarding/filtering information about this address (e.g., in the dot1dStaticTable). Implementors are encouraged to assign the port value to this object whenever it is learned, even for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).
.1.3.6.1.2.1.17.4.3.1.3,BRIDGE-MIB::dot1dTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the values are: other(1) - none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1dTpFdbAddress are being forwarded. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out), but has not yet been flushed from the table. learned(3) - the value of the corresponding instance of dot1dTpFdbPort was learned, and is being used. self(4) - the value of the corresponding instance of dot1dTpFdbAddress represents one of the bridge's addresses. The corresponding instance of dot1dTpFdbPort indicates which of the bridge's ports has this address. mgmt(5) - the value of the corresponding instance of dot1dTpFdbAddress is also the value of an existing instance of dot1dStaticAddress.
.1.3.6.1.2.1.17.4.4,BRIDGE-MIB::dot1dTpPortTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.4.4.1,BRIDGE-MIB::dot1dTpPortEntry,,not-accessible,dot1dTpPort,current,,A list of information for each port of a transparent bridge.
.1.3.6.1.2.1.17.4.4.1.1,BRIDGE-MIB::dot1dTpPort,Integer32,read-only,,current,,The port number of the port for which this entry contains Transparent bridging management information.
.1.3.6.1.2.1.17.4.4.1.2,BRIDGE-MIB::dot1dTpPortMaxInfo,Integer32,read-only,,current,,The maximum size of the INFO (non-MAC) field that this port will receive or transmit.
.1.3.6.1.2.1.17.4.4.1.3,BRIDGE-MIB::dot1dTpPortInFrames,Counter32,read-only,,current,,The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.4.1.4,BRIDGE-MIB::dot1dTpPortOutFrames,Counter32,read-only,,current,,The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.4.1.5,BRIDGE-MIB::dot1dTpPortInDiscards,Counter32,read-only,,current,,Count of received valid frames that were discarded (i.e., filtered) by the Forwarding Process.
.1.3.6.1.2.1.17.4.5,P-BRIDGE-MIB::dot1dTpHCPortTable,,not-accessible,,current,,A table that contains information about every high- capacity port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.4.5.1,P-BRIDGE-MIB::dot1dTpHCPortEntry,,not-accessible,dot1dTpPort,current,,Statistics information for each high-capacity port of a transparent bridge.
.1.3.6.1.2.1.17.4.5.1.1,P-BRIDGE-MIB::dot1dTpHCPortInFrames,Counter64,read-only,,current,,The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.5.1.2,P-BRIDGE-MIB::dot1dTpHCPortOutFrames,Counter64,read-only,,current,,The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.5.1.3,P-BRIDGE-MIB::dot1dTpHCPortInDiscards,Counter64,read-only,,current,,Count of valid frames that have been received by this port from its segment that were discarded (i.e., filtered) by the Forwarding Process.
.1.3.6.1.2.1.17.4.6,P-BRIDGE-MIB::dot1dTpPortOverflowTable,,not-accessible,,current,,A table that contains the most-significant bits of statistics counters for ports that are associated with this transparent bridge that are on high-capacity interfaces, as defined in the conformance clauses for this table. This table is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least-significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification.
.1.3.6.1.2.1.17.4.6.1,P-BRIDGE-MIB::dot1dTpPortOverflowEntry,,not-accessible,dot1dTpPort,current,,The most significant bits of statistics counters for a high- capacity interface of a transparent bridge. Each object is associated with a corresponding object in dot1dTpPortTable that indicates the least significant bits of the counter.
.1.3.6.1.2.1.17.4.6.1.1,P-BRIDGE-MIB::dot1dTpPortInOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1dTpPortInFrames counter has overflowed.
.1.3.6.1.2.1.17.4.6.1.2,P-BRIDGE-MIB::dot1dTpPortOutOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1dTpPortOutFrames counter has overflowed.
.1.3.6.1.2.1.17.4.6.1.3,P-BRIDGE-MIB::dot1dTpPortInOverflowDiscards,Counter32,read-only,,current,,The number of times the associated dot1dTpPortInDiscards counter has overflowed.
.1.3.6.1.2.1.17.5,BRIDGE-MIB::dot1dStatic,,,,,,
.1.3.6.1.2.1.17.5.1,BRIDGE-MIB::dot1dStaticTable,,not-accessible,,current,,A table containing filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table, as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and for group/broadcast addresses.
.1.3.6.1.2.1.17.5.1.1,BRIDGE-MIB::dot1dStaticEntry,,not-accessible,dot1dStaticAddress:dot1dStaticReceivePort,current,,Filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.5.1.1.1,BRIDGE-MIB::dot1dStaticAddress,OCTET,read-create,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object can take the value of a unicast address, a group address, or the broadcast address.
.1.3.6.1.2.1.17.5.1.1.2,BRIDGE-MIB::dot1dStaticReceivePort,Integer32,read-create,,current,,Either the value '0', or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.
.1.3.6.1.2.1.17.5.1.1.3,BRIDGE-MIB::dot1dStaticAllowedToGoTo,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific MAC address, are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the bridge is represented by a single bit within the value of this object. If that bit has a value of '1', then that port is included in the set of ports; the port is not included if its bit has a value of '0'. (Note that the setting of the bit corresponding to the port from which a frame is received is irrelevant.) The default value of this object is a string of ones of appropriate length. The value of this object may exceed the required minimum maximum message size of some SNMP transport (484 bytes, in the case of SNMP over UDP, see RFC 3417, section 3.2). SNMP engines on bridges supporting a large number of ports must support appropriate maximum message sizes.
.1.3.6.1.2.1.17.5.1.1.4,BRIDGE-MIB::dot1dStaticStatus,INTEGER,read-create,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. The default value is permanent(3). other(1) - this entry is currently in use but the conditions under which it will remain so are different from each of the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out.
.1.3.6.1.2.1.17.6,P-BRIDGE-MIB::pBridgeMIB,,,,,,The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998, including Restricted Group Registration defined by IEEE 802.1t-2001. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4363; See the RFC itself for full legal notices.
.1.3.6.1.2.1.17.6.1,P-BRIDGE-MIB::pBridgeMIBObjects,,,,,,
.1.3.6.1.2.1.17.6.1.1,P-BRIDGE-MIB::dot1dExtBase,,,,,,
.1.3.6.1.2.1.17.6.1.1.1,P-BRIDGE-MIB::dot1dDeviceCapabilities,BITS,read-only,,current,dot1dExtendedFilteringServices(0):dot1dTrafficClasses(1):dot1qStaticEntryIndividualPort(2):dot1qIVLCapable(3):dot1qSVLCapable(4):dot1qHybridCapable(5):dot1qConfigurablePvidTagging(6):dot1dLocalVlanCapable(7),Indicates the optional parts of IEEE 802.1D and 802.1Q that are implemented by this device and are manageable through this MIB. Capabilities that are allowed on a per-port basis are indicated in dot1dPortCapabilities. dot1dExtendedFilteringServices(0), -- can perform filtering of -- individual multicast addresses -- controlled by GMRP. dot1dTrafficClasses(1), -- can map user priority to -- multiple traffic classes. dot1qStaticEntryIndividualPort(2), -- dot1qStaticUnicastReceivePort & -- dot1qStaticMulticastReceivePort -- can represent non-zero entries. dot1qIVLCapable(3), -- Independent VLAN Learning (IVL). dot1qSVLCapable(4), -- Shared VLAN Learning (SVL). dot1qHybridCapable(5), -- both IVL & SVL simultaneously. dot1qConfigurablePvidTagging(6), -- whether the implementation -- supports the ability to -- override the default PVID -- setting and its egress status -- (VLAN-Tagged or Untagged) on -- each port. dot1dLocalVlanCapable(7) -- can support multiple local -- bridges, outside of the scope -- of 802.1Q defined VLANs.
.1.3.6.1.2.1.17.6.1.1.2,P-BRIDGE-MIB::dot1dTrafficClassesEnabled,INTEGER,read-write,,current,true(1):false(2),The value true(1) indicates that Traffic Classes are enabled on this bridge. When false(2), the bridge operates with a single priority level for all traffic. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.1.3,P-BRIDGE-MIB::dot1dGmrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status requested by management for GMRP. The value enabled(1) indicates that GMRP should be enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When disabled(2), GMRP is disabled, in all VLANs and on all ports, and all GMRP packets will be forwarded transparently. This object affects both Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.1.4,P-BRIDGE-MIB::dot1dPortCapabilitiesTable,,not-accessible,,current,,A table that contains capabilities information about every port that is associated with this bridge.
.1.3.6.1.2.1.17.6.1.1.4.1,P-BRIDGE-MIB::dot1dPortCapabilitiesEntry,,not-accessible,,current,,A set of capabilities information about this port indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.1.4.1.1,P-BRIDGE-MIB::dot1dPortCapabilities,BITS,read-only,,current,dot1qDot1qTagging(0):dot1qConfigurableAcceptableFrameTypes(1):dot1qIngressFiltering(2),Indicates the parts of IEEE 802.1D and 802.1Q that are optional on a per-port basis, that are implemented by this device, and that are manageable through this MIB. dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of -- frames and GVRP. dot1qConfigurableAcceptableFrameTypes(1), -- allows modified values of -- dot1qPortAcceptableFrameTypes. dot1qIngressFiltering(2) -- supports the discarding of any -- frame received on a Port whose -- VLAN classification does not -- include that Port in its Member -- set.
.1.3.6.1.2.1.17.6.1.2,P-BRIDGE-MIB::dot1dPriority,,,,,,
.1.3.6.1.2.1.17.6.1.2.1,P-BRIDGE-MIB::dot1dPortPriorityTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.6.1.2.1.1,P-BRIDGE-MIB::dot1dPortPriorityEntry,,not-accessible,,current,,A list of Default User Priorities for each port of a transparent bridge. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.2.1.1.1,P-BRIDGE-MIB::dot1dPortDefaultUserPriority,Integer32,read-write,,current,,The default ingress User Priority for this port. This only has effect on media, such as Ethernet, that do not support native User Priority. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.1.1.2,P-BRIDGE-MIB::dot1dPortNumTrafficClasses,Integer32,read-write,,current,,The number of egress traffic classes supported on this port. This object may optionally be read-only. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.2,P-BRIDGE-MIB::dot1dUserPriorityRegenTable,,not-accessible,,current,,A list of Regenerated User Priorities for each received User Priority on each port of a bridge. The Regenerated User Priority value may be used to index the Traffic Class Table for each input port. This only has effect on media that support native User Priority. The default values for Regenerated User Priorities are the same as the User Priorities.
.1.3.6.1.2.1.17.6.1.2.2.1,P-BRIDGE-MIB::dot1dUserPriorityRegenEntry,,not-accessible,dot1dBasePort:dot1dUserPriority,current,,A mapping of incoming User Priority to a Regenerated User Priority.
.1.3.6.1.2.1.17.6.1.2.2.1.1,P-BRIDGE-MIB::dot1dUserPriority,Integer32,not-accessible,,current,,The User Priority for a frame received on this port.
.1.3.6.1.2.1.17.6.1.2.2.1.2,P-BRIDGE-MIB::dot1dRegenUserPriority,Integer32,read-write,,current,,The Regenerated User Priority that the incoming User Priority is mapped to for this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.3,P-BRIDGE-MIB::dot1dTrafficClassTable,,not-accessible,,current,,A table mapping evaluated User Priority to Traffic Class, for forwarding by the bridge. Traffic class is a number in the range (0..(dot1dPortNumTrafficClasses-1)).
.1.3.6.1.2.1.17.6.1.2.3.1,P-BRIDGE-MIB::dot1dTrafficClassEntry,,not-accessible,dot1dBasePort:dot1dTrafficClassPriority,current,,User Priority to Traffic Class mapping.
.1.3.6.1.2.1.17.6.1.2.3.1.1,P-BRIDGE-MIB::dot1dTrafficClassPriority,Integer32,not-accessible,,current,,The Priority value determined for the received frame. This value is equivalent to the priority indicated in the tagged frame received, or one of the evaluated priorities, determined according to the media-type. For untagged frames received from Ethernet media, this value is equal to the dot1dPortDefaultUserPriority value for the ingress port. For untagged frames received from non-Ethernet media, this value is equal to the dot1dRegenUserPriority value for the ingress port and media-specific user priority.
.1.3.6.1.2.1.17.6.1.2.3.1.2,P-BRIDGE-MIB::dot1dTrafficClass,Integer32,read-write,,current,,The Traffic Class the received frame is mapped to. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.4,P-BRIDGE-MIB::dot1dPortOutboundAccessPriorityTable,,not-accessible,,current,,A table mapping Regenerated User Priority to Outbound Access Priority. This is a fixed mapping for all port types, with two options for 802.5 Token Ring.
.1.3.6.1.2.1.17.6.1.2.4.1,P-BRIDGE-MIB::dot1dPortOutboundAccessPriorityEntry,,not-accessible,dot1dBasePort:dot1dRegenUserPriority,current,,Regenerated User Priority to Outbound Access Priority mapping.
.1.3.6.1.2.1.17.6.1.2.4.1.1,P-BRIDGE-MIB::dot1dPortOutboundAccessPriority,Integer32,read-only,,current,,The Outbound Access Priority the received frame is mapped to.
.1.3.6.1.2.1.17.6.1.3,P-BRIDGE-MIB::dot1dGarp,,,,,,
.1.3.6.1.2.1.17.6.1.3.1,P-BRIDGE-MIB::dot1dPortGarpTable,,not-accessible,,current,,A table of GARP control information about every bridge port. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.3.1.1,P-BRIDGE-MIB::dot1dPortGarpEntry,,not-accessible,,current,,GARP control information for a bridge port.
.1.3.6.1.2.1.17.6.1.3.1.1.1,P-BRIDGE-MIB::dot1dPortGarpJoinTime,INTEGER,read-write,,current,,The GARP Join time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.3.1.1.2,P-BRIDGE-MIB::dot1dPortGarpLeaveTime,INTEGER,read-write,,current,,The GARP Leave time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.3.1.1.3,P-BRIDGE-MIB::dot1dPortGarpLeaveAllTime,INTEGER,read-write,,current,,The GARP LeaveAll time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.4,P-BRIDGE-MIB::dot1dGmrp,,,,,,
.1.3.6.1.2.1.17.6.1.4.1,P-BRIDGE-MIB::dot1dPortGmrpTable,,not-accessible,,current,,A table of GMRP control and status information about every bridge port. Augments the dot1dBasePortTable.
.1.3.6.1.2.1.17.6.1.4.1.1,P-BRIDGE-MIB::dot1dPortGmrpEntry,,not-accessible,,current,,GMRP control and status information for a bridge port.
.1.3.6.1.2.1.17.6.1.4.1.1.1,P-BRIDGE-MIB::dot1dPortGmrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative state of GMRP operation on this port. The value enabled(1) indicates that GMRP is enabled on this port in all VLANs as long as dot1dGmrpStatus is also enabled(1). A value of disabled(2) indicates that GMRP is disabled on this port in all VLANs: any GMRP packets received will be silently discarded, and no GMRP registrations will be propagated from other ports. Setting this to a value of enabled(1) will be stored by the agent but will only take effect on the GMRP protocol operation if dot1dGmrpStatus also indicates the value enabled(1). This object affects all GMRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.4.1.1.2,P-BRIDGE-MIB::dot1dPortGmrpFailedRegistrations,Counter32,read-only,,current,,The total number of failed GMRP registrations, for any reason, in all VLANs, on this port.
.1.3.6.1.2.1.17.6.1.4.1.1.3,P-BRIDGE-MIB::dot1dPortGmrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last GMRP message received on this port.
.1.3.6.1.2.1.17.6.1.4.1.1.4,P-BRIDGE-MIB::dot1dPortRestrictedGroupRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted Group Registration on this port. If the value of this control is true(1), then creation of a new dynamic entry is permitted only if there is a Static Filtering Entry for the VLAN concerned, in which the Registrar Administrative Control value is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.2,P-BRIDGE-MIB::pBridgeConformance,,,,,,
.1.3.6.1.2.1.17.6.2.1,P-BRIDGE-MIB::pBridgeGroups,,,,,,
.1.3.6.1.2.1.17.6.2.1.1,P-BRIDGE-MIB::pBridgeExtCapGroup,,,,,,A collection of objects indicating the optional capabilities of the device.
.1.3.6.1.2.1.17.6.2.1.2,P-BRIDGE-MIB::pBridgeDeviceGmrpGroup,,,,,,A collection of objects providing device-level control for the Multicast Filtering extended bridge services.
.1.3.6.1.2.1.17.6.2.1.3,P-BRIDGE-MIB::pBridgeDevicePriorityGroup,,,,,,A collection of objects providing device-level control for the Priority services.
.1.3.6.1.2.1.17.6.2.1.4,P-BRIDGE-MIB::pBridgeDefaultPriorityGroup,,,,,,A collection of objects defining the User Priority applicable to each port for media that do not support native User Priority.
.1.3.6.1.2.1.17.6.2.1.5,P-BRIDGE-MIB::pBridgeRegenPriorityGroup,,,,,,A collection of objects defining the User Priorities applicable to each port for media that support native User Priority.
.1.3.6.1.2.1.17.6.2.1.6,P-BRIDGE-MIB::pBridgePriorityGroup,,,,,,A collection of objects defining the traffic classes within a bridge for each evaluated User Priority.
.1.3.6.1.2.1.17.6.2.1.7,P-BRIDGE-MIB::pBridgeAccessPriorityGroup,,,,,,A collection of objects defining the media-dependent outbound access level for each priority.
.1.3.6.1.2.1.17.6.2.1.8,P-BRIDGE-MIB::pBridgePortGarpGroup,,,,,,A collection of objects providing port level control and status information for GARP operation.
.1.3.6.1.2.1.17.6.2.1.9,P-BRIDGE-MIB::pBridgePortGmrpGroup,,,,,,A collection of objects providing port level control and status information for GMRP operation.
.1.3.6.1.2.1.17.6.2.1.10,P-BRIDGE-MIB::pBridgeHCPortGroup,,,,,,A collection of objects providing 64-bit statistics counters for high-capacity bridge ports.
.1.3.6.1.2.1.17.6.2.1.11,P-BRIDGE-MIB::pBridgePortOverflowGroup,,,,,,A collection of objects providing overflow statistics counters for high-capacity bridge ports.
.1.3.6.1.2.1.17.6.2.1.12,P-BRIDGE-MIB::pBridgePortGmrpGroup2,,,,,,A collection of objects providing port level control and status information for GMRP operation.
.1.3.6.1.2.1.17.6.2.2,P-BRIDGE-MIB::pBridgeCompliances,,,,,,
.1.3.6.1.2.1.17.6.2.2.1,P-BRIDGE-MIB::pBridgeCompliance,,,,,,The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
.1.3.6.1.2.1.17.6.2.2.2,P-BRIDGE-MIB::pBridgeCompliance2,,,,,,The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
.1.3.6.1.2.1.17.7,Q-BRIDGE-MIB::qBridgeMIB,,,,,,The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q-2003, including Restricted Vlan Registration defined by IEEE 802.1u-2001 and Vlan Classification defined by IEEE 802.1v-2001. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4363; See the RFC itself for full legal notices.
.1.3.6.1.2.1.17.7.1,Q-BRIDGE-MIB::qBridgeMIBObjects,,,,,,
.1.3.6.1.2.1.17.7.1.1,Q-BRIDGE-MIB::dot1qBase,,,,,,
.1.3.6.1.2.1.17.7.1.1.1,Q-BRIDGE-MIB::dot1qVlanVersionNumber,INTEGER,read-only,,current,version1(1),The version number of IEEE 802.1Q that this device supports.
.1.3.6.1.2.1.17.7.1.1.2,Q-BRIDGE-MIB::dot1qMaxVlanId,Integer32,read-only,,current,,The maximum IEEE 802.1Q VLAN-ID that this device supports.
.1.3.6.1.2.1.17.7.1.1.3,Q-BRIDGE-MIB::dot1qMaxSupportedVlans,Unsigned32,read-only,,current,,The maximum number of IEEE 802.1Q VLANs that this device supports.
.1.3.6.1.2.1.17.7.1.1.4,Q-BRIDGE-MIB::dot1qNumVlans,Unsigned32,read-only,,current,,The current number of IEEE 802.1Q VLANs that are configured in this device.
.1.3.6.1.2.1.17.7.1.1.5,Q-BRIDGE-MIB::dot1qGvrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status requested by management for GVRP. The value enabled(1) indicates that GVRP should be enabled on this device, on all ports for which it has not been specifically disabled. When disabled(2), GVRP is disabled on all ports, and all GVRP packets will be forwarded transparently. This object affects all GVRP Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2,Q-BRIDGE-MIB::dot1qTp,,,,,,
.1.3.6.1.2.1.17.7.1.2.1,Q-BRIDGE-MIB::dot1qFdbTable,,not-accessible,,current,,A table that contains configuration and control information for each Filtering Database currently operating on this device. Entries in this table appear automatically when VLANs are assigned FDB IDs in the dot1qVlanCurrentTable.
.1.3.6.1.2.1.17.7.1.2.1.1,Q-BRIDGE-MIB::dot1qFdbEntry,,not-accessible,dot1qFdbId,current,,Information about a specific Filtering Database.
.1.3.6.1.2.1.17.7.1.2.1.1.1,Q-BRIDGE-MIB::dot1qFdbId,Unsigned32,not-accessible,,current,,The identity of this Filtering Database.
.1.3.6.1.2.1.17.7.1.2.1.1.2,Q-BRIDGE-MIB::dot1qFdbDynamicCount,Counter32,read-only,,current,,The current number of dynamic entries in this Filtering Database.
.1.3.6.1.2.1.17.7.1.2.2,Q-BRIDGE-MIB::dot1qTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.6.1.2.1.17.7.1.2.2.1,Q-BRIDGE-MIB::dot1qTpFdbEntry,,not-accessible,dot1qFdbId:dot1qTpFdbAddress,current,,Information about a specific unicast MAC address for which the device has some forwarding and/or filtering information.
.1.3.6.1.2.1.17.7.1.2.2.1.1,Q-BRIDGE-MIB::dot1qTpFdbAddress,OCTET,not-accessible,,current,,A unicast MAC address for which the device has forwarding and/or filtering information.
.1.3.6.1.2.1.17.7.1.2.2.1.2,Q-BRIDGE-MIB::dot1qTpFdbPort,Integer32,read-only,,current,,Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1qTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the device does have some forwarding/filtering information about this address (e.g., in the dot1qStaticUnicastTable). Implementors are encouraged to assign the port value to this object whenever it is learned, even for addresses for which the corresponding value of dot1qTpFdbStatus is not learned(3).
.1.3.6.1.2.1.17.7.1.2.2.1.3,Q-BRIDGE-MIB::dot1qTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the values are: other(1) - none of the following. This may include the case where some other MIB object (not the corresponding instance of dot1qTpFdbPort, nor an entry in the dot1qStaticUnicastTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1qTpFdbAddress are being forwarded. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out), but has not yet been flushed from the table. learned(3) - the value of the corresponding instance of dot1qTpFdbPort was learned and is being used. self(4) - the value of the corresponding instance of dot1qTpFdbAddress represents one of the device's addresses. The corresponding instance of dot1qTpFdbPort indicates which of the device's ports has this address. mgmt(5) - the value of the corresponding instance of dot1qTpFdbAddress is also the value of an existing instance of dot1qStaticAddress.
.1.3.6.1.2.1.17.7.1.2.3,Q-BRIDGE-MIB::dot1qTpGroupTable,,not-accessible,,current,,A table containing filtering information for VLANs configured into the bridge by (local or network) management, or learned dynamically, specifying the set of ports to which frames received on a VLAN for this FDB and containing a specific Group destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.2.3.1,Q-BRIDGE-MIB::dot1qTpGroupEntry,,not-accessible,dot1qVlanIndex:dot1qTpGroupAddress,current,,Filtering information configured into the bridge by management, or learned dynamically, specifying the set of ports to which frames received on a VLAN and containing a specific Group destination address are allowed to be forwarded. The subset of these ports learned dynamically is also provided.
.1.3.6.1.2.1.17.7.1.2.3.1.1,Q-BRIDGE-MIB::dot1qTpGroupAddress,OCTET,not-accessible,,current,,The destination Group MAC address in a frame to which this entry's filtering information applies.
.1.3.6.1.2.1.17.7.1.2.3.1.2,Q-BRIDGE-MIB::dot1qTpGroupEgressPorts,OCTET,read-only,,current,,The complete set of ports, in this VLAN, to which frames destined for this Group MAC address are currently being explicitly forwarded. This does not include ports for which this address is only implicitly forwarded, in the dot1qForwardAllPorts list.
.1.3.6.1.2.1.17.7.1.2.3.1.3,Q-BRIDGE-MIB::dot1qTpGroupLearnt,OCTET,read-only,,current,,The subset of ports in dot1qTpGroupEgressPorts that were learned by GMRP or some other dynamic mechanism, in this Filtering database.
.1.3.6.1.2.1.17.7.1.2.4,Q-BRIDGE-MIB::dot1qForwardAllTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of all multicasts applies, configured statically by management or dynamically by GMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.6.1.2.1.17.7.1.2.4.1,Q-BRIDGE-MIB::dot1qForwardAllEntry,,not-accessible,dot1qVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts should be forwarded, configured statically by management or dynamically by GMRP.
.1.3.6.1.2.1.17.7.1.2.4.1.1,Q-BRIDGE-MIB::dot1qForwardAllPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which all multicast group-addressed frames are to be forwarded. This includes ports for which this need has been determined dynamically by GMRP, or configured statically by management.
.1.3.6.1.2.1.17.7.1.2.4.1.2,Q-BRIDGE-MIB::dot1qForwardAllStaticPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN to which all multicast group-addressed frames are to be forwarded. Ports entered in this list will also appear in the complete set shown by dot1qForwardAllPorts. This value will be restored after the device is reset. This only applies to ports that are members of the VLAN, defined by dot1qVlanCurrentEgressPorts. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardAllForbiddenPorts. The default value is a string of ones of appropriate length, to indicate the standard behaviour of using basic filtering services, i.e., forward all multicasts to all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.4.1.3,Q-BRIDGE-MIB::dot1qForwardAllForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward All Multicast Groups may not be dynamically registered by GMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardAllStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.5,Q-BRIDGE-MIB::dot1qForwardUnregisteredTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of multicast group-addressed frames for which no more specific forwarding information applies. This is configured statically by management and determined dynamically by GMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.6.1.2.1.17.7.1.2.5.1,Q-BRIDGE-MIB::dot1qForwardUnregisteredEntry,,not-accessible,dot1qVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts for which there is no more specific forwarding information shall be forwarded. This is configured statically by management or dynamically by GMRP.
.1.3.6.1.2.1.17.7.1.2.5.1.1,Q-BRIDGE-MIB::dot1qForwardUnregisteredPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which multicast group-addressed frames for which there is no more specific forwarding information will be forwarded. This includes ports for which this need has been determined dynamically by GMRP, or configured statically by management.
.1.3.6.1.2.1.17.7.1.2.5.1.2,Q-BRIDGE-MIB::dot1qForwardUnregisteredStaticPorts,OCTET,read-write,,current,,The set of ports configured by management, in this VLAN, to which multicast group-addressed frames for which there is no more specific forwarding information are to be forwarded. Ports entered in this list will also appear in the complete set shown by dot1qForwardUnregisteredPorts. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardUnregisteredForbiddenPorts. The default value is a string of zeros of appropriate length, although this has no effect with the default value of dot1qForwardAllStaticPorts. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.5.1.3,Q-BRIDGE-MIB::dot1qForwardUnregisteredForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward Unregistered Multicast Groups may not be dynamically registered by GMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardUnregisteredStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3,Q-BRIDGE-MIB::dot1qStatic,,,,,,
.1.3.6.1.2.1.17.7.1.3.1,Q-BRIDGE-MIB::dot1qStaticUnicastTable,,not-accessible,,current,,A table containing filtering information for Unicast MAC addresses for each Filtering Database, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific unicast destination addresses are allowed to be forwarded. A value of zero in this table (as the port number from which frames with a specific destination address are received) is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast addresses only.
.1.3.6.1.2.1.17.7.1.3.1.1,Q-BRIDGE-MIB::dot1qStaticUnicastEntry,,not-accessible,dot1qFdbId:dot1qStaticUnicastAddress:dot1qStaticUnicastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific unicast destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.3.1.1.1,Q-BRIDGE-MIB::dot1qStaticUnicastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a unicast address.
.1.3.6.1.2.1.17.7.1.3.1.1.2,Q-BRIDGE-MIB::dot1qStaticUnicastReceivePort,Integer32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry.
.1.3.6.1.2.1.17.7.1.3.1.1.3,Q-BRIDGE-MIB::dot1qStaticUnicastAllowedToGoTo,OCTET,read-write,,current,,The set of ports for which a frame with a specific unicast address will be flooded in the event that it has not been learned. It also specifies the set of ports on which a specific unicast address may be dynamically learned. The dot1qTpFdbTable will have an equivalent entry with a dot1qTpFdbPort value of '0' until this address has been learned, at which point it will be updated with the port the address has been seen on. This only applies to ports that are members of the VLAN, defined by dot1qVlanCurrentEgressPorts. The default value of this object is a string of ones of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.1.1.4,Q-BRIDGE-MIB::dot1qStaticUnicastStatus,INTEGER,read-write,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2,Q-BRIDGE-MIB::dot1qStaticMulticastTable,,not-accessible,,current,,A table containing filtering information for Multicast and Broadcast MAC addresses for each VLAN, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific Multicast and Broadcast destination addresses are allowed to be forwarded. A value of zero in this table (as the port number from which frames with a specific destination address are received) is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for Multicast and Broadcast addresses only.
.1.3.6.1.2.1.17.7.1.3.2.1,Q-BRIDGE-MIB::dot1qStaticMulticastEntry,,not-accessible,dot1qVlanIndex:dot1qStaticMulticastAddress:dot1qStaticMulticastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from this specific port for this VLAN and containing this Multicast or Broadcast destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.3.2.1.1,Q-BRIDGE-MIB::dot1qStaticMulticastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a Multicast or Broadcast address.
.1.3.6.1.2.1.17.7.1.3.2.1.2,Q-BRIDGE-MIB::dot1qStaticMulticastReceivePort,Integer32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry.
.1.3.6.1.2.1.17.7.1.3.2.1.3,Q-BRIDGE-MIB::dot1qStaticMulticastStaticEgressPorts,OCTET,read-write,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must be forwarded, regardless of any dynamic information, e.g., from GMRP. A port may not be added in this set if it is already a member of the set of ports in dot1qStaticMulticastForbiddenEgressPorts. The default value of this object is a string of ones of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2.1.4,Q-BRIDGE-MIB::dot1qStaticMulticastForbiddenEgressPorts,OCTET,read-write,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must not be forwarded, regardless of any dynamic information, e.g., from GMRP. A port may not be added in this set if it is already a member of the set of ports in dot1qStaticMulticastStaticEgressPorts. The default value of this object is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2.1.5,Q-BRIDGE-MIB::dot1qStaticMulticastStatus,INTEGER,read-write,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4,Q-BRIDGE-MIB::dot1qVlan,,,,,,
.1.3.6.1.2.1.17.7.1.4.1,Q-BRIDGE-MIB::dot1qVlanNumDeletes,Counter32,read-only,,current,,The number of times a VLAN entry has been deleted from the dot1qVlanCurrentTable (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2.
.1.3.6.1.2.1.17.7.1.4.2,Q-BRIDGE-MIB::dot1qVlanCurrentTable,,not-accessible,,current,,A table containing current configuration information for each VLAN currently configured into the device by (local or network) management, or dynamically created as a result of GVRP requests received.
.1.3.6.1.2.1.17.7.1.4.2.1,Q-BRIDGE-MIB::dot1qVlanCurrentEntry,,not-accessible,dot1qVlanTimeMark:dot1qVlanIndex,current,,Information for a VLAN configured into the device by (local or network) management, or dynamically created as a result of GVRP requests received.
.1.3.6.1.2.1.17.7.1.4.2.1.1,Q-BRIDGE-MIB::dot1qVlanTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.17.7.1.4.2.1.2,Q-BRIDGE-MIB::dot1qVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.6.1.2.1.17.7.1.4.2.1.3,Q-BRIDGE-MIB::dot1qVlanFdbId,Unsigned32,read-only,,current,,The Filtering Database used by this VLAN. This is one of the dot1qFdbId values in the dot1qFdbTable. This value is allocated automatically by the device whenever the VLAN is created: either dynamically by GVRP, or by management, in dot1qVlanStaticTable. Allocation of this value follows the learning constraints defined for this VLAN in dot1qLearningConstraintsTable.
.1.3.6.1.2.1.17.7.1.4.2.1.4,Q-BRIDGE-MIB::dot1qVlanCurrentEgressPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as either tagged or untagged frames.
.1.3.6.1.2.1.17.7.1.4.2.1.5,Q-BRIDGE-MIB::dot1qVlanCurrentUntaggedPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as untagged frames.
.1.3.6.1.2.1.17.7.1.4.2.1.6,Q-BRIDGE-MIB::dot1qVlanStatus,INTEGER,read-only,,current,other(1):permanent(2):dynamicGvrp(3),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. permanent(2) - this entry, corresponding to an entry in dot1qVlanStaticTable, is currently in use and will remain so after the next reset of the device. The port lists for this entry include ports from the equivalent dot1qVlanStaticTable entry and ports learned dynamically. dynamicGvrp(3) - this entry is currently in use and will remain so until removed by GVRP. There is no static entry for this VLAN, and it will be removed when the last port leaves the VLAN.
.1.3.6.1.2.1.17.7.1.4.2.1.7,Q-BRIDGE-MIB::dot1qVlanCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime when this VLAN was created.
.1.3.6.1.2.1.17.7.1.4.3,Q-BRIDGE-MIB::dot1qVlanStaticTable,,not-accessible,,current,,A table containing static configuration information for each VLAN configured into the device by (local or network) management. All entries are permanent and will be restored after the device is reset.
.1.3.6.1.2.1.17.7.1.4.3.1,Q-BRIDGE-MIB::dot1qVlanStaticEntry,,not-accessible,dot1qVlanIndex,current,,Static information for a VLAN configured into the device by (local or network) management.
.1.3.6.1.2.1.17.7.1.4.3.1.1,Q-BRIDGE-MIB::dot1qVlanStaticName,OCTET,read-create,,current,,An administratively assigned string, which may be used to identify the VLAN.
.1.3.6.1.2.1.17.7.1.4.3.1.2,Q-BRIDGE-MIB::dot1qVlanStaticEgressPorts,OCTET,read-create,,current,,The set of ports that are permanently assigned to the egress list for this VLAN by management. Changes to a bit in this object affect the per-port, per-VLAN Registrar control for Registration Fixed for the relevant GVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in dot1qVlanForbiddenEgressPorts. The default value of this object is a string of zeros of appropriate length, indicating not fixed.
.1.3.6.1.2.1.17.7.1.4.3.1.3,Q-BRIDGE-MIB::dot1qVlanForbiddenEgressPorts,OCTET,read-create,,current,,The set of ports that are prohibited by management from being included in the egress list for this VLAN. Changes to this object that cause a port to be included or excluded affect the per-port, per-VLAN Registrar control for Registration Forbidden for the relevant GVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in dot1qVlanStaticEgressPorts. The default value of this object is a string of zeros of appropriate length, excluding all ports from the forbidden set.
.1.3.6.1.2.1.17.7.1.4.3.1.4,Q-BRIDGE-MIB::dot1qVlanStaticUntaggedPorts,OCTET,read-create,,current,,The set of ports that should transmit egress packets for this VLAN as untagged. The default value of this object for the default VLAN (dot1qVlanIndex = 1) is a string of appropriate length including all ports. There is no specified default for other VLANs. If a device agent cannot support the set of ports being set, then it will reject the set operation with an error. For example, a manager might attempt to set more than one VLAN to be untagged on egress where the device does not support this IEEE 802.1Q option.
.1.3.6.1.2.1.17.7.1.4.3.1.5,Q-BRIDGE-MIB::dot1qVlanStaticRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.1.4.4,Q-BRIDGE-MIB::dot1qNextFreeLocalVlanIndex,Integer32,read-only,,current,,The next available value for dot1qVlanIndex of a local VLAN entry in dot1qVlanStaticTable. This will report values >=4096 if a new Local VLAN may be created or else the value 0 if this is not possible. A row creation operation in this table for an entry with a local VlanIndex value may fail if the current value of this object is not used as the index. Even if the value read is used, there is no guarantee that it will still be the valid index when the create operation is attempted; another manager may have already got in during the intervening time interval. In this case, dot1qNextFreeLocalVlanIndex should be re-read and the creation re-tried with the new value. This value will automatically change when the current value is used to create a new row.
.1.3.6.1.2.1.17.7.1.4.5,Q-BRIDGE-MIB::dot1qPortVlanTable,,not-accessible,,current,,A table containing per-port control and status information for VLAN configuration in the device.
.1.3.6.1.2.1.17.7.1.4.5.1,Q-BRIDGE-MIB::dot1qPortVlanEntry,,not-accessible,,current,,Information controlling VLAN configuration for a port on the device. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.7.1.4.5.1.1,Q-BRIDGE-MIB::dot1qPvid,Unsigned32,read-write,,current,,The PVID, the VLAN-ID assigned to untagged frames or Priority-Tagged frames received on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.2,Q-BRIDGE-MIB::dot1qPortAcceptableFrameTypes,INTEGER,read-write,,current,admitAll(1):admitOnlyVlanTagged(2),When this is admitOnlyVlanTagged(2), the device will discard untagged frames or Priority-Tagged frames received on this port. When admitAll(1), untagged frames or Priority-Tagged frames received on this port will be accepted and assigned to a VID based on the PVID and VID Set for this port. This control does not affect VLAN-independent Bridge Protocol Data Unit (BPDU) frames, such as GVRP and Spanning Tree Protocol (STP). It does affect VLAN- dependent BPDU frames, such as GMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.3,Q-BRIDGE-MIB::dot1qPortIngressFiltering,INTEGER,read-write,,current,true(1):false(2),When this is true(1), the device will discard incoming frames for VLANs that do not include this Port in its Member set. When false(2), the port will accept all incoming frames. This control does not affect VLAN-independent BPDU frames, such as GVRP and STP. It does affect VLAN- dependent BPDU frames, such as GMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.4,Q-BRIDGE-MIB::dot1qPortGvrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The state of GVRP operation on this port. The value enabled(1) indicates that GVRP is enabled on this port, as long as dot1qGvrpStatus is also enabled for this device. When disabled(2) but dot1qGvrpStatus is still enabled for the device, GVRP is disabled on this port: any GVRP packets received will be silently discarded, and no GVRP registrations will be propagated from other ports. This object affects all GVRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.5,Q-BRIDGE-MIB::dot1qPortGvrpFailedRegistrations,Counter32,read-only,,current,,The total number of failed GVRP registrations, for any reason, on this port.
.1.3.6.1.2.1.17.7.1.4.5.1.6,Q-BRIDGE-MIB::dot1qPortGvrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last GVRP message received on this port.
.1.3.6.1.2.1.17.7.1.4.5.1.7,Q-BRIDGE-MIB::dot1qPortRestrictedVlanRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted VLAN Registration on this port. If the value of this control is true(1), then creation of a new dynamic VLAN entry is permitted only if there is a Static VLAN Registration Entry for the VLAN concerned, in which the Registrar Administrative Control value for this port is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.6,Q-BRIDGE-MIB::dot1qPortVlanStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high-capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification.
.1.3.6.1.2.1.17.7.1.4.6.1,Q-BRIDGE-MIB::dot1qPortVlanStatisticsEntry,,not-accessible,dot1dBasePort:dot1qVlanIndex,current,,Traffic statistics for a VLAN on an interface.
.1.3.6.1.2.1.17.7.1.4.6.1.1,Q-BRIDGE-MIB::dot1qTpVlanPortInFrames,Counter32,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN. Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by the local forwarding process for this VLAN. This object includes received bridge management frames classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP.
.1.3.6.1.2.1.17.7.1.4.6.1.2,Q-BRIDGE-MIB::dot1qTpVlanPortOutFrames,Counter32,read-only,,current,,The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This includes bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.6.1.3,Q-BRIDGE-MIB::dot1qTpVlanPortInDiscards,Counter32,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering.
.1.3.6.1.2.1.17.7.1.4.6.1.4,Q-BRIDGE-MIB::dot1qTpVlanPortInOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortInFrames counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.6.1.5,Q-BRIDGE-MIB::dot1qTpVlanPortOutOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortOutFrames counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.6.1.6,Q-BRIDGE-MIB::dot1qTpVlanPortInOverflowDiscards,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortInDiscards counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.7,Q-BRIDGE-MIB::dot1qPortVlanHCStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VLAN statistics for traffic on high-capacity interfaces.
.1.3.6.1.2.1.17.7.1.4.7.1,Q-BRIDGE-MIB::dot1qPortVlanHCStatisticsEntry,,not-accessible,dot1dBasePort:dot1qVlanIndex,current,,Traffic statistics for a VLAN on a high-capacity interface.
.1.3.6.1.2.1.17.7.1.4.7.1.1,Q-BRIDGE-MIB::dot1qTpVlanPortHCInFrames,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN. Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by the local forwarding process for this VLAN. This object includes received bridge management frames classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.7.1.2,Q-BRIDGE-MIB::dot1qTpVlanPortHCOutFrames,Counter64,read-only,,current,,The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This includes bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.7.1.3,Q-BRIDGE-MIB::dot1qTpVlanPortHCInDiscards,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering.
.1.3.6.1.2.1.17.7.1.4.8,Q-BRIDGE-MIB::dot1qLearningConstraintsTable,,not-accessible,,current,,A table containing learning constraints for sets of Shared and Independent VLANs.
.1.3.6.1.2.1.17.7.1.4.8.1,Q-BRIDGE-MIB::dot1qLearningConstraintsEntry,,not-accessible,dot1qConstraintVlan:dot1qConstraintSet,current,,A learning constraint defined for a VLAN.
.1.3.6.1.2.1.17.7.1.4.8.1.1,Q-BRIDGE-MIB::dot1qConstraintVlan,Unsigned32,not-accessible,,current,,The index of the row in dot1qVlanCurrentTable for the VLAN constrained by this entry.
.1.3.6.1.2.1.17.7.1.4.8.1.2,Q-BRIDGE-MIB::dot1qConstraintSet,Integer32,not-accessible,,current,,The identity of the constraint set to which dot1qConstraintVlan belongs. These values may be chosen by the management station.
.1.3.6.1.2.1.17.7.1.4.8.1.3,Q-BRIDGE-MIB::dot1qConstraintType,INTEGER,read-create,,current,independent(1):shared(2),The type of constraint this entry defines. independent(1) - the VLAN, dot1qConstraintVlan, uses a filtering database independent from all other VLANs in the same set, defined by dot1qConstraintSet. shared(2) - the VLAN, dot1qConstraintVlan, shares the same filtering database as all other VLANs in the same set, defined by dot1qConstraintSet.
.1.3.6.1.2.1.17.7.1.4.8.1.4,Q-BRIDGE-MIB::dot1qConstraintStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry.
.1.3.6.1.2.1.17.7.1.4.9,Q-BRIDGE-MIB::dot1qConstraintSetDefault,Integer32,read-write,,current,,The identity of the constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in dot1qLearningConstraintsTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.10,Q-BRIDGE-MIB::dot1qConstraintTypeDefault,INTEGER,read-write,,current,independent(1):shared(2),The type of constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in dot1qLearningConstraintsTable. The types are as defined for dot1qConstraintType. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.5,Q-BRIDGE-MIB::dot1vProtocol,,,,,,
.1.3.6.1.2.1.17.7.1.5.1,Q-BRIDGE-MIB::dot1vProtocolGroupTable,,not-accessible,,current,,A table that contains mappings from Protocol Templates to Protocol Group Identifiers used for Port-and-Protocol-based VLAN Classification.
.1.3.6.1.2.1.17.7.1.5.1.1,Q-BRIDGE-MIB::dot1vProtocolGroupEntry,,not-accessible,dot1vProtocolTemplateFrameType:dot1vProtocolTemplateProtocolValue,current,,A mapping from a Protocol Template to a Protocol Group Identifier.
.1.3.6.1.2.1.17.7.1.5.1.1.1,Q-BRIDGE-MIB::dot1vProtocolTemplateFrameType,INTEGER,not-accessible,,current,ethernet(1):rfc1042(2):snap8021H(3):snapOther(4):llcOther(5),The data-link encapsulation format or the 'detagged_frame_type' in a Protocol Template.
.1.3.6.1.2.1.17.7.1.5.1.1.2,Q-BRIDGE-MIB::dot1vProtocolTemplateProtocolValue,OCTET,not-accessible,,current,,The identification of the protocol above the data-link layer in a Protocol Template. Depending on the frame type, the octet string will have one of the following values: For 'ethernet', 'rfc1042' and 'snap8021H', this is the 16-bit (2-octet) IEEE 802.3 Type Field. For 'snapOther', this is the 40-bit (5-octet) PID. For 'llcOther', this is the 2-octet IEEE 802.2 Link Service Access Point (LSAP) pair: first octet for Destination Service Access Point (DSAP) and second octet for Source Service Access Point (SSAP).
.1.3.6.1.2.1.17.7.1.5.1.1.3,Q-BRIDGE-MIB::dot1vProtocolGroupId,Integer32,read-create,,current,,Represents a group of protocols that are associated together when assigning a VID to a frame.
.1.3.6.1.2.1.17.7.1.5.1.1.4,Q-BRIDGE-MIB::dot1vProtocolGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.1.5.2,Q-BRIDGE-MIB::dot1vProtocolPortTable,,not-accessible,,current,,A table that contains VID sets used for Port-and-Protocol-based VLAN Classification.
.1.3.6.1.2.1.17.7.1.5.2.1,Q-BRIDGE-MIB::dot1vProtocolPortEntry,,not-accessible,dot1dBasePort:dot1vProtocolPortGroupId,current,,A VID set for a port.
.1.3.6.1.2.1.17.7.1.5.2.1.1,Q-BRIDGE-MIB::dot1vProtocolPortGroupId,Integer32,not-accessible,,current,,Designates a group of protocols in the Protocol Group Database.
.1.3.6.1.2.1.17.7.1.5.2.1.2,Q-BRIDGE-MIB::dot1vProtocolPortGroupVid,Integer32,read-create,,current,,The VID associated with a group of protocols for each port.
.1.3.6.1.2.1.17.7.1.5.2.1.3,Q-BRIDGE-MIB::dot1vProtocolPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.2,Q-BRIDGE-MIB::qBridgeConformance,,,,,,
.1.3.6.1.2.1.17.7.2.1,Q-BRIDGE-MIB::qBridgeGroups,,,,,,
.1.3.6.1.2.1.17.7.2.1.1,Q-BRIDGE-MIB::qBridgeBaseGroup,,,,,,A collection of objects providing device-level control and status information for the Virtual LAN bridge services.
.1.3.6.1.2.1.17.7.2.1.2,Q-BRIDGE-MIB::qBridgeFdbUnicastGroup,,,,,,A collection of objects providing information about all unicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.3,Q-BRIDGE-MIB::qBridgeFdbMulticastGroup,,,,,,A collection of objects providing information about all multicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.4,Q-BRIDGE-MIB::qBridgeServiceRequirementsGroup,,,,,,A collection of objects providing information about service requirements, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.5,Q-BRIDGE-MIB::qBridgeFdbStaticGroup,,,,,,A collection of objects providing information about unicast and multicast addresses statically configured by management, in each Filtering Database or VLAN.
.1.3.6.1.2.1.17.7.2.1.6,Q-BRIDGE-MIB::qBridgeVlanGroup,,,,,,A collection of objects providing information about all VLANs currently configured on this device.
.1.3.6.1.2.1.17.7.2.1.7,Q-BRIDGE-MIB::qBridgeVlanStaticGroup,,,,,,A collection of objects providing information about VLANs statically configured by management.
.1.3.6.1.2.1.17.7.2.1.8,Q-BRIDGE-MIB::qBridgePortGroup,,,,,,A collection of objects providing port-level VLAN control and status information for all ports.
.1.3.6.1.2.1.17.7.2.1.9,Q-BRIDGE-MIB::qBridgeVlanStatisticsGroup,,,,,,A collection of objects providing per-port packet statistics for all VLANs currently configured on this device.
.1.3.6.1.2.1.17.7.2.1.10,Q-BRIDGE-MIB::qBridgeVlanStatisticsOverflowGroup,,,,,,A collection of objects providing overflow counters for per-port packet statistics for all VLANs currently configured on this device for high-capacity interfaces, defined as those that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second.
.1.3.6.1.2.1.17.7.2.1.11,Q-BRIDGE-MIB::qBridgeVlanHCStatisticsGroup,,,,,,A collection of objects providing per-port packet statistics for all VLANs currently configured on this device for high-capacity interfaces, defined as those that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second.
.1.3.6.1.2.1.17.7.2.1.12,Q-BRIDGE-MIB::qBridgeLearningConstraintsGroup,,,,,,A collection of objects defining the Filtering Database constraints all VLANs have with each other.
.1.3.6.1.2.1.17.7.2.1.13,Q-BRIDGE-MIB::qBridgeLearningConstraintDefaultGroup,,,,,,A collection of objects defining the default Filtering Database constraints for VLANs that have no specific constraints defined.
.1.3.6.1.2.1.17.7.2.1.14,Q-BRIDGE-MIB::qBridgeClassificationDeviceGroup,,,,,,VLAN classification information for the bridge.
.1.3.6.1.2.1.17.7.2.1.15,Q-BRIDGE-MIB::qBridgeClassificationPortGroup,,,,,,VLAN classification information for individual ports.
.1.3.6.1.2.1.17.7.2.1.16,Q-BRIDGE-MIB::qBridgePortGroup2,,,,,,A collection of objects providing port-level VLAN control and status information for all ports.
.1.3.6.1.2.1.17.7.2.2,Q-BRIDGE-MIB::qBridgeCompliances,,,,,,
.1.3.6.1.2.1.17.7.2.2.1,Q-BRIDGE-MIB::qBridgeCompliance,,,,,,The compliance statement for device support of Virtual LAN Bridge services. RFC2674 was silent about the expected persistence of the read-write objects in this MIB module. Applications MUST NOT assume that the values of the read-write objects are persistent across reinitializations of the management system and MUST NOT assume that the values are not persistent across reinitializations of the management system.
.1.3.6.1.2.1.17.7.2.2.2,Q-BRIDGE-MIB::qBridgeCompliance2,,,,,,The compliance statement for device support of Virtual LAN Bridge services. This document clarifies the persistence requirements for the read-write objects in this MIB module. All implementations claiming compliance to qBridgeCompliance2 MUST retain the values of those read-write objects that specify this requirement.
.1.3.6.1.2.1.17.8,BRIDGE-MIB::dot1dConformance,,,,,,
.1.3.6.1.2.1.17.8.1,BRIDGE-MIB::dot1dGroups,,,,,,
.1.3.6.1.2.1.17.8.1.1,BRIDGE-MIB::dot1dBaseBridgeGroup,,,,,,Bridge level information for this device.
.1.3.6.1.2.1.17.8.1.2,BRIDGE-MIB::dot1dBasePortGroup,,,,,,Information for each port on this device.
.1.3.6.1.2.1.17.8.1.3,BRIDGE-MIB::dot1dStpBridgeGroup,,,,,,Bridge level Spanning Tree data for this device.
.1.3.6.1.2.1.17.8.1.4,BRIDGE-MIB::dot1dStpPortGroup,,,,,,Spanning Tree data for each port on this device.
.1.3.6.1.2.1.17.8.1.5,BRIDGE-MIB::dot1dStpPortGroup2,,,,,,Spanning Tree data for each port on this device.
.1.3.6.1.2.1.17.8.1.6,BRIDGE-MIB::dot1dStpPortGroup3,,,,,,Spanning Tree data for devices supporting 32-bit path costs.
.1.3.6.1.2.1.17.8.1.7,BRIDGE-MIB::dot1dTpBridgeGroup,,,,,,Bridge level Transparent Bridging data.
.1.3.6.1.2.1.17.8.1.8,BRIDGE-MIB::dot1dTpFdbGroup,,,,,,Filtering Database information for the Bridge.
.1.3.6.1.2.1.17.8.1.9,BRIDGE-MIB::dot1dTpGroup,,,,,,Dynamic Filtering Database information for each port of the Bridge.
.1.3.6.1.2.1.17.8.1.10,BRIDGE-MIB::dot1dStaticGroup,,,,,,Static Filtering Database information for each port of the Bridge.
.1.3.6.1.2.1.17.8.1.11,BRIDGE-MIB::dot1dNotificationGroup,,,,,,Group of objects describing notifications (traps).
.1.3.6.1.2.1.17.8.2,BRIDGE-MIB::dot1dCompliances,,,,,,
.1.3.6.1.2.1.17.8.2.1,BRIDGE-MIB::bridgeCompliance1493,,,,,,The compliance statement for device support of bridging services, as per RFC1493.
.1.3.6.1.2.1.17.8.2.2,BRIDGE-MIB::bridgeCompliance4188,,,,,,The compliance statement for device support of bridging services. This supports 32-bit Path Cost values and the more restricted bridge and port priorities, as per IEEE 802.1t. Full support for the 802.1D management objects requires that the SNMPv2-MIB [RFC3418] objects sysDescr, and sysUpTime, as well as the IF-MIB [RFC2863] objects ifIndex, ifType, ifDescr, ifPhysAddress, and ifLastChange are implemented.
.1.3.6.1.2.1.30,IANAifType-MIB::ianaifType,,,,,,This MIB module defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable.
.1.3.6.1.2.1.31,IF-MIB::ifMIB,,,,,,The MIB module to describe generic objects for network interface sub-layers. This MIB is an updated version of MIB-II's ifTable, and incorporates the extensions defined in RFC 1229.
.1.3.6.1.2.1.31.1,IF-MIB::ifMIBObjects,,,,,,
.1.3.6.1.2.1.31.1.1,IF-MIB::ifXTable,,not-accessible,,current,,A list of interface entries. The number of entries is given by the value of ifNumber. This table contains additional objects for the interface table.
.1.3.6.1.2.1.31.1.1.1,IF-MIB::ifXEntry,,not-accessible,,current,,An entry containing additional management information applicable to a particular interface.
.1.3.6.1.2.1.31.1.1.1.1,IF-MIB::ifName,OCTET,read-only,,current,,The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name, such as `le0' or a simple port number, such as `1', depending on the interface naming syntax of the device. If several entries in the ifTable together represent a single interface as named by the device, then each will have the same value of ifName. Note that for an agent which responds to SNMP queries concerning an interface on some other (proxied) device, then the value of ifName for such an interface is the proxied device's local name for it. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.
.1.3.6.1.2.1.31.1.1.1.2,IF-MIB::ifInMulticastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.3,IF-MIB::ifInBroadcastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.4,IF-MIB::ifOutMulticastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.5,IF-MIB::ifOutBroadcastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.6,IF-MIB::ifHCInOctets,Counter64,read-only,,current,,The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.7,IF-MIB::ifHCInUcastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. This object is a 64-bit version of ifInUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.8,IF-MIB::ifHCInMulticastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifInMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.9,IF-MIB::ifHCInBroadcastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer. This object is a 64-bit version of ifInBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.10,IF-MIB::ifHCOutOctets,Counter64,read-only,,current,,The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.11,IF-MIB::ifHCOutUcastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.12,IF-MIB::ifHCOutMulticastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.13,IF-MIB::ifHCOutBroadcastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.14,IF-MIB::ifLinkUpDownTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether linkUp/linkDown traps should be generated for this interface. By default, this object should have the value enabled(1) for interfaces which do not operate on 'top' of any other interface (as defined in the ifStackTable), and disabled(2) otherwise.
.1.3.6.1.2.1.31.1.1.1.15,IF-MIB::ifHighSpeed,Gauge32,read-only,,current,,An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of `n' then the speed of the interface is somewhere in the range of `n-500,000' to `n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.
.1.3.6.1.2.1.31.1.1.1.16,IF-MIB::ifPromiscuousMode,INTEGER,read-write,,current,true(1):false(2),This object has a value of false(2) if this interface only accepts packets/frames that are addressed to this station. This object has a value of true(1) when the station accepts all packets/frames transmitted on the media. The value true(1) is only legal on certain types of media. If legal, setting this object to a value of true(1) may require the interface to be reset before becoming effective. The value of ifPromiscuousMode does not affect the reception of broadcast and multicast packets/frames by the interface.
.1.3.6.1.2.1.31.1.1.1.17,IF-MIB::ifConnectorPresent,INTEGER,read-only,,current,true(1):false(2),This object has the value 'true(1)' if the interface sublayer has a physical connector and the value 'false(2)' otherwise.
.1.3.6.1.2.1.31.1.1.1.18,IF-MIB::ifAlias,OCTET,read-write,,current,,This object is an 'alias' name for the interface as specified by a network manager, and provides a non-volatile 'handle' for the interface. On the first instantiation of an interface, the value of ifAlias associated with that interface is the zero-length string. As and when a value is written into an instance of ifAlias through a network management set operation, then the agent must retain the supplied value in the ifAlias instance associated with the same interface for as long as that interface remains instantiated, including across all re- initializations/reboots of the network management system, including those which result in a change of the interface's ifIndex value. An example of the value which a network manager might store in this object for a WAN interface is the (Telco's) circuit number/identifier of the interface. Some agents may support write-access only for interfaces having particular values of ifType. An agent which supports write access to this object is required to keep the value in non-volatile storage, but it may limit the length of new values depending on how much storage is already occupied by the current values for other interfaces.
.1.3.6.1.2.1.31.1.1.1.19,IF-MIB::ifCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the ifTable or ifXTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.1.2,IF-MIB::ifStackTable,,not-accessible,,current,,The table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'on top of' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs over the sub-layer with ifIndex value y, then this table contains: ifStackStatus.x.y=active For each ifIndex value, I, which identifies an active interface, there are always at least two instantiated rows in this table associated with I. For one of these rows, I is the value of ifStackHigherLayer; for the other, I is the value of ifStackLowerLayer. (If I is not involved in multiplexing, then these are the only two rows associated with I.) For example, two rows exist even for an interface which has no others stacked on top or below it: ifStackStatus.0.x=active ifStackStatus.x.0=active 
.1.3.6.1.2.1.31.1.2.1,IF-MIB::ifStackEntry,,not-accessible,ifStackHigherLayer:ifStackLowerLayer,current,,Information on a particular relationship between two sub- layers, specifying that one sub-layer runs on 'top' of the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
.1.3.6.1.2.1.31.1.2.1.1,IF-MIB::ifStackHigherLayer,Integer32,not-accessible,,current,,The value of ifIndex corresponding to the higher sub-layer of the relationship, i.e., the sub-layer which runs on 'top' of the sub-layer identified by the corresponding instance of ifStackLowerLayer. If there is no higher sub-layer (below the internetwork layer), then this object has the value 0.
.1.3.6.1.2.1.31.1.2.1.2,IF-MIB::ifStackLowerLayer,Integer32,not-accessible,,current,,The value of ifIndex corresponding to the lower sub-layer of the relationship, i.e., the sub-layer which runs 'below' the sub-layer identified by the corresponding instance of ifStackHigherLayer. If there is no lower sub-layer, then this object has the value 0.
.1.3.6.1.2.1.31.1.2.1.3,IF-MIB::ifStackStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the relationship between two sub-layers. Changing the value of this object from 'active' to 'notInService' or 'destroy' will likely have consequences up and down the interface stack. Thus, write access to this object is likely to be inappropriate for some types of interfaces, and many implementations will choose not to support write-access for any type of interface.
.1.3.6.1.2.1.31.1.3,IF-MIB::ifTestTable,,not-accessible,,deprecated,,This table contains one entry per interface. It defines objects which allow a network manager to instruct an agent to test an interface for various faults. Tests for an interface are defined in the media-specific MIB for that interface. After invoking a test, the object ifTestResult can be read to determine the outcome. If an agent can not perform the test, ifTestResult is set to so indicate. The object ifTestCode can be used to provide further test- specific or interface-specific (or even enterprise-specific) information concerning the outcome of the test. Only one test can be in progress on each interface at any one time. If one test is in progress when another test is invoked, the second test is rejected. Some agents may reject a test when a prior test is active on another interface. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the ifTestTable for the interface to be tested. This is accomplished with the ifTestId and ifTestStatus objects as follows: try_again: get (ifTestId, ifTestStatus) while (ifTestStatus != notInUse) /* * Loop while a test is running or some other * manager is configuring a test. */ short delay get (ifTestId, ifTestStatus) } /* * Is not being used right now -- let's compete * to see who gets it. */ lock_value = ifTestId if ( set(ifTestId = lock_value, ifTestStatus = inUse, ifTestOwner = 'my-IP-address') == FAILURE) /* * Another manager got the ifTestEntry -- go * try again */ goto try_again; /* * I have the lock */ set up any test parameters. /* * This starts the test */ set(ifTestType = test_to_run); wait for test completion by polling ifTestResult when test completes, agent sets ifTestResult agent also sets ifTestStatus = 'notInUse' retrieve any additional test results, and ifTestId if (ifTestId == lock_value+1) results are valid A manager station first retrieves the value of the appropriate ifTestId and ifTestStatus objects, periodically repeating the retrieval if necessary, until the value of ifTestStatus is 'notInUse'. The manager station then tries to set the same ifTestId object to the value it just retrieved, the same ifTestStatus object to 'inUse', and the corresponding ifTestOwner object to a value indicating itself. If the set operation succeeds then the manager has obtained ownership of the ifTestEntry, and the value of the ifTestId object is incremented by the agent (per the semantics of TestAndIncr). Failure of the set operation indicates that some other manager has obtained ownership of the ifTestEntry. Once ownership is obtained, any test parameters can be setup, and then the test is initiated by setting ifTestType. On completion of the test, the agent sets ifTestStatus to 'notInUse'. Once this occurs, the manager can retrieve the results. In the (rare) event that the invocation of tests by two network managers were to overlap, then there would be a possibility that the first test's results might be overwritten by the second test's results prior to the first results being read. This unlikely circumstance ca
.1.3.6.1.2.1.31.1.3.1,IF-MIB::ifTestEntry,,not-accessible,,deprecated,,An entry containing objects for invoking tests on an interface.
.1.3.6.1.2.1.31.1.3.1.1,IF-MIB::ifTestId,INTEGER,read-write,,deprecated,,This object identifies the current invocation of the interface's test.
.1.3.6.1.2.1.31.1.3.1.2,IF-MIB::ifTestStatus,INTEGER,read-write,,deprecated,notInUse(1):inUse(2),This object indicates whether or not some manager currently has the necessary 'ownership' required to invoke a test on this interface. A write to this object is only successful when it changes its value from 'notInUse(1)' to 'inUse(2)'. After completion of a test, the agent resets the value back to 'notInUse(1)'.
.1.3.6.1.2.1.31.1.3.1.3,IF-MIB::ifTestType,OBJECT,read-write,,deprecated,,A control variable used to start and stop operator- initiated interface tests. Most OBJECT IDENTIFIER values assigned to tests are defined elsewhere, in association with specific types of interface. However, this document assigns a value for a full-duplex loopback test, and defines the special meanings of the subject identifier: noTest OBJECT IDENTIFIER ::= { 0 0 } When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the indicated test is initiated. When read, this object always returns the most recent value that ifTestType was set to. If it has not been set since the last initialization of the network management subsystem on the agent, a value of noTest is returned.
.1.3.6.1.2.1.31.1.3.1.4,IF-MIB::ifTestResult,INTEGER,read-only,,deprecated,none(1):success(2):inProgress(3):notSupported(4):unAbleToRun(5):aborted(6):failed(7),This object contains the result of the most recently requested test, or the value none(1) if no tests have been requested since the last reset. Note that this facility provides no provision for saving the results of one test when starting another, as could be required if used by multiple managers concurrently.
.1.3.6.1.2.1.31.1.3.1.5,IF-MIB::ifTestCode,OBJECT,read-only,,deprecated,,This object contains a code which contains more specific information on the test result, for example an error-code after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test. The value may have the semantics of either the AutonomousType or InstancePointer textual conventions as defined in RFC 2579. The identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } is defined for use if no additional result code is available.
.1.3.6.1.2.1.31.1.3.1.6,IF-MIB::ifTestOwner,OCTET,read-write,,deprecated,,The entity which currently has the 'ownership' required to invoke a test on this interface.
.1.3.6.1.2.1.31.1.4,IF-MIB::ifRcvAddressTable,,not-accessible,,current,,This table contains an entry for each address (broadcast, multicast, or uni-cast) for which the system will receive packets/frames on a particular interface, except as follows: - for an interface operating in promiscuous mode, entries are only required for those addresses for which the system would receive frames were it not operating in promiscuous mode. - for 802.5 functional addresses, only one entry is required, for the address which has the functional address bit ANDed with the bit mask of all functional addresses for which the interface will accept frames. A system is normally able to use any unicast address which corresponds to an entry in this table as a source address.
.1.3.6.1.2.1.31.1.4.1,IF-MIB::ifRcvAddressEntry,,not-accessible,ifIndex:ifRcvAddressAddress,current,,A list of objects identifying an address for which the system will accept packets/frames on the particular interface identified by the index value ifIndex.
.1.3.6.1.2.1.31.1.4.1.1,IF-MIB::ifRcvAddressAddress,OCTET,not-accessible,,current,,An address for which the system will accept packets/frames on this entry's interface.
.1.3.6.1.2.1.31.1.4.1.2,IF-MIB::ifRcvAddressStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the ifRcvAddressTable.
.1.3.6.1.2.1.31.1.4.1.3,IF-MIB::ifRcvAddressType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3),This object has the value nonVolatile(3) for those entries in the table which are valid and will not be deleted by the next restart of the managed system. Entries having the value volatile(2) are valid and exist, but have not been saved, so that will not exist after the next restart of the managed system. Entries having the value other(1) are valid and exist but are not classified as to whether they will continue to exist after the next restart.
.1.3.6.1.2.1.31.1.5,IF-MIB::ifTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last creation or deletion of an entry in the ifTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.1.6,IF-MIB::ifStackLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last change of the (whole) interface stack. A change of the interface stack is defined to be any creation, deletion, or change in value of any instance of ifStackStatus. If the interface stack has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.2,IF-MIB::ifConformance,,,,,,
.1.3.6.1.2.1.31.2.1,IF-MIB::ifGroups,,,,,,
.1.3.6.1.2.1.31.2.1.1,IF-MIB::ifGeneralGroup,,,,,,A collection of objects deprecated in favour of ifGeneralInformationGroup.
.1.3.6.1.2.1.31.2.1.2,IF-MIB::ifFixedLengthGroup,,,,,,A collection of objects providing information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20,000,000 bits/second) character-oriented or fixed-length-transmission network interfaces.
.1.3.6.1.2.1.31.2.1.3,IF-MIB::ifHCFixedLengthGroup,,,,,,A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second) character- oriented or fixed-length-transmission network interfaces.
.1.3.6.1.2.1.31.2.1.4,IF-MIB::ifPacketGroup,,,,,,A collection of objects providing information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20,000,000 bits/second) packet-oriented network interfaces.
.1.3.6.1.2.1.31.2.1.5,IF-MIB::ifHCPacketGroup,,,,,,A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second but less than or equal to 650,000,000 bits/second) packet-oriented network interfaces.
.1.3.6.1.2.1.31.2.1.6,IF-MIB::ifVHCPacketGroup,,,,,,A collection of objects providing information specific to higher speed (greater than 650,000,000 bits/second) packet- oriented network interfaces.
.1.3.6.1.2.1.31.2.1.7,IF-MIB::ifRcvAddressGroup,,,,,,A collection of objects providing information on the multiple addresses which an interface receives.
.1.3.6.1.2.1.31.2.1.8,IF-MIB::ifTestGroup,,,,,,A collection of objects providing the ability to invoke tests on an interface.
.1.3.6.1.2.1.31.2.1.9,IF-MIB::ifStackGroup,,,,,,The previous collection of objects providing information on the layering of MIB-II interfaces.
.1.3.6.1.2.1.31.2.1.10,IF-MIB::ifGeneralInformationGroup,,,,,,A collection of objects providing information applicable to all network interfaces.
.1.3.6.1.2.1.31.2.1.11,IF-MIB::ifStackGroup2,,,,,,A collection of objects providing information on the layering of MIB-II interfaces.
.1.3.6.1.2.1.31.2.1.12,IF-MIB::ifOldObjectsGroup,,,,,,The collection of objects deprecated from the original MIB- II interfaces group.
.1.3.6.1.2.1.31.2.1.13,IF-MIB::ifCounterDiscontinuityGroup,,,,,,A collection of objects providing information specific to interface counter discontinuities.
.1.3.6.1.2.1.31.2.1.14,IF-MIB::linkUpDownNotificationsGroup,,,,,,The notifications which indicate specific changes in the value of ifOperStatus.
.1.3.6.1.2.1.31.2.2,IF-MIB::ifCompliances,,,,,,
.1.3.6.1.2.1.31.2.2.1,IF-MIB::ifCompliance,,,,,,A compliance statement defined in a previous version of this MIB module, for SNMP entities which have network interfaces.
.1.3.6.1.2.1.31.2.2.2,IF-MIB::ifCompliance2,,,,,,A compliance statement defined in a previous version of this MIB module, for SNMP entities which have network interfaces.
.1.3.6.1.2.1.31.2.2.3,IF-MIB::ifCompliance3,,,,,,The compliance statement for SNMP entities which have network interfaces.
.1.3.6.1.2.1.47,ENTITY-MIB::entityMIB,,,,,,The MIB module for representing multiple logical entities supported by a single SNMP agent. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.47.1,ENTITY-MIB::entityMIBObjects,,,,,,
.1.3.6.1.2.1.47.1.1,ENTITY-MIB::entityPhysical,,,,,,
.1.3.6.1.2.1.47.1.1.1,ENTITY-MIB::entPhysicalTable,,not-accessible,,current,,This table contains one row per physical entity. There is always at least one row for an 'overall' physical entity.
.1.3.6.1.2.1.47.1.1.1.1,ENTITY-MIB::entPhysicalEntry,,not-accessible,entPhysicalIndex,current,,Information about a particular physical entity. Each entry provides objects (entPhysicalDescr, entPhysicalVendorType, and entPhysicalClass) to help an NMS identify and characterize the entry and objects (entPhysicalContainedIn and entPhysicalParentRelPos) to help an NMS relate the particular entry to other entries in this table.
.1.3.6.1.2.1.47.1.1.1.1.1,ENTITY-MIB::entPhysicalIndex,Integer32,not-accessible,,current,,The index for this entry.
.1.3.6.1.2.1.47.1.1.1.1.2,ENTITY-MIB::entPhysicalDescr,OCTET,read-only,,current,,A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.
.1.3.6.1.2.1.47.1.1.1.1.3,ENTITY-MIB::entPhysicalVendorType,OBJECT,read-only,,current,,An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID. An agent should set this object to an enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device. If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.
.1.3.6.1.2.1.47.1.1.1.1.4,ENTITY-MIB::entPhysicalContainedIn,Integer32,read-only,,current,,The value of entPhysicalIndex for the physical entity that 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed. In the event that a physical entity is contained by more than one physical entity (e.g., double-wide modules), this object should identify the containing entity with the lowest value of entPhysicalIndex.
.1.3.6.1.2.1.47.1.1.1.1.5,ENTITY-MIB::entPhysicalClass,INTEGER,read-only,,current,other(1):unknown(2):chassis(3):backplane(4):container(5):powerSupply(6):fan(7):sensor(8):module(9):port(10):stack(11):cpu(12):energyObject(13):battery(14):storageDrive(15),An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one entity. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned.
.1.3.6.1.2.1.47.1.1.1.1.6,ENTITY-MIB::entPhysicalParentRelPos,Integer32,read-only,,current,,An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects. An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the entPhysicalContainedIn instance in each sibling entry). If possible, this value should match any external labeling of the physical component. For example, for a container (e.g., card slot) labeled as 'slot #3', entPhysicalParentRelPos should have the value '3'. Note that the entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of '1'. If the physical position of this component does not match any external numbering or clearly visible ordering, then user documentation or other external reference material should be used to determine the parent-relative position. If this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of 'sibling' components, perhaps based on internal representation of the components. If the agent cannot determine the parent-relative position for some reason, or if the associated value of entPhysicalContainedIn is '0', then the value '-1' is returned. Otherwise, a non-negative integer is returned, indicating the parent-relative position of this physical entity. Parent-relative ordering normally starts from '1' and continues to 'N', where 'N' represents the highest positioned child entity. However, if the physical entities (e.g., slots) are labeled from a starting position of zero, then the first sibling should be associated with an entPhysicalParentRelPos value of '0'. Note that this ordering may be sparse or dense, depending on agent implementation. The actual values returned are not globally meaningful, as each 'parent' component may use different numbering algorithms. The ordering is only meaningful among siblings of the same parent component. The agent should retain parent-relative position values across reboots, either through algorithmic assignment or use of non-volatile storage.
.1.3.6.1.2.1.47.1.1.1.1.7,ENTITY-MIB::entPhysicalName,OCTET,read-only,,current,,The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
.1.3.6.1.2.1.47.1.1.1.1.8,ENTITY-MIB::entPhysicalHardwareRev,OCTET,read-only,,current,,The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present). Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific hardware revision string is associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.9,ENTITY-MIB::entPhysicalFirmwareRev,OCTET,read-only,,current,,The vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.10,ENTITY-MIB::entPhysicalSoftwareRev,OCTET,read-only,,current,,The vendor-specific software revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific software programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.11,ENTITY-MIB::entPhysicalSerialNum,OCTET,read-write,,current,,The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present). On the first instantiation of a physical entity, the value of entPhysicalSerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the entPhysicalSerialNum will be set to a zero-length string instead. Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object. Agents that cannot provide non-volatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object. Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique serial numbers. An agent does not have to provide write access for such entities and may return a zero-length string. If write access is implemented for an instance of entPhysicalSerialNum and a value is written into the instance, the agent must retain the supplied value in the entPhysicalSerialNum instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value.
.1.3.6.1.2.1.47.1.1.1.1.12,ENTITY-MIB::entPhysicalMfgName,OCTET,read-only,,current,,The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present). Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects are only meaningful amongst entPhysicalEntries with the same value of entPhysicalMfgName. If the manufacturer name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.13,ENTITY-MIB::entPhysicalModelName,OCTET,read-only,,current,,The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.14,ENTITY-MIB::entPhysicalAlias,OCTET,read-write,,current,,This object is an 'alias' name for the physical entity, as specified by a network manager, and provides a non-volatile 'handle' for the physical entity. On the first instantiation of a physical entity, the value of entPhysicalAlias associated with that entity is set to the zero-length string. However, the agent may set the value to a locally unique default value, instead of a zero-length string. If write access is implemented for an instance of entPhysicalAlias and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAlias instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value.
.1.3.6.1.2.1.47.1.1.1.1.15,ENTITY-MIB::entPhysicalAssetID,OCTET,read-write,,current,,This object is a user-assigned asset tracking identifier (as specified by a network manager) for the physical entity and provides non-volatile storage of this information. On the first instantiation of a physical entity, the value of entPhysicalAssetID associated with that entity is set to the zero-length string. Not every physical component will have an asset tracking identifier or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities and may instead return a zero-length string. If write access is implemented for an instance of entPhysicalAssetID and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAssetID instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value. If no asset tracking information is associated with the physical component, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.16,ENTITY-MIB::entPhysicalIsFRU,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not this physical entity is considered a 'field replaceable unit' by the vendor. If this object contains the value 'true(1)', then this entPhysicalEntry identifies a field replaceable unit. For all entPhysicalEntries that represent components permanently contained within a field replaceable unit, the value 'false(2)' should be returned for this object.
.1.3.6.1.2.1.47.1.1.1.1.17,ENTITY-MIB::entPhysicalMfgDate,OCTET,read-only,,current,,This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported, the object is not instantiated. The special value '0000000000000000'H may also be returned in this case.
.1.3.6.1.2.1.47.1.1.1.1.18,ENTITY-MIB::entPhysicalUris,OCTET,read-write,,current,,This object contains identification information about the physical entity. The object contains URIs; therefore, the syntax of this object must conform to RFC 3986, Section 3. Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored. If no URI identification information is known about the physical entity, the object is not instantiated. A zero-length octet string may also be returned in this case.
.1.3.6.1.2.1.47.1.1.1.1.19,ENTITY-MIB::entPhysicalUUID,OCTET,read-only,,current,,This object contains identification information about the physical entity. The object contains a Universally Unique Identifier, the syntax of this object must conform to RFC 4122, Section 4.1. A zero-length octet string is returned if no UUID information is known.
.1.3.6.1.2.1.47.1.2,ENTITY-MIB::entityLogical,,,,,,
.1.3.6.1.2.1.47.1.2.1,ENTITY-MIB::entLogicalTable,,not-accessible,,current,,This table contains one row per logical entity. For agents that implement more than one naming scope, at least one entry must exist. Agents that instantiate all MIB objects within a single naming scope are not required to implement this table.
.1.3.6.1.2.1.47.1.2.1.1,ENTITY-MIB::entLogicalEntry,,not-accessible,entLogicalIndex,current,,Information about a particular logical entity. Entities may be managed by this agent or other SNMP agents (possibly) in the same chassis.
.1.3.6.1.2.1.47.1.2.1.1.1,ENTITY-MIB::entLogicalIndex,Integer32,not-accessible,,current,,The value of this object uniquely identifies the logical entity. The value should be a small positive integer; index values for different logical entities are not necessarily contiguous.
.1.3.6.1.2.1.47.1.2.1.1.2,ENTITY-MIB::entLogicalDescr,OCTET,read-only,,current,,A textual description of the logical entity. This object should contain a string that identifies the manufacturer's name for the logical entity and should be set to a distinct value for each version of the logical entity.
.1.3.6.1.2.1.47.1.2.1.1.3,ENTITY-MIB::entLogicalType,OBJECT,read-only,,current,,An indication of the type of logical entity. This will typically be the OBJECT IDENTIFIER name of the node in the SMI's naming hierarchy that represents the major MIB module, or the majority of the MIB modules, supported by the logical entity. For example: a logical entity of a regular host/router -> mib-2 a logical entity of a 802.1d bridge -> dot1dBridge a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt If an appropriate node in the SMI's naming hierarchy cannot be identified, the value 'mib-2' should be used.
.1.3.6.1.2.1.47.1.2.1.1.4,ENTITY-MIB::entLogicalCommunity,OCTET,read-only,,deprecated,,An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object or may continue to return a community string (e.g., tri-lingual agent support).
.1.3.6.1.2.1.47.1.2.1.1.5,ENTITY-MIB::entLogicalTAddress,OCTET,read-only,,current,,The transport service address by which the logical entity receives network management traffic, formatted according to the corresponding value of entLogicalTDomain. For snmpUDPDomain, a TAddress is 6 octets long: the initial 4 octets contain the IP-address in network-byte order, and the last 2 contain the UDP port in network-byte order. Consult RFC 3417 for further information on snmpUDPDomain.
.1.3.6.1.2.1.47.1.2.1.1.6,ENTITY-MIB::entLogicalTDomain,OBJECT,read-only,,current,,Indicates the kind of transport service by which the logical entity receives network management traffic. Possible values for this object are presently found in RFC 3417.
.1.3.6.1.2.1.47.1.2.1.1.7,ENTITY-MIB::entLogicalContextEngineID,OCTET,read-only,,current,,The authoritative contextEngineID that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. This object, together with the associated entLogicalContextName object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to instantiate this object at all.
.1.3.6.1.2.1.47.1.2.1.1.8,ENTITY-MIB::entLogicalContextName,OCTET,read-only,,current,,The contextName that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. This object, together with the associated entLogicalContextEngineID object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to instantiate this object at all.
.1.3.6.1.2.1.47.1.3,ENTITY-MIB::entityMapping,,,,,,
.1.3.6.1.2.1.47.1.3.1,ENTITY-MIB::entLPMappingTable,,not-accessible,,current,,This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources, which are used to realize that logical entity. An agent should limit the number and nature of entries in this table such that only meaningful and non-redundant information is returned. For example, in a system that contains a single power supply, mappings between logical entities and the power supply are not useful and should not be included. Also, only the most appropriate physical component, which is closest to the root of a particular containment tree, should be identified in an entLPMapping entry. For example, suppose a bridge is realized on a particular module, and all ports on that module are ports on this bridge. A mapping between the bridge and the module would be useful, but additional mappings between the bridge and each of the ports on that module would be redundant (because the entPhysicalContainedIn hierarchy can provide the same information). On the other hand, if more than one bridge were utilizing ports on this module, then mappings between each bridge and the ports it used would be appropriate. Also, in the case of a single backplane repeater, a mapping for the backplane to the single repeater entity is not necessary.
.1.3.6.1.2.1.47.1.3.1.1,ENTITY-MIB::entLPMappingEntry,,not-accessible,entLogicalIndex:entLPPhysicalIndex,current,,Information about a particular logical-entity-to-physical- equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIB modules used to manage a particular logical entity to infer how physical component information is utilized.
.1.3.6.1.2.1.47.1.3.1.1.1,ENTITY-MIB::entLPPhysicalIndex,Integer32,read-only,,current,,The value of this object identifies the index value of a particular entPhysicalEntry associated with the indicated entLogicalEntity.
.1.3.6.1.2.1.47.1.3.2,ENTITY-MIB::entAliasMappingTable,,not-accessible,,current,,This table contains zero or more rows, representing mappings of logical entities and physical components to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical entity's naming scope. A 'wildcard' mechanism is provided to indicate that an identifier is associated with more than one logical entity.
.1.3.6.1.2.1.47.1.3.2.1,ENTITY-MIB::entAliasMappingEntry,,not-accessible,entPhysicalIndex:entAliasLogicalIndexOrZero,current,,Information about a particular binding between a logical entity/physical component pair and an external identifier. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero objectclause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
.1.3.6.1.2.1.47.1.3.2.1.1,ENTITY-MIB::entAliasLogicalIndexOrZero,Integer32,not-accessible,,current,,The value of this object identifies the logical entity that defines the naming scope for the associated instance of the entAliasMappingIdentifier object. If this object has a non-zero value, then it identifies the logical entity named by the same value of entLogicalIndex. If this object has a value of zero, then the mapping between the physical component and the alias identifier for this entAliasMapping entry is associated with all unspecified logical entities. That is, a value of zero (the default mapping) identifies any logical entity that does not have an explicit entry in this table for a particular entPhysicalIndex/entAliasMappingIdentifier pair. For example, to indicate that a particular interface (e.g., physical component 33) is identified by the same value of ifIndex for all logical entities, the following instance might exist: entAliasMappingIdentifier.33.0 = ifIndex.5 In the event an entPhysicalEntry is associated differently for some logical entities, additional entAliasMapping entries may exist, e.g.: entAliasMappingIdentifier.33.0 = ifIndex.6 entAliasMappingIdentifier.33.4 = ifIndex.1 entAliasMappingIdentifier.33.5 = ifIndex.1 entAliasMappingIdentifier.33.10 = ifIndex.12 Note that entries with non-zero entAliasLogicalIndexOrZero index values have precedence over zero-indexed entries. In this example, all logical entities except 4, 5, and 10 associate physical entity 33 with ifIndex.6.
.1.3.6.1.2.1.47.1.3.2.1.2,ENTITY-MIB::entAliasMappingIdentifier,OBJECT,read-only,,current,,The value of this object identifies a particular conceptual row associated with the indicated entPhysicalIndex and entLogicalIndex pair. Because only physical ports are modeled in this table, only entries that represent interfaces or ports are allowed. If an ifEntry exists on behalf of a particular physical port, then this object should identify the associated ifEntry. For repeater ports, the appropriate row in the 'rptrPortGroupTable' should be identified instead. For example, suppose a physical port was represented by entPhysicalEntry.3, entLogicalEntry.15 existed for a repeater, and entLogicalEntry.22 existed for a bridge. Then there might be two related instances of entAliasMappingIdentifier: entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2 entAliasMappingIdentifier.3.22 == ifIndex.17 It is possible that other mappings (besides interfaces and repeater ports) may be defined in the future, as required. Bridge ports are identified by examining the Bridge MIB and appropriate ifEntries associated with each 'dot1dBasePort' and are thus not represented in this table.
.1.3.6.1.2.1.47.1.3.3,ENTITY-MIB::entPhysicalContainsTable,,not-accessible,,current,,A table that exposes the container/'containee' relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format. In the event a physical entity is contained by more than one other physical entity (e.g., double-wide modules), this table should include these additional mappings, which cannot be represented in the entPhysicalTable virtual containment tree.
.1.3.6.1.2.1.47.1.3.3.1,ENTITY-MIB::entPhysicalContainsEntry,,not-accessible,entPhysicalIndex:entPhysicalChildIndex,current,,A single container/'containee' relationship.
.1.3.6.1.2.1.47.1.3.3.1.1,ENTITY-MIB::entPhysicalChildIndex,Integer32,read-only,,current,,The value of entPhysicalIndex for the contained physical entity.
.1.3.6.1.2.1.47.1.4,ENTITY-MIB::entityGeneral,,,,,,
.1.3.6.1.2.1.47.1.4.1,ENTITY-MIB::entLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time a conceptual row is created, modified, or deleted in any of these tables: - entPhysicalTable - entLogicalTable - entLPMappingTable - entAliasMappingTable - entPhysicalContainsTable 
.1.3.6.1.2.1.47.2,ENTITY-MIB::entityMIBTraps,,,,,,
.1.3.6.1.2.1.47.2.0,ENTITY-MIB::entityMIBTrapPrefix,,,,,,
.1.3.6.1.2.1.47.2.0.1,ENTITY-MIB::entConfigChange,,,,,,An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events, e.g., due to throttling or transmission loss.
.1.3.6.1.2.1.47.3,ENTITY-MIB::entityConformance,,,,,,
.1.3.6.1.2.1.47.3.1,ENTITY-MIB::entityCompliances,,,,,,
.1.3.6.1.2.1.47.3.1.1,ENTITY-MIB::entityCompliance,,,,,,The compliance statement for SNMP entities that implement version 1 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.2,ENTITY-MIB::entity2Compliance,,,,,,The compliance statement for SNMP entities that implement version 2 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.3,ENTITY-MIB::entity3Compliance,,,,,,The compliance statement for SNMP entities that implement version 3 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.4,ENTITY-MIB::entity4Compliance,,,,,,The compliance statement for SNMP entities that implement the full version 4 (full compliance) of the Entity MIB.
.1.3.6.1.2.1.47.3.1.5,ENTITY-MIB::entity4CRCompliance,,,,,,The compliance statement for SNMP entities that implement version 4 of the Entity MIB on devices with constrained resources.
.1.3.6.1.2.1.47.3.2,ENTITY-MIB::entityGroups,,,,,,
.1.3.6.1.2.1.47.3.2.1,ENTITY-MIB::entityPhysicalGroup,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.2,ENTITY-MIB::entityLogicalGroup,,,,,,The collection of objects used to represent the list of logical entities for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.3,ENTITY-MIB::entityMappingGroup,,,,,,The collection of objects used to represent the associations between multiple logical entities, physical components, interfaces, and port identifiers for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.4,ENTITY-MIB::entityGeneralGroup,,,,,,The collection of objects used to represent general entity information for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.5,ENTITY-MIB::entityNotificationsGroup,,,,,,The collection of notifications used to indicate Entity MIB data consistency and general status information.
.1.3.6.1.2.1.47.3.2.6,ENTITY-MIB::entityPhysical2Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup.
.1.3.6.1.2.1.47.3.2.7,ENTITY-MIB::entityLogical2Group,,,,,,The collection of objects used to represent the list of logical entities for which a single SNMP entity provides management information.
.1.3.6.1.2.1.47.3.2.8,ENTITY-MIB::entityPhysical3Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup.
.1.3.6.1.2.1.47.3.2.9,ENTITY-MIB::entityPhysical4Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup and entityPhysicalCRGroup.
.1.3.6.1.2.1.47.3.2.10,ENTITY-MIB::entityPhysicalCRGroup,,,,,,The collection of objects used to represent physical system components for constrained resourced devices, for which a single agent provides management information.
.1.3.6.1.2.1.72,IANA-ADDRESS-FAMILY-NUMBERS-MIB::ianaAddressFamilyNumbers,,,,,,The MIB module defines the AddressFamilyNumbers textual convention.
.1.3.6.1.2.1.76,INET-ADDRESS-MIB::inetAddressMIB,,,,,,This MIB module defines textual conventions for representing Internet addresses. An Internet address can be an IPv4 address, an IPv6 address, or a DNS domain name. This module also defines textual conventions for Internet port numbers, autonomous system numbers, and the length of an Internet address prefix. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4001, see the RFC itself for full legal notices.
.1.3.6.1.2.1.105,POWER-ETHERNET-MIB::powerEthernetMIB,,,,,,The MIB module for managing Power Source Equipment (PSE) working according to the IEEE 802.af Powered Ethernet (DTE Power via MDI) standard. The following terms are used throughout this MIB module. For complete formal definitions, the IEEE 802.3 standards should be consulted wherever possible: Group - A recommended, but optional, entity defined by the IEEE 802.3 management standard, in order to support a modular numbering scheme. The classical example allows an implementor to represent field-replaceable units as groups of ports, with the port numbering matching the modular hardware implementation. Port - This entity identifies the port within the group for which this entry contains information. The numbering scheme for ports is implementation specific. Copyright (c) The Internet Society (2003). This version of this MIB module is part of RFC 3621; See the RFC itself for full legal notices.
.1.3.6.1.2.1.105.0,POWER-ETHERNET-MIB::pethNotifications,,,,,,
.1.3.6.1.2.1.105.0.1,POWER-ETHERNET-MIB::pethPsePortOnOffNotification,,,,,, This Notification indicates if Pse Port is delivering or not power to the PD. This Notification SHOULD be sent on every status change except in the searching mode. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.0.2,POWER-ETHERNET-MIB::pethMainPowerUsageOnNotification,,,,,, This Notification indicate PSE Threshold usage indication is on, the usage power is above the threshold. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.0.3,POWER-ETHERNET-MIB::pethMainPowerUsageOffNotification,,,,,, This Notification indicates PSE Threshold usage indication off, the usage power is below the threshold. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.1,POWER-ETHERNET-MIB::pethObjects,,,,,,
.1.3.6.1.2.1.105.1.1,POWER-ETHERNET-MIB::pethPsePortTable,,not-accessible,,current,,A table of objects that display and control the power characteristics of power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented in managed power Ethernet switches and mid-span devices. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.1.1,POWER-ETHERNET-MIB::pethPsePortEntry,,not-accessible,pethPsePortGroupIndex:pethPsePortIndex,current,,A set of objects that display and control the power characteristics of a power Ethernet PSE port.
.1.3.6.1.2.1.105.1.1.1.1,POWER-ETHERNET-MIB::pethPsePortGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the port to which a power Ethernet PSE is connected. Group means box in the stack, module in a rack and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethMainPseGroupIndex, and pethNotificationControlGroupIndex to refer to a given box in a stack or module in the rack.
.1.3.6.1.2.1.105.1.1.1.2,POWER-ETHERNET-MIB::pethPsePortIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the power Ethernet PSE port within group pethPsePortGroupIndex to which the power Ethernet PSE entry is connected.
.1.3.6.1.2.1.105.1.1.1.3,POWER-ETHERNET-MIB::pethPsePortAdminEnable,INTEGER,read-write,,current,true(1):false(2),true (1) An interface which can provide the PSE functions. false(2) The interface will act as it would if it had no PSE function.
.1.3.6.1.2.1.105.1.1.1.4,POWER-ETHERNET-MIB::pethPsePortPowerPairsControlAbility,INTEGER,read-only,,current,true(1):false(2),Describes the capability of controlling the power pairs functionality to switch pins for sourcing power. The value true indicate that the device has the capability to control the power pairs. When false the PSE Pinout Alternative used cannot be controlled through the PethPsePortAdminEnable attribute.
.1.3.6.1.2.1.105.1.1.1.5,POWER-ETHERNET-MIB::pethPsePortPowerPairs,INTEGER,read-write,,current,signal(1):spare(2),Describes or controls the pairs in use. If the value of pethPsePortPowerPairsControl is true, this object is writable. A value of signal(1) means that the signal pairs only are in use. A value of spare(2) means that the spare pairs only are in use.
.1.3.6.1.2.1.105.1.1.1.6,POWER-ETHERNET-MIB::pethPsePortDetectionStatus,INTEGER,read-only,,current,disabled(1):searching(2):deliveringPower(3):fault(4):test(5):otherFault(6),Describes the operational status of the port PD detection. A value of disabled(1)- indicates that the PSE State diagram is in the state DISABLED. A value of deliveringPower(3) - indicates that the PSE State diagram is in the state POWER_ON for a duration greater than tlim max (see IEEE Std 802.3af Table 33-5 tlim). A value of fault(4) - indicates that the PSE State diagram is in the state TEST_ERROR. A value of test(5) - indicates that the PSE State diagram is in the state TEST_MODE. A value of otherFault(6) - indicates that the PSE State diagram is in the state IDLE due to the variable error_conditions. A value of searching(2)- indicates the PSE State diagram is in a state other than those listed above.
.1.3.6.1.2.1.105.1.1.1.7,POWER-ETHERNET-MIB::pethPsePortPowerPriority,INTEGER,read-write,,current,critical(1):high(2):low(3),This object controls the priority of the port from the point of view of a power management algorithm. The priority that is set by this variable could be used by a control mechanism that prevents over current situations by disconnecting first ports with lower power priority. Ports that connect devices critical to the operation of the network - like the E911 telephones ports - should be set to higher priority.
.1.3.6.1.2.1.105.1.1.1.8,POWER-ETHERNET-MIB::pethPsePortMPSAbsentCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram transitions directly from the state POWER_ON to the state IDLE due to tmpdo_timer_done being asserted.
.1.3.6.1.2.1.105.1.1.1.9,POWER-ETHERNET-MIB::pethPsePortType,OCTET,read-write,,current,,A manager will set the value of this variable to indicate the type of powered device that is connected to the port. The default value supplied by the agent if no value has ever been set should be a zero-length octet string.
.1.3.6.1.2.1.105.1.1.1.10,POWER-ETHERNET-MIB::pethPsePortPowerClassifications,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5),Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. The meaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered, that is, while the attribute pethPsePortDetectionStatus is reporting the enumeration deliveringPower.
.1.3.6.1.2.1.105.1.1.1.11,POWER-ETHERNET-MIB::pethPsePortInvalidSignatureCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state SIGNATURE_INVALID.
.1.3.6.1.2.1.105.1.1.1.12,POWER-ETHERNET-MIB::pethPsePortPowerDeniedCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state POWER_DENIED.
.1.3.6.1.2.1.105.1.1.1.13,POWER-ETHERNET-MIB::pethPsePortOverLoadCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_OVER.
.1.3.6.1.2.1.105.1.1.1.14,POWER-ETHERNET-MIB::pethPsePortShortCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_SHORT.
.1.3.6.1.2.1.105.1.3,POWER-ETHERNET-MIB::pethMainPseObjects,,,,,,
.1.3.6.1.2.1.105.1.3.1,POWER-ETHERNET-MIB::pethMainPseTable,,not-accessible,,current,,A table of objects that display and control attributes of the main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.3.1.1,POWER-ETHERNET-MIB::pethMainPseEntry,,not-accessible,pethMainPseGroupIndex,current,,A set of objects that display and control the Main power of a PSE. 
.1.3.6.1.2.1.105.1.3.1.1.1,POWER-ETHERNET-MIB::pethMainPseGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group to which power Ethernet PSE is connected. Group means (box in the stack, module in a rack) and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethPsePortGroupIndex, and pethNotificationControlGroupIndex to refer to a given box in a stack or module in a rack.
.1.3.6.1.2.1.105.1.3.1.1.2,POWER-ETHERNET-MIB::pethMainPsePower,Gauge32,read-only,,current,,The nominal power of the PSE expressed in Watts.
.1.3.6.1.2.1.105.1.3.1.1.3,POWER-ETHERNET-MIB::pethMainPseOperStatus,INTEGER,read-only,,current,on(1):off(2):faulty(3),The operational status of the main PSE.
.1.3.6.1.2.1.105.1.3.1.1.4,POWER-ETHERNET-MIB::pethMainPseConsumptionPower,Gauge32,read-only,,current,,Measured usage power expressed in Watts.
.1.3.6.1.2.1.105.1.3.1.1.5,POWER-ETHERNET-MIB::pethMainPseUsageThreshold,Integer32,read-write,,current,,The usage threshold expressed in percents for comparing the measured power and initiating an alarm if the threshold is exceeded.
.1.3.6.1.2.1.105.1.4,POWER-ETHERNET-MIB::pethNotificationControl,,,,,,
.1.3.6.1.2.1.105.1.4.1,POWER-ETHERNET-MIB::pethNotificationControlTable,,not-accessible,,current,,A table of objects that display and control the Notification on a PSE device. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.4.1.1,POWER-ETHERNET-MIB::pethNotificationControlEntry,,not-accessible,pethNotificationControlGroupIndex,current,,A set of objects that control the Notification events.
.1.3.6.1.2.1.105.1.4.1.1.1,POWER-ETHERNET-MIB::pethNotificationControlGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group. Group means box in the stack, module in a rack and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethPsePortGroupIndex, and pethMainPseGroupIndex to refer to a given box in a stack or module in a rack. 
.1.3.6.1.2.1.105.1.4.1.1.2,POWER-ETHERNET-MIB::pethNotificationControlEnable,INTEGER,read-write,,current,true(1):false(2),This object controls, on a per-group basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.3.6.1.2.1.105.2,POWER-ETHERNET-MIB::pethConformance,,,,,,
.1.3.6.1.2.1.105.2.1,POWER-ETHERNET-MIB::pethCompliances,,,,,,
.1.3.6.1.2.1.105.2.1.1,POWER-ETHERNET-MIB::pethCompliance,,,,,,Describes the requirements for conformance to the Power Ethernet MIB.
.1.3.6.1.2.1.105.2.2,POWER-ETHERNET-MIB::pethGroups,,,,,,
.1.3.6.1.2.1.105.2.2.1,POWER-ETHERNET-MIB::pethPsePortGroup,,,,,,PSE Port objects.
.1.3.6.1.2.1.105.2.2.2,POWER-ETHERNET-MIB::pethMainPseGroup,,,,,,Main PSE Objects. 
.1.3.6.1.2.1.105.2.2.3,POWER-ETHERNET-MIB::pethNotificationControlGroup,,,,,,Notification Control Objects. 
.1.3.6.1.2.1.105.2.2.4,POWER-ETHERNET-MIB::pethPsePortNotificationGroup,,,,,,Pse Port Notifications.
.1.3.6.1.2.1.105.2.2.5,POWER-ETHERNET-MIB::pethMainPowerNotificationGroup,,,,,,Main PSE Notifications.
.1.3.6.1.2.1.216,IANA-ENTITY-MIB::ianaEntityMIB,,,,,,This MIB module defines a TEXTUAL-CONVENTION that provides an indication of the general hardware type of a particular physical entity. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The initial version of this MIB module was published in RFC 6933; for full legal notices see the RFC itself.
.1.3.6.1.2.1.217,UUID-TC-MIB::uuidTCMIB,,,,,,This MIB module defines TEXTUAL-CONVENTIONs representing Universally Unique IDentifiers (UUIDs). Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.3,SNMPv2-SMI::experimental,,,,,,
.1.3.6.1.4,SNMPv2-SMI::private,,,,,,
.1.3.6.1.4.1,SNMPv2-SMI::enterprises,,,,,,
.1.3.6.1.4.1.47196,ARUBAWIRED-NETWORKING-OID::hpe,,,,,,
.1.3.6.1.4.1.47196.4,ARUBAWIRED-NETWORKING-OID::hpeNetworking,,,,,,This MIB module defines HPE Networking product hardware MIBs and proprietary MIBs. 
.1.3.6.1.4.1.47196.4.0,ARUBAWIRED-NETWORKING-OID::reservedhpeNetworking,,,,,,
.1.3.6.1.4.1.47196.4.1,ARUBAWIRED-NETWORKING-OID::wiredNetworkingDevices,,,,,,
.1.3.6.1.4.1.47196.4.1.1,ARUBAWIRED-NETWORKING-OID::arubaOS-CX,,,,,,
.1.3.6.1.4.1.47196.4.1.1.1,ARUBAWIRED-NETWORKING-OID::wndDeviceIds,,,,,,
.1.3.6.1.4.1.47196.4.1.1.1.1,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL375A,,,,,,The authoritative identifier for the JL375A Aruba 8400 8-slot chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.2,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL479A,,,,,,The authoritative identifier for the JL479A Aruba 8320 48p 10G SFP/SFP+ and 6p 40G QSFP+ chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.3,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL579A,,,,,,The authoritative identifier for the JL579A Aruba 8320 32p QSFP+ chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.5,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL581A,,,,,,The authoritative identifier for the JL581A Aruba 8320 48p 1G/10GBASE-T and 6p 40G QSFP+ chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.50,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL635A,,,,,,The authoritative identifier for the JL635A Aruba 8325 8325-48Y8C chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.70,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL636A,,,,,,The authoritative identifier for the JL636A Aruba 8325 8325-32C chassis switch.
.1.3.6.1.4.1.47196.4.1.1.1.100,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL658A,,,,,,The authoritative identifier for the Aruba 6300M 24SFP+/4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.101,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL659A,,,,,,The authoritative identifier for the Aruba 6300M 48SR PoE CLS6 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.102,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL660A,,,,,,The authoritative identifier for the Aruba 6300M 24SR PoECLS 6 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.103,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL661A,,,,,,The authoritative identifier for the Aruba 6300M 48G PoE CLS 4 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.104,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL662A,,,,,,The authoritative identifier for the Aruba 6300M 24G PoE CLS 4 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.105,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL663A,,,,,,The authoritative identifier for the Aruba 6300M 248G /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.106,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL664A,,,,,,The authoritative identifier for the Aruba 6300M 24G /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.107,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL665A,,,,,,The authoritative identifier for the Aruba 6300F 48G PoE CLS 4 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.108,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL666A,,,,,,The authoritative identifier for the Aruba 6300F 48G PoE CLS 4 /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.109,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL667A,,,,,,The authoritative identifier for the Aruba 6300F 48G /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.110,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL668A,,,,,,The authoritative identifier for the Aruba 6300F 24G /4SFP56 Swch.
.1.3.6.1.4.1.47196.4.1.1.1.111,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL762A,,,,,,The authoritative identifier for the Aruba 6300M 48G /4SFP56 Pwr2Prt Swch.
.1.3.6.1.4.1.47196.4.1.1.1.150,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X24A,,,,,,The authoritative identifier for the Aruba 6405 Chassis.
.1.3.6.1.4.1.47196.4.1.1.1.151,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X25A,,,,,,The authoritative identifier for the Aruba 6410 Chassis.
.1.3.6.1.4.1.47196.4.1.1.1.300,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL724A,,,,,,The authoritative identifier for the Aruba 6200F 24G 4SFP+ Swch.
.1.3.6.1.4.1.47196.4.1.1.1.301,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL725A,,,,,,The authoritative identifier for the Aruba 6200F 24G CL4 4SFP+370W Swch.
.1.3.6.1.4.1.47196.4.1.1.1.302,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL726A,,,,,,The authoritative identifier for the Aruba 6200F 48G 4SFP+ Swch.
.1.3.6.1.4.1.47196.4.1.1.1.303,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL727A,,,,,,The authoritative identifier for the Aruba 6200F 48G CL4 4SFP+370W Swch.
.1.3.6.1.4.1.47196.4.1.1.1.304,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL728A,,,,,,The authoritative identifier for the Aruba 6200F 48G CL4 4SFP+740W Swch.
.1.3.6.1.4.1.47196.4.1.1.2,ARUBAWIRED-NETWORKING-OID::wndComponentIds,,,,,,
.1.3.6.1.4.1.47196.4.1.1.2.1,ARUBAWIRED-NETWORKING-OID::wndSensors,,,,,,
.1.3.6.1.4.1.47196.4.1.1.2.1.1,ARUBAWIRED-NETWORKING-OID::arubaWiredTemperatureSensor,,,,,,Identifier for a temperature sensor type.
.1.3.6.1.4.1.47196.4.1.1.2.1.2,ARUBAWIRED-NETWORKING-OID::arubaWiredRPMSensor,,,,,,Identifier for a fan RPM sensor type.
.1.3.6.1.4.1.47196.4.1.1.2.1.3,ARUBAWIRED-NETWORKING-OID::arubaWiredPowerSensor,,,,,,Identifier for a PSU power sensor type.
.1.3.6.1.4.1.47196.4.1.1.2.2,ARUBAWIRED-NETWORKING-OID::wndSlots,,,,,,
.1.3.6.1.4.1.47196.4.1.1.2.2.1,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400FanTraySlot,,,,,,Represents slot for Aruba X731 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.2.2,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400PowerSupplySlot,,,,,,The authoritative identifier for a power supply bay in an Aruba 8400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.3,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400ManagementModuleSlot,,,,,,The authoritative identifier for a Management Module bay in a Aruba 8400 switch. 
.1.3.6.1.4.1.47196.4.1.1.2.2.4,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400LineCardSlot,,,,,,The authoritative identifier for a line card module slot in an Aruba 8400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.5,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400FabricCardSlot,,,,,,The authoritative identifier for a fabric module slot in an Aruba 8400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.6,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8400RearDisplayCardSlot,,,,,,The authoritative identifier for a fabric module slot in an Aruba 8400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.7,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8320FanTraySlot,,,,,,Represents slot for Aruba F2B Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.2.8,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8320PowerSupplySlot,,,,,,The authoritative identifier for a power supply bay in an Aruba 8320 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.9,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8325FanTraySlot,,,,,,Represents slot for Aruba Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.2.10,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch8325PowerSupplySlot,,,,,,The authoritative identifier for a power supply bay in an Aruba 8325 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.11,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6300FanTraySlot,,,,,,Represents slot for Aruba 6300M Switch Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.2.12,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6300PowerSupplySlot,,,,,,The authoritative identifier for a power supply bay in an Aruba 6300M switch. 
.1.3.6.1.4.1.47196.4.1.1.2.2.13,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6400ManagementModuleSlot,,,,,,The authoritative identifier for a Management Module slot in a Aruba 6400 switch. 
.1.3.6.1.4.1.47196.4.1.1.2.2.14,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6400LineCardSlot,,,,,,The authoritative identifier for a line card module slot in an Aruba 6400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.2.15,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6400FanTraySlot,,,,,,Represents slot for Aruba 6400 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.2.16,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch6400PowerSupplySlot,,,,,,The authoritative identifier for a power supply slot in an Aruba 6400 switch chassis. 
.1.3.6.1.4.1.47196.4.1.1.2.3,ARUBAWIRED-NETWORKING-OID::wndModules,,,,,,
.1.3.6.1.4.1.47196.4.1.1.2.3.1,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchManagementModuleJL368A,,,,,,The authoritative identifier for Aruba 8400 Management Module. 
.1.3.6.1.4.1.47196.4.1.1.2.3.2,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL363A,,,,,,The authoritative identifier for Aruba 8400X 32-port 10GbE SFP/SFP+ with MACsec Advanced Module. 
.1.3.6.1.4.1.47196.4.1.1.2.3.3,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL365A,,,,,,The authoritative identifier for Aruba 8400X 8-port 40GbE QSFP+ Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.4,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL366A,,,,,,The authoritative identifier for Aruba 8400X 6-port 40GbE/100GbE QSFP28 Advanced Module. 
.1.3.6.1.4.1.47196.4.1.1.2.3.5,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFabricModuleJL367A,,,,,,The authoritative identifier for Aruba 8400X 7.2Tbps Fabric Module. 
.1.3.6.1.4.1.47196.4.1.1.2.3.6,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanModuleJL370A,,,,,,The authoritative identifier for Aruba 8400 Fan for X731 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.7,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL372A,,,,,,The authoritative identifier for Aruba X382 54VDC 2700W AC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.8,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL369AFanTray,,,,,,The authoritative identifier for Aruba X731 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.9,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL479A,,,,,,The authoritative identifier for Aruba 8320 48p 10G SFP/SFP+ and 6p 40G QSFP+ Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.10,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL480A,,,,,,The authoritative identifier for Aruba 8320 400W AC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.11,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchJL481AFanTray,,,,,,The authoritative identifier for Aruba 8320 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.12,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchRearDisplayModule8400,,,,,,The authoritative identifier for Aruba 8400 Rear Display Module. 
.1.3.6.1.4.1.47196.4.1.1.2.3.13,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch1GbMaxPort,,,,,,The authoritative identifier for a 1Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.14,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch10GbMaxPort,,,,,,The authoritative identifier for a 10Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.15,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch25GbMaxPort,,,,,,The authoritative identifier for a 25Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.16,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch40GbMaxPort,,,,,,The authoritative identifier for a 40Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.17,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch100GbMaxPort,,,,,,The authoritative identifier for a 100Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.18,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchSmartRatePort,,,,,,The authoritative identifier for a Smart Rate multi-gigabit port.
.1.3.6.1.4.1.47196.4.1.1.2.3.19,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL579A,,,,,,The authoritative identifier for Aruba 8320 32p 40GbE QSFP+ Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.20,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL581A,,,,,,The authoritative identifier for Aruba 8320 48p 1G/10GBASE-T and 6p 40G QSFP+ Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.21,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL635A,,,,,,The authoritative identifier for Aruba 8325-48Y8C Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.22,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL624A,,,,,,The authoritative identifier for Aruba 8325-48Y8C FB Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.23,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL625A,,,,,,The authoritative identifier for Aruba 8325-48Y8C BF Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.24,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL636A,,,,,,The authoritative identifier for Aruba 8325-32C Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.25,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL626A,,,,,,The authoritative identifier for Aruba 8325-32C FB Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.26,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL627A,,,,,,The authoritative identifier for Aruba 8325-32C BF Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.27,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL632A,,,,,,The authoritative identifier for Aruba 8325 650W 100-240V FB AC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.28,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL633A,,,,,,The authoritative identifier for Aruba 8325 650W 100-240V BF AC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.29,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL628A,,,,,,The authoritative identifier for Aruba 8325-48Y8C F2B Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.30,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL629A,,,,,,The authoritative identifier for Aruba 8325-48Y8C B2F Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.31,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL630A,,,,,,The authoritative identifier for Aruba 8325-32C F2B Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.32,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL631A,,,,,,The authoritative identifier for Aruba 8325-32C B2F Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.33,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL658A,,,,,,The authoritative identifier for Aruba 6300M 24SFP+ 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.34,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL659A,,,,,,The authoritative identifier for Aruba 6300M 48SR5 CL6 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.35,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL660A,,,,,,The authoritative identifier for Aruba 6300M 24SR5 CL6 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.36,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL661A,,,,,,The authoritative identifier for Aruba 6300M 48G CL4 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.37,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL662A,,,,,,The authoritative identifier for Aruba 6300M 24G CL4 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.38,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL663A,,,,,,The authoritative identifier for Aruba 6300M 48G 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.39,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL664A,,,,,,The authoritative identifier for Aruba 6300M 24G 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.40,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL665A,,,,,,The authoritative identifier for Aruba 6300F 48G CL4 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.41,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL666A,,,,,,The authoritative identifier for Aruba 6300F 24G CL4 PoE 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.42,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL667A,,,,,,The authoritative identifier for Aruba 6300F 48G 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.43,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL668A,,,,,,The authoritative identifier for Aruba 6300F 24G 4SFP56 Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.44,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL669A,,,,,,The authoritative identifier for Aruba 6300 Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.45,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL085A,,,,,,The authoritative identifier for Aruba X371 12VDC 250W100-240VAC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.46,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL086A,,,,,,The authoritative identifier for Aruba X372 54VDC 680W 100-240VAC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.47,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL087A,,,,,,The authoritative identifier for Aruba X372 54VDC 1050W 110-240VAC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.48,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL670A,,,,,,The authoritative identifier for Aruba X372 54VDC 1600W 110-240VAC Power Supply. 
.1.3.6.1.4.1.47196.4.1.1.2.3.50,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitch50GbMaxPort,,,,,,The authoritative identifier for a 50Gb maximum speed port.
.1.3.6.1.4.1.47196.4.1.1.2.3.51,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X31A,,,,,,The authoritative identifier for the Aruba 6400 Management Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.52,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X32A,,,,,,The authoritative identifier for the Aruba 6400 Fan Tray.
.1.3.6.1.4.1.47196.4.1.1.2.3.53,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X33A,,,,,,The authoritative identifier for the Aruba 6400 C16 Inlet Adapter.
.1.3.6.1.4.1.47196.4.1.1.2.3.54,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X34A,,,,,,The authoritative identifier for the Aruba 6400 C20 Inlet Adapter.
.1.3.6.1.4.1.47196.4.1.1.2.3.55,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X35A,,,,,,The authoritative identifier for the Aruba 6400 1800W Power Supply with C16 Inlet Adapter.
.1.3.6.1.4.1.47196.4.1.1.2.3.56,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X36A,,,,,,The authoritative identifier for the Aruba 6400 3000W Power Supply with C20 Inlet Adapter.
.1.3.6.1.4.1.47196.4.1.1.2.3.57,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X37A,,,,,,The authoritative identifier for the Aruba 6400 4-post Rack Mount Kit.
.1.3.6.1.4.1.47196.4.1.1.2.3.58,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X38A,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 4 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.59,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X39A,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 4 and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.60,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X40A,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 6 and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.61,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X41A,,,,,,The authoritative identifier for the Aruba 6400 48-port HPE Smart Rate PoE Class 6 and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.62,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X42A,,,,,,The authoritative identifier for the Aruba 6400 24-port HPE Smart Rate and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.63,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X43A,,,,,,The authoritative identifier for the Aruba 6400 24-port SFP+ and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.64,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X44A,,,,,,The authoritative identifier for the Aruba 6400 48-port 10/25GbE SFP28 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.65,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X45A,,,,,,The authoritative identifier for the Aruba 6400 12-Port 40/100GbE QSFP28 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.70,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL762A,,,,,,The authoritative identifier for Aruba 6300M 48G 4SFP56 Pwr2Prt Advanced Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.71,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchFanTrayJL761A,,,,,,The authoritative identifier for Aruba 6300M Pwr2Prt Fan Tray. 
.1.3.6.1.4.1.47196.4.1.1.2.3.72,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchPowerSupplyUnitJL760A,,,,,,The authoritative identifier for Aruba X371 12VDC 250W 100-240VAC Power-to-Ports Power Supply.
.1.3.6.1.4.1.47196.4.1.1.2.3.90,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL724A,,,,,,The authoritative identifier for Aruba 6200F 24G 4SFP+ Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.91,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL725A,,,,,,The authoritative identifier for Aruba 6200F 24G CL4 4SFP+370W Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.92,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL726A,,,,,,The authoritative identifier for Aruba 6200F 48G 4SFP+ Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.93,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL727A,,,,,,The authoritative identifier for Aruba 6200F 48G CL4 4SFP+370W Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.94,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL728A,,,,,,The authoritative identifier for Aruba 6200F 48G CL4 4SFP+740W Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.103,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X38B,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 4 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.104,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X39B,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 4 and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.105,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchR0X40B,,,,,,The authoritative identifier for the Aruba 6400 48-port 1GbE PoE Class 6 and 4-port SFP56 Module.
.1.3.6.1.4.1.47196.4.1.1.2.3.350,ARUBAWIRED-NETWORKING-OID::arubaWiredSwitchModuleJL687A,,,,,,The authoritative identifier for Aruba 8400X-32Y 32p 1/10/25G SFP/SFP+/SFP28 Module. 
.1.3.6.1.4.1.47196.4.1.1.3,ARUBAWIRED-NETWORKING-OID::wndFeatures,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1,ARUBAWIRED-NETWORKING-OID::arubaWiredLoopProtectMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtect,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.0,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.0.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectLoopDetectedNotification,,,,,,A arubaWiredLoopProtectLoopDetectedNotification signifies that a loop is detected by the Loop Protection Protocol. Generation of this notification is controlled by arubaWiredLoopProtectTrapLoopDetectEnable. To prevent excessive notifications, this trap allows only one notifications every 30 seconds. Notifications that are missed due to this limitation are dropped and are not sent later.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.0.2,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectVlanLoopDetectedNotification,,,,,,A arubaWiredLoopProtectVlanLoopDetectedNotification signifies that a loop is detected by the Loop Protection feature while operating in VLAN mode. Generation of this notification is controlled by arubaWiredLoopProtectTrapLoopDetectEnable. To prevent excessive notifications, this trap allows only one notifications every 30 seconds. Notifications that are missed due to this limitation are dropped and are not sent later.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectBase,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectInterval,Integer32,read-write,,current,,The interval in seconds at which Loop Protection packets are transmitted. The default value is 5 seconds.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1.2,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectTrapLoopDetectEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether notifications should be sent when a loop is detected on a port. By default this object will have a value of false(2).
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1.3,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectEnableTimer,Integer32,read-write,,current,,The time in seconds to wait before re-enabling a port disabled by Loop Protection. When a port is disabled by Loop Protection, a re-enable timer for the port is initialized. If the re-enable timer value is specified as zero seconds the port remains disabled, else the port is re-enabled after the specified time.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1.4,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectMode,INTEGER,read-write,,current,port(1):vlan(2),This object is used to configure the operational mode of Loop Protection feature. The Loop Protection feature can be configured to operate in port mode or VLAN mode.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.1.5,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectVIDList,OCTET,read-write,,current,,A list of VLANs on which Loop Protection is enabled.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPort,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortTable,,not-accessible,,current,,Per-interface configuration for Loop Protection.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortEntry,,not-accessible,arubaWiredLoopProtectPortInterfaceIndex,current,,Loop Protection configuration information for a single port.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortInterfaceIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.2,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortEnable,INTEGER,read-write,,current,true(1):false(2),This object indicates whether the Loop Protection is enabled on a port. The default value is FALSE
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.3,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortLoopDetected,INTEGER,read-only,,current,true(1):false(2),This object will be set to TRUE when a loop is detected on the port. The value of this object will be reset to FALSE when the port's arubaWiredLoopProtectPortEnable is set to FALSE.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.4,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortLastLoopTime,TimeTicks,read-only,,current,,The value of sysUpTime when a loop was last detected on this port. A value of 0 means that the timestamp has not been set.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.5,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortLoopCount,Counter32,read-only,,current,,This object provides the number of loops detected on a Loop Protection enabled port. The value of this object is set to zero when Loop Protection is disabled on a port.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.6,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortReceiverAction,INTEGER,read-write,,current,disableTx(1):noDisable(2):disableTxRx(3),Controls the action taken when a Loop Protection packet is received on this port. When set to 'disableTx' the port that transmitted the packet is disabled. When set to 'noDisable' the transmitting port is not disabled. When set to 'disableTxRx' the ports transmitting and receiving the packets are disabled.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.7,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectLoopDetectedVlan,Integer32,read-only,,current,,Refers to this object for the port on which loop is detected.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.2.1.1.8,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectPortVlanList,OCTET,read-write,,current,,A list of VLANs for this interface in which Loop Protection is enabled.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3.1,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3.1.4,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectBaseGroup,,,,,,A collection of objects providing basic instrumentation and control of the HP Loop protection entity.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3.1.10,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectVLANGroup,,,,,,A collection of objects providing support for Loop Protect per VLAN feature.
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3.2,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.1.1.5.3.2.5,ARUBAWIRED-LOOPPROTECT-MIB::arubaWiredLoopProtectCompliance,,,,,,The compliance statement for HP Switches with support for arubaWired loop protection objects.
.1.3.6.1.4.1.47196.4.1.1.3.2,ARUBAWIRED-NETWORKING-OID::arubaWiredMclagMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslPort,Integer32,read-write,,obsolete,,IfIndex corresponding to the Mclag InterSwitchLink port. A value of 0 means there is no ISL port configuration.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslHelloInterval,Integer32,read-write,,obsolete,,ISLP hello interval in seconds. The default value is 1.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslHoldTime,Integer32,read-write,,obsolete,,ISL port-flap hold time in seconds. The default value is 0.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.4,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslHelloTimeout,Integer32,read-write,,obsolete,,ISL hello timeout in seconds. The default value is 3.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.5,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslDevicePriority,Integer32,read-write,,obsolete,,Mclags on device with lower value of priority will stay UP in the case of split. The default value is 8.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.6,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslSystemID,OCTET,read-only,,obsolete,,Device identifier. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.7,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslPlatformName,OCTET,read-only,,obsolete,,Device type. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.8,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslSwVersion,OCTET,read-only,,obsolete,,S/W version running on the device type. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.1.9,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslVIDList,OCTET,read-only,,obsolete,,VLAN IDs that the ISL port is a member of.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveSrcIPAddrType,INTEGER,read-write,,obsolete,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The KeepAlive source address type. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveSrcIPAddr,OCTET,read-write,,obsolete,,The KeepAlive source address. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveVrf,OCTET,read-write,,obsolete,,The KeepAlive VRF domain.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.4,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveUdpPort,Integer32,read-write,,obsolete,,The KeepAlive UDP port. Same port is used as source and destination UDP ports.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.5,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePeerIPAddrType,INTEGER,read-write,,obsolete,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The KeepAlive peer address type. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.6,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePeerIPAddr,OCTET,read-write,,obsolete,,The KeepAlive peer address. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.7,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveHelloInterval,Integer32,read-write,,obsolete,,KeepAlive hello interval in seconds. The default value is 1.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.8,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveHelloTimeout,Integer32,read-write,,obsolete,,KeepAlive hello timeout in seconds. The default value is 3.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.9,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveDevicePriority,Integer32,read-only,,obsolete,,Device priority that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.10,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveSystemID,OCTET,read-only,,obsolete,,Device identifier that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.11,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePlatformName,OCTET,read-only,,obsolete,,Device type that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.2.12,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveSwVersion,OCTET,read-only,,obsolete,,S/W version that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagAggregatorConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagAggregatorTable,,not-accessible,,obsolete,,This table supplements the table 'dot3adAggTable' in ieee802.3ad mib.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagAggregatorEntry,,not-accessible,arubaWiredMclagAggregatorIndex,obsolete,,The fields in this entry will be used to supplement fields of dot3adAggEntry in ieee802.3ad mib.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagAggregatorIndex,Integer32,not-accessible,,obsolete,,The unique identifier allocated to this Aggregator by the local System. This attribute identifies an Aggregator instance among the subordinate managed objects of the containing object. This value is read-only.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagAggregatorType,INTEGER,read-create,,obsolete,point2Point(1):multiChassis(2),This field specifies the aggregator/lag type.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagVlanList,OCTET,read-only,,obsolete,,VLANs that this aggregator is a member of. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.4,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagLoopProtectEnabled,INTEGER,read-only,,obsolete,true(1):false(2),Loop Protect protocol admin state for this MCLAG. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.5,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagLoadBalanceScheme,INTEGER,read-only,,obsolete,l2-Src-Dst(1):l3-Src-Dst(2):l4-Src-Dst(3),Load balance scheme configured for this MCLAG. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.6,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagCosOverride,INTEGER,read-only,,obsolete,,CoS override configuration for this MCLAG. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.7,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagDscpOverride,INTEGER,read-only,,obsolete,,DSCP override configuration for this MCLAG. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.1.3.1.1.8,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagQoSTrust,INTEGER,read-only,,obsolete,cos(1):dscp(2),Port QoS trust mode configured for this MCLAG. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.2.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslOperState,INTEGER,read-only,,obsolete,init(1):outSync(2):inSync(3),ISL operational state.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslPduTx,Integer32,read-only,,obsolete,,Number of ISL PDUs transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslPduRx,Integer32,read-only,,obsolete,,Number of ISL PDUs received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.4,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslHelloTx,Integer32,read-only,,obsolete,,Number of ISL Hello packets transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.5,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagIslHelloRx,Integer32,read-only,,obsolete,,Number of ISL Hello packets received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.6,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagDeviceOperRole,INTEGER,read-only,,obsolete,primary(1):secondary(2),Operational role of this device derived based on device priority of the 2 devices.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.1.7,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagDeviceOperSystemID,OCTET,read-only,,obsolete,,System identifier used by this device - derived from system identifier values of the 2 devices.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.1,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveOperState,INTEGER,read-only,,obsolete,initialized(1):configured(2):established(3):failed(4):stopped(5),KeepAlive protocol operational state.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.2,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePacketsTx,Integer32,read-only,,obsolete,,Number of KeepAlive protocol packets transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.3,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePacketsRx,Integer32,read-only,,obsolete,,Number of KeepAlive protocol packets received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.4,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAlivePacketsDrop,Integer32,read-only,,obsolete,,Number of KeepAlive protocol packets dropped.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.5,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveTimeoutCount,Integer32,read-only,,obsolete,,Number of times KeepAlive protocol went to failed state because of KeepAlive timer expiry.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.6,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveLastEstablishedTime,TimeTicks,read-only,,obsolete,,Stores the most recent time KeepAlive handshake was successful and a value of 0 indicates KeepAlive handshake was never established.
.1.3.6.1.4.1.47196.4.1.1.3.2.2.2.7,ARUBAWIRED-MCLAG-MIB::arubaWiredMclagKeepAliveLastFailedTime,TimeTicks,read-only,,obsolete,,Stores the most recent time KeepAlive handshake failed and a value of 0 indicates KeepAlive handshake never failed.
.1.3.6.1.4.1.47196.4.1.1.3.3,ARUBAWIRED-NETWORKING-OID::arubaWiredMgmdSnoopingMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.3.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.3.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingControlDropUnknownMulticast,INTEGER,read-write,,current,true(1):false(2),When enabled along with IGMP Snooping, any IP Multicast packets that are not joined by an IGMP host will be restricted to ports that have detected a multicast router or ports that are configured to always forward IP multicast. When set to disabled or when IGMP Snooping is disabled, the unjoined IP multicast packets will be flooded out all ports in the VLAN. Permanently assigned multicast addresses are always flooded and so are not impacted by this object.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingEnabledVLANCount,Unsigned32,read-only,,current,,Current total count of VLANs with IGMP Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingMcastGroupJoinsCount,Unsigned32,read-only,,current,,Current total count of Multicast groups joined.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingMcastFilteredGroupJoinsCount,Unsigned32,read-only,,current,,Current total count of groups being traced across all VLANs on a per port basis. Traffic for these groups will be filtered to flow only to ports with active joins, subject to hardware resource limitations such as the maximum number of groups supported by the hardware.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingMcastExcludeGroupJoinsCount,Unsigned32,read-only,,current,,Number of multicast groups in the EXCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdIgmpSnoopingMcastIncludeGroupJoinsCount,Unsigned32,read-only,,current,,Number of multicast groups in the INCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingControlDropUnknownMulticast,INTEGER,read-write,,current,true(1):false(2),When enabled along with MLD Snooping, any IPv6 Multicast packets that are not joined by an MLD host will be restricted to ports that have detected a multicast router or ports that are configured to always forward IPv6 multicast. When set to disabled or when MLD Snooping is disabled, the unjoined IPv6 multicast packets will be flooded out all ports in the VLAN. Permanently assigned multicast addresses are always flooded and so are not impacted by this object.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingEnabledVLANCount,Unsigned32,read-only,,current,,Current total count of VLANs with MLD Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.9,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingMcastGroupJoinsCount,Unsigned32,read-only,,current,,Current total count of Multicast groups joined.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.10,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingMcastExcludeGroupJoinsCount,Unsigned32,read-only,,current,,Number of multicast groups in EXCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.11,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingMcastIncludeGroupJoinsCount,Unsigned32,read-only,,current,,Number of multicast groups in INCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.12,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingMcastFilteredGroupJoinsCount,Unsigned32,read-only,,current,,Current total count of groups being traced across all VLANs on a per port basis. Traffic for these groups will be filtered to flow only to ports with active joins, subject to hardware resource limitations such as the maximum number of groups supported by the hardware.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.13,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMldSnoopingSendRouterAlertPaddingOption,INTEGER,read-write,,current,default(1):alternativePadding(2):disabled(3),This enumerated value indicates whether the router alert option has to include padding after option type (1), include padding before option type (2) or should not be sent(3).
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanTable,,not-accessible,,current,,This table object contains the MGMD Snooping VLAN information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntry,,not-accessible,arubaWiredMgmdSnoopingVlanEntryVid:arubaWiredMgmdSnoopingVlanEntryType,current,,An entry in the mgmdSnoopingVlanTable.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which MGMD Snooping is enabled. The table is indexed by the vid value and the InetAddressType to allow for VLANs that may be configured in both IPv4 and IPv6 modes.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this VLAN. This entry along with the vid value acts as the index to the mgmdSnoopingVlanTable. A VLAN may be configured in multiple modes concurrently, e.g., in IPv4 and IPv6 modes connected to the same VLAN; however, the traffic is considered to be logically separate.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntrySnoopingFeature,INTEGER,read-write,,current,true(1):false(2),Turns MGMD Snooping feature on and off.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryControlDropUnknownMulticastStatus,INTEGER,read-only,,current,true(1):false(2),The operational status of the MGMD Snooping Control Unknown Multicast mode. A value of true indicates the mgmdSnoopingVlanEntryControlDropUnknownMulticastStatus setting is operational. A value of false indicates the mgmdSnoopingVlanEntryControlDropUnknownMulticastStatus setting is not operational.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryQuerierPort,Unsigned32,read-only,,current,,Logical port which the querier is connected to. This is determined by the presence of querier packets on this port.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryFilteredJoins,Unsigned32,read-only,,current,,Current total count of groups on this VLAN being tracked on a per port basis. Traffic for these groups will be filtered to flow only to ports with active joins, subject to hardware resource limitations such as the maximum number of groups supported by the hardware.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryPortsWithMcastRouter,OCTET,read-only,,current,,List of multicast router detected ports on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatGeneralQueryRx,Counter32,read-only,,current,,Number of General Queries received by this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.9,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatGSQRx,Counter32,read-only,,current,,Number of Group Specific Queries received by this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.10,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV1ReportRx,Counter32,read-only,,current,,Number of MGMD v1 reports received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.11,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV2ReportRx,Counter32,read-only,,current,,Number of MGMD v2 reports received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.12,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV3ReportRx,Counter32,read-only,,current,,Number of MGMD v3 reports received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.13,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV2LeaveRx,Counter32,read-only,,current,,Number of MGMD V2 Leave Messages received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.14,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatUnknownTypeRx,Counter32,read-only,,current,,Number of Unknown type MGMD packets received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.15,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatForwardToRoutersTx,Counter32,read-only,,current,,Number of packets forwarded to router detected ports on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.16,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatForwardToAllPortsTx,Counter32,read-only,,current,,Number of packets sent out on all ports of this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.17,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatJoinTimeouts,Counter32,read-only,,current,,Number of times joins got timed out on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.18,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStaticJoins,Unsigned32,read-only,,current,,Total count of user created static groups on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.19,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryOtherQuerierInterval,Unsigned32,read-only,,current,,The length of time that must pass before a multicast router decides that there is no longer another multicast router which should be the querier. This value MUST be ((the Robustness Variable) times (the Query Interval)) plus (one half of one Query Response Interval).
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.20,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryOtherQuerierExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before a multicast router decides that there is no longer another multicast router which should be the querier.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.21,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryOtherQuerierRobustness,Unsigned32,read-only,,current,,The Robustness Variable allows tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the Robustness Variable may be increased. MGMD is robust to (Robustness Variable-1) packet losses.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.22,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatExcludeGroupJoinsCount,Counter32,read-only,,current,,Current number of groups on this VLAN which are in EXCLUDE mode 
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.23,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatIncludeGroupJoinsCount,Counter32,read-only,,current,,Current number of groups on this VLAN which are in INCLUDE mode 
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.24,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatFilteredExcludeGroupJoinsCount,Counter32,read-only,,current,,Current number of filtered groups on this VLAN which are in EXCLUDE mode 
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.25,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatFilteredIncludeGroupJoinsCount,Counter32,read-only,,current,,Current number of filtered groups on this VLAN which are in INCLUDE mode 
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.26,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV1QueryRx,Counter32,read-only,,current,,The number of V1 Queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.27,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV2QueryRx,Counter32,read-only,,current,,The number of V2 Queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.28,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV3QueryRx,Counter32,read-only,,current,,The number of V3 Queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.29,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatGSSQRx,Counter32,read-only,,current,,The number of Group Source Specific Queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.30,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatMalformedPktRx,Counter32,read-only,,current,,The number of malformed packets received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.31,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatBadCheckSumRx,Counter32,read-only,,current,,The number of bad checksum packets received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.32,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatMartianSourceRx,Counter32,read-only,,current,,The number of packets received on this VLAN from Martian source. Martian source are the packets with invalid source address, e.g 255.255.255.255
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.33,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatPacketsRxOnDisabled,Counter32,read-only,,current,,The number of MGMD packets received on this VLAN when MGMD is disabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.34,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV2GSQRx,Counter32,read-only,,current,,The number of MGMD V2 group specific queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.35,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatV3GSQRx,Counter32,read-only,,current,,The number of MGMD V2 group specific queries received on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.14.1.36,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryStatWrongVersionQueries,Counter32,read-only,,current,,The number of general queries received whose MGMD version does not match the equivalent VLAN Version.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheTable,,not-accessible,,current,,The table listing the IP multicast groups for which there are members on a particular VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheEntry,,not-accessible,arubaWiredMgmdSnoopingCacheVid:arubaWiredMgmdSnoopingCacheAddressType:arubaWiredMgmdSnoopingCacheAddress,current,,An entry in the arubaWiredMgmdSnoopingCacheTable.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheVid,Unsigned32,not-accessible,,current,,The VLAN for which this entry contains information for an IP multicast group address.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheSelf,INTEGER,read-create,,current,true(1):false(2),An indication of whether the local system is a member of this group address on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheLastReporter,OCTET,read-only,,current,,The IP address of the source of the last membership report received for this IP Multicast group address on this VLAN. If no membership report has been received, this object has the value 0.0.0.0. or 0::0
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. A value of 0 indicates that the entry is only present because arubaWiredMgmdSnoopingCacheSelf is true and that if the router left the group, this entry would be aged out immediately. Note that some implementations may process Membership Reports from the local system in the same way as reports from other hosts, so a value of 0 is not required.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheGroupType,INTEGER,read-create,,current,filtered(1):static(2),Reference MgmdSnoopingGroupTypeDefinition will indicate the type of group.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.9,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheJoinedPorts,OCTET,read-only,,current,,Logical ports with active MGMD joins on them for this entry. For Filtered groups this will be the logical ports which have active joins. For static groups this will include all logical ports on the VLAN running MGMD Snooping.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.10,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or existing entries deleted from this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.11,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheQueriesRcvd,Counter32,read-only,,current,,This represents the number of MGMD queries received for this group.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.12,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheJoinsRcvd,Counter32,read-only,,current,,This represents the number of MGMD Reports received for this group.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.13,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheFilterMode,INTEGER,read-only,,current,include(1):exclude(2),The value indicates whether the group state is the INCLUDE(1)/ EXCLUDE(2).
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.14,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheExcludeModeExpiryTimer,TimeTicks,read-only,,current,,The time remaining before the group in EXCLUDE state expires and transitions to INCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.15,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheVersion1HostTimer,TimeTicks,read-only,,current,,The time remaining after which the local router will assume that there are no longer any MGMD version 1 members on the IP subnet attached to this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.16,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheVersion2HostTimer,TimeTicks,read-only,,current,,The time remaining after which the local router will assume that there are no longer any MGMD version 2 members on the IP subnet attached to this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.15.1.17,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheSrcCount,Counter32,read-only,,current,,The number of sources either included or excluded from this group. If V1 host timer (arubaWiredMgmdSnoopingCacheVersion1HostTimer) or V2 host timer (arubaWiredMgmdSnoopingCacheVersion2HostTimer) is Active, this value will be zero.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.16,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortConfigTable,,not-accessible,,current,,This table contains information about the MGMD Snooping port configurations on this switch.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.16.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortConfigEntry,,not-accessible,arubaWiredMgmdSnoopingPortConfigEntryVid:arubaWiredMgmdSnoopingPortConfigEntryIndex,current,,An entry in the arubaWiredMgmdSnoopingPortConfigEntry.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.16.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortConfigEntryVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which MGMD Snooping is enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.16.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortConfigEntryIndex,Unsigned32,not-accessible,,current,,The index value which uniquely identifies a row in the VLAN Table for a port or trunk.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.16.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortConfigEntryPortModeFeature,INTEGER,read-write,,current,auto(1):blocked(2):forward(3),The operational status of the MGMD Snooping feature for this port or trunk. 1 implies that all IP Multicast traffic will be monitored on the port, 2 implies that IP Multicast traffic will be dropped on the port, and 3 implies that all IP Multicast traffic will be forwarded without the switch examining it.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheTable,,not-accessible,,current,,This table contains information about the MGMD Snooping port configurations on this switch.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheEntry,,not-accessible,arubaWiredMgmdSnoopingFilteredGroupPortCacheVid:arubaWiredMgmdSnoopingFilteredGroupPortCacheGroupAddressType:arubaWiredMgmdSnoopingFilteredGroupPortCacheGroupAddress:arubaWiredMgmdSnoopingFilteredGroupPortCachePortIndex,current,,An entry in the arubaWiredMgmdSnoopingFilteredGroupPortCacheEntry.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which MGMD Snooping is enabled and for which this filtered group exists.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheGroupAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheGroupAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCachePortIndex,Unsigned32,not-accessible,,current,,The index value which uniquely identifies a row in the VLAN Table for a port or trunk.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.17.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListTable,,not-accessible,,current,,This table provides MGMD Snooping information for each Source entry.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListEntry,,not-accessible,arubaWiredMgmdSnoopingSrcListVid:arubaWiredMgmdSnoopingSrcListAddressType:arubaWiredMgmdSnoopingSrcListAddress:arubaWiredMgmdSnoopingSrcListHostAddress,current,,An entry in the arubaWiredMgmdSnoopingSrcListEntry.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which this entry contains information for an IPv4 or IPv6 multicast group address.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListAddress,OCTET,not-accessible,,current,,The IPv4 or IPv6 multicast group address for which this entry contains information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListHostAddress,OCTET,not-accessible,,current,,The source address to which this entry corresponds.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListPorts,OCTET,read-only,,current,,List of ports for which this source entry is either excluded or included.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListExpiry,TimeTicks,read-only,,current,,This value indicates the relevance of the SrcList entry, whereby a non-zero value indicates that is an INCLUDE state value, and a zero value indicates this to be an EXCLUDE state value.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.18.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListType,INTEGER,read-only,,current,filtered(1):static(2),See MgmdSnoopingGroupTypeDefinition description. 
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcTable,,not-accessible,,current,,This table contains information about the MGMD Snooping PortSrc configurations on this switch.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcEntry,,not-accessible,arubaWiredMgmdSnoopingPortSrcVid:arubaWiredMgmdSnoopingPortSrcAddressType:arubaWiredMgmdSnoopingPortSrcAddress:arubaWiredMgmdSnoopingPortSrcHostAddress:arubaWiredMgmdSnoopingPortSrcPortIndex,current,,An entry in the arubaWiredMgmdSnoopingPortSrcTable.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which this entry contains information for an IPv4 or IPv6 multicast group address.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcAddress,OCTET,not-accessible,,current,,The IPv4 or IPv6 multicast group address for which this entry contains information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcHostAddress,OCTET,not-accessible,,current,,The host address to which this entry corresponds.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcPortIndex,Unsigned32,not-accessible,,current,,The index value that uniquely identifies a row in the PortSrc table for a port or trunk.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcExpiry,TimeTicks,read-only,,current,,This value indicates the relevance of the SrcList entry, whereby a non-zero value indicates this is an INCLUDE state value, and a zero value indicates this to be an EXCLUDE state value.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.19.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcFilterMode,INTEGER,read-only,,current,include(1):exclude(2),The value indicates whether the port state is the INCLUDE(1)/ EXCLUDE(2).
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheTable,,not-accessible,,current,,This table contains information about the MGMD Snooping port configurations on this switch.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheEntry,,not-accessible,arubaWiredMgmdSnoopingGroupPortCacheVid:arubaWiredMgmdSnoopingGroupPortCacheGroupAddressType:arubaWiredMgmdSnoopingGroupPortCacheGroupAddress:arubaWiredMgmdSnoopingGroupPortCachePortIndex,current,,An entry in the arubaWiredMgmdSnoopingGroupPortCacheTable.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheVid,Unsigned32,not-accessible,,current,,The vid value of the VLAN for which MGMD Snooping is enabled and for which this group exists.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheGroupAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheGroupAddress,OCTET,not-accessible,,current,,The IPv4 or IPv6 multicast group address for which this entry contains information.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCachePortIndex,Unsigned32,not-accessible,,current,,The index value which uniquely identifies a row in the VLAN Table for a port or trunk.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheVersion1Timer,TimeTicks,read-only,,current,,The time remaining until the local router will assume that there are no longer any MGMD version 1 members on this port.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheVersion2Timer,TimeTicks,read-only,,current,,The time remaining until the local router will assume that there are no longer any MGMD version 2 members on this port.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheFilterTimer,TimeTicks,read-only,,current,,The time remaining before the port in EXCLUDE state expires and transitions to INCLUDE mode.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.9,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheFilterMode,INTEGER,read-only,,current,include(1):exclude(2),The value indicates whether the port state is the INCLUDE(1)/ EXCLUDE(2).
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.10,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheExcludeSrcCount,Counter32,read-only,,current,,Current number of sources excluded from this port.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.11,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheRequestedSrcCount,Counter32,read-only,,current,,Current number of sources requested from this port.
.1.3.6.1.4.1.47196.4.1.1.3.3.1.20.1.12,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroupPortCacheExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out.
.1.3.6.1.4.1.47196.4.1.1.3.3.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingBaseGroup,,,,,,A collection of objects to support MGMD Snooping feature.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingVlanEntryGroup,,,,,,A collection of objects to support management of VLAN with MGMD Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.3,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCacheGroup,,,,,,A collection of objects to support management of VLAN with MGMD Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.4,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortGroup,,,,,,A collection of objects to support management of VLAN with MGMD Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.5,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingFilteredGroupPortCacheGroup,,,,,,A collection of objects to support management of VLAN with MGMD Snooping enabled.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.6,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingSrcListGroup,,,,,,A collection of objects to support Source entries corresponding to each VLAN and multicast group pair.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.7,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingPortSrcGroup,,,,,,A collection objects for an entry in the MGMD PortSrc Table.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.1.8,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingGruoupPortCacheGroup,,,,,,A collection of objects associated with each MGMD Snooping port configuration.
.1.3.6.1.4.1.47196.4.1.1.3.3.2.2,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdSnoopingCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.3.2.2.1,ARUBAWIRED-MGMD-SNOOPING-MIB::arubaWiredMgmdMIBCompliance,,,,,,The compliance statement for HPE routers running MGMD Snooping and implementing the MGMD Snooping MIB.
.1.3.6.1.4.1.47196.4.1.1.3.4,ARUBAWIRED-NETWORKING-OID::arubaWiredMgmdRmonTrapMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.4.1,ARUBAWIRED-MGMD-RMON-TRAP-MIB::arubaWiredMgmdRmonTrapNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.4.1.1,ARUBAWIRED-MGMD-RMON-TRAP-MIB::arubaWiredMgmdRmonTrapEvent,,,,,,The event ID for which the trap is set has occured.
.1.3.6.1.4.1.47196.4.1.1.3.5,ARUBAWIRED-NETWORKING-OID::arubaWiredRpvstMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.0,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.0.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstErrantBpduReceived,,,,,,This Trap is generated when an unexpected (errant) BPDU has been received on a port.
.1.3.6.1.4.1.47196.4.1.1.3.5.0.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNewRoot,,,,,,Trap generated when sending agent has become the new root of spanning Tree for the specified VLAN; the notification is sent by a bridge soon after its election as the new root.
.1.3.6.1.4.1.47196.4.1.1.3.5.0.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstRootGuardInconsistency,,,,,,Trap generated when a Root Guard feature enabled port receives superior BPDUs on its interface for a given instance.
.1.3.6.1.4.1.47196.4.1.1.3.5.0.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstLoopGuardInconsistency,,,,,,Trap generated when a Loop Guard feature enabled port receives superior BPDUs on its interface for a given instance.
.1.3.6.1.4.1.47196.4.1.1.3.5.0.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstTopologyChange,,,,,,Trap is generated when a Topology Change is detected in the specified VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstGeneralGroup,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.1.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstResetCounters,INTEGER,read-write,,current,true(1):false(2), Setting this object to true(1) will reset all the RPVST counters. Setting this to false(2) is no operation.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstExtendedSystemID,INTEGER,read-write,,current,true(1):false(2), Creates a unique bridge identifier for each VLAN by adding the VLAN ID (vid) value to the priority field of the bridge identifier in every RPVST BPDU. Indicates whether Extended System ID feature is enabled or not.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstIgnorePVIDInconsistency,INTEGER,read-write,,current,true(1):false(2),Setting this object to True(1) will enable RPVST to run on mismatched PVID links.Once set it will apply to all RPVST instances
.1.3.6.1.4.1.47196.4.1.1.3.5.1.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPathCostMode,INTEGER,read-write,,current,pathCost8021d(1):pathCost8021t(2):proprietary(3),arubaWiredRpvstPathCostMode controls which pathcost mode to use. A device can function in one of the 3 modes defined below. pathCost8021d - The device calculates the default path cost for ports based on IEEE 802.1d. pathCost8021t - The device calculates the default path cost for ports based on IEEE 802.1t. proprietary -The device calculates the default path cost for ports based on the proprietary standard. Link Speed Vs Pathcost Table ---------------------------------------------------------- |Link speed| Pathcost in | Pathcost in | Pathcost in | | | IEEE802.1d | IEEE 802.1t | private standard| ---------------------------------------------------------- | 10 Mbps | 100 | 2,000,000 | 100 | ---------------------------------------------------------- | 100 Mbps | 10 | 200,000 | 19 | ---------------------------------------------------------- | 1000 Mbps| 4 | 20,000 | 4 | ---------------------------------------------------------- | 10 Gbps | 1 | 2,000 | 2 | ---------------------------------------------------------- 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanTable,,not-accessible,,current,,Information describing the RPVST configuration and statistics of the VLANs.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanEntry,,not-accessible,arubaWiredRpvstVlanId,current,,Information describing the RPVST configuration and statistics of each of the VLANs.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanId,Unsigned32,not-accessible,,current,,A VLAN ID to uniquely identify the entries. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanHelloTime,Integer32,read-write,,current,, The amount of time between the transmission of configuration BPDUs by this node on any port in this VLAN when it is root of the spanning tree, or trying to become so for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanForwardDelay,Integer32,read-write,,current,, The amount of time between transitioning from listening to learning and learning to forwarding by this node on any port when it is acting as a root for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanMaxAge,Integer32,read-write,,current,, The maximum age of RPVST information learned from the network on any port before it is discarded.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanPriority,Integer32,read-write,,current,,The value of the write-able portion of the Bridge ID (i.e., the first two octets of the (8 octet long) Bridge ID). The other (last) 6 octets of the Bridge ID are given by the value dot1dBridgeBaseAddress.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.6,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRoot,INTEGER,read-write,,current,none(0):primary(1):secondary(2), To explicitly configure this switch to be primary/secondary root for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.7,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRpvstAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2), To enable/disable RPVST on the VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.8,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanResetCounters,INTEGER,read-write,,current,true(1):false(2), Setting this object to true(1) will reset the RPVST counters for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.9,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanOperHelloTime,Integer32,read-only,,current,, The amount of time between the transmission of BPDUs by this node on any port in this VLAN when it is root of the spanning tree, or trying to become so for this VLAN. This is the actual value that this bridge is using.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.10,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRootPriority,Integer32,read-only,,current,,The priority of root bridge in this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.11,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRootPort,Integer32,read-only,,current,,The root port for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.12,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRootPathCost,Integer32,read-only,,current,,The path cost to the Root from this bridge in this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.13,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRootMacAddress,OCTET,read-only,,current,,MAC address of the Root in this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.14,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanRootChangeCounter,Counter32,read-only,,current,,The number of times the root has changed for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.15,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanTimeSinceLastTopoChange,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.16,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanTopoChangeCount,Counter32,read-only,,current,,The total number of topology changes detected by this bridge in this VLAN since the management entity was last reset or initialized.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.17,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanSendTopoChangeCtrl,INTEGER,read-write,,current,true(1):false(2),Setting this object to true(1) will enable sending of SNMP notifications for all topology change events on this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.2.1.18,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanLogPortStateTransitions,INTEGER,read-write,,current,true(1):false(2),Setting this object to true(1) will enable event logging of PVST port state transitions for this VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortTable,,not-accessible,,current,,Information describing the RPVST specific configuration and statistics of the ports.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortEntry,,not-accessible,arubaWiredRpvstPortIndex,current,,Information describing the RPVST specific configuration and statistics of the ports.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortIndex,Integer32,not-accessible,,current,, The port ifIndex 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortAdminEdge,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Edge Port parameter. A value of true(1) indicates that this port should be assumed as an edge-port, and a value of false(2) indicates that this port should be assumed as a non-edge-port. Note that even when this object's value is true(1), the arubaWiredRpvstOperEdgePort can be false(2) if a BPDU has been received.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortAdminPointToPoint,INTEGER,read-write,,current,forceTrue(1):forceFalse(2):auto(3),Refer the PointToPoint textual-convention.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortAutoEdge,INTEGER,read-write,,current,true(1):false(2),It is used by the Bridge detection state machine for the automatic identification of edge ports. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortBpduFiltering,INTEGER,read-write,,current,true(1):false(2),This value indicates whether or not BPDUs need to be filtered on this port and BPDU filter option forces a port to always stay in the forwarding state and be excluded from standard STP operation. If the value is true(1) the received BPDUs will be dropped and no BPDUs will be transmitted on the port. If the value is false (2) the BPDUs will be processed as usual. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.6,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortRestrictedTcn,INTEGER,read-write,,current,true(1):false(2), This value indicates whether or not to propagate topology changes to other ports. true(1) causes the port not to propagate topology changes to other ports.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.7,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortRootGuard,INTEGER,read-write,,current,true(1):false(2), Setting this object to true(1) forces port to not to be selected as root port even if this port has the least path cost to the root. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.8,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortLoopGuard,INTEGER,read-write,,current,true(1):false(2), Setting this object to true(1) causes the non-designated port to go into the STP loop inconsistent state instead of the forwarding state. In the loop-inconsistent state, the port prevents data traffic through the link, therefore avoiding the loop creation. When BPDUs again are received on the inconsistent port, it resumes normal STP operation automatically. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.3.1.9,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortBpduProtection,INTEGER,read-write,,current,true(1):false(2), Setting this true (1) indicates that no BPDUs are expected to be received on this port. At the reception of BPDUs the BPDU protection mechanism will disable this port and port will transition into BPDU Error state.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanTable,,not-accessible,,current,,Information describing the RPVST configuration and statistics of the ports in the given VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanEntry,,not-accessible,arubaWiredRpvstPortVlanId:arubaWiredRpvstPortVlanIndex,current,,Information describing the RPVST configuration and statistics of the ports in the given VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanId,Unsigned32,not-accessible,,current,,A VLAN ID to uniquely identify the entries. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanIndex,Integer32,not-accessible,,current,, The port ifIndex 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanPathCost,Integer32,read-write,,current,, The contribution of this port to the path cost of paths towards the root which include this port. auto(0) 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanPriority,Integer32,read-write,,current,,The value of the port priority field that is contained in the first (in network byte order) octet of the (2 octet long) Port ID. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanResetCounters,INTEGER,read-write,,current,true(1):false(2), Setting this object to true(1) will reset the RPVST counters for this port-vlan pair. Get on this object will always return false(2)
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.6,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanRole,INTEGER,read-only,,current,root(1):alternate(2):designated(3):backup(4):master(5):disabled(6), Role played by the port in a given VLAN.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.7,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanState,INTEGER,read-only,,current,disabled(1):blocking(2):listening(3):learning(4):forwarding(5):broken(6):bpduError(7):loopInconsistent(8):pvidInconsistent(9):rootGuard(10),The port's current state. This state controls what action a port takes on reception of a frame.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.8,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanDesigBridge,OCTET,read-only,,current,, The Bridge Identifier of the bridge that this port considers to be the Designated Bridge for this port's segment.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.9,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanOperPointToPoint,INTEGER,read-only,,current,true(1):false(2), true : This value indicates that the MAC is connected to a point-to-point LAN segment; i.e., there is at most one other system attached to the LAN segment. false: This value indicates that the MAC is connected to a non-point-to-point LAN segment; i.e., there can be more than one other system attached to the LAN segment.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.10,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanOperEdge,INTEGER,read-only,,current,true(1):false(2),The operational status of the edge port parameter. A value of true(1) indicates that this port should be assumed as an edge-port, and a value of false(2) indicates that this port should be assumed as a non-edge-port. 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.4.1.11,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanInconsistencyReason,INTEGER,read-only,,current,rootProtected(1):loopProtected(2):inconsistentPvidProtected(3),The reason for which port is blocked by spanning tree protection function.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotificationTable,,not-accessible,,current,,Information describing the Rpvst configuration and statistics of the Ports and Vlans.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotificationEntry,,not-accessible,arubaWiredRpvstId,current,,Information describing the Rpvst events for trap generation.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortName,OCTET,accessible-for-notify,,current,,Port name 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanIndex,Integer32,accessible-for-notify,,current,,VLAN ID 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanErrantBpduRxCount,Integer32,accessible-for-notify,,current,,The number of BPDUs received on a BPDU-filtering or BPDU-protected enabled port.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstErrantBpduSrcMac,OCTET,accessible-for-notify,,current,,The source MAC address of the port sending Errant BPDU.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstSuperiorBpduSrcPort,OCTET,accessible-for-notify,,current,,The name of the port sending superior BPDU
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.6,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstSuperiorBpduSrcMac,OCTET,accessible-for-notify,,current,,The MacAddress of the port sending superior BPDU
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.7,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstErrantBpduDetector,INTEGER,accessible-for-notify,,current,bpduFilter(1):bpduProtection(2),The identifier of the feature generating Errant BPDU trap.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.8,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstDesignatedPort,OCTET,accessible-for-notify,,current,,Designated Port of the Bridge.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.9,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstOldPortRole,OCTET,accessible-for-notify,,current,,Old Port state 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.10,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNewPortRole,OCTET,accessible-for-notify,,current,,new port state 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.11,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstTopoChangeTime,OCTET,accessible-for-notify,,current,,Topology change time 
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.12,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPreviousRootBridgeID,OCTET,accessible-for-notify,,current,,Bridge ID of the previous Root. Bridge Id consists of priority and MAC address.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.13,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNewRootBridgeID,OCTET,accessible-for-notify,,current,,Bridge ID of the new Root. Bridge Id consists of priority and MAC address.
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.14,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstRootBridgeChangeTimeStamp,OCTET,accessible-for-notify,,current,,Time when the root changed
.1.3.6.1.4.1.47196.4.1.1.3.5.1.5.1.15,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstId,Integer32,not-accessible,,current,,VLAN ID
.1.3.6.1.4.1.47196.4.1.1.3.5.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstGroup,,,,,,These objects are used for managing/monitoring RPVST global parameters.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstVlanGroup,,,,,,These objects are used for managing/monitoring RPVST VLAN parameters.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortVlanGroup,,,,,,These objects are used for managing/monitoring RPVST port parameters for the VLANs.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.4,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPortGroup,,,,,,These objects are used for managing/monitoring RPVST port parameters
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.5,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstPvst1,,,,,,Group of object added part of pvst1.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.6,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotificationObjectGrp,,,,,,Group of objects required for notifications.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.1.7,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotificationGroup,,,,,,Group of notifications.
.1.3.6.1.4.1.47196.4.1.1.3.5.2.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.5.2.2.1,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstCompliance1,,,,,,The compliance statement
.1.3.6.1.4.1.47196.4.1.1.3.5.2.2.2,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstCompliance2,,,,,,The compliance statement
.1.3.6.1.4.1.47196.4.1.1.3.5.2.2.3,ARUBAWIRED-RPVST-MIB::arubaWiredRpvstNotificationCompliance,,,,,,The compliance statement for Rpvst extension notifications.
.1.3.6.1.4.1.47196.4.1.1.3.6,ARUBAWIRED-NETWORKING-OID::arubaWiredMvrpMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.0,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.0.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpVlanLimitReachedEvent,,,,,,The number of VLANs learned dynamically by MVRP has reached a configured limit. Notify the management entity with the number of VLANs learned dynamically by MVRP and the configured MVRP VLAN limit.
.1.3.6.1.4.1.47196.4.1.1.3.6.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpGlobalClearStats,INTEGER,read-write,,current,true(1):false(2),Defines the global clear statistics control for MVRP. True(1) indicates that MVRP should clear all statistic counters related to all ports in the system. A write operation of False(0) leads to a no operation and a GET request for this object always returns FALSE.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpMaxVlanLimit,Integer32,read-write,,current,,Defines the maximum number of dynamic VLANs that can be created on the system by MVRP. If the number of VLANs created by MVRP reaches this limit, the system will prevent MVRP from creating additional VLANs. A write operation for this object is not supported.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigTable,,not-accessible,,current,,A table containing MVRP port configuration information.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigEntry,,not-accessible,arubaWiredMvrpPortConfigifIndex,current,,An MVRP port configuration entry.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigifIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigRegistrarMode,INTEGER,read-write,,current,normal(1):fixed(2),Defines the mode of operation of all the registrar state machines associated to the port. normal - Registration as well as de-registration of VLANs are allowed. fixed - The Registrar ignores all MRP messages and remains in IN state(Registered). NOTE: Forbidden Registration Mode will be managed by ieee8021QBridgeVlanForbiddenEgressPorts.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigPeriodicTimer,Gauge32,read-write,,current,,Interval at which the Periodic transmission state machine of an MVRP instance generates transmission opportunities for the MVRP instance.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1.4,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigPeriodicTransmissionStatus,INTEGER,read-write,,current,enabled(1):disabled(2),Used to enable or disable the Periodic transmission state machine of an MVRP instance.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.1.3.1.5,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsClearStats,INTEGER,read-write,,current,true(1):false(2),Clear all statistics parameters corresponding to this port. True(1) indicates that MVRP will clear all statistic counters related to this port. A write operation of False(0) leads to a no operation and a GET request for this object always returns FALSE.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpStats,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsTable,,not-accessible,,current,,A table containing MVRP port statistics information.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsEntry,,not-accessible,arubaWiredMvrpPortStatsifIndex,current,,An MVRP port statistics entry.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsifIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsNewReceived,Counter32,read-only,,current,,The number of New messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsJoinInReceived,Counter32,read-only,,current,,The number of Join In messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.4,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsJoinEmptyReceived,Counter32,read-only,,current,,The number of Join Empty messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.5,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsLeaveReceived,Counter32,read-only,,current,,The number of Leave messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.6,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsInReceived,Counter32,read-only,,current,,The number of In messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.7,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsEmptyReceived,Counter32,read-only,,current,,The number of Empty messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.8,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsLeaveAllReceived,Counter32,read-only,,current,,The number of Leave all messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.9,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsNewTransmitted,Counter32,read-only,,current,,The number of New messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.10,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsJoinInTransmitted,Counter32,read-only,,current,,The number of Join In messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.11,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsJoinEmptyTransmitted,Counter32,read-only,,current,,The number of Join Empty messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.12,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsLeaveTransmitted,Counter32,read-only,,current,,The number of Leave messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.13,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsInTransmitted,Counter32,read-only,,current,,The number of In messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.14,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsEmptyTransmitted,Counter32,read-only,,current,,The number of Empty messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.15,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsLeaveAllTransmitted,Counter32,read-only,,current,,The number of Leave all messages transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.16,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsTotalPDUReceived,Counter32,read-only,,current,,The total number of MVRP PDUs received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.17,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsTotalPDUTransmitted,Counter32,read-only,,current,,The total number of MVRP PDUs transmitted.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.1.1.18,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsFramesDiscarded,Counter32,read-only,,current,,The number of Invalid messages received.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpStateTable,,not-accessible,,current,,A table that contains information about the MVRP state Machine(s) configuration.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpStateEntry,,not-accessible,arubaWiredMvrpVlanId:arubaWiredMvrpStateifIndex,current,,A row in a table that contains the VLAN ID and port list.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpVlanId,Integer32,not-accessible,,current,,The VLAN ID to which this entry belongs.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2.1.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpStateifIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2.1.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpApplicantState,INTEGER,read-only,,current,aa(0):qa(1):la(2):vp(3):ap(4):qp(5):vo(6):ao(7):qo(8):lo(9):vn(10):an(11), This MIB provides the Applicant State Machine values of the MVRP enabled port as follows: 0 = aa, 1 = qa, 2 = la, 3 = vp, 4 = ap, 5 = qp, 6 = vo, 7 = ao, 8 = qo, 9 = lo, 10 = vn, 11 = an. The first letter indicates the state: V for Very anxious, A for Anxious, Q for Quiet, and L for Leaving. The second letter indicates the membership state: A for Active member, P for Passive member, O for Observer and N for New.
.1.3.6.1.4.1.47196.4.1.1.3.6.1.2.2.1.4,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpRegistrarState,INTEGER,read-only,,current,in(1):lv(2):mt(3),This MIB provides the Registrar state machine value for the MVRP enabled port as follows: 1 = registered, 2 = leaving, 3 = empty.
.1.3.6.1.4.1.47196.4.1.1.3.6.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.3.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.3.1.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpCompliance,,,,,,Compliance statement for MVRP.
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2.1,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpBaseGroup,,,,,,Collection of objects for management of MVRP Base Group.
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2.2,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortConfigGroup,,,,,,Collection of objects for management of MVRP Port Configuration Table.
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2.3,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStatsGroup,,,,,,Collection of objects for management of MVRP Statistics Table.
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2.4,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpPortStateGroup,,,,,,Collection of objects to display Applicant and Registrar state machine of the ports.
.1.3.6.1.4.1.47196.4.1.1.3.6.3.2.5,ARUBAWIRED-MVRP-MIB::arubaWiredMvrpNotifyGroup,,,,,,MVRP notification group.
.1.3.6.1.4.1.47196.4.1.1.3.7,ARUBAWIRED-NETWORKING-OID::arubaWiredVsxMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslPort,OCTET,read-write,,current,,Interface name corresponding to the VSX InterSwitchLink port. A value of 0 means there is no ISL port configuration.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslHelloInterval,Integer32,read-write,,current,,ISLP hello interval in seconds. The default value is 1.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslHoldTime,Integer32,read-write,,current,,ISL port-flap hold time in seconds. The default value is 0.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslHelloTimeout,Integer32,read-write,,current,,ISL hello timeout in seconds. The default value is 3.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.5,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslSystemID,OCTET,read-only,,current,,Device identifier. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.6,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslPlatformName,OCTET,read-only,,current,,Device type. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.7,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslSwVersion,OCTET,read-only,,current,,S/W version running on the device type. This is advertised over ISL.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.1.8,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslVIDList,OCTET,read-only,,current,,VLAN IDs that the ISL port is a member of.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveSrcIPAddrType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The KeepAlive source address type. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveSrcIPAddr,OCTET,read-write,,current,,The KeepAlive source address. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveVrf,OCTET,read-write,,current,,The KeepAlive VRF domain.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveUdpPort,Integer32,read-write,,current,,The KeepAlive UDP port. Same port is used as source and destination UDP ports.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.5,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePeerIPAddrType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The KeepAlive peer address type. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.6,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePeerIPAddr,OCTET,read-write,,current,,The KeepAlive peer address. It can be IPv4 or IPv6.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.7,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveHelloInterval,Integer32,read-write,,current,,KeepAlive hello interval in seconds. The default value is 1.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.8,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveHelloTimeout,Integer32,read-write,,current,,KeepAlive hello timeout in seconds. The default value is 3.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.9,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveSystemID,OCTET,read-only,,current,,Device identifier that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.10,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePlatformName,OCTET,read-only,,current,,Device type that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.2.11,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveSwVersion,OCTET,read-only,,current,,S/W version that will be advertised via KeepAlive protocol.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxAggregatorConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxAggregatorTable,,not-accessible,,current,,This table supplements the table 'dot3adAggTable' in ieee802.3ad mib.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxAggregatorEntry,,not-accessible,arubaWiredVsxAggregatorIndex,current,,The fields in this entry will be used to supplement fields of dot3adAggEntry in ieee802.3ad mib.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxAggregatorIndex,Integer32,not-accessible,,current,,The unique identifier allocated to this Aggregator by the local System. This attribute identifies an Aggregator instance among the subordinate managed objects of the containing object. This value is read-only.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxAggregatorType,INTEGER,read-create,,current,point2Point(1):multiChassis(2),This field specifies the aggregator/lag type.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxVlanList,OCTET,read-only,,current,,VLANs that this aggregator is a member of. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxLoopProtectEnabled,INTEGER,read-only,,current,true(1):false(2),Loop Protect protocol admin state for this VSX. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.5,ARUBAWIRED-VSX-MIB::arubaWiredVsxLoadBalanceScheme,INTEGER,read-only,,current,l2-Src-Dst(1):l3-Src-Dst(2):l4-Src-Dst(3),Load balance scheme configured for this VSX. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.6,ARUBAWIRED-VSX-MIB::arubaWiredVsxCosOverride,INTEGER,read-only,,current,,CoS override configuration for this VSX. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.7,ARUBAWIRED-VSX-MIB::arubaWiredVsxDscpOverride,INTEGER,read-only,,current,,DSCP override configuration for this VSX. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.3.1.1.8,ARUBAWIRED-VSX-MIB::arubaWiredVsxQoSTrust,INTEGER,read-only,,current,cos(1):dscp(2),Port QoS trust mode configured for this VSX. This is used for configuration consistency validation.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxGlobalConfiguration,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.1.4.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxDeviceRole,INTEGER,read-only,,current,primary(1):secondary(2):notConfigured(3),VSX device role.
.1.3.6.1.4.1.47196.4.1.1.3.7.1.4.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxConfigSync,INTEGER,read-only,,current,enabled(1):disabled(2),VSX config sync.
.1.3.6.1.4.1.47196.4.1.1.3.7.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslOperState,INTEGER,read-only,,current,init(1):outSync(2):inSync(3),ISL operational state.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslPduTx,Integer32,read-only,,current,,Number of ISL PDUs transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslPduRx,Integer32,read-only,,current,,Number of ISL PDUs received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslHelloTx,Integer32,read-only,,current,,Number of ISL Hello packets transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.5,ARUBAWIRED-VSX-MIB::arubaWiredVsxIslHelloRx,Integer32,read-only,,current,,Number of ISL Hello packets received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.1.6,ARUBAWIRED-VSX-MIB::arubaWiredVsxDeviceOperSystemID,OCTET,read-only,,current,,System identifier used by this device - derived from system identifier values of the 2 devices.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveOperState,INTEGER,read-only,,current,init(1):configured(2):inSyncEstablished(3):outofSyncEstablished(4):initEstablished(5):failed(6):stopped(7),KeepAlive protocol operational state.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.2,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePacketsTx,Integer32,read-only,,current,,Number of KeepAlive protocol packets transmitted by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePacketsRx,Integer32,read-only,,current,,Number of KeepAlive protocol packets received by this device.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.4,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAlivePacketsDrop,Integer32,read-only,,current,,Number of KeepAlive protocol packets dropped.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.5,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveTimeoutCount,Integer32,read-only,,current,,Number of times KeepAlive protocol went to failed state because of KeepAlive timer expiry.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.6,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveLastEstablishedTime,TimeTicks,read-only,,current,,Stores the most recent time KeepAlive handshake was successful and a value of 0 indicates KeepAlive handshake was never established.
.1.3.6.1.4.1.47196.4.1.1.3.7.2.2.7,ARUBAWIRED-VSX-MIB::arubaWiredVsxKeepAliveLastFailedTime,TimeTicks,read-only,,current,,Stores the most recent time KeepAlive handshake failed and a value of 0 indicates KeepAlive handshake never failed.
.1.3.6.1.4.1.47196.4.1.1.3.7.3,ARUBAWIRED-VSX-MIB::arubaWiredVsxNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.3.1,ARUBAWIRED-VSX-MIB::arubaWiredVsxTraps,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.7.3.1.1,ARUBAWIRED-VSX-MIB::islUp,,,,,,An islUp trap signifies that ISL transitioned to inSync state
.1.3.6.1.4.1.47196.4.1.1.3.7.3.1.2,ARUBAWIRED-VSX-MIB::islDown,,,,,,An islDown trap signifies that ISL transitioned to outOfSync state
.1.3.6.1.4.1.47196.4.1.1.3.7.3.1.3,ARUBAWIRED-VSX-MIB::keepAliveUp,,,,,,A keepAliveUp trap signifies that KA is in established state
.1.3.6.1.4.1.47196.4.1.1.3.7.3.1.4,ARUBAWIRED-VSX-MIB::keepAliveDown,,,,,,A keepAliveDown trap signifies that KA is in failed state
.1.3.6.1.4.1.47196.4.1.1.3.8,ARUBAWIRED-NETWORKING-OID::arubaWiredPoeMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePort,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortTable,,not-accessible,,current,,A table of objects that display and control the power characteristics of power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented in managed power Ethernet switches and mid-span devices. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortEntry,,not-accessible,,current,,The fields in these entries will be used to supplement fields in 'pethPsePortEntry in ieee802af.mib.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerAllocateBy,INTEGER,read-write,,current,usage(1):class(2),Allows control over the power allocation strategy used for this port. Two power allocation strategies are class(2) and usage(1). When allocating by usage(1) power is delivered as requested by a PD. When allocating by class(2) the PSE uses the power ramp-up signature of the PD to identify the PD's power class and use the power level for the specified class.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPreStdDetect,INTEGER,read-only,,current,off(1):on(2),This field specifies the pre standard detect configuration for this port. A value of on - indicates that pre-802.3af-standard devices to power on. A value of off - indicates that only pre-802.3at/bt compliant devices are allowed. The default value is off.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortRpd,INTEGER,read-only,,current,off(1):on(2),Rapid Power Down is executed by the hardware in the event of a power-supply failure. It quickly cuts power to a PD to prevent an over-current scenario in the PSE. This field indicates whether the interface will go down in the event of any PSU failure or not. A value of on(2) indicates that a power supply failure will cause the power delivery to be cut on supply failure. A value of off(1) indicates that the port is unaffected by the failure of any single PSU.The default value is off(1).
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.4,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortCurrent,Integer32,read-only,,current,,This field specifies the current supplied at this port. This value is specified in milliamperes(mA).
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.5,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortVoltage,Integer32,read-only,,current,,This field specifies the Voltage supplied at this port. This value is specified in 10's of Volts (dV).
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.6,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortReservedPower,Integer32,read-only,,current,,This field specifies quantum of power which has been reserved for the PD at this port. This value is specified in milliwatts (mW).
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.7,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerDrawn,Integer32,read-only,,current,,This field specifies quantum of power which has indicating the actual power drawn by powered device(PD). This value is specified in milliwatts (mW).
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.8,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortAveragePower,Integer32,read-only,,current,,This field specifies the average power in milliwatts drawn by the powered device (PD) on this port.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.9,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPeakPower,Integer32,read-only,,current,,This field specifies the peak power supplied in milliwatts to the powered device (PD) connected to this port.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.10,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortOperStatus,INTEGER,read-only,,current,deny(1):off(2):on(3),This field specifies the operational status of the port.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.11,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPdSignature,INTEGER,read-only,,current,unknownSignature(0):singleSignature(1):dualSignature(2),This Signature value represents the PD signature. This variable is valid only while a PD is detected. In 802.3af and 802.3at standards the power controller on the PSE uses two of the four pairs of wires in the RJ45 connector to supply power to a power controller on the PD. With 802.3bt standard the controller on the PSE uses all four pairs. On the PD side there can either be single power controller, or two distinct power controllers connected to each of the two pairs and each of the two controllers would negotiate and draw power independently from the PSE. The Controller on the PSE is capable of detecting the PD signature, which will indicate whether the PD comprises a single controller or two independent controllers. Possible values: unknownSignature : 2-pair mode, singleSignature : 4-pair mode and one controller on the PD side, dualSignature : 4-pair mode and two controllers on the PD side.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.12,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerClassification,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5):class5(6):class6(7):class7(8):class8(9),A read-only value that indicates the PD Class of a detected PD. Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. The meaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered, that is, while the attribute pethPsePortDetectionStatus is reporting the enumeration deliveringPower.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.1.1.13,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPseAssignedClass,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5):class5(6):class6(7),This field indicates the actual class assigned by PSE to the PD. Class demotion allows the PSE to allocate less than the PD requested power based on the PD requested power and PSE available power. This information is published to the PD via the LLDP protocol. This read-only value indicates the PSE assigned class on this port. This variable is valid only while a PD is being powered, that is, while the attribute pethPsePortDetectionStatus is reporting the enumeration deliveringPower.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseFourPairPortTable,,not-accessible,,current,,A table of objects that display and control the power characteristics of power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented in managed power Ethernet switches and mid-span devices. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseFourPairPortEntry,,not-accessible,,current,,The fields in these entries will be used to supplement fields in 'pethPsePortEntry in ieee802af.mib.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortDetectionStatusPairA,INTEGER,read-only,,current,searchingAltA(1):deliveringPowerAltA(2):faultAltA(3),Describes the operational status of the port PD detection. A value of deliveringPowerAltA - indicates that the PSE State diagram is in the state POWER_ON_PRI if alt_pri='a', or the state POWER_ON_SEC if alt_pri='b'. A value of faultAltA - indicates that the PSE State diagram is in the state IDLE_PRI if alt_pri='a', or the state IDLE_SEC if alt_pri='b' due to the variable error_condition_pri = TRUE (if alt_pri='a') or error_condition_sec = TRUE (if alt_pri='b'). A value of searchingAltA - indicates the PSE State diagram is in a state other than those listed above.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortDetectionStatusPairB,INTEGER,read-only,,current,searchingAltB(1):deliveringPowerAltB(2):faultAltB(3),Describes the operational status of the port PD detection. A value of deliveringPowerAltB - indicates that the PSE State diagram is in the state POWER_ON_SEC if alt_pri='a', or the state POWER_ON_PRI if alt_pri='b'. A value of faultAltB - indicates that the PSE State diagram is in the state IDLE_SEC if alt_pri='a', or the state IDLE_PRI if alt_pri='b' due to the variable error_condition_sec = TRUE (if alt_pri='a') or error_condition_pri = TRUE (if alt_pri='b'). A value of searchingAltB - indicates the PSE State diagram is in a state other than those listed above.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerClassificationPairA,INTEGER,read-only,,current,class1(1):class2(2):class3(3):class4(4):class5(5),A read-only value that indicates the PD Class of a detected dual-signature PD on paira. Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. The meaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered that is, while the attribute arubaWiredPoePethPsePortDetectionStatusPairA is reporting the enumeration deliveringPowerAltA.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.4,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerClassificationPairB,INTEGER,read-only,,current,class1(1):class2(2):class3(3):class4(4):class5(5),A read-only value that indicates the PD Class of a detected dual-signature PD on paira. Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. The meaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered, that is, while the attribute arubaWiredPoePethPsePortDetectionStatusPairB is reporting the enumeration deliveringPowerAltB.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.5,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPseAssignedClassA,INTEGER,read-only,,current,class1(1):class2(2):class3(3):class4(4),This field indicates the actual class assigned by PSE to the PD. Class demotion allows the PSE to allocate less than the PD requested power based on the PD requested power and PSE available power. This information is published to the PD via the LLDP protocol. This read-only value indicates the PSE assigned class to PairA of this port.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.6,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPseAssignedClassB,INTEGER,read-only,,current,class1(1):class2(2):class3(3):class4(4),This field indicates the actual class assigned by PSE to the PD. Class demotion allows the PSE to allocate less than the PD requested power based on the PD requested power and PSE available power. This information is published to the PD via the LLDP protocol. This read-only value indicates the PSE assigned class to PairA of this port.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.7,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortInvalidSignatureCounterPairA,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state SIGNATURE_INVALID, if alt_pri='a'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.8,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortInvalidSignatureCounterPairB,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state SIGNATURE_INVALID, if alt_pri='b'
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.9,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerDeniedCounterPairA,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state POWER_DENIED, if alt_pri='a'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.10,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortPowerDeniedCounterPairB,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state POWER_DENIED, if alt_pri='b'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.11,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortOverLoadCounterPairA,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_OVER, if alt_pri='a'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.12,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortOverLoadCounterPairB,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_OVER, if alt_pri='b'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.13,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortMPSAbsentCounterPairA,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram transitions directly from the state POWER_ON to the state IDLE due to tmpdo_timer_done being asserted, if alt_pri='a'.
.1.3.6.1.4.1.47196.4.1.1.3.8.1.2.1.14,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortMPSAbsentCounterPairB,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram transitions directly from the state POWER_ON to the state IDLE due to tmpdo_timer_done being asserted, if alt_pri='b'.
.1.3.6.1.4.1.47196.4.1.1.3.8.2,ARUBAWIRED-POE-MIB::arubaWiredPoeConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.2.1,ARUBAWIRED-POE-MIB::arubaWiredPoeCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.2.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoeCompliance,,,,,,A compliance statement for HP Routing switches with PoE capability.
.1.3.6.1.4.1.47196.4.1.1.3.8.2.2,ARUBAWIRED-POE-MIB::arubaWiredPoeGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.2.2.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPsePortTableGroup,,,,,,A collection of objects display configuration, status, PD information and mesurements of PoE PSE Port table.
.1.3.6.1.4.1.47196.4.1.1.3.8.2.2.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseFourPairPortTableGroup,,,,,,A collection of objects display four pair paramentets of each pair PD information, status, and counters of PoE PSE Port table.
.1.3.6.1.4.1.47196.4.1.1.3.8.2.2.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseTableGroup,,,,,,A Collection of Object(s) that provide information about each power source equipment instance.
.1.3.6.1.4.1.47196.4.1.1.3.8.2.2.4,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleTableGroup,,,,,,A Collection of Object(s) that provide AlwaysOnPoe information about each module on switch.
.1.3.6.1.4.1.47196.4.1.1.3.8.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPse,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.3.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseTable,,not-accessible,,current,,A table of objects that display and control attributes of the main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.4.1.47196.4.1.1.3.8.3.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseEntry,,not-accessible,,current,,The fields in these entries will be used to supplement fields in 'pethMainPseEntry in ieee802af.mib.
.1.3.6.1.4.1.47196.4.1.1.3.8.3.1.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseReservedPower,Integer32,read-only,,current,,This field specifies the power in Watts, in the switch available for PoE power delivery. This power is available only for subsystems of type chassis, as power supplies are associated with chassis subsystem.
.1.3.6.1.4.1.47196.4.1.1.3.8.3.1.1.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseFailoverPower,Integer32,read-only,,current,,This field specifies the power in Watts, in the switch available for PoE power delivery when a single power supply failure happens. This power is available only for subsystems of type chassis, as power supplies are associated with chassis subsystem.
.1.3.6.1.4.1.47196.4.1.1.3.8.3.1.1.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethMainPseRedundantPower,Integer32,read-only,,current,,This field specifies power in Watts reserved by power supply based on power redundancy configurations. This power is available only for subsystems of type chassis, as power supplies are associated with chassis subsystem.
.1.3.6.1.4.1.47196.4.1.1.3.8.4,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModule,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.8.4.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleTable,,not-accessible,,current,,A table of objects contains the AlwaysOnPoe status information on module.
.1.3.6.1.4.1.47196.4.1.1.3.8.4.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleEntry,,not-accessible,arubaWiredPoePethPseModuleGroupIndex:arubaWiredPoePethPseModuleSlotIndex,current,,The fields in these entries will be used to display alwaysonpoe status information on specific module.
.1.3.6.1.4.1.47196.4.1.1.3.8.4.1.1.1,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the module to which a power Ethernet PSE is connected. Group means box in the stack and the value 1 MUST be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.8.4.1.1.2,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleSlotIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the module in a switch and value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.8.4.1.1.3,ARUBAWIRED-POE-MIB::arubaWiredPoePethPseModuleAlwaysOnPoe,INTEGER,read-only,,current,off(1):on(2),Alwayson PoE is a feature that provides the ability for a switch to continue to provide power across a soft reboot. Value on(2) indicates Always-on PoE feature is enabled on the subsystem. Value off(1) indicates Alwayson PoE feature is disabled on the subsystem. This feature is applicable to subsystems of type chassis in non-modular switches, and to subsystems of type line-card in modular switches. This configuration is ignored on a non-PoE capable subsystems.
.1.3.6.1.4.1.47196.4.1.1.3.9,ARUBAWIRED-NETWORKING-OID::arubaWiredLldpMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3Objects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocalData,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerTable,,not-accessible,,current,,This table contains one row per port of power ethernet information (as a part of the LLDP 802.3bt organizational extension) on the local system known to this agent.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port component.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the local system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the local system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.3,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is enabled on given port associated with the local system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.4,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate the ability to control which PSE Pinout Alternative is used for PD detection and power.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.5,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerPairs,INTEGER,read-only,,current,pairSignal(1):pairSpare(2),The truth value that identifies the PSE Pinout Alternative in use for detecting and supplying power to the PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.6,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerClass,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5),The truth value that indicates the requested Class of the PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.7,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerType,INTEGER,read-only,,current,type2PSE(1):type2PD(2):type1PSE(3):type1PD(4),This field reflects the actual local power type.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.8,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerSource,INTEGER,read-only,,current,unknown(1):primary(2):backup(3):reserved(4),This field reflects the requested local device power source. When the power type is PSE, this field shall be set to primary(2) when the PSE is sourcing its power through the PI from its primary supply; to backup(3) when the PSE is sourcing its power through the PI from a backup source; and to unknown(1) when this information is not available.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.9,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerPriority,INTEGER,read-write,,current,unknown(1):critical(2):high(3):low(4),This field reflects the requested local device power priority. When the power type is PD, this field shall be set to the power priority configured for the device. If a PD is unable to determine its power priority or it has not been configured, then this field shall be set to unknown(1). When the power type is PSE, this field shall be set to unknown(1).
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.10,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPDRequestedPowerValue,Integer32,read-only,,current,,It indicates the maximum input average power the PD is requesting in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.11,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPDRequestedPowerValueA,Integer32,read-only,,current,,It indicates the PD requested power value for the Mode A pairset in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.12,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPDRequestedPowerValueB,Integer32,read-only,,current,,It indicates the PD requested power value for the Mode B pairset in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.13,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEAllocatedPowerValue,Integer32,read-only,,current,,It indicates the maximum input average power the PSE expects the PD to draw in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.14,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEAllocatedPowerValueA,Integer32,read-only,,current,,It indicates the maximum input average power levels the PSE expects the dual-signature PD to draw, in units of 0.1 W, on Alternative A, when the PSE provides power over 4-pair.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.15,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEAllocatedPowerValueB,Integer32,read-only,,current,,It indicates the maximum input average power levels the PSE expects the dual-signature PD to draw, in units of 0.1 W, on Alternative B, when the PSE provides power over 4-pair.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.16,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEPoweringStatus,INTEGER,read-write,,current,twoPair(1):fourPsinglesigPD(2):fourPdualsigPD(3),This field reflects the existing powering configuration of the PSE and thus indicates that the PSE is using the 'PSE allocated power value' field or is using the 'PSE allocated power value Alternative A' field and 'PSE allocated power value Alternative B' field. For a PD the contents of this attribute are undefined.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.17,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerPairsExt,INTEGER,read-write,,current,altA(1):altB(2):both(3),This field indicates the supported PSE Pinout Alternative. For a PD the contents of this attribute are undefined
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.18,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerClassExtA,INTEGER,read-write,,current,singlesig(1):class1(2):class2(3):class3(4):class4(5):class5(6),For a dual-signature PD, it indicates the requested Class for Mode A during Physical Layer Classification. For a single-signature PD, a read-only value set to 'singlesig'. For a PSE connected to a dual-signature PD, a read-only value that indicates the currently assigned Class for Mode A. For a PSE connected to a single-signature PD, or a PSE that operates only in 2-pair mode, the value is set to 'singlesig'
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.19,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerClassExtB,INTEGER,read-write,,current,singlesig(1):class1(2):class2(3):class3(4):class4(5):class5(6),For a dual-signature PD, it indicates the requested Class for Mode B during Physical Layer Classification. For a single-signature PD, a read-only value set to 'singlesig'. For a PSE connected to a dual-signature PD, a read-only value that indicates the currently assigned Class for Mode B. For a PSE connected to a single-signature PD, or a PSE that operates only in 2-pair mode, the value is set to 'singlesig'
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.20,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerClassExt,INTEGER,read-write,,current,dualsig(1):class1(2):class2(3):class3(4):class4(5):class5(6):class6(7):class7(8):class8(9),For a single-signature PD, it indicates the requested Class during Physical Layer Classification. For a dual-signature PD, the value is set to 'dualsig'. For a PSE connected to a single-signature PD or a PSE that operates only in 2-pair mode, a readonly value that indicates the currently assigned Class. For a PSE connected to a dualsignature PD, a read-only value set to 'dualsig'.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.21,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPowerTypeExt,INTEGER,read-only,,current,type3PSE(1):type4PSE(2):type3singlesigPD(3):type3dualsigPD(4):type4singlesigPD(5):type4dualsigPD(6),This field indicates if the local system is a Type 3 or Type 4 PSE or PD, and in the case of a Type 3 or Type 4 PD, if it is a single-signature PD or a dual-signature PD
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.22,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPDLoad,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the load of a dual- signature PD is electrically isolated. For a single-signature PD, or a PSE, the value of this attribute is FALSE.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.23,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEMaxAvailPower,Integer32,read-only,,current,,It indicates the local PSE maximum available power value in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.24,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocPSEAutoclassSupport,INTEGER,read-only,,current,true(1):false(2),It indicates whether the local PSE system supports Autoclass
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.25,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocAutoclassCompleted,INTEGER,read-only,,current,true(1):false(2),It indicates whether the local PSE system has completed the Autoclass measurement
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.26,ARUBAWIRED-LLDP-MIB::arubaWiredLldpLocPseTlvSentType,INTEGER,read-only,,current,med(1):dot3(2):dot3-ext(3),This field specifies the set of TLVs that are actually sent by the PSE
.1.3.6.1.4.1.47196.4.1.1.3.9.1.1.1.1.27,ARUBAWIRED-LLDP-MIB::arubaWiredLldpLocPdTlvSentType,INTEGER,read-only,,current,med(1):dot3(2):dot3-ext(3):medanddot3(4):medanddot3-ext(5),This field specifies the set of TLVs that are actually sent by the PD
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemoteData,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerTable,,not-accessible,,current,,This table contains one row per port of power ethernet information (as a part of the LLDP 802.3bt organizational extension) on the remote system known to this agent.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular port component.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the remote system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the remote system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.3,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is enabled on given port associated with the remote system.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.4,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate the ability to control which PSE Pinout Alternative is used for PD detection and power.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.5,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerPairs,INTEGER,read-only,,current,pairSignal(1):pairSpare(2),The truth value that identifies the PSE Pinout Alternative in use for detecting and supplying power to the PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.6,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerClass,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5),The truth value that indicates the requested Class of the PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.7,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerType,INTEGER,read-only,,current,type2PSE(1):type2PD(2):type1PSE(3):type1PD(4),This field reflects the actual remote power type.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.8,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerSource,INTEGER,read-only,,current,unknown(1):pse(2):local(3):pseAndLocal(4),This field reflects the remote device (PD) requested power source. This field is encoded as pseAndLocal(4) when a PD being powered both locally and by a PSE, to local(3) when the PD being powered locally only, and to pse(2) when the PD is being powered by a PSE
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.9,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerPriority,INTEGER,read-write,,current,unknown(1):critical(2):high(3):low(4),This field reflects the requested remote device power priority. When the power type is PD, this field shall be set to the power priority configured for the device. If a PD is unable to determine its power priority or it has not been configured, then this field shall be set to unknown(1). When the power type is PSE, this field shall be set to unknown(1).
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.10,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPDRequestedPowerValue,Integer32,read-only,,current,,It indicates the maximum input average power the PD is requesting in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.11,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPDRequestedPowerValueA,Integer32,read-only,,current,,It indicates the PD requested power value for the Mode A pairset in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.12,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPDRequestedPowerValueB,Integer32,read-only,,current,,It indicates the PD requested power value for the Mode B pairset in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.13,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPSEAllocatedPowerValue,Integer32,read-only,,current,,It indicates the PSE allocated power value received from the remote system. For a PSE, it is the PSE allocated power value that was echoed back by the remote PD, in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.14,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPSEAllocatedPowerValueA,Integer32,read-only,,current,,It indicates the PSE allocated power value for the Alternative A pairset received from the remote system. For a PSE, it is the PSE allocated power value for the Alternative A pairset that was echoed back by the remote PD, in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.15,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPSEAllocatedPowerValueB,Integer32,read-only,,current,,It indicates the PSE allocated power value for the Alternative B pairset received from the remote system. For a PSE, it is the PSE allocated power value for the Alternative A pairset that was echoed back by the remote PD, in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.16,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPDPoweredStatus,INTEGER,read-write,,current,singlesigPD(1):twoPdualsigPD(2):fourPdualsigPD(3),This field indicates the existing powered configuration of the PD and thus indicate that the PD is using the 'PD requested power value' field or is using the 'PD requested power value Mode A' field and the 'PD requested power value Mode B' field. For a PSE the contents of this attribute are undefined.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.17,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerClassExtA,INTEGER,read-write,,current,singlesig(1):class1(2):class2(3):class3(4):class4(5):class5(6),For a dual-signature PD, a read-only value that indicates the currently assigned Class for Mode A by the remote 4-pair PSE. For a single-signature PD, or a dual-signature PD connected to a 2-pair only PSE, a read-only value set to 'singlesig' by the remote PSE. For a PSE connected to a dualsignature PD, a read-only value that indicates the requested Class for Mode A during Physical Layer classification by the remote PD. For a PSE connected to a single-signature PD, a read-only value set to 'singlesig' by the remote PD
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.18,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerClassExtB,INTEGER,read-write,,current,singlesig(1):class1(2):class2(3):class3(4):class4(5):class5(6),For a dual-signature PD, a read-only value that indicates the currently assigned Class for Mode A by the remote 4-pair PSE. For a single-signature PD, or a dual-signature PD connected to a 2-pair only PSE, a read-only value set to 'singlesig' by the remote PSE. For a PSE connected to a dualsignature PD, a read-only value that indicates the requested Class for Mode B during Physical Layer classification by the remote PD. For a PSE connected to a single-signature PD, a read-only value set to 'singlesig' by the remote PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.19,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerClassExt,INTEGER,read-write,,current,dualsig(1):class1(2):class2(3):class3(4):class4(5):class5(6):class6(7):class7(8):class8(9),For a single-signature PD or a dual-signature PD connected to a 2-pair only PSE, a read-only value that indicates the currently assigned Class by the remote PSE. For a dual- signature PD connected to a 4-pair capable PSE, a read-only value set to 'dualsig' by the remote PSE. For a PSE connected to a single-signature PD, a read-only value that indicates the requested Class during Physical Layer classification by the remote PD. For a PSE connected to a dual-signature PD, a readonly value set to 'dualsig' by the remote PD.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.20,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerTypeExt,INTEGER,read-only,,current,type3PSE(1):type4PSE(2):type3singlesigPD(3):type3dualsigPD(4):type4singlesigPD(5):type4dualsigPD(6),This field indicates if the remote system is a Type 3 or Type 4 PSE or PD, and in the case of a Type 3 or Type 4 PD, if it is a single-signature PD or dual-signature PD
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.21,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPDLoad,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the load of the remote dual-signature PD is electrically isolated. For a PD this attribute is set to FALSE
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.22,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPD4PID,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the remote PD system supports powering of both PD Modes
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.23,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPSEMaxAvailPower,Integer32,read-only,,current,,It indicates the remote PSE maximum available power value in units of 0.1 W.
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.24,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemAutoclassRequest,INTEGER,read-only,,current,true(1):false(2),It indicates whether the remote PD system is requesting an Autoclass measurement
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.25,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerDownRequest,INTEGER,read-only,,current,,It indicates that the remote PD system is requesting a power down when the value is 0x1D
.1.3.6.1.4.1.47196.4.1.1.3.9.1.2.1.1.26,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemPowerDownTime,INTEGER,read-only,,current,,It indicates the number of seconds the remote PD requests to stay powered off. A value of zero indicates an indefinite amount of time.
.1.3.6.1.4.1.47196.4.1.1.3.9.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.2.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.2.1.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3Compliance,,,,,,The compliance statement for LLDP implementation.
.1.3.6.1.4.1.47196.4.1.1.3.9.2.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.9.2.2.1,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3LocSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension for POEP Local Device Information. This group is mandatory for agents which implement the LLDP 802.3 organizational extension for POEP.
.1.3.6.1.4.1.47196.4.1.1.3.9.2.2.2,ARUBAWIRED-LLDP-MIB::arubaWiredLldpXdot3RemSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension for POEP Remote Device Information. This group is mandatory for agents which implement the LLDP 802.3 organizational extension for POEP.
.1.3.6.1.4.1.47196.4.1.1.3.10,ARUBAWIRED-NETWORKING-OID::arubaWiredVsfMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.0,ARUBAWIRED-VSF-MIB::arubaWiredVsfObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.0.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.0.1.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfTrapEnable,INTEGER,read-write,,current,true(1):false(2),If set to 'true', SNMP traps will be generated for VSF events.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.1.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfOobmMADEnable,INTEGER,read-write,,current,none(1):mgmt(2),Split detection scheme configured on the VSF stack. Supported schemes: 'none`: No split detection. In the event of a stack split, multiple fragments can be active. `mgmt`: The management network interface will be used to detect a stack split. If multiple fragments are detected, only the stack fragment containing the 'primary' member will keep its network interfaces active.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfStatus,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.0.2.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfOperStatus,OCTET,read-only,,current,,Describes current split state of VSF stack. Split state can be one of the following: noSplit: Both primary and secondary members are physically present and operational. fragmemtActive: A stack split has been detected and all network interfaces in this fragment are active. fragmentInactive: A stack split has been detected and all network interfaces in this fragment are inactive.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.2.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfTopology,OCTET,read-only,,current,,This object describes the physical topology of the VSF stack. Supported technologies include: standalone: The VSF stack comprises a single member only. chain: The VSF stack members are connected in a daisy chain. ring: The VSF stack members are connected in a ring.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberTable,,not-accessible,,current,,This table contains information about the Virtual Switching Framework members.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberEntry,,not-accessible,arubaWiredVsfMemberIndex,current,,A row in the Virtual Switching Framework member table.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberIndex,Integer32,read-only,,current,,Virtual Switching Framework Member ID.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberRole,OCTET,read-only,,current,,Role of VSF member in stack.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.3,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberStatus,OCTET,read-only,,current,,Specifies the status of the member-switch in the VSF stack. The switch status can be one of: `notPresent`: Member is not physically part of the stack. `booting`: Member is booting up. `ready`: Member has finished booting, and its interfaces can forward traffic. `versionMismatch`: Member is not running the same operating system version as the master switch. `communicationFailure`: The master switch is unable to communicate with the member. `inOtherFragment`: Member is part of another fragment as discovered through split detection.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.4,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberPartNumber,OCTET,read-only,,current,,The Part Number Identifier of the VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.5,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberMacAddr,OCTET,read-only,,current,,The switch base MAC address of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.6,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberProductName,OCTET,read-only,,current,,This product name of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.7,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberSerialNum,OCTET,read-only,,current,,The serial number identifier of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.8,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberBootImage,OCTET,read-only,,current,,The software image version running on this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.9,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberCpuUtil,Integer32,read-only,,current,,The CPU utilization, in percentage, of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.10,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberMemoryUtil,Integer32,read-only,,current,,The memory utilization, in percentage, of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.11,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberBootTime,TimeTicks,read-only,,current,,The boot up time, in seconds, of this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.12,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberBootRomVersion,OCTET,read-only,,current,,The software version of the running ServiceOS image on this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.13,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberTotalMemory,Integer32,read-only,,current,,Specifies the total memory (RAM) available on this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.3.1.14,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberCurrentUsage,Integer32,read-only,,current,,Specifies the current memory (RAM) usage on this VSF stack member.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkTable,,not-accessible,,current,,This table contains information about the Virtual Switching Framework Links.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkEntry,,not-accessible,arubaWiredVsfLinkMemberId:arubaWiredVsfLinkId,current,,A row in the Virtual Switching Framework Link table.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkMemberId,Integer32,not-accessible,,current,,Virtual Switching Framework link member ID.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkId,Integer32,not-accessible,,current,,Virtual Switching Framework link ID.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.3,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkOperStatus,OCTET,read-only,,current,,The state of the VSF link.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.4,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkPeerMemberId,Integer32,read-only,,current,,The member ID of the peer switch on the link.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.5,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkPeerLinkId,Integer32,read-only,,current,,The link id of the peer member on the link.
.1.3.6.1.4.1.47196.4.1.1.3.10.0.4.1.6,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkPortList,OCTET,read-only,,current,,Interface(s) associated to the link.
.1.3.6.1.4.1.47196.4.1.1.3.10.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.1.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberStatusChange,,,,,,This notification is generated when a new member joins the VSF stack.
.1.3.6.1.4.1.47196.4.1.1.3.10.1.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfFragmentStatusChange,,,,,,This notification is generated when a stack fragment becomes active or inactive.
.1.3.6.1.4.1.47196.4.1.1.3.10.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.2.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.2.1.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfMibCompliance,,,,,,The compliance statement for devices implementing the ARUBA WIRED VSF Mib.
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2.1,ARUBAWIRED-VSF-MIB::arubaWiredVsfConfigScalarGroup,,,,,,A collection of Virtual Switching Framework scalar objects.
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2.2,ARUBAWIRED-VSF-MIB::arubaWiredVsfStatusScalarGroup,,,,,,A collection of Virtual Switching Framework notifications objects.
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2.3,ARUBAWIRED-VSF-MIB::arubaWiredVsfMemberTableGroup,,,,,,A collection of Virtual Switching Framework member table objects.
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2.4,ARUBAWIRED-VSF-MIB::arubaWiredVsfLinkTableGroup,,,,,,A collection of Virtual Switching Framework link table objects.
.1.3.6.1.4.1.47196.4.1.1.3.10.2.2.5,ARUBAWIRED-VSF-MIB::arubaWiredVsfNotificationsGroup,,,,,,A collection of VSF virtual chassis notifications objects.
.1.3.6.1.4.1.47196.4.1.1.3.11,ARUBAWIRED-NETWORKING-OID::arubaWiredChassisMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2,ARUBAWIRED-CHASSIS-MIB::arubaWiredPowerSupply,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2.0,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2.0.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUStateNotification,,,,,,A notification generated when a PSU state change occurs. This can happen if a PSU is powerd on, powerd off, inserted, removed, or exeriences a fault.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyTable,,not-accessible,,current,,This table contains one row per switch power supply entity.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyEntry,,not-accessible,arubaWiredPSUGroupIndex:arubaWiredPSUSlotIndex,current,,Information about the power supply physical entity table.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUGroupIndex,Integer32,read-only,,current,,This variable uniquely identifies the group containing the power supply. Group means chassis in the stack and the value 1 MUST be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.2,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUSlotIndex,Integer32,read-only,,current,,This variable uniquely identifies the power supply in a chassis and value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.3,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUName,OCTET,read-only,,current,,Identification of the power supply for the system.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.4,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUState,OCTET,read-only,,current,,Current status for the power supply.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.5,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUProductName,OCTET,read-only,,current,,Power supply product name identification. This field is used to determine if the power supply is supported.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.6,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUSerialNumber,OCTET,read-only,,current,,Power supply serial number to uniquely identify the power supply.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.7,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUInstantaneousPower,Integer32,read-only,,current,,Total instantaneous power supplied by the power supply in Watts.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.8,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUMaximumPower,Integer32,read-only,,current,,Total maximum power capacity that can be supplied by the power supply in Watts.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.9,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUNumberFailures,Integer32,read-only,,current,,Number of failures the power supply has experienced since the most recent insertion of the power supply and boot of the system. The number of failures for a power supply will be cleared if the power supply is removed from the system or if the system is rebooted. For non removable power supplies, the number of failures will not clear until the system reboots. Failures are any events where power delivery from the power supply did not occur when expected. This includes unsupported power supply types since their power delivery is not considered valid even though the power supply itself may not have an internal failure. Some examples of failures are over current, invalid input power, and unsupported power supply type.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.1.1.10,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUAirflowDirection,OCTET,read-only,,current,,Power Supply airflow direction.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99.1.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyCompliance,,,,,,A compliance statement for Aruba switch chassis.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99.2,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99.2.1,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPowerSupplyTableGroup,,,,,,A collection of objects display configuration, status, and measurements of Power Supply table.
.1.3.6.1.4.1.47196.4.1.1.3.11.2.99.2.2,ARUBAWIRED-POWERSUPPLY-MIB::arubaWiredPSUNotificationsGroup,,,,,,Notifications sent by power management.
.1.3.6.1.4.1.47196.4.1.1.3.11.3,ARUBAWIRED-CHASSIS-MIB::arubaWiredTempSensor,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.3.0,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.3.0.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorStateNotification,,,,,,A notification generated when a temperature sensor state change occurs. This can happen if a temperature sensor experiences a fault or critical temperature value.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorTable,,not-accessible,,current,,This table contains one row per switch temperature sensor entity.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorEntry,,not-accessible,arubaWiredTempSensorGroupIndex:arubaWiredTempSensorSlotTypeIndex:arubaWiredTempSensorSlotIndex:arubaWiredTempSensorIndex,current,,Information about the temperature sensor physical entity table.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the temperature sensor. Group means chassis in the stack and the value 1 MUST be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.2,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorSlotTypeIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the type of subsystem in a chassis that the temperature sensor is in. A value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.3,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorSlotIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the subsystem instance in a chassis and value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.4,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the temperature sensor instance in a subsystem. A value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.5,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorName,OCTET,read-only,,current,,Identification of the temperature sensor for the system.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.6,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorState,OCTET,read-only,,current,,Current status for the temperature sensor.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.7,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorTemperature,Integer32,read-only,,current,,Current temperature value read from the temperature sensor.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.8,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorMinTemp,Integer32,read-only,,current,,Historic minimum temperature of the temperature sensor.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.1.1.9,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorMaxTemp,Integer32,read-only,,current,,Historic maximum temperature of the temperature sensor.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99.1.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorCompliance,,,,,,A compliance statement for Aruba switch chassis.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99.2,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99.2.1,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorTableGroup,,,,,,A collection of objects display configuration, status, and measurements of Temperature Sensor table.
.1.3.6.1.4.1.47196.4.1.1.3.11.3.99.2.2,ARUBAWIRED-TEMPSENSOR-MIB::arubaWiredTempSensorNotificationsGroup,,,,,,Notifications sent by temperature sensor management.
.1.3.6.1.4.1.47196.4.1.1.3.11.4,ARUBAWIRED-CHASSIS-MIB::arubaWiredFanTray,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.4.0,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.4.0.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayStateNotification,,,,,,A notification generated when a fan tray subsystem state change occurs. This can happen if a fan tray is inserted, removed, or experiences a fault.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayTable,,not-accessible,,current,,This table contains one row per switch fan tray entity.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayEntry,,not-accessible,arubaWiredFanTrayGroupIndex:arubaWiredFanTraySlotIndex,current,,Information about the fan tray physical entity table.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the fan tray. Group means chassis in the stack and the value 1 MUST be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.2,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTraySlotIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the fan tray instance in a chassis and value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.3,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayName,OCTET,read-only,,current,,Identification of the fan tray for the system.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.4,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayState,OCTET,read-only,,current,,Current status for the fan tray.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.5,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayProductName,OCTET,read-only,,current,,Fan tray product name identification.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.6,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTraySerialNumber,OCTET,read-only,,current,,Fan tray serial number to uniquely identify the fan tray.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.1.1.7,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayNumberFans,Integer32,read-only,,current,,Number of fans the fan tray can contain.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99.1.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayCompliance,,,,,,A compliance statement for Aruba switch chassis.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99.2,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99.2.1,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayTableGroup,,,,,,A collection of objects display configuration, status, and measurements of Fan Tray table.
.1.3.6.1.4.1.47196.4.1.1.3.11.4.99.2.2,ARUBAWIRED-FANTRAY-MIB::arubaWiredFanTrayNotificationsGroup,,,,,,Notifications sent by fan management.
.1.3.6.1.4.1.47196.4.1.1.3.11.5,ARUBAWIRED-CHASSIS-MIB::arubaWiredFan,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.5.0,ARUBAWIRED-FAN-MIB::arubaWiredFanNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.5.0.1,ARUBAWIRED-FAN-MIB::arubaWiredFanStateNotification,,,,,,A notification generated when a fan state change occurs. This can happen if a fan is inserted, removed, or experiences a fault.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1,ARUBAWIRED-FAN-MIB::arubaWiredFanTable,,not-accessible,,current,,This table contains one row per switch fan entity.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1,ARUBAWIRED-FAN-MIB::arubaWiredFanEntry,,not-accessible,arubaWiredFanGroupIndex:arubaWiredFanTrayIndex:arubaWiredFanSlotIndex,current,,Information about the fan physical entity table.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.1,ARUBAWIRED-FAN-MIB::arubaWiredFanGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the fan. Group means chassis in the stack and the value 1 MUST be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.2,ARUBAWIRED-FAN-MIB::arubaWiredFanTrayIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the fan tray instance in a chassis that contains the fan. A value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.3,ARUBAWIRED-FAN-MIB::arubaWiredFanSlotIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the fan instance in a fan tray and value 1 must be used for non-modular devices.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.4,ARUBAWIRED-FAN-MIB::arubaWiredFanName,OCTET,read-only,,current,,Identification of the fan for the system.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.5,ARUBAWIRED-FAN-MIB::arubaWiredFanState,OCTET,read-only,,current,,Current status for the fan.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.6,ARUBAWIRED-FAN-MIB::arubaWiredFanProductName,OCTET,read-only,,current,,Fan product name identification.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.7,ARUBAWIRED-FAN-MIB::arubaWiredFanSerialNumber,OCTET,read-only,,current,,Fan serial number to uniquely identify the fan.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.8,ARUBAWIRED-FAN-MIB::arubaWiredFanRPM,Integer32,read-only,,current,,Current RPM read for the fan.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.1.1.9,ARUBAWIRED-FAN-MIB::arubaWiredFanAirflowDirection,OCTET,read-only,,current,,Air flow direction for the fan.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99,ARUBAWIRED-FAN-MIB::arubaWiredFanConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99.1,ARUBAWIRED-FAN-MIB::arubaWiredFanCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99.1.1,ARUBAWIRED-FAN-MIB::arubaWiredFanCompliance,,,,,,A compliance statement for Aruba switch chassis.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99.2,ARUBAWIRED-FAN-MIB::arubaWiredFanGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99.2.1,ARUBAWIRED-FAN-MIB::arubaWiredFanTableGroup,,,,,,A collection of objects display configuration, status, and measurements of Fan table.
.1.3.6.1.4.1.47196.4.1.1.3.11.5.99.2.2,ARUBAWIRED-FAN-MIB::arubaWiredFanNotificationsGroup,,,,,,Notifications sent by fan management.
.1.3.6.1.4.1.47196.4.1.1.3.12,ARUBAWIRED-NETWORKING-OID::arubaWiredCiptMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptGlobalConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.1.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether client IP tracker is enabled or disabled. By default this object will have a value of false(2).
.1.3.6.1.4.1.47196.4.1.1.3.12.1.1.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptProbeEnable,INTEGER,read-write,,current,true(1):false(2),This object is used to enable client IP tracker probing to update client IP.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptVlanConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.1.2.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptVidList,OCTET,read-write,,current,,A list of VLANs on which client IP tracker is enabled.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortConfig,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortTable,,not-accessible,,current,,Per-port configuration of Client IP tracker.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortEntry,,not-accessible,arubaWiredCiptPortIfIndex,current,,Client IP tracker configuration information for a single port.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the port on which the client IP tracker entry is enabled. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1.1.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortEnable,INTEGER,read-write,,current,disable(0):enable(1):auto(2),This object indicates whether client IP tracker is enabled on a port or not . The default value is auto(2)
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1.1.3,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortUpdateInterval,Unsigned32,read-write,,current,,The interval in seconds at which client IP is refreshed. The default value is 1800 seconds.
.1.3.6.1.4.1.47196.4.1.1.3.12.1.3.1.1.4,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortClientLimit,Unsigned32,read-write,,current,,Maximum number of clients which can be tracked on this port. 6100 max clients - 128 6200, 6300 max clients - 2048 6400 max client - 4096
.1.3.6.1.4.1.47196.4.1.1.3.12.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClients,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptTrackedClients,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientTable,,not-accessible,,current,,Client IP tracker learnt IP addresses for a client MAC.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientEntry,,not-accessible,arubaWiredCiptClientMacAddress:arubaWiredCiptClientVlanId:arubaWiredCiptClientIpIndex,current,,Learnt IP address of a client MAC on a port.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientMacAddress,OCTET,not-accessible,,current,,MAC address of the client whose IP is being tracked.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientVlanId,Unsigned32,not-accessible,,current,,The VLAN on which the client IP is being tracked.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.3,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientIpIndex,Unsigned32,not-accessible,,current,,The index of IP when a client being tracked has multiple IP addresses.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.4,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientIpAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the InetAddress variables in this table.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.5,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientIpAddress,OCTET,read-only,,current,,Tracked IP address of the client.
.1.3.6.1.4.1.47196.4.1.1.3.12.2.1.1.1.6,ARUBAWIRED-CIPT-MIB::arubaWiredCiptClientPortIfIndex,Integer32,read-only,,current,,IfIndex of the port on which client IP address is being tracked.
.1.3.6.1.4.1.47196.4.1.1.3.12.3,ARUBAWIRED-CIPT-MIB::arubaWiredCiptConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.3.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.3.1.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptConfigGlobalGroup,,,,,,A collection of objects providing global configuration of client IP tracker.
.1.3.6.1.4.1.47196.4.1.1.3.12.3.1.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptVlanConfigGroup,,,,,,A collection of objects providing per VLAN configuration of client IP tracker.
.1.3.6.1.4.1.47196.4.1.1.3.12.3.1.3,ARUBAWIRED-CIPT-MIB::arubaWiredCiptPortConfigGroup,,,,,,A collection of objects providing per port configuration of client IP tracker.
.1.3.6.1.4.1.47196.4.1.1.3.12.3.1.4,ARUBAWIRED-CIPT-MIB::arubaWiredCiptTrackedClientsGroup,,,,,,A collection of objects providing details of client whose IP address is being tracked.
.1.3.6.1.4.1.47196.4.1.1.3.12.3.2,ARUBAWIRED-CIPT-MIB::arubaWiredCiptCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.12.3.2.1,ARUBAWIRED-CIPT-MIB::arubaWiredCiptCompliance,,,,,,The compliance statement for HP Switches with support for arubaWired client IP tracker objects.
.1.3.6.1.4.1.47196.4.1.1.3.13,ARUBAWIRED-NETWORKING-OID::arubaWiredMstpMIB,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.0,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotifications,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.0.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpErrantBpduReceived,,,,,,This Trap is generated when an unexpected (errant) BPDU has been received on a port.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.2,ARUBAWIRED-MSTP-MIB::arubaWiredMstpInstanceTopologyChange,,,,,,Trap is generated when a Topology Change is detected in the specified INSTANCE.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.3,ARUBAWIRED-MSTP-MIB::arubaWiredMstpCISTTopologyChange,,,,,,Trap is generated when a Topology Change is detected in CIST.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.4,ARUBAWIRED-MSTP-MIB::arubaWiredMstpInstanceNewRoot,,,,,,Trap generated when sending agent has become the new root of spanning Tree for the specified INSTANCE; the notification is sent by a bridge soon after its election as the new root.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.5,ARUBAWIRED-MSTP-MIB::arubaWiredMstpCISTNewRoot,,,,,,Trap generated when sending agent has become the new root of spanning Tree for the specified CIST; the notification is sent by a bridge soon after its election as the new root.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.6,ARUBAWIRED-MSTP-MIB::arubaWiredMstpInstanceLoopGuardInconsistency,,,,,,Trap generated when a Loop Guard feature enabled port receives superior BPDUs on its interface for a given instance.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.7,ARUBAWIRED-MSTP-MIB::arubaWiredMstpCISTLoopGuardInconsistency,,,,,,Trap generated when a Loop Guard feature enabled port receives superior BPDUs on its interface for CIST.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.8,ARUBAWIRED-MSTP-MIB::arubaWiredMstpInstanceRootGuardInconsistency,,,,,,Trap generated when a Root Guard feature enabled port receives superior BPDUs on its interface for a given instance.
.1.3.6.1.4.1.47196.4.1.1.3.13.0.9,ARUBAWIRED-MSTP-MIB::arubaWiredMstpCISTRootGuardInconsistency,,,,,,Trap generated when a Root Guard feature enabled port receives superior BPDUs on its interface for CIST.
.1.3.6.1.4.1.47196.4.1.1.3.13.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpObjects,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotificationTable,,not-accessible,,current,,Information describing the Mstp configuration and statistics of the Instances and CIST.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotificationEntry,,not-accessible,arubaWiredMstpId,current,,Information describing the Mstp events for trap generation.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpPortName,OCTET,accessible-for-notify,,current,,The port Name
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.2,ARUBAWIRED-MSTP-MIB::arubaWiredMstpInstanceID,Integer32,accessible-for-notify,,current,,Unique identifier of the STP Instance.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.3,ARUBAWIRED-MSTP-MIB::arubaWiredMstpPortErrantBpduRxCount,Integer32,accessible-for-notify,,current,,The number of errant bpdu rx on the port  for the particular instance 
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.4,ARUBAWIRED-MSTP-MIB::arubaWiredMstpErrantBpduSrcMac,OCTET,accessible-for-notify,,current,,Source MAC address of the port sending this Errant trap.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.5,ARUBAWIRED-MSTP-MIB::arubaWiredMstpSuperiorBpduSrcPort,OCTET,accessible-for-notify,,current,,Port belonging to the Bridge, which  transmitted the superior BPDU.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.6,ARUBAWIRED-MSTP-MIB::arubaWiredMstpSuperiorBpduSrcMac,OCTET,accessible-for-notify,,current,,The source MAC address of the port sending superior BPDU.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.7,ARUBAWIRED-MSTP-MIB::arubaWiredMstpPortInstanceState,OCTET,accessible-for-notify,,current,,State of the port for the particular Instance
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.8,ARUBAWIRED-MSTP-MIB::arubaWiredMstpErrantBpduDetector,INTEGER,accessible-for-notify,,current,bpduFilter(1):bpduProtection(2),The identifier of the feature generating Errant BPDU trap.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.9,ARUBAWIRED-MSTP-MIB::arubaWiredMstpPortDesignatedBridge,OCTET,accessible-for-notify,,current,,The designated bridge name for this STP instance.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.10,ARUBAWIRED-MSTP-MIB::arubaWiredMstpOldPortRole,OCTET,accessible-for-notify,,current,,The previous role of the port before the Topology change. Forwarding/Blocking/Err-DisabledState
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.11,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNewPortRole,OCTET,accessible-for-notify,,current,,The new role of the port after the Topology change. Forwarding/Blocking/Err-DisabledState
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.12,ARUBAWIRED-MSTP-MIB::arubaWiredMstpTopoChangeTime,OCTET,accessible-for-notify,,current,,Time at which the Topology Change happened.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.13,ARUBAWIRED-MSTP-MIB::arubaWiredMstpPreviousRootBridgeID,OCTET,accessible-for-notify,,current,,Bridge ID of the Previous root, before the Topology change.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.14,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNewRootBridgeID,OCTET,accessible-for-notify,,current,,Bridge ID of the New root, after the Topology change.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.15,ARUBAWIRED-MSTP-MIB::arubaWiredMstpRootBridgeChangeTimeStamp,OCTET,accessible-for-notify,,current,,Time when the new root is elected.
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.16,ARUBAWIRED-MSTP-MIB::arubaWiredMstpId,Integer32,not-accessible,,current,,Instance ID
.1.3.6.1.4.1.47196.4.1.1.3.13.2,ARUBAWIRED-MSTP-MIB::arubaWiredMstpConformance,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpGroups,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotificationObjectGroup,,,,,,Group of objects required for notifications.
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1.2,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotificationGroup,,,,,,Group of notifications.
.1.3.6.1.4.1.47196.4.1.1.3.13.2.2,ARUBAWIRED-MSTP-MIB::arubaWiredMstpCompliances,,,,,,
.1.3.6.1.4.1.47196.4.1.1.3.13.2.2.1,ARUBAWIRED-MSTP-MIB::arubaWiredMstpNotificationCompliance,,,,,,The compliance statement for Mstp extension notifications.
.1.3.6.1.5,SNMPv2-SMI::security,,,,,,
.1.3.6.1.6,SNMPv2-SMI::snmpV2,,,,,,
.1.3.6.1.6.1,SNMPv2-SMI::snmpDomains,,,,,,
.1.3.6.1.6.2,SNMPv2-SMI::snmpProxys,,,,,,
.1.3.6.1.6.3,SNMPv2-SMI::snmpModules,,,,,,
.1.3.6.1.6.3.1,SNMPv2-MIB::snmpMIB,,,,,,The MIB module for SNMP entities. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3418; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.1.1,SNMPv2-MIB::snmpMIBObjects,,,,,,
.1.3.6.1.6.3.1.1.4,SNMPv2-MIB::snmpTrap,,,,,,
.1.3.6.1.6.3.1.1.4.1,SNMPv2-MIB::snmpTrapOID,OBJECT,accessible-for-notify,,current,,The authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2-Trap-PDU and InformRequest-PDU.
.1.3.6.1.6.3.1.1.4.3,SNMPv2-MIB::snmpTrapEnterprise,OBJECT,accessible-for-notify,,current,,The authoritative identification of the enterprise associated with the trap currently being sent. When an SNMP proxy agent is mapping an RFC1157 Trap-PDU into a SNMPv2-Trap-PDU, this variable occurs as the last varbind.
.1.3.6.1.6.3.1.1.5,SNMPv2-MIB::snmpTraps,,,,,,
.1.3.6.1.6.3.1.1.5.1,SNMPv2-MIB::coldStart,,,,,,A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
.1.3.6.1.6.3.1.1.5.2,SNMPv2-MIB::warmStart,,,,,,A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its configuration is unaltered.
.1.3.6.1.6.3.1.1.5.3,IF-MIB::linkDown,,,,,,A linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.
.1.3.6.1.6.3.1.1.5.4,IF-MIB::linkUp,,,,,,A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.
.1.3.6.1.6.3.1.1.5.5,SNMPv2-MIB::authenticationFailure,,,,,,An authenticationFailure trap signifies that the SNMP entity has received a protocol message that is not properly authenticated. While all implementations of SNMP entities MAY be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated.
.1.3.6.1.6.3.1.1.6,SNMPv2-MIB::snmpSet,,,,,,
.1.3.6.1.6.3.1.1.6.1,SNMPv2-MIB::snmpSetSerialNo,INTEGER,read-write,,current,,An advisory lock used to allow several cooperating command generator applications to coordinate their use of the SNMP set operation. This object is used for coarse-grain coordination. To achieve fine-grain coordination, one or more similar objects might be defined within each MIB group, as appropriate.
.1.3.6.1.6.3.1.2,SNMPv2-MIB::snmpMIBConformance,,,,,,
.1.3.6.1.6.3.1.2.1,SNMPv2-MIB::snmpMIBCompliances,,,,,,
.1.3.6.1.6.3.1.2.1.2,SNMPv2-MIB::snmpBasicCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the SNMPv2 MIB. This compliance statement is replaced by snmpBasicComplianceRev2.
.1.3.6.1.6.3.1.2.1.3,SNMPv2-MIB::snmpBasicComplianceRev2,,,,,,The compliance statement for SNMP entities which implement this MIB module.
.1.3.6.1.6.3.1.2.2,SNMPv2-MIB::snmpMIBGroups,,,,,,
.1.3.6.1.6.3.1.2.2.5,SNMPv2-MIB::snmpSetGroup,,,,,,A collection of objects which allow several cooperating command generator applications to coordinate their use of the set operation.
.1.3.6.1.6.3.1.2.2.6,SNMPv2-MIB::systemGroup,,,,,,The system group defines objects which are common to all managed systems.
.1.3.6.1.6.3.1.2.2.7,SNMPv2-MIB::snmpBasicNotificationsGroup,,,,,,The basic notifications implemented by an SNMP entity supporting command responder applications.
.1.3.6.1.6.3.1.2.2.8,SNMPv2-MIB::snmpGroup,,,,,,A collection of objects providing basic instrumentation and control of an SNMP entity.
.1.3.6.1.6.3.1.2.2.9,SNMPv2-MIB::snmpCommunityGroup,,,,,,A collection of objects providing basic instrumentation of a SNMP entity which supports community-based authentication.
.1.3.6.1.6.3.1.2.2.10,SNMPv2-MIB::snmpObsoleteGroup,,,,,,A collection of objects from RFC 1213 made obsolete by this MIB module.
.1.3.6.1.6.3.1.2.2.11,SNMPv2-MIB::snmpWarmStartNotificationGroup,,,,,,An additional notification for an SNMP entity supporting command responder applications, if it is able to reinitialize itself such that its configuration is unaltered.
.1.3.6.1.6.3.1.2.2.12,SNMPv2-MIB::snmpNotificationGroup,,,,,,These objects are required for entities which support notification originator applications.
.1.3.6.1.6.3.10,SNMP-FRAMEWORK-MIB::snmpFrameworkMIB,,,,,,The SNMP Management Architecture MIB Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3411; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.10.1,SNMP-FRAMEWORK-MIB::snmpFrameworkAdmin,,,,,,
.1.3.6.1.6.3.10.1.1,SNMP-FRAMEWORK-MIB::snmpAuthProtocols,,,,,,Registration point for standards-track authentication protocols used in SNMP Management Frameworks. 
.1.3.6.1.6.3.10.1.2,SNMP-FRAMEWORK-MIB::snmpPrivProtocols,,,,,,Registration point for standards-track privacy protocols used in SNMP Management Frameworks. 
.1.3.6.1.6.3.10.2,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBObjects,,,,,,
.1.3.6.1.6.3.10.2.1,SNMP-FRAMEWORK-MIB::snmpEngine,,,,,,
.1.3.6.1.6.3.10.2.1.1,SNMP-FRAMEWORK-MIB::snmpEngineID,OCTET,read-only,,current,,An SNMP engine's administratively-unique identifier. This information SHOULD be stored in non-volatile storage so that it remains constant across re-initializations of the SNMP engine. 
.1.3.6.1.6.3.10.2.1.2,SNMP-FRAMEWORK-MIB::snmpEngineBoots,INTEGER,read-only,,current,,The number of times that the SNMP engine has (re-)initialized itself since snmpEngineID was last configured. 
.1.3.6.1.6.3.10.2.1.3,SNMP-FRAMEWORK-MIB::snmpEngineTime,INTEGER,read-only,,current,,The number of seconds since the value of the snmpEngineBoots object last changed. When incrementing this object's value would cause it to exceed its maximum, snmpEngineBoots is incremented as if a re-initialization had occurred, and this object's value consequently reverts to zero. 
.1.3.6.1.6.3.10.2.1.4,SNMP-FRAMEWORK-MIB::snmpEngineMaxMessageSize,INTEGER,read-only,,current,,The maximum length in octets of an SNMP message which this SNMP engine can send or receive and process, determined as the minimum of the maximum message size values supported among all of the transports available to and supported by the engine. 
.1.3.6.1.6.3.10.3,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBConformance,,,,,,
.1.3.6.1.6.3.10.3.1,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliances,,,,,,
.1.3.6.1.6.3.10.3.1.1,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP Management Framework MIB. 
.1.3.6.1.6.3.10.3.2,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBGroups,,,,,,
.1.3.6.1.6.3.10.3.2.1,SNMP-FRAMEWORK-MIB::snmpEngineGroup,,,,,,A collection of objects for identifying and determining the configuration and current timeliness values of an SNMP engine. 
