Performing scoped and filtered M-GET operations

 

In order to clarify the cooperation of the distributed management environment, we will describe now how a scoped and filtered M-GET.request is handled by the QAF.

1.

The OSF issues through its CMIS/ACSE stack a scoped and filtered M-GET.request on a Base Managed Object Class (BMOC) of the QAF.

2.

The Infrastructure receives an M-GET.indication and passes the parameters to the Naming and Replication component.

3.

The instances contained in the scope are determined.

4.

If the base MOI of the request is not present in the containment hierarchy, an M-GET.response containing the noSuchInstance message is returned to the OSF.

5.

If the scope can be determined, every concerned MOI in the core agent receives a replica of the request.

6.

The core agent locates the MOI and executes the request on the MOI.

7.

This triggers the callback method of the addressed attribute. The callback method determines the OID and invokes an SNMP GET request on the managed resource through the SNMP interface. The SNMP GET response returns the value of the addressed SNMP MIB variable.

8.

The Core Agent receives the result and forwards it to the Infrastructure.

9.

The Infrastructure generates an M-GET.response message with linked replies. The OSF receives these replies (M-GET.confirm) through its CMIS/ACSE protocol stack.