All MIBs › Fore-Common-MIB
Organization: Marconi Communications
Last Updated: 1999-11-05
Category: ATM, Textual Conventions and Registries, Vendor: Fore Systems (ATM)
Description:
Fore Systems common MIB defining shared object types and base management objects used across the Fore Systems ForeRunner MIB suite.
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| TimeTicks | |
| enterprises |
From SNMPv2-TC
| DisplayString |
What Is Fore-Common-MIB?
Fore-Common-MIB is a Fore Systems (later Marconi/Ericsson) proprietary MIB defining shared base object types and OID subtree structure used across the entire ForeRunner ATM switch MIB suite. Rather than exposing device metrics directly, it establishes common top-level branches (administration, systems, experimental, operations) and shared objects such as SNMP error counters and configured trap-destination addresses that other Fore Systems MIBs build upon. Its direct monitoring relevance is narrow but real: the snmpErrors and snmpTrapDest objects let an operator confirm the switch's SNMP agent is tracking protocol errors correctly and that trap notifications are configured to reach the intended management station, foundational to reliable fault reporting from the rest of the platform. It is a foundational dependency imported by other Fore Systems MIBs (e.g., DS3, E1 interface MIBs) that extend the Fore-Common-MIB OID subtree, rather than a standalone data source. It is used in ForeRunner ATM switch deployments as the base module underpinning the full Fore Systems SNMP management architecture.
IPNetwork Monitor allows you to monitor SNMP objects defined in Fore-Common-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
- SNMP protocol error count
- configured trap destination address
Supported Devices
- Fore Systems ForeRunner ATM switches
Monitoring Examples
An admin would check snmpTrapDest to confirm the switch is configured to send its traps to the correct management station's address, and monitor snmpErrors to catch a rising count of SNMP protocol errors that might indicate a management-station polling misconfiguration or agent issue. Beyond these, the module mainly defines shared OID branches (admin, systems, foreExperiment, operations) rather than pollable device metrics, so most of the actual monitoring data lives in the other Fore Systems MIBs built on top of this common base.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| fore | 1.3.6.1.4.1.326 | Definitions common to all FORE private MIBS. | ||
| admin | 1.3.6.1.4.1.326.1 | |||
| operations | 1.3.6.1.4.1.326.1.1 | |||
| snmpErrors | 1.3.6.1.4.1.326.1.2 | |||
| snmpTrapDest | 1.3.6.1.4.1.326.1.3 | |||
| snmpAccess | 1.3.6.1.4.1.326.1.4 | |||
| assembly | 1.3.6.1.4.1.326.1.5 | |||
| fileXfr | 1.3.6.1.4.1.326.1.6 | |||
| rmonExtensions | 1.3.6.1.4.1.326.1.7 | |||
| preDot1qVlanMIB | 1.3.6.1.4.1.326.1.8 | |||
| snmpTrapLog | 1.3.6.1.4.1.326.1.9 | |||
| ilmisnmp | 1.3.6.1.4.1.326.1.10 | |||
| entityExtensionMIB | 1.3.6.1.4.1.326.1.11 | |||
| ilmiRegistry | 1.3.6.1.4.1.326.1.14 | |||
| foreIfExtension | 1.3.6.1.4.1.326.1.15 | |||
| frameInternetworking | 1.3.6.1.4.1.326.1.16 | |||
| ifExtensions | 1.3.6.1.4.1.326.1.17 | |||
| systems | 1.3.6.1.4.1.326.2 | |||
| atmAdapter | 1.3.6.1.4.1.326.2.1 | |||
| atmSwitch | 1.3.6.1.4.1.326.2.2 | |||
| hardware | 1.3.6.1.4.1.326.2.2.1 | |||
| asx | 1.3.6.1.4.1.326.2.2.1.1 | |||
| software | 1.3.6.1.4.1.326.2.2.2 | |||
| asxd | 1.3.6.1.4.1.326.2.2.2.1 | |||
| asx200wg | 1.3.6.1.4.1.326.2.2.4 | |||
| asx200bx | 1.3.6.1.4.1.326.2.2.5 | |||
| asx200bxe | 1.3.6.1.4.1.326.2.2.6 | |||
| cabletron9A000 | 1.3.6.1.4.1.326.2.2.7 | |||
| asx1000 | 1.3.6.1.4.1.326.2.2.8 | |||
| le155 | 1.3.6.1.4.1.326.2.2.9 | |||
| sfcs200wg | 1.3.6.1.4.1.326.2.2.10 | |||
| sfcs200bx | 1.3.6.1.4.1.326.2.2.11 | |||
| sfcs1000 | 1.3.6.1.4.1.326.2.2.12 | |||
| tnx210 | 1.3.6.1.4.1.326.2.2.15 | |||
| tnx1100 | 1.3.6.1.4.1.326.2.2.16 | |||
| asx1200 | 1.3.6.1.4.1.326.2.2.17 | |||
| asx4000 | 1.3.6.1.4.1.326.2.2.18 | |||
| le25 | 1.3.6.1.4.1.326.2.2.19 | |||
| esx3000 | 1.3.6.1.4.1.326.2.2.20 | |||
| tnx1100b | 1.3.6.1.4.1.326.2.2.21 | |||
| asx150 | 1.3.6.1.4.1.326.2.2.22 | |||
| bxr48000 | 1.3.6.1.4.1.326.2.2.24 | |||
| asx4000m | 1.3.6.1.4.1.326.2.2.25 | |||
| axhIp | 1.3.6.1.4.1.326.2.2.26 | |||
| axhSig | 1.3.6.1.4.1.326.2.2.27 | |||
| etherSwitch | 1.3.6.1.4.1.326.2.3 | |||
| atmAccess | 1.3.6.1.4.1.326.2.5 | |||
| hubSwitchRouter | 1.3.6.1.4.1.326.2.6 | |||
| ipoa | 1.3.6.1.4.1.326.2.7 | |||
| stackSwitch | 1.3.6.1.4.1.326.2.10 | |||
| switchRouter | 1.3.6.1.4.1.326.2.15 | |||
| foreExperiment | 1.3.6.1.4.1.326.3 |
FAQ
What monitoring value does Fore-Common-MIB provide even though it's mostly a shared base module?
It exposes SNMP protocol error counters and the configured trap-destination address, letting an operator confirm the ForeRunner switch's SNMP agent is tracking protocol errors and that traps are configured to reach the right management station.
Why would I check Fore-Common-MIB if fault traps from a ForeRunner switch stop arriving?
It holds the snmpTrapDest object recording where traps are configured to be sent, so verifying that value confirms whether the switch is even pointed at your management station.
RFC description
Defines the enterprise root (Marconi/Fore Systems) and common OID structure for Fore/Marconi products.
Start monitoring Fore Systems (later Marconi) ForeRunner ATM switch (shared base MIB/OID structure) 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.