AIIPVCTABLE-MIB
The AIIPVCTABLE-MIB module enables monitoring and management of Permanent Virtual Circuit (PVC) parameters, including status, traffic statistics, and configuration attributes, on ATM (Asynchronous Transfer Mode) network interfaces. This MIB provides the necessary data structures for tracking PVC operational states and performance counters within ATM-based infrastructure.
Imported Objects
Objects
16 total| Object Name |
|---|
aii OBJECT IDENTIFIER .1.3.6.1.4.1.539 |
aiSLC2 OBJECT IDENTIFIER .1.3.6.1.4.1.539.16 |
aiPVCThe MIB module for the PVC Table MODULE-IDENTITY .1.3.6.1.4.1.539.16.1 |
aiPVCTableEntries define permanent virtual circuits (PVCs) in the system. Each entry contains enough information to create one PVC on one network interface. Each entry may also contain the information required to create another circuit in the system, of any kind. This other circuit we will call a companion circuit, since eventually it is going to be connected to the PVC defined in the same entry. This connection information does not need to be present, but may be, to allow for a rapid association between a PVC and its companion circuit. SEQUENCE OF AIPVCEntry .1.3.6.1.4.1.539.16.1.1 |
aiPVCEntryEntries of aiPVCTable. AIPVCEntry .1.3.6.1.4.1.539.16.1.1.1 |
aiPVCStatusThe status of this PVC entry. See RFC 1443 for details of usage.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.539.16.1.1.1.1 |
aiPVCIfTypeThe type of subnetwork on which this PVC is to be created. Examples are frameRelay(32), and x25ple(40).rw IANAifType .1.3.6.1.4.1.539.16.1.1.1.2 |
aiPVCIfIndexThe index into the interfaces group of MIB-II, which defines the particular subnetwork on which this PVC will be created. This index corresponds to what AII calls a link.rw IfIndexType .1.3.6.1.4.1.539.16.1.1.1.3 |
aiPVCCircuitThe individual circuit number on the subnetwork (defined by aiPVCIfIndex), to which the PVC defined by this entry is mapped. In X.25, this number maps directly to a Logical Channel Number. In Frame Relay, this number maps directly to a DLCI. In other words, this object, and aiPVCIfIndex, tell the SLC where a PVC is located.rw PositiveInteger .1.3.6.1.4.1.539.16.1.1.1.4 |
aiPVCCallTimerThe time, in seconds, between successive attempts to create a composite circuit comprising the PVC defined in this entry, and its companion circuit. When a PVC is created, if its aiPVCCallTimer is greater than zero, then the PVC will attempt to connect to a remote host (as specified elsewhere). If the connection attempt times out before completion, then the PVC will try again after aiPVCCallTimer seconds.rw UnsignedShort .1.3.6.1.4.1.539.16.1.1.1.5 |
aiPVCInactivityTimerThe time, in seconds, of inactivity on a composite circuit before a PVC will tear down the composite circuit. Once a composite circuit has been created, comprising a PVC and its companion circuit, then if the PVC's aiPVCInactivityTimer is greater than zero, and if no data passes through the composite circuit in either direction for aiPVCInactivityTimer seconds, then the PVC will close the composite circuit.rw UnsignedShort .1.3.6.1.4.1.539.16.1.1.1.6 |
aiPVCConformance OBJECT IDENTIFIER .1.3.6.1.4.1.539.16.1.2 |
aiPVCGroups OBJECT IDENTIFIER .1.3.6.1.4.1.539.16.1.2.1 |
aiPVCGroupA collection of objects providing information applicable to all AII cal parameter name tables. Unknown .1.3.6.1.4.1.539.16.1.2.1.1 |
aiPVCCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.539.16.1.2.2 |
aiPVCComplianceThe compliance statement for SNMPv2 entities which have AII PVC tables. Unknown .1.3.6.1.4.1.539.16.1.2.2.1 |
More MIBs from Applied Innovation
Browse all Applied InnovationMIBs →Standard SNMP MIB module defining data structures for AISPY-MIB.
The AI198CLC-MIB facilitates SNMP-based monitoring and management of Series 1 Common Logic Controllers (CLCs), enabling the retrieval of operational status, alarm states, and performance counters for these industrial automation devices.
Standard SNMP MIB module defining data structures for AIX1-MIB.
The AIMIB module facilitates SNMP-based monitoring and management of Common Logic Controller (CLC) hardware, providing access to operational status, configuration parameters, and performance counters specific to the controller's logic execution and I/O subsystems.
STREAMS-MIB monitors the configuration and operational status of STREAMS subsystems, specifically tracking pipe instances, module bindings, and data flow states within Unix-based operating systems. This module enables administrators to verify the integrity of STREAMS drivers and multiplexers by observing interface counters, error conditions, and resource allocation metrics.
The AIBADGER-MIB module provides SNMP management interfaces for AI's AIBadger hardware or software platform, exposing specific operational metrics such as system status, resource utilization, and device health counters. This module enables network administrators to monitor the performance and availability of AIBadger instances within an infrastructure environment.