This class is used to implement routing policies. It aggregates a set of FilterLists, along with other appropriate constructs, into a unit. One of the most important uses of this class is to change the routing policy by changing values of various attributes in a consistent manner. A RoutingPolicy is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class. Note that this class was defined before the Policy Model and hence is not positioned in that hierarchy. The class will be repositioned in a later release of the Network Model. | Qualifiers:Version ( "2.7.0" ) | Parameters (local in grey) | | Values { "Replace" , "Prepend" , "Append" } ModelCorrespondence { "CIM_RoutingPolicy.BGPAction" } ValueMap { "1" , "2" , "3" } uint16 AttributeAction ; This controls whether protocol-specific attributes replace, get prepended, or get appended to their existing values. | MaxLen ( 256 ) Override ( "Name" ) Key string Name ; This is the name of the Routing Policy. | Propagated ( "CIM_ComputerSystem.CreationClassName" ) MaxLen ( 256 ) Key string SystemCreationClassName ; The scoping ComputerSystem's CreationClassName. | Values { "Other" , "Input Flow Policing" , "Output Flow Policing" , "Input Aggregate Policing" , "Output Aggregate Policing" , "Police By Marking Down" , "Police By Dropping Down" } ModelCorrespondence { "CIM_RoutingPolicy.ConditioningValue" , "CIM_RoutingPolicy.OtherConditioningAction" } ValueMap { "1" , "2" , "3" , "4" , "5" , "6" , "7" } uint16 ConditioningAction ; This defines another action to be taken for this traffic. | Values { "Change DSCP" , "Change ToS" , "Change 802.1Q Value" , "Change CIR" , "Change CBR" , "Change ABR" , "Change VBR" } ModelCorrespondence { "CIM_RoutingPolicy.RemarkValue" } ValueMap { "1" , "2" , "3" , "4" , "5" , "6" , "7" } uint16 RemarkAction ; This defines a remarking action for this traffic. | ModelCorrespondence { "CIM_RoutingPolicy.ConditioningAction" } string ConditioningValue ; The value for the corresponding ConditioningAction, if appropriate. | ModelCorrespondence { "CIM_RoutingPolicy.ConditioningAction" } string OtherConditioningAction ; If the value of the ConditioningAction property of this class is 1, this contains an application-specific type of conditioning that is to be performed. Otherwise, if the ConditioningAction property is any other value, the value of this property should be NULL. | Propagated ( "CIM_ComputerSystem.Name" ) MaxLen ( 256 ) Key string SystemName ; The scoping ComputerSystem's Name. | ModelCorrespondence { "CIM_RoutingPolicy.BGPAction" } string BGPValue ; The value for the corresponding BGPAction. | ModelCorrespondence { "CIM_RoutingPolicy.RemarkAction" } string RemarkValue ; The value for the corresponding RemarkAction. | Values { "Accept As Is" , "Accept With Protocol Attribute Changes" , "Accept and Remark Packet" , "Accept With Protocol Attribute Changes and Remark" , "Accept With Other Action" , "Accept With Protocol Attribute Changes and Other Action" , "Accept with Remark and Other Action" , "Accept with Protocol Attribute Changes, " "Remark and Other Action" , "Deny" } ValueMap { "1" , "2" , "3" , "4" , "5" , "6" , "7" , "8" , "9" } uint16 Action ; This defines the type of action that will be performed if the match conditions of the policy are met. The match conditions are defined by the associated ListsIn RoutingPolicy. There are essentially three choices: forward the traffic unmodified, forward the traffic but modify either the attributes describing the route and/or other attributes that define how to condition the traffic (e.g., its ToS byte settings), or prevent the traffic from being forwarded. | Values { "Origin" , "AS_Path" , "NEXT_HOP" , "Multi_Exit_Disc" , "Local_Pref" , "Atomic_Aggregate" , "Aggregator" , "Community" , "Originator_ID" , "Cluster_List" } ModelCorrespondence { "CIM_RoutingPolicy.BGPValue" } ValueMap { "1" , "2" , "3" , "4" , "5" , "6" , "7" , "8" , "9" , "10" } uint16 BGPAction ; This defines one or more BGP-specific attributes that should be used to modify this routing update. | MaxLen ( 256 ) Key string CreationClassName ; CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | ModelCorrespondence { "CIM_ManagedSystemElement.OperationalStatus" } ArrayType ( "Indexed" ) string StatusDescriptions [ ] ; Strings describing the various OperationalStatus array values. For example, if 'Stopping' is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus. | Values { "Unknown" , "Other" , "OK" , "Degraded" , "Stressed" , "Predictive Failure" , "Error" , "Non-Recoverable Error" , "Starting" , "Stopping" , "Stopped" , "In Service" , "No Contact" , "Lost Communication" , "Aborted" , "Dormant" , "Supporting Entity in Error" , "Completed" , "Power Mode" , "DMTF Reserved" , "Vendor Reserved" } ModelCorrespondence { "CIM_ManagedSystemElement.StatusDescriptions" } ValueMap { "0" , "1" , "2" , "3" , "4" , "5" , "6" , "7" , "8" , "9" , "10" , "11" , "12" , "13" , "14" , "15" , "16" , "17" , "18" , ".." , "0x8000.." } ArrayType ( "Indexed" ) uint16 OperationalStatus [ ] ; Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. 'Stopped' and 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the element's state and configuration may need to be updated. 'Dormant' indicates that the element is inactive or quiesced. 'Supporting Entity in Error' describes that this element may be 'OK' but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. 'Completed' indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier since it required the DEPRECATED qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly RECOMMENDED that providers/instrumentation provide BOTH the Status and OperationalStatus properties. Further, the first value of OperationalStatus SHOULD contain the primary status for the element. When instrumented, Status (since it is single-valued) SHOULD also provide the primary status of the element. | MappingStrings { "MIF.DMTF|ComponentID|001.5" } datetime InstallDate ; A datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed. | MaxLen ( 10 ) Deprecated { "CIM_ManagedSystemElement.OperationalStatus" } ValueMap { "OK" , "Error" , "Degraded" , "Unknown" , "Pred Fail" , "Starting" , "Stopping" , "Service" , "Stressed" , "NonRecover" , "No Contact" , "Lost Comm" , "Stopped" } string Status ; A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This overcomes the limitation of describing status via a single value, when it is really a multi-valued property (for example, an element may be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. And, 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the Deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus. | MaxLen ( 64 ) string Caption ; The Caption property is a short textual description (one- line string) of the object. | string Description ; The Description property provides a textual description of the object. | string ElementName ; 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. |
| | | | |
|