Return to CIM_IngressConditioningServiceOnEndpoint.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_IngressConditioningServiceOnEndpoint.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_IngressConditioningServiceOnEndpoint // ================================================================== [Association, Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::QoS" ), Description ( "This association represents the binding, in the ingress " "direction, between a ProtocolEndpoint and the first " "ConditioningService that processes packets received via that " "Endpoint. Since there can only be one \'first\' " "ConditioningService for a ProtocolEndpoint, the cardinality " "for the Dependent object reference is narrowed from 0..n to " "0..1. On the other hand, a single ConditioningService can be " "the first to process packets received via multiple " "ProtocolEndpoints. So, the cardinality of the Antecedent " "object reference remains 0..n." )] class CIM_IngressConditioningServiceOnEndpoint : CIM_ServiceSAPDependency { [Override ( "Antecedent" ), Description ( "The ProtocolEndpoint through which traffic arrives at a " "network device." )] CIM_ProtocolEndpoint REF Antecedent; [Override ( "Dependent" ), Max ( 1 ), Description ( "The ConditioningService which begins the traffic " "conditioning processing within a network device." )] CIM_ConditioningService REF Dependent; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |