Home/Catalog/SML-MIB

SML-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for SML-MIB.

77
Objects
Active
Status
3
Dependencies

Imported Objects

Objects

77 total
Object Name
ibm
OBJECT IDENTIFIER
.1.3.6.1.4.1.2
IMPORTS
Unknown
.1.3.6.1.4.1.2
ibmProd
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6
ibm3584
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182
smlRoot
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3
smlMibVersionThis string contains version information for the MIB filero
DisplayString
.1.3.6.1.4.1.2.6.182.3.1
smlCimVersionThis string contains information about the CIM version that corresponds to the MIB. The decriptions in this MIB file are based on CIM version 2.7, as documented by Steve Jerman for HP.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.2
productGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.3
product-NameCommonly used Product name.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.3.1
product-IdentifyingNumberProduct identification such as a serial number on software, a die number on a hardware chip, or (for non-commercial Products) a project number.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.3.2
product-VendorThe 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.3.3
product-VersionProduct version information. Corresponds to the Version property in the Product object in the DMTF Solution Exchange Standard.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.3.4
chassisGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.4
chassis-ManufacturerThe 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.4.1
chassis-ModelThe name by which the PhysicalElement is generally known.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.4.2
chassis-SerialNumberA manufacturer-allocated number used to identify the Physical Element.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.4.3
chassis-LockPresentBoolean indicating whether the Frame is protected with a lock.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.4.4
chassis-SecurityBreachSecurityBreach 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.4.5
chassis-IsLockedBoolean indicating that the Frame is currently locked.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.4.6
storageLibraryGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.5
storageLibrary-NameThe inherited Name serves as key of a System instance in an enterprise environment.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.5.1
storageLibrary-DescriptionThe Description property provides a textual description of the object.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.5.2
storageLibrary-CaptionThe Caption property is a short textual description (one- line string) of the object.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.5.3
storageLibrary-StatusA 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.5.4
storageLibrary-InstallDateA datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.ro
CimDateTime
.1.3.6.1.4.1.2.6.182.3.5.5
mediaAccessDeviceGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.6
numberOfMediaAccessDevicesThis value specifies the number of MediaAccessDevices that are present.ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.6.1
mediaAccessDeviceTableA MediaAccessDevice represents the ability to access one or more media and use this media to store and retrieve data.
SEQUENCE OF TableInfo-1
.1.3.6.1.4.1.2.6.182.3.6.2
mediaAccessDeviceEntryEach entry in the table contains information about a MediaAccessDevice that is present in the library.
TableInfo-1
.1.3.6.1.4.1.2.6.182.3.6.2.1
mediaAccessDeviceIndexThe current index value for the MediaAccessDevice.ro
UINT32
.1.3.6.1.4.1.2.6.182.3.6.2.1.1
mediaAccessDeviceObjectTypeIn 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.6.2.1.2
mediaAccessDevice-NameThe Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.6.2.1.3
mediaAccessDevice-StatusA 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.6.2.1.4
mediaAccessDevice-AvailabilityThe primary availability and status of the Device. (Additional status information can be specified using the AdditionalAvailability 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.6.2.1.5
mediaAccessDevice-NeedsCleaningBoolean indicating that the MediaAccessDevice needs cleaning. Whether manual or automatic cleaning is possible is indicated in the Capabilities array property.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.6.2.1.6
physicalMediaGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.7
numberOfPhysicalMediasThis value specifies the number of PhysicalMedia that are present.ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.7.1
physicalMediaTableThe PhysicalMedia class 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.
SEQUENCE OF TableInfo-2
.1.3.6.1.4.1.2.6.182.3.7.2
physicalMediaEntryEach entry in the table contains information about a PhysicalMedia that is present in the library.
TableInfo-2
.1.3.6.1.4.1.2.6.182.3.7.2.1
physicalMediaIndexThe current index value for the PhysicalMedia.ro
UINT32
.1.3.6.1.4.1.2.6.182.3.7.2.1.1
physicalMediaObjectTypeIn the 2.7 CIM Schema a Type property is no longer associated with physicalMedia. The MediaType property provides more detailed information.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.2
physicalMedia-RemovableA 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.3
physicalMedia-ReplaceableA 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.4
physicalMedia-HotSwappableA 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.5
physicalMedia-CapacityThe 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.ro
UINT64
.1.3.6.1.4.1.2.6.182.3.7.2.1.6
physicalMedia-MediaTypeSpecifies 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.7
physicalMedia-MediaDescriptionAdditional 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.7.2.1.8
physicalMedia-CleanerMediaBoolean indicating that the PhysicalMedia is used for cleaning purposes and not data storage.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.9
physicalMedia-DualSidedBoolean 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.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.7.2.1.10
physicalMedia-PhysicalLabelOne 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.7.2.1.11
physicalPackageGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.8
numberOfPhysicalPackagesThis value specifies the number of PhysicalPackages that are present.ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.8.1
physicalPackageTableThe 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)
SEQUENCE OF TableInfo-3
.1.3.6.1.4.1.2.6.182.3.8.2
physicalPackageEntryEach entry in the table contains information about a PhysicalPackage that is present in the library.
TableInfo-3
.1.3.6.1.4.1.2.6.182.3.8.2.1
physicalPackageIndexThe current index value for the PhysicalPackage.ro
UINT32
.1.3.6.1.4.1.2.6.182.3.8.2.1.1
physicalPackage-ManufacturerThe 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.8.2.1.2
physicalPackage-ModelThe name by which the PhysicalElement is generally known.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.8.2.1.3
physicalPackage-SerialNumberA manufacturer-allocated number used to identify the Physical Element.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.8.2.1.4
physicalPackage-Realizes-MediaAccessDeviceIndexThe index value of the the MediaAccess device that is associated with this physical package.'ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.8.2.1.5
softwareElementGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.9
numberOfSoftwareElementsThis value specifies the number of SoftwareElements that are present.ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.9.1
softwareElementTableThe 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.
SEQUENCE OF TableInfo-4
.1.3.6.1.4.1.2.6.182.3.9.2
softwareElementEntryEach entry in the table contains information about a SoftwareElement that is present in the library.
TableInfo-4
.1.3.6.1.4.1.2.6.182.3.9.2.1
softwareElementIndexThe current index value for the SoftwareElement.ro
UINT32
.1.3.6.1.4.1.2.6.182.3.9.2.1.1
softwareElement-NameThe name used to identify this software elementro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.2
softwareElement-VersionVersion should be in the form .. or .ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.3
softwareElement-SoftwareElementIDThis is an identifier for this software element and is designed to be used in conjunction with other keys to create a unique representation of this SoftwareElementro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.4
softwareElement-ManufacturerManufacturer of this software elementro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.5
softwareElement-BuildNumberThe internal identifier for this compilation of this software element.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.6
softwareElement-SerialNumberThe assigned serial number of this software element.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.7
softwareElement-CodeSetThe code set used by this software element.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.8
softwareElement-IdentificationCodeThe 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.9
softwareElement-LanguageEditionThe 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.ro
DisplayString
.1.3.6.1.4.1.2.6.182.3.9.2.1.10
softwareElement-AssociationsUse this value to associate a SoftwareElement with another object in the MIB
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.9.2.1.11
softwareElement-DeviceSoftware-LogicalDeviceAssociation-ObjectTUse this value to associate a SoftwareElement with a specific media access device or the library itself.ro
Enumeration
.1.3.6.1.4.1.2.6.182.3.9.2.1.12
softwareElement-DeviceSoftware-LogicalDeviceAssociationIdFurther clarification required.ro
INTEGER
.1.3.6.1.4.1.2.6.182.3.9.2.1.13
endOfSmlMibDescription here
OBJECT IDENTIFIER
.1.3.6.1.4.1.2.6.182.3.10
SML-MIB - SNMP MIB Reference | MIBs Explorer