Home/Catalog/MRV-IN-REACH-BOOT-SERVER-MIB

MRV-IN-REACH-BOOT-SERVER-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for MRV-IN-REACH-BOOT-SERVER-MIB.

108
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

108 total
Object Name
xBootServer
OBJECT IDENTIFIER
.1.3.6.1.4.1.33.6
RFC1213-MIB
Unknown
.1.3.6.1.4.1.33.6
xBsBasic
OBJECT IDENTIFIER
.1.3.6.1.4.1.33.6.1
basicLogLimitMaximum allowed number of kilobytes for recording events. Corresponds directly to MANAGER LOG FILE SIZE and the value labeled 'Log File Size:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.1.1
basicActiveLimitMaximum allowed number of simultaneous service dialogs. Corresponds directly to MANAGER SIMULTANEOUS and the value labeled 'Maximum simultaneous requests:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.1.2
basicActiveNumberNumber of active service dialogs. Corresponds indirectly to the list of active clients in the MANAGER STATUS display.ro
Gauge
.1.3.6.1.4.1.33.6.1.3
basicClientNumberNumber of defined clients. Corresponds indirectly to the list of defined clients in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.ro
Gauge
.1.3.6.1.4.1.33.6.1.4
basicOffersSentTotal number of service offers sent in response to client requests. Corresponds directly to the value labeled 'Total service offers sent:' in the MANAGER STATUS display.ro
Counter
.1.3.6.1.4.1.33.6.1.5
basicEventTotalTotal number of events that have been written to the event log since it was last purged. This may be less than the number currently in the log. Corresponds directly to the value labeled 'Total Messages Logged:' in the MANAGER EVENTS display.ro
Gauge
.1.3.6.1.4.1.33.6.1.6
basicEventPurgeControl to cause emptying the event log. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the event log to immediately become empty. Corresponds directly to the PURGE MANAGER LOG FILE command.rw
Enumeration
.1.3.6.1.4.1.33.6.1.7
activeTableA list of active client dialog entries. The number of entries is given by basicActiveNumber.
SEQUENCE OF ActiveEntry
.1.3.6.1.4.1.33.6.1.8
activeEntryParameter values for an active client dialog entry.
ActiveEntry
.1.3.6.1.4.1.33.6.1.8.1
activeIdentificationTypeThe type of identification value in activeIdentification. Corresponds indirectly to the value labeled 'EthernetAddress' in the MANAGER STATUS display.ro
AddressType
.1.3.6.1.4.1.33.6.1.8.1.1
activeIdentificationIdentification of the active partner. Corresponds directly to the value labeled 'EthernetAddress' in the MANAGER STATUS display.ro
OCTET STRING
.1.3.6.1.4.1.33.6.1.8.1.2
activeFunctionThe function the server is performing with the partner. Corresponds directly to the value labeled 'Function' in the MANAGER STATUS display.ro
Enumeration
.1.3.6.1.4.1.33.6.1.8.1.3
activeSoftwareVersionTypeIf activeFunction is 'load', the software version being sent to the client, otherwise 'notApplicable'. Corresponds to the letter in the software version labeled 'Version' in the MANAGER STATUS display. alpha 'A': alpha test beta 'B': beta test production null: normal, production software special 'S': special, custom software diagnostic 'D': diagnostic, debug softwarero
Enumeration
.1.3.6.1.4.1.33.6.1.8.1.4
activeSoftwareVersionIf activeFunction is 'load', the 4-byte software version being sent to the client, otherwise zero length. In order, the octets contain major version, minor version, ECO, and pre-release number. Corresponds to the numbers in the software version labeled 'Version' in the MANAGER STATUS display. For example, the version display for activeSoftwareVersionType 'production' and activeSoftwareVersion '2.2.0.0' is 'V2.2'. The version display for activeSoftwareVersionType 'beta' and activeSoftwareVersion '3.1.0.4' is 'V3.1B4'.ro
OCTET STRING
.1.3.6.1.4.1.33.6.1.8.1.5
activeParameterVersionIf activeFunction is 'parameterStore', the parameter version being stored by the client, otherwise zero. Corresponds directly to the value labeled 'Version' in the MANAGER STATUS display.ro
INTEGER
.1.3.6.1.4.1.33.6.1.8.1.6
activeCurrentSequenceThe current dialog sequence number. Corresponds directly to the value labeled 'Seq' in the MANAGER STATUS display.ro
INTEGER
.1.3.6.1.4.1.33.6.1.8.1.7
activeBytesRemainingThe number of bytes remaining to be transferred in the dialog. Corresponds directly to the value labeled 'Left' in the MANAGER STATUS display.ro
INTEGER
.1.3.6.1.4.1.33.6.1.8.1.8
activeFileThe name of the file being used in the dialog. Corresponds directly to the value labeled 'File' in the MANAGER STATUS display.ro
DisplayString
.1.3.6.1.4.1.33.6.1.8.1.9
activeStatusThe final status of the most recent attempt to get an image. Corresponds directly to the value labeled 'Get Status:' in the DEVICE STATUS display.ro
DialogStatus
.1.3.6.1.4.1.33.6.1.8.1.10
activeStateThe dynamic state of an active attempt to get an image. Corresponds directly to the value labeled 'Get State:' in the DEVICE STATUS display.ro
Enumeration
.1.3.6.1.4.1.33.6.1.8.1.11
clientTableA list of client data base entries. The number of entries is given by basicClientNumber.
SEQUENCE OF ClientEntry
.1.3.6.1.4.1.33.6.1.9
clientEntryParameter values for a client data base entry.
ClientEntry
.1.3.6.1.4.1.33.6.1.9.1
clientIdentificationTypeThe type of identification value in clientIdentification. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.ro
AddressType
.1.3.6.1.4.1.33.6.1.9.1.1
clientIdentificationIdentification of the client, either a hardware type or an Ethernet address, depending on clientIdentificationType. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.ro
OCTET STRING
.1.3.6.1.4.1.33.6.1.9.1.2
clientEntryStatusThe status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the PURGE LOCAL, PURGE GLOBAL, and PURGE NODE commands. Actual removal of the entry is implementation specific.rw
Enumeration
.1.3.6.1.4.1.33.6.1.9.1.3
clientNameA name that may be used to identify the client. Corresponds directly to the value labeled 'Name' in the MANAGER NODE display.rw
DisplayString
.1.3.6.1.4.1.33.6.1.9.1.4
clientLoadFileThe file with the client's load image. Corresponds directly to the value labeled 'Load File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.rw
DisplayString
.1.3.6.1.4.1.33.6.1.9.1.5
clientDiagnosticFileThe file with the client's diagnostic test image. Corresponds directly to the value labeled 'Diag File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.rw
DisplayString
.1.3.6.1.4.1.33.6.1.9.1.6
clientLoadServiceControl for allowing load service for the client. Corresponds directly to the value labeled 'Load' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.rw
Enumeration
.1.3.6.1.4.1.33.6.1.9.1.7
clientDumpServiceControl for allowing dump service for the client. Corresponds directly to the value labeled 'Dump' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.rw
Enumeration
.1.3.6.1.4.1.33.6.1.9.1.8
namedTableA list of named client data base entries. The number of entries is given by basicClientNumber.
SEQUENCE OF NamedEntry
.1.3.6.1.4.1.33.6.1.10
namedEntryParameter values for a named client data base entry.
NamedEntry
.1.3.6.1.4.1.33.6.1.10.1
namedIdentificationTypeThe type of identification value in namedIdentification. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.ro
AddressType
.1.3.6.1.4.1.33.6.1.10.1.1
namedIdentificationIdentification of the client, either a hardware type or an Ethernet address, depending on namedIdentificationType. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.ro
OCTET STRING
.1.3.6.1.4.1.33.6.1.10.1.2
namedEntryStatusThe status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the PURGE LOCAL, PURGE GLOBAL, and PURGE NODE commands. Actual removal of the entry is implementation specific.ro
Enumeration
.1.3.6.1.4.1.33.6.1.10.1.3
namedNameA name that may be used to identify the client. Corresponds directly to the value labeled 'Name' in the MANAGER NODE display.ro
DisplayString
.1.3.6.1.4.1.33.6.1.10.1.4
namedLoadFileThe file with the client's load image. Corresponds directly to the value labeled 'Load File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.ro
DisplayString
.1.3.6.1.4.1.33.6.1.10.1.5
namedDiagnosticFileThe file with the client's diagnostic test image. Corresponds directly to the value labeled 'Diag File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.ro
DisplayString
.1.3.6.1.4.1.33.6.1.10.1.6
namedLoadServiceControl for allowing load service for the client. Corresponds directly to the value labeled 'Load' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.ro
Enumeration
.1.3.6.1.4.1.33.6.1.10.1.7
namedDumpServiceControl for allowing dump service for the client. Corresponds directly to the value labeled 'Dump' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.ro
Enumeration
.1.3.6.1.4.1.33.6.1.10.1.8
xEventTableA list of event entries. The number of entries is given by basicEventNumber.
SEQUENCE OF XEventEntry
.1.3.6.1.4.1.33.6.1.11
xEventEntryParameter values for a event entry.
XEventEntry
.1.3.6.1.4.1.33.6.1.11.1
xEventIndexIn identification number for an event. The value 1 indicates the oldest event in the file, with subsequent numbers indicating sequential events. The event text for a given number may change as a circular event log wraps over its beginning. Corresponds directly to the relative position of an event in the MANAGER EVENTS display.ro
INTEGER
.1.3.6.1.4.1.33.6.1.11.1.1
xEventTextThe text of the event, including date, time and other information. Corresponds directly to the individual event text in the MANAGER EVENTS display.ro
DisplayString
.1.3.6.1.4.1.33.6.1.11.1.2
basicDeviceNumberThe system's number of mass-storage devices.ro
INTEGER
.1.3.6.1.4.1.33.6.1.12
deviceTableA list of device entries. The number of entries is given by basicDeviceNumber.
SEQUENCE OF DeviceEntry
.1.3.6.1.4.1.33.6.1.13
deviceEntryParameter values for a device entry.
DeviceEntry
.1.3.6.1.4.1.33.6.1.13.1
deviceIndexIn identification number for a device, in the range 1 to basicDeviceNumberro
INTEGER
.1.3.6.1.4.1.33.6.1.13.1.1
deviceNameA name by which the device is known in other displays, such as 'C1' or 'D2'.ro
DisplayString
.1.3.6.1.4.1.33.6.1.13.1.2
deviceDescrDetails of the device type, including, for example, size, manufacturer, Flash versus RAM, and such. Corresponds directly to the value labeled 'Device Type: in the MANAGER DEVICE STATUS display.ro
DisplayString
.1.3.6.1.4.1.33.6.1.13.1.3
deviceOperationCurrent operational state of the device. Corresponds directly the value labeled 'Device Operation:' in the MANAGER DEVICE STATUS display.ro
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.4
deviceFormatFormatting status of the device. Corresponds directly the presence of one of the value labels under the label 'Device Status:' in the MANAGER DEVICE STATUS display.ro
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.5
deviceProtectionWrite-protect status of the device. Corresponds directly the presence of one of the value labels under the label 'Device Status:' in the MANAGER DEVICE STATUS display.ro
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.6
deviceFormatMediumControl to cause formatting of the medium in the device. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the device to be formatted. Corresponds directly to the FORMAT DEVICE command.rw
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.7
deviceGetFileControl to cause getting a file to the device from a remote host system. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the get to be attempted. Corresponds directly to the GET DEVICE command. When set to 'execute', the objects deviceGetFileHostIdentificationType, deviceGetFileHostIdentification, deviceGetFileName and deviceGetFileArea must be somewhere in the same set request message.rw
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.8
deviceGetFileHostIdentificationTypeThe type of identification value in deviceIdentification. Corresponds indirectly to ADDRESS in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is 'undefined'.rw
AddressType
.1.3.6.1.4.1.33.6.1.13.1.9
deviceGetFileHostIdentificationIdentification of the host to get the file from, with type depending on deviceIdentificationType. Corresponds directly to ADDRESS in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero length.rw
OCTET STRING
.1.3.6.1.4.1.33.6.1.13.1.10
deviceGetFileNameThe name of the file to get. Corresponds directly to LOAD FILE in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero length.rw
DisplayString
.1.3.6.1.4.1.33.6.1.13.1.11
deviceGetFileAreaThe area number in which to put the file. Corresponds directly to AREA in the GET DEVICE command. If it is not relevant to the particular device, it is ignored. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero.rw
INTEGER
.1.3.6.1.4.1.33.6.1.13.1.12
deviceFormatOptionFormatting option to apply. Corresponds directly to the OPTION in the FORMAT DEVICE command. This object may not be set outside the context of setting deviceFormatMedium to 'execute'. In response to a get-request or get-next-request, the value of this object is zero.rw
INTEGER
.1.3.6.1.4.1.33.6.1.13.1.13
deviceFormatRedundantParamsControl for creating redundant parameter storage areas when formatting. Corresponds directly to NONREDUNDANT in the FORMAT DEVICE command. This object may not be set outside the context of setting deviceFormatMedium to 'execute'. In response to a get-request or get-next-request, the value of this object is zero.rw
Enumeration
.1.3.6.1.4.1.33.6.1.13.1.14
devicePreviousStatusResult of the immediately previous concluded boot dialog. Corresponds directly to the value labeled 'Get File Previous Status:' in the SHOW CARD STATUS display.ro
DialogStatus
.1.3.6.1.4.1.33.6.1.13.1.15
xDump
OBJECT IDENTIFIER
.1.3.6.1.4.1.33.6.2
dumpServiceControl for allowing dump service for any client. Corresponds directly to DUMP and the value labeled 'Dump:' in the MANAGER CHARACTERISTICS display.rw
Enumeration
.1.3.6.1.4.1.33.6.2.1
dumpDriveIdentification number of the disk drive where dumps are stored. Corresponds directly to DUMP DRIVE and the value labeled 'Dump Drive:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.2.2
dumpMeritRelative preference for this dump server over others. Corresponds directly to DUMP MERIT and the value labeled 'Dump Merit:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.2.3
dumpSizeType of dump file to keep. Corresponds directly to DUMP SIZE and the value labeled 'Dump Size:' in the MANAGER CHARACTERISTICS display.rw
Enumeration
.1.3.6.1.4.1.33.6.2.4
dumpCompletedThe number of dumps completed since system initialization. Corresponds directly to the value labeled 'Dump Operations Completed:' in the MANAGER STATUS display.ro
Counter
.1.3.6.1.4.1.33.6.2.5
dumpActiveThe number of dumps in progress. Corresponds directly to the value labeled 'Currently Dumping:' in the MANAGER STATUS display.ro
Gauge
.1.3.6.1.4.1.33.6.2.6
dumpFileNumberThe number of dump files currently stored. Corresponds directly to the value labeled 'Network dump files' and 'files' in the MANAGER FILES display.ro
Gauge
.1.3.6.1.4.1.33.6.2.7
dumpFileTableA list of dump file entries. The number of entries is given by dumpFileNumber.
SEQUENCE OF DumpFileEntry
.1.3.6.1.4.1.33.6.2.8
dumpFileEntryParameter values for a dump file entry.
DumpFileEntry
.1.3.6.1.4.1.33.6.2.8.1
dumpFileIdentificationTypeThe type of identification value in dumpFileIdentification. Corresponds indirectly to a file name part in the section labeled 'Network dump files' in the MANAGER FILES display.ro
AddressType
.1.3.6.1.4.1.33.6.2.8.1.1
dumpFileIdentificationIdentification of the dump file, an Ethernet address, as indicated by dumpFileIdentificationType. Corresponds indirectly to a file name part in the section labeled 'Network dump files' in the MANAGER FILES display.ro
OCTET STRING
.1.3.6.1.4.1.33.6.2.8.1.2
dumpFileEntryStatusThe status of the entry. Set to 'invalid' to remove the entry, which corresponds indirectly to the PURGE MANAGER DUMP FILES command. Actual removal of the entry is implementation specific.rw
Enumeration
.1.3.6.1.4.1.33.6.2.8.1.3
dumpFileCreationThe time the dump file was created. Corresponds directly to a date and time in the section labeled 'Network dump files' in the MANAGER FILES display.ro
DateTime
.1.3.6.1.4.1.33.6.2.8.1.4
dumpFileSizeThe number of bytes stored in the dump file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Network dump files' in the MANAGER FILES display.ro
INTEGER
.1.3.6.1.4.1.33.6.2.8.1.5
xLoad
OBJECT IDENTIFIER
.1.3.6.1.4.1.33.6.3
loadServiceControl for allowing load service for any client. Corresponds directly to LOAD and the value labeled 'Load:' in the MANAGER CHARACTERISTICS display.rw
Enumeration
.1.3.6.1.4.1.33.6.3.1
loadMeritRelative preference for this load server over others. Corresponds directly to LOAD MERIT and the value labeled 'Load Merit:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.3.2
loadCompletedThe number of loads completed since system initialization. Corresponds directly to the value labeled 'Load Operations Completed:' in the MANAGER STATUS display.ro
Counter
.1.3.6.1.4.1.33.6.3.3
loadActiveThe number of loads in progress. Corresponds directly to the value labeled 'Currently Loading:' in the MANAGER STATUS display.ro
Gauge
.1.3.6.1.4.1.33.6.3.4
loadFileNumberThe number of load files currently stored. Corresponds directly to the value labeled 'Load image files' and 'files' in the MANAGER FILES display.ro
Gauge
.1.3.6.1.4.1.33.6.3.5
loadFileTableA list of load file entries. The number of entries is given by loadFileNumber.
SEQUENCE OF LoadFileEntry
.1.3.6.1.4.1.33.6.3.6
loadFileEntryParameter values for a load file entry.
LoadFileEntry
.1.3.6.1.4.1.33.6.3.6.1
loadFileNameThe name of a load file. Corresponds directly to a file name part in the section labeled 'Load image files' in the MANAGER FILES display.ro
DisplayString
.1.3.6.1.4.1.33.6.3.6.1.1
loadFileCreationThe time the load file was created. Corresponds directly to a date and time in the section labeled 'Load image files' in the MANAGER FILES display.ro
DateTime
.1.3.6.1.4.1.33.6.3.6.1.2
loadFileSizeThe number of bytes stored in the load file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Load image files' in the MANAGER FILES display.ro
INTEGER
.1.3.6.1.4.1.33.6.3.6.1.3
loadFileSoftwareVersionTypeThe software version type of the image in the load file. Corresponds directly to a software version in the section labeled 'Load image files' in the MANAGER FILES display. alpha 'A': alpha test beta 'B': beta test production null: normal, production software special 'S': special, custom softwarero
Enumeration
.1.3.6.1.4.1.33.6.3.6.1.4
loadFileSoftwareVersionThe software version of the image in the load file. Corresponds directly to a software version in the section labeled 'Load image files' in the MANAGER FILES display. For example, the version display for loadFileSoftwareVersionType 'production' and loadFileSoftwareVersion '2.2.0.0' is 'V2.2'. The version display for loadFileSoftwareVersionType 'beta' and loadFileSoftwareVersion '3.1.0.4' is 'V3.1B4'.ro
OCTET STRING
.1.3.6.1.4.1.33.6.3.6.1.5
xParam
OBJECT IDENTIFIER
.1.3.6.1.4.1.33.6.4
paramServiceControl for allowing parameter storage service for any client. Corresponds directly to PARAMETER SERVICE and the value labeled 'Parameter Service:' in the MANAGER CHARACTERISTICS display.rw
Enumeration
.1.3.6.1.4.1.33.6.4.1
paramDefaultServiceControl for allowing default parameter loading service for any client. Corresponds directly to PARAMETER DEFAULT SERVICE and the value labeled 'Parameter Default Service:' in the MANAGER CHARACTERISTICS display.rw
Enumeration
.1.3.6.1.4.1.33.6.4.2
paramDriveIdentification number of the disk drive where parameters are stored. Corresponds directly to PARAMETER DRIVE and the value labeled 'Parameter Drive:' in the MANAGER CHARACTERISTICS display.rw
INTEGER
.1.3.6.1.4.1.33.6.4.3
paramActiveThe number of params in progress. Corresponds directly to the value labeled 'Currently Paraming:' in the MANAGER STATUS display.ro
Gauge
.1.3.6.1.4.1.33.6.4.4
paramStorageActiveThe number of parameter storage operations in progress. Corresponds directly to the value labeled 'Currently saving parameters:' in the MANAGER STATUS display.ro
Gauge
.1.3.6.1.4.1.33.6.4.5
paramFileNumberThe number of parameter files currently stored. Corresponds directly to the value labeled 'Parameter files' and 'files' in the MANAGER FILES display.ro
Gauge
.1.3.6.1.4.1.33.6.4.6
paramFileTableA list of param file entries. The number of entries is given by paramFileNumber.
SEQUENCE OF ParamFileEntry
.1.3.6.1.4.1.33.6.4.7
paramFileEntryParameter values for a param file entry.
ParamFileEntry
.1.3.6.1.4.1.33.6.4.7.1
paramFileIdentificationTypeThe type of identification value in paramFileIdentification. Corresponds indirectly to a file name part in the section labeled 'Parameter files' in the MANAGER FILES display.ro
AddressType
.1.3.6.1.4.1.33.6.4.7.1.1
paramFileIdentificationIdentification of the param file, an Ethernet address, as indicated by paramFileIdentificationType. Corresponds indirectly to a file name part in the section labeled 'Parameter files' in the MANAGER FILES display.ro
OCTET STRING
.1.3.6.1.4.1.33.6.4.7.1.2
paramFileEntryStatusThe status of the entry. Set to 'invalid' to remove the entry, which corresponds indirectly to the PURGE MANAGER PARAMETER FILES command. Actual removal of the entry is implementation specific.rw
Enumeration
.1.3.6.1.4.1.33.6.4.7.1.3
paramFileWriteThe time the parameter file was last written. Corresponds directly to a date and time in the section labeled 'Parameter files' in the MANAGER FILES display.ro
DateTime
.1.3.6.1.4.1.33.6.4.7.1.4
paramFileSizeThe number of bytes stored in the param file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Parameter files' in the MANAGER FILES display.ro
INTEGER
.1.3.6.1.4.1.33.6.4.7.1.5
paramFileParameterVersionThe version number of the parameter data in the file. Corresponds directly to the value labeled 'ver' in the section labeled 'Parameter files' in the MANAGER FILES display.ro
INTEGER
.1.3.6.1.4.1.33.6.4.7.1.6
MRV-IN-REACH-BOOT-SERVER-MIB - SNMP MIB Reference | MIBs Explorer