A row in the CODIMA Express History Long Term
Segment Database Ethernet Objects table. Based on 15
minute intervals Segment statistics are gathered
on the network segment to which the Express is attached.
The statistics in this databases are calculated by adding
Port 1 statistics and Port 2 statistics together.
Port 2 however will only be active if you are using the
Express as a dual port analyzer, i.e., monitoring full duplex.
The Ethernet object implements statistics that are specific
to Ethernet Networks, e.g., Collisions, Jabbers, Runts,
CRC errors etc.
The number of rows in this table is dependant on the value
chosen for the Long Term dcTimeSlots object.
Parsed from file CODIMA-EXPRESS-MIB.my.txt
Company: None
Module: CODIMA-EXPRESS-MIB
A row in the CODIMA Express History Long Term
Segment Database Ethernet Objects table. Based on 15
minute intervals Segment statistics are gathered
on the network segment to which the Express is attached.
The statistics in this databases are calculated by adding
Port 1 statistics and Port 2 statistics together.
Port 2 however will only be active if you are using the
Express as a dual port analyzer, i.e., monitoring full duplex.
The Ethernet object implements statistics that are specific
to Ethernet Networks, e.g., Collisions, Jabbers, Runts,
CRC errors etc.
The number of rows in this table is dependant on the value
chosen for the Long Term dcTimeSlots object.
Parsed from file CODIMA-EXPRESS-MIB.mib
Module: CODIMA-EXPRESS-MIB
Vendor: CODIMA Technologies Ltd
Module: CODIMA-EXPRESS-MIB
[Automatically extracted from oidview.com]
slEthernetEntry OBJECT-TYPE SYNTAX SlEthernetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the CODIMA Express History Long Term Segment Database Ethernet Objects table. Based on 15 minute intervals Segment statistics are gathered on the network segment to which the Express is attached. The statistics in this databases are calculated by adding Port 1 statistics and Port 2 statistics together. Port 2 however will only be active if you are using the Express as a dual port analyzer, i.e., monitoring full duplex. The Ethernet object implements statistics that are specific to Ethernet Networks, e.g., Collisions, Jabbers, Runts, CRC errors etc. The number of rows in this table is dependant on the value chosen for the Long Term dcTimeSlots object." INDEX { sleTimeStampIndex } ::= { slEthernetTable 1 }
slEthernetEntry OBJECT-TYPE SYNTAX SlEthernetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the CODIMA Express History Long Term Segment Database Ethernet Objects table. Based on 15 minute intervals Segment statistics are gathered on the network segment to which the Express is attached. The statistics in this databases are calculated by adding Port 1 statistics and Port 2 statistics together. Port 2 however will only be active if you are using the Express as a dual port analyzer, i.e., monitoring full duplex. The Ethernet object implements statistics that are specific to Ethernet Networks, e.g., Collisions, Jabbers, Runts, CRC errors etc. The number of rows in this table is dependant on the value chosen for the Long Term dcTimeSlots object." INDEX { sleTimeStampIndex } ::= { slEthernetTable 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.1 | sleTimeStampIndex | 0 | 0 | Identifies the History Time-stamp for this row. This is UTC time, measured in seconds from Midnight January 1st 1970. |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.2 | sleTimeStamp | 0 | 0 | A textual representation of the associated TimeStampIndex object which shows the History time-stamp for this row. The value is in … |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.3 | sleRunts | 0 | 0 | Number of Runts. Runts are frames which are smaller than the Ethernet minimum frames size of 64 bytes. A value of 4294967294 ind… |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.4 | sleJabbers | 0 | 0 | Number of Jabber Frames. Jabbers are frames which exceed the Ethernet maximum packets size of 1518, they are most often caused b… |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.5 | sleCrc | 0 | 0 | Number of CRC/Alignment Errors. CRC errors are frames which have been damaged. The Cyclic Redundancy Checksum used to confirm th… |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.6 | sleCollisions | 0 | 0 | Number of Collisions. Collisions are the result of two workstations trying to use shared a transmission medium (cable) simultan… |
| 1.3.6.1.4.1.226.3.2.1.1.2.1.4.1.7 | sleLateCollisions | 0 | 0 | Number of Late Collisions. The term late collisions applies to collisions which occur late enough for the first 12 bytes of the f… |