OID reference

atmPolicyConstraintMIB

1.3.6.1.4.1.353.5.9.5.1

Description

The MIB module for Policy Contraints of ATM Forum Policy Routing. The Policy Constraint MIB is organized as two main tables: the policyConstraintTable and the policyTable. The policyConstraintTable provides the entries that can be referenced by other MIB objects to utilize a policy constraint. Each entry in the table …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.353.5.9.5 (atmfPolicyConstraint)
Node code
1
Node name
atmPolicyConstraintMIB
Numeric OID
1.3.6.1.4.1.353.5.9.5.1
URN notation
urn:oid:1.3.6.1.4.1.353.5.9.5.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 353 5 9 5 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagement(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmForum(353) atmForumNetworkManagment(5) atmfSignalling(9) atmfPolicyConstraint(5) atmPolicyConstraintMIB(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/353/5/9/5/1
  • /ISO/Identified-Organization/6/1/4/1/353/5/9/5/1
  • /ISO/3/6/1/4/1/353/5/9/5/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/enterprises/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/ldap-enterprise/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagement/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • /iso/org/dod/internet/private/vendor-objects/atmForum/atmForumNetworkManagment/atmfSignalling/atmfPolicyConstraint/atmPolicyConstraintMIB
  • Additional combinations skipped.

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

atmPolicyConstraintMIB MODULE-IDENTITY
    LAST-UPDATED     "200307080000Z"
    ORGANIZATION     "The ATM Forum."
    CONTACT-INFO
        "The ATM Forum
        2570 West El Camino Real, Suite 304
        Mountain View, CA 94040-1313 USA
        Phone: +1 650-949-670
        Fax:    +1 415-949-6705
        info@atmforum.com"
    DESCRIPTION
        "The MIB module for Policy Contraints of ATM Forum
        Policy Routing.

           The Policy Constraint MIB is organized as two main tables:
           the policyConstraintTable and the policyTable.

           The policyConstraintTable provides the entries that
           can be referenced by other MIB objects to utilize
           a policy constraint. Each entry in the table contains a set of
           up to six pointers into the policyTable. The policyTable
           specifies the operators of a policy. Associated with the
           policyTable are the policyNeNscTable and the policyRpNscTable.




           These two tables contain the lists of NSCs on which the
           policy operators operate.

           To create a policy, the management station should first
           create an associated instance of the row status in a
           policyEntry, using a value of policyIndex that
           is not currently in use. The object policyNextPolicyIndex
           can be read to get an available policyIndex.
           It must also, either in the same or in successive PDUs,
           create the associated instances of the Ne-NSC and
           Rp-NSC lists for the policyIndex. It should also
           specify the values for the policy operators.

           Once the appropriate instance of all the configuration
           objects have been created for the policyEntry,
           policyRpNscEntry, and the policyNeNscEntry (as appropriate),
           the row status of the policyEntry should be set to active
           to activate the policy.

         The policy constraint table can include pointers to
         policies that are notReady but they must exist.
         If such a policy constraint is used for a call establishment
         request, then that policy is not used in the signaled
         policy constraint.
         "
     REVISION        "200307080000Z"
     DESCRIPTION
         "Initial version of the MIB for Policy Constraints."
     ::= { atmfPolicyConstraint 1 }

Meaning

Descriptions

1 unique

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

The MIB module for Policy Contraints of ATM Forum Policy Routing. The Policy Constraint MIB is organized as two main tables: the policyConstraintTable and the policyTable. The policyConstraintTable provides the entries that can be referenced by other MIB objects to utilize a policy constraint. Each entry in the table contains a set of up to six pointers into the policyTable. The policyTable specifies the operators of a policy. Associated with the policyTable are the policyNeNscTable and the policyRpNscTable. These two tables contain the lists of NSCs on which the policy operators operate. To create a policy, the management station should first create an associated instance of the row status in a policyEntry, using a value of policyIndex that is not currently in use. The object policyNextPolicyIndex can be read to get an available policyIndex. It must also, either in the same or in successive PDUs, create the associated instances of the Ne-NSC and Rp-NSC lists for the policyIndex. It should also specify the values for the policy operators. Once the appropriate instance of all the configuration objects have been created for the policyEntry, policyRpNscEntry, and the policyNeNscEntry (as appropriate), the row status of the policyEntry should be set to active to activate the policy. The policy constraint table can include pointers to policies that are notReady but they must exist. If such a policy constraint is used for a call establishment request, then that policy is not used in the signaled policy constraint.

Sources for this description

ATM Forum official specifications

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 1ATM Forum official specifications1 record · 1 source

Description 1

atmPolicyConstraintMIB · unspecifiedATM Forum official specifications1 source

Status in source: unspecified.

Names: atmPolicyConstraintMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "atmPolicyConstraintMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303330373038303030305a22"
    ],
    "ORGANIZATION",
    "\"The ATM Forum.\"",
    "CONTACT-INFO",
    "\"The ATM Forum 2570 West El Camino Real, Suite 304 Mountain View, CA 94040-1313 USA Phone: +1 650-949-670 Fax: +1 415-949-6705 info@atmforum.com\"",
    "DESCRIPTION",
    "\"The MIB module for Policy Contraints of ATM Forum Policy Routing. The Policy Constraint MIB is organized as two main tables: the policyConstraintTable and the policyTable. The policyConstraintTable provides the entries that can be referenced by other MIB objects to utilize a policy constraint. Each entry in the table contains a set of up to six pointers into the policyTable. The policyTable specifies the operators of a policy. Associated with the policyTable are the policyNeNscTable and the policyRpNscTable. These two tables contain the lists of NSCs on which the policy operators operate. To create a policy, the management station should first create an associated instance of the row status in a policyEntry, using a value of policyIndex that is not currently in use. The object policyNextPolicyIndex can be read to get an available policyIndex. It must also, either in the same or in successive PDUs, create the associated instances of the Ne-NSC and Rp-NSC lists for the policyIndex. It should also specify the values for the policy operators. Once the appropriate instance of all the configuration objects have been created for the policyEntry, policyRpNscEntry, and the policyNeNscEntry (as appropriate), the row status of the policyEntry should be set to active to activate the policy. The policy constraint table can include pointers to policies that are notReady but they must exist. If such a policy constraint is used for a call establishment request, then that policy is not used in the signaled policy constraint. \"",
    "REVISION",
    [
      "literal",
      "223230303330373038303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of the MIB for Policy Constraints.\"",
    "::=",
    "{",
    "atmfPolicyConstraint",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200307080000Z"
    ],
    [
      "ORGANIZATION",
      "The ATM Forum."
    ],
    [
      "CONTACT-INFO",
      "The ATM Forum 2570 West El Camino Real, Suite 304 Mountain View, CA 94040-1313 USA Phone: +1 650-949-670 Fax: +1 415-949-6705 info@atmforum.com"
    ],
    [
      "DESCRIPTION",
      "The MIB module for Policy Contraints of ATM Forum Policy Routing. The Policy Constraint MIB is organized as two main tables: the policyConstraintTable and the policyTable. The policyConstraintTable provides the entries that can be referenced by other MIB objects to utilize a policy constraint. Each entry in the table contains a set of up to six pointers into the policyTable. The policyTable specifies the operators of a policy. Associated with the policyTable are the policyNeNscTable and the policyRpNscTable. These two tables contain the lists of NSCs on which the policy operators operate. To create a policy, the management station should first create an associated instance of the row status in a policyEntry, using a value of policyIndex that is not currently in use. The object policyNextPolicyIndex can be read to get an available policyIndex. It must also, either in the same or in successive PDUs, create the associated instances of the Ne-NSC and Rp-NSC lists for the policyIndex. It should also specify the values for the policy operators. Once the appropriate instance of all the configuration objects have been created for the policyEntry, policyRpNscEntry, and the policyNeNscEntry (as appropriate), the row status of the policyEntry should be set to active to activate the policy. The policy constraint table can include pointers to policies that are notReady but they must exist. If such a policy constraint is used for a call establishment request, then that policy is not used in the signaled policy constraint."
    ],
    [
      "Revisions",
      [
        [
          "200307080000Z",
          [
            "DESCRIPTION",
            "Initial version of the MIB for Policy Constraints."
          ]
        ]
      ]
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.353)

McCloghrie Keith

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.353.5.9.5.1.1 policyConstraintMIBObjects446