-- MIB created 9/24/97 17:32:31, by -- SMIC (the next generation) version 1.6.31, December 11, 1994. -- CHANGE LOG -- 092497 schiang -- ***** NOTE ***** -- Changed the definition of AtmAddr to (0..20) due to smic -- compiler restriction, BUT THE AGENT FOLLOWS THE STATNDARD -- DEFINITIONS of (0|8|20). -- -- Changed AtmIlmiNetworkPrefix to OCTET STRING(SIZE(8 .. 13)) -- due to smic restriction. -- -- Added atmMIB and atmMIBObjects and modified the definition -- for atmTCMIB and atmTrafficDescriptorTypes. -- 'smic' does not accept {mib-2 37 3} nor {mib-2 37 1 1} -- ATM-TC-MIB DEFINITIONS ::= BEGIN -- From file: "atm-tc.mi2" -- Compile options "4 G A M" IMPORTS Integer32, TimeTicks FROM SNMPv2-SMI-v1 mib-2 FROM RFC1213-MIB; atmMIB OBJECT IDENTIFIER ::= {mib-2 37} atmMIBObjects OBJECT IDENTIFIER ::= { atmMIB 1 } atmTCMIB OBJECT IDENTIFIER ::= { atmMIB 3} -- atmTCMIB OBJECT IDENTIFIER ::= {mib-2 37 3} -- MODULE-IDENTITY -- LastUpdated -- 9701080200Z -- OrgName -- IETF AToMMIB Working Group -- ContactInfo -- Michael Noto -- Postal: Network Equipment Technologies -- 800 Saginaw Drive RM 21.1.111 -- Redwood City, CA 94063 -- USA -- Tel: +1 415 569-7134 -- E-mail: mike_noto@net.com -- -- Ethan Mickey Spiegel -- Postal: Cisco Systems -- 170 W. Tasman Dr. -- San Jose, CA 95134 -- USA -- Tel: +1 408 526 6408 -- E-mail: mspiegel@cisco.com -- -- Kaj Tesink -- Postal: Bell Communications Research -- 331 Newman Springs Road -- Red Bank, NJ 07701 -- USA -- Tel: +1 908 758 5254 -- Fax: +1 908 758 4177 -- E-mail: kaj@cc.bellcore.com -- Descr -- This MIB Module provides Textuanl Coventions -- and OBJECT-IDENTITY Objects to be used by -- ATM systems. -- 092497 schiang -- Following is the output from smicn however is not acceptable -- by smic thus need some work around. --atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= { mib-2 37 1 1 } atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= { atmMIBObjects 1 } -- All other and new OBJECT IDENTITIES go here: atmObjectIdentities OBJECT IDENTIFIER ::= { atmTCMIB 1 } atmNoTrafficDescriptor OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 1 } -- OBJECT-IDENTITY -- Status -- obsolete -- Descr -- This identifies the no ATM traffic -- descriptor type. Parameters 1, 2, 3, 4, -- and 5 are not used. This traffic descriptor -- type can be used for best effort traffic. atmNoClpNoScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 2 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for no CLP -- and no Sustained Cell Rate. The use of the -- parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: CDVT in tenths of microseconds -- Parameter 3: not used -- Parameter 4: not used -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- CBR connections following the UNI 3.0/3.1 -- conformance definition for PCR CLP=0+1 [3,4]. -- These CBR connections differ from CBR.1 -- connections [13] in that the CLR objective -- applies only to the CLP=0 cell flow. -- -- This traffic descriptor type is also -- applicable to connections following the UBR.1 -- conformance definition [13]. atmClpNoTaggingNoScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 3 } -- OBJECT-IDENTITY -- Status -- obsolete -- Descr -- This traffic descriptor is for CLP without -- tagging and no Sustained Cell Rate. The use -- of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: peak cell rate in cells/second -- for CLP=0 traffic -- Parameter 3: not used -- Parameter 4: not used -- Parameter 5: not used. atmClpTaggingNoScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 4 } -- OBJECT-IDENTITY -- Status -- obsolete -- Descr -- This traffic descriptor is for CLP with -- tagging and no Sustained Cell Rate. The use -- of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: peak cell rate in cells/second -- for CLP=0 traffic, excess -- tagged as CLP=1 -- Parameter 3: not used -- Parameter 4: not used -- Parameter 5: not used. atmNoClpScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 5 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for no CLP -- with Sustained Cell Rate. The use of the -- parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: sustainable cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 3: maximum burst size in cells -- Parameter 4: CDVT in tenths of microseconds -- Parameter 5: not used. -- -- This traffic descriptor type is applicable -- to VBR connections following the UNI 3.0/3.1 -- conformance definition for PCR CLP=0+1 and -- SCR CLP=0+1 [3,4]. These VBR connections -- differ from VBR.1 connections [13] in that -- the CLR objective applies only to the CLP=0 -- cell flow. atmClpNoTaggingScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 6 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for CLP with -- Sustained Cell Rate and no tagging. The use -- of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: sustainable cell rate in cells/second -- for CLP=0 traffic -- Parameter 3: maximum burst size in cells -- Parameter 4: CDVT in tenths of microseconds -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- connections following the VBR.2 conformance -- definition [13]. atmClpTaggingScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 7 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for CLP with -- tagging and Sustained Cell Rate. The use of -- the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: sustainable cell rate in cells/second -- for CLP=0 traffic, excess tagged as -- CLP=1 -- Parameter 3: maximum burst size in cells -- Parameter 4: CDVT in tenths of microseconds -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- connections following the VBR.3 conformance -- definition [13]. atmClpNoTaggingMcr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 8 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for CLP with -- Minimum Cell Rate and no tagging. The use of -- the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: CDVT in tenths of microseconds -- Parameter 3: minimum cell rate in cells/second -- Parameter 4: unused -- Parameter 5: unused. -- -- This traffic descriptor type is applicable to -- connections following the ABR conformance -- definition [13]. atmClpTransparentNoScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 9 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for the CLP- -- transparent model [13] and no Sustained Cell Rate. -- The use of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: CDVT in tenths of microseconds -- Parameter 3: not used -- Parameter 4: not used -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- connections following the CBR.1 conformance -- definition [13]. -- -- Connections specifying this traffic descriptor -- type will be rejected at UNI 3.0 or UNI 3.1 -- interfaces. For a similar traffic descriptor -- type that can be accepted at UNI 3.0 and -- UNI 3.1 interfaces, see atmNoClpNoScr. atmClpTransparentScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 10 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for the CLP- -- transparent model [13] with Sustained Cell Rate. -- The use of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: sustainable cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 3: maximum burst size in cells -- Parameter 4: CDVT in tenths of microseconds -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- connections following the VBR.1 conformance -- definition [13]. -- -- Connections specifying this traffic descriptor -- type will be rejected at UNI 3.0 or UNI 3.1 -- interfaces. For a similar traffic descriptor -- type that can be accepted at UNI 3.0 and -- UNI 3.1 interfaces, see atmNoClpScr. atmNoClpTaggingNoScr OBJECT IDENTIFIER ::= { atmTrafficDescriptorTypes 11 } -- OBJECT-IDENTITY -- Status -- mandatory -- Descr -- This traffic descriptor type is for no CLP -- with tagging and no Sustained Cell Rate. The -- use of the parameter vector for this type: -- Parameter 1: peak cell rate in cells/second -- for CLP=0+1 traffic -- Parameter 2: CDVT in tenths of microseconds -- Parameter 3: not used -- Parameter 4: not used -- Parameter 5: not used. -- -- This traffic descriptor type is applicable to -- connections following the UBR.2 conformance -- definition [13]. AtmAddr ::= OCTET STRING(SIZE(0..20)) --AtmAddr ::= OCTET STRING(SIZE(0 | 8 | 20)) -- TEXTUAL-CONVENTION -- DspHint -- 1x -- Status -- mandatory -- Descr -- The ATM address used by the network entity. -- The address types are: no address (0 octets), -- E.164 (8 octets), and NSAP (20 octets). -- Note: The E.164 address is encoded in BCD -- format. AtmConnCastType ::= INTEGER { p2p(1), p2mpRoot(2), p2mpLeaf(3) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The type of topology of a connection (point- -- to-point, point-to-multipoint). In the case -- of point-to-multipoint, the orientation of -- this VPL or VCL in the connection. -- On a host: -- - p2mpRoot indicates that the host -- is the root of the p2mp connection. -- - p2mpLeaf indicates that the host -- is a leaf of the p2mp connection. -- On a switch: -- - p2mpRoot indicates that cells received -- by the switching fabric from the interface -- are from the root of the p2mp connection. -- - p2mpLeaf indicates that cells transmitted -- to the interface from the switching fabric -- are to the leaf of the p2mp connection. AtmConnKind ::= INTEGER { pvc(1), svcIncoming(2), svcOutgoing(3), spvcInitiator(4), spvcTarget(5) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The use of call control. The use is as -- follows: -- pvc(1) -- Virtual link of a PVC. Should not be -- used in an PVC/SVC (i.e., SPVC) -- crossconnect. -- svcIncoming(2) -- Virtual link established after a -- received signaling request to setup -- an SVC. -- svcOutgoing(3) -- Virtual link established after a -- transmitted or forwarded signaling -- request to setup an SVC. -- spvcInitiator(4) -- Virtual link at the PVC side of an -- SVC/PVC crossconnect, where the -- switch is the initiator of the SPVC -- setup. -- spvcTarget(5) -- Virtual link at the PVC side of an -- SVC/PVC crossconnect, where the -- switch is the target of the SPVC -- setup. -- -- An spvcInitiator is always cross-connected to -- an svcOutgoing, and an spvcTarget is always -- cross-connected to an svcIncoming. AtmIlmiNetworkPrefix ::= OCTET STRING(SIZE(8..13)) --AtmIlmiNetworkPrefix ::= OCTET STRING(SIZE(8 | 13)) -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- A network prefix used for ILMI address -- registration. In the case of ATM endsystem -- addresses (AESAs), the network prefix is the first -- 13 octets of the address which includes the AFI, -- IDI, and HO-DSP fields. In the case of native -- E.164 addresses, the network prefix is the entire -- E.164 address encoded in 8 octets, as if it were -- an E.164 IDP in an ATM endsystem address -- structure. -- Refer -- ATM Forum ILMI 4.0 Section 9, -- ATM Forum UNI Signalling 4.0 Section 3 AtmInterfaceType ::= INTEGER { other(1), autoConfig(2), ituDss2(3), atmfUni3Dot0(4), atmfUni3Dot1(5), atmfUni4Dot0(6), atmfIispUni3Dot0(7), atmfIispUni3Dot1(8), atmfIispUni4Dot0(9), atmfPnni1Dot0(10), atmfBici2Dot0(11), atmfUniPvcOnly(12), atmfNniPvcOnly(13) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The connection setup procedures used for the -- identified interface. -- -- Other: Connection setup procedures other than -- those listed below. -- -- Auto-configuration: -- Indicates that the connection setup -- procedures are to be determined dynamically, -- or that determination has not yet been -- completed. One such mechanism is via ATM -- Forum ILMI auto-configuration procedures. -- -- ITU-T DSS2: -- - ITU-T Recommendation Q.2931, Broadband -- Integrated Service Digital Network (B-ISDN) -- Digital Subscriber Signalling System No.2 -- (DSS2) User-Network Interface (UNI) Layer 3 -- Specification for Basic Call/Connection -- Control (September 1994) [5] -- - ITU-T Draft Recommendation Q.2961, -- B-ISDN DSS 2 Support of Additional Traffic -- Parameters (May 1995) [8] -- -- - ITU-T Draft Recommendation Q.2971, -- B-ISDN DSS 2 User Network Interface Layer 3 -- Specification for Point-to-multipoint -- Call/connection Control (May 1995) [9] -- -- ATM Forum UNI 3.0: -- ATM Forum, ATM User-Network Interface, -- Version 3.0 (UNI 3.0) Specification, -- (1994) [3]. -- -- ATM Forum UNI 3.1: -- ATM Forum, ATM User-Network Interface, -- Version 3.1 (UNI 3.1) Specification, -- (November 1994) [4]. -- -- ATM Forum UNI Signalling 4.0: -- ATM Forum, ATM User-Network Interface (UNI) -- Signalling Specification Version 4.0, -- af-sig-0061.000 (June 1996) [7]. -- -- ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : -- Interim Inter-switch Signaling Protocol -- (IISP) Specification, Version 1.0, -- af-pnni-0026.000, (December 1994) [10]. -- -- ATM Forum PNNI 1.0 : -- ATM Forum, Private Network-Network Interface -- Specification, Version 1.0, af-pnni-0055.000, -- (March 1996) [6]. -- -- ATM Forum B-ICI: -- ATM Forum, B-ICI Specification, Version 2.0, -- af-bici-0013.002, (November 1995) [11]. -- -- ATM Forum UNI PVC Only: -- An ATM Forum compliant UNI with the -- signalling disabled. -- -- ATM Forum NNI PVC Only: -- An ATM Forum compliant NNI with the -- signalling disabled. AtmServiceCategory ::= INTEGER { other(1), cbr(2), rtVbr(3), nrtVbr(4), abr(5), ubr(6) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The service category for a connection. -- Refer -- ATM Forum Traffic Management 4.0. AtmSigDescrParamIndex ::= INTEGER(0..2147483647) -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The value of this object identifies a row in the -- atmSigDescrParamTable. The value 0 signifies that -- none of the signalling parameters defined in the -- atmSigDescrParamTable are applicable. AtmTrafficDescrParamIndex ::= INTEGER(0..2147483647) -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The value of this object identifies a row in the -- atmTrafficDescrParamTable. The value 0 signifies -- that no row has been identified. AtmVcIdentifier ::= INTEGER(0..65535) -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The VCI value for a VCL. The maximum VCI value -- cannot exceed the value allowable by -- atmInterfaceMaxVciBits defined in ATM-MIB. AtmVpIdentifier ::= INTEGER(0..4095) -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The VPI value for a VPL or VCL. The value VPI=0 -- is only allowed for a VCL. For ATM UNIs supporting -- VPCs the VPI value ranges from 1 to 255. For ATM -- UNIs supporting VCCs the VPI value ranges from 0 -- to 255. For ATM NNIs the VPI value ranges from 0 -- to 4095. The maximum VPI value cannot exceed the -- value allowable by atmInterfaceMaxVpiBits defined -- in ATM-MIB. AtmVorXAdminStatus ::= INTEGER { up(1), down(2) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The value determines the desired administrative -- status of a virtual link or cross-connect. The up -- and down states indicate that the traffic flow is -- enabled or disabled respectively on the virtual -- link or cross-connect. AtmVorXLastChange ::= TimeTicks -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The value of MIB II's sysUpTime at the time this -- virtual link or cross-connect entered its current -- operational state. If the current state was -- entered prior to the last re-initialization of the -- agent then this object contains a zero value. AtmVorXOperStatus ::= INTEGER { up(1), down(2), unknown(3) } -- TEXTUAL-CONVENTION -- Status -- mandatory -- Descr -- The value determines the operational status of a -- virtual link or cross-connect. The up and down -- states indicate that the traffic flow is enabled -- or disabled respectively on the virtual link or -- cross-connect. The unknown state indicates that -- the state of it cannot be determined. The state -- will be down or unknown if the supporting ATM -- interface(s) is down or unknown respectively. END