cmd 4 0 managed object hierarchy

7/30/2019 Cmd 4 0 Managed Object Hierarchy

1/5

DN09107604

Issue 2-1

CMD 4.0 Managed Object Hierarchy


The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is not an official customer document and Nokia Siemens Networks does not take responsibility for any errors or omissionsin this document. This document is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement underwhich the document is submitted. No part of this documentation may be used, reproduced, modified or transmitted in any form or means withoutthe prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trainedpersonnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of theprocess of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity or performance of the mentioned hardware orsoftware products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusivelyand finally in a separate agreement between Nokia Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDINGBUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUT NOT LIMITEDTO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, that might arise from the use of thisdocument or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE MANDATORY LAW, NOWARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT, ARE MADE IN RELATION TO THEACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE

THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.

This document and the product it describes are considered protected by copyrights and other intellectual property rights according to theapplicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registeredtrademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identificationpurposes only.

Copyright @ Nokia Siemens Networks 2008. All rights reserved.


2/5

DN09107604Issue 2-1


Object Class: ONL

Object class attributes Value

ID ONL

Path NSNNetwork->CMDContainer->CMD->ONL

Super class ManagedObject

Presentation ONL

Description ONL

Object Class: EMC


ID EMC

Path NSNNetwork->CMDContainer->NETY->NEIN->EMC

Super class ManagedObjectPresentation EMC CLARiiON

Description EMC CLARiiON storage device

Object Class: CCLI


ID CCLI

Path NSNNetwork->CMDContainer->CMD->OFFL->COLL->CCLI

Super class ManagedObjectPresentation CCLI

Description CCLI

Object Class: NETY


ID NETY

Path NSNNetwork->CMDContainer->NETY

Super class ManagedObjectPresentation NETY

Description NETY

Object Class: DIST


ID DIST

Path NSNNetwork->CMDContainer->CMD->OFFL->DIST

Super class ManagedObjectPresentation DIST

Description DIST


3/5

DN09107604Issue 2-1


Object Class: FS


ID FS

Path NSNNetwork->CMDContainer->NETY->NEIN->BRM->FS


Presentation FS

Description FS

Object Class: BRM


ID BRM

Path NSNNetwork->CMDContainer->NETY->NEIN->BRM

Super class ManagedObjectPresentation BRM

Description BRM

Object Class: CMDContainer


ID CMDContainer

Path NSNNetwork->CMDContainer

Super class NSNNetworkElementPresentation Charge AtOnce Mediate Container

Description The container for holding the CMD and NETY Objects

Object Class: CMD


ID CMD

Path NSNNetwork->CMDContainer->CMD

Super class NSNNetworkElementPresentation Charge AtOnce Mediate NE

Description Charge AtOnce Mediate Network Element

Object Class: PROC


ID PROC

Path NSNNetwork->CMDContainer->CMD->OFFL->PROC

Super class ManagedObjectPresentation PROC

Description PROC


4/5

DN09107604Issue 2-1


Object Class: OFFL


ID OFFL

Path NSNNetwork->CMDContainer->CMD->OFFL


Presentation OFFL

Description OFFL

Object Class: PCLI


ID PCLI

Path NSNNetwork->CMDContainer->CMD->OFFL->PROC->PCLI

Super class ManagedObjectPresentation PCLI

Description PCLI

Object Class: COLL


ID COLL

Path NSNNetwork->CMDContainer->CMD->OFFL->COLL

Super class ManagedObjectPresentation COLL

Description COLL

Object Class: NODE


ID NODE

Path NSNNetwork->CMDContainer->CMD->NODE

Super class PhysicalDevicePresentation Charge AtOnce Mediate Node

Description Node of Charge AtOnce network element

Object Class: NEIN


ID NEIN

Path NSNNetwork->CMDContainer->NETY->NEIN

Super class ManagedObjectPresentation NEIN

Description NEIN


5/5

DN09107604Issue 2-1


Object Class: NSNNetwork


ID NSNNetwork

Path NSNNetwork

Super class Network

Presentation NSN Network

Description The Network class is derived from M.3100; DEN-ng has enhanced this definition by providing additional semantics thatenable objects defined in the ITU to interact with objects defined in the IETF and the TMF. A Network is a managed objectthat represents an aggregation of interconnected telecommunications and management objects capable of exchanging information. The reason that a Network is subclassed from ResourceCollection is that it is important that a Networkbe able to represent physical as well as logical characteristics and behavior of this collection of telecommunications andmanagement objects. A Network has the additional semantics of having one or more common characteristics and/orbehavior. For example, a network may be owned by a single customer or provider, or be associated with the delivery of aspecific set of services. A network may be nested within another (larger) network, thereby forming a containment relationship. An example of a network that is contained in another network is a transmission sub-network. It is owned by a singleAdministration and can only perform transmission functions. The m.3100 SystemTitle attribute is NOT implemented in thisclass, we're using UserLabel instead. Note that the LocationName attribute of m.3100 and MTNM is NOT implementedin this class, but rather is defined through an association to the Location object class in order to represent more generictypes of associations. The MTNM managedElementName, nativeEMSName, communucationState, and emsInSyncState attributes are NOT implemented in this class, as all SHOULD be derived from the ManagedDevices association. Notethat there can be multiple EMSes that manage any given ManagedElement. The MTNM owner attribute is NOT implement

ed in this class, as it is derived from the MEOwner association. Note that there can be multiple owners for any givenManagedElement. The MTNM connectionRate attribute is NOT implemented in this class, as not all ManagedElementshav...

Object Class: DCLI


ID DCLI

Path NSNNetwork->CMDContainer->CMD->OFFL->DIST->DCLI


Presentation DCLI

Description DCLI

cmd 4 0 managed object hierarchy

Documents