All MIBs › APPIAN-SMI-MIB
Organization: Appian Communications, Inc.
Last Updated: 2000-01-27
Category: Optical and WDM, Vendor: Appian
Description:
Appian Communications SMI structure defining the enterprise OID registration hierarchy.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| TimeTicks | |
| enterprises |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION |
What Is APPIAN-SMI-MIB?
APPIAN-SMI-MIB is the Structure of Management Information (SMI) root module for Appian Communications, a vendor of broadband access and optical networking equipment. Rather than exposing any live monitoring data itself, it defines the top-level enterprise OID arc under which all other Appian-specific MIB modules register their object identifiers. As a pure registration/naming module it exposes no interface, environmental, performance, or fault data of its own -- hardware and software status such as uptime, temperature, CPU load, and power/fan health are instead monitored through the child MIBs anchored beneath this root. It has no meaningful dependency beyond the standard SNMPv2-SMI enterprise-numbering convention used to build the OID tree. It would be encountered only indirectly, loaded as a prerequisite when compiling or browsing other Appian device MIBs in an SNMP management tool. Opening the APPIAN-SMI-MIB MIB file in a compiler reveals nothing but OID arc assignments, confirming it exists solely to anchor the vendor's other Appian modules.
IPNetwork Monitor allows you to monitor SNMP objects defined in APPIAN-SMI-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.
Supported Devices
- Appian Communications broadband access/optical equipment
Monitoring Examples
This module contains no runtime tables or scalars -- sample_objects is empty because it is purely a namespace/registration MIB. An administrator would never poll it directly; instead, tools like snmpwalk or a MIB browser use it only to resolve OID prefixes when navigating to the actual Appian device MIBs registered underneath it. There is no monitoring scenario to describe honestly, since it defines structure, not data.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| appian | 1.3.6.1.4.1.2785 | Appian Communications Enterprise MIB Definitions | ||
| acIdentifier | 1.3.6.1.4.1.2785.1 | |||
| acProductId | 1.3.6.1.4.1.2785.1.1 | |||
| acOsap | 1.3.6.1.4.1.2785.2 | |||
| acPport | 1.3.6.1.4.1.2785.2.3 | |||
| acLport | 1.3.6.1.4.1.2785.2.4 | |||
| acTrunks | 1.3.6.1.4.1.2785.2.6 | |||
| acServices | 1.3.6.1.4.1.2785.2.8 |
RFC description
Appian Communications enterprise root SMI for Appian optical transport and network management systems.
Start monitoring Appian Communications OSAP SONET/optical access platform (legacy) 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.