Reference record for OID 1.3.6.1.2.1.12345.2.11.1.4


parent
1.3.6.1.2.1.12345.2.11.1 (diffServSchedulerEntry)
node code
4
node name
diffServSchedulerNext
dot oid
1.3.6.1.2.1.12345.2.11.1.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) diffServMib(12345) diffServMIBConformance(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) diffServMib(12345) diffServTables(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) diffServMib(12345) diffServMIBConformance(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) diffServMib(12345) diffServTables(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) diffServMib(12345) diffServMIBConformance(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) diffServMib(12345) diffServTables(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) diffServMib(12345) diffServMIBConformance(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) diffServMib(12345) diffServTables(2) diffServSchedulerTable(11) diffServSchedulerEntry(1) diffServSchedulerNext(4)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/diffServMib/diffServMIBConformance/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • /iso/identified-organization/dod/internet/mgmt/mib-2/diffServMib/diffServTables/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • ...skipped...
  • /iso/org/dod/internet/mgmt/mib-2/diffServMib/diffServMIBConformance/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • /iso/org/dod/internet/mgmt/mib-2/diffServMib/diffServTables/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • /iso/org/dod/internet/mgmt/mib/diffServMib/diffServMIBConformance/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • /iso/org/dod/internet/mgmt/mib/diffServMib/diffServTables/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/diffServMib/diffServMIBConformance/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/diffServMib/diffServTables/diffServSchedulerTable/diffServSchedulerEntry/diffServSchedulerNext
  • Description by circitor

    Selects the next data path component, which can be another
    scheduler or other TC elements. One usage of multiple scheduler
    elements in series is for Class Base Queueing (CBQ).

    The value zeroDotZero in this variable indicates no further
    DiffServ treatment is performed on this flow by the current
    interface for this interface direction. For example, for an
    inbound interface the value zeroDotZero indicates that the packet
    flow has now completed inbound DiffServ treatment and should be
    forwarded on to the appropriate outbound interface. If the row
    pointed to does not exist, the scheduler element is considered
    inactive.

    Parsed from file DIFF-SERV-MIB.mib
    Module: DIFF-SERV-MIB

    Information by circitor

    diffServSchedulerNext OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Selects the next data path component, which can be another scheduler or other TC elements. One usage of multiple scheduler elements in series is for Class Base Queueing (CBQ). The value zeroDotZero in this variable indicates no further DiffServ treatment is performed on this flow by the current interface for this interface direction. For example, for an inbound interface the value zeroDotZero indicates that the packet flow has now completed inbound DiffServ treatment and should be forwarded on to the appropriate outbound interface. If the row pointed to does not exist, the scheduler element is considered inactive." DEFVAL { zeroDotZero } ::= { diffServSchedulerEntry 4 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (4)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.12345.2.11.1.1 diffServSchedulerIfDirection 0 0 Specifies the direction for which this scheduler entry applies
    on this interface.
    1.3.6.1.2.1.12345.2.11.1.2 diffServSchedulerId 0 0 This identifies the scheduler entry. Managers should obtain new
    values for row creation in this table by reading
    diffServSchedule…
    1.3.6.1.2.1.12345.2.11.1.3 diffServSchedulerMethod 0 0 The scheduling algorithm used by this Scheduler.

    A value of priorityq(2) is used to indicate strict priority
    queueing: only the d…
    1.3.6.1.2.1.12345.2.11.1.5 diffServSchedulerStatus 0 0 The RowStatus variable controls the activation, deactivation, or
    deletion of a queue. Any writable variable may be modified
    whet…