1 / 29

Java Based API and Daemon for Network Management using Common Management Information Protocol

Java Based API and Daemon for Network Management using Common Management Information Protocol. Mohan Lal Jangir 2000EET010 with Dr. Subrat Kar. Background Proposed problem and motivation Outline of proposed work Brief review ASN.1 Management Model CMIP Elements and Services

jonco
Télécharger la présentation

Java Based API and Daemon for Network Management using Common Management Information Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Java Based API and Daemon for Network Management usingCommon Management Information Protocol Mohan Lal Jangir2000EET010 with Dr. Subrat Kar

  2. Background Proposed problem and motivation Outline of proposed work Brief review ASN.1 Management Model CMIP Elements and Services CMIP over TCP/IP Summary

  3. Abstract Syntax Notation ( ASN.1 ) Good morning Representation: Issues in inhomogeneous networks

  4. A1 D4 B2 C3 C3 B2 D4 A1 • An integer value 2712847316 can be stored in two ways : Big-endian 10.10.1.4 Little-endian 10.64.2.10

  5. Other representation problems : floating point format data type size : 16 bit, 32 bit, 64 bit different size : layout of data structure Therefore a medium is required which could be understood by either of the systems. This is provided by ASN.1

  6. Abstract Syntax data description language, not a programming language defines universal data types allow user-defined data types BasicEncodingRules converts abstract syntax specification of data structure into series of bytes ASN.1: Syntax

  7. Tagging and Encoding ASN.1 data is self-identifying each transmitted value is encoded using tag-length-value (TLV) encoding 8-bit tag tag type, 2-bits primitive versus constructed, 1-bit tag value, 5-bits 8-bit length can exceed if length is more than 127 bytes ASN.1:Tagging & Encoding

  8. Conceptual repository of data each component has a unique identifier name called OBJECT IDENTIFIER ManagementInformationBase

  9. tcp tcpRtoAlgorithm tcpConnTable tcpConnEntry tcpConnState tcpConnLocalAddress tcpConnLocalPort tcpConnRemAddress tcpConnRemPort A small portion of MIB

  10. ISO Management Model • Managed Resource • manageable device or logical unit in network • Managed Object • presents an abstract view of managed resource • Inheritance • relationship between managed object classes • Containment • relationship between managed object instances • used to name managed object instances

  11. Router 1 Interface card 2 Interface card 1 Router1 Interface card 3 Interface card 3 Managed Objects Interface card 2 Interface card 1 Managed Resources Containment Hierarchy

  12. CMISE ROSE ACSE Lightweight Presentation Layer TCP UDP Internet Protocol Data Link CMOT Protocol Suite

  13. This protocol consists of three elements : Association Control Service Element (ACSE) Common Management Information Service Element (CMISE) Remote Operation Service Elements (ROSE) CMISE uses services provided by ACSE and ROSE ACSE and ROSE uses services provided by LPP layer CMIP

  14. CMISE Services

  15. multipleObjectSelection pertains to CMIP request that specify scoping scoping allows a single request to be fanned out to several managed objects optional multipleReply pertains to responses request containing scoping generally results in multipleReply optional Functional Units

  16. Filter pertains to CMIP requests that specify a test to be applied to managed objects before request is carried out very useful with scoping optional kernel support for M-GET, M-SET, M-ACTION, M-DELETE, M-CREATE and M-EVENT REPORT mandatory

  17. 23 1 21 80 5 6 tcpConnEntry Delete 4, 5 1, 2, 3, 4, 5 3 4 2 7 Power of Scoping and Filtering SNMP

  18. 23 1 21 80 5 6 tcpConnEntry, remotePort 80 Delete 4, 5 3 4 2 4, 5 7 CMIP

  19. Issues in CMIP • Scoping • Base object only • base object plus subordinates down to level n * • subordinates at level n • all subordinates • Filtering • item • and • or • not • filterItem • equality • greaterorequal • lessorequal • subsetof

  20. Baseobjectonly Entire subtree Level 2 subordinate objects Base object plus subordinate objects down to level 3 root

  21. ACSE is necessary for establishing and releasing application associations ACSE services A-ASSOCIATE : initiates an application association between two application entities A-RELESE : releases an application association without loss of information A-ABORT : causes abnormal release of an association with a possible loss of information LPP services are used for above services Association Control Service Element

  22. Can be used once an association has been established ROSE services : RO-INVOKE : used by an invoking ROSE-user to cause the invocation of an operation to be performed by an invoked ROSE-user RO-RESULT : used by an invoked ROSE-user to reply to a previous RO-INVOKE indication, if operation was performed successfully Remote Operation Service Element

  23. Services continued . . . RO-ERROR : used by an invoked ROSE-user to reply to a previous RO-INVOKE indication in the case of an unsuccessfully performed operation RO-REJECT : to reject a request of other ROSE-user LPP services are used for above services

  24. Issue is to put ISO application on top of TCP/IP suite goal is to somehow fill the gap between the ISO protocol (ACSE & ROSE) and the Internet protocols (UDP & TCP) Two approaches are possible : CMIP over TCP/IP (CMOT)

  25. Extending ISO stack extend the ISO portion of the protocol stack down to the transport layer this allows us to operate “standard” ISO application over TCP regardless of their service requirements full ISO presentation, session, and transport layers are expensive to implement

  26. Lightweight Presentation Layer since the ACSE, ROSE and CMISE do not require use of full ISO presentation services, we can do with services required only, (thus  lightweight) minimal approach is justified because non-ISO presentation protocol is very small and simple Lightweight Presentation Layer

  27. MIB GUI 3 1.3.6.1.2.1.1 3 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 3 1.3.6.1.2.1.1 3 49 8 2 1 -126 3 17 -63 -45 SET INTEGER 3 INTEGER 1163731 sysUpTime 1163731 3 1.3.6.1.2.1.1 3 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 1163731 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 49 8 2 1 -126 3 17 -63 -45 49 8 2 1 -126 3 17 -63 -45 SET INTEGER 3 INTEGER 1163731 49 8 2 1 -126 3 17 -63 -45 M-GET System sysUpTime 49 8 2 1 -126 3 17 -63 -45 1163731 2 1 3 48 13 6 6 43 6 1 2 1 1 48 3 2 1 3 49 8 2 1 -126 3 17 -63 -45 Interpreter Manager Serializer/ Deserializer Serializer/ Deserializer Agent LPP Network LPP An Example Data Flow and Format

  28. Development of Daemon Development of API Development of GUI Development of Serializer and Deserializer for ASN.1 LPP Layer PDUs : M-GET, M-SET (c/n), M-DELETE Work Done

  29. R.Stalling : SNMP, SNMPv2 and RMON, Prentice Hall, 2000 RFC 1095 (CMIP) RFC 1085 (LPP) RFC 1213 (SNMP) References

More Related