Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary
CIM_TopologyGraph --> CIM_Collection --> CIM_ManagedElement --> [top]
Class Declaration Attributes Name Value SUPERCLASS CIM_Collection NAME CIM_TopologyGraph
Class CIM_TopologyGraph Qualifiers Name Type Value From Class Experimental boolean true CIM_TopologyGraph Version string 2.8.1000 CIM_TopologyGraph Description string TopologyGraph is a general structure for representing network topologies. Often, a topology graph consists of a set of nodes and a set of edges which connect the nodes. The TopologyGraph structure is slightly different, in order to support multipoint links and to express the connectivity within what would normally be considered a ’ node ’ . Multipoint links occur in entities such as IP subnets, where all of the IP endpoints on the subnet can communicate directly, and Ethernet links where all of the Ethernet interfaces on the shared media can communicate directly. An example of connectivity within a node is when the various endpoints/interfaces on a router are connected through the router ’ s forwarding mechanism. There may be different groups of endpoints which communicate within their groups exclusively. This is modeled as a DeviceConnectivityCollection. To represent these examples in a graph structure, TopologyGraph generalizes the node and edge structures of a typical graph. It is a collection of ConnectivityCollections, which can communicate with one another, and are at the same protocol layer. ConnectivityCollections are aggregated into Topology Graphs using the MemberOfCollection relationship. The actual network topology encoded in TopologyGraph is extracted by connecting the ConnectivityCollection instances that share common ProtocolEndpoint instances. For example, if the graph contains three collections, defined as: - Router1={PE1, PE2}, a DeviceConnectivityCollection - Link1={PE2, PE3}, an IPConnectivitySubnet - Router2={PE3, PE4}, a DeviceConnectivityCollection then we can determine that the PE2 interface on Router1 is connected to the PE3 interface on Router2 via the subnet Link1. By finding all of the endpoints that are in multiple ConnectivityCollections within the graph, and connecting those Collections with common endpoints, we can construct the network topology. CIM_TopologyGraph Description string Collection is an abstract class that provides a common superclass for data elements that represent collections of ManagedElements and its subclasses. CIM_Collection Description string ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. CIM_ManagedElement
Properties Name Type Value Qualifiers ClassOrigin InstanceID string Key
DescriptionCIM_TopologyGraph Caption string Description
MaxLenCIM_ManagedElement Description string Description CIM_ManagedElement ElementName string Description CIM_ManagedElement Property Qualifiers
Property InstanceID Qualifiers Name Type Value From Class Key boolean true CIM_TopologyGraph Description string Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following ’ preferred ’ algorithm: < OrgID > : < LocalID > Where < OrgID > and < LocalID > are separated by a colon ’ : ’ , and where < OrgID > MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the < Schema Name > _ < Class Name > structure of Schema class names.) In addition, to ensure uniqueness < OrgID > MUST NOT contain a colon ( ’ : ’ ). When using this algorithm, the first colon to appear in InstanceID MUST appear between < OrgID > and < LocalID > . < LocalID > is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above ’ preferred ’ algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance ’ s NameSpace. For DMTF defined instances, the ’ preferred ’ algorithm MUST be used with the < OrgID > set to ’ CIM ’ . CIM_TopologyGraph
Property Caption Qualifiers Name Type Value From Class Description string The Caption property is a short textual description (one- line string) of the object. CIM_ManagedElement MaxLen uint32 64 CIM_ManagedElement
Property Description Qualifiers Name Type Value From Class Description string The Description property provides a textual description of the object. CIM_ManagedElement
Property ElementName Qualifiers Name Type Value From Class Description string A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. CIM_ManagedElement
Method Qualifiers
Parameters
Parameter Qualifiers