Reference record for OID 1.3.6.1.4.1.278.117.1.15.3.1.1.5

Parent
1.3.6.1.4.1.278.117.1.15.3.1.1 (rmonHistoryControlEntry)
Node code
5
Node name
rmonHistoryControlInterval
Numeric OID
1.3.6.1.4.1.278.117.1.15.3.1.1.5
URN notation
urn:oid:1.3.6.1.4.1.278.117.1.15.3.1.1.5
ASN.1 notation

{1 3 6 1 4 1 278 117 1 15 3 1 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplms(117) msMibs(1) sysRMON(15) rmonHistory(3) rmonHistoryControlTable(1) rmonHistoryControlEntry(1) rmonHistoryControlInterval(5)}
OID-IRI notation
  • /1/3/6/1/4/1/278/117/1/15/3/1/1/5
  • /ISO/Identified-Organization/6/1/4/1/278/117/1/15/3/1/1/5
  • /ISO/3/6/1/4/1/278/117/1/15/3/1/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/enterprise/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/enterprises/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/enterprises/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/enterprise/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/enterprise/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/enterprises/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/enterprises/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/ldap-enterprise/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/ldap-enterprise/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/vendor-objects/278/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • /iso/org/dod/internet/private/vendor-objects/hitachi-cable/aplms/msMibs/sysRMON/rmonHistory/rmonHistoryControlTable/rmonHistoryControlEntry/rmonHistoryControlInterval
  • Additional combinations skipped.

Descriptions

rmonHistoryControlInterval — APRESIA official small-business switch MIB packages

The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this rmonHistoryControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the rmonHistoryControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the rmonEtherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated rmonHistoryControlStatus object is equal to valid(1).

Source records

rmonHistoryControlInterval

Status in source: current.

Names: rmonHistoryControlInterval

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rmonHistoryControlInterval",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "3600",
    ")",
    "UNITS",
    [
      "literal",
      "225365636f6e647322"
    ],
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this rmonHistoryControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the rmonHistoryControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the rmonEtherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated rmonHistoryControlStatus object is equal to valid(1).\"",
    "DEFVAL",
    "{",
    "1800",
    "}",
    "::=",
    "{",
    "rmonHistoryControlEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            3600
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "Seconds"
    ],
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this rmonHistoryControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the rmonHistoryControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the rmonEtherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated rmonHistoryControlStatus object is equal to valid(1)."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      1800
    ]
  ]
}
  • APRESIA official small-business switch MIB packages · Publisher's source file: Source package: ApresiaLightMS-mibs_102.zip

    Module: ApresiaLightMS-Series

    Published definition
    rmonHistoryControlInterval OBJECT-TYPE
    		SYNTAX     Integer32 (1..3600)
    		UNITS      "Seconds"
    		MAX-ACCESS read-create
    		STATUS     current
    		DESCRIPTION
    			"The interval in seconds over which the data is
    			sampled for each bucket in the part of the
    			media-specific table associated with this
    			rmonHistoryControlEntry.  This interval can
    			be set to any number of seconds between 1 and
    			3600 (1 hour).
    
    			Because the counters in a bucket may overflow at their
    
    			maximum value with no indication, a prudent manager will
    			take into account the possibility of overflow in any of
    			the associated counters.  It is important to consider the
    			minimum time in which any counter could overflow on a
    			particular media type and set the rmonHistoryControlInterval
    			object to a value less than this interval.  This is
    			typically most important for the 'octets' counter in any
    			media-specific table.  For example, on an Ethernet
    			network, the rmonEtherHistoryOctets counter could overflow
    			in about one hour at the Ethernet's maximum
    			utilization.
    
    			This object may not be modified if the associated
    			rmonHistoryControlStatus object is equal to valid(1)."
    		DEFVAL { 1800 }
    		::= { rmonHistoryControlEntry 5 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'DisplayString', 'TEXTUAL-CONVENTION', 'MacAddress', 'TimeStamp', 'DateAndTime', 'TimeInterval'], 'BRIDGE-MIB': ['dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Gauge32', 'enterprises', 'IpAddress', 'Integer32', 'Unsigned32', 'TimeTicks', 'Counter32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetScopeType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpSecurityLevel']}
    · Download APRESIA official MIB — ApresiaLightMS-mibs_102.zip / ApresiaLightMS-mibs.mib

    Related source files and packages:


    Source location: ApresiaLightMS-Series::rmonHistoryControlInterval.
    Source version and references

    Downloaded: 2026-11-03T01:07:39.696013+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.278)

Asai Takahiro

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.278.117.1.15.3.1.1.1 rmonHistoryControlIndex00
1.3.6.1.4.1.278.117.1.15.3.1.1.2 rmonHistoryControlDataSource00
1.3.6.1.4.1.278.117.1.15.3.1.1.3 rmonHistoryControlBucketsRequested00
1.3.6.1.4.1.278.117.1.15.3.1.1.4 rmonHistoryControlBucketsGranted00
1.3.6.1.4.1.278.117.1.15.3.1.1.6 rmonHistoryControlOwner00
1.3.6.1.4.1.278.117.1.15.3.1.1.7 rmonHistoryControlStatus00