SNIA-SML-MIB: View SNMP OID List / Download MIB

This string contains version information for the MIB file

This string contains information about the CIM version that corresponds to the MIB. The decriptions in this MIB file are based on CIM version 2.8

Commonly used Product name.

Product identification such as a serial number on software, a die number on a hardware chip, or (for non-commercial Products) a project number.

The name of the Product's supplier, or entity selling the Product (the manufacturer, reseller, OEM, etc.). Corresponds to the Vendor property in the Product object in the DMTF Solution Exchange Standard.

Product version information. Corresponds to the Version property in the Product object in the DMTF Solution Exchange Standard.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

The name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.

The name by which the PhysicalElement is generally known.

A manufacturer-allocated number used to identify the Physical Element.

Boolean indicating whether the Frame is protected with a lock. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

SecurityBreach is an enumerated, integer-valued property indicating whether a physical breach of the Frame was attempted but unsuccessful (value=4) or attempted and successful (5). Also, the values, 'Unknown', 'Other' or 'No Breach', can be specified. Enumeration: 'unknown': 1, 'noBreach': 3, 'other': 2, 'breachAttempted': 4, 'breachSuccessful': 5.

Boolean indicating that the Frame is currently locked. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

An arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

This value specifies the number of sub Chassis that are present.

The SubChassis class represents the physical frames in the library

Each entry in the table contains information about a frame that is present in the library.

The current index value for the subChassis.

The name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.

The name by which the PhysicalElement is generally known.

A manufacturer-allocated number used to identify the Physical Element.

Boolean indicating whether the Frame is protected with a lock. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

SecurityBreach is an enumerated, integer-valued property indicating whether a physical breach of the Frame was attempted but unsuccessful (value=4) or attempted and successful (5). Also, the values, 'Unknown', 'Other' or 'No Breach', can be specified. Enumeration: 'unknown': 1, 'noBreach': 3, 'other': 2, 'breachAttempted': 4, 'breachSuccessful': 5.

Boolean indicating that the Frame is currently locked. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

An arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

Package type of the subChassis. The enumeration values for this variable should be the same as the DMTF CIM_Chassis.ChassisPackageType property. Use the Vendor reserved values for vendor-specific types. Enumeration: 'unknown': 0, 'serviceBay': 32769, 'subChassis': 19, 'expansionChassis': 18, 'mainSystemChassis': 17.

The inherited Name serves as key of a System instance in an enterprise environment.

The Description property provides a textual description of the object.

The Caption property is a short textual description (one- line string) of the object.

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 three reasons: 1) Status is more correctly defined as an array property. 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.

A datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.

This value specifies the number of MediaAccessDevices that are present.

A MediaAccessDevice represents the ability to access one or more media and use this media to store and retrieve data.

Each entry in the table contains information about a MediaAccessDevice that is present in the library.

The current index value for the MediaAccessDevice.

In the 2.7 CIM Schema a Type property is no longer associated with MediaAccessDevice. However, it can be used here to specify the type of drive that is present. Enumeration: 'wormDrive': 1, 'cdromDrive': 5, 'unknown': 0, 'dvdDrive': 4, 'tapeDrive': 3, 'magnetoOpticalDrive': 2.

Deprecated

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 three reasons: 1) Status is more correctly defined as an array property. 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.

Inherited from CIM_LogicalDevice The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 (Power Save - Unknown) indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 (Power Save - Low Power Mode) indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 (Power Save - Standby) describes that the Device is not functioning but could be brought to full power 'quickly'; and value 17 (Power Save - Warning) indicates that the Device is in a warning state, though also in a power save mode. Enumeration: 'powerSaveStandby': 15, 'paused': 18, 'installError': 12, 'notConfigured': 20, 'quiesced': 21, 'unknown': 2, 'powerSaveUnknown': 13, 'notInstalled': 11, 'offDuty': 9, 'inTest': 5, 'powerSaveWarning': 17, 'notApplicable': 6, 'powerOff': 7, 'other': 1, 'notReady': 19, 'runningFullPower': 3, 'offLine': 8, 'warning': 4, 'degraded': 10, 'powerSaveLowPowerMode': 14, 'powerCycle': 16.

Boolean indicating that the MediaAccessDevice needs cleaning. Whether manual or automatic cleaning is possible is indicated in the Capabilities array property. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

For a MediaAccessDevice that supports removable Media, the number of times that Media have been mounted for data transfer or to clean the Device. For Devices accessing nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.

An address or other identifying information to uniquely name the LogicalDevice.

The number of consecutive hours that this Device has been powered, since its last power cycle.

The total number of hours that this Device has been powered.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

The current index value for the storageMediaLocationIndex that this MediaAccessDevice is associated with. If no association exists an index of 0 may be returned.

The current index value for the softwareElementIndex that this MediaAccessDevice is associated with. If no association exists an index of 0 may be returned.

This value specifies the number of PhysicalPackages that are present.

The PhysicalPackage class represents PhysicalElements that contain or host other components. Examples are a Rack enclosure or an adapter Card. (also a tape magazine inside an auto-loader)

Each entry in the table contains information about a PhysicalPackage that is present in the library.

The current index value for the PhysicalPackage.

The name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.

The name by which the PhysicalElement is generally known.

A manufacturer-allocated number used to identify the Physical Element.

The index value of the the MediaAccess device that is associated with this physical package.'

An arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

This value specifies the number of SoftwareElements that are present.

The CIM_SoftwareElement class is used to decompose a CIM_SoftwareFeature object into a set of individually manageable or deployable parts for a particular platform. A software element's platform is uniquely identified by its underlying hardware architecture and operating system (for example Sun Solaris on Sun Sparc or Windows NT on Intel). As such, to understand the details of how the functionality of a particular software feature is provided on a particular platform, the CIM_SoftwareElement objects referenced by CIM_SoftwareFeatureSoftwareElement associations are organized in disjoint sets based on the TargetOperatingSystem property. A CIM_SoftwareElement object captures the management details of a part or component in one of four states characterized by the SoftwareElementState property.

Each entry in the table contains information about a SoftwareElement that is present in the library.

The current index value for the SoftwareElement.

deprecated

Version should be in the form .. or .

SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may be acquired, SoftwareIdentity can be associated with a Product using the ProductSoftwareComponent relationship. Note that the Application Model manages the deployment and installation of software via the classes, SoftwareFeatures and SoftwareElements. The deployment/installation concepts are related to the asset/identity one. In fact, a SoftwareIdentity may correspond to a Product, or to one or more SoftwareFeatures or SoftwareElements - depending on the granularity of these classes and the deployment model. The correspondence of Software Identity to Product, SoftwareFeature or SoftwareElement is indicated using the ConcreteIdentity association. Note that there may not be sufficient detail or instrumentation to instantiate ConcreteIdentity. And, if the association is instantiated, some duplication of information may result. For example, the Vendor described in the instances of Product and SoftwareIdentity MAY be the same. However, this is not necessarily true, and it is why vendor and similar information are duplicated in this class. Note that ConcreteIdentity can also be used to describe the relationship of the software to any LogicalFiles that result from installing it. As above, there may not be sufficient detail or instrumentation to instantiate this association.

Manufacturer of this software element

The internal identifier for this compilation of this software element.

The assigned serial number of this software element.

The code set used by this software element.

The value of this property is the manufacturer's identifier for this software element. Often this will be a stock keeping unit (SKU) or a part number.

The value of this property identifies the language edition of this software element. The language codes defined in ISO 639 should be used. Where the software element represents multi-lingual or international version of a product, the string multilingual should be used.

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm: : Where and are separated by a colon ':', and where MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between and . is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace. For DMTF defined instances, the 'preferred' algorithm MUST be used with the set to 'CIM'.

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. \n Note that ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.

The ComputerSystem object and its derivatives are Top Level Objects of CIM. They provide the scope for numerous components. Having unique System keys is required. The NameFormat property identifies how the ComputerSystem Name is generated. The NameFormat ValueMap qualifier defines the various mechanisms for assigning the name. Note that another name can be assigned and used for the ComputerSystem that better suit a business, using the inherited ElementName property. Possible values include 'Other', 'IP', 'Dial', 'HID', 'NWA', 'HWA', 'X25', 'ISDN', 'IPX', 'DCC', 'ICD', 'E.164', 'SNA', 'OID/OSI', 'WWN', 'NAA'

Enumeration indicating whether the ComputerSystem is a special-purpose System (ie, dedicated to a particular use), versus being 'general purpose'. For example, one could specify that the System is dedicated to 'Print' (value=11) or acts as a 'Hub' (value=8). \n A clarification is needed with respect to the value 17 ('Mobile User Device'). An example of a dedicated user device is a mobile phone or a barcode scanner in a store that communicates via radio frequency. These systems are quite limited in functionality and programmability, and are not considered 'general purpose' computing platforms. Alternately, an example of a mobile system that is 'general purpose' (i.e., is NOT dedicated) is a hand-held computer. Although limited in its programmability, new software can be downloaded and its functionality expanded by the user. Enumeration: 'fileServer': 16, 'layer3switch': 6, 'management': 14, 'repeater': 18, 'hub': 8, 'centralOfficeSwitch': 7, 'unknown': 1, 'bridgeExtender': 19, 'mobileUserDevice': 17, 'storage': 3, 'notDedicated': 0, 'gateway': 20, 'firewall': 10, 'switch': 5, 'other': 2, 'io': 12, 'webCaching': 13, 'print': 11, 'router': 4, 'accessServer': 9, 'blockServer': 15.

A string that provides information on how the primary system owner can be reached (e.g. phone number, email address, ...)

The name of the primary system owner. The system owner is the primary user of the system.

The Description property provides a textual description of the object.

The Caption property is a short textual description (one- line string) of the object.

The current index value for the softwareElementIndex that this computerSystem is associated with. If no association exists an index of 0 may be returned.

This value specifies the number of ChangerDevices that are present.

The changerDevice class represents changerDevices in the library

Each entry in the table contains information about a changerDevice that is present in the library.

The current index value for the changerDevice.

An address or other identifying information to uniquely name the LogicalDevice.

Boolean set to TRUE if the Changer supports media flipping. Media needs to be flipped when multi-sided PhysicalMedia are placed into a MediaAccessDevice that does NOT support dual sided access. Enumeration: 'false': 2, 'true': 1.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

The Caption property is a short textual description (one- line string) of the object.

The Description property provides a textual description of the object.

The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows Value 13 (\'Power Save - Unknown\') indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 (\'Power Save - Low Power Mode\') indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance 15 (\'Power Save - Standby\') describes that the Device is not functioning but could be brought to full power 'quickly'; and value 17 (\'Power Save - Warning\') indicates that the Device is in a warning state, though also in a power save mode. Enumeration: 'powerSaveStandby': 15, 'paused': 18, 'installError': 12, 'notConfigured': 20, 'quiesced': 21, 'unknown': 2, 'powerSaveUnknown': 13, 'notInstalled': 11, 'offDuty': 9, 'inTest': 5, 'powerSaveWarning': 17, 'notApplicable': 6, 'powerOff': 7, 'other': 1, 'notReady': 19, 'runningFullPower': 3, 'offLine': 8, 'warning': 4, 'degraded': 10, 'powerSaveLowPowerMode': 14, 'powerCycle': 16.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

The current index value for the storageMediaLocationIndex that this changerDevice is associated with. If no association exists an index of 0 may be returned.

This value specifies the number of SCSIProtocolControllers that are present.

The scsiProtocolController class represents SCSIProtocolControllers in the library

Each entry in the table contains information about a SCSIProtocolController that is present in the library.

The current index value for the scsiProtocolController.

An address or other identifying information to uniquely name the LogicalDevice.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

The Description property provides a textual description of the object.

The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 (\'Power Save - Unknown\') indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 (\'Power Save - Low Power Mode\') indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 (\'Power Save - Standby\') describes that the Device is not functioning but could be brought to full power 'quickly'; and value 17 (\'Power Save - Warning\') indicates that the Device is in a warning state, though also in a power save mode. Enumeration: 'powerSaveStandby': 15, 'paused': 18, 'installError': 12, 'notConfigured': 20, 'quiesced': 21, 'unknown': 2, 'powerSaveUnknown': 13, 'notInstalled': 11, 'offDuty': 9, 'inTest': 5, 'powerSaveWarning': 17, 'notApplicable': 6, 'powerOff': 7, 'other': 1, 'notReady': 19, 'runningFullPower': 3, 'offLine': 8, 'warning': 4, 'degraded': 10, 'powerSaveLowPowerMode': 14, 'powerCycle': 16.

The current index value for the ChangerDeviceIndex that this scsiProtocolController is associated with. If no association exists an index of 0 may be returned.

The current index value for the MediaAccessDeviceIndex that this scsiProtocolController is associated with. If no association exists an index of 0 may be returned.

This value specifies the number of StorageMediaLocations that are present.

This value specifies the number of PhysicalMedia that are present.

StorageMediaLocation represents a possible location for an instance of PhysicalMedia. PhysicalMedia represents any type of documentation or storage medium, such as tapes, CDROMs, etc. This class is typically used to locate and manage Removable Media (versus Media sealed with the MediaAccessDevice, as a single Package, as is the case with hard disks). However, 'sealed' Media can also be modeled using this class, where the Media would then be associated with the PhysicalPackage using the PackagedComponent relationship.

Each entry in the table contains information about a StorageMediaLocation that is present in the library.

The current index value for the StorageMediaLocation.

An arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

The type of Location. For example, whether this is an individual Media \'Slot\' (value=2), a MediaAccessDevice (value=4) or a \'Magazine\' (value=3) is indicated in this property. Enumeration: 'slot': 2, 'limitedAccessPort': 6, 'unknown': 0, 'mediaAccessDevice': 4, 'magazine': 3, 'other': 1, 'shelf': 8, 'door': 7, 'interLibraryPort': 5, 'vault': 9.

LocationCoordinates represent the physical location of the the FrameSlot instance. The property is defined as a free-form string to allow the location information to be described in vendor-unique terminology.

Certain StorageMediaLocations may only be able to accept a limited set of PhysicalMedia MediaTypes. This property defines an array containing the types of Media that are acceptable for placement in the Location. Additional information and description of the contained MediaTypes can be provided using the TypesDescription array. Also, size data (for example, DVD disc diameter) can be specified using the MediaSizesSupported array. \n \n Values defined here correspond to those in the CIM_Physical Media.MediaType property. This allows quick comparisons using value equivalence calculations. It is understood that there is no external physical difference between (for example) DVD- Video and DVD-RAM. But, equivalent values in both the Physical Media and StorageMediaLocation enumerations allows for one for one comparisons with no additional processing logic (i.e., the following is not required ... if \'DVD-Video\' then value=\'DVD\'). Enumeration: 'dvdRecordable': 36, 'ablativeWriteOnce': 49, 'dvd9': 40, 'dvdRAM': 24, 'dstSmall': 64, 'dvdVideo': 26, 'cdDA': 34, 'cdRW': 33, 'wORM': 20, 'qic': 3, 'memoryCard': 30, 'tape18Track': 59, 'dvd10': 41, 'dvd': 22, 'dvdRW': 37, 'magstarMP': 62, 'eightmmTape': 7, 'clikDisk': 32, 'nearField': 50, 'travan': 52, 'miniQic': 51, 'eightmmAdvanced': 54, 'tape36Track': 60, 'unknown': 0, 'dvdROM': 25, 'phaseChangeDualRewriteable': 48, 'hardDisk': 29, 'cdI': 18, 'dvdAudio': 38, 'magstar3590': 61, 'other': 1, 'tape': 2, 'dstMedium': 65, 'dlt': 9, 'eightmmMetal': 53, 'moLIMDOW': 45, 'dstLarge': 66, 'winchesterDisk': 15, 'tape9Track': 58, 'cdRecordable': 19, 'cdRomXA': 17, 'zipDisk': 13, 'moRewriteable': 43, 'dat': 6, 'divx': 27, 'nineteenmmTape': 8, 'nctp': 55, 'dvd5': 39, 'ltoAccelis': 57, 'ltoUltrium': 56, 'dvd18': 42, 'syQuestDisk': 14, 'halfInchMO': 10, 'dvdRWPlus': 23, 'hardCopy': 31, 'dtf': 5, 'catridgeDisk': 11, 'moWriteOnce': 44, 'd2Tape': 63, 'floppyDiskette': 28, 'ait': 4, 'cdRom': 16, 'phaseChangeRewriteable': 47, 'jazDisk': 12, 'magneto-Optical': 21, 'phaseChangeWO': 46, 'cdPlus': 35.

A StorageMediaLocation may hold more than one PhysicalMedia - for example, a Magazine. This property indicates the Physical Media capacity of the Location.

Experimental: The current index value for the ChangerDeviceIndex that this storageMediaLocation is associated with. If no association exists an index of 0 may be returned. This association allows a representation of the experimental

'true' when Physical Media is present in this storage location. When this is 'false' -physicalMedia- entries are undefined Enumeration: 'false': 2, 'true': 1.

A PhysicalComponent is Removable if it is designed to be taken in and out of the physical container in which it is normally found, without impairing the function of the overall packaging. A Component can still be Removable if power must be 'off' in order to perform the removal. If power can be 'on' and the Component removed, then the Element is both Removable and HotSwappable. For example, an upgradeable Processor chip is Removable. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

A PhysicalComponent is Replaceable if it is possible to replace (FRU or upgrade) the Element with a physically different one. For example, some ComputerSystems allow the main Processor chip to be upgraded to one of a higher clock rating. In this case, the Processor is said to be Replaceable. All Removable Components are inherently Replaceable. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

A PhysicalComponent is HotSwappable if it is possible to replace the Element with a physically different but equivalent one while the containing Package has power applied to it (ie, is 'on'). For example, a fan Component may be designed to be HotSwappable. All HotSwappable Components are inherently Removable and Replaceable. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

The number of bytes that can be read from or written to a Media. This property is not applicable to 'Hard Copy' (documentation) or cleaner Media. Data compression should not be assumed, as it would increase the value in this property. For tapes, it should be assumed that no filemarks or blank space areas are recorded on the Media.

Specifies the type of the PhysicalMedia, as an enumerated integer. The MediaDescription property is used to provide more explicit definition of the Media type, whether it is pre-formatted, compatability features, etc. Enumeration: 'dvdRecordable': 36, 'ablativeWriteOnce': 49, 'dvd9': 40, 'dvdRAM': 24, 'dstSmall': 64, 'dvdVideo': 26, 'cdDA': 34, 'cdRW': 33, 'wORM': 20, 'qic': 3, 'memoryCard': 30, 'tape18Track': 59, 'dvd10': 41, 'dvd': 22, 'dvdRW': 37, 'magstarMP': 62, 'eightmmTape': 7, 'clikDisk': 32, 'nearField': 50, 'travan': 52, 'miniQic': 51, 'eightmmAdvanced': 54, 'tape36Track': 60, 'unknown': 0, 'dvdROM': 25, 'phaseChangeDualRewriteable': 48, 'hardDisk': 29, 'cdI': 18, 'dvdAudio': 38, 'magstar3590': 61, 'other': 1, 'tape': 2, 'dstMedium': 65, 'dlt': 9, 'eightmmMetal': 53, 'moLIMDOW': 45, 'dstLarge': 66, 'winchesterDisk': 15, 'tape9Track': 58, 'cdRecordable': 19, 'cdRomXA': 17, 'zipDisk': 13, 'moRewriteable': 43, 'dat': 6, 'divx': 27, 'nineteenmmTape': 8, 'nctp': 55, 'dvd5': 39, 'ltoAccelis': 57, 'ltoUltrium': 56, 'dvd18': 42, 'syQuestDisk': 14, 'halfInchMO': 10, 'dvdRWPlus': 23, 'hardCopy': 31, 'dtf': 5, 'catridgeDisk': 11, 'moWriteOnce': 44, 'd2Tape': 63, 'floppyDiskette': 28, 'ait': 4, 'cdRom': 16, 'phaseChangeRewriteable': 47, 'jazDisk': 12, 'magneto-Optical': 21, 'phaseChangeWO': 46, 'cdPlus': 35.

Additional detail related to the MediaType enumeration. For example, if value 3 ('QIC Cartridge') is specified, this property could indicate whether the tape is wide or 1/4 inch, whether it is pre-formatted, whether it is Travan compatible, etc.

Boolean indicating that the PhysicalMedia is used for cleaning purposes and not data storage. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

Boolean indicating that the Media has two recording sides (TRUE) or only a single side (FALSE). Examples of dual sided Media include DVD-ROM and some optical disks. Examples of single sided Media are tapes and CD-ROM. Enumeration: 'unknown': 0, 'false': 2, 'true': 1.

One or more strings on 'labels' on the PhysicalMedia. The format of the labels and their state (readable, unreadable, upside-down) are indicated in the LabelFormats and LabelStates array properties.

An arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial data. The key for PhysicalElement is placed very high in number the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.

This value specifies the number of limitedAccessPorts that are present.

The limitedAccessPort class represents limitedAccessPorts in the library

Each entry in the table contains information about a limitedAccessPort that is present in the library.

The current index value for the limitedAccessPort.

An address or other identifying information to uniquely name the LogicalDevice.

When a Port is 'Extended' or 'open' (value=TRUE), its Storage MediaLocations are accessible to a human operator. If not extended (value=FALSE), the Locations are accessible to a PickerElement. Enumeration: 'false': 2, 'true': 1.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

The Caption property is a short textual description (one- line string) of the object.

The Description property provides a textual description of the object.

The current index value for the storageMediaLocationIndex that this limitedAccessPort is associated with. If no association exists an index of 0 may be returned.

This value specifies the number of fcPorts that are present.

The fcPort class represents Fibre Channel Ports in the library

Each entry in the table contains information about an fcPort that is present in the library.

The current index value for the fCPort.

An address or other identifying information to uniquely name the LogicalDevice.

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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties.

The Caption property is a short textual description (one- line string) of the object.

The Description property provides a textual description of the object.

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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. SMI-S 1.1 Section 8.1.2.2.3 additional description for FC Ports OK - Port is online Error - Port has a failure Stopped - Port is disabled InService - Port is in Self Test Unknown Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

PermanentAddress defines the network address hardcoded into a port. This 'hardcoded' address may be changed via firmware upgrade or software configuration. If so, this field should be updated when the change is made. PermanentAddress should be left blank if no 'hardcoded' address exists for the NetworkAdapter. In SMI-S 1.1 table 1304 FCPorts are defined to use the port WWN as described in table 7.2.4.5.2 World Wide Name (i.e. FC Name_Identifier) FCPort Permanent Address property; no corresponding format property 16 un-separated upper case hex digits (e.g. '21000020372D3C73')

The current index value for the scsiProtocolControllerIndex that this fCPort is associated with. If no association exists an index of 0 may be returned.

Set to enable sending traps Enumeration: 'disabled': 2, 'enabled': 1.

Short summary of a media (tape, optical, etc.) driveAlert trap. Corresponds to the Number/Flag property of drive/autoloader alerts in the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) as modified by the EventSummary property in the SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications for Library Devices. In particular, all occurances of 'tape' have been replaced with 'media'. (This summary property has a 1 to 1 relationship to the CIM_AlertIndication.OtherAlertType property, and might be stored in the CIM_AlertIndication.Message property.) Enumeration: 'hardwareA': 30, 'cleanNow': 20, 'hardwareB': 31, 'mediaDirectoryInvalidAtUnload': 51, 'unrecoverableSnappedTape': 14, 'wormMediumIntegrityCheckFailed': 59, 'diagnosticsRequired': 39, 'driveTemperature': 36, 'powerSupplyFailure': 27, 'expiredCleaningMedia': 22, 'unsupportedFormat': 12, 'wormMediumOverwriteAttempted': 60, 'invalidCleaningMedia': 23, 'writeFailure': 6, 'writeProtect': 9, 'automationInterfaceFailure': 57, 'media': 4, 'unrecoverableUnloadFailure': 56, 'readOnlyFormat': 17, 'mediaLife': 7, 'forcedEject': 16, 'hardError': 3, 'writeWarning': 2, 'directoryCorruptedOnLoad': 18, 'cleaningMedia': 11, 'firmwareFailure': 58, 'nearingMediaLife': 19, 'lostStatistics': 50, 'powerConsumption': 28, 'noStartOfData': 54, 'driveVoltage': 37, 'recoverableSnappedTape': 13, 'ejectMedia': 33, 'interface': 32, 'notDataGrade': 8, 'cleanPeriodic': 21, 'readFailure': 5, 'mediaSystemAreaWriteFailure': 52, 'mediaSystemAreaReadFailure': 53, 'retentionRequested': 24, 'downloadFailure': 34, 'noRemoval': 10, 'coolingFanError': 26, 'dualPortInterfaceError': 25, 'driveHumidity': 35, 'readWarning': 1, 'driveMaintenance': 29, 'predictiveFailure': 38, 'loadingFailure': 55, 'memoryChipInCartridgeFailure': 15.

The current index value for the MediaAccessDeviceIndex that this changerAlert trap is associated with. If no association exists an index of 0 may be returned.

Short summary of a changer (eg. robot) changerAlert trap. Corresponds to the Number/Flag property of stand-alone changer alerts in the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) as modified by the EventSummary property in the SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications for Library Devices. In particular, all occurances of 'tape' have been replaced with 'media'. (This summary property has a 1 to 1 relationship to the CIM_AlertIndication.OtherAlertType property, and might be stored in the CIM_AlertIndication.Message property.) Enumeration: 'passThroughMechanismFailure': 30, 'libraryDoor': 16, 'libraryOffline': 21, 'libraryHardwareC': 3, 'libraryHardwareB': 2, 'libraryHardwareA': 1, 'unreadableBarCodeLabels': 32, 'libraryHardwareD': 4, 'cartridgeInPassThroughMechanism': 31, 'libraryInterface': 6, 'libraryHumidityLimits': 9, 'libraryInventory': 24, 'libraryVoltageLimits': 11, 'libraryPickRetry': 13, 'libraryTemperatureLimits': 10, 'coolingFanFailure': 27, 'libraryStrayMedia': 12, 'libraryLoadRetry': 15, 'failurePrediction': 7, 'libraryScanRetry': 23, 'libraryIllegalOperation': 25, 'powerConsumption': 29, 'libraryMaintenance': 8, 'dualPortInterfaceError': 26, 'libraryMailslot': 17, 'powerSupply': 28, 'libraryDiagnosticsRequired': 5, 'librarySecurity': 19, 'libraryPlaceRetry': 14, 'libraryDriveOffline': 22, 'libraryMagazine': 18, 'librarySecurityMode': 20.

The current index value for the ChangerDeviceIndex that this changerAlert trap is associated with. If no association exists an index of 0 may be returned.

An enumerated value that describes the severity of the Alert Indication from the notifier's point of view: 1 - Other, by CIM convention, is used to indicate that the Severity's value can be found in the OtherSeverity property. 3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 - Major should be used to indicate action is needed NOW. 6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it's too late to take remedial action. 2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the AlertIndication is purely informational or its severity is simply unknown. This would have values described in SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications for Library Devices, the PerceivedSeverity column. These values are a superset of the Info/Warning/Critical values in the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) , and an SNMP agent may choose to only specify those if that's all that's available. (This corresponds to the CIM_AlertIndication.PerceivedSeverity property.) Enumeration: 'information': 2, 'major': 5, 'unknown': 0, 'fatalNonRecoverable': 7, 'degradedWarning': 3, 'other': 1, 'critical': 6, 'minor': 4.

Table of client/manager desitinations which will receive traps

Entry containing information needed to send traps to an SNMP client/manager

This value specifies the number of trap destination SNMP clients/managers.

The type of addressing model to represent the network address (IPv4/IPv6) Enumeration: 'iPv4': 1, 'iPv6': 2.

The network address of this client/manager, to which the trap should be sent

The port number where this client/manager is listening for traps.

Indicates the previous 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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

Indicates the previous 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. \n 'Stressed' indicates that the element is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, etc. \n 'Predictive Failure' indicates that an element is functioning nominally but predicting a failure in the near future. \n 'In Service' describes an element being configured, maintained, cleaned, or otherwise administered. \n 'No Contact' indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. \n 'Lost Communication' indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. \n '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. \n 'Dormant' indicates that the element is inactive or quiesced. \n '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. \n '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. \n 'Power Mode' indicates the element has additional power model information contained in the Associated PowerManagementService association. \n 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. Enumeration: 'lostCommunication': 13, 'dormant': 15, 'powerMode': 18, 'ok': 2, 'aborted': 14, 'unknown': 0, 'noContact': 12, 'error': 6, 'dMTFReserved': 19, 'vendorReserved': 32768, 'stopping': 9, 'other': 1, 'stopped': 10, 'predictiveFailure': 5, 'stressed': 4, 'non-RecoverableError': 7, 'degraded': 3, 'supportingEntityInError': 16, 'starting': 8, 'completed': 17, 'inService': 11.

Description here

A library is added to the SMI-S agent. This trap is to support the SMI-S 1.1 section 8.1.8.23 InstCreation indication.

A library is deleted in the SMI-S agent. This trap is to support the SMI-S 1.1 section 8.1.8.23 InstDeletion indication.

A library OperationalStatus has changed in the SMI-S agent. This trap is to support the SMI-S 1.1 section 8.1.8.23 InstModification indication.

A media access device (trap drive) is added to the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstCreation indication.

A media access device (trap drive) is deleted from the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstDeletion indication.

A drive OperationalStatus has changed in the SMI-S agent. This trap is to support the SMI-S 1.1 section 8.1.8.23 InstModification indication.

A changer device is added to the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstCreation indication.

A changer device is deleted from the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstDeletion indication.

A changer OperationalStatus has changed in the SMI-S agent. This trap is to support the SMI-S 1.1 section 8.1.8.23 InstModification indication.

A physical media is added to the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstCreation indication.

A physical media is deleted from the library. This trap is to support the SMI-S 1.1 section 8.1.8.25 InstDeletion indication.

A Drive/Autoloader Alert trap, based on the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) and SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications.

A Changer Device (eg. robot) Alert trap, based on the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) and SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications.