Home/Catalog/SIEMENS-VV-MIB

SIEMENS-VV-MIB

Detailed view of the defined objects, syntax rules, and hierarchical paths.

70
Objects
Active
Status
3
Dependencies

Imported Objects

Objects

70 total
Object Name
sni
OBJECT IDENTIFIER
.1.3.6.1.4.1.231
IMPORTS
Unknown
.1.3.6.1.4.1.231
sniProductMibs
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2
sniExtensions
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10
sniServerMgmt
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2
sieVersionView
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10
sieVvAgentInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.1
sieVvAgentIdVersionView SNMP agent ID stringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.1.1
sieVvAgentCompanyVersionView SNMP agent company stringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.1.2
sieVvAgentVersionVersionView SNMP agent version stringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.1.3
sieVvAgentBuildVersionView SNMP agent build date and time stringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.1.4
sieVvState
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.2
sieVvLastDateDate of actual collection of data in time_t (seconds since 1.1.70 00:00:00)ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.2.1
sieVvLastScanDate of last scanning cycle in time_t (seconds since 1.1.70 00:00:00)ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.2.2
sieVvScanStateactual scanning statero
Enumeration
.1.3.6.1.4.1.231.2.10.2.10.2.3
sieVvDef
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.3
sieVvCompDefTableTable of available Component Type Definitions
SEQUENCE OF SieVvCompDef
.1.3.6.1.4.1.231.2.10.2.10.3.1
sieVvCompDefEntry in Table of Component Type Definitions
SieVvCompDef
.1.3.6.1.4.1.231.2.10.2.10.3.1.1
sieVvCompDefNoNumber of Table Entry: A unique value for each component definition. Its value starts at 1 and must remain constant at least from one re-initialization of the SNMP agent to the next reinitialization.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.1.1.1
sieVvCompDefTypeType of Component from Master DB. The details are defined in the document: VersionView MIB Supplementary. Declaration is found in the file VersionView.iniro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.1.1.2
sieVvCompDefNameName of Component. The details are defined in the document: VersionView MIB Supplementary. Declaration is found in the file VersionView.iniro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.3.1.1.3
sieVvPhysNodeDefTableTable of node definitions that are used in the sieVvCont group
SEQUENCE OF SieVvPhysNodeDef
.1.3.6.1.4.1.231.2.10.2.10.3.2
sieVvPhysNodeDefEntry in Table of Physical Node Definitions
SieVvPhysNodeDef
.1.3.6.1.4.1.231.2.10.2.10.3.2.1
sieVvPhysNodeDefNoNumber of Table Entry: A unique value for each physical container definition. Its value starts at 1 and must remain constant at least from one re-initialization of the SNMP agent to the next reinitialization.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.2.1.1
sieVvPhysNodeDefTypeType of node in the physical tree. The details are defined in the document: VersionView MIB Supplementary.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.2.1.2
sieVvPhysNodeDefNameName of node in the physical tree. The details are defined in the document: VersionView MIB Supplementary.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.3.2.1.3
sieVvFuncNodeDefTableTable of node definitions that are used in the sieVvCont group
SEQUENCE OF SieVvFuncNodeDef
.1.3.6.1.4.1.231.2.10.2.10.3.3
sieVvFuncNodeDefEntry in Table of Functional Node Definitions
SieVvFuncNodeDef
.1.3.6.1.4.1.231.2.10.2.10.3.3.1
sieVvFuncNodeDefNoNumber of Table Entry: A unique value for each functional container definition. Its value starts at 1 and must remain constant at least from one re-initialization of the SNMP agent to the next reinitialization.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.3.1.1
sieVvFuncNodeDefTypeType of node in the functional tree. The details are defined in the document: VersionView MIB Supplementary.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.3.3.1.2
sieVvFuncNodeDefNameName of node in the functional tree. The details are defined in the document: VersionView MIB Supplementary.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.3.3.1.3
sieVvCont
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.4
sieVvPhysContTableTable of expressing the hierarchy of Physical Containers for Components
SEQUENCE OF SieVvPhysCont
.1.3.6.1.4.1.231.2.10.2.10.4.1
sieVvPhysContEntry in Table of Physical Containers
SieVvPhysCont
.1.3.6.1.4.1.231.2.10.2.10.4.1.1
sieVvPhysContNoNumber of Table Entry A unique value for each physical container. Its value starts at 1. The value for each container may change during an update of the MIB data, i.e. at the date specified in sieVvLastDate.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.1.1.1
sieVvPhysContTypeType of Physical Container. This value is the value of sieVvPhysNodeDefNo of the corresponding entry in the table of Physical Container Definitions.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.1.1.2
sieVvPhysContParentValue of sieVvPhysContNo for the entry which describes the parent container. The value 0 indicates that there is no parent container, i.e. it is the root.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.1.1.3
sieVvPhysContNameName of node in the physical tree, corresponding to Type of Physical Container. The details are defined in the document: VersionView MIB Supplementary. (Added for debug purpose)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.4.1.1.4
sieVvFuncContTableTable of available Components
SEQUENCE OF SieVvFuncCont
.1.3.6.1.4.1.231.2.10.2.10.4.2
sieVvFuncContEntry in Table of Functional Containers
SieVvFuncCont
.1.3.6.1.4.1.231.2.10.2.10.4.2.1
sieVvFuncContNoNumber of Table Entry: A unique value for each functional container. Its value starts at 1. The value for each container may change during an update of the MIB data, i.e. at the date specified in sieVvLastDate.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.2.1.1
sieVvFuncContTypeType of Functional Container. This value is the value of sieVvFuncNodeDefNo of the corresponding entry in the table of Functional Container Definitions.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.2.1.2
sieVvFuncContParentValue of sieVvFuncContNo for the entry which describes the parent container. The value 0 indicates that there is no parent container, i.e. it is the root.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.4.2.1.3
sieVvFuncContNameName of node in the functional tree, corresponding to Type of Functional Container. The details are defined in the document: VersionView MIB Supplementary. (Added for debug purpose)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.4.2.1.4
sieVvInfos
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.5
sieVvInfoTableTable of available Components
SEQUENCE OF SieVvInfo
.1.3.6.1.4.1.231.2.10.2.10.5.1
sieVvInfoEntry in Table of Components
SieVvInfo
.1.3.6.1.4.1.231.2.10.2.10.5.1.1
sieVvInfoNoNumber of Table Entry: A unique value for each component. Its value starts at 1. The value for each component may change during an update of the MIB data, i.e. at the date specified in sieVvLastDate.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.1
sieVvInfoPhysContNoValue of sieVvPhysContNo for the entry which describes the parent container. The value 0 indicates that there is no parent container. For example, software or firmware components are in no physical containers.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.2
sieVvInfoFuncContNoValue of sieVvFuncContNo for the entry which describes the functional parent container.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.3
sieVvInfoCompTypeComponent type: This value is the value of sieVvCompDefNo of the corresponding entry in the table of Component Definitions.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.4
sieVvInfoVendorComponent Vendorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.5
sieVvInfoProductNameProduct Name of Component Software: (e.g. Driver) File Name (e.g. abcd.sys) HW: Component Name (e.g. DAC960xx, D981)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.6
sieVvInfoProductNumberProduct Number of Component e.g. S26361 D981ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.7
sieVvInfoProductDescriptionDescription of Component e.g. SCSI Miniport Driver, CD-ROM IDE Devicero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.8
sieVvInfoVersionVersion Number of Component e.g. for Driver: FileVersion//ProductVersion//InternalName//OperatingSystem e.g. for HW: V2 GS1 or Version x.y Revision a.bro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.9
sieVvInfoManufacturingDateManufacturing Date of Component in the form YYYY-MM-DD hh:mm:ss e.g. for Software: Date of last changero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.10
sieVvInfoSerialNoSerial Number of Componentro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.11
sieVvInfoLanguageSupported Language of Component as defined in ISO 639/ISO 3166 (ISO 639 LanguageName//ISO 3166 Territory Name) e.g. en//USro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.12
sieVvInfoComponentIdIdentification String for Component e.g. <Bus>\VEN_110A&DEV_0013&SUBSYS_0013110A&REV_01 Bus PCI, EISA, USB,... VEN_vvvv VendorID from PCI-ConfigSpace DEV_dddd DeviceID from PCI-ConfigSpace SUBSYS_sdsdsvsv SubDeviceID/SubVendorID from PCI-ConfigSpace REV_rr Revision from PCI-ConfigSpace the entries SUBSYS_sdsdsvsv and REV_rr are optionalro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.13
sieVvInfoCompLocationKeyDevice location key, used for identifying the component; e.g. 'TYPE_PCI&BUS_3&DEV_14&FUNC_0'ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.5.1.1.14
sieVvFwuObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.231.2.10.2.10.6
sieVvFwuObjectTableTable of objects having updatable firmware.
SEQUENCE OF SieVvFwuObject
.1.3.6.1.4.1.231.2.10.2.10.6.1
sieVvFwuObjectEntry in Table of Firmware Update Objects
SieVvFwuObject
.1.3.6.1.4.1.231.2.10.2.10.6.1.1
sieVvFwuObjectNoNumber of Table Entry: A unique value for each update object. Its value starts at 1. The value for each object may change during an update of the MIB data, i.e. at the date specified in sieVvLastDate.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.1
sieVvFwuObjectNameUnique name to identify the updatable object within the server system: NT device name, with an extension in some cases such as a physical disk within a RAID array.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.2
sieVvFwuObjectPathPathname to indicate more precisely the logical position of the object within the server system: e.g. bus path (including for example PCI bridge), SCSI target ID., etc.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.3
sieVvFwuObjectParentIn some cases an object hierarchy has to be established for the purpose of updating firmware, e.g. a RAID controller which contains a physical disk, acting as a passthrough controller to that disk.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.4
sieVvFwuObjectUpdateStateSpecifies the state of this object with regard to update: 0 = normal, default state, 1 = cannot update now, e.g. a RAID rebuild is running, 2 = in the process of updating, 3 = error, update could not be completed successfully. 4 = update OK, but needs a reboot to become active, 5 = update OK, but needs a reset to become active.ro
Enumeration
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.5
sieVvFwuObjectComponentIndexValue of sieVvInfoNo for the entry which describes the updatable object in the table of component information.ro
INTEGER
.1.3.6.1.4.1.231.2.10.2.10.6.1.1.6
SIEMENS-VV-MIB - SNMP MIB Reference | MIBs Explorer