All MIBs › XEDIA-L2DIAL-MIB
Organization: Xedia Corp.
Last Updated: 1999-02-27
Category: Xedia Enterprise Networking
Description:
Manages Xedia Corp. Layer 2 dial-on-demand connection triggers, idle timers, and call accounting.
Imported Objects
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| RowStatus | |
| TEXTUAL-CONVENTION |
From XEDIA-REG
| xediaMibs | OBJECT-IDENTITY |
What Is XEDIA-L2DIAL-MIB?
The XEDIA-L2DIAL-MIB is a proprietary Xedia Corporation MIB for managing Layer 2 dial-on-demand connections, such as ISDN or dial backup links, including connection triggers, idle timers, and call accounting. It exposes a status table showing per-sublayer dial connection state and the IP address negotiated on each dial link. Its monitoring emphasis is on software/connection status: confirming whether a dial-on-demand link is currently up, which address it obtained, and detecting a link stuck connected (accruing call charges) or failing to establish when traffic demands it. No dependency on other standard MIBs is apparent, though it layers conceptually on top of standard PPP/dial interfaces. It was deployed on Xedia routers using dial backup or on-demand ISDN/analog links for branch-office connectivity, where XEDIA-L2DIAL-MIB SNMP monitoring flagged a stuck dial connection accruing unwanted call charges.
IPNetwork Monitor allows you to monitor SNMP objects defined in XEDIA-L2DIAL-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
- dial-on-demand connection status
- assigned IP address per dial link
- idle timeout behavior
- call/connection trigger events
Supported Devices
- Xedia router with dial-on-demand/ISDN interface
Monitoring Examples
Polling l2DialStatusTable/l2DialStatusEntry, an admin can see per-sublayer status such as l2DialStatusIpAddress and l2DialStatusSublayer to confirm whether a dial-on-demand circuit is currently connected and which address it negotiated. A dial link remaining connected far longer than its configured idle timer would suggest a stuck connection accumulating unwanted call charges, while an entry showing no address when traffic is expected would indicate a failed dial attempt.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| xediaL2DialMIB | 1.3.6.1.4.1.838.3.30 | This module defines objects for management of Xedia's Layer 2 Dial layer (l2Dial). | ||
| l2DialObjects | 1.3.6.1.4.1.838.3.30.1 | |||
| l2DialStatusTable | 1.3.6.1.4.1.838.3.30.1.1 | not-accessible | The L2Dial status table. | |
| l2DialStatusEntry | 1.3.6.1.4.1.838.3.30.1.1.1 | not-accessible | An L2Dial status entry. An entry in this table corresponds to an ip addresses / sublayer mapping. | |
| IP l2DialStatusIpAddress | 1.3.6.1.4.1.838.3.30.1.1.1.1 | IpAddress | not-accessible | An IP address. |
| INT l2DialStatusSublayer | 1.3.6.1.4.1.838.3.30.1.1.1.2 | INTEGER | read-only | A sublayer. |
| l2DialConformance | 1.3.6.1.4.1.838.3.30.2 | |||
| l2DialCompliances | 1.3.6.1.4.1.838.3.30.2.1 | |||
| l2DialCompliance | 1.3.6.1.4.1.838.3.30.2.1.1 | The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB. | ||
| l2DialGroups | 1.3.6.1.4.1.838.3.30.2.2 | |||
| l2DialStatusGroup | 1.3.6.1.4.1.838.3.30.2.2.1 | A collection of objects providing addresses to sublayer mappings. |
RFC description
Manages Xedia Layer 2 Dial (L2Dial) layer for Layer 2 connection dialup on Xedia routers.
Start monitoring Xedia router with dial-on-demand/ISDN interface (per-sublayer dial-connection state 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.