Reference record for OID 1.3.6.1.4.1.226.3.2.1.1.2.2.4.1



parent
1.3.6.1.4.1.226.3.2.1.1.2.2.4 (ssEthernetTable)
node code
1
node name
ssEthernetEntry
dot oid
1.3.6.1.4.1.226.3.2.1.1.2.2.4.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) codima(226) codimaProducts(3) codimaExpressMIB(2) codimaExpressObjects(1) expHistoryDatabases(1) dbSegment(2) segShortTerm(2) ssEthernetTable(4) ssEthernetEntry(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • /iso/identified-organization/dod/internet/private/enterprises/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • /iso/org/dod/internet/private/enterprise/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • /iso/org/dod/internet/private/enterprises/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprise/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/codima/codimaProducts/codimaExpressMIB/codimaExpressObjects/expHistoryDatabases/dbSegment/segShortTerm/ssEthernetTable/ssEthernetEntry
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/226/3/2/1/1/2/2/4/1

    Description by mibdepot

    A row in the CODIMA Express History Short Term
    Segment Database Ethernet Objects table. Based on 15
    second 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 Short Term dcTimeSlots object.

    Parsed from file CODIMA-EXPRESS-MIB.my.txt
    Company: None
    Module: CODIMA-EXPRESS-MIB

    Description by circitor

    A row in the CODIMA Express History Short Term
    Segment Database Ethernet Objects table. Based on 15
    second 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 Short Term dcTimeSlots object.

    Parsed from file CODIMA-EXPRESS-MIB.mib
    Module: CODIMA-EXPRESS-MIB

    Information by oid_info

    Vendor: CODIMA Technologies Ltd
    Module: CODIMA-EXPRESS-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    ssEthernetEntry OBJECT-TYPE SYNTAX SsEthernetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the CODIMA Express History Short Term Segment Database Ethernet Objects table. Based on 15 second 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 Short Term dcTimeSlots object." INDEX { sseTimeStampIndex } ::= { ssEthernetTable 1 }

    Information by circitor

    ssEthernetEntry OBJECT-TYPE SYNTAX SsEthernetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row in the CODIMA Express History Short Term Segment Database Ethernet Objects table. Based on 15 second 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 Short Term dcTimeSlots object." INDEX { sseTimeStampIndex } ::= { ssEthernetTable 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.226)

    Barratt Dave

    Children (7)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.226.3.2.1.1.2.2.4.1.1 sseTimeStampIndex 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.2.4.1.2 sseTimeStamp 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.2.4.1.3 sseRunts 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.2.4.1.4 sseJabbers 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.2.4.1.5 sseCrc 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.2.4.1.6 sseCollisions 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.2.4.1.7 sseLateCollisions 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…