Return to CIM_OSPFServiceConfiguration.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_OSPFServiceConfiguration.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:20 2012 UTC (12 years, 5 months ago) by marek Branch: MAIN CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824 Branch point for: TASK-PEP317_pullop-branch BUG#:9155 TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS DESCRIPTION: |
// Copyright (c) 2005 DMTF. All rights reserved. // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath // qualifier values to CIM Schema.</change> // ================================================================== // CIM_OSPFServiceConfiguration // ================================================================== [Association, Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::OSPF" ), Description ( "OSPFServiceConfiguration connects an OSPF service to its area " "configurations. The configurations are defined for the OSPF " "Service, and so do not make sense as stand alone objects. This " "is the reason for the Min (1), Max (1) cardinalities on " "OSPFService. They mandate the instantiation of the service and " "of this association for the referenced instance of " "OSPFAreaConfiguration. The area configuration acts as a focal " "point to bring together the router (indicated as a " "ComputerSystem with an instance of OSPFService, associated to " "the AreaConfiguration using this relationship), the area " "(indicated as an OSPFArea, associated to the AreaConfiguration " "using AreaOfConfiguration) and the address ranges for " "advertising (indicated as instances of RangeOfIPAddresses, " "associated to the AreaConfiguration using " "RangesOfConfiguration). There would be an instance of " "OSPFAreaConfiguration for each connected area of a " "router/OSPFService." )] class CIM_OSPFServiceConfiguration : CIM_Dependency { [Override ( "Antecedent" ), Min ( 1 ), Max ( 1 ), Description ( "The OSPF service." )] CIM_OSPFService REF Antecedent; [Override ( "Dependent" ), Description ( "The area configuration." )] CIM_OSPFAreaConfiguration REF Dependent; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |