(file) Return to CIM_PreambleMarkerService.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network / CIM_PreambleMarkerService.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_PreambleMarkerService 
// ==================================================================
   [Version ( "2.7.0" ), 
    UMLPackagePath ( "CIM::Network::QoS" ), 
    Description ( 
       "PreambleMarkerService models the storing of traffic- "
       "conditioning results in a packet preamble. An instance appends "
       "a two-part string of the form \'<type>,<value>\' to the packet "
       "preamble. The concept of \'type\'s is discussed more fully in "
       "the Description of the class\' FilterItemList property." )]
class CIM_PreambleMarkerService : CIM_MarkerService {

      [Description ( 
          "To foster interoperability, the basic format of the "
          "information captured by a PreambleMarker is specified. "
          "That information is contained in the FilterItemList "
          "property (an ordered, string array). Each entry in the "
          "array takes the form \'type,value\'. When entries are "
          "added, they are appended to the end of the list. \n"
          "\n"
          "A limited set of standardized \'type\'s exist. They are: \n"
          "- ConformingFromMeter, NonConformingFromMeter and "
          "PartConformingFromMeter to convey metering results "
          "(where the \'value\' is the name of the meter) \n"
          "- VlanId to describe the traffic\'s VLAN information "
          "(where the \'value\' is the VLAN ID). \n"
          "An implementation is free to define and use other "
          "preamble \'types\'. \n"
          "Note that a wildcard value of \"any\" is allowed to "
          "indicate that the preamble entry matches for any \'value\' "
          "of the specified \'type\'. For example, using the "
          "wildcard, an administrator can define a filter to select "
          "all packets that were found to be conforming (\'type\' = "
          "\"ConformingFromMeter\") without having to name each "
          "meter individually." ), 
       ArrayType ( "Ordered" )]
   string FilterItemList[];


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2