AIIPVCTABLE-MIB

File: AIIPVCTABLE-MIB.mib (9331 bytes)

Imported modules

Imported symbols

MODULE-IDENTITY	OBJECT-TYPE	enterprises
TEXTUAL-CONVENTION	RowStatus	MODULE-COMPLIANCE
OBJECT-GROUP

Defined Types

UnsignedShort
INTEGER	0..65535

PositiveInteger
INTEGER	0..2147483647

IfIndexType
INTEGER	1..2147483647

IANAifType
This data type is used as the syntax of the ifType object in the (updated) definition of MIB-II's ifTable. The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) Requests for new values should be made to IANA via email (iana@isi.edu). The relationship between the assignment of ifType values and of OIDs to particular media-specific MIBs is solely the purview of IANA and is subject to change without notice. Quite often, a media-specific MIB's OID-subtree assignment within MIB-II's 'transmission' subtree will be the same as its ifType value. However, in some circumstances this will not be the case, and implementors must not pre-assume any specific relationship between ifType values and transmission subtree OIDs.
TEXTUAL-CONVENTION
	INTEGER	other(1), regular1822(2), hdh1822(3), ddnX25(4), rfc877x25(5), ethernetCsmacd(6), iso88023Csmacd(7), iso88024TokenBus(8), iso88025TokenRing(9), iso88026Man(10), starLan(11), proteon10Mbit(12), proteon80Mbit(13), hyperchannel(14), fddi(15), lapb(16), sdlc(17), ds1(18), e1(19), basicISDN(20), primaryISDN(21), propPointToPointSerial(22), ppp(23), softwareLoopback(24), eon(25), ethernet3Mbit(26), nsip(27), slip(28), ultra(29), ds3(30), sip(31), frameRelay(32), rs232(33), para(34), arcnet(35), arcnetPlus(36), atm(37), miox25(38), sonet(39), x25ple(40), iso88022llc(41), localTalk(42), smdsDxi(43), frameRelayService(44), v35(45), hssi(46), hippi(47), modem(48), aal5(49), sonetPath(50), sonetVT(51), smdsIcip(52), propVirtual(53), propMultiplexor(54)

AIPVCEntry
SEQUENCE
	aiPVCStatus	RowStatus
	aiPVCIfType	IANAifType
	aiPVCIfIndex	IfIndexType
	aiPVCCircuit	PositiveInteger
	aiPVCCallTimer	UnsignedShort
	aiPVCInactivityTimer	UnsignedShort

Defined Values

aii		1.3.6.1.4.1.539
OBJECT IDENTIFIER

aiSLC2		1.3.6.1.4.1.539.16
OBJECT IDENTIFIER

aiPVC		1.3.6.1.4.1.539.16.1
The MIB module for the PVC Table
MODULE-IDENTITY

aiPVCTable		1.3.6.1.4.1.539.16.1.1
Entries 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.
Status: current	Access: not-accessible
OBJECT-TYPE
	SEQUENCE OF
		AIPVCEntry

aiPVCEntry		1.3.6.1.4.1.539.16.1.1.1
Entries of aiPVCTable.
Status: current	Access: not-accessible
OBJECT-TYPE
	AIPVCEntry

aiPVCStatus		1.3.6.1.4.1.539.16.1.1.1.1
The status of this PVC entry. See RFC 1443 for details of usage.
Status: current	Access: read-create
OBJECT-TYPE
	RowStatus

aiPVCIfType		1.3.6.1.4.1.539.16.1.1.1.2
The type of subnetwork on which this PVC is to be created. Examples are frameRelay(32), and x25ple(40).
Status: current	Access: read-write
OBJECT-TYPE
	IANAifType

aiPVCIfIndex		1.3.6.1.4.1.539.16.1.1.1.3
The 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.
Status: current	Access: read-write
OBJECT-TYPE
	IfIndexType

aiPVCCircuit		1.3.6.1.4.1.539.16.1.1.1.4
The 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.
Status: current	Access: read-write
OBJECT-TYPE
	PositiveInteger

aiPVCCallTimer		1.3.6.1.4.1.539.16.1.1.1.5
The 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.
Status: current	Access: read-write
OBJECT-TYPE
	UnsignedShort

aiPVCInactivityTimer		1.3.6.1.4.1.539.16.1.1.1.6
The 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.
Status: current	Access: read-write
OBJECT-TYPE
	UnsignedShort

aiPVCConformance		1.3.6.1.4.1.539.16.1.2
OBJECT IDENTIFIER

aiPVCGroups		1.3.6.1.4.1.539.16.1.2.1
OBJECT IDENTIFIER

aiPVCCompliances		1.3.6.1.4.1.539.16.1.2.2
OBJECT IDENTIFIER

aiPVCCompliance		1.3.6.1.4.1.539.16.1.2.2.1
The compliance statement for SNMPv2 entities which have AII PVC tables.
Status: current	Access: read-write
MODULE-COMPLIANCE

aiPVCGroup		1.3.6.1.4.1.539.16.1.2.1.1
A collection of objects providing information applicable to all AII cal parameter name tables.
Status: current	Access: read-write
OBJECT-GROUP

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor