All MIBs › MRV-IN-REACH-BOOT-CLIENT-MIB
Category: Boot / Configuration Services, MRV In-Reach Console / Terminal Server
Description:
Manages MRV In-Reach boot client BOOTP/TFTP configuration and state.
Imported Objects
From MRV-IN-REACH-PRODUCT-DIVISION-MIB
| mrvInReachProductDivision | OBJECT-IDENTITY |
From RFC-1212
| OBJECT-TYPE |
From RFC1213-MIB
| DisplayString |
What Is MRV-IN-REACH-BOOT-CLIENT-MIB?
This is MRV Communications' private MIB for the boot client function on its In-Reach product line of console servers and terminal servers, which use BOOTP/TFTP to load their firmware image and configuration at startup. It exposes configuration for the boot process, such as the boot server address and image/file name, along with the outcome of the boot attempt. Its monitoring emphasis is on software status: confirming whether the device successfully retrieved and booted its firmware/configuration over the network, which is the key diagnostic signal when an In-Reach unit fails to come up correctly after a power cycle. It layers a private management wrapper around the standard BOOTP protocol rather than depending on another SNMP MIB. It is deployed on MRV In-Reach console/terminal servers used for out-of-band management access in data centers and remote sites, where MRV-IN-REACH-BOOT-CLIENT-MIB SNMP monitoring helps confirm each unit boots successfully after a power cycle.
IPNetwork Monitor allows you to monitor SNMP objects defined in MRV-IN-REACH-BOOT-CLIENT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- boot server address configuration
- boot/firmware file name
- last boot status/result
Supported Devices
- MRV In-Reach terminal/console server
- MRV In-Reach multiplexer
Monitoring Examples
No specific object or table names were provided in the sample for this MIB, so exact identifiers can't be cited here. Conceptually, an admin would check the configured boot server address and boot/firmware file name to confirm the client is pointed at the correct source, and check the last boot status/result to diagnose a unit that fails to load its image over the network at startup, which would otherwise leave a remote console server unreachable.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| xBootClient | 1.3.6.1.4.1.33.12 | |||
| STR bootClientStatus | 1.3.6.1.4.1.33.12.1 | DisplayString | read-only | The overall status of the bootstrapping operation, including, for example, what is presently happening and error information. |
RFC description
MRV Communications vendor MIB for In-Reach boot client management on network devices.
Start monitoring MRV In-Reach console/terminal server (BOOTP/TFTP boot client) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.