All MIBs › XYPLEX-BOOT-CLIENT-MIB
Category: Xylogics and Xyplex Terminal Servers
Description:
Manages Xyplex network device boot client configuration, TFTP server addresses, and boot file parameters.
Imported Objects
What Is XYPLEX-BOOT-CLIENT-MIB?
XYPLEX-BOOT-CLIENT-MIB is a Xyplex proprietary MIB module, Xyplex being a terminal-server/network-device vendor later absorbed into MRV Communications, covering the device's network boot client function, including TFTP server addressing and boot-file parameters. With no module description or sample objects available, its exact object set can't be detailed, but based on its name and short description it exposes configuration data governing how the device retrieves its firmware or configuration image at startup. This is primarily a software/configuration-status MIB rather than a performance or fault-monitoring one: administrators would use it to confirm the correct TFTP server address and boot filename are configured, which matters when diagnosing a device that fails to load new firmware on boot. It likely has no significant dependency on other standard MIBs beyond basic SNMPv2 conventions, being a self-contained legacy vendor module. It would have been deployed on legacy Xyplex terminal servers and network access devices that relied on network-based (TFTP) boot processes. Engineers can download the XYPLEX-BOOT-CLIENT-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in XYPLEX-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
- TFTP boot server address
- boot file configuration
Supported Devices
- Xyplex terminal servers and network access devices (legacy)
Monitoring Examples
No sample object names were provided for this module, so specific table or object identifiers cannot be cited with confidence. In general terms, an administrator would expect to poll objects for the configured TFTP boot server IP address and boot filename to confirm a device is set to load the correct firmware image on its next restart. A mismatch or unreachable boot server configured here would explain a device failing to complete its boot/upgrade cycle.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| bootClient | 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
MIB module for managing clients of Xyplex bootstrap service, supporting bootstrap operations and status reporting.
Start monitoring Xyplex terminal servers and network access devices, legacy (TFTP boot-server-address/boot-filename config status) 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.