| OID symbolic | OID numeric | Type | Access | Description |
| atmForum | 1.3.6.1.4.1.353 | | | |
| atmForumNetworkManagement | 1.3.6.1.4.1.353.5 | | | |
| atmfPolicyConstraint | 1.3.6.1.4.1.353.5.9.5 | | | |
| atmfSignalling | 1.3.6.1.4.1.353.5.9 | | | |
| atmPolicyConstraintMIB | 1.3.6.1.4.1.353.5.9.5.1 | | | 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. |
| INT mustAvoidNeNscOperator | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1.4 | INTEGER | read-create | An integer identifying the NSC List operator
for the Ne-NSC list of the must avoid policy operator.
The policy operator singleNeNsc is assumed if only one Ne-NSC
is specified in the associated Ne-NSC list. |
| policyConstraintBaseGroup | 1.3.6.1.4.1.353.5.9.5.1.1.1 | | | |
| policyConstraintEntry | 1.3.6.1.4.1.353.5.9.5.1.1.2.2.1 | | not-accessible | Each entry in this table specifies a policy constraint.
The policy constraint consists of up to 6 policies.
A policy constraint must contain at least one policy
if it is to be used in another MIB object.
The order of the policies within the policy constraint
is important and defines the order in which the policies
are to be applied during path selection and call
establishment.
If a policy is specified in the policy constraint, but that
policy does not exist as an active row of the policyTable,
then that policy is ignored when the policy constraint is used
for call establishment. |
| policyConstraintGroup | 1.3.6.1.4.1.353.5.9.5.1.1.2 | | | |
| NUM policyConstraintIndex | 1.3.6.1.4.1.353.5.9.5.1.1.2.2.1.1 | PolicyConstraintIndex | not-accessible | An arbitrary integer uniquely identifying a policy
constraint. Its value can be used within other managed
objects to apply a policy constraint to the object. |
| I32 policyConstraintMaximum | 1.3.6.1.4.1.353.5.9.5.1.1.1.1 | Integer32 | read-write | The maximum number of concurrent active policy constraints
that are allowed by the agent. A value of 0 for this
object implies that there is no limit on the number of
concurrent active policy constraints. |
| policyConstraintMIBCompliance | 1.3.6.1.4.1.353.5.9.5.1.1.4.1.1 | | | The compliance statement for entities which implement the
Policy Routing Addendum for Policy Constraint MIB.
Groups of objects required to support certain functionality
are identified by the suffix MandatoryGroup.
Groups of optional objects are identified by the suffix
OptionalGroup. |
| policyConstraintMIBCompliances | 1.3.6.1.4.1.353.5.9.5.1.1.4.1 | | | |
| policyConstraintMIBConformance | 1.3.6.1.4.1.353.5.9.5.1.1.4 | | | |
| policyConstraintMIBGroups | 1.3.6.1.4.1.353.5.9.5.1.1.4.2 | | | |
| policyConstraintMIBMandatoryGroup | 1.3.6.1.4.1.353.5.9.5.1.1.4.2.1 | | | A collection of objects required when policy constraint
specification is supported. |
| policyConstraintMIBObjects | 1.3.6.1.4.1.353.5.9.5.1.1 | | | |
| policyConstraintMIBOptionalGroup | 1.3.6.1.4.1.353.5.9.5.1.1.4.2.2 | | | A collection of optional objects used for path and connection
trace. |
| STR policyConstraintName | 1.3.6.1.4.1.353.5.9.5.1.1.2.3.1.1 | DisplayString | read-create | The name of the Policy Constraint. This is used
to facilitate management of the policy constraints
between SNMP and other management interfaces. |
| policyConstraintNameEntry | 1.3.6.1.4.1.353.5.9.5.1.1.2.3.1 | | not-accessible | Each entry in this table specifies a name of a
policy constraint. |
| ROW policyConstraintNameRowStatus | 1.3.6.1.4.1.353.5.9.5.1.1.2.3.1.2 | RowStatus | read-create | To create, delete, activate and de-activate a name
of a policy constraint. |
| policyConstraintNameTable | 1.3.6.1.4.1.353.5.9.5.1.1.2.3 | | not-accessible | The table whose entries define the names for the policy
constraints. |
| NUM policyConstraintPolicyIndex | 1.3.6.1.4.1.353.5.9.5.1.1.2.2.1.2 | PolicyConstraintPolicyIndex | not-accessible | An integer uniquely identifying a policy
within a policy constraint. The value of this
index defines the order in which the policies
of the policy constraint are applied. |
| ROW policyConstraintRowStatus | 1.3.6.1.4.1.353.5.9.5.1.1.2.2.1.4 | RowStatus | read-create | To create, delete, activate and de-activate a row
of a policy constraint.
Only those rows of the PolicyConstraintTable that have
an active status are considered when the policyConstraintIndex
is used for call establishment. |
| policyConstraintTable | 1.3.6.1.4.1.353.5.9.5.1.1.2.2 | | not-accessible | The table whose entries describe the policy constraints
configured in the agent. |
| policyEntry | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1 | | not-accessible | An entry representing a policy. |
| policyGroup | 1.3.6.1.4.1.353.5.9.5.1.1.3 | | | |
| POL policyIndex | 1.3.6.1.4.1.353.5.9.5.1.1.2.2.1.3 | PolicyIndex | read-create | The index into the policyTable for the policy
to be used in a given position within the
the policy constraint. There must be an entry
in the policyTable for this policy index
or the set is rejected.
The distinguished value of zero may be used to indicate
no policy is to be used in the position. |
| I32 policyMaximum | 1.3.6.1.4.1.353.5.9.5.1.1.1.2 | Integer32 | read-write | The maximum number of concurrent active policies
that are allowed by the agent. A value of 0 for this
object implies that there is no limit on the number of
concurrent active policies. |
| STR policyName | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1.1 | DisplayString | read-create | A textual string describing the policy. This is used
to facilitate management of the policies
between SNMP and other management interfaces. |
| NET policyNeNsc | 1.3.6.1.4.1.353.5.9.5.1.1.3.3.1.3 | NetworkEntityNetworkServiceCategory | read-create | One of the Ne-NSCs of the Ne-NSC list of the policy.
The policyNeNscOperator object defines how the list
is to be used by the policy.
Setting this object with a value of 65536 is equivalent
to deleting the object. Deleting the object will fail
if there are no other policyNeNsc objects with the same
policyIndex and policyOperator and the policyRowStatus
object for the policyIndex has the value active |
| policyNeNscEntry | 1.3.6.1.4.1.353.5.9.5.1.1.3.3.1 | | not-accessible | An entry representing the Ne-NSC list for a policy. |
| I32 policyNeNscIndex | 1.3.6.1.4.1.353.5.9.5.1.1.3.3.1.1 | Integer32 | not-accessible | An integer identifying the NeNSC within the Ne_NSC list
of a policy. |
| I32 policyNeNSCListMaximum | 1.3.6.1.4.1.353.5.9.5.1.1.1.3 | Integer32 | read-write | The maximum number of Ne-NSCs that can be included
in the Ne-NSC list of a policy. A value of 0 for this
object implies that there is no limit. |
| ROW policyNeNscRowStatus | 1.3.6.1.4.1.353.5.9.5.1.1.3.3.1.4 | RowStatus | read-create | Used to create and delete entries in this table.
When a new entry is being created or an existing
entry is being modified, then the RowStatus
should be set to createAndWait or notInService. Once
the objects for this row have been set, then the RowStatus
should be set to active. When a row is active, it can be
used in a policy to effect the establishment
of a call. If a policyNeNscEntry is used in a policy
while it is not active, then it shall be ignored
during the application of the policy. |
| policyNeNscTable | 1.3.6.1.4.1.353.5.9.5.1.1.3.3 | | not-accessible | The table whose entries describe the NeNSCs of the Ne-NSC lists
of a policy. |
| NUM policyNextPolicyConstraintIndex | 1.3.6.1.4.1.353.5.9.5.1.1.2.1 | PolicyConstraintIndex | read-only | Coordinate policyConstraintIndex value allocation for
entries in the policyConstraintTable.
A GET of this object returns the next available
policyConstraintIndex to be used to create an entry in the
policyTable; or zero if no valid policyIndex value
is available. This object also returns a value of zero
when it is the lexicographic successor of a varbind
presented in an SNMP GETNEXT or GETBULK request, for which
circumstance it is assumed that policyConstraintIndex
allocation is unintended.
Successive GETs will typically return different values,
Thus avoiding collisions among cooperating management
clients seeking to create table entries simultaneously. |
| POL policyNextPolicyIndex | 1.3.6.1.4.1.353.5.9.5.1.1.3.1 | PolicyIndex | read-only | Coordinate policyIndex value allocation for entries in
policyTable.
A GET of this object returns the next available policyIndex
to be used to create an entry in the policyTable; or zero if
no valid policyIndex value is available. This object also
returns a value of zero when it is the lexicographic
successor of a varbind presented in an SNMP GETNEXT or
GETBULK request, for which circumstance it is assumed
that policyIndex allocation is unintended.
Successive GETs will typically return different values,
Thus avoiding collisions among cooperating management
clients seeking to create table entries simultaneously. |
| POL policyOperator | 1.3.6.1.4.1.353.5.9.5.1.1.3.3.1.2 | PolicyOperator | not-accessible | An integer identifying whether the Ne-NSC list
is part of the require or must avoid operator
of a policy. |
| policyReferenceEntry | 1.3.6.1.4.1.353.5.9.5.1.1.3.5.1 | | not-accessible | An entry for the policy reference table. |
| NUM policyReferencePCIndex | 1.3.6.1.4.1.353.5.9.5.1.1.3.5.1.1 | PolicyConstraintIndex | read-only | If any of the entries of the PolicyConstraintTable
for the specified policyConstraintIndex has a value
for its policyIndex that matches the policyIndex
of this entry, then this returns the
policyConstraintIndex; otherwise, the value zero is
returned.
This object should be walked using GETNEXT
and specifying an initial value of zero for the
policyConstraintIndex. If a value of zero is returned,
then there are no more matching entries for the policyIndex. |
| policyReferenceTable | 1.3.6.1.4.1.353.5.9.5.1.1.3.5 | | not-accessible | This table provides pointers to entries in the
policyConstraintTable that reference the policyIndex.
This is provided to facilitate management of the
policies and policy constraints. |
| ROW policyRowStatus | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1.5 | RowStatus | read-create | Used to create and delete entries in this table.
When a new entry is being created or an existing
entry is being modified, then the RowStatus
should be set to createAndWait or notInService. Once
the objects for this row have been set, then the RowStatus
should be set to active. When a row is active, it can be
used in a policy constraint to effect the establishment
of a call. If a policy is used in a policy constraint
while it is not active, then it shall be ignored
during call establishment. |
| RES policyRpNsc | 1.3.6.1.4.1.353.5.9.5.1.1.3.4.1.2 | ResourcePartitionNetworkServiceCategory | read-create | One of the Rp-NSCs of the Rp-NSC list of the policy.
The policyRpNscOperator object defines how the list
is to be used by the policy.
Setting this object with a value of 65536 is equivalent
to deleting the object. Deleting the object will fail
if there are no other policyRpNsc objects with the same
policyIndex and the policyRowStatus
object for the policyIndex has the value active |
| policyRpNscEntry | 1.3.6.1.4.1.353.5.9.5.1.1.3.4.1 | | not-accessible | An entry representing the Ne-NSC list for a policy. |
| I32 policyRpNscIndex | 1.3.6.1.4.1.353.5.9.5.1.1.3.4.1.1 | Integer32 | not-accessible | An integer identifying the RpNSC within the Rp_NSC list
of a policy. |
| I32 policyRpNSCListMaximum | 1.3.6.1.4.1.353.5.9.5.1.1.1.4 | Integer32 | read-write | The maximum number of Rp-NSC entries that can be included
in the Rp-NSC list of a policy. A value of 0 for this
object implies that there is no limit. |
| ROW policyRpNscRowStatus | 1.3.6.1.4.1.353.5.9.5.1.1.3.4.1.3 | RowStatus | read-create | Used to create and delete entries in this table.
When a new entry is being created or an existing
entry is being modified, then the RowStatus
should be set to createAndWait or notInService. Once
the objects for this row have been set, then the RowStatus
should be set to active. When a row is active, it can be
used in a policy to effect the establishment
of a call. If a policyRpNSC Entry is used in a policy
while it is not active, then it shall be ignored
during the application of that policy |
| policyRpNscTable | 1.3.6.1.4.1.353.5.9.5.1.1.3.4 | | not-accessible | The table whose entries describe the RpNSCs of the Rp-NSC list
of a policy. |
| policyTable | 1.3.6.1.4.1.353.5.9.5.1.1.3.2 | | not-accessible | 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. |
| INT requireNeNscOperator | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1.2 | INTEGER | read-create | An integer identifying the NSC List operator
for the Ne-NSC list of the require policy operator.
The policy operator singleNeNsc is assumed if only one Ne-NSC
is specified in the associated Ne-NSC list. |
| INT requireRpNscOperator | 1.3.6.1.4.1.353.5.9.5.1.1.3.2.1.3 | INTEGER | read-create | An integer identifying the NSC List operator
for the Rp-NSC list of the require policy operator.
The policy operator singleRpNsc is assumed if only one Rp-NSC
is specified in the associated Ne-NSC list. |