All MIBs › APPIAN-TRUNK-FR-MIB
Organization: Appian Communications, Inc.
Last Updated: 1999-11-10
Category: Optical and WDM, Vendor: Appian
Description: Appian Communications Frame Relay trunk configuration and PVC status management.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock 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.
What Is APPIAN-TRUNK-FR-MIB?
This is an Appian Communications vendor MIB for managing Frame Relay trunk interfaces on Appian's access/aggregation platforms, covering trunk-level LMI (Local Management Interface) protocol configuration and PVC status. It exposes configuration data for each Frame Relay trunk — LMI protocol type, polling mode, and the standard Frame Relay timers/counters (T391, T392, N391, N392, N393) — alongside trunk sharing settings. It is primarily used for monitoring the software/protocol-level health of Frame Relay trunks, since LMI protocol mismatches or incorrect timer values are a classic cause of a Frame Relay trunk failing to establish or repeatedly flapping, and this MIB lets an administrator confirm those parameters match the carrier/peer configuration. It parallels concepts from the standard Frame Relay DTE/DCE interface MIB (RFC 2115) though implemented as an Appian-specific enterprise MIB. It is typically deployed on Appian Communications access platforms in service-provider or enterprise WAN environments using Frame Relay trunking to aggregate multiple PVCs. Engineers can download the APPIAN-TRUNK-FR-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in APPIAN-TRUNK-FR-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 Frame Relay access/aggregation platform
Monitoring Examples
An administrator would poll acFrTrunkTable/acFrTrunkEntry indexed by acFrTrunkIndex to check acFrTrunkLmiProtocol and acFrTrunkLmiPollingMode, confirming the LMI type matches what the carrier expects; if the trunk is failing to come up, comparing acFrTrunkT391/T392 and acFrTrunkN391/N392/N393 timer values against the peer's configuration would reveal a timer mismatch causing repeated LMI status-inquiry failures, and acFrTrunkShared indicates whether the trunk's bandwidth is being shared across multiple logical circuits.
What Can Be Monitored
- LMI protocol type and polling mode
- Frame Relay trunk timers (T391/T392)
- Frame Relay trunk counters (N391/N392/N393)
- trunk sharing configuration
Imported Objects
From APPIAN-SMI-MIB
| acTrunks | OBJECT-IDENTITY |
From SNMPv2-SMI
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| TruthValue |
OIDs
RFC description
Contains Frame Relay trunk MIB definitions for Appian Communications trunking systems, managing frame relay trunk configuration and status for Appian equipment.
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.