Introduction to CMIS/P (Common Management Information Services / Protocol) 陳彥錚 (Yen-Cheng Chen)

1. Introduction to CMIS/P (Common Management Information Services / Protocol) 陳彥錚(Yen-Cheng Chen) http://www.im.tj.mcu.edu.tw/~ycchen/ yencheng@mcu.edu.tw

2. OSI Management Model SMI/GDMO SMFs MAs MO . . . . . . SMASE SMASE SMASE SMASE CMISE CMISE ACSE ROSE ACSE ROSE OSI Protocol Stack OSI Protocol Stack CMIS/P Link Link Network SMASE: Systems Management Application Service Element

3. OSI Management Standards • CMIS/P • Common Management Information Service / Protocol • SMFs • Systems Management Functions • SMI/GDMO • SMI: Structure of Management Information • GDMO: Guidelines for the Definition of Managed Objects

4. ACSE & ROSE • ACSE • Association Control Service Element • ROSE • Remote Operation Service Element

5. Systems Management Functions Applications SMFAs CM FM PM SM AM State Management Object Management Event Reporting Management Log Control Alarm Reporting Management Security Audit Trail Security Alarm Reporting SMFs Accounting Metering Test Management Workload Monitoring Summarization CMIS Get Set Action Cancel Get Event Report Delete Create Lower Layer Services

6. CMIS/P Standards • Recommendation X.701 | ISO/IEC 9595: 1991 Common Management Information Service (CMIS) Definition • Recommendation X.711 | ISO/IEC 9596-1: 1991 Common Management Information Protocol (CMIP) Specification • Recommendation X.712 | ISO/IEC 9596-2 Common Management Information Protocol (CMIP) - Protocol Implementation Conformance Statement (PICS) proforma

7. Protocol Stacks for OSI Management Management Applications SMASE Application Layer CMISE ACSE ROSE Presentation Session Transport Network Data Link Physical

8. Basic Reference Model CMISE User CMISE User req resp ind conf CMISE CMISE PDU conf: Confirmation ind: Indication req: Request resp: Response

9. CMISE Services Service Type M-CANCEL-GET confirmed M-EVENT-REPORT confirmed/non-confirmed M-GET confirmed M-SET confirmed/non-confirmed M-ACTION confirmed/non-confirmed M-CREATE confirmed M-DELETE confirmed

10. CMISE Services • M-GET: invoked by a CMISE-service-user to request the retrieval of management information from a peer CMISE-service-user • M-SET: invoked by a CMISE-service-user to request the modification of management information by a peer CMISE-service-user • M-CANCEL-GET: invoked by a CMISE-service user to request a peer CMISE-service-user to cancel a previously requested and currently outstanding invocation of the M-GET service

11. CMISE Services • M-CREATE: invoked by a CMISE-service-user to create an instance of a managed object • M-DELETE: invoked by a CMISE-service-user to request a peer CMISE-service-user to delete an instance of a managed object • M-ACTION: invoked by a CMISE-service-user to request a peer CMISE-service-user to perform an action • M-EVENT-REPORT:invoked by a CMISE-service-user to report an event about a managed object to a peer CMISE-service-user

12. CMISE Service Primitives CMIP Agent Manager Service Primitives in Manager Role Service Primitives in Agent Role M_CREATE request M_DELETE request M_GET request M_CANCEL_GET request M_SET request M_ACTION request M_Event_REPORT response M_CREATE response M_DELETE response M_GET response M_CANCEL_GET response M_SET response M_ACTION response M_Event_REPORT request

13. Three Trees in OSI Management • Registration Tree • Containment Tree • Inheritance Tree

14. Containment Tree root

15. Managed Object Selection - Scoping: identify the managed object(s) which a filter is to be applied. - Filtering: apply a set of tests to each member of the set of previously scoped managed objects to extract a subset.

16. Scoping base object • the base object alone • the nth level subordinates of the base object • the base object and all its subordinates down to and including the nth level • the base object and all of its subordinates (whole substree) 1th level

17. Filtering and Synchronization - Filtering - A filter is a set of one or more assertions about the presence or values of attributes in a scoped MO. If the filter test succeeds for a given managed object, then that managed object is selected for performance of the operation. - Synchronization -A synchronization parameter is provided to allow the CMISE-service-user to indicate the manner in which operations are to be synchronized across managed object instances when multiple MOs have been selected by the scope and filter mechanism. -Best efforts & atomic

18. Association Services Services Type A-ASSOCIATE Confirmed A-RELEASE Confirmed A-ABORT Non-confirmed A-P-ABORT Provider-initiated

19. Association Services A-ASSOCIATE Causes the establishment of an association A-RELEASE Causes the release of an association A-ABORT Causes the abnormal release of the association with the possible loss of information in transit A-P-ABORT Indicates the abnormal release of the association as a result of action by the underlying services

20. M_GET Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M Linked identifier - C Base object class M - Base object instance M - Scope U - Filter U - Access control U - Synchronization U - Attribute identifier list U - Managed object class - C Managed object instance - C Current time - U Attribute list - C Errors - C

21. Invoke Identifier and Linked Identifier Invoke Identifier: specifies the identifier of the operation. It can be used to distinguish this operation from other notification or operations that the CMISE-service-provider may have in progress. Each response shall have a unique invoke identifier; the final response shall have an invoke identifier equal to that of the invoke identifier provided in the indication primitive. Linked Identifier: When multiple replies are to be sent, it shall have the same value as that of the invoke identifier provided in the indication primitive. The completion of the response is indicated by the performing CMISE-service-user issuing an M-GET response primitive which shall not contain the linked identifier, and, if there were linked responses generated, which shall not contain the attribute list.

22. M_SET Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M Linked identifier - C Mode M - Base object class M - Base object instance M - Scope U - Filter U - Access control U - Synchronization U - Managed object class - C Managed object instance - C Modification list M - Attribute list - U Current time - U Errors - C

23. M-ACTION Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M Linked identifier - C Mode M - Base object class M - Base object instance M - Scope U - Filter U - Managed object class - C Managed object instance - C Access control U - Synchronization U - Action type M C(=) Action information U - Current time - U Action reply - C Errors - C

24. M-CREATE Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M(=) Managed object class M U MO instance M C Superior object instance U - Access U - Reference object instance U - Attribute list U C Current time - U Errors - C

25. M-DELETE Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M Linked identifier - C Base object class M - Base object instance M - Scope U - Filter U - Access control U - Synchronization U - Managed object class - C Managed object instance - C Current time - U Errors - C

26. M-EVENT-REPORT Service Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M(=) Mode M - Managed object class M U Managed object instance M U Event type M C(=) Event time U - Event information U - Current time - U Event reply - C Errors - C

27. M-CANCEL-GET Parameter/Name Req/Ind Rsp/Conf Invoke identifier M M Get invoke identifier M - Errors - C

28. Underlying Services invocation: CMISE request --> RO_INVOKE response: CMISE response --> RO_RESULT response: CMISE error response --> RO_ERROR receipt: CMISE APDU error --> RO_REJECT_U