OID reference

policyTable

1.3.6.1.4.1.353.5.9.5.1.1.3.2

Description

The table whose entries describe the policies configured. Each policy contains two possible policy operators: 'require' and 'must avoid'. The require policy operator can be applied with an Ne-NSC list, an Rp-NSC list or both. The must avoid policy operator can be applied with only an Ne-NSc list. In order to create a …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.353.5.9.5.1.1.3 (policyGroup)
Node code
2
Node name
policyTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.353.5.9.5.1.1.3.2
URN notation
urn:oid:1.3.6.1.4.1.353.5.9.5.1.1.3.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF PolicyEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

policyTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF PolicyEntry
    MAX-ACCESS not-accessible
    STATUS      current
    DESCRIPTION
        "The table whose entries describe the policies
        configured.

           Each policy contains two possible policy operators:
           'require' and 'must avoid'. The require policy




           operator can be applied with an Ne-NSC list, an Rp-NSC
           list or both. The must avoid policy operator can
           be applied with only an Ne-NSc list.

           In order to create a new policy, the policyRowStatus
           should be set to createAndWait. The status should
           not be set to active until the remaining objects
           of the entry have been specified.

           If an existing entry is to be modified, then the RowStatus
           should be set to notInService, the objects modified,
           and then the RowStatus set to active.

           If the RowStatus is set to indicate that the entry
           is to become active (CreateAndGo or Active), then the
           following rules are checked:
             1) At least one of requireNeNscOperator or
                requireRpNscOperator or mustAvoidNeNscOperator
                must be specified.
             2) If the requireNeNscOperator is specified,
                then at least one Ne-NSC value must
                exist in an active row of the policyNeNscTable for this
                policyIndex and an policyOperator of require.
             3) If the requireRpNscOperator is specified,
                then at least one Rp-NSC value must
                exist in an active row of the policyRpNscTable for this
                policyIndex.
             4) If the mustAvoidNeNscOperator is specified,
                then at least one Ne-NSC value must
                exist in an active row of the policyNeNscTable for this
                policyIndex and an policyOperator
                of mustAvoid.
           If a row is deleted from this table, then the corresponding
           rows of the policyNeNscTable and policyRpNscTable are also
           deleted. In addition, any entries in the policyConstraintTable
           that reference this policyIndex are removed. "

     ::= { policyGroup 2}

Meaning

Descriptions

1 unique

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

The table whose entries describe the policies configured. Each policy contains two possible policy operators: 'require' and 'must avoid'. The require policy operator can be applied with an Ne-NSC list, an Rp-NSC list or both. The must avoid policy operator can be applied with only an Ne-NSc list. In order to create a new policy, the policyRowStatus should be set to createAndWait. The status should not be set to active until the remaining objects of the entry have been specified. If an existing entry is to be modified, then the RowStatus should be set to notInService, the objects modified, and then the RowStatus set to active. If the RowStatus is set to indicate that the entry is to become active (CreateAndGo or Active), then the following rules are checked: 1) At least one of requireNeNscOperator or requireRpNscOperator or mustAvoidNeNscOperator must be specified. 2) If the requireNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of require. 3) If the requireRpNscOperator is specified, then at least one Rp-NSC value must exist in an active row of the policyRpNscTable for this policyIndex. 4) If the mustAvoidNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of mustAvoid. If a row is deleted from this table, then the corresponding rows of the policyNeNscTable and policyRpNscTable are also deleted. In addition, any entries in the policyConstraintTable that reference this policyIndex are removed.

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

policyTable · currentATM Forum official specifications1 source

Status in source: current.

Names: policyTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "policyTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "PolicyEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The table whose entries describe the policies configured. Each policy contains two possible policy operators: 'require' and 'must avoid'. The require policy operator can be applied with an Ne-NSC list, an Rp-NSC list or both. The must avoid policy operator can be applied with only an Ne-NSc list. In order to create a new policy, the policyRowStatus should be set to createAndWait. The status should not be set to active until the remaining objects of the entry have been specified. If an existing entry is to be modified, then the RowStatus should be set to notInService, the objects modified, and then the RowStatus set to active. If the RowStatus is set to indicate that the entry is to become active (CreateAndGo or Active), then the following rules are checked: 1) At least one of requireNeNscOperator or requireRpNscOperator or mustAvoidNeNscOperator must be specified. 2) If the requireNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of require. 3) If the requireRpNscOperator is specified, then at least one Rp-NSC value must exist in an active row of the policyRpNscTable for this policyIndex. 4) If the mustAvoidNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of mustAvoid. If a row is deleted from this table, then the corresponding rows of the policyNeNscTable and policyRpNscTable are also deleted. In addition, any entries in the policyConstraintTable that reference this policyIndex are removed. \"",
    "::=",
    "{",
    "policyGroup",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "PolicyEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The table whose entries describe the policies configured. Each policy contains two possible policy operators: 'require' and 'must avoid'. The require policy operator can be applied with an Ne-NSC list, an Rp-NSC list or both. The must avoid policy operator can be applied with only an Ne-NSc list. In order to create a new policy, the policyRowStatus should be set to createAndWait. The status should not be set to active until the remaining objects of the entry have been specified. If an existing entry is to be modified, then the RowStatus should be set to notInService, the objects modified, and then the RowStatus set to active. If the RowStatus is set to indicate that the entry is to become active (CreateAndGo or Active), then the following rules are checked: 1) At least one of requireNeNscOperator or requireRpNscOperator or mustAvoidNeNscOperator must be specified. 2) If the requireNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of require. 3) If the requireRpNscOperator is specified, then at least one Rp-NSC value must exist in an active row of the policyRpNscTable for this policyIndex. 4) If the mustAvoidNeNscOperator is specified, then at least one Ne-NSC value must exist in an active row of the policyNeNscTable for this policyIndex and an policyOperator of mustAvoid. If a row is deleted from this table, then the corresponding rows of the policyNeNscTable and policyRpNscTable are also deleted. In addition, any entries in the policyConstraintTable that reference this policyIndex are removed."
    ],
    null,
    null,
    null,
    null
  ]
}

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.3.2.1 policyEntry55

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.353.5.9.5.1.1.3.1 policyNextPolicyIndex00
1.3.6.1.4.1.353.5.9.5.1.1.3.3 policyNeNscTable15
1.3.6.1.4.1.353.5.9.5.1.1.3.4 policyRpNscTable14
1.3.6.1.4.1.353.5.9.5.1.1.3.5 policyReferenceTable12