GDMO / CMIS / CMIP Karina Marcus Institut Eurécom.

of 35/35
GDMO / CMIS / CMIP Karina Marcus Institut Eurécom
  • date post

  • Category


  • view

  • download


Embed Size (px)

Transcript of GDMO / CMIS / CMIP Karina Marcus Institut Eurécom.

  • Page 1
  • GDMO / CMIS / CMIP Karina Marcus Institut Eurcom
  • Page 2
  • Le modle OSI Cadre gnral s'inscrit dans la partie 4 du modle de rfrence OSI spcifie les procdures de gestion d'un rseau htrogne dfinit le cadre architectural des normes de gestion OSI Objectifs "planifier, coordonner, organiser, contrler et superviser les ressources utilises dans les communications conformes au modle OSI et rendre compte de leur utilisation"
  • Page 3
  • Trois modles Modle organisationnel Modle dinformation Modle fonctionnel
  • Page 4
  • Le modle organisationnel dfinit le cadre pour rpartir la gestion s'appuie sur les concepts de "systmes grs" et de "systmes grants" (agents and management systems) le processus d'application de gestion distribue (DMAP : Distributed management application process) est l'application qui contrle et surveille les objets grs. le processus agent (AP : Agent Process) permet la gestion locale.
  • Page 5
  • Schma dorganisation Systme d'administration Processus de gestion CMISE CMIP Processus agent Fonctions Objets grs D Systme administr
  • Page 6
  • Objets grs Objet administr Attributs Opration Notification
  • Page 7
  • Le modle dinformation Une approche objet un langage de description un langage dchanges Des principes nommage enregistrement Des bibliothques
  • Page 8
  • Approche objets Objectif : Permettre de dfinir les objets administrs de manire standard cohrence des dfinitions cohrence avec l'environnement d'administration (CMIP et fonctions) rpartition du travail
  • Page 9
  • Modle objet Le modle dfinit : ce qu'est un objet de quoi il est compos ce qu'il peut faire ce qui peut lui tre fait comment il est nomm dans le protocole comment il est reli aux autres objets
  • Page 10
  • Description des objets Les attributs Les mthodes Les relations Les paquetages conditionnels L'arbre de contenance L'allomorphisme
  • Page 11
  • Hierarchy tree example TOP Open System Layer Entity ConnectionCounterAddress T-entity T-connection TPDU counter Peer T-address Hierarchy subtree
  • Page 12
  • Hierarchy and contenance tree example TOP Open System Layer Entity ConnectionCounterAddress T-entity T-connection TPDU counter Peer T-address Hierarchy subtree + Contenance
  • Page 13
  • Name Levels DN: [email protected][email protected]=1, LDN: [email protected]=1, RDN: T-connectionId=1, DN and LDN are sequence of RDNs, MO instances can be referenced either as DNs or LDNs since their application is relative to a given association with a given agent. systemId=fuschia systemId=lotus T-entityId=TCP T-connectionId=1T-connectionId=2... root
  • Page 14
  • GDMO: Guidelines for the Definition of MOs Templates for the definition of the interface to managed objects: Nature of managed objects in the MIT, inheritance relationships, features Structure of the MIT, Limited specification of behaviors Features of MOs are encapsulated into packages, one mandatory and eventually optional packages: Attributes with their ASN.1 syntax, access modes and matching rules, Actions with ASN.1 types for their action argument, reply and parameters, Notifications with ASN.1 types for event argument, reply and parameters. Name bindings: possible containment relationships between classes (superior, subordinate and a naming attribute), MIT and MOs are purely virtual management abstractions, there is no need for any corresponding actual representations.
  • Page 15
  • Information Model All that is defined using the templates may be registered in the registration tree. Templates to specify Managed object class Package Parameter Behavior Notification Name binding Attribute Attribute group Action
  • Page 16
  • The registration tree root (world) ccitt iso joint-iso-ccitt std reg member org authority body dod internet directory mgmt experimental private entreprises reserved proteon ibm hp 0 21 0 12 3 6 1 1 23 4 1 0 1 2 11 MIB-1 MIB-2 1 ms 3 9 smi part1partN... 1N
  • Page 17
  • Page 18
  • Page 19
  • Package Template PACKAGE [BEHAVIOUR DEFINITIONS [, ]*;] [ATTRIBUTES propertylist [ ]* [, propertylist [ ]*]*;] [ACTIONS [ ]* [, [ ]*]*;] [NOTIFICATIONS [ ]* [, [ ]* ]*;] [REGISTERED AS ];
  • Page 20
  • Package Template Propertylist -> [REPLACE WITH DEFAULT] [DEFAULT VALUE ] [INITIAL VALUE ] [PERMITTED VALUES ] [REQUIRED VALUES ] [get-replace] [add-remove] get-replace -> GET | REPLACE | GET-REPLACE add-remove -> ADD | REMOVE | ADD-REMOVE
  • Page 21
  • Example of a class exampleObjectClass MANAGED OBJECT CLASS DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2 : 1992" : top; CHARACTERIZED BY examplePackage1 PACKAGE; examplePackage2 CONDITIONAL PACKAGE ACTIONS qOSResetAction; NOTIFICATION communicationError ; REGISTRED AS {joint-iso-ccitt ms(9) smi(3) part4(4) package(4) examplepack1(0)}; PRESENT IF!conformance class 2 of underlying ressource implemented as descriptor in ISO/IEC xxxx! ; REGISTRED AS {joint-iso-ccitt ms(9) smi(3) part4(4) managedObjectClass(3) exampleclass(0)} ;
  • Page 22
  • Example : system object system MANAGED OBJECT CLASS DERIVED FROM top; CHARACTERIZED BY systemPackagePACKAGE ATTRIBUTESsystemIdGET, systemTitleGET, operationalStateGET, usageStateGET, administrativeStateGET-REPLACE;;; CONDITIONAL PACKAGES administrativeStatePackagePACKAGE ATTRIBUTESadministratoveStateGET-REPLACE; REGISTERED AS{smi2Package14}; PRESENT IF "an instance supports it",....
  • Page 23
  • The object TOP topMANAGED OBJECT CLASS CHARACTERIZED BY topPackage PACKAGE BEHAVIOUR topBehaviour; ObjectClassGET, nameBindingGET;;; CONDITIONAL PACKAGESpackagesPackagePACKAGE ATTRIBUTESpackagesGET; REGISTERED AS {smi2Package 16}; PRESENT IF "any REGISTERED package, other than this package has been instancied", allomorphicPackagePACKAGE ATTRIBUTESallomorphsGET; REGISTERED AS {Smi2Package 17}; PRESENT IF "if an object supports allomorphism"; REGISTERED AS {smi2MObjectClass 14}; topBehaviourBEHAVIOUR DEFINED AS "This is the top level of managed object class hierarchy and every other managed objet class is a specialization of either this generic class (top) or a specialization of a subclass of top..."
  • Page 24
  • Attribute Template ATTRIBUTE derived-or-with-syntax-choice; [MATCHES FOR qualifier [, qualifier]*;] [BEHAVIOUR [, ]*] [PARAMETERS [, ]*;] [REGISTERED AS ]; qualifier -> EQUALITY | ORDERING | SUBSTRINGS | SET COMPARISON | SET INTERSECTION derived-or-with-syntax-choice -> DERIVED FROM | WITH ATTRIBUTE SYNTAX
  • Page 25
  • Attribute definition example eventTime ATTRIBUTE WITH ATTRIBUTE SYNTAXE AttributeASN1Module.EventTime ; MATCHES FOR EQUALITY, ORDERING; BEHAVIOUR timeOrdering; REGISTERED AS {smi2AttributeID 13}; timeOrdering BEHAVIOUR DEFINED AS The year, month, day, hour, minute, and seconds fields are compared in order to determine whether the specified value is greater or less than the value of the attribute. The values for the year, month, day, hour, minute, and seconds are determined from the character string representation and the year value is first compared. If equal, the month value is compared and this process is continues if the compared fields are equal.
  • Page 26
  • Managed Object Naming Locating MOs in the MIT, Supported by the name binding template establishing a containment relationship between a superior MOC and a subordinate MOC according to a naming attribute of the subordinate class, Example transportConnection-nb-1 NAME BINDING SUBORDINATE OBJECT CLASS T-connection; NAMED BY SUPERIOR OBJECT CLASS T-entity; WITH ATTRIBUTE T-connectionId; DELETE deletes-contained-objects; T-entityId=TCP T-connectionId=1T-connectionId=n...
  • Page 27
  • Page 28
  • CMIS Services vs GDMO CMIS services enable access/manipulation of the MIT, GDMO specifications give the rules to define adequate CMIS parameters, Name Bindings and naming attribute give the object instance names for MOs, ASN.1 attribute types, action / event argument / reply / parameters types are given by the corresponding GDMO specifications, Attribute matching rules determine the possible filters
  • Page 29
  • CMISE/CMIP Les services de CMISE Interactions avec les interfaces des objets (lecture, criture, creation, destruction dinstances,...) Utilisation des principes de nommage Slection dobjets multiples Actions multiples (atomicit)
  • Page 30
  • Slection dobjets multiples -2 -3 Scoping Filtering (valeurs dattributs)
  • Page 31
  • Multiple Object Selection and Multiple Replies Multiple object selection = scoping + filtering scoping: baseObject=3 wholeSubTree: 3,6,7,8,9,10,11, nthLevel e.g. 1stLevel: 6,7, baseToNthLevel e.g. baseTo1stLevel: 3,6,7. Filtering: logical expression on MO attribute values (numerical or string based comparisons) grouped through AND/OR/NOT logical operators, This results as a subset of MIT MOs on which is executed the CMIS request (m-get, m-set, m-action, m-delete) and incurring several replies, Multiple replies may also simply occur through action incurring several replies 11 1 2 3 4 567 8910
  • Page 32
  • Services CMIP Opration/notificationService Mode Get attribute valueM-GET confirm M-CANCEL-GET confirm Replace attribute value Replace with default value Add memberM-SETconf/non-conf Remove member CreateM-CREATE confirm DeleteM-DELETE confirm ActionM-ACTIONconf/non-conf NotificationM-EVENT-REPORTconf/non-conf
  • Page 33
  • Exemple : M_CREATE Paramtres spcifiques superior object instance reference object instance Service nommage : c'est--dire dfinir le GDN (Global Distinguished Name) -->choisir le suprieur dans l'arbre de nommage choisir le RDN (Relative Distinguished Name) M-CREATE utilise 3 paramtres spcifiques : - MOC (Managed object Class) - sa classe - MOI (Managed Object Instance) - son GDN - SOI (Superior Object Instance) - le GDN du suprieur Le gestionnaire a trois possibilits : il peut envoyer MOC et MOI, MOC et SOI ou MOC Dans tous les cas, l'agent renverra MOC et MOI
  • Page 34
  • Exemple : M_CREATE services (suite) Valorisation des attributs Par ordre de priorit : liste d'attributs envoys valeurs de l'objet de rfrence valeurs par dfaut de la classe
  • Page 35
  • Quelques liens... GDMO - a searchMiddleware definition - see also: Guidelines...... GDMO, GDMO (Guidelines for Definition of Managed Objects) is a standard for defining objects in a network in a consistent way. With a consistent "language" for...,,sid26_gci213981,00.html - Solstice GDMO Builder 1.0... Solstice TM GDMO Builder 1.0.... Solstice GDMO Builder Home | Management Home | software site map, Solstice GDMO Builder : Overview.... - 16k - Cached - Similar pages A Methodology for Formalizing GDMO Behavior Descriptions -... A Methodology for Formalizing GDMO Behavior Descriptions (1999) (Correct) (1 citation) P. Hasselmeyer Information Technology Transfer Office Darmstadt... - 18k - Cached - Similar pages etc.. Rechercher GDMO avec Google J ai not pour vous :