LBMSH-MIB

File: LBMSH-MIB.mib (301525 bytes)

Imported modules

RFC1155-SMI RFC-1212 RFC-1215
RFC1213-MIB

Imported symbols

mgmt NetworkAddress IpAddress
Counter Gauge TimeTicks
enterprises OBJECT-TYPE TRAP-TYPE
DisplayString PhysAddress snmp
ifIndex

Defined Types

DisplayString  
OCTET STRING    

PhysAddress  
OCTET STRING    

IfEntry  
SEQUENCE    
  ifIndex INTEGER
  ifDescr DisplayString
  ifType INTEGER
  ifMtu INTEGER
  ifSpeed Gauge
  ifPhysAddress PhysAddress
  ifAdminStatus INTEGER
  ifOperStatus INTEGER
  ifLastChange TimeTicks
  ifInOctets Counter
  ifInUcastPkts Counter
  ifInNUcastPkts Counter
  ifInDiscards Counter
  ifInErrors Counter
  ifInUnknownProtos Counter
  ifOutOctets Counter
  ifOutUcastPkts Counter
  ifOutNUcastPkts Counter
  ifOutDiscards Counter
  ifOutErrors Counter
  ifOutQLen Gauge
  ifSpecific OBJECT IDENTIFIER

IpAddrEntry  
SEQUENCE    
  ipAdEntAddr IpAddress
  ipAdEntIfIndex INTEGER
  ipAdEntNetMask IpAddress
  ipAdEntBcastAddr INTEGER
  ipAdEntReasmMaxSize INTEGER 0..65535

IpRouteEntry  
SEQUENCE    
  ipRouteDest IpAddress
  ipRouteIfIndex INTEGER
  ipRouteMetric1 INTEGER
  ipRouteMetric2 INTEGER
  ipRouteMetric3 INTEGER
  ipRouteMetric4 INTEGER
  ipRouteNextHop IpAddress
  ipRouteType INTEGER
  ipRouteProto INTEGER
  ipRouteAge INTEGER
  ipRouteMask IpAddress
  ipRouteMetric5 INTEGER
  ipRouteInfo OBJECT IDENTIFIER

IpNetToMediaEntry  
SEQUENCE    
  ipNetToMediaIfIndex INTEGER
  ipNetToMediaPhysAddress PhysAddress
  ipNetToMediaNetAddress IpAddress
  ipNetToMediaType INTEGER

TcpConnEntry  
SEQUENCE    
  tcpConnState INTEGER
  tcpConnLocalAddress IpAddress
  tcpConnLocalPort INTEGER 0..65535
  tcpConnRemAddress IpAddress
  tcpConnRemPort INTEGER 0..65535

UdpEntry  
SEQUENCE    
  udpLocalAddress IpAddress
  udpLocalPort INTEGER 0..65535

RptrGroupEntry  
SEQUENCE    
  rptrGroupIndex INTEGER
  rptrGroupDescr DisplayString
  rptrGroupObjectID OBJECT IDENTIFIER
  rptrGroupOperStatus INTEGER
  rptrGroupLastOperStatusChange TimeTicks
  rptrGroupPortCapacity INTEGER

RptrPortEntry  
SEQUENCE    
  rptrPortGroupIndex INTEGER
  rptrPortIndex INTEGER
  rptrPortAdminStatus INTEGER
  rptrPortAutoPartitionState INTEGER
  rptrPortOperStatus INTEGER

RptrMonitorGroupEntry  
SEQUENCE    
  rptrMonitorGroupIndex INTEGER
  rptrMonitorGroupTotalFrames Counter
  rptrMonitorGroupTotalOctets Counter
  rptrMonitorGroupTotalErrors Counter

RptrMonitorPortEntry  
SEQUENCE    
  rptrMonitorPortGroupIndex INTEGER
  rptrMonitorPortIndex INTEGER
  rptrMonitorPortReadableFrames Counter
  rptrMonitorPortReadableOctets Counter
  rptrMonitorPortFCSErrors Counter
  rptrMonitorPortAlignmentErrors Counter
  rptrMonitorPortFrameTooLongs Counter
  rptrMonitorPortShortEvents Counter
  rptrMonitorPortRunts Counter
  rptrMonitorPortCollisions Counter
  rptrMonitorPortLateEvents Counter
  rptrMonitorPortVeryLongEvents Counter
  rptrMonitorPortDataRateMismatches Counter
  rptrMonitorPortAutoPartitions Counter
  rptrMonitorPortTotalErrors Counter

RptrAddrTrackEntry  
SEQUENCE    
  rptrAddrTrackGroupIndex INTEGER
  rptrAddrTrackPortIndex INTEGER
  rptrAddrTrackLastSourceAddress PhysAddress
  rptrAddrTrackSourceAddrChanges Counter

RpMauEntry  
SEQUENCE    
  rpMauGroupIndex INTEGER
  rpMauPortIndex INTEGER
  rpMauIndex INTEGER
  rpMauType INTEGER
  rpMauAdminState INTEGER
  rpMauMediaAvailable INTEGER
  rpMauLostMedias Counter
  rpMauJabberState INTEGER
  rpMauJabbers Counter

SetIpIfEntry  
SEQUENCE    
  setIpIfIndex INTEGER
  setIpIfAddr IpAddress
  setIpIfMask IpAddress

LoadableDevice  
SEQUENCE    
  slDeviceType INTEGER
  slDeviceInstance INTEGER
  slLoadStatus INTEGER
  slSoftwareVersion DisplayString
  slHardwareVersion INTEGER
  slFilename DisplayString
  slServerIpAddress IpAddress
  slLoad INTEGER

SecurityEnableTableEntry  
SEQUENCE    
  securityLevel INTEGER
  securityCommunityEnable INTEGER
  securitySecureEnable INTEGER
  securityTermEnable INTEGER
  securityTelnetEnable INTEGER
  securityFrontPanelEnable INTEGER

SecurityUserTableEntry  
SEQUENCE    
  securityUserStatus INTEGER
  securityUserName DisplayString
  securityUserLevel INTEGER
  securityUserPassword DisplayString
  securityUserCommunity DisplayString
  securityUserLocParty OBJECT IDENTIFIER
  securityUserMgrParty OBJECT IDENTIFIER

SecurityAuditLogEntry  
SEQUENCE    
  securityAuditIndex INTEGER
  securityAuditTime TimeTicks
  securityAuditUser DisplayString
  securityAuditObject OBJECT IDENTIFIER
  securityAuditValue OCTET STRING
  securityAuditResult INTEGER

GaugeTableEntry  
SEQUENCE    
  gaugeIndex INTEGER
  gaugeItemId OBJECT IDENTIFIER
  gaugeItemType INTEGER
  gaugeSamplesPerAverage INTEGER
  gaugeSamplePeriod INTEGER
  gaugeValue INTEGER
  gaugePeakValue INTEGER
  gaugeThresholdLevel INTEGER
  gaugeRecoveryLevel INTEGER
  gaugeThresholdAction INTEGER
  gaugeRecoveryAction INTEGER
  gaugeState INTEGER

ConfigV24Entry  
SEQUENCE    
  configV24PortID INTEGER
  configV24ConnType INTEGER
  configV24AutoConfig INTEGER
  configV24Speed INTEGER
  configV24CharSize INTEGER
  configV24StopBits INTEGER
  configV24Parity INTEGER
  configV24DSRControl INTEGER
  configV24DCDControl INTEGER
  configV24FlowControl INTEGER
  configV24Update INTEGER

MrmSecurePortEntry  
SEQUENCE    
  mrmSecRepIndex INTEGER
  mrmSecSlotIndex INTEGER
  mrmSecPortIndex INTEGER
  mrmSecPortState INTEGER
  mrmSecNTKState INTEGER
  mrmSecBroadcastState INTEGER
  mrmSecMulticastState INTEGER
  mrmSecLearnMode INTEGER
  mrmSecReportMode INTEGER
  mrmSecMACAddress OCTET STRING
  mrmSecRowStatus INTEGER

EsTableEntry  
SEQUENCE    
  esAddrType INTEGER
  esAddress OCTET STRING
  esSlotNumber INTEGER
  esPortNumber INTEGER

EsModTableEntry  
SEQUENCE    
  esModAddrType INTEGER
  esModAddress OCTET STRING
  esModSlotNumber INTEGER
  esModPortNumber INTEGER

EsPortAccessEntry  
SEQUENCE    
  ecPortCardNo INTEGER
  ecPortPortNo INTEGER
  ecPortIndex INTEGER
  ecPortAddrType INTEGER
  ecPortAddress OCTET STRING

TrapEntry  
SEQUENCE    
  trapStatus INTEGER
  trapDestination IpAddress
  trapCommunity DisplayString
  trapSubject OBJECT IDENTIFIER
  trapCategory INTEGER
  trapThrottle INTEGER

PhyConfigEntry  
SEQUENCE    
  phyLocationType INTEGER
  phyLocation INTEGER
  phySysObjId OBJECT IDENTIFIER
  phyServiceType INTEGER
  phyEntityType INTEGER
  phyHwVersion DisplayString
  phySwVersion DisplayString
  phyServiceId INTEGER
  phyEntityName DisplayString
  phyPowerReq INTEGER
  phyNumberOfPorts INTEGER
  phyLampTest INTEGER
  phyEntityState INTEGER
  phyAction INTEGER

PhyLimitEntry  
SEQUENCE    
  phyLimLocationType INTEGER
  phyLimLimit INTEGER

ServiceEntry  
SEQUENCE    
  serviceId INTEGER
  serviceName DisplayString
  serviceReset INTEGER

AddressTableEntry  
SEQUENCE    
  mgmtServiceId INTEGER
  mgmtSubIndex INTEGER
  mgmtAddressType INTEGER
  mgmtAddress OCTET STRING

FacilityEntry  
SEQUENCE    
  fcSlotNumber INTEGER
  fcFacilityIndex INTEGER
  fcType INTEGER
  fcConnection INTEGER

StatusInputTableEntry  
SEQUENCE    
  statusInputIndex INTEGER
  statusInputState INTEGER
  statusTrapEnable INTEGER
  statusName DisplayString

ChassisMgmtMACEntry  
SEQUENCE    
  macSlotNumber INTEGER
  macIndex INTEGER
  macBroadcastAvailable INTEGER
  macLSAPFiltering INTEGER
  macTypeFiltering INTEGER
  macMaxPDUsize INTEGER
  macPhyAddress OCTET STRING
  macStatus INTEGER

ChassisLedEntry  
SEQUENCE    
  chassisSlotNumber INTEGER
  chassisLedColour INTEGER
  chassisAttentionState INTEGER

MshFaultEntry  
SEQUENCE    
  mshFaultIndex INTEGER
  mshFaultErrorNumber INTEGER
  mshFaultTimeStamp TimeTicks
  mshFaultRestartCount INTEGER

ResTableEntry  
SEQUENCE    
  resRepeater INTEGER
  resMainSlot INTEGER
  resMainPort INTEGER
  resMainState INTEGER
  resStandbySlot INTEGER
  resStandbyPort INTEGER
  resStandbyState INTEGER
  resPairState INTEGER
  resPairModificationStatus INTEGER
  resPairAction INTEGER
  resPairEnable INTEGER

ResStandbyMapTableEntry  
SEQUENCE    
  resSbRepeater INTEGER
  resSbSlot INTEGER
  resSbPort INTEGER
  resSbType INTEGER
  resSbMainSlot INTEGER
  resSbMainPort INTEGER

MrmCardEntry  
SEQUENCE    
  mrmCardServiceId INTEGER
  mrmCardIndex INTEGER
  mrmCardPortCapacity INTEGER
  mrmCardTest INTEGER
  mrmCardDOBPorts INTEGER

MrmPortEntry  
SEQUENCE    
  mrmPortServiceId INTEGER
  mrmPortCardIndex INTEGER
  mrmPortIndex INTEGER
  mrmPortInterfaceType INTEGER
  mrmPortConnectorType INTEGER
  mrmPortAdminStatus INTEGER
  mrmPortAutoPartitionState INTEGER
  mrmPortLinkState INTEGER
  mrmPortBootState INTEGER
  mrmPortESTFilter INTEGER
  mrmPortPartitionEvent INTEGER
  mrmPortLinkStateEvent INTEGER
  mrmPortSecurityAvailable INTEGER
  mrmPortLinkPulse INTEGER

MrmMonitorRepEntry  
SEQUENCE    
  mrmMonRepServiceId INTEGER
  mrmMonRepReadableFrames Counter
  mrmMonRepUnicastFrames Counter
  mrmMonRepMulticastFrames Counter
  mrmMonRepBroadcastFrames Counter
  mrmMonRepReadableOctets Counter
  mrmMonRepUnicastOctets Counter
  mrmMonRepMulticastOctets Counter
  mrmMonRepBroadcastOctets Counter
  mrmMonRepFCSErrors Counter
  mrmMonRepAlignmentErrors Counter
  mrmMonRepFrameTooLongs Counter
  mrmMonRepShortEvents Counter
  mrmMonRepRunts Counter
  mrmMonRepTxCollisions Counter
  mrmMonRepLateEvents Counter
  mrmMonRepVeryLongEvents Counter
  mrmMonRepDataRateMismatches Counter
  mrmMonRepAutoPartitions Counter
  mrmMonRepTotalErrors Counter
  mrmMonRepBound0 Counter
  mrmMonRepBound1 Counter
  mrmMonRepBound2 Counter
  mrmMonRepBound3 Counter
  mrmMonRepBound4 Counter
  mrmMonRepBound5 Counter
  mrmMonRepAction INTEGER

MrmMonitorCardEntry  
SEQUENCE    
  mrmMonCardServiceId INTEGER
  mrmMonCardIndex INTEGER
  mrmMonCardReadableFrames Counter
  mrmMonCardUnicastFrames Counter
  mrmMonCardMulticastFrames Counter
  mrmMonCardBroadcastFrames Counter
  mrmMonCardReadableOctets Counter
  mrmMonCardUnicastOctets Counter
  mrmMonCardMulticastOctets Counter
  mrmMonCardBroadcastOctets Counter
  mrmMonCardFCSErrors Counter
  mrmMonCardAlignmentErrors Counter
  mrmMonCardFrameTooLongs Counter
  mrmMonCardShortEvents Counter
  mrmMonCardRunts Counter
  mrmMonCardLateEvents Counter
  mrmMonCardVeryLongEvents Counter
  mrmMonCardDataRateMismatches Counter
  mrmMonCardAutoPartitions Counter
  mrmMonCardTotalErrors Counter
  mrmMonCardBound0 Counter
  mrmMonCardBound1 Counter
  mrmMonCardBound2 Counter
  mrmMonCardBound3 Counter
  mrmMonCardBound4 Counter
  mrmMonCardBound5 Counter
  mrmMonCardClearCounters INTEGER

MrmMonitorPortEntry  
SEQUENCE    
  mrmMonPortServiceId INTEGER
  mrmMonPortCardIndex INTEGER
  mrmMonPortIndex INTEGER
  mrmMonPortReadableFrames Counter
  mrmMonPortUnicastFrames Counter
  mrmMonPortMulticastFrames Counter
  mrmMonPortBroadcastFrames Counter
  mrmMonPortReadableOctets Counter
  mrmMonPortUnicastOctets Counter
  mrmMonPortMulticastOctets Counter
  mrmMonPortBroadcastOctets Counter
  mrmMonPortFCSErrors Counter
  mrmMonPortAlignmentErrors Counter
  mrmMonPortFrameTooLongs Counter
  mrmMonPortShortEvents Counter
  mrmMonPortRunts Counter
  mrmMonPortCollisions Counter
  mrmMonPortLateEvents Counter
  mrmMonPortVeryLongEvents Counter
  mrmMonPortDataRateMismatches Counter
  mrmMonPortAutoPartitions Counter
  mrmMonPortTotalErrors Counter
  mrmMonPortBound0 Counter
  mrmMonPortBound1 Counter
  mrmMonPortBound2 Counter
  mrmMonPortBound3 Counter
  mrmMonPortBound4 Counter
  mrmMonPortBound5 Counter
  mrmMonPortBandwidthUsed Counter
  mrmMonPortErrorsPer10000Packets Counter
  mrmMonPortClearCounters INTEGER
  mrmMonPortLastAddress OCTET STRING
  mrmMonPortAddressChanges Counter

Defined Values

mib-2 2.2.1
OBJECT IDENTIFIER    

system 2.2.1.1
OBJECT IDENTIFIER    

interfaces 2.2.1.2
OBJECT IDENTIFIER    

at 2.2.1.3
OBJECT IDENTIFIER    

ip 2.2.1.4
OBJECT IDENTIFIER    

icmp 2.2.1.5
OBJECT IDENTIFIER    

tcp 2.2.1.6
OBJECT IDENTIFIER    

udp 2.2.1.7
OBJECT IDENTIFIER    

egp 2.2.1.8
OBJECT IDENTIFIER    

transmission 2.2.1.10
OBJECT IDENTIFIER    

snmp 2.2.1.11
OBJECT IDENTIFIER    

a3Com 2.4.1.43
OBJECT IDENTIFIER    

products 2.4.1.43.1
OBJECT IDENTIFIER    

terminalServer 2.4.1.43.1.1
OBJECT IDENTIFIER    

dedicatedBridgeServer 2.4.1.43.1.2
OBJECT IDENTIFIER    

dedicatedRouteServer 2.4.1.43.1.3
OBJECT IDENTIFIER    

brouter 2.4.1.43.1.4
OBJECT IDENTIFIER    

genericMSWorkstation 2.4.1.43.1.5
OBJECT IDENTIFIER    

genericMSServer 2.4.1.43.1.6
OBJECT IDENTIFIER    

genericUnixServer 2.4.1.43.1.7
OBJECT IDENTIFIER    

hub 2.4.1.43.1.8
OBJECT IDENTIFIER    

cards 2.4.1.43.1.9
OBJECT IDENTIFIER    

linkBuilder3GH 2.4.1.43.1.8.1
OBJECT IDENTIFIER    

linkBuilder10BTi 2.4.1.43.1.8.2
OBJECT IDENTIFIER    

linkBuilderECS 2.4.1.43.1.8.3
OBJECT IDENTIFIER    

linkBuilderMSH 2.4.1.43.1.8.4
OBJECT IDENTIFIER    

linkBuilderFMS 2.4.1.43.1.8.5
OBJECT IDENTIFIER    

linkBuilder3GH-cards 2.4.1.43.1.9.1
OBJECT IDENTIFIER    

linkBuilder10BTi-cards 2.4.1.43.1.9.2
OBJECT IDENTIFIER    

linkBuilderECS-cards 2.4.1.43.1.9.3
OBJECT IDENTIFIER    

linkBuilderMSH-cards 2.4.1.43.1.9.4
OBJECT IDENTIFIER    

linkBuilderFMS-cards 2.4.1.43.1.9.5
OBJECT IDENTIFIER    

linkBuilder10BTi-cards-utp 2.4.1.43.1.9.2.1
OBJECT IDENTIFIER    

linkBuilderFMS-cards-utp 2.4.1.43.1.9.5.1
OBJECT IDENTIFIER    

linkBuilderFMS-cards-coax 2.4.1.43.1.9.5.2
OBJECT IDENTIFIER    

linkBuilderFMS-cards-fiber 2.4.1.43.1.9.5.3
OBJECT IDENTIFIER    

amp-mib 2.4.1.43.3
OBJECT IDENTIFIER    

genericTrap 2.4.1.43.4
OBJECT IDENTIFIER    

viewBuilderApps 2.4.1.43.5
OBJECT IDENTIFIER    

specificTrap 2.4.1.43.6
OBJECT IDENTIFIER    

linkBuilder3GH-mib 2.4.1.43.7
OBJECT IDENTIFIER    

linkBuilder10BTi-mib 2.4.1.43.8
OBJECT IDENTIFIER    

linkBuilderECS-mib 2.4.1.43.9
OBJECT IDENTIFIER    

generic 2.4.1.43.10
OBJECT IDENTIFIER    

genExperimental 2.4.1.43.10.1
OBJECT IDENTIFIER    

setup 2.4.1.43.10.2
OBJECT IDENTIFIER    

sysLoader 2.4.1.43.10.3
OBJECT IDENTIFIER    

security 2.4.1.43.10.4
OBJECT IDENTIFIER    

gauges 2.4.1.43.10.5
OBJECT IDENTIFIER    

asciiAgent 2.4.1.43.10.6
OBJECT IDENTIFIER    

serialIf 2.4.1.43.10.7
OBJECT IDENTIFIER    

repeaterMgmt 2.4.1.43.10.8
OBJECT IDENTIFIER    

endStation 2.4.1.43.10.9
OBJECT IDENTIFIER    

localSnmp 2.4.1.43.10.10
OBJECT IDENTIFIER    

manager 2.4.1.43.10.11
OBJECT IDENTIFIER    

ietf8023RptrMgmtTmp 2.4.1.43.10.12
OBJECT IDENTIFIER    

chassis 2.4.1.43.10.14
OBJECT IDENTIFIER    

mrmResilience 2.4.1.43.10.15
OBJECT IDENTIFIER    

tokenRing 2.4.1.43.10.16
OBJECT IDENTIFIER    

multiRepeater 2.4.1.43.10.17
OBJECT IDENTIFIER    

testData 2.4.1.43.10.1.1
OBJECT IDENTIFIER    

netBuilder-mib 2.4.1.43.11
OBJECT IDENTIFIER    

lBridgeECS-mib 2.4.1.43.12
OBJECT IDENTIFIER    

deskMan-mib 2.4.1.43.13
OBJECT IDENTIFIER    

linkBuilderMSH-mib 2.4.1.43.14
OBJECT IDENTIFIER    

linkBuilderFMS-mib 2.4.1.43.15
OBJECT IDENTIFIER    

sysDescr 2.2.1.1.1
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. It is mandatory that this only contain printable ASCII characters.
OBJECT-TYPE    
  DisplayString Size(0..255)  

sysObjectID 2.2.1.1.2
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.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

sysUpTime 2.2.1.1.3
The time (in hundredths of a second) since the network management portion of the system was last re-initialized.
OBJECT-TYPE    
  TimeTicks  

sysContact 2.2.1.1.4
The textual identification of the contact person for this managed node, together with information on how to contact this person.
OBJECT-TYPE    
  DisplayString Size(0..255)  

sysName 2.2.1.1.5
An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.
OBJECT-TYPE    
  DisplayString Size(0..255)  

sysLocation 2.2.1.1.6
The physical location of this node (e.g., `telephone closet, 3rd floor').
OBJECT-TYPE    
  DisplayString Size(0..255)  

sysServices 2.2.1.1.7
A value which indicates the set of services that this entity primarily offers. 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 primarily 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., IP gateways) 4 end-to-end (e.g., IP hosts) 7 applications (e.g., mail relays) For systems including OSI protocols, layers 5 and 6 may also be counted.
OBJECT-TYPE    
  INTEGER 0..127  

ifNumber 2.2.1.2.1
The number of network interfaces (regardless of their current state) present on this system.
OBJECT-TYPE    
  INTEGER  

ifTable 2.2.1.2.2
A list of interface entries. The number of entries is given by the value of ifNumber.
OBJECT-TYPE    
  SEQUENCE OF  
    IfEntry

ifEntry 2.2.1.2.2.1
An interface entry containing objects at the subnetwork layer and below for a particular interface.
OBJECT-TYPE    
  IfEntry  

ifIndex 2.2.1.2.2.1.1
A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
OBJECT-TYPE    
  INTEGER  

ifDescr 2.2.1.2.2.1.2
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 hardware interface.
OBJECT-TYPE    
  DisplayString Size(0..255)  

ifType 2.2.1.2.2.1.3
The type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack.
OBJECT-TYPE    
  INTEGER other(1), regular1822(2), hdh1822(3), ddn-x25(4), rfc877-x25(5), ethernet-csmacd(6), iso88023-csmacd(7), iso88024-tokenBus(8), iso88025-tokenRing(9), iso88026-man(10), starLan(11), proteon-10Mbit(12), proteon-80Mbit(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), ethernet-3Mbit(26), nsip(27), slip(28), ultra(29), ds3(30), sip(31), frame-relay(32)  

ifMtu 2.2.1.2.2.1.4
The size of the largest datagram 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.
OBJECT-TYPE    
  INTEGER  

ifSpeed 2.2.1.2.2.1.5
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.
OBJECT-TYPE    
  Gauge  

ifPhysAddress 2.2.1.2.2.1.6
The interface's address at the protocol layer immediately `below' the network layer in the protocol stack. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length.
OBJECT-TYPE    
  PhysAddress  

ifAdminStatus 2.2.1.2.2.1.7
The desired state of the interface. The testing(3) state indicates that no operational packets can be passed.
OBJECT-TYPE    
  INTEGER up(1), down(2), testing(3)  

ifOperStatus 2.2.1.2.2.1.8
The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed.
OBJECT-TYPE    
  INTEGER up(1), down(2), testing(3)  

ifLastChange 2.2.1.2.2.1.9
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.
OBJECT-TYPE    
  TimeTicks  

ifInOctets 2.2.1.2.2.1.10
The total number of octets received on the interface, including framing characters.
OBJECT-TYPE    
  Counter  

ifInUcastPkts 2.2.1.2.2.1.11
The number of subnetwork-unicast packets delivered to a higher-layer protocol.
OBJECT-TYPE    
  Counter  

ifInNUcastPkts 2.2.1.2.2.1.12
The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
OBJECT-TYPE    
  Counter  

ifInDiscards 2.2.1.2.2.1.13
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.
OBJECT-TYPE    
  Counter  

ifInErrors 2.2.1.2.2.1.14
The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
OBJECT-TYPE    
  Counter  

ifInUnknownProtos 2.2.1.2.2.1.15
The number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
OBJECT-TYPE    
  Counter  

ifOutOctets 2.2.1.2.2.1.16
The total number of octets transmitted out of the interface, including framing characters.
OBJECT-TYPE    
  Counter  

ifOutUcastPkts 2.2.1.2.2.1.17
The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
OBJECT-TYPE    
  Counter  

ifOutNUcastPkts 2.2.1.2.2.1.18
The total number of packets that higher-level protocols requested be transmitted to a non- unicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent.
OBJECT-TYPE    
  Counter  

ifOutDiscards 2.2.1.2.2.1.19
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.
OBJECT-TYPE    
  Counter  

ifOutErrors 2.2.1.2.2.1.20
The number of outbound packets that could not be transmitted because of errors.
OBJECT-TYPE    
  Counter  

ifOutQLen 2.2.1.2.2.1.21
The length of the output packet queue (in packets).
OBJECT-TYPE    
  Gauge  

ifSpecific 2.2.1.2.2.1.22
A reference to MIB definitions specific to the particular media being used to realize the interface. For example, if the interface is realized by an ethernet, then the value of this object refers to a document defining objects specific to ethernet. If this information is not present, its value should be set to the OBJECT object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

ipForwarding 2.2.1.4.1
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.
OBJECT-TYPE    
  INTEGER forwarding(1), not-forwarding(2)  

ipDefaultTTL 2.2.1.4.2
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.
OBJECT-TYPE    
  INTEGER  

ipInReceives 2.2.1.4.3
The total number of input datagrams received from interfaces, including those received in error.
OBJECT-TYPE    
  Counter  

ipInHdrErrors 2.2.1.4.4
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.
OBJECT-TYPE    
  Counter  

ipInAddrErrors 2.2.1.4.5
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.
OBJECT-TYPE    
  Counter  

ipForwDatagrams 2.2.1.4.6
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.
OBJECT-TYPE    
  Counter  

ipInUnknownProtos 2.2.1.4.7
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
OBJECT-TYPE    
  Counter  

ipInDiscards 2.2.1.4.8
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.
OBJECT-TYPE    
  Counter  

ipInDelivers 2.2.1.4.9
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
OBJECT-TYPE    
  Counter  

ipOutRequests 2.2.1.4.10
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.
OBJECT-TYPE    
  Counter  

ipOutDiscards 2.2.1.4.11
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.
OBJECT-TYPE    
  Counter  

ipOutNoRoutes 2.2.1.4.12
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 datagrams which a host cannot route because all of its default gateways are down.
OBJECT-TYPE    
  Counter  

ipReasmTimeout 2.2.1.4.13
The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
OBJECT-TYPE    
  INTEGER  

ipReasmReqds 2.2.1.4.14
The number of IP fragments received which needed to be reassembled at this entity.
OBJECT-TYPE    
  Counter  

ipReasmOKs 2.2.1.4.15
The number of IP datagrams successfully re- assembled.
OBJECT-TYPE    
  Counter  

ipReasmFails 2.2.1.4.16
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.
OBJECT-TYPE    
  Counter  

ipFragOKs 2.2.1.4.17
The number of IP datagrams that have been successfully fragmented at this entity.
OBJECT-TYPE    
  Counter  

ipFragFails 2.2.1.4.18
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.
OBJECT-TYPE    
  Counter  

ipFragCreates 2.2.1.4.19
The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
OBJECT-TYPE    
  Counter  

ipAddrTable 2.2.1.4.20
The table of addressing information relevant to this entity's IP addresses.
OBJECT-TYPE    
  SEQUENCE OF  
    IpAddrEntry

ipAddrEntry 2.2.1.4.20.1
The addressing information for one of this entity's IP addresses.
OBJECT-TYPE    
  IpAddrEntry  

ipAdEntAddr 2.2.1.4.20.1.1
The IP address to which this entry's addressing information pertains.
OBJECT-TYPE    
  IpAddress  

ipAdEntIfIndex 2.2.1.4.20.1.2
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.
OBJECT-TYPE    
  INTEGER  

ipAdEntNetMask 2.2.1.4.20.1.3
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.
OBJECT-TYPE    
  IpAddress  

ipAdEntBcastAddr 2.2.1.4.20.1.4
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.
OBJECT-TYPE    
  INTEGER  

ipAdEntReasmMaxSiz 2.2.1.4.20.1.5
The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.
OBJECT-TYPE    
  INTEGER 0..65535  

ipRouteTable 2.2.1.4.21
This entity's IP Routing table.
OBJECT-TYPE    
  SEQUENCE OF  
    IpRouteEntry

ipRouteEntry 2.2.1.4.21.1
A route to a particular destination.
OBJECT-TYPE    
  IpRouteEntry  

ipRouteDest 2.2.1.4.21.1.1
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.
OBJECT-TYPE    
  IpAddress  

ipRouteIfIndex 2.2.1.4.21.1.2
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.
OBJECT-TYPE    
  INTEGER  

ipRouteMetric1 2.2.1.4.21.1.3
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.
OBJECT-TYPE    
  INTEGER  

ipRouteMetric2 2.2.1.4.21.1.4
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.
OBJECT-TYPE    
  INTEGER  

ipRouteMetric3 2.2.1.4.21.1.5
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.
OBJECT-TYPE    
  INTEGER  

ipRouteMetric4 2.2.1.4.21.1.6
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.
OBJECT-TYPE    
  INTEGER  

ipRouteNextHop 2.2.1.4.21.1.7
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.)
OBJECT-TYPE    
  IpAddress  

ipRouteType 2.2.1.4.21.1.8
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 disassociates 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.
OBJECT-TYPE    
  INTEGER other(1), invalid(2), direct(3), indirect(4)  

ipRouteProto 2.2.1.4.21.1.9
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.
OBJECT-TYPE    
  INTEGER 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)  

ipRouteAge 2.2.1.4.21.1.10
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.
OBJECT-TYPE    
  INTEGER  

ipRouteMask 2.2.1.4.21.1.11
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.
OBJECT-TYPE    
  IpAddress  

ipRouteMetric5 2.2.1.4.21.1.12
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.
OBJECT-TYPE    
  INTEGER  

ipRouteInfo 2.2.1.4.21.1.13
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 syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

ipNetToMediaTable 2.2.1.4.22
The IP Address Translation table used for mapping from IP addresses to physical addresses.
OBJECT-TYPE    
  SEQUENCE OF  
    IpNetToMediaEntry

ipNetToMediaEntry 2.2.1.4.22.1
Each entry contains one IpAddress to `physical' address equivalence.
OBJECT-TYPE    
  IpNetToMediaEntry  

ipNetToMediaIfIndex 2.2.1.4.22.1.1
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.
OBJECT-TYPE    
  INTEGER  

ipNetToMediaPhysAddress 2.2.1.4.22.1.2
The media-dependent `physical' address.
OBJECT-TYPE    
  PhysAddress  

ipNetToMediaNetAddress 2.2.1.4.22.1.3
The IpAddress corresponding to the media- dependent `physical' address.
OBJECT-TYPE    
  IpAddress  

ipNetToMediaType 2.2.1.4.22.1.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 disassociates 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.
OBJECT-TYPE    
  INTEGER other(1), invalid(2), dynamic(3), static(4)  

ipRoutingDiscards 2.2.1.4.23
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.
OBJECT-TYPE    
  Counter  

icmpInMsgs 2.2.1.5.1
The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
OBJECT-TYPE    
  Counter  

icmpInErrors 2.2.1.5.2
The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
OBJECT-TYPE    
  Counter  

icmpInDestUnreachs 2.2.1.5.3
The number of ICMP Destination Unreachable messages received.
OBJECT-TYPE    
  Counter  

icmpInTimeExcds 2.2.1.5.4
The number of ICMP Time Exceeded messages received.
OBJECT-TYPE    
  Counter  

icmpInParmProbs 2.2.1.5.5
The number of ICMP Parameter Problem messages received.
OBJECT-TYPE    
  Counter  

icmpInSrcQuenchs 2.2.1.5.6
The number of ICMP Source Quench messages received.
OBJECT-TYPE    
  Counter  

icmpInRedirects 2.2.1.5.7
The number of ICMP Redirect messages received.
OBJECT-TYPE    
  Counter  

icmpInEchos 2.2.1.5.8
The number of ICMP Echo (request) messages received.
OBJECT-TYPE    
  Counter  

icmpInEchoReps 2.2.1.5.9
The number of ICMP Echo Reply messages received.
OBJECT-TYPE    
  Counter  

icmpInTimestamps 2.2.1.5.10
The number of ICMP Timestamp (request) messages received.
OBJECT-TYPE    
  Counter  

icmpInTimestampReps 2.2.1.5.11
The number of ICMP Timestamp Reply messages received.
OBJECT-TYPE    
  Counter  

icmpInAddrMasks 2.2.1.5.12
The number of ICMP Address Mask Request messages received.
OBJECT-TYPE    
  Counter  

icmpInAddrMaskReps 2.2.1.5.13
The number of ICMP Address Mask Reply messages received.
OBJECT-TYPE    
  Counter  

icmpOutMsgs 2.2.1.5.14
The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
OBJECT-TYPE    
  Counter  

icmpOutErrors 2.2.1.5.15
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.
OBJECT-TYPE    
  Counter  

icmpOutDestUnreachs 2.2.1.5.16
The number of ICMP Destination Unreachable messages sent.
OBJECT-TYPE    
  Counter  

icmpOutTimeExcds 2.2.1.5.17
The number of ICMP Time Exceeded messages sent.
OBJECT-TYPE    
  Counter  

icmpOutParmProbs 2.2.1.5.18
The number of ICMP Parameter Problem messages sent.
OBJECT-TYPE    
  Counter  

icmpOutSrcQuenchs 2.2.1.5.19
The number of ICMP Source Quench Messages Sent.
OBJECT-TYPE    
  Counter  

icmpOutRedirects 2.2.1.5.20
The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.
OBJECT-TYPE    
  Counter  

icmpOutEchos 2.2.1.5.21
The number of ICMP Echo (request) messages sent.
OBJECT-TYPE    
  Counter  

icmpOutEchoReps 2.2.1.5.22
The number of ICMP Echo Reply messages sent.
OBJECT-TYPE    
  Counter  

icmpOutTimestamps 2.2.1.5.23
The number of ICMP Timestamp (request) messages sent.
OBJECT-TYPE    
  Counter  

icmpOutTimestampReps 2.2.1.5.24
The number of ICMP Timestamp Reply messages sent.
OBJECT-TYPE    
  Counter  

icmpOutAddrMasks 2.2.1.5.25
The number of ICMP Address Mask Request messages sent.
OBJECT-TYPE    
  Counter  

icmpOutAddrMaskReps 2.2.1.5.26
The number of ICMP Address Mask Reply messages sent.
OBJECT-TYPE    
  Counter  

tcpRtoAlgorithm 2.2.1.6.1
The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
OBJECT-TYPE    
  INTEGER other(1), constant(2), rsre(3), vanj(4)  

tcpRtoMin 2.2.1.6.2
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.
OBJECT-TYPE    
  INTEGER  

tcpRtoMax 2.2.1.6.3
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.
OBJECT-TYPE    
  INTEGER  

tcpMaxConn 2.2.1.6.4
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.
OBJECT-TYPE    
  INTEGER  

tcpActiveOpens 2.2.1.6.5
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
OBJECT-TYPE    
  Counter  

tcpPassiveOpens 2.2.1.6.6
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
OBJECT-TYPE    
  Counter  

tcpAttemptFails 2.2.1.6.7
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.
OBJECT-TYPE    
  Counter  

tcpEstabResets 2.2.1.6.8
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.
OBJECT-TYPE    
  Counter  

tcpCurrEstab 2.2.1.6.9
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
OBJECT-TYPE    
  Gauge  

tcpInSegs 2.2.1.6.10
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
OBJECT-TYPE    
  Counter  

tcpOutSegs 2.2.1.6.11
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
OBJECT-TYPE    
  Counter  

tcpRetransSegs 2.2.1.6.12
The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
OBJECT-TYPE    
  Counter  

tcpConnTable 2.2.1.6.13
A table containing TCP connection-specific information.
OBJECT-TYPE    
  SEQUENCE OF  
    TcpConnEntry

tcpConnEntry 2.2.1.6.13.1
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.
OBJECT-TYPE    
  TcpConnEntry  

tcpConnState 2.2.1.6.13.1.1
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).
OBJECT-TYPE    
  INTEGER closed(1), listen(2), synSent(3), synReceived(4), established(5), finWait1(6), finWait2(7), closeWait(8), lastAck(9), closing(10), timeWait(11), deleteTCB(12)  

tcpConnLocalAddress 2.2.1.6.13.1.2
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.
OBJECT-TYPE    
  IpAddress  

tcpConnLocalPort 2.2.1.6.13.1.3
The local port number for this TCP connection.
OBJECT-TYPE    
  INTEGER 0..65535  

tcpConnRemAddress 2.2.1.6.13.1.4
The remote IP address for this TCP connection.
OBJECT-TYPE    
  IpAddress  

tcpConnRemPort 2.2.1.6.13.1.5
The remote port number for this TCP connection.
OBJECT-TYPE    
  INTEGER 0..65535  

tcpInErrs 2.2.1.6.14
The total number of segments received in error (e.g., bad TCP checksums).
OBJECT-TYPE    
  Counter  

tcpOutRsts 2.2.1.6.15
The number of TCP segments sent containing the RST flag.
OBJECT-TYPE    
  Counter  

udpInDatagrams 2.2.1.7.1
The total number of UDP datagrams delivered to UDP users.
OBJECT-TYPE    
  Counter  

udpNoPorts 2.2.1.7.2
The total number of received UDP datagrams for which there was no application at the destination port.
OBJECT-TYPE    
  Counter  

udpInErrors 2.2.1.7.3
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
OBJECT-TYPE    
  Counter  

udpOutDatagrams 2.2.1.7.4
The total number of UDP datagrams sent from this entity.
OBJECT-TYPE    
  Counter  

udpTable 2.2.1.7.5
A table containing UDP listener information.
OBJECT-TYPE    
  SEQUENCE OF  
    UdpEntry

udpEntry 2.2.1.7.5.1
Information about a particular current UDP listener.
OBJECT-TYPE    
  UdpEntry  

udpLocalAddress 2.2.1.7.5.1.1
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.
OBJECT-TYPE    
  IpAddress  

udpLocalPort 2.2.1.7.5.1.2
The local port number for this UDP listener.
OBJECT-TYPE    
  INTEGER 0..65535  

snmpInPkts 2.2.1.11.1
The total number of Messages delivered to the SNMP entity from the transport service.
OBJECT-TYPE    
  Counter  

snmpOutPkts 2.2.1.11.2
The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
OBJECT-TYPE    
  Counter  

snmpInBadVersions 2.2.1.11.3
The total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.
OBJECT-TYPE    
  Counter  

snmpInBadCommunityNames 2.2.1.11.4
The total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.
OBJECT-TYPE    
  Counter  

snmpInBadCommunityUses 2.2.1.11.5
The total number of SNMP Messages delivered to the SNMP protocol entity which represented an SNMP operation which was not allowed by the SNMP community named in the Message.
OBJECT-TYPE    
  Counter  

snmpInASNParseErrs 2.2.1.11.6
The total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.
OBJECT-TYPE    
  Counter  

snmpInTooBigs 2.2.1.11.8
The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `tooBig'.
OBJECT-TYPE    
  Counter  

snmpInNoSuchNames 2.2.1.11.9
The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `noSuchName'.
OBJECT-TYPE    
  Counter  

snmpInBadValues 2.2.1.11.10
The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `badValue'.
OBJECT-TYPE    
  Counter  

snmpInReadOnlys 2.2.1.11.11
The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `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.
OBJECT-TYPE    
  Counter  

snmpInGenErrs 2.2.1.11.12
The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `genErr'.
OBJECT-TYPE    
  Counter  

snmpInTotalReqVars 2.2.1.11.13
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.
OBJECT-TYPE    
  Counter  

snmpInTotalSetVars 2.2.1.11.14
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.
OBJECT-TYPE    
  Counter  

snmpInGetRequests 2.2.1.11.15
The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpInGetNexts 2.2.1.11.16
The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpInSetRequests 2.2.1.11.17
The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpInGetResponses 2.2.1.11.18
The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpInTraps 2.2.1.11.19
The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpOutTooBigs 2.2.1.11.20
The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `tooBig.'
OBJECT-TYPE    
  Counter  

snmpOutNoSuchNames 2.2.1.11.21
The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.
OBJECT-TYPE    
  Counter  

snmpOutBadValues 2.2.1.11.22
The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `badValue'.
OBJECT-TYPE    
  Counter  

snmpOutGenErrs 2.2.1.11.24
The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `genErr'.
OBJECT-TYPE    
  Counter  

snmpOutGetRequests 2.2.1.11.25
The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpOutGetNexts 2.2.1.11.26
The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpOutSetRequests 2.2.1.11.27
The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpOutGetResponses 2.2.1.11.28
The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpOutTraps 2.2.1.11.29
The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
OBJECT-TYPE    
  Counter  

snmpEnableAuthTraps 2.2.1.11.30
Indicates whether the SNMP agent process is permitted to generate authentication-failure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authentication-failure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant between re-initializations of the network management system.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

snmpDot3RptrMgt 2.2.1.22
OBJECT IDENTIFIER    

rptrBasicPackage 2.2.1.22.1
OBJECT IDENTIFIER    

rptrMonitorPackage 2.2.1.22.2
OBJECT IDENTIFIER    

rptrAddrTrackPackage 2.2.1.22.3
OBJECT IDENTIFIER    

rptrRptrInfo 2.2.1.22.1.1
OBJECT IDENTIFIER    

rptrGroupInfo 2.2.1.22.1.2
OBJECT IDENTIFIER    

rptrPortInfo 2.2.1.22.1.3
OBJECT IDENTIFIER    

rptrMonitorRptrInfo 2.2.1.22.2.1
OBJECT IDENTIFIER    

rptrMonitorGroupInfo 2.2.1.22.2.2
OBJECT IDENTIFIER    

rptrMonitorPortInfo 2.2.1.22.2.3
OBJECT IDENTIFIER    

rptrAddrTrackRptrInfo 2.2.1.22.3.1
OBJECT IDENTIFIER    

rptrAddrTrackGroupInfo 2.2.1.22.3.2
OBJECT IDENTIFIER    

rptrAddrTrackPortInfo 2.2.1.22.3.3
OBJECT IDENTIFIER    

rptrGroupCapacity 2.2.1.22.1.1.1
The rptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to rptrGroupCapacity. Some groups may not be present in a given repeater instance, in which case the actual number of groups present will be less than rptrGroupCapacity. The number of groups present will never be greater than rptrGroupCapacity. Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrOperStatus 2.2.1.22.1.1.2
The rptrOperStatus object indicates the operational state of the repeater. The rptrHealthText object may be consulted for more specific information about the state of the repeater's health. In the case of multiple kinds of failures (e.g., repeater failure and port failure), the value of this attribute shall reflect the highest priority failure in the following order: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6)
OBJECT-TYPE    
  INTEGER other(1), ok(2), rptrFailure(3), groupFailure(4), portFailure(5), generalFailure(6)  

rptrHealthText 2.2.1.22.1.1.3
The health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this mechanism to provide detailed failure information or instructions for problem resolution. The contents are agent-specific.
OBJECT-TYPE    
  DisplayString Size(0..255)  

rptrReset 2.2.1.22.1.1.4
Setting this variable to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [11]. Setting this variable to noReset(1) has no effect. The agent will always return the value noReset(1) when this variable is read. This action does not reset the management counters defined in this document nor does it affect the portAdminState parameters. Included in this action is the execution of a disruptive Self-Test. As a result of this action a rptrReset trap may be sent. Note: This action may result in the loss of packets.
OBJECT-TYPE    
  INTEGER noReset(1), reset(2)  

rptrNonDisruptTest 2.2.1.22.1.1.5
Setting this variable to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the following characteristics: (1) The nature of the tests is not specified. (2) The test does not change the state of the repeater or management information about the repeater. (3) The test does not inject packets onto any segment. (4) The test does not prevent the relay of any packets. (5) The test does not interfere with management functions. After performing this test the agent will update the repeater health information. If a change in the repeater health has occurred, the agent will send a rptrHealth trap. Setting this variable to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this variable is read.
OBJECT-TYPE    
  INTEGER noSelfTest(1), selfTest(2)  

rptrTotalPartitionedPorts 2.2.1.22.1.1.6
This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rptrPortOperStatus does not have the value notPresent(3), rptrPortAdminStatus is enabled(1), and rptrPortAutoPartitionState is autoPartitioned(2).
OBJECT-TYPE    
  Gauge  

rptrGroupTable 2.2.1.22.1.2.1
Table of descriptive and status information about the groups of ports.
OBJECT-TYPE    
  SEQUENCE OF  
    RptrGroupEntry

rptrGroupEntry 2.2.1.22.1.2.1.1
An entry in the table, containing information about a single group of ports.
OBJECT-TYPE    
  RptrGroupEntry  

rptrGroupIndex 2.2.1.22.1.2.1.1.1
This variable identifies the group within the repeater for which this entry contains information. This value is never greater than rptrGroupCapacity.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrGroupDescr 2.2.1.22.1.2.1.1.2
A textual description of the group. This value should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other groups in the repeater. 'Wilma Flintstone 6-Port FOIRL Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket V. 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters.
OBJECT-TYPE    
  DisplayString Size(0..255)  

rptrGroupObjectID 2.2.1.22.1.2.1.1.3
The vendor's authoritative identification of the group. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this variable could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port FOIRL Plug-in Module.'
OBJECT-TYPE    
  OBJECT IDENTIFIER  

rptrGroupOperStatus 2.2.1.22.1.2.1.1.4
An object that indicates the operational status of the group. A status of notPresent(4) indicates that the group has been physically removed from the repeater. A status of operational(2) indicates that the group is functioning, and a status of malFunctioning(3) indicates that the group is malfunctioning in some way.
OBJECT-TYPE    
  INTEGER other(1), operational(2), malfunctioning(3), notPresent(4), underTest(5), resetInProgress(6)  

rptrGroupLastOperStatusChange 2.2.1.22.1.2.1.1.5
An object that contains the value of sysUpTime at the time that the value of the rptrGroupOperStatus object for this group last changed. A value of zero indicates that the group's operational status has not changed since the agent last restarted.
OBJECT-TYPE    
  TimeTicks  

rptrGroupPortCapacity 2.2.1.22.1.2.1.1.6
The rptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to rptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrPortTable 2.2.1.22.1.3.1
Table of descriptive and status information about the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    RptrPortEntry

rptrPortEntry 2.2.1.22.1.3.1.1
An entry in the table, containing information about a single port.
OBJECT-TYPE    
  RptrPortEntry  

rptrPortGroupIndex 2.2.1.22.1.3.1.1.1
This variable identifies the group containing the port for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrPortIndex 2.2.1.22.1.3.1.1.2
This variable identifies the port within the group within the repeater for which this entry contains management information. This value can never be greater than rptrGroupPortCapacity for the associated group.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrPortAdminStatus 2.2.1.22.1.3.1.1.3
Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. (In effect, when a port is disabled, the value of rptrPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the rptrPortAutoPartitionState becomes notAutoPartitioned(1), regardless of its pre-disabling state.)
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

rptrPortAutoPartitionState 2.2.1.22.1.3.1.1.4
The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Sect. 9 [11]. They are not differentiated here.
OBJECT-TYPE    
  INTEGER notAutoPartitioned(1), autoPartitioned(2)  

rptrPortOperStatus 2.2.1.22.1.3.1.1.5
This object indicates the port's operational state. The notPresent(3) state indicates the port is physically removed (note this may or may not be possible depending on the type of port.) The operational(1) state indicates that the port is enabled (see rptrPortAdminStatus) and working, even though it might be auto-partitioned (see rptrPortAutoPartitionState).
OBJECT-TYPE    
  INTEGER operational(1), notOperational(2), notPresent(3)  

rptrMonitorTransmitCollisions 2.2.1.22.2.1.1
This counter is incremented every time the repeater state machine enters the TRANSMIT COLLISION state from any state other than ONE PORT LEFT (Ref: Fig 9-2) [11]. Note: The approximate minimum time for counter rollover is 16 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorGroupTable 2.2.1.22.2.2.1
Table of performance and error statistics for the groups.
OBJECT-TYPE    
  SEQUENCE OF  
    RptrMonitorGroupEntry

rptrMonitorGroupEntry 2.2.1.22.2.2.1.1
An entry in the table, containing total performance and error statistics for a single group. Regular retrieval of the information in this table provides a means of tracking the performance and health of the networked devices attached to this group's ports. The counters in this table are redundant in the sense that they are the summations of information already available through other objects. However, these sums provide a considerable optimization of network management traffic over the otherwise necessary retrieval of the individual counters included in each sum.
OBJECT-TYPE    
  RptrMonitorGroupEntry  

rptrMonitorGroupIndex 2.2.1.22.2.2.1.1.1
This object identifies the group within the repeater for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrMonitorGroupTotalFrames 2.2.1.22.2.2.1.1.2
The total number of frames of valid frame length that have been received on the ports in this group. This counter is the summation of the values of the rptrMonitorPortReadableFrames counters for all of the ports in the group. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorGroupTotalOctets 2.2.1.22.2.2.1.1.3
The total number of octets contained in the valid frames that have been received on the ports in this group. This counter is the summation of the values of the rptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

rptrMonitorGroupTotalErrors 2.2.1.22.2.2.1.1.4
The total number of errors which have occurred on all of the ports in this group. This counter is the summation of the values of the rptrMonitorPortTotalErrors counters for all of the ports in the group.
OBJECT-TYPE    
  Counter  

rptrMonitorPortTable 2.2.1.22.2.3.1
Table of performance and error statistics for the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    RptrMonitorPortEntry

rptrMonitorPortEntry 2.2.1.22.2.3.1.1
An entry in the table, containing performance and error statistics for a single port.
OBJECT-TYPE    
  RptrMonitorPortEntry  

rptrMonitorPortGroupIndex 2.2.1.22.2.3.1.1.1
This object identifies the group containing the port for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrMonitorPortIndex 2.2.1.22.2.3.1.1.2
This object identifies the port within the group for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrMonitorPortReadableFrames 2.2.1.22.2.3.1.1.3
This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortReadableOctets 2.2.1.22.2.3.1.1.4
This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

rptrMonitorPortFCSErrors 2.2.1.22.2.3.1.1.5
This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortAlignmentErrors 2.2.1.22.2.3.1.1.6
This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortFrameTooLongs 2.2.1.22.2.3.1.1.7
This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If rptrMonitorPortFrameTooLongs is incremented then neither the rptrMonitorPortAlignmentErrors nor the rptrMonitorPortFCSErrors counter shall be incremented for the frame. The approximate minimum time for rollover of this counter is 61 days.
OBJECT-TYPE    
  Counter  

rptrMonitorPortShortEvents 2.2.1.22.2.3.1.1.8
This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Note: shortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. Implementors may wish to consider selecting the ShortEventMaxTime towards the lower end of the allowed tolerance range to accommodate bit losses suffered through physical channel devices not budgeted for within this standard. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortRunts 2.2.1.22.2.3.1.1.9
This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of runts may exceed ValidPacketMinTime. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortCollisions 2.2.1.22.2.3.1.1.10
This counter is incremented by one for any CarrierEvent signal on any port for which the CollisionEvent signal on this port is asserted. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortLateEvents 2.2.1.22.2.3.1.1.11
This counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. The approximate minimum time for rollover of this counter is 81 hours.
OBJECT-TYPE    
  Counter  

rptrMonitorPortVeryLongEvents 2.2.1.22.2.3.1.1.12
This counter is incremented by one for each CarrierEvent on this port whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). Other counters may be incremented as appropriate.
OBJECT-TYPE    
  Counter  

rptrMonitorPortDataRateMismatches 2.2.1.22.2.3.1.1.13
This counter is incremented by one for each frame received on this port that meets all of the following conditions: a) The CollisionEvent signal is not asserted. b) The ActivityDuration is greater than ValidPacketMinTime. c) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.
OBJECT-TYPE    
  Counter  

rptrMonitorPortAutoPartitions 2.2.1.22.2.3.1.1.14
This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in the partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.
OBJECT-TYPE    
  Counter  

rptrMonitorPortTotalErrors 2.2.1.22.2.3.1.1.15
The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: rptrMonitorPortFCSErrors, rptrMonitorPortAlignmentErrors, rptrMonitorPortFrameTooLongs, rptrMonitorPortShortEvents, rptrMonitorPortLateEvents, rptrMonitorPortVeryLongEvents, and rptrMonitorPortDataRateMismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.
OBJECT-TYPE    
  Counter  

rptrAddrTrackTable 2.2.1.22.3.3.1
Table of address mapping information about the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    RptrAddrTrackEntry

rptrAddrTrackEntry 2.2.1.22.3.3.1.1
An entry in the table, containing address mapping information about a single port.
OBJECT-TYPE    
  RptrAddrTrackEntry  

rptrAddrTrackGroupIndex 2.2.1.22.3.3.1.1.1
This object identifies the group containing the port for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrAddrTrackPortIndex 2.2.1.22.3.3.1.1.2
This object identifies the port within the group for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rptrAddrTrackLastSourceAddress 2.2.1.22.3.3.1.1.3
This object is the SourceAddress of the last readable frame (i.e., counted by rptrMonitorPortReadableFrames) received by this port.
OBJECT-TYPE    
  PhysAddress  

rptrAddrTrackSourceAddrChanges 2.2.1.22.3.3.1.1.4
This counter is incremented by one for each time that the rptrAddrTrackLastSourceAddress attribute for this port has changed. This may indicate whether a link is connected to a single DTE or another multi-user segment. The approximate minimum time for rollover of this counter is 81 hours.
OBJECT-TYPE    
  Counter  

rptrHealth 1
The rptrHealth trap conveys information related to the operational state of the repeater. This trap is sent only when the operational status of the repeater changes. The rptrHealth trap must contain the rptrOperStatus variable. The agent may optionally include the rptrHealthText variable in the varBind list. See the rptrOperStatus and rptrHealthText objects for descriptions of the information that is sent. The agent must throttle the generation of consecutive rptrHealth traps so that there is at least a five-second gap between them.
TRAP-TYPE    

rptrGroupChange 2
This trap is sent when a change occurs in the group structure of a repeater. This occurs only when a group is logically removed from or added to a repeater. The varBind list contains the identifier of the group that was removed or added. The agent must throttle the generation of consecutive rptrGroupChange traps for the same group so that there is at least a five-second gap between them.
TRAP-TYPE    

rptrResetEvent 3
The rptrReset trap conveys information related to the operational state of the repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as an a transition to the START state of Fig 9-2 in section 9 [11], when triggered by a management command (e.g., an SNMP Set on the rptrReset object). The agent must throttle the generation of consecutive rptrReset traps so that there is at least a five-second gap between them. The rptrReset trap is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrHealth variables as optional variables with its coldStart and warmStart trap PDUs. The rptrOperStatus variable must be included in the varbind list sent with this trap. The agent may optionally include the rptrHealthText variable as well.
TRAP-TYPE    

snmpDot3RpMauMgt 2.4.1.43.14.2
OBJECT IDENTIFIER    

rpMauBasicGroup 2.4.1.43.14.2.1
OBJECT IDENTIFIER    

rpMauTable 2.4.1.43.14.2.1.1
Table of descriptive and status information about the groups of ports.
OBJECT-TYPE    
  SEQUENCE OF  
    RpMauEntry

rpMauEntry 2.4.1.43.14.2.1.1.1
An entry in the table, containing information about a single group of ports.
OBJECT-TYPE    
  RpMauEntry  

rpMauGroupIndex 2.4.1.43.14.2.1.1.1.1
This variable uniquely identifies the repeater group that contains the port to which is connected the MAU for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rpMauPortIndex 2.4.1.43.14.2.1.1.1.2
This variable uniquely identifies the repeater port to which is connected the MAU for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rpMauIndex 2.4.1.43.14.2.1.1.1.3
This variable uniquely identifies the MAU for which this entry contains information.
OBJECT-TYPE    
  INTEGER 1..1024  

rpMauType 2.4.1.43.14.2.1.1.1.4
A value that identifies the 10 Mb/s baseband MAU type. The enumeration of the type is such that the value matches the section number of the IEEE 802.3 standard that specifies the particular MAU.
OBJECT-TYPE    
  INTEGER other(1), unknown(2), aui(7), tenbase5(8), foirl(9), tenbase2(10), tenbaseT(14), tenbaseFP(16), tenbaseFB(17), tenbaseFL(18)  

rpMauAdminState 2.4.1.43.14.2.1.1.1.5
The administrative state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the administrative state. A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI and the media transmitter to idle. Standby(4) mode only applies to link type MAUs. The state of mauMediaAvailable is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as if it were powered down. The MAU may return other(1) state for the mauJabber and mauMediaAvailable objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power- on cycle would. Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
OBJECT-TYPE    
  INTEGER other(1), unknown(2), operational(3), standby(4), shutdown(5), reset(6)  

rpMauMediaAvailable 2.4.1.43.14.2.1.1.1.6
If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link integrity/low light state. For an AUI or coax MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2, and 10BASE-FP. NOTE: IEEE 802.3 modified the following descriptive text at their meeting the week of 3/9/92. New text will be provided at the San Diego IETF plenary. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI receives input within startUpDelay of the start of output on DO, loopback will be detected. The value of startUpDelay shall be between 15 and 25 BT (bit times). Transition form input to output_idle on DI while output is present on DO may also be detected on loopback. The value of this attribute will only change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs.
OBJECT-TYPE    
  INTEGER other(1), unknown(2), available(3), notAvailable(4), remoteFault(5), invalidSignal(6)  

rpMauLostMedias 2.4.1.43.14.2.1.1.1.7
A count of the number of times that rpMauMediaAvailable for this MAU instance leaves the state available(3). Implementation of this object is mandatory for MAU instances with rpMauType of AUI(7). It is recommended for all MAU types.
OBJECT-TYPE    
  Counter  

rpMauJabberState 2.4.1.43.14.2.1.1.1.8
If the MAU is in jabber state the attribute is set to the jabbering(4) value. This object returns the value other(1) for MAU type AUI.
OBJECT-TYPE    
  INTEGER other(1), unknown(2), noJabber(3), jabbering(4)  

rpMauJabbers 2.4.1.43.14.2.1.1.1.9
A count of the number of times that rpMauJabberState for this MAU instance enters the state jabbering(4).
OBJECT-TYPE    
  Counter  

rpMauJabberTrap 24
This trap is sent whenever a managed MAU enters the jabber state. The agent must throttle the generation of consecutive rpMauJabberTraps so that there is at least a five-second gap between them.
TRAP-TYPE    

setupGeneral 2.4.1.43.10.2.1
OBJECT IDENTIFIER    

heartbeatInterval 2.4.1.43.10.2.1.1
The time, in seconds, between successive heartbeat events sent to the management station. An interval of 0 indicates that no heartbeat events are to be generated.
OBJECT-TYPE    
  INTEGER 0..65535  

heartbeatEvent 13
Generated at a regular interval to inform the manager this device is still operating and can be reached on the network.
TRAP-TYPE    

setupIp 2.4.1.43.10.2.2
OBJECT IDENTIFIER    

setIpIfTable 2.4.1.43.10.2.2.1
This table shows the IP address and network mask to be used to initialise ipAddrTable on each network interface after the next system restart. There is one entry per network interface and the index is equivalent to the index for the ifTable in the MIB-II interfaces group.
OBJECT-TYPE    
  SEQUENCE OF  
    SetIpIfEntry

setIpIfEntry 2.4.1.43.10.2.2.1.1
The default information relating to a single IP interface.
OBJECT-TYPE    
  SetIpIfEntry  

setIpIfIndex 2.4.1.43.10.2.2.1.1.1
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 (for ifTable).
OBJECT-TYPE    
  INTEGER  

setIpIfAddr 2.4.1.43.10.2.2.1.1.2
The IP address to be used for this interface.
OBJECT-TYPE    
  IpAddress  

setIpIfMask 2.4.1.43.10.2.2.1.1.3
The IP network mask to be used for this interface.
OBJECT-TYPE    
  IpAddress  

setIpIfRouter 2.4.1.43.10.2.2.2
This is the IP address of the default router to be used for sending IP datagrams to remote destinations which have no suitable entry in the routing table. This corresponds to an entry in the MIB-II ipRouteTable with an ipRouteDest field of '0.0.0.0' (the default router) which is set up from this value after a system restart. Changes to this value do not affect the IP routing table until after the next system restart. (To change the default router without a restart, the IP routing table should be changed directly, with an equivalent change to setIpIfRouter only if the change is required to be made permanently.)
OBJECT-TYPE    
  IpAddress  

setupStart 2.4.1.43.10.2.3
OBJECT IDENTIFIER    

startPROMSwVerNo 2.4.1.43.10.2.3.1
The PROM software version number.
OBJECT-TYPE    
  DisplayString Size(1..16)  

startRestartCount 2.4.1.43.10.2.3.2
The number of restarts the box has undergone, either power on or reset switch or watchdog expiries.
OBJECT-TYPE    
  Counter  

startLastRestartType 2.4.1.43.10.2.3.3
The reason for the last system restart. This may be due to management command; watchdog timeout expiry; power interruption; the reset switch was pressed or system error. It is not possible to differentiate between the latter two causes.
OBJECT-TYPE    
  INTEGER other(1), command(2), watchdog(3), power-reset(4), system-error(5)  

startResetAction 2.4.1.43.10.2.3.4
Reset the device with manufacturers default configuration if the manDefaultReset value is written to this item.
OBJECT-TYPE    
  INTEGER nochange(1), manDefaultReset(2)  

startLastSystemError 2.4.1.43.10.2.3.5
The last System Error experienced by the system. This is set equal to the last system error code recorded in non-volatile memory on startup. When the system issues a TRAP indicating the last system error number, the value in non-volatile memory is set to zero. Hence after the next restart this attribute will also have the value zero.
OBJECT-TYPE    
  INTEGER  

startRestartAction 2.4.1.43.10.2.3.6
Restart the device with it's current configuration if the restart value is written to this item.
OBJECT-TYPE    
  INTEGER nochange(1), restart(2)  

loadableDeviceTable 2.4.1.43.10.3.1
A table which is used to control the loading of new software images to the devices controlled by the management agent. By convention the first entry in the table (device type = system(1), instance = 1) controls the loading of the device containing the management agent itself and agents in systems which have no subsidiary devices will have only this one entry in the table. If the system does have subsidiary devices, the other entries have device type = component(2), and control the loading of software into subsidiary devices.
OBJECT-TYPE    
  SEQUENCE OF  
    LoadableDevice

loadableDeviceEntry 2.4.1.43.10.3.1.1
An entry containing the objects for controlling the loading of a software image to a single device within the system.
OBJECT-TYPE    
  LoadableDevice  

slDeviceType 2.4.1.43.10.3.1.1.1
The type of the device to load. Simple devices only contain one device type, which is always `system'. More complex devices, probably containing multiple processors, may contain subsidiary devices denoted (for the purposes of the system loader) as `component'. In general, a `system' device is one which monitors and/or manages the operation of `component' devices.
OBJECT-TYPE    
  INTEGER system(1), component(2)  

slDeviceInstance 2.4.1.43.10.3.1.1.2
The instance of the device type specified by slDeviceType. By convention instance 1 of the system devices is the one containing the management agent, and always exists. Many systems will contain only the one instance of the system device type.
OBJECT-TYPE    
  INTEGER  

slLoadStatus 2.4.1.43.10.3.1.1.3
The status of the last system load operation requested for this device. If the value of this object is in the range 1 to 18 inclusive, the download failed, and the value is an error code indicating the reason why. Codes 1 to 7 are a direct mapping from the TFTP error codes defined in RFC-783. The other error codes have the following meanings:- noResponse(8) load server failed to respond; noResource(9) the download could not be started because of a lack of resources; recLenMismatch(10) the record length differs from that implied by the value of the record length field; invalidRecType(11) the record type is not recognised; checksumError(12) record checksum error; wrongDevice(13) the device type in the file is incorrect; wrongHardwareVersion(14) the software image is not suitable for this version of the hardware; noFileHeader(15) the first record in the file was not a file header; byteCountError(16) the byte count reported in the file trailer record differed from the number of bytes actually received; invalidProgAddress(17) the load file contained a load address which was outside the valid range of memory; eraseFailed(18) unable to erase the program memory; progFailed(19) hardware error programming the memory. The meanings of the remaining values are as follows:- loadPending(20) a load has been requested but has not yet begun; loadActive(21) the device is currently being downloaded; success(22) the device has been downloaded successfully.
OBJECT-TYPE    
  INTEGER fileNotFound(1), accessViolation(2), illegalOperation(4), unknownTransferID(5), noSuchUser(7), noResponse(8), noResource(9), recLenMismatch(10), invalidRecType(11), checksumError(12), wrongDevice(13), wrongHardwareVersion(14), noFileHeader(15), byteCountError(16), invalidProgAddress(17), eraseFailed(18), progFailed(19), loadPending(20), loadActive(21), success(22)  

slSoftwareVersion 2.4.1.43.10.3.1.1.4
The version identifier of the software running in the device.
OBJECT-TYPE    
  DisplayString Size(0..32)  

slHardwareVersion 2.4.1.43.10.3.1.1.5
The version number identifying the revision level of the hardware of the device
OBJECT-TYPE    
  INTEGER  

slFilename 2.4.1.43.10.3.1.1.6
The name of the file which contains the software image to load, or which was the last loaded to the device.
OBJECT-TYPE    
  DisplayString Size(1..128)  

slServerIpAddress 2.4.1.43.10.3.1.1.7
The IP address of the host containing the software image to load, or from which the last image loaded was read.
OBJECT-TYPE    
  IpAddress  

slLoad 2.4.1.43.10.3.1.1.8
Writing 2 to this object causes the agent to attempt to load a new software image to the corresponding device. The file to load and the IP address of the station to load it from are specified in the other objects in the same row of the table.
OBJECT-TYPE    
  INTEGER noAction(1), startDownload(2)  

slFailed 18
When a system load is requested, a response is returned immediately and the load proceeds in the background. If an error is detected this trap is generated indicating the reason why in the status, as follows:- (1) file not found; (2) access violation; (4) illegal TFTP operation; (5) unknown transfer ID; (7) no such user; (8) no response from the load server; (9) the download could not be started because of a lack of resources; (10) the length of a record differs from that implied by the value of the record length field; (11) the record type is not recognised; (12) record checksum error; (13) the device type in the file is incorrect; (14) the software image is not suitable for this version of the hardware; (15) the first record in the file was not a file header; (16) The byte count reported in the file trailer record differed from the number of bytes actually received. When loading a new image into the device containing the agent itself, the agent first reads the beginning of the image file to test if it is accessible and contains a valid image. If there is anything wrong, this trap is generated, no download is performed and the device continues to run uninterrupted. If this check is successful the download proper is begun. Should that fail, it is simply retried continuously until either an attempt succeeds or the device is reset.
TRAP-TYPE    

securityEnableTable 2.4.1.43.10.4.1
A table of permissions for access to the managed device from each of its interfaces, at each security access level. The table is fixed at 5 rows, indexed by the access level.
OBJECT-TYPE    
  SEQUENCE OF  
    SecurityEnableTableEntry

securityEnableTableEntry 2.4.1.43.10.4.1.1
This table allows individual interfaces to be enabled or disabled separately for each security level.
OBJECT-TYPE    
  SecurityEnableTableEntry  

securityLevel 2.4.1.43.10.4.1.1.1
Index to the security enable table.
OBJECT-TYPE    
  INTEGER monitor(1), secureMonitor(2), manager(3), specialist(4), security(5)  

securityCommunityEnable 2.4.1.43.10.4.1.1.2
Community SNMP access permission
OBJECT-TYPE    
  INTEGER enable(1), disable(2), permanentlyEnabled(3), permanentlyDisabled(4)  

securitySecureEnable 2.4.1.43.10.4.1.1.3
Secure SNMP access permission
OBJECT-TYPE    
  INTEGER enable(1), disable(2), permanentlyEnabled(3), permanentlyDisabled(4)  

securityTermEnable 2.4.1.43.10.4.1.1.4
Local Terminal access permission
OBJECT-TYPE    
  INTEGER enable(1), disable(2), permanentlyEnabled(3), permanentlyDisabled(4)  

securityTelnetEnable 2.4.1.43.10.4.1.1.5
Telnet access permission
OBJECT-TYPE    
  INTEGER enable(1), disable(2), permanentlyEnabled(3), permanentlyDisabled(4)  

securityFrontPanelEnable 2.4.1.43.10.4.1.1.6
Front Panel access permission
OBJECT-TYPE    
  INTEGER enable(1), disable(2), permanentlyEnabled(3), permanentlyDisabled(4)  

securityUserTable 2.4.1.43.10.4.2
A table used to define Users. Users can be created/modified or deleted, with the exception of the default Users which cannot be deleted.
OBJECT-TYPE    
  SEQUENCE OF  
    SecurityUserTableEntry

securityUserTableEntry 2.4.1.43.10.4.2.1
1. Creating a new user is done by using the username as a qualifier and SETting any of the items in the row - defaults will be used for the remaining values. 2. Deleting a user is by writing 'invalid' to the status column. 3. There must always be users called 'monitor', 'manager' and 'security' - these cannot be deleted.
OBJECT-TYPE    
  SecurityUserTableEntry  

securityUserStatus 2.4.1.43.10.4.2.1.1
User Status. `invalid' is used to indicate this user is no longer allowed to access this device, and the table entry may subsequently be re-used. Note that the Status of default Users cannot be set to invalid.
OBJECT-TYPE    
  INTEGER valid(1), invalid(2)  

securityUserName 2.4.1.43.10.4.2.1.2
An ASCII string for the User Name. Empty strings are not allowed. The index column for the User Table.
OBJECT-TYPE    
  DisplayString Size(1..10)  

securityUserLevel 2.4.1.43.10.4.2.1.3
User Access Level defining the scope of management allowed for this user. Note that the access level of default Users cannot be changed.
OBJECT-TYPE    
  INTEGER monitor(1), secureMonitor(2), manager(3), specialist(4), security(5)  

securityUserPassword 2.4.1.43.10.4.2.1.4
The password required for user confirmation, when access is made via the local serial port, the front panel, or via Telnet.
OBJECT-TYPE    
  DisplayString Size(0..10)  

securityUserCommunity 2.4.1.43.10.4.2.1.5
The community string identifying this user, when access is made via the original community-based SNMP (RFC1157).
OBJECT-TYPE    
  DisplayString Size(0..32)  

securityUserLocParty 2.4.1.43.10.4.2.1.6
The local party identity of this user, when access is made via secure SNMP.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

securityUserMgrParty 2.4.1.43.10.4.2.1.7
The manager party identity for this user, when access is made via secure SNMP.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

securityAuditLog 2.4.1.43.10.4.3
The audit log is a circular table recording all updates to the managed database on the device. The log must be read regularly by a management device, to maintain a more permanent record of the management history.
OBJECT-TYPE    
  SEQUENCE OF  
    SecurityAuditLogEntry

securityAuditLogEntry 2.4.1.43.10.4.3.1
Each entry contains the time an update was made, by whom, the item referenced, the new value and the result of this request.
OBJECT-TYPE    
  SecurityAuditLogEntry  

securityAuditIndex 2.4.1.43.10.4.3.1.1
Audit Log Index. A monotonically increasing value to uniquely identify an entry in the audit log. This value wraps around (to 1) after reaching the maximum value (65535).
OBJECT-TYPE    
  INTEGER 1..65535  

securityAuditTime 2.4.1.43.10.4.3.1.2
The time, in hundredths of a second since the last system restart, of the update request.
OBJECT-TYPE    
  TimeTicks  

securityAuditUser 2.4.1.43.10.4.3.1.3
The name of the user making the request.
OBJECT-TYPE    
  DisplayString Size(0..10)  

securityAuditObject 2.4.1.43.10.4.3.1.4
The object identifier of the item being updated. This includes any qualifier for the item.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

securityAuditValue 2.4.1.43.10.4.3.1.5
The new value for the item.
OBJECT-TYPE    
  OCTET STRING Size(0..200)  

securityAuditResult 2.4.1.43.10.4.3.1.6
The result of the update request may indicate that it was applied successfully, that it failed (for one of a number of reasons) or that it is still in progress.
OBJECT-TYPE    
  INTEGER success(255), pending(1), too-big(2), failed(3), locked(4), security-violation(5), no-such-function(6), no-such-item(7)  

gaugeTable 2.4.1.43.10.5.1
A table used to define Alarms.
OBJECT-TYPE    
  SEQUENCE OF  
    GaugeTableEntry

gaugeTableEntry 2.4.1.43.10.5.1.1
This table allows Alarms to be set-up on items in the MIB.
OBJECT-TYPE    
  GaugeTableEntry  

gaugeIndex 2.4.1.43.10.5.1.1.1
Unique identifier for a row in the Alarm Table. Allocated by the Alarms Subsystem. An integer in the range 1..gaugeTableSize.
OBJECT-TYPE    
  INTEGER  

gaugeItemId 2.4.1.43.10.5.1.1.2
The object Id and qualifier of the item to be monitored by this alarm.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

gaugeItemType 2.4.1.43.10.5.1.1.3
A 'counter', by definition will always be a positive number. 'Meters' can be signed or unsigned.
OBJECT-TYPE    
  INTEGER counter(1), signedMeter(2), unsignedMeter(3)  

gaugeSamplesPerAverage 2.4.1.43.10.5.1.1.4
The number of samples used to calculate the Alarm Value. The default number of samples is four. If a SamplesPerAverage value of one is used, no average is calculated and the GaugeValue will be the most recent sample.
OBJECT-TYPE    
  INTEGER nonAveraging(1), twoSamples(2), threeSamples(3), maxSamples(4)  

gaugeSamplePeriod 2.4.1.43.10.5.1.1.5
Number of seconds between samples. The total averaging period is given by (gaugeSamplesPerAverage * gaugeSamplePeiod) secs.
OBJECT-TYPE    
  INTEGER 1..4294967295  

gaugeValue 2.4.1.43.10.5.1.1.6
The most recently computed average of the item being monitored. For a `meter' alarm, this is the simple average of the samples. For a 'counter' alarm, this is the average of the differences between successive samples. Counters and unsignedMeters are unsigned 32-bit values and have a maximum value of 4294967295. signedMeters are signed 32-bit values and have a maximum value of +-2147483647 divided by the value of gaugeSamplesPerAverage .
OBJECT-TYPE    
  INTEGER 0..4294967295  

gaugePeakValue 2.4.1.43.10.5.1.1.7
The highest recorded Alarm Value. This will be either a signed or unsigned 32 bit value depending on the gaugeItemType
OBJECT-TYPE    
  INTEGER 0..4294967295  

gaugeThresholdLevel 2.4.1.43.10.5.1.1.8
The threshold value of the the Alarm which causes the ThresholdState to move from the 'ready' state to the 'fired' state and also causes the the ThresholdAction to be taken. It will be either a signed or unsigned 32-bit integer depending on the gaugeItemType.
OBJECT-TYPE    
  INTEGER 0..4294967295  

gaugeRecoveryLevel 2.4.1.43.10.5.1.1.9
The threshold value of the the Alarm which causes the ThresholdState to move from the `fired' state to the `ready' state and also causes the the RecoveryAction to be taken. This value will be either a signed or unsigned 32-bit integer depending on the gaugeItemType.
OBJECT-TYPE    
  INTEGER  

gaugeThresholdAction 2.4.1.43.10.5.1.1.10
This object identifies the action to be taken when an Alarm crosses the Threshold Level. The default action will be to send a trigger event (sendTrap). The actions for 'disable' and 'enable' are device specific.
OBJECT-TYPE    
  INTEGER noAction(1), sendTrap(2), disable(3), enable(4), notifyAndBlipPortOff(5), notifyAndBlipCardOff(6), notifyAndDisablePort(8), notifyAndDisableCard(9), blipPortOff(12), blipCardOff(13), disablePort(14), disableCard(15), notifyAndResilientSwitch(18), notifyBandwidthExceeded(19), notifyErrorsExceeded(20)  

gaugeRecoveryAction 2.4.1.43.10.5.1.1.11
This object identifies the action to be taken when a 'fired' Alarm crosses the Recovery Level. The default action will be to send a recovery event (sendTrap). The actions for 'disable' and 'enable' are device specific.
OBJECT-TYPE    
  INTEGER noAction(1), sendTrap(2), disable(3), enable(4), notifyAndEnablePort(10), notifyAndEnableCard(11), enablePort(16), enableCard(17)  

gaugeState 2.4.1.43.10.5.1.1.12
onTriggersEnabled - This is the normal active state of a alarm. The gaugeValue is updated on every sample and if it crosses the Threshold or Recovery Levels, the corresponding Action will be taken. onTriggersDisabled - This is used when a new device, or alarm is set up and the Threshold and Recovery Levels have not been calibrated. The Alarm runs as normal and the gaugeValue and peakValue are updated. However, if the gaugeValue crosses the Threshold or Recovery Levels, no action is taken. off - This de-activates the alarm, allowing it to be configured safely . Before updating any of the Alarm fields the alarm SHOULD be turned off. Turning the alarm 'off' and then 'on' will not lose any of the sampling data, gaugeValue, peakValue, or thresholdStatus. Updates to the index fields will fail since they are read-only. deleted - An alarm is invalidated by setting it to 'deleted'. A 'deleted' alarm will not be returned by a 'GetNext' request. autoCalibrate - Updates the Threshold and Recovery values according to the current peak value. The gaugeState will then be set to 'onTriggersEnabled'. This can be done when the gaugeState is in states (1), (2), or (3). After this operation: thresholdLevel = peakValue * %gaugeThresholdLevelScaler recoveryLevel = peakValue * %gaugeRecoveryLevelScaler gaugeState = onTriggersEnabled When the gaugeState is set to either of the 'on' states, all the fields for the Alarm are validated. If any of the fields are invalid, the operation will fail. The sampling data, gaugeValue, peakValue and thresholdState can be reset by writing 'onTriggersEnabled', 'onTriggers- Disabled' , or 'autoCalibrate' to the gaugeState when it is already in either of the 'on' states.
OBJECT-TYPE    
  INTEGER onTriggersEnabled(1), onTriggersDisabled(2), off(3), deleted(4), autoCalibrate(5)  

gaugeTableSize 2.4.1.43.10.5.2
Number of entries in Alarm Table. The size of the Alarm Table depends on the requirements and available resources of the device. The actual maximum will probably be around 1000.
OBJECT-TYPE    
  INTEGER 1..65535  

gaugeThresholdLevelScaler 2.4.1.43.10.5.3
The ThresholdLevel is set to this percentage of the peakValue when the Alarm is auto-calibrated. e.g gaugeThresholdLevelScaler = 120 gaugePeakValue = 360 After writing 'calibrateTriggers' to the gaugeState: ThresholdLevel = 120/100 * 360 = 432
OBJECT-TYPE    
  INTEGER 1..65535  

gaugeRecoveryLevelScaler 2.4.1.43.10.5.4
The RecoveryLevel is set to this percentage of the peakValue when the Alarm is auto-calibrated. e.g gaugeRecoveryLevelScaler = 90 gaugePeakValue = 360 After writing 'calibrateTriggers' to the gaugeState: RecoveryLevel = 90/100 * 360 = 324
OBJECT-TYPE    
  INTEGER 1..65535  

gaugeTableUpdate 2.4.1.43.10.5.5
Performs the specified operation on every Alarm in the table.
OBJECT-TYPE    
  INTEGER deleteAll(1)  

gaugeConfigureObjId 2.4.1.43.10.5.6
Object Id and qualifier of alarm(s) to be updated.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

gaugeConfigureColumn 2.4.1.43.10.5.7
Alarm Table Column to be updated.
OBJECT-TYPE    
  INTEGER itemType(1), samplesPerAverage(2), samplePeriod(3), thresholdLevel(4), recoveryLevel(5), thresholdAction(6), recoveryAction(7), gaugeState(8)  

gaugeConfigureValue 2.4.1.43.10.5.8
Value to be written to the 'gaugeConfigureColumn' of the Alarms which match the 'gaugeConfigureObjId'. Writing to this value initiates the operation.
OBJECT-TYPE    
  INTEGER 1..4294967295  

gaugeNextFreeIndex 2.4.1.43.10.5.9
Indicates the gaugeIndex which must be used to create the next alarm. Index is set to GAUGE_TABLE_FULL (zero) if there are no free rows in the table.
OBJECT-TYPE    
  INTEGER  

gaugesThresholdTrap 16
Generated when the Alarm value for this Alarm crosses the Threshold Level.
TRAP-TYPE    

gaugesRecoveryTrap 17
Generated when the Alarm value for this Alarm crosses the Recovery Level.
TRAP-TYPE    

ascTimeAttemptedLogin 2.4.1.43.10.6.1
Time in hundredths of a second when the last Login was attempted. Note, that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR
OBJECT-TYPE    
  TimeTicks  

ascUserNameForLastAttemptedLogin 2.4.1.43.10.6.2
An ASCII string used when attempted login. Empty string is NOT valid. Note, that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR
OBJECT-TYPE    
  DisplayString Size(0..10)  

ascLoginStatus 2.4.1.43.10.6.3
Status of last attempted login. The value 'loginOKFromTelnet' or 'loginOKFromSerialPort' is used to show that the user was allowed access via Telnet or Serial Port. 'DeniedAccessFromTelnet' indicates that a user was denied access via Telnet. The value 'unknownUserFromTelnet' is used to show that a user attempted to login with an invalid user name from a Telnet session and 'incorrectPasswordFromTelnet' is used to show that an invalid password was entered having supplied a valid user name. The value 'securityViolationFromTelnet' is used to indicate that a user has entered the password incorrectly three time consecutively from a Telnet session. Note that only the ASCII Agent can write to this parameter. A write operation from any other agent will result in an ERROR
OBJECT-TYPE    
  INTEGER loginOKFromTelnet(1), loginOKFromSerialPort(2), deniedAccessFromTelnet(3), deniedAccessFromSerialPort(4), unknownUserFromTelnet(5), unknownUserFromSerialPort(6), incorrectPasswordFromTelnet(7), incorrectPasswordFromSerialPort(8), securityViolationFromTelnet(9), securityViolationFromSerialPort(10), nologin(11)  

ascLocalManagementBanner 2.4.1.43.10.6.4
An ASCII string describing the Banner to appear on the FIRST screen of the Local Management Terminal. The string of 490 characters defines a region in the centre of the screen which is 7 Rows by 70 Columns
OBJECT-TYPE    
  DisplayString Size(0..490)  

localManagementUpdate 14
A local management update trap indicates that the configuration of the device has been modified via the ascii agent. This may be through Telnet or the V24 port.
TRAP-TYPE    

securityViolation 15
A security violation trap indicates that a user has attempted to login and failed to enter the correct password Three times consecutively.
TRAP-TYPE    

siSlipPort 2.4.1.43.10.7.1
This object identifies the serial port which SLIP can use to send/receive packets. If this object is set to 0xFFFF, then SLIP cannot send/receive packets.
OBJECT-TYPE    
  INTEGER  

configV24Table 2.4.1.43.10.7.2
Configuration parameters for all the V.24 ports in a system.
OBJECT-TYPE    
  SEQUENCE OF  
    ConfigV24Entry

configV24Entry 2.4.1.43.10.7.2.1
Configuration parameters for a V.24 port in the system.
OBJECT-TYPE    
  ConfigV24Entry  

configV24PortID 2.4.1.43.10.7.2.1.1
This attribute uniquely identifies this V.24 port, it is the index for the V.24 table.
OBJECT-TYPE    
  INTEGER 1..16  

configV24ConnType 2.4.1.43.10.7.2.1.2
This determines if the V.24 port is to be connected locally to a terminal or terminal emulator in which case no interface signals need to be asserted unless requested by other management options below or if the V.24 port is to be connected to a modem when at least DSR is required to be asserted.
OBJECT-TYPE    
  INTEGER local(1), remote(2)  

configV24AutoConfig 2.4.1.43.10.7.2.1.3
This determines if the configuration parameters for the V.24 port, speed, parity, stop bits, character size, are to be determined automatically from an initial character sequence entered by the user or they will be defined by the management options below.
OBJECT-TYPE    
  INTEGER disabled(1), enabled(2)  

configV24Speed 2.4.1.43.10.7.2.1.4
This determines the receive and transmit speed of the V.24 port unless the autoconfigure attribute is enabled when the data rates are determined from the line. Split rx and tx speeds are not possible.
OBJECT-TYPE    
  INTEGER speed1200(4), speed2400(5), speed4800(6), speed9600(7)  

configV24CharSize 2.4.1.43.10.7.2.1.5
This determines the character size, unless the autoconfigure attribute is enabled when character size is determined automatically from the line, it may be set to either 7 or 8 bits.
OBJECT-TYPE    
  INTEGER size7(3), size8(4)  

configV24StopBits 2.4.1.43.10.7.2.1.6
This determines the number of stop bits.
OBJECT-TYPE    
  INTEGER stopOne(1), stopOneDotFive(2), stopTwo(3)  

configV24Parity 2.4.1.43.10.7.2.1.7
This determines the parity option to be used, unless the autoconfigure attribute is enabled when parity is determined automatically from the line, it may be set to either no parity, space (parity bit always 0), mark (parity bit always 1), odd or even.
OBJECT-TYPE    
  INTEGER noParity(1), spaceParity(2), markParity(3), oddParity(4), evenParity(5)  

configV24DSRControl 2.4.1.43.10.7.2.1.8
This attribute is only applicable to local connection types. It determines if DSR need be asserted for a local connection to be made and if the connection need be released if DSR is seen deasserted.
OBJECT-TYPE    
  INTEGER disabled(1), enabled(2)  

configV24DCDControl 2.4.1.43.10.7.2.1.9
This attribute is only applicable to local connection types. It determines if DCD need be asserted for a local connection to be made and if the connection should be release if DCD is seen deasserted.
OBJECT-TYPE    
  INTEGER disabled(1), enabled(2)  

configV24FlowControl 2.4.1.43.10.7.2.1.10
This determines the flow control protocol to be used, either no flow control, xon-xoff, rts-cts full duplex or rts-cts. Full duplex rts/cts uses the rts and cts lines as two independent signals. The DTE signals to the DCE that it is prepared to accept more data by asserting RTS, the DCE signals to the DTE that is is prepared to accept more data by asserting CTS. Half duplex rts/cts (the conventional way) uses CTS as a response to RTS, the DCE flow controls the DTE by only returning CTS is response to a RTS from the DTE when the DCE can accept more data. The DTE can flow control the DCE by raising RTS when it does not want to receive any more input and dropping it when it is ready to receive more.
OBJECT-TYPE    
  INTEGER noFlowControl(1), xonXoff(2), rtsCtsFullDplx(3), rtsCtsHalfDplx(4)  

configV24Update 2.4.1.43.10.7.2.1.11
This attribute may be written to to force the operational V.24 port parameters to be updated.
OBJECT-TYPE    
  INTEGER nochange(1), update(2)  

mrmSecurityPackage 2.4.1.43.10.8.6
OBJECT IDENTIFIER    

mrmSecurePortTable 2.4.1.43.10.8.6.1
A table which allows management of the secure Repeater Ports.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmSecurePortEntry

mrmSecurePortEntry 2.4.1.43.10.8.6.1.1
This table allows repeater ports to be configured on a per port basis. It is index using the objects mrmSecRepIndex, mrmSecSlotIndex and mrmSecPortIndex.
OBJECT-TYPE    
  MrmSecurePortEntry  

mrmSecRepIndex 2.4.1.43.10.8.6.1.1.1
The secure port repeater index. This is the first of three indexes into the mrmSecurePortTable.
OBJECT-TYPE    
  INTEGER  

mrmSecSlotIndex 2.4.1.43.10.8.6.1.1.2
The secure port slot index. This is the second of three indexes into the mrmSecurePortTable.
OBJECT-TYPE    
  INTEGER  

mrmSecPortIndex 2.4.1.43.10.8.6.1.1.3
The secure port port index. This is the third of three indexes into the mrmSecurePortTable.
OBJECT-TYPE    
  INTEGER  

mrmSecPortState 2.4.1.43.10.8.6.1.1.5
Attribute to determine the current security status of a port. This attribute is used by the security trap to identify the reason for the trap. The range of values returned by this object is 1 other 2 unauthorised-station-seen 3 unauthorised-station-port-disabled 4 authorised-station-learnt
OBJECT-TYPE    
  INTEGER other(1), unauthorised-station-seen(2), unauthorised-station-port-disabled(3), authorised-station-learnt(4)  

mrmSecNTKState 2.4.1.43.10.8.6.1.1.6
Attribute to determine whether the Need to Know feature is enabled on the secure Repeater Line Card. The range of values that are valid for this object are 1 other 2 Need to Know is disabled 3 Need to know is enabled It is only valid to write the values 2 and 3.
OBJECT-TYPE    
  INTEGER other(1), disabled(2), enabled(3)  

mrmSecBroadcastState 2.4.1.43.10.8.6.1.1.7
Attribute to determine whether broadcasts are allowed or not allowed to be transmitted. 1 other 2 Broadcasts are not allowed 3 Broadcasts are allowed It is only valid to write the values 2 and 3.
OBJECT-TYPE    
  INTEGER other(1), disabled(2), enabled(3)  

mrmSecMulticastState 2.4.1.43.10.8.6.1.1.8
Attribute to determine whether multicasts are allowed or not allowed to be transmitted. 1 other 2 Multicasts are not allowed 3 Multicasts are allowed It is only valid to write the values 2 and 3.
OBJECT-TYPE    
  INTEGER other(1), disabled(2), enabled(3)  

mrmSecLearnMode 2.4.1.43.10.8.6.1.1.9
Attribute to determine the learning mode of the secure repeater line card. The range of values that are valid for this object are 1 no learning, the address is managed 2 the address of the first incoming packet is learnt 3 the address is continually learning
OBJECT-TYPE    
  INTEGER off(1), single(2), continual(3)  

mrmSecReportMode 2.4.1.43.10.8.6.1.1.10
Attribute to determine the reporting mode of the secure repeater port. The range of values that are valid for this object are 1 Not in applicable learn state 2 Report only 3 Disconnect and Report
OBJECT-TYPE    
  INTEGER off(1), reportonly(2), disconnectandreport(3)  

mrmSecMACAddress 2.4.1.43.10.8.6.1.1.11
The MAC address in use by the secure repeater port.
OBJECT-TYPE    
  OCTET STRING Size(6)  

mrmSecRowStatus 2.4.1.43.10.8.6.1.1.12
This parameter must be set to under-modification before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable.
OBJECT-TYPE    
  INTEGER under-modification(1), stable(2)  

mrmSecurityTrap 37
This trap indicates that this port has detected a security violation.
TRAP-TYPE    

mrmStationLearnTrap 36
This trap indicates that this port has autolearnt an end station address.
TRAP-TYPE    

esDatabaseState 2.4.1.43.10.9.1
This parameter is normally set to 'NO-CHANGE'. When any change is made to the database the value of this parameter becomes 'MODIFIED'. It will remain in this state until a manager sets it back to NO-CHANGE.
OBJECT-TYPE    
  INTEGER noChange(1), modified(2)  

esDatabaseFlush 2.4.1.43.10.9.2
This parameter clears the End Station Database
OBJECT-TYPE    
  INTEGER dummy(1)  

esTable 2.4.1.43.10.9.3
End Station Table
OBJECT-TYPE    
  SEQUENCE OF  
    EsTableEntry

esTableEntry 2.4.1.43.10.9.3.1
The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table is indexed firstly on address type and then on address and so can be used to read the entire contents of the database in end-station address order. Additionally one can read all addresses of a certain type from the database, e.g. all IP addresses known. There are some points to note when reading the contents of the end station table. Firstly the repeater number reported will change if a unit is moved from one repeater within a device to another or if a unit is isolated. Secondly an address will only appear in the table once. If an address which is already present in the database is found on another port then the original record is changed and the 'modified' flag set for that entry.
OBJECT-TYPE    
  EsTableEntry  

esAddrType 2.4.1.43.10.9.3.1.1
The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter allows access to the end station database indexed on address type. For example to read all IEE8021 addresses simply start with a get-next operation on IEEE8021.0 and read until the type changes.
OBJECT-TYPE    
  INTEGER ieee8021(1), internet(2), ipx(3)  

esAddress 2.4.1.43.10.9.3.1.2
The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.
OBJECT-TYPE    
  OCTET STRING Size(6)  

esSlotNumber 2.4.1.43.10.9.3.1.3
Number of unit on which this address was learnt.
OBJECT-TYPE    
  INTEGER  

esPortNumber 2.4.1.43.10.9.3.1.4
Port number of unit on which this address was learnt.
OBJECT-TYPE    
  INTEGER  

esModTable 2.4.1.43.10.9.4
End Station Table ( Modified )
OBJECT-TYPE    
  SEQUENCE OF  
    EsModTableEntry

esModTableEntry 2.4.1.43.10.9.4.1
The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table is indexed firstly on address type and then on address. The view is restricted to include only those entries in the database which have the MODIFIED flag set, i.e. that have been changed since the database was last viewed by the manager. This table can be used to read all the modified entries in the table. This is the table generally used to update the contents of a station map in a management station. Note that it can take a reasonable time to read the contents of the table and in that time other changes may occur. To detect this an additional MIB parameter is specified 'esDatabaseState'. This parameter is normally set to 'NO-CHANGE'. When any change is made to the database the value of this parameter becomes 'MODIFIED'. It will remain in this state until a manager sets it back to NO-CHANGE. The recommended access for this table is as follows: do { write 'NO-CHANGE' to esDatabaseState read modified table read esDatabaseState } while esDatabaseState is MODIFIED There are some points to note when reading the contents of the end station table. Firstly the repeater number reported will change if a unit is moved from one repeater within a device to another or if a unit is isolated. Secondly an address will only appear in the table once. If an address which is already present in the database is found on another port then the original record is changed and the 'modified' flag set for that entry.
OBJECT-TYPE    
  EsModTableEntry  

esModAddrType 2.4.1.43.10.9.4.1.1
The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter allows access to the end station database indexed on address type. For example to read all IEE8021 addresses simply start with a get-next operation on IEEE8021.0 and read until the type changes.
OBJECT-TYPE    
  INTEGER ieee8021(1), internet(2), ipx(3)  

esModAddress 2.4.1.43.10.9.4.1.2
The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.
OBJECT-TYPE    
  OCTET STRING Size(6)  

esModSlotNumber 2.4.1.43.10.9.4.1.3
Unit number on which this address was learnt.
OBJECT-TYPE    
  INTEGER  

esModPortNumber 2.4.1.43.10.9.4.1.4
Port number of unit on which this address was learnt.
OBJECT-TYPE    
  INTEGER  

esPortAccessTable 2.4.1.43.10.9.5
End Station Table ( Port Access )
OBJECT-TYPE    
  SEQUENCE OF  
    EsPortAccessEntry

esPortAccessEntry 2.4.1.43.10.9.5.1
The end station database maintains information concerning end-station address information against device port for 802.3 repeater type devices. This table provides one of three views on that database. The view provided by this particular table allows one to determine the addresses learnt against a particular port.
OBJECT-TYPE    
  EsPortAccessEntry  

ecPortCardNo 2.4.1.43.10.9.5.1.2
Unit part of the identifier for this port.
OBJECT-TYPE    
  INTEGER  

ecPortPortNo 2.4.1.43.10.9.5.1.3
Port number on unit of port for which end station information is required.
OBJECT-TYPE    
  INTEGER  

ecPortIndex 2.4.1.43.10.9.5.1.4
Each port may have a number of addresses against it. This index allows these various addresses to be distinguished. The only stipulation on this number is that it will be unique for the any combination of unit and port. The numbers will be returned in numerically ascending order for a particular unit.port combination but will not be contiguous. For example the following sequence could be seen: Unit Port Index 1 1 211 1 1 231 1 1 438 1 1 672 1 2 120 etc
OBJECT-TYPE    
  INTEGER  

ecPortAddrType 2.4.1.43.10.9.5.1.5
The end station database is capable of storing information for a number of different protocols. Each protocol has it's own addressing format. This parameter identifies the type of address in this entry of the table.
OBJECT-TYPE    
  INTEGER ieee8021(1), internet(2), ipx(3)  

ecPortAddress 2.4.1.43.10.9.5.1.6
The address information held in this entry of the database. The length and format of the string depends on the address type. For example a MAC address will be a 6 byte OCTET STRING, an IP address a 4 byte OCTET STRING.
OBJECT-TYPE    
  OCTET STRING Size(6)  

estStateChange 19
When the end-station table moves from the noChange to modified state this trap is generated. The trap is sent once on this transition and not subsequently until the 'Database State' is changed back to 'noChange' by a manager.
TRAP-TYPE    

estTableFull 20
When the end-station table becomes full this trap is generated.
TRAP-TYPE    

trapTable 2.4.1.43.10.10.1
The snmp Trap database
OBJECT-TYPE    
  SEQUENCE OF  
    TrapEntry

trapEntry 2.4.1.43.10.10.1.1
A single snmp Trap entry
OBJECT-TYPE    
  TrapEntry  

trapStatus 2.4.1.43.10.10.1.1.1
The Status of the Entry valid(1) or invalid(2), writing invalid(2) will delete the entry from the table
OBJECT-TYPE    
  INTEGER valid(1), invalid(2)  

trapDestination 2.4.1.43.10.10.1.1.2
The Destination IP Address
OBJECT-TYPE    
  IpAddress  

trapCommunity 2.4.1.43.10.10.1.1.3
SNMP Community to be used to send traps to destination trapDestination
OBJECT-TYPE    
  DisplayString Size(0..32)  

trapSubject 2.4.1.43.10.10.1.1.4
SNMP Subject Party used to generate traps to destination trapDestination
OBJECT-TYPE    
  OBJECT IDENTIFIER  

trapCategory 2.4.1.43.10.10.1.1.5
32 Bit Mask indicating which trap categories trapDestination is interested in
OBJECT-TYPE    
  INTEGER  

trapThrottle 2.4.1.43.10.10.1.1.6
The Maximum rate at which that trapDestination is willing to receive traps, specified as the minimum interval in milliseconds between traps. A value of zero indicates that no trap throttling is required.
OBJECT-TYPE    
  INTEGER  

coldStart 0
A coldStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered.
TRAP-TYPE    

warmStart 1
A warmStart trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered.
TRAP-TYPE    

linkDown 2
A linkDown trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration.
TRAP-TYPE    

linkUp 3
A linkUp trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up.
TRAP-TYPE    

authenticationFailure 4
An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation- specific mechanism.
TRAP-TYPE    

enclosure 2.4.1.43.10.14.1
OBJECT IDENTIFIER    

physicalConfig 2.4.1.43.10.14.2
OBJECT IDENTIFIER    

logicalConfig 2.4.1.43.10.14.3
OBJECT IDENTIFIER    

enclosureName 2.4.1.43.10.14.1.1
A text string describing the chassis that this MIB describes.
OBJECT-TYPE    
  DisplayString Size(0..32)  

enclosureObjId 2.4.1.43.10.14.1.2
An OBJECT IDENTIFIER specific to this type of this chassis.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

enclosureHardwareVers 2.4.1.43.10.14.1.3
The hardware version number of the chassis. This is a string which includes the major and minor revision levels of the hardware.
OBJECT-TYPE    
  DisplayString Size(0..32)  

phyConfigTable 2.4.1.43.10.14.2.1
This table specifies the current physical configuration of the chassis. This table defines a chassis to contain a number of physical entities. Each such entity has some position that distinguishes it from other potentially similar entities. Examples of entities are cards, power supplies etc. Note that this table only contains information on a location that is currently occupied by some entity.
OBJECT-TYPE    
  SEQUENCE OF  
    PhyConfigEntry

phyConfigEntry 2.4.1.43.10.14.2.1.1
This is one entry in the Physical Configuration Table. It is indexed by physical location.
OBJECT-TYPE    
  PhyConfigEntry  

phyLocationType 2.4.1.43.10.14.2.1.1.1
A chassis contains a number of physical entities such as power supplies and cards. Each physical entity resides at some location. A chassis can contain a number of types of location. Each type of location is specialised to a different purpose. Currently there are four types of location defined. This list can be extended for a particular application: modular-slot: A location of this type can take a number of different entities. They are general purpose and are often the purpose of the device. power-supply-bay: Locations of this type can only contain an instance of a power supply. fan-position: This location can only hold a fan. backplane-position: A position of this type can only contain a backplane.
OBJECT-TYPE    
  INTEGER module(1), power-supply(2), fan(3), backplane(4)  

phyLocation 2.4.1.43.10.14.2.1.1.2
A chassis contains a number of physical entities such as power supplies and cards. Each physical entity resides at some location. Some locations are known and have special purposes, others are general and can contain one of a number of different physical entities. The location type defines a 'kind' of location. Within each category there may be one or more instances of that kind of location. For example in a 10 slot modular hub there are potentially 10 instances of card locations occupied at any time.
OBJECT-TYPE    
  INTEGER  

phySysObjId 2.4.1.43.10.14.2.1.1.3
This object is the OBJECT ID of the entity at this location.
OBJECT-TYPE    
  OBJECT IDENTIFIER  

phyServiceType 2.4.1.43.10.14.2.1.1.4
This object idendifies what kind of entity is present at this location. The value represents a category of entity, for example '802.3 Repeater' or 'power supply'. It does not identify the specific kind of entity within that category, for this refer to the entity type.
OBJECT-TYPE    
  INTEGER dumb8023Repeater(1), ieee8023Repeater(2), ieee8025MauModule(3), ieee8025Ringbuilder(4), fddiConcentrator(5), managementModule(6), standardBackplane(12), extendedBackplane(13), displayPanel(14), fan(17), powerSupply(18), standardBridge(19), bridgePerPort(20), terminalServer(21), remoteBridge(22)  

phyEntityType 2.4.1.43.10.14.2.1.1.5
This object is read in conjunction with service type to uniquely identify the specific physical entity. For example the service type may indicate '802.3 Repeater' while the entity type then says within this category this card is a 12 port UTP card. Below are the values currently allocated: smart8023Repeater 1: 4 Port RLC Coax (ECS Variant) 2: 8 Port UTP (ECS Variant) 3: 4 Port Fibre (ECS Variant) 4: 8 Port STP (ECS Variant) 6: 4 Port Fanout (ECS Variant) 7: 12 Port UTP (ECS Variant) 8: 12 Port STP (ECS Variant) 9: 12 Port Secure UTP (ECS Variant) 10: 12 Port Secure STP (ECS Variant) 11: 6 Port Fibre (ECS Variant) 12: 4 Port Coax (ECS Variant) 32: 6 Port Resilient Fibre (ECS Variant) 65: 12 Port UTP, RJ45 Connector 66: 12 Port UTP, RJ45 Connector (Expandable) 67: 13 Port UTP, Telco + Module 68: 24 Port UTP, 2xTelco 69: 6 Port fibre, ST Connector (Expandable) 70: 6 Port fibre, SMA Connector (Expandable) 71: 6 Port Coax (Expandable) 72: 4 Port Fanout ieee8025MauModule 1: 12 Port UTP, PJ45 Connector 2: 12 Port STP, RJ45 Connector ieee8025Ringbuilder 1: Ring Builder. STP Rin/Rout. RJ45 Connectors managementModule 1: Standard Management Module 2: Enhanced Management Module standardBackplane 1: Standard Backplane displayPanel 1: First release front panel fan 1: Standard Fan Tray powerSupply 2: Standard Power Supply
OBJECT-TYPE    
  INTEGER 0..65535  

phyHwVersion 2.4.1.43.10.14.2.1.1.6
This string identifies the major and minor revision level of the entity at this location.
OBJECT-TYPE    
  DisplayString  

phySwVersion 2.4.1.43.10.14.2.1.1.7
If the entity at this location contains a processor there will be some programme code present. This parameter specifies the version number of that code. The version number is a string. If an entity has no software then the value of this parameter will be 'None'.
OBJECT-TYPE    
  DisplayString  

phyServiceId 2.4.1.43.10.14.2.1.1.8
Every chassis is considered as a collection of services. Each service is implemented using the resources of one or more physical entities within the rack. For example a repeater may be implemented using 2x12 port UTP cards. A power supply by 3 modular power supply entities. The service table contains an entry for each service present in the MSH at any point in time. This object provides a valid index into the service table. By reading the service table and specifying the value of this object one can determine to which service this card belongs.
OBJECT-TYPE    
  INTEGER  

phyEntityName 2.4.1.43.10.14.2.1.1.9
This item is a text string describing the entity at this location.
OBJECT-TYPE    
  DisplayString Size(0..32)  

phyPowerReq 2.4.1.43.10.14.2.1.1.10
This item takes the +5V and +12V current requirements of the entity and uses the values to obtain a power consumption requirement for the entity. A power supply will specify a negative value indicating a source of power. The value is in Watts. Note that the value returned from this object is the simple arithmetic addition of the all power rail requirements. Note that a power supply may be overloaded even if this value is within the spec of the power supplies. Such a situation can occur if the power supplies can source, say X5 Watts at 5V and X12 Watts at 12V. The total power by this definition is X5 + X12. Now a card could draw Y5 and Y12 from the two supplies. If Y12 is X12+1 and Y5 is X5-2, total supply exceeds total consumption but the 12V rail is overloaded!
OBJECT-TYPE    
  INTEGER  

phyNumberOfPorts 2.4.1.43.10.14.2.1.1.11
This object contains the number of physical, external ports this entity is known to have. Note this value only applies to entities that communicate with the management card. For other cards a value of -1 indicates 'unknown'. A value of zero indicates that this entity has no external ports.
OBJECT-TYPE    
  INTEGER  

phyLampTest 2.4.1.43.10.14.2.1.1.12
This object allows a visual test to be performed on entities contained in the rack. The state will be recorded against the card even if that entity does not actually do anything different in this state.
OBJECT-TYPE    
  INTEGER test-off(1), test-on(2)  

phyEntityState 2.4.1.43.10.14.2.1.1.13
Each entity in the chassis has a basic state independent of what function that entity performs within the chassis. If the agent cannot determine the state of a particular entity then the value of this object is 'unknown'.
OBJECT-TYPE    
  INTEGER unknown(1), initialising(2), operational(3), failure(4)  

phyAction 2.4.1.43.10.14.2.1.1.14
This parameter allows a number of actions to be defined for cards in a chassis. Currently only one action is defined: reset. Invoking this operation will reset the specified card.
OBJECT-TYPE    
  INTEGER reset(1)  

phyLimits 2.4.1.43.10.14.2.2
The physical config table describes the chassis as a number of physical entities, each of which has some physical location. This table defines the number of physical locations of each type that actually exists within an instance of the chassis.
OBJECT-TYPE    
  SEQUENCE OF  
    PhyLimitEntry

phyLimitEntry 2.4.1.43.10.14.2.2.1
This entry provides information on the number of physical locations present in this chassis for the specified type of location. Practically this is interpreted as the 'number of power supplies' or 'number of slots' etc.
OBJECT-TYPE    
  PhyLimitEntry  

phyLimLocationType 2.4.1.43.10.14.2.2.1.1
A chassis contains a number of physical entities such as power supplies and cards. Each physical entity resides at some location. A chassis can contain a number of types of location. For each particular type of location there is a limit to the number that may be present in the chassis.
OBJECT-TYPE    
  INTEGER module(1), power-supply(2), fan(3), backplane(4)  

phyLimLimit 2.4.1.43.10.14.2.2.1.2
A chassis contains a number of physical entities such as power supplies and cards. Each physical entity resides at some location. A chassis can contain a number of types of location. For each particular type of location there is a limit to the number that may be present in the chassis. This object identifies the actual number of locations in this chassis that exist for the specified type. Practically this is interpreted as the 'number of power supplies' or 'number of slots' etc.
OBJECT-TYPE    
  INTEGER  

frontPanelDisplayMessage 2.4.1.43.10.14.2.3
This is a string which may be user-defined for display on the lower line of the front panel display.
OBJECT-TYPE    
  DisplayString  

serviceTable 2.4.1.43.10.14.3.1
An MSH chassis is logically comprised of a number of services, e.g. a repeater, bridge etc. Each service is implemented by one or more physical entities. This table contains an entry for each service, providing a name for that service type. Note that every entry in the physical configuration table MUST belong to a service. For example there may NOT be an entry in the phyConfigTable for which the value of phyServiceId does not provide an index into this table of an existent row.
OBJECT-TYPE    
  SEQUENCE OF  
    ServiceEntry

serviceEntry 2.4.1.43.10.14.3.1.1
This is an entry in the Service Table which is indexed by the Service Index for that service.
OBJECT-TYPE    
  ServiceEntry  

serviceId 2.4.1.43.10.14.3.1.1.1
This is a number representing the service in the rack. This id can be used to reference the service elsewhere in the MIB. There are several conventions used to allocate a service Id. Firstly if a card forms a service by itself, for example a bridge card, which uses none of the backplane 802.3 or token ring lines, then the service id is the same as the slot position of that card within the rack. If a service is constructed using one of the backplane 802.3 facilities then the service id is 101, 102 or 103 for the three backplane 802.3 paths. If a service is a token ring fragment then the service id for that service is 200 plus the ring fragment id. For example if Ring Builder builder builds a ring from MAU cards with ring fragment id 7, the corresponding service will be 207.
OBJECT-TYPE    
  INTEGER  

serviceName 2.4.1.43.10.14.3.1.1.2
This is a text string describing the service at a particular Service Index.
OBJECT-TYPE    
  DisplayString Size(0..32)  

serviceReset 2.4.1.43.10.14.3.1.1.3
This action will reset all the cards that belong to this service.
OBJECT-TYPE    
  INTEGER reset(1)  

addressTable 2.4.1.43.10.14.3.2
An MSH chassis contains a number of services. Each service is implemented by one or more cards. A number of services are 'intelligent' in that they communicate with the management station through their own communications stack. This table allows a manager to determine the addresses relevant to a particular service. The table will only have entries present for cards which have management addresses. The table is accessed by specifying a service Id and a sub-index value to distinguish between potentially multiple addresses for a service. NOTE: This table includes entries for the management card itself. The management card entries contain the physical address of the currently active MAC and the IP address of the SNMP stack.
OBJECT-TYPE    
  SEQUENCE OF  
    AddressTableEntry

addressTableEntry 2.4.1.43.10.14.3.2.1
text
OBJECT-TYPE    
  AddressTableEntry  

mgmtServiceId 2.4.1.43.10.14.3.2.1.1
Identifies the service for which this row provides address information.
OBJECT-TYPE    
  INTEGER  

mgmtSubIndex 2.4.1.43.10.14.3.2.1.2
Used to distinguish between multiple addresses for a service in the chassis.
OBJECT-TYPE    
  INTEGER  

mgmtAddressType 2.4.1.43.10.14.3.2.1.3
A card in the chassis can have several addresses, either because of multiple stacks and/or for each relevant level in the stack(s). Each relevant address is represented in this table as a display string and a type. Note that ieee8023Address and ieee8025Address types differ from each other in the bit ordering of the physical address.
OBJECT-TYPE    
  INTEGER ieee8023address(1), ieee8025address(2), ipaddress(3), slipaddress(4)  

mgmtAddress 2.4.1.43.10.14.3.2.1.4
The address as block of bytes. An IP address would occupy 4 bytes and a MAC address 6 bytes.
OBJECT-TYPE    
  OCTET STRING  

facilityTable 2.4.1.43.10.14.3.3
The MSH chassis can simultaneously maintain a number of different sub-networks. Examples of these are the independent repeaters and a number of Token Rings. These fundamental services are referred to as facilities. Each card in the chassis can either provide or be connected to one or more of these facilities. This table provides a means of determining and changing the facilities used by a particular card. The number of entries per card depends on the type of card. For example an 802.3 repeater card can be expected to have a single entry while an 'n' port bridge would have 'n'. The number of entries for a particular card is fixed (can't insert into or delete from this table).
OBJECT-TYPE    
  SEQUENCE OF  
    FacilityEntry

facilityEntry 2.4.1.43.10.14.3.3.1
This is an entry in the Facility Table for a particular slot. There may be more than one entry per slot, each entry being distinguished by FacilityIndex.
OBJECT-TYPE    
  FacilityEntry  

fcSlotNumber 2.4.1.43.10.14.3.3.1.1
Allows access to the table for a particular card. One can use this in conjunction with get-next to read all the facility associations for a particular card.
OBJECT-TYPE    
  INTEGER  

fcFacilityIndex 2.4.1.43.10.14.3.3.1.2
Each card may have multiple entries in the Facility Table. This object provides the means of uniquely identifying each of these entries. Note: It is a convention that the value of this index maps as closely as possible to the physical configuration of the entity represented. For example if a bridge has ports numbered 1, 2, 3 and 4 and all are switchable then this table will have four entries for that entity indexed 1, 2, 3 and 4. Entry with index 1 represents port 1 etc. Similarly if a bridge had two ports numbered, for some reason, 234 and 456 then these values would be used as the index to this table.
OBJECT-TYPE    
  INTEGER  

fcType 2.4.1.43.10.14.3.3.1.3
Each entry in the facility table represents an association between a physical module and one of the facilities provided by the particular configuration of this chassis. There are a number of different types of facilities the chassis can provide. This object identifies the particular type of the facility represented by this table entry. Note that the list of types in this object may be extended in future.
OBJECT-TYPE    
  INTEGER ieee8023(1), ieee8025(2), fddi(3), ringbuilderconnection(4), ieee8023v3(5), atm(6), smds(7)  

fcConnection 2.4.1.43.10.14.3.3.1.4
This object identifies the current assignment of this attachment point in this card. The legal values of this object depends on the type card. Writing an illegal value to this object will cause an error. Generally the table following identifies the possible values, depending on type. Each card type will support a subset of these values. Type Possible Values IEEE8023 0 Isolated (i.e. this interface is not connected to anything). 1,2,3 One of the backplane 802.3 networks. IEEE8025 0 Isolated 1..0x7f A ring number. This must match the value of one of he ring builder cards or the request will be rejected. FDDI Unknown at the moment. Probably similar to IEEE8025 Note: Values greater than 0x7f are reserved to be private values for a particular card. The meaning of these values depend on the card type. A possible use of this is in a multiport 802.3 bridge. Consider such a bridge being capable of bridging between three sources and having two external 802.3 connections. Such a bridge would have three entries in the facility table, one for each bridge source. Each entry could be assigned to one of the backplane 802.3 paths or to one of the two external connections. In this case the possible values for each table entry would be: 0x00 : Not used (isolated) 0x01, 0x02, 0x03 : One of the backplanes 0x81, 0x82 : One of the external connections. The MSH agent will not allow two different entries in this table for the same card to be assigned to the same facility!
OBJECT-TYPE    
  INTEGER  

phyEntityInserted 27
This trap is sent when a new entity is detected in the chassis. The entity is identified both by its location in the chassis and it's type information. The display string is included to make event descriptions more understandable. The phyServiceId indicates to which service the new entity belongs or implements. If the entity belongs to more than one service then this parameter indicates one of the services.
TRAP-TYPE    

phyEntityRemoved 28
This trap is sent when an entity is removed. The qualifier information on the variables identify the location of the entity that has been removed while the entity name is the textual description of the card that was removed.
TRAP-TYPE    

phyFacilityChanged 29
This trap is sent when the facility table is changed. This trap is only send when the change is made as the result of a local management request. The trap includes information about the type of the connection changed and the new connection value.
TRAP-TYPE    

serviceEntityAdded 30
This trap is sent when a card is added to a service. This trap is always sent, regardless of how the card addition occurred. There are two situations in which a card is added to a service. The first is where a new card is inserted and is attached to a service. The second is where an existing card is removed from one service and added to another. Note that the transmission of this trap may imply the creation of a new service.
TRAP-TYPE    

serviceEntityRemoved 31
This trap is sent when an entity is removed from a service. This trap is always sent, regardless of how the card removal occurred. There are two situations in which a card is removed from a service. The first is where a card is removed from the chassis. The second is where an existing card is removed from one service and added to another. The service id in the variables list indicates the service to which to card did belong. Note that the transmission of this trap may imply that the service to which it belongs no longer exists. This is the case where the card was the only current member of the service.
TRAP-TYPE    

physicalStateChange 32
A physical entity in the rack has changed state. This can be the result of a failure or recovery. The variables accompanying this trap identify the entity which has changed state.
TRAP-TYPE    

psuCapacityExceeded 33
The combination of the power requirements of all the entities in the chassis has been calculated to exceed the power capacity of the power supplies present in the chassis.
TRAP-TYPE    

misc 2.4.1.43.1.8.4.1
OBJECT IDENTIFIER    

mshFault 2.4.1.43.1.8.4.2
OBJECT IDENTIFIER    

tempSensorOutput 2.4.1.43.1.8.4.1.1
Mounted on the Management card is a temperature sensing device. This device provides three output levels : OK, WARM and DANGER.
OBJECT-TYPE    
  INTEGER ok(1), warm(2), danger(3)  

statusInputTable 2.4.1.43.1.8.4.1.2
This table provides information about and allows configuration of the 4 general purpose inputs provided by the MSH management card.
OBJECT-TYPE    
  SEQUENCE OF  
    StatusInputTableEntry

statusInputTableEntry 2.4.1.43.1.8.4.1.2.1
This entry describes one of the status inputs provided by the MSH management card.
OBJECT-TYPE    
  StatusInputTableEntry  

statusInputIndex 2.4.1.43.1.8.4.1.2.1.1
Identify one of the status inputs provided by the MSH card.
OBJECT-TYPE    
  INTEGER  

statusInputState 2.4.1.43.1.8.4.1.2.1.2
Each of the MSH management general purpose input lines is actually a pair of wires. In order to use one of the lines the two wires of a particular pair must be connected to some kind of external switch. The switch could for example be a relay or micro-switch. If the two wires of a pair are shorted together by closing the switch the value of this object will be 'closed'. If the switch is open then the value of this object is 'open'. The MSH can be configured to generate an SNMP trap if the state of this object changes.
OBJECT-TYPE    
  INTEGER open(1), closed(2)  

statusTrapEnable 2.4.1.43.1.8.4.1.2.1.3
By setting the value of this object to enable, the MSH will monitor the value of statusInputState for changes. If a change from open to close or from close to open occurs then an SNMP trap is generated. Note that the value of the object is de-bounced by the agent to prevent multiple closures of a 'bouncing' relay causing multiple SNMP traps!
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

statusName 2.4.1.43.1.8.4.1.2.1.4
This is a writable string associated with one of the status inputs. By default the string will initialise to 'Status Input #x' where x is 1, 2, 3 or 4. The user can choose to write a more descriptive string to this object that better describes the use of a particular input. For example if input line 2 is connected to a switch which changes state when a cabinet is opened or closed then the statusName may be set to 'Door Status ' The value of this object is sent to attached management stations in the state change trap.
OBJECT-TYPE    
  DisplayString  

chassisMgmtMACTable 2.4.1.43.1.8.4.1.3
The chassis management card contains an 802.3 MAC and physical layer that can be used for management traffic. In some situations this interface may be inappropriate. For example in a Token Ring only environment it is appropriate to transmit management traffic directly onto the token ring network. The MSH chassis provides the ability for the management card to use either its own MAC or to share the MAC provided by another card in the chassis. There may be a number of MACs available at any particular time from which the management card can choose. This table provides a summary of the available MACs and allows the manager to select one of those for current use. Note: The table also includes the MAC actually present on the management card!
OBJECT-TYPE    
  SEQUENCE OF  
    ChassisMgmtMACEntry

chassisMgmtMACEntry 2.4.1.43.1.8.4.1.3.1
This entry describes the abilities and the state of one of the MACs available for management use in the chassis.
OBJECT-TYPE    
  ChassisMgmtMACEntry  

macSlotNumber 2.4.1.43.1.8.4.1.3.1.1
Index into the table. This is identifies the card on which the MAC that this conceptual row describes.
OBJECT-TYPE    
  INTEGER  

macIndex 2.4.1.43.1.8.4.1.3.1.2
Index into the table. This object distinguishes the MAC described by this row in the conceptual table from the potentially many MACs supported by this card.
OBJECT-TYPE    
  INTEGER  

macBroadcastAvailable 2.4.1.43.1.8.4.1.3.1.3
This is an informational field. It describes the capability of the MAC represented by this conceptual row to receive and transmit a 'broadcast' packet. Note that the shared MAC is currently used to transmit and receive SNMP frames. If an attempt is made to use a MAC with insufficient capability that request will be rejected.
OBJECT-TYPE    
  INTEGER true(1), false(2)  

macLSAPFiltering 2.4.1.43.1.8.4.1.3.1.4
This is an informational field. It describes the capability of the MAC represented by this conceptual row to directly filter packets based on the contents of the LSAP field locally to that card. This can improve performance but is not required for protocol operation. The management card will automatically make best use of this feature if present.
OBJECT-TYPE    
  INTEGER true(1), false(2)  

macTypeFiltering 2.4.1.43.1.8.4.1.3.1.5
This is an informational field. It describes the capability of the MAC represented by this conceptual row to directly filter packets based on type field locally to that card. The type field is held in a SNAP header in IEEE networks or in the Ethernet type field. This can improve performance but is not required for protocol operation. The management card will automatically make best use of this feature if present.
OBJECT-TYPE    
  INTEGER  

macMaxPDUsize 2.4.1.43.1.8.4.1.3.1.6
This is an informational field. It indicates the maximum number of data octets that can be transmitted or received using the shared MAC. When used for SNMP it is likely that a larger PDU size will increase the performance of some management operations. Note that a minimum size of 474 octets is required for SNMPv1
OBJECT-TYPE    
  INTEGER  

macPhyAddress 2.4.1.43.1.8.4.1.3.1.7
The physical MAC address of this specific MAC.
OBJECT-TYPE    
  OCTET STRING  

macStatus 2.4.1.43.1.8.4.1.3.1.8
This object is used to enable or disable a shared MAC for SNMP protocol usage. Note that if a shared MAC has insufficient capabilities to run the SNMP stack then an attempt to set the status to active will fail. This object has three values: available, unavailable and snmpMac. The meaning of each of these is: available: This MAC is currently available to run SNMP on behalf of the management card. unavailable: MAC cannot be selected to carry SNMP on behalf of the management card. The MAC may be in this state for a number of reasons. Examples are insufficient resource on the card, shared MAC already in use for something other than SNMP. snmpMac: This MAC is currently being used as the physical interface for management card SNMP traffic. To select a MAC write snmpMac to this object. If the MAC is suitable and available then the current snmpMac will become unavailable and the selected MAC will become available.
OBJECT-TYPE    
  INTEGER available(1), unavailable(2), snmpMac(3)  

chassisLedTable 2.4.1.43.1.8.4.1.4
This table contains configuration information for each of the card specific LEDs on the front panel module. There is one LED for each card location.
OBJECT-TYPE    
  SEQUENCE OF  
    ChassisLedEntry

chassisLedEntry 2.4.1.43.1.8.4.1.4.1
This entry describes the abilities and the state of one of the MACs available for management use in the chassis.
OBJECT-TYPE    
  ChassisLedEntry  

chassisSlotNumber 2.4.1.43.1.8.4.1.4.1.1
Identifies which LED this row describes.
OBJECT-TYPE    
  INTEGER  

chassisLedColour 2.4.1.43.1.8.4.1.4.1.2
Read the current colour of the LED. This is intended for use by FullView type applications.
OBJECT-TYPE    
  INTEGER off(1), green(2), red(3)  

chassisAttentionState 2.4.1.43.1.8.4.1.4.1.3
Writing 'attention' to this object will cause the LED above that card to become RED. This is intended to be used to aid maintenance of a large system.
OBJECT-TYPE    
  INTEGER ok(1), attention(2)  

mshFaultModifiedFlag 2.4.1.43.1.8.4.2.1
In order to ensure a clean read of the Fault table this flag should be set to clean_read when commencing to read the table and should be examined after reading the entire table. If still set to clean_read then the table read is okay, if not the table should be re-read as it has been modified during the read process.
OBJECT-TYPE    
  INTEGER clean-read(1), modified(2)  

mshFaultTable 2.4.1.43.1.8.4.2.2
The Fault Table.
OBJECT-TYPE    
  SEQUENCE OF  
    MshFaultEntry

mshFaultEntry 2.4.1.43.1.8.4.2.2.1
Information relating to a single fault.
OBJECT-TYPE    
  MshFaultEntry  

mshFaultIndex 2.4.1.43.1.8.4.2.2.1.1
The index into the Fault table. The initial read from the table should be read as the next, from an index of 0; subsequent reads should read the next from the index returned by the previous read.
OBJECT-TYPE    
  INTEGER  

mshFaultErrorNumber 2.4.1.43.1.8.4.2.2.1.2
This error number for this fault log entry.
OBJECT-TYPE    
  INTEGER  

mshFaultTimeStamp 2.4.1.43.1.8.4.2.2.1.3
The time since startup, in milliseconds, when the fault occurred.
OBJECT-TYPE    
  TimeTicks  

mshFaultRestartCount 2.4.1.43.1.8.4.2.2.1.4
The number of restarts at time of fault.
OBJECT-TYPE    
  INTEGER  

tempStateChange 34
Mounted on the Management card is a temperature sensing device. This device provides three output levels : OK, WARM and DANGER. DANGER causes a trap to be generated.
TRAP-TYPE    

statusInputStateChange 35
Sent when the state of one of the management card status inputs changes from open to close or vice-versa and the value of statusTrapEnable is 'enable'
TRAP-TYPE    

resTable 2.4.1.43.10.15.1
Tok_String
OBJECT-TYPE    
  SEQUENCE OF  
    ResTableEntry

resTableEntry 2.4.1.43.10.15.1.1
An MSH may be configured to contain a number of 'resilient pairs'. These are 802.3 point to point connections, e.g. UTP, that allow two repeaters to be connected together in a resilient configuration. In such a configuration one of the two ports is nominated the 'main' port while the other is the 'standby' port. One of these two ports is enabled and is the current active port. The other is present in case of failure of the active port. Such a failure is detected by the MSH and a switch performed. There are a couple of rules that must apply to a resilient pair definition before that definition becomes a valid resilient pair. Firstly both ports must be on the same repeater. Secondly the standby port must be configured to be 'disabled on boot'. That is it must recover from a power failure in a disabled state. This prevents loops in the network. Several tables control the resilient repeater configuration for the MSH. This is the first. This is the main table and allows the creation and deletion of pairs and provides status control and information. The information in this table is indexed on the repeater number and the slot/port location of the main port. To create a new resilient pair simply write any writeable object indexed on the main port. This will create a new entry in the table which has the state 'invalid' (read resPairState). Having created the row, write to the other parameters specifying valid information. When all the parameters are valid the resPairState will become 'operational'. In this state the pair will correctly operate as a resilient pair. If any of the attributes in the table change so that the pair in no linger valid this will be reflected in the resPortState parameter. To delete a resilient pair, write 'delete' to resPairAction.
OBJECT-TYPE    
  ResTableEntry  

resRepeater 2.4.1.43.10.15.1.1.1
A resilient pair must be attached to one of the repeaters in the chassis. This is part of the index value required to access this table.
OBJECT-TYPE    
  INTEGER  

resMainSlot 2.4.1.43.10.15.1.1.2
This is the second key in the index to this table. This is the slot number of the main port in this pair.
OBJECT-TYPE    
  INTEGER  

resMainPort 2.4.1.43.10.15.1.1.3
This is the final, key used to index entries in this table. It is the port number of the main port in the pair.
OBJECT-TYPE    
  INTEGER  

resMainState 2.4.1.43.10.15.1.1.4
Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly OK. This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the OK and Active state. OK and Active means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
OBJECT-TYPE    
  INTEGER failed(1), ok(2), ok-and-active(3)  

resStandbySlot 2.4.1.43.10.15.1.1.5
This is the slot number of the standby port for this pair. The port must be present on the same repeater as the main port and so this information is not duplicated.
OBJECT-TYPE    
  INTEGER  

resStandbyPort 2.4.1.43.10.15.1.1.6
This is the port number of the standby port.
OBJECT-TYPE    
  INTEGER  

resStandbyState 2.4.1.43.10.15.1.1.7
Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly OK. This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the OK and Active state. OK and Active means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
OBJECT-TYPE    
  INTEGER failed(1), ok(2), ok-and-active(3)  

resPairState 2.4.1.43.10.15.1.1.8
Each row in the table is in one of two states, 'invalid' or 'operational'. If the state is 'invalid', the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the MSH configuration. The rules are that both main and standby ports be on the same repeater and that the standby port be 'disable on boot'. Changing the standby card, moving one of the cards to a different repeater are two possible changes that can invalidate a pair configration. If the parameters in the row are all valid then the pair becomes 'operational'.
OBJECT-TYPE    
  INTEGER invalid(1), operational(2)  

resPairModificationStatus 2.4.1.43.10.15.1.1.9
This parameter must be set to under-modification before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable.
OBJECT-TYPE    
  INTEGER under-modification(1), stable(2)  

resPairAction 2.4.1.43.10.15.1.1.10
This is object allows the state of a resilient pair to be modified. The create operation configures the resilient port from this table entry. The delete operation removes the resilient definitions from this table and terminates operation of resilience on this pair of ports. The togglePort operation allows the current active port to be changed to the other port. This second operation will only take affect if the state of the currently non-active port is 'OK'.
OBJECT-TYPE    
  INTEGER create(1), delete(2), togglePort(3)  

resPairEnable 2.4.1.43.10.15.1.1.11
This parameter controls whether the resilient pair is enabled or not. In the disabled state , both ports of the resilient pair are disabled. The default value of this parameter is enable
OBJECT-TYPE    
  INTEGER enable(1), disable(2)  

resStandbyMapTable 2.4.1.43.10.15.2
Tok_String
OBJECT-TYPE    
  SEQUENCE OF  
    ResStandbyMapTableEntry

resStandbyMapTableEntry 2.4.1.43.10.15.2.1
This table is read-only. If provides shortcut information to allow for the translation of a port number to a corresponding main port number. This value can then be used to access the main resilience table. Each resilient pair has two entries in this table, one for the main port and one for the standby port. The entry for the main port returns the same port, the entry for the standby port returns the corresponding main port.
OBJECT-TYPE    
  ResStandbyMapTableEntry  

resSbRepeater 2.4.1.43.10.15.2.1.1
The repeater index of the port being accessed. This is the first of three indices on this table.
OBJECT-TYPE    
  INTEGER  

resSbSlot 2.4.1.43.10.15.2.1.2
Second index on this table.
OBJECT-TYPE    
  INTEGER  

resSbPort 2.4.1.43.10.15.2.1.3
Third index on this table.
OBJECT-TYPE    
  INTEGER  

resSbType 2.4.1.43.10.15.2.1.4
This attribute specifies whether the port indexed is a main or standby port in the resilient pair table. If the port is neither then there will not be a row in this table indexed for that port.
OBJECT-TYPE    
  INTEGER main(1), standby(2)  

resSbMainSlot 2.4.1.43.10.15.2.1.5
This is the slot number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
OBJECT-TYPE    
  INTEGER  

resSbMainPort 2.4.1.43.10.15.2.1.6
This is the port number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
OBJECT-TYPE    
  INTEGER  

resFlushTable 2.4.1.43.10.15.3
This parameter causes all entries in the resilience table to be flushed. Flushing the resilience table does not affect the state of any of the resilient links or ports. Once the table has been flushed , NO resilient links are configured. This parameter is used to ensure that the resilient link table is empty , before new resilient links are configured.
OBJECT-TYPE    
  INTEGER  

resResilienceSwitch 43
This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated. Generation of this trap is summarised in the following table: ------------------------------------------------------------------------------ State | Event Main Backup |Main Fail |Main OK |StandBy Fail |Standby OK ------------------------------------------------------------------------------ Active OK | switch | ----- | state | ----- Active Fail | state | ----- | ----- | state OK Active | state | ----- | switch | ----- Fail Active | ----- | state | state | ----- Fail Fail | ----- | switch | ----- | state ----------------------------------------------------------------------------- In this table '-----' indicates no trap is sent. 'switch' indicates the resResilienceSwitch trap is sent and 'state' indicates resStateChange is sent. NOTE: The agent in the MSH does not suppress any traps that caused the state change. For example if the active link is lost then both a 'loss-of-link' trap AND a resilienceSwitch trap are generated.
TRAP-TYPE    

resStateChange 44
This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated. Generation of this trap is summarised in the following table: ------------------------------------------------------------------------------ State | Event Main Backup |Main Fail |Main OK |StandBy Fail |Standby OK ------------------------------------------------------------------------------ Active OK | switch | ----- | state | ----- Active Fail | state | ----- | ----- | state OK Active | state | ----- | switch | ----- Fail Active | ----- | state | state | ----- Fail Fail | ----- | switch | ----- | state ----------------------------------------------------------------------------- In this table '-----' indicates no trap is sent. 'switch' indicates the resResilienceSwitch trap is sent and 'state' indicates resStateChange is sent. NOTE: The agent in the MSH does not suppress any traps that caused the state change. For example if the active link is lost then both a 'loss-of-link' trap AND a resilienceSwitch trap are generated.
TRAP-TYPE    

mrmBasicPackage 2.4.1.43.10.17.1
OBJECT IDENTIFIER    

mrmMonitorPackage 2.4.1.43.10.17.2
OBJECT IDENTIFIER    

mrmBasCardPackage 2.4.1.43.10.17.1.1
OBJECT IDENTIFIER    

mrmBasPortPackage 2.4.1.43.10.17.1.2
OBJECT IDENTIFIER    

mrmMonRepeaterPackage 2.4.1.43.10.17.2.1
OBJECT IDENTIFIER    

mrmMonCardPackage 2.4.1.43.10.17.2.2
OBJECT IDENTIFIER    

mrmMonPortPackage 2.4.1.43.10.17.2.3
OBJECT IDENTIFIER    

mrmMonDummyPackage 2.4.1.43.10.17.2.4
OBJECT IDENTIFIER    

mrmCardTable 2.4.1.43.10.17.1.1.1
Table of descriptive and status information about the groups of ports.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmCardEntry

mrmCardEntry 2.4.1.43.10.17.1.1.1.1
An entry in the table, containing information about a single group of ports.
OBJECT-TYPE    
  MrmCardEntry  

mrmCardServiceId 2.4.1.43.10.17.1.1.1.1.1
This identifies one of the repeaters within the chassis as the target of a request.
OBJECT-TYPE    
  INTEGER  

mrmCardIndex 2.4.1.43.10.17.1.1.1.1.2
This object identifies the card within the repeater for which this entry contains information.
OBJECT-TYPE    
  INTEGER  

mrmCardPortCapacity 2.4.1.43.10.17.1.1.1.1.3
The mrmCardPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to mrmCardPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.
OBJECT-TYPE    
  INTEGER  

mrmCardTest 2.4.1.43.10.17.1.1.1.1.4
An object that allows the user to test the operation of a card. Writing test(2) to this object forces the card to perform a disruptive test to determine if the card is functioning properly. Reading this object while the card is under test return the value testing(3). When the test is completed, reading this value will return either passed(4) or failed(5).
OBJECT-TYPE    
  INTEGER noTest(1), test(2), testing(3), passed(4), failed(5)  

mrmCardDOBPorts 2.4.1.43.10.17.1.1.1.1.5
MSH Repeater Cards have the ability to disable ports at power up or reset. Ports configured in this way are useful for configuring resilient links because they prevent loops in the network from occurring at startup. The disable on boot feature is determined according to a hardware strap which cannot be changed via software. This parameter is a mask containing a single bit for each port on the card. Port 1 is represented by bit 0 and so-on. If a bit representing a particular port is 0 this port boots up disabled. If the bit is a 1 the port boots up enabled. This parameter allows the state of these parameters to be rapidly determined by a network management application.
OBJECT-TYPE    
  INTEGER  

mrmPortTable 2.4.1.43.10.17.1.2.1
Table of descriptive and status information about the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmPortEntry

mrmPortEntry 2.4.1.43.10.17.1.2.1.1
An entry in the table, containing information about a single port.
OBJECT-TYPE    
  MrmPortEntry  

mrmPortServiceId 2.4.1.43.10.17.1.2.1.1.1
This object identifies the repeater which this entry contains information.
OBJECT-TYPE    
  INTEGER  

mrmPortCardIndex 2.4.1.43.10.17.1.2.1.1.2
This object identifies the group containing the port for which this entry contains information.
OBJECT-TYPE    
  INTEGER  

mrmPortIndex 2.4.1.43.10.17.1.2.1.1.3
This object identifies the port within the group for which this entry contains information. This value can never be greater than mrmCardPortCapacity for the associated group.
OBJECT-TYPE    
  INTEGER  

mrmPortInterfaceType 2.4.1.43.10.17.1.2.1.1.4
This object specifies the type of electrical interface made available at the interface to the card for this port. The interface does not necessarily specify what the actual media to end station is.
OBJECT-TYPE    
  INTEGER unknown(1), maleAUI(2), femaleAUI(3), thinCoax(4), twistedPair(5), unshieldedTP(6), fiber(7)  

mrmPortConnectorType 2.4.1.43.10.17.1.2.1.1.5
This specifies the type of the physical connector through which one would attach to this card. This is distinct from the media type. For example UTP may be connected to the port via either an RJ45 or a Telco connector.
OBJECT-TYPE    
  INTEGER unknown(1), rj45(2), telco(3), st(4), sma(5), dtype-15(6), bnc(7)  

mrmPortAdminStatus 2.4.1.43.10.17.1.2.1.1.6
Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. In effect, when a port is disabled, the value of mrmPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the mrmPortAutoPartitionState becomes notAutoPartitioned(2), regardless of its pre-disabling state.)
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mrmPortAutoPartitionState 2.4.1.43.10.17.1.2.1.1.7
The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Section 9 IEEE 802.3 Std]. They are not differentiated here.
OBJECT-TYPE    
  INTEGER partitioned(1), unpartitioned(2)  

mrmPortLinkState 2.4.1.43.10.17.1.2.1.1.8
This object reflects the presence or absence of signal on this port. The signal may be either light in the case of fiber, or general link present in the case of copper. The value of this parameter is correct regardless of the state the admin state or the partition state.
OBJECT-TYPE    
  INTEGER present(1), absent(2)  

mrmPortBootState 2.4.1.43.10.17.1.2.1.1.9
A repeater port may be enabled or disabled after a reset. This parameter indicates the default for this port.
OBJECT-TYPE    
  INTEGER disable(1), enable(2)  

mrmPortESTFilter 2.4.1.43.10.17.1.2.1.1.10
This attribute determines whether and which address information is extracted from packets received on a port and forwarded to the end station database. It is recommended that this attribute be disabled for inter-repeater links to prevent the database being filled with remote information. To disable this feature for all address types write the value forwardNone (128) to this variable.
OBJECT-TYPE    
  INTEGER forwardMAC(1), forwardIP(2), forwardAll(127), forwardNone(128)  

mrmPortPartitionEvent 2.4.1.43.10.17.1.2.1.1.11
Specifies whether a trap should be sent if the port partition state changes.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mrmPortLinkStateEvent 2.4.1.43.10.17.1.2.1.1.12
Specifies whether a trap should be sent if the link state changes.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mrmPortSecurityAvailable 2.4.1.43.10.17.1.2.1.1.13
Specifies whether security is an available feature on this port. Only ports that have this feature available can have an entry in the repeater security table.
OBJECT-TYPE    
  INTEGER available(1), notAvailable(2)  

mrmPortLinkPulse 2.4.1.43.10.17.1.2.1.1.14
This attribute determines if link pulse generating and monitoring is enabled or disabled for a 10BaseT port. The attribute may take the values of enabled (standard) or disabled (non standard).
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2), notApplicable(3)  

mrmMonitorRepTable 2.4.1.43.10.17.2.1.1
Table of performance and error statistics for the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmMonitorRepEntry

mrmMonitorRepEntry 2.4.1.43.10.17.2.1.1.1
This table provides statistical and control information concerning the entire repeater.
OBJECT-TYPE    
  MrmMonitorRepEntry  

mrmMonRepServiceId 2.4.1.43.10.17.2.1.1.1.1
This parameter is used as the index in this table. A modular chassis contains potentially many repeater services. Each repeater service contains a number of cards (or groups). This parameter allows one of those repeaters to be selected.
OBJECT-TYPE    
  INTEGER  

mrmMonRepReadableFrames 2.4.1.43.10.17.2.1.1.1.2
This counter is incremented by one for each frame whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize and for which FCSError is not asserted that is received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepUnicastFrames 2.4.1.43.10.17.2.1.1.1.3
This counter is incremented by one for each readable frame seen by the Repeater that is addressed to a unicast (non Card) address.
OBJECT-TYPE    
  Counter  

mrmMonRepMulticastFrames 2.4.1.43.10.17.2.1.1.1.4
This counter is incremented by one for each readable frame seen by the Repeater that is addressed to a multicast (non broadcast) address.
OBJECT-TYPE    
  Counter  

mrmMonRepBroadcastFrames 2.4.1.43.10.17.2.1.1.1.5
This counter is incremented by one for each readable frame seen by the Repeater that is addressed to the broadcast address ffffffffffff.
OBJECT-TYPE    
  Counter  

mrmMonRepReadableOctets 2.4.1.43.10.17.2.1.1.1.6
This counter is incremented by the octet count for each readable frame received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepUnicastOctets 2.4.1.43.10.17.2.1.1.1.7
This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonRepMulticastOctets 2.4.1.43.10.17.2.1.1.1.8
This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonRepBroadcastOctets 2.4.1.43.10.17.2.1.1.1.9
This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonRepFCSErrors 2.4.1.43.10.17.2.1.1.1.10
This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepAlignmentErrors 2.4.1.43.10.17.2.1.1.1.11
This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepFrameTooLongs 2.4.1.43.10.17.2.1.1.1.12
This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepShortEvents 2.4.1.43.10.17.2.1.1.1.13
This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepRunts 2.4.1.43.10.17.2.1.1.1.14
This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision detected by the repeater. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepTxCollisions 2.4.1.43.10.17.2.1.1.1.15
This counter is incremented by one for any CarrierEvent signal on any port of this repeater for which the CollisionEvent signal on this port is asserted. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

mrmMonRepLateEvents 2.4.1.43.10.17.2.1.1.1.16
This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepVeryLongEvents 2.4.1.43.10.17.2.1.1.1.17
This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepDataRateMismatches 2.4.1.43.10.17.2.1.1.1.18
This counter is incremented by one each time a packet has been received by this repeater with the data rate detectably mismatched from the local frequency. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepAutoPartitions 2.4.1.43.10.17.2.1.1.1.19
This counter is incremented by one each time the repeater has automatically partitioned any port. NOTE: This counter does not really exist. It is calculated by adding together all the port counters within this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepTotalErrors 2.4.1.43.10.17.2.1.1.1.20
The total number of errors which have occurred on all ports on all groups of this repeater. This counter is the summation of the values of the mrmMonCardTotalErrors counters for all of the cards in the repeater. It is the sum of the following: FCS, Alignment, Frames Too Long, Short Events, Late Events, Very Long Events and Data Rate Mismatches. As a general indicator the individual error counters are too detailed. This parameter gives a very good monitor type parameter.
OBJECT-TYPE    
  Counter  

mrmMonRepBound0 2.4.1.43.10.17.2.1.1.1.21
This object is a summation of the number of frames (including error frames) with a length of 64 octets which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepBound1 2.4.1.43.10.17.2.1.1.1.22
This object is a summation of the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepBound2 2.4.1.43.10.17.2.1.1.1.23
This object is a summation of the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepBound3 2.4.1.43.10.17.2.1.1.1.24
This object is a summation of the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepBound4 2.4.1.43.10.17.2.1.1.1.25
This object is a summation of the number of frames (including error frames) with a length of between 512 and 1023 octets inclusive which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepBound5 2.4.1.43.10.17.2.1.1.1.26
This object is a summation of the number of frames (including error frames) with a length of between 1024 and 1518 octets inclusive which were received by each port on every card of this repeater.
OBJECT-TYPE    
  Counter  

mrmMonRepAction 2.4.1.43.10.17.2.1.1.1.27
This object allows repeater stats specific actions to be implemented. There is only one action currently defined, 'clearCounters'. Writing this value to a repeater entry will clear ALL counters in this repeater. That include port stats, card and repeater totals.
OBJECT-TYPE    
  INTEGER clearCounters(1)  

mrmMonitorCardTable 2.4.1.43.10.17.2.2.1
This table contains parameters about the various repeater cards within the chassis. The table is indexed using the 'serviceIndex' for the repeater and the slot number within that repeater.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmMonitorCardEntry

mrmMonitorCardEntry 2.4.1.43.10.17.2.2.1.1
Status information and control variables for the ports on a single card.
OBJECT-TYPE    
  MrmMonitorCardEntry  

mrmMonCardServiceId 2.4.1.43.10.17.2.2.1.1.1
This parameter is used as the first of two indices in this table. A modular chassis contains potentially many repeater services. Each repeater service contains a number of cards (or groups). In order to uniquely identify a port it is necessary to specify both the repeater service and the card within that repeater.
OBJECT-TYPE    
  INTEGER  

mrmMonCardIndex 2.4.1.43.10.17.2.2.1.1.2
This is the second part of the key on this table. Having selected one of the repeaters within the chassis it is necessary to identify the card within that repeater.
OBJECT-TYPE    
  INTEGER  

mrmMonCardReadableFrames 2.4.1.43.10.17.2.2.1.1.3
This counter is incremented by one for each frame whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize and for which FCSError is not asserted that is received for any port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardUnicastFrames 2.4.1.43.10.17.2.2.1.1.4
This counter is incremented by one for each readable frame seen by the Card that is addressed to a unicast (non Card) address.
OBJECT-TYPE    
  Counter  

mrmMonCardMulticastFrames 2.4.1.43.10.17.2.2.1.1.5
This counter is incremented by one for each readable frame seen by the Card that is addressed to a multicast (non broadcast) address.
OBJECT-TYPE    
  Counter  

mrmMonCardBroadcastFrames 2.4.1.43.10.17.2.2.1.1.6
This counter is incremented by one for each readable frame seen by the Card that is addressed to the broadcast address ffffffffffff.
OBJECT-TYPE    
  Counter  

mrmMonCardReadableOctets 2.4.1.43.10.17.2.2.1.1.7
This counter is incremented by the octet count for each readable frame received by any port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardUnicastOctets 2.4.1.43.10.17.2.2.1.1.8
This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonCardMulticastOctets 2.4.1.43.10.17.2.2.1.1.9
This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonCardBroadcastOctets 2.4.1.43.10.17.2.2.1.1.10
This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonCardFCSErrors 2.4.1.43.10.17.2.2.1.1.11
This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size.
OBJECT-TYPE    
  Counter  

mrmMonCardAlignmentErrors 2.4.1.43.10.17.2.2.1.1.12
This counter is incremented by one for each frame with an FCS error that does have a framing error and which is of legal frame size .
OBJECT-TYPE    
  Counter  

mrmMonCardFrameTooLongs 2.4.1.43.10.17.2.2.1.1.13
This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater.
OBJECT-TYPE    
  Counter  

mrmMonCardShortEvents 2.4.1.43.10.17.2.2.1.1.14
This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected.
OBJECT-TYPE    
  Counter  

mrmMonCardRunts 2.4.1.43.10.17.2.2.1.1.15
This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision.
OBJECT-TYPE    
  Counter  

mrmMonCardLateEvents 2.4.1.43.10.17.2.2.1.1.16
This counter is incremented by one each time a collisions occurs after valid packet min time, a late event is counted as both a collision and as a late event.
OBJECT-TYPE    
  Counter  

mrmMonCardVeryLongEvents 2.4.1.43.10.17.2.2.1.1.17
This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time.
OBJECT-TYPE    
  Counter  

mrmMonCardDataRateMismatches 2.4.1.43.10.17.2.2.1.1.18
This counter is incremented by one each time a packet has been received with the data rate detectably mismatched from the local frequency.
OBJECT-TYPE    
  Counter  

mrmMonCardAutoPartitions 2.4.1.43.10.17.2.2.1.1.19
This counter is incremented by one each time the repeater has automatically partitioned any port.
OBJECT-TYPE    
  Counter  

mrmMonCardTotalErrors 2.4.1.43.10.17.2.2.1.1.20
The total number of errors which have occurred on all ports of this card. This counter is the summation of the values of other error counters (for each port), namely: FCS Errors, Alignment Errors, Frames Too Long, Short Events, Late Events, Very Long Events, Data Rate Mismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.
OBJECT-TYPE    
  Counter  

mrmMonCardBound0 2.4.1.43.10.17.2.2.1.1.21
This object is a summation of the number of frames (including error frames) with a length of 64 octets which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardBound1 2.4.1.43.10.17.2.2.1.1.22
This object is a summation of the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardBound2 2.4.1.43.10.17.2.2.1.1.23
This object is a summation of the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardBound3 2.4.1.43.10.17.2.2.1.1.24
This object is a summation of the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardBound4 2.4.1.43.10.17.2.2.1.1.25
This object is a summation of the number of frames (including error frames) with a length of between 512 and 1023 octets inclusive which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardBound5 2.4.1.43.10.17.2.2.1.1.26
This object is a summation of the number of frames (including error frames) with a length of between 1024 and 1518 octets inclusive which were received by each port on this card.
OBJECT-TYPE    
  Counter  

mrmMonCardClearCounters 2.4.1.43.10.17.2.2.1.1.27
This attribute allows all counters on this Card to be cleared.
OBJECT-TYPE    
  INTEGER noChangeCounters(1), clearCounters(2)  

mrmMonitorPortTable 2.4.1.43.10.17.2.3.1
Table of performance and error statistics for the ports.
OBJECT-TYPE    
  SEQUENCE OF  
    MrmMonitorPortEntry

mrmMonitorPortEntry 2.4.1.43.10.17.2.3.1.1
Performance and error statistics for a single port.
OBJECT-TYPE    
  MrmMonitorPortEntry  

mrmMonPortServiceId 2.4.1.43.10.17.2.3.1.1.1
This parameter selects one of the repeaters within the chassis. This forms the first, most significant index column. Having selected a repeater one must select a card then port within that repeater.
OBJECT-TYPE    
  INTEGER 1..1024  

mrmMonPortCardIndex 2.4.1.43.10.17.2.3.1.1.2
This attribute uniquely identifies this Card within the repeater, it is part of the index for the port table.
OBJECT-TYPE    
  INTEGER  

mrmMonPortIndex 2.4.1.43.10.17.2.3.1.1.3
This attribute uniquely identifies this port within the Card, it is part of the index for the port table.
OBJECT-TYPE    
  INTEGER  

mrmMonPortReadableFrames 2.4.1.43.10.17.2.3.1.1.4
This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortUnicastFrames 2.4.1.43.10.17.2.3.1.1.5
This counter is incremented by one for each readable frame seen by the Card that is addressed to a unicast (non Card) address.
OBJECT-TYPE    
  Counter  

mrmMonPortMulticastFrames 2.4.1.43.10.17.2.3.1.1.6
This counter is incremented by one for each readable frame seen by the Card that is addressed to a multicast (non broadcast) address.
OBJECT-TYPE    
  Counter  

mrmMonPortBroadcastFrames 2.4.1.43.10.17.2.3.1.1.7
This counter is incremented by one for each readable frame seen by the Card that is addressed to the broadcast address.
OBJECT-TYPE    
  Counter  

mrmMonPortReadableOctets 2.4.1.43.10.17.2.3.1.1.8
This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonPortUnicastOctets 2.4.1.43.10.17.2.3.1.1.9
This object is the number of octets contained in valid frames that have been received on this port in which the destination field was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonPortMulticastOctets 2.4.1.43.10.17.2.3.1.1.10
This object is the number of octets contained in valid frames that have been received on this port in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonPortBroadcastOctets 2.4.1.43.10.17.2.3.1.1.11
This object is the number of octets contained in valid frames that have been received on this port in which the destination was the broadcast address ffffffffffff. By attaching a gauge to this counter one can monitor the port for broadcast storms. Action can then be taken to automatically recover network normal operation. The approximate minimum time for rollover of this counter is 58 minutes.
OBJECT-TYPE    
  Counter  

mrmMonPortFCSErrors 2.4.1.43.10.17.2.3.1.1.12
This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortAlignmentErrors 2.4.1.43.10.17.2.3.1.1.13
This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. The approximate minimum time for rollover of this counter is 80 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortFrameTooLongs 2.4.1.43.10.17.2.3.1.1.14
This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If this parameter is incremented then neither the alignment error nor the FCS error counters shall be incremented for the frame. The approximate minimum time for rollover of this counter is 61 days.
OBJECT-TYPE    
  Counter  

mrmMonPortShortEvents 2.4.1.43.10.17.2.3.1.1.15
This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Note: shortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortRunts 2.4.1.43.10.17.2.3.1.1.16
This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of runts may exceed ValidPacketMinTime. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortCollisions 2.4.1.43.10.17.2.3.1.1.17
This counter is incremented by one each time a collision is detected on this port or when the CollisionEvent signal is asserted on this port. The approximate minimum time for rollover of this counter is 16 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortLateEvents 2.4.1.43.10.17.2.3.1.1.18
This counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. The approximate minimum time for rollover of this counter is 81 hours.
OBJECT-TYPE    
  Counter  

mrmMonPortVeryLongEvents 2.4.1.43.10.17.2.3.1.1.19
This counter is incremented by one for each CarrierEvent on this port whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). Other counters may be incremented as appropriate.
OBJECT-TYPE    
  Counter  

mrmMonPortDataRateMismatches 2.4.1.43.10.17.2.3.1.1.20
This counter is incremented by one for each frame received on this port that meets all of the following conditions: a) The CollisionEvent signal is not asserted. b) The ActivityDuration is greater than ValidPacketMinTime. c) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.
OBJECT-TYPE    
  Counter  

mrmMonPortAutoPartitions 2.4.1.43.10.17.2.3.1.1.21
This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause port partitioning are specified in the partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here.
OBJECT-TYPE    
  Counter  

mrmMonPortTotalErrors 2.4.1.43.10.17.2.3.1.1.22
The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: FCS Errors, Alignment Errors, Frames Too Long, Short Events, Late Events, Very Long Events, Data Rate Mismatches. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters.
OBJECT-TYPE    
  Counter  

mrmMonPortBound0 2.4.1.43.10.17.2.3.1.1.23
This object is the number of frames (including error frames) with a length of 64 octets which were received on this port.
OBJECT-TYPE    
  Counter  

mrmMonPortBound1 2.4.1.43.10.17.2.3.1.1.24
This object is the number of frames (including error frames) with a length of between 65 and 127 octets inclusive which were received on this port.
OBJECT-TYPE    
  Counter  

mrmMonPortBound2 2.4.1.43.10.17.2.3.1.1.25
This object is the number of frames (including error frames) with a length of between 128 and 255 octets inclusive which were received on this port.
OBJECT-TYPE    
  Counter  

mrmMonPortBound3 2.4.1.43.10.17.2.3.1.1.26
This object is the number of frames (including error frames) with a length of between 256 and 511 octets inclusive which were received on this port.