![]() ![]() |
![]() |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Device / CIM_ProtocolControllerForDevice.mof
(download)
Revision: 1.1, Tue Jan 24 13:50:08 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_ProtocolControllerForDevice // ================================================================== [Association, Abstract, Version ( "2.8.1000" ), UMLPackagePath ( "CIM::Device::ProtocolController" ), Description ( "This association indicates a subclass of LogicalDevice (for " "example a Storage Volume) is connected through a specific " "ProtocolController. In many situations (for example storage " "LUN masking), there may be many of these associations used to " "relate to different objects. Therefore subclasses have been " "defined to optimize enumeration of the associations." )] class CIM_ProtocolControllerForDevice : CIM_Dependency { [Override ( "Antecedent" ), Description ( "The ProtocolController." )] CIM_ProtocolController REF Antecedent; [Override ( "Dependent" ), Description ( "The controlled Device." )] CIM_LogicalDevice REF Dependent; [Description ( "Address of the associated Device in the context of the " "Antecedent Controller." )] string DeviceNumber; [Description ( "This property describes the priority given to accesses " "of the device through this Controller. The highest " "priority path will have the lowest value for this " "parameter." )] uint16 AccessPriority; [Description ( "The AccessState property describes the accessibility of " "the LogicalDevice through the ProtocolController. \n" "Unknown (0) indicates the instrumentation does not know " "whether access is or is not functioning. \n" "Active (2) indicates normal access. \n" "Inactive (3) indicates the instrumentation knows this " "path is not active, and one of the other values (below) " "does not apply. \n" "Replication in Progress (4) indicates that the path is " "temporarily inactive due to a replication activity. \n" "Mapping Inconsistency (5) indicates the instrumentation " "has detected that this path is inactive due to an " "inconsistency in the DeviceNumber/DeviceAccess " "configuration." ), ValueMap { "0", "2", "3", "4", "5" }, Values { "Unknown", "Active", "Inactive", "Replication In Progress", "Mapping Inconsistency" }] uint16 AccessState; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |