OID reference

setPtNtpWeight

1.3.6.1.4.1.601.3.1.1.3.22.1.1.9

Description

Set the load distribution between portA/B in percent. For example, 70 means port-A get 70% of total bandwidth, port-B gets remaining 30%. If port-A reaches 70% of total bandwidth but port-B has no traffic, the 30% of bandwidth will be wasted, port-A cannot use it. To allow either port to use all the bandwidth, portAWe…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.601.3.1.1.3.22.1.1 (setPtNtpEntry)
Node code
9
Node name
setPtNtpWeight
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.601.3.1.1.3.22.1.1.9
URN notation
urn:oid:1.3.6.1.4.1.601.3.1.1.3.22.1.1.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 601 3 1 1 3 22 1 1 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) datum(601) austron(3) products(1) ssu2000(1) msetup(3) setupPtNtp(22) setPtNtpTable(1) setPtNtpEntry(1) setPtNtpWeight(9)}
OID-IRI notation
  • /1/3/6/1/4/1/601/3/1/1/3/22/1/1/9
  • /ISO/Identified-Organization/6/1/4/1/601/3/1/1/3/22/1/1/9
  • /ISO/3/6/1/4/1/601/3/1/1/3/22/1/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/enterprise/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/enterprises/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/enterprises/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/vendor-objects/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/identified-organization/dod/internet/private/vendor-objects/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/enterprise/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/enterprise/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/enterprises/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/enterprises/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/ldap-enterprise/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/ldap-enterprise/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/vendor-objects/601/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • /iso/org/dod/internet/private/vendor-objects/datum/austron/products/ssu2000/msetup/setupPtNtp/setPtNtpTable/setPtNtpEntry/setPtNtpWeight
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Allowed ranges
-1–100

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In SSU2000-MIB, the row index consists of these components in order:

  1. setPtNtpChassis (INTEGER): one numeric subidentifier for the non-negative value.
  2. setPtNtpSlot (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.601.3.1.1.3.22.1.1.9.<setPtNtpChassis>.<setPtNtpSlot>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.601.3.1.1.3.22.1.1.9

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

setPtNtpWeight OBJECT-TYPE
        SYNTAX  INTEGER (-1..100)
        MAX-ACCESS  read-write
        STATUS  current
        DESCRIPTION
        "Set the load distribution between portA/B in percent.
        For example, 70 means port-A get 70% of total bandwidth, 
        port-B gets remaining 30%. If port-A reaches 70% of total 
        bandwidth but port-B has no traffic, the 30% of bandwidth 
        will be wasted, port-A cannot use it. To allow either port 
        to use all the bandwidth, portAWeight  can be set to -1, 
        indicating no limit between port-A and port-B (either port-A 
        or port-B can get all the bandwidth, based on first come 
        first serve). Thus the range of this parameter -1 to 100. 
        For bonding mode, this parameter must be forced to -1, 
        so the active port can use 100% of the bandwidth. 
        For non-bonding mode, user can set any value between -1 to 100.
        "
    ::= { setPtNtpEntry 9 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Set the load distribution between portA/B in percent. For example, 70 means port-A get 70% of total bandwidth, port-B gets remaining 30%. If port-A reaches 70% of total bandwidth but port-B has no traffic, the 30% of bandwidth will be wasted, port-A cannot use it. To allow either port to use all the bandwidth, portAWeight can be set to -1, indicating no limit between port-A and port-B (either port-A or port-B can get all the bandwidth, based on first come first serve). Thus the range of this parameter -1 to 100. For bonding mode, this parameter must be forced to -1, so the active port can use 100% of the bandwidth. For non-bonding mode, user can set any value between -1 to 100.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

setPtNtpWeight · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: setPtNtpWeight

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "setPtNtpWeight",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "-",
    "1",
    ".",
    ".",
    "100",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Set the load distribution between portA/B in percent. For example, 70 means port-A get 70% of total bandwidth, port-B gets remaining 30%. If port-A reaches 70% of total bandwidth but port-B has no traffic, the 30% of bandwidth will be wasted, port-A cannot use it. To allow either port to use all the bandwidth, portAWeight can be set to -1, indicating no limit between port-A and port-B (either port-A or port-B can get all the bandwidth, based on first come first serve). Thus the range of this parameter -1 to 100. For bonding mode, this parameter must be forced to -1, so the active port can use 100% of the bandwidth. For non-bonding mode, user can set any value between -1 to 100. \"",
    "::=",
    "{",
    "setPtNtpEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            -1,
            100
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Set the load distribution between portA/B in percent. For example, 70 means port-A get 70% of total bandwidth, port-B gets remaining 30%. If port-A reaches 70% of total bandwidth but port-B has no traffic, the 30% of bandwidth will be wasted, port-A cannot use it. To allow either port to use all the bandwidth, portAWeight can be set to -1, indicating no limit between port-A and port-B (either port-A or port-B can get all the bandwidth, based on first come first serve). Thus the range of this parameter -1 to 100. For bonding mode, this parameter must be forced to -1, so the active port can use 100% of the bandwidth. For non-bonding mode, user can set any value between -1 to 100."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.601)

Fontes Joe

Siblings (15)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.601.3.1.1.3.22.1.1.1 setPtNtpChassis00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.2 setPtNtpSlot00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.3 setPtNtpCommit00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.4 setPtNtpProbe00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.5 setPtNtpBond00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.6 setPtNtpNTPd00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.7 setPtNtpTodsrcPrefer00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.8 setPtNtpTodsrcPriority00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.10 setPtNtpCompensation00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.11 setPtNtpPeerTimeout00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.12 setPtNtpPeerPrefer00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.13 setPtNtpBypass00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.14 setPtNtpModActive00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.15 setPtNtpPAActive00
1.3.6.1.4.1.601.3.1.1.3.22.1.1.16 setPtNtpPBActive00