![]() ![]() |
![]() |
File: [Pegasus] / pegasus / Schemas / CIM225 / DMTF / Network / CIM_PreambleFilter.mof
(download)
Revision: 1.1, Tue Jun 15 08:21:03 2010 UTC (14 years ago) by s.kodali Branch: MAIN CVS Tags: preBug9676, postBug9676, TASK_PEP317_1JUNE_2013, 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-root, TASK-PEP317_pullop-merged_out_to_branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, TASK-PEP317_pullop-merged_in_from_branch, TASK-PEP317_pullop-branch, 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, RELEASE_2_11_2-RC1, RELEASE_2_11_2, RELEASE_2_11_1-RC1, RELEASE_2_11_1, RELEASE_2_11_0-RC1, RELEASE_2_11_0-FC, RELEASE_2_11_0, RELEASE_2_11-root, RELEASE_2_11-branch, PREAUG25UPDATE, POSTAUG25UPDATE, HEAD, CIMRS_WORK_20130824, BeforeUpdateToHeadOct82011 BUG#: 8782 TITLE: Add Schema 225 to the cvs |
// Copyright (c) 2005 DMTF. All rights reserved. // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath // qualifier values to CIM Schema.</change> // ================================================================== // CIM_PreambleFilter // ================================================================== [Version ( "2.7.0" ), UMLPackagePath ( "CIM::Network::Filtering" ), Description ( "PreambleFilter allows the classification of packets using " "traffic-conditioning results (where the results are determined " "by a PreambleMarkerService and stored in a \'packet " "preamble\'). This permits information about the treatment that " "a packet receives on an ingress interface to be communicated " "along with the packet to the egress interface. An instance of " "PreambleFilter selects packets based on a two-part string " "(type and value pair) identifying a specific entry in the " "preamble. The logic for this match is \'at least one.\' That " "is, a packet with multiple entries/results in its preamble " "matches a filter if at least one of these matches the filter." )] class CIM_PreambleFilter : CIM_FilterEntryBase { [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" "\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 |