All MIBs › REDSTONE-SMI
Organization: Redstone Communications, Inc.
Last Updated: 1998-01-01
Category: Vendor SMI and Registration
Description:
Defines the Redstone Communications enterprise OID structure and SMI registration hierarchy.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| enterprises |
What Is REDSTONE-SMI?
REDSTONE-SMI is the Structure of Management Information module for Redstone Communications Inc., defining the enterprise's top-level OID hierarchy and registering its hardware platform identities, such as the RX1400 and RX700 product lines. As an SMI module it does not itself expose monitoring data; instead it provides the OID namespace under which all other Redstone MIBs (address pool, DS1, etc.) register their objects and traps. Its practical use in monitoring is indirect: sysObjectID values derived from this tree let an NMS auto-identify which Redstone hardware platform (RX1400 vs RX700) it is talking to, so it can load the correct set of feature MIBs and status checks for that device model. It depends entirely on the standard SNMPv2-SMI enterprises arc for registration and is a prerequisite for interpreting any other Redstone-specific MIB, so engineers typically compile the REDSTONE-SMI MIB file first before loading any dependent Redstone module. It is deployed universally alongside any Redstone router or access device as the foundational naming layer.
IPNetwork Monitor allows you to monitor SNMP objects defined in REDSTONE-SMI. 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
- hardware platform/model identification
- enterprise OID registration for other Redstone MIBs
Supported Devices
- Redstone Communications RX1400 and RX700 routers/access platforms
Monitoring Examples
An NMS reading sysObjectID.0 from a device and matching it against rsRegHwPlatformRX1400 or rsRegHwPlatformRX700 can automatically determine whether the box is an RX1400 or RX700 chassis and select the appropriate polling profile (e.g., which DS1 or address-pool MIBs apply). This platform identification step typically precedes any deeper hardware/software status polling on the device.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| redstone | 1.3.6.1.4.1.2773 | The Structure of Management Information for the Redstone Communications Inc. enterprise. | ||
| rsRegistration | 1.3.6.1.4.1.2773.1 | The root OBJECT IDENTIFIER under which administratively assigned OBJECT IDENTIFIERS are registered, for example, sysObjectIDs, hardware components, chip sets, etc. | ||
| rsRegGeneric | 1.3.6.1.4.1.2773.1.1 | The root OBJECT IDENTIFIER under which identifiers of generic significance are assigned. | ||
| rsRegGenericOther | 1.3.6.1.4.1.2773.1.1.1 | |||
| rsRegGenericNone | 1.3.6.1.4.1.2773.1.1.2 | |||
| rsRegGenericUnknown | 1.3.6.1.4.1.2773.1.1.3 | |||
| rsRegHardware | 1.3.6.1.4.1.2773.1.2 | The root OBJECT IDENTIFIER under which identifiers for hardware components are assigned. | ||
| rsRegHwPlatform | 1.3.6.1.4.1.2773.1.2.1 | The root OBJECT IDENTIFIER under which identifiers for platforms are assigned. These identifiers are typically used as sysObjectID values. | ||
| rsRegHwPlatformRX1400 | 1.3.6.1.4.1.2773.1.2.1.1 | |||
| rsRegHwPlatformRX700 | 1.3.6.1.4.1.2773.1.2.1.2 | |||
| rsRegHwModule | 1.3.6.1.4.1.2773.1.2.2 | The root OBJECT IDENTIFIER under which identifiers for platform modules are assigned. | ||
| rsRegHwChip | 1.3.6.1.4.1.2773.1.2.3 | The root OBJECT IDENTIFIER under which identifiers for chip sets are assigned. | ||
| rsMgmt | 1.3.6.1.4.1.2773.2 | The root OBJECT IDENTIFIER under which enterprise MIB modules are defined. | ||
| rsRegAgentCapabilities | 1.3.6.1.4.1.2773.3 | The root OBJECT IDENTIFIER under which AGENT-CAPABILITIES identifiers are assigned. | ||
| rsExperiment | 1.3.6.1.4.1.2773.4 | The root OBJECT IDENTIFIER under which experimental MIBs may be temporarily located for development purposes. Support for MIBs in the rsExperiment subtree will be deleted when a permanent object identifier is assigned. |
RFC description
Redstone Communications (acquired by Juniper) enterprise root SMI for Redstone E-series router and security appliance management.
Start monitoring Redstone Communications RX1400/RX700 routers/access platforms (base OID registry) 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.