Scoping in CMTP / CMIS mgmt standard -

• Scoping is meant to be understood in terms of containment hierarchy. A position at a certain level of the containment tree is defined by the CMIS managed object close parameters.

• The CIMS scope parameter is then, interpreted relative to this managed object.

• The scope parameter can be used to select object alone, all MO's in the entire subtree (of the containment tree) below the object, or all managed objects in the "nth level ( n = 1, 2, 3, ---) below the object.

• Filtering produces the ability to select a subset of these objects based on conditions applied to attributes. e.g. (IP routing table entries with the " ip Route Age > 100" ) and logical operations ( and, or, not)

• Within the objects selected as a result of the scope parameters, it is possible to further refine the selection of managed objects through the use of filtering.

• common mgmt information service element (CMISE) applies some powerful features to the operations that helps to distinguish CMISE function SNMP.

• The M-GET, M- Action, M - Delate, M- set, M- create services can be applied to more then one managed object through the application of scoping filtering.

• CMISE requests can be scoped to apply to a range of managed objects. four levels of scoping can be applied, with the request being applied to

  1) Base object.

  2) Objects at the n th level subordinate to the object.

  3) Base object and all managed objects to the nth level.

  4) An entire subtree - the base object and all subordinate objects.

• Filtering is the application of a expression to the request with the request being applied to only those managed objects and attributes to which the expression is TRUE.

• The type of rules that can be applied to the request include equality, greater than or equal, less than are equal and presence of an attributes.

• CMIP Protocol service elements :

  1. m-CREATE - detects the agent be create new instance (s) of a MO class or attributes within a MO.

  2. M-DELETE - directs the agent to delete existing instances of MP class (es) or attributes within a set contained in a MO.

  3. M-GET - Directs the agent to return attribute values from MOs

  4. M-SET - directs the agent to change the value of MO attribute(s)

  5. M-ACTION - directs the agent to cause one or more MOs to execute or action.

  6. M-EVENT REPORT - Service is issued by an agent to send a notification to managers.

• Once all the requested objects have been identified, the performance of the request can be completed based on one of the two synchronisation schemes : atomic or best effort.

• Atomic operations are only performed after all MOs pertaining to the scoping/filling are able to successfully complete the requested operation.

• Best effort synchronization will direct the request to all applicable MOs. The requested operation is complete by as many objects that can comply.