Home/Catalog/LX-10-MIB

LX-10-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for LX-10-MIB.

135
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

135 total
Object Name
onstream
OBJECT IDENTIFIER
.1.3.6.1.4.1.135
RFC-1215
Unknown
.1.3.6.1.4.1.135
lx-10
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22
alarmOnReport}
TRAP-TYPE
.1.3.6.1.4.1.135.22.0.1
alarmOffReport}
TRAP-TYPE
.1.3.6.1.4.1.135.22.0.2
sys
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.1
sysGenInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.1.1
sysGenInfoShelfNameName of the managed node.rw
DisplayString
.1.3.6.1.4.1.135.22.1.1.1
sysGenInfoCustomerNameName of the organization that uses the managed node.rw
DisplayString
.1.3.6.1.4.1.135.22.1.1.2
sysGenInfoPhoneNumberPhone number of the organization that uses the managed node.rw
DisplayString
.1.3.6.1.4.1.135.22.1.1.3
sysGenInfoMaintenanceContactMaintenance contact of the managed node.rw
DisplayString
.1.3.6.1.4.1.135.22.1.1.4
sysGenInfoLocationLocation of the managed node.rw
DisplayString
.1.3.6.1.4.1.135.22.1.1.5
sysGenInfoAutoLogoutTimeThe time a TELNET or VT-100 terminal user can maintain a session with the managed node without any keyboard action. Unit: minuterw
INTEGER
.1.3.6.1.4.1.135.22.1.1.6
sysGenInfoPasswordPassword required to access the managed node using VT-100 terminal or TELNET. A get request always returns a NULL string.rw
OCTET STRING
.1.3.6.1.4.1.135.22.1.1.7
sysGenInfoShelfIdLX-10 unit identification number required to identify and set up the device's role (primary/secondary). This number should be unique among interconnected devices.rw
INTEGER
.1.3.6.1.4.1.135.22.1.1.8
sysTimeAndDateTime and date maintained in the managed node.rw
TimeAndDate
.1.3.6.1.4.1.135.22.1.2
sysIpConfig
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.1.3
sysIpConfigHostInterfaceTableTable of available host IP interfaces.
SEQUENCE OF SysIpConfigHostInterfaceEntry
.1.3.6.1.4.1.135.22.1.3.1
sysIpConfigHostInterfaceEntryEach entry contains the IP address and subnet mask of the specified interface and a flag which enables/disables the managed node to broadcast its (RIP) routing table through the interface.
SysIpConfigHostInterfaceEntry
.1.3.6.1.4.1.135.22.1.3.1.1
sysIpConfigHostInterfaceIndexro
Enumeration
.1.3.6.1.4.1.135.22.1.3.1.1.1
sysIpConfigHostInterfaceIpAddressHost's IP address.ro
IpAddress
.1.3.6.1.4.1.135.22.1.3.1.1.2
sysIpConfigHostInterfaceSubnetMaskHost's IP subnet mask.ro
IpAddress
.1.3.6.1.4.1.135.22.1.3.1.1.3
sysIpConfigHostInterfaceXmtRoutingMsgThis object controls whether the managed node should broadcast its (RIP) routing table through the interface.rw
Enumeration
.1.3.6.1.4.1.135.22.1.3.1.1.4
sysIpConfigDefaultGateway
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.1.3.2
sysIpConfigDefaultGatewayIpAddressDefault gateway's IP address.rw
IpAddress
.1.3.6.1.4.1.135.22.1.3.2.1
sysIpConfigDefaultGatewaySubnetMaskDefault gateway's IP subnet mask.rw
IpAddress
.1.3.6.1.4.1.135.22.1.3.2.2
sysIpConfigTrapClientTableTrap client table has 4 entries
SEQUENCE OF SysIpConfigTrapClientEntry
.1.3.6.1.4.1.135.22.1.3.3
sysIpConfigTrapClientEntryEach entry contains IP address and port number of an SNMP manager which receives traps from the managed node.
SysIpConfigTrapClientEntry
.1.3.6.1.4.1.135.22.1.3.3.1
sysIpConfigTrapClientIndexrw
INTEGER
.1.3.6.1.4.1.135.22.1.3.3.1.1
sysIpConfigTrapClientIpAddressTrap client's IP address.rw
IpAddress
.1.3.6.1.4.1.135.22.1.3.3.1.2
sysIpConfigTrapClientSubnetMaskTrap client's IP subnet mask.rw
IpAddress
.1.3.6.1.4.1.135.22.1.3.3.1.3
sysIpConfigTrapClientPortNumberTrap client's port number.rw
INTEGER
.1.3.6.1.4.1.135.22.1.3.3.1.4
sysIpConfigCommunityNameCommunity name of the managed node. A get request for an instance of this object always returns a NULL string.rw
DisplayString
.1.3.6.1.4.1.135.22.1.3.4
sysIpConfigMacAddressMAC-layer address of the management Ethernet port.ro
PhysAddress (SNMPv2-TC)
.1.3.6.1.4.1.135.22.1.3.5
sysRs232TableThis table contains 2 rows. The first row shows the physical configuration of the port connected to a VT100 termianl. The second row is used to configure the port which supports SLIP. Access to the first row is read-only and access to the second row is read-write.
SEQUENCE OF SysRs232Entry
.1.3.6.1.4.1.135.22.1.4
sysRs232EntryEach entry contains the attributes of a serial port.
SysRs232Entry
.1.3.6.1.4.1.135.22.1.4.1
sysRs232PortThe managed node has 2 serial ports: port 1 and port 2.ro
Enumeration
.1.3.6.1.4.1.135.22.1.4.1.1
sysRs232BaudRateBaud rate. The instance of this object in port-1 is read-only.rw
Enumeration
.1.3.6.1.4.1.135.22.1.4.1.2
sysRs232ParityParity. The instance of this object in port-1 is read-only.rw
Enumeration
.1.3.6.1.4.1.135.22.1.4.1.3
sysRs232DataBitsNumber of data bits. The instance of this object in port-1 is read-only.rw
Enumeration
.1.3.6.1.4.1.135.22.1.4.1.4
sysRs232StopBitsNumber of stop bits. The instance of this object in port-1 is read-only.rw
Enumeration
.1.3.6.1.4.1.135.22.1.4.1.5
sysMainProcessorFirmwareRevFirmware revision of the management CPU.ro
DisplayString
.1.3.6.1.4.1.135.22.1.5
sysPortCardFirmwareRevFirmware revision of the Ethernet (DATA) card.ro
DisplayString
.1.3.6.1.4.1.135.22.1.6
config
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.2
configDs1TableDS1 configuration table.
SEQUENCE OF ConfigDs1Entry
.1.3.6.1.4.1.135.22.2.1
configDs1EntryEach entry contains the configuration attributes for a DS1 port.
ConfigDs1Entry
.1.3.6.1.4.1.135.22.2.1.1
configDs1PortDS1 port number.ro
INTEGER
.1.3.6.1.4.1.135.22.2.1.1.1
configDs1AdminStatusDS1 administrative status.rw
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.2
configDs1OperStatusDS1 operational status.ro
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.3
configDs1LBOLBO. This object is not accessible if the managed node is the E1 version of LX10.rw
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.4
configDs1EncodingEncoding. This object is not accessible if the managed node is the E1 version of LX10.rw
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.5
configDs1FramingFraming format. This object is not accessible if the managed node is the E1 version of LX10.rw
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.6
configDs1XmtAisEnable/disable transmit AIS.rw
Enumeration
.1.3.6.1.4.1.135.22.2.1.1.7
configDs1TimingDS1 clock Source.rw
Enumeration
.1.3.6.1.4.1.135.22.2.2
configAfa
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.2.3
configAfaActivationRateAFA activation rate is used by the managed node to decide when it will disable the operational status of a T1 interface if the interface's BER rate is above the selected activation rate for a period specified by configAfaActivationTime (see below).rw
Enumeration
.1.3.6.1.4.1.135.22.2.3.1
configAfaActivationTimeSee above description. Unit - minuterw
INTEGER
.1.3.6.1.4.1.135.22.2.3.2
configAfaDeactivationRateAFA deactivation rate is used by the managed node to decide when it will enable the operational status of a T1 interface if the interface's BER rate is below the selected activation rate for a period specified by configAfaDectivationTime (see below).rw
Enumeration
.1.3.6.1.4.1.135.22.2.3.3
configAfaDeactivationTimeSee above description. Unit - minuterw
INTEGER
.1.3.6.1.4.1.135.22.2.3.4
configAfaStatusEnable/disable AFA function.rw
Enumeration
.1.3.6.1.4.1.135.22.2.3.5
configAfaFarEndLpbkDetectThis object controls whether AFA will be activated when a near end LX-10 detects network loopback in the far end LX-10. If it's disabled, no AFA will be activated because of a far end network loopback.rw
Enumeration
.1.3.6.1.4.1.135.22.2.3.6
configPortCardTypeThere are 3 kinds of cards/port supported by the managed node: HSDP, Ethernet, or Token-Ring. Only one of them can be installed in the managed node. Hsdp is a high speed data port with v.35, rs-422, and HSSI interfaces.ro
Enumeration
.1.3.6.1.4.1.135.22.2.4
configHsdp
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.2.5
configHsdpModeInterface type used by HSDP.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.1
configHsdpCtsControlCTS line control in HSDP. If the value of an instance of this object is set, the CTS line will always be set. If the value of an instance of this object is no-bandwidth, the CTS line will go low when no bandwidth is available after a hold-off time. If the value of an instance of this object is frequency- change, the CTS line will go low for a hold-off time when there is a frequency change.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.2
configHsdpCtsStatusStatus of CTS line in HSDP.ro
Enumeration
.1.3.6.1.4.1.135.22.2.5.3
configHsdpTermTimingSourceTerminal timing source in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.4
configHsdpTermTimingStatus of terminal timing in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.5
configHsdpRecvTimingStatus of receive timing in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.6
configHsdpHoldoffSecondsHold-off time for CA lead. If the hold-off is set at 5 seconds, and if the CTS control is sensitive to no-bandwidth, the CTS line will go low after 5 seconds when no bandwidth is available. If the CTS control is sensitive to frequency-change, the CTS line will stay low for 5 seconds when there is a frequency change, and then back to high.rw
Enumeration
.1.3.6.1.4.1.135.22.2.5.7
configHdlc
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.2.6
configHdlcModeSelect the way in which HDLC port will be assigned. If mode is manual, the HDLC port is selectable by the NMS. If mode is auto, the 2 LX-10's in the 2 sides will match their HDLC ports automatically.rw
Enumeration
.1.3.6.1.4.1.135.22.2.6.1
configHdlcLocalPortAssign one of the DS1 ports as the HDLC port. If its value is 0, no port is asssigned as the HDLC port.rw
INTEGER
.1.3.6.1.4.1.135.22.2.6.2
configHdlcFarEndPortThe DS1 port currently being used as the HDLC port in the far end LX-10.ro
INTEGER
.1.3.6.1.4.1.135.22.2.6.3
configInverseMuxMaster/slave relationship of the 2 LX-10E's in the point to point connection.rw
Enumeration
.1.3.6.1.4.1.135.22.2.7
fault
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.3
faultDs1
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.3.1
faultDs1LoopbackTableDS1 loopback table for 7 DS1 ports.
SEQUENCE OF FaultDs1LoopbackEntry
.1.3.6.1.4.1.135.22.3.1.1
faultDs1LoopbackEntryEach entry in the table contains the loopback status of a DS1 port.
FaultDs1LoopbackEntry
.1.3.6.1.4.1.135.22.3.1.1.1
faultDs1LoopbackPortThe port number of one of the 7 DS1 portsro
INTEGER
.1.3.6.1.4.1.135.22.3.1.1.1.1
faultDs1LoopbackNetworkLoopbackDS1 loopback is used to control the loopback state of one of the 7 DS1 interfaces in the managed node.rw
Enumeration
.1.3.6.1.4.1.135.22.3.1.1.1.2
faultDs1RemoteLineLoopbackThis loopback status is controlled by the LA/LB leads in the remote node.ro
Enumeration
.1.3.6.1.4.1.135.22.3.1.2
faultDte
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.3.2
faultDteLaLeadThe state of the LA loopbak lead.ro
Enumeration
.1.3.6.1.4.1.135.22.3.2.1
faultDteLbLeadThe state of the LB loopbak lead.ro
Enumeration
.1.3.6.1.4.1.135.22.3.2.2
faultDteLaLbTranslationThe managed node uses the states of the LA and LB leads to decide what kind of loopback to perform if faultLaLbLoopbackEnable (see below) is ENABLED. The meaning of LA and LB leads is as follows: loopback LA-Lead LB-Lead none clear clear local-line set clear remote-line clear set dte set setro
Enumeration
.1.3.6.1.4.1.135.22.3.2.3
faultDteLaLbLoopbackEnableEnable/disable the managed node to use the LA and LB lead states to perform loopbaks.rw
Enumeration
.1.3.6.1.4.1.135.22.3.2.4
faultDteCustomerLoopbackEnable/disable the customer equipment (DTE) to perform loopback toward the managed node.rw
Enumeration
.1.3.6.1.4.1.135.22.3.2.5
faultDteDteLoopbackEnable/disable the managed node to perform loopback toward the customer equipment (DTE).rw
Enumeration
.1.3.6.1.4.1.135.22.3.2.6
faultClearCurrentAlarmsA set request clears all entries in the current alarm table. A get/get-next request returns 0.rw
INTEGER
.1.3.6.1.4.1.135.22.3.3
faultClearHistoryAlarmsA set request clears all entries in the history alarm table. A get/get-next request returns 0.rw
INTEGER
.1.3.6.1.4.1.135.22.3.4
faultCurrentAlarmTableCurrent alarm table.
SEQUENCE OF FaultCurrentAlarmEntry
.1.3.6.1.4.1.135.22.3.5
faultCurrentAlarmEntryEach entry in the table contains the information of a currently active alarm.
FaultCurrentAlarmEntry
.1.3.6.1.4.1.135.22.3.5.1
faultCurrentAlarmTagThe tag of the alarm in the current alarm table.ro
INTEGER
.1.3.6.1.4.1.135.22.3.5.1.1
faultCurrentAlarmAlarmTypeThe alarm type of the alarm.ro
Enumeration
.1.3.6.1.4.1.135.22.3.5.1.2
faultCurrentAlarmSeverityThe severity of the alarm.ro
Enumeration
.1.3.6.1.4.1.135.22.3.5.1.3
faultCurrentAlarmCardTypeThe type of the card which caused the alarm.ro
Enumeration
.1.3.6.1.4.1.135.22.3.5.1.4
faultCurrentAlarmPortNumberThe port number of the card which caused the alarm. Its value is between 1 and 7 for DS1 ports and 0 for others.ro
INTEGER
.1.3.6.1.4.1.135.22.3.5.1.5
faultCurrentAlarmSetTimeThe time when the alarm was set.ro
TimeAndDate
.1.3.6.1.4.1.135.22.3.5.1.6
faultCurrentAlarmDescriptionA readable string which describes the alarm. Its format is as follows: <Level> <Card> <Port> <Alarm Type> <Time Occured> 'Level' is the alarm severity. Its value can be 'Info', 'Major', or 'Minor'. 'Card' refers to where the alarm was generated. Its value can be 'HSDP', 'ENET', 'TRING', or 'DS1'. 'Port' refers to which port generated the alarm. Its value can be 1 to 7 for DS1 and 'empty' if no port number can be used for an alarm. 'Alarm Type' is an ASCII string of the alarm type. 'Time Occured' is the time when the alarm was generated.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.135.22.3.5.1.8
faultHistoryAlarmTableHistory/Information alarm table.
SEQUENCE OF FaultHistoryAlarmEntry
.1.3.6.1.4.1.135.22.3.6
faultHistoryAlarmEntryEach entry in the history alarm table contains either a cleared alarm or an information alarm.
FaultHistoryAlarmEntry
.1.3.6.1.4.1.135.22.3.6.1
faultHistoryAlarmTagThe tag of the alarm in the history alarm table.ro
INTEGER
.1.3.6.1.4.1.135.22.3.6.1.1
faultHistoryAlarmAlarmTypeThe alarm type of the alarm.ro
Enumeration
.1.3.6.1.4.1.135.22.3.6.1.2
faultHistoryAlarmSeverityThe severity of the alarm. Its value can be either major or minor for DS1 ports and info for others.ro
Enumeration
.1.3.6.1.4.1.135.22.3.6.1.3
faultHistoryAlarmCardTypeThe type of the card which caused the alarm.ro
Enumeration
.1.3.6.1.4.1.135.22.3.6.1.4
faultHistoryAlarmPortNumberThe port number of the card which caused the alarm. Its value is between 1 and 7 for DS1 ports and 0 for others.ro
INTEGER
.1.3.6.1.4.1.135.22.3.6.1.5
faultHistoryAlarmSetTimeThe time when the alarm was set.ro
TimeAndDate
.1.3.6.1.4.1.135.22.3.6.1.6
faultHistoryAlarmClearTimeThe time when the alarm was cleared.ro
TimeAndDate
.1.3.6.1.4.1.135.22.3.6.1.7
faultHistoryAlarmDescriptionA readable string which describes the alarm. Its format is as follows: <Level> <Card> <Port> <Alarm Type> <Time Occured> <Time Cleared> 'Level' is the alarm severity. Its value can be 'Info', 'Major', or 'Minor'. 'Card' refers to where the alarm was generated. Its value can be 'HSDP', 'ENET', 'TRING', or 'DS1'. 'Port' refers to which port generated the alarm. Its value can be 1 to 7 for DS1 and 'empty' if no port number can be used for an alarm. 'Alarm Type' is an ASCII string of the alarm type. 'Time Occured' is the time when the alarm was generated. 'Time Cleared' is the time when the alarm was cleared.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.135.22.3.6.1.8
perf
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.4
perfClearDs1PerformanceA set request clears all DS1 performance monitoring data. A get/get-next request returns 0.rw
INTEGER
.1.3.6.1.4.1.135.22.4.1
perfClearEnetPortCardStatsA set request clears all ethernet port card statistics. A get/get-next request returns 0.rw
INTEGER
.1.3.6.1.4.1.135.22.4.2
enetPortCardStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.4.3
enetPortCardStatsFramesReceivedA count of frames received by the ethernet port card.ro
Counter
.1.3.6.1.4.1.135.22.4.3.1
enetPortCardStatsBytesReceivedA count of bytes received by the ethernet port card.ro
Counter
.1.3.6.1.4.1.135.22.4.3.2
enetPortCardStatsFramesTransmittedA count of frames transmitted on the ethernet port card.ro
Counter
.1.3.6.1.4.1.135.22.4.3.3
enetPortCardStatsBytesTransmittedA count of bytes transmitted on the ethernet port card.ro
Counter
.1.3.6.1.4.1.135.22.4.3.4
enetPortCardStatsAlignmentErrorsA count of frames received that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.ro
Counter
.1.3.6.1.4.1.135.22.4.3.5
enetPortCardStatsFCSErrorsA count of frames received that are an integral number of octets in length but do not pass the FCS check. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.ro
Counter
.1.3.6.1.4.1.135.22.4.3.6
enetPortCardStatsSingleCollisionFramesA count of successfully transmitted frames for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the enetPortCardStatsMultipleCollisionFrames object.ro
Counter
.1.3.6.1.4.1.135.22.4.3.7
enetPortCardStatsMultipleCollisionFramesA count of successfully transmitted frames for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the enetPortCardStatsSingleCollisionFrames object.ro
Counter
.1.3.6.1.4.1.135.22.4.3.8
enetPortCardStatsDeferredTransmissionsA count of frames for which the first transmission attempt is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.ro
Counter
.1.3.6.1.4.1.135.22.4.3.9
enetPortCardStatsLateCollisionsThe number of times that a collision is detected on later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.ro
Counter
.1.3.6.1.4.1.135.22.4.3.10
enetPortCardStatsExcessiveCollisionsA count of frames for which transmission fails due to excessive collisions.ro
Counter
.1.3.6.1.4.1.135.22.4.3.11
enetPortCardStatsInternalMacTransmitErrorsA count of frames for which transmission fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the enetPortCardStatsLateCollisions object, the enetPortCardStatsExcessiveCollisions object, or the enetPortCardStatsCarrierSenseErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of transmission errors that are not otherwise counted.ro
Counter
.1.3.6.1.4.1.135.22.4.3.12
enetPortCardStatsCarrierSenseErrorsThe number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.ro
Counter
.1.3.6.1.4.1.135.22.4.3.13
enetPortCardStatsFrameTooLongsA count of frames received that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.ro
Counter
.1.3.6.1.4.1.135.22.4.3.14
perfClearNxT1PortStatsA set request clears all nxt1 port statistics. A get/get-next request returns 0.rw
INTEGER
.1.3.6.1.4.1.135.22.4.4
nxt1PortStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.135.22.4.5
nxt1PortStatsFramesReceivedA count of frames received by the NxT1 port.ro
Counter
.1.3.6.1.4.1.135.22.4.5.1
nxt1PortStatsBytesReceivedA count of bytes received by the NxT1 port.ro
Counter
.1.3.6.1.4.1.135.22.4.5.2
nxt1PortStatsFramesTransmittedA count of frames transmitted on the NxT1 port.ro
Counter
.1.3.6.1.4.1.135.22.4.5.3
nxt1PortStatsBytesTransmittedA count of bytes transmitted on the NxT1 port.ro
Counter
.1.3.6.1.4.1.135.22.4.5.4
nxt1PortStatsCrcErrorsA count of frames received by the NxT1 port that do not pass the CRC check.ro
Counter
.1.3.6.1.4.1.135.22.4.5.5
LX-10-MIB - SNMP MIB Reference | MIBs Explorer