smilint output for ./ATM-TC-MIB

Messages:

ATM-TC-MIB

   1: -- extracted from rfc2514.txt
   2: -- at Mon Nov 15 17:11:38 1999

  13: 
  14:      atmTCMIB MODULE-IDENTITY

  15:           LAST-UPDATED "9810190200Z"
  16:           ORGANIZATION "IETF AToMMIB Working Group"
  17:           CONTACT-INFO
  18:             "          Michael Noto
  19:               Postal:  3Com Corporation
  20:                        5400 Bayfront Plaza, M/S 3109
  21:                        Santa Clara, CA 95052
  22:                        USA
  23:               Tel:     +1 408 326 2218
  24:               E-mail:  mike_noto@3com.com
  25: 
  26:                        Ethan Mickey Spiegel
  27: 
  28:               Postal:  Cisco Systems
  29:                        170 W. Tasman Dr.
  30:                        San Jose, CA 95134
  31:                        USA
  32:               Tel:     +1 408 526 6408
  33:               E-mail:  mspiegel@cisco.com
  34: 
  35:                        Kaj Tesink
  36:               Postal:  Bellcore
  37:                        331 Newman Springs Road
  38:                        Red Bank, NJ 07701
  39:                        USA
  40:               Tel:     +1 732 758 5254
  41:               Fax:     +1 732 758 4177
  42:               E-mail:  kaj@bellcore.com"
  43:           DESCRIPTION
  44:            "This MIB Module provides Textual Conventions
  45:            and OBJECT-IDENTITY Objects to be used by
  46:            ATM systems."
  47:           ::= { mib-2 37 3 } -- atmMIB 3 (see [3])

  48: 
  49:      -- The Textual Conventions defined below are organized
  50:      -- alphabetically
  51: 
  52: 
  53:      AtmAddr ::= TEXTUAL-CONVENTION

  54:              DISPLAY-HINT "1x"
  55:              STATUS  current
  56:              DESCRIPTION
  57:                  "An ATM address. The semantics are implied by
  58:                  the length. The address types are: - no
  59:                  address (0 octets) - E.164 (8 octets) - NSAP
  60:                  (20 octets) In addition, when subaddresses
  61:                  are used the AtmAddr may represent the
  62:                  concatenation of address and subaddress. The
  63:                  associated address types are: - E.164, E.164
  64:                  (16 octets) - E.164, NSAP (28 octets) - NSAP,
  65:                  NSAP (40 octets) Address lengths other than
  66:                  defined in this definition imply address
  67:                  types defined elsewhere.  Note: The E.164
  68:                  address is encoded in BCD format."
  69:             SYNTAX   OCTET STRING (SIZE(0..40))
  70: 
  71: 
  72:     AtmConnCastType ::= TEXTUAL-CONVENTION

  73:             STATUS  current
  74:             DESCRIPTION
  75:               "The type of topology of a connection (point-
  76:               to-point, point-to-multipoint). In the case
  77:               of point-to-multipoint, the orientation of
  78:               this VPL or VCL in the connection.
  79:               On a host:
  80:               - p2mpRoot indicates that the host
  81:                 is the root of the p2mp connection.
  82:               - p2mpLeaf indicates that the host
  83:                 is a leaf of the p2mp connection.
  84:               On a switch interface:
  85:               - p2mpRoot indicates that cells received
  86:                 by the switching fabric from the interface
  87:                 are from the root of the p2mp connection.
  88:               - p2mpLeaf indicates that cells transmitted
  89:                 to the interface from the switching fabric
  90:                 are to the leaf of the p2mp connection."
  91:             SYNTAX   INTEGER {
  92:                p2p(1),
  93:                p2mpRoot(2),
  94:                p2mpLeaf(3)
  95:                }
  96: 
  97:     AtmConnKind ::= TEXTUAL-CONVENTION

  98:             STATUS  current
  99:             DESCRIPTION
 100:                 "The type of call control used for an ATM
 101:                 connection at a particular interface. The use
 102:                 is as follows:
 103:                    pvc(1)
 104:                       Virtual link of a PVC. Should not be
 105:                       used for an PVC/SVC (i.e., Soft PVC)
 106:                       crossconnect.
 107:                    svcIncoming(2)
 108:                       Virtual link established after a
 109:                       received signaling request to setup
 110:                       an SVC.
 111:                    svcOutgoing(3)
 112:                       Virtual link established after a
 113:                       transmitted or forwarded signaling
 114:                       request to setup an SVC.
 115:                    spvcInitiator(4)
 116:                       Virtual link at the PVC side of an
 117:                       SVC/PVC crossconnect, where the
 118:                       switch is the initiator of the Soft PVC
 119:                       setup.
 120:                    spvcTarget(5)
 121:                       Virtual link at the PVC side of an
 122:                       SVC/PVC crossconnect, where the
 123:                       switch is the target of the Soft PVC
 124:                       setup.
 125: 
 126:                 For PVCs, a pvc virtual link is always cross-
 127:                 connected to a pvc virtual link.
 128: 
 129:                 For SVCs, an svcIncoming virtual link is always cross-
 130:                 connected to an svcOutgoing virtual link.
 131: 
 132: For Soft PVCs, an spvcInitiator is either cross-connected to
 133: an svcOutgoing or an spvcTarget, and an spvcTarget is either
 134: cross-connected to an svcIncoming or an spvcInitiator."
 135:         SYNTAX   INTEGER {
 136:            pvc(1),
 137:            svcIncoming(2),
 138:            svcOutgoing(3),
 139:            spvcInitiator(4),
 140:            spvcTarget(5)
 141:            }
 142: 
 143:     AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION

 144:         STATUS   current
 145:         DESCRIPTION
 146:             "A network prefix used for ILMI address
 147:             registration.  In the case of ATM endsystem
 148:             addresses (AESAs), the network prefix is the first
 149:             13 octets of the address which includes the AFI,
 150:             IDI, and HO-DSP fields.  In the case of native
 151:             E.164 addresses, the network prefix is the entire
 152:             E.164 address encoded in 8 octets, as if it were
 153:             an E.164 IDP in an ATM endsystem address
 154:             structure."
 155:         REFERENCE
 156:             "ATM Forum, Integrated Local Management Interface
 157:                (ILMI) Specification, Version 4.0,
 158:                af-ilmi-0065.000, September 1996, Section 9
 159:              ATM Forum, ATM User-Network Interface Signalling
 160:                Specification, Version 4.0 (UNI 4.0),
 161:                af-sig-0061.000, June 1996, Section 3"
 162:         SYNTAX   OCTET STRING (SIZE(8|13))
 163: 
 164: AtmInterfaceType ::= TEXTUAL-CONVENTION

 165:         STATUS       current
 166:         DESCRIPTION
 167:             "The connection setup procedures used for the
 168:             identified interface.
 169: 
 170:             Other: Connection setup procedures other than
 171:                those listed below.
 172: 
 173:             Auto-configuration:
 174:                Indicates that the connection setup
 175:                procedures are to be determined dynamically,
 176:                or that determination has not yet been
 177:                completed. One such mechanism is via ATM
 178:                Forum ILMI auto-configuration procedures.
 179: 
 180:             ITU-T DSS2:
 181:             -  ITU-T Recommendation Q.2931, Broadband
 182:                Integrated Service Digital Network (B-ISDN)
 183:                Digital Subscriber Signalling System No.2
 184:                (DSS2) User-Network Interface (UNI) Layer 3
 185:                Specification for Basic Call/Connection
 186:                Control (September 1994)
 187:             -  ITU-T Draft Recommendation Q.2961,
 188:                B-ISDN DSS 2 Support of Additional Traffic
 189:                Parameters (May 1995)
 190: 
 191:             -  ITU-T Draft Recommendation Q.2971,
 192:                B-ISDN DSS 2 User Network Interface Layer 3
 193:                Specification for Point-to-multipoint
 194:                Call/connection Control (May 1995)
 195: 
 196:             ATM Forum UNI 3.0:
 197:                ATM Forum, ATM User-Network Interface,
 198:                Version 3.0 (UNI 3.0) Specification,
 199:                (1994).
 200: 
 201:             ATM Forum UNI 3.1:
 202:                ATM Forum, ATM User-Network Interface,
 203:                Version 3.1 (UNI 3.1) Specification,
 204:                (November 1994).
 205: 
 206:             ATM Forum UNI Signalling 4.0:
 207:                ATM Forum, ATM User-Network Interface (UNI)
 208:                Signalling Specification Version 4.0,
 209:                af-sig-0061.000 (June 1996).
 210: 
 211:             ATM Forum IISP (based on UNI 3.0 or UNI 3.1) :
 212:                Interim Inter-switch Signaling Protocol
 213:                (IISP) Specification, Version 1.0,
 214:                af-pnni-0026.000, (December 1994).
 215: 
 216:             ATM Forum PNNI 1.0 :
 217:                ATM Forum, Private Network-Network Interface
 218:                Specification, Version 1.0, af-pnni-0055.000,
 219:                (March 1996).
 220: 
 221:             ATM Forum B-ICI:
 222:                ATM Forum, B-ICI Specification, Version 2.0,
 223:                af-bici-0013.002, (November 1995).
 224: 
 225:             ATM Forum UNI PVC Only:
 226:                An ATM Forum compliant UNI with the
 227:                signalling disabled.
 228:             ATM Forum NNI PVC Only:
 229:                An ATM Forum compliant NNI with the
 230:                signalling disabled."
 231:         SYNTAX  INTEGER  {
 232:                   other(1),
 233:                   autoConfig(2),
 234:                   ituDss2(3),
 235:                   atmfUni3Dot0(4),
 236:                   atmfUni3Dot1(5),
 237:                   atmfUni4Dot0(6),
 238:                   atmfIispUni3Dot0(7),
 239:                   atmfIispUni3Dot1(8),
 240:                   atmfIispUni4Dot0(9),
 241:         atmfPnni1Dot0(10),
 242:         atmfBici2Dot0(11),
 243:         atmfUniPvcOnly(12),
 244:         atmfNniPvcOnly(13)  }
 245: 
 246: AtmServiceCategory ::= TEXTUAL-CONVENTION

 247:         STATUS  current
 248:         DESCRIPTION
 249:             "The service category for a connection."
 250:         REFERENCE
 251:             "ATM Forum Traffic Management Specification,
 252:             Version 4.0, af-tm-0056.000, June 1996."
 253:         SYNTAX   INTEGER {
 254:            other(1),   -- none of the following
 255:            cbr(2),     -- constant bit rate
 256:            rtVbr(3),   -- real-time variable bit rate
 257:            nrtVbr(4),  -- non real-time variable bit rate
 258:            abr(5),     -- available bit rate
 259:            ubr(6)      -- unspecified bit rate
 260:            }
 261: 
 262: AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION

 263:         STATUS  current
 264:         DESCRIPTION
 265:             "The value of this object identifies a row in the
 266:             atmSigDescrParamTable. The value 0 signifies that
 267:             none of the signalling parameters defined in the
 268:             atmSigDescrParamTable are applicable."
 269: 
 270:         SYNTAX  INTEGER (0..2147483647)

 271: 
 272: AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION

 273:         STATUS  current
 274:         DESCRIPTION
 275:             "The value of this object identifies a row in the
 276:             atmTrafficDescrParamTable.  The value 0 signifies
 277:             that no row has been identified."
 278:         SYNTAX  INTEGER (0..2147483647)

 279: 
 280: AtmVcIdentifier ::= TEXTUAL-CONVENTION

 281:         STATUS  current
 282:         DESCRIPTION
 283:             "The VCI value for a VCL. The maximum VCI value
 284:             cannot exceed the value allowable by
 285:             atmInterfaceMaxVciBits defined in ATM-MIB."
 286:         SYNTAX   INTEGER (0..65535)

 287: 
 288: AtmVpIdentifier ::= TEXTUAL-CONVENTION

 289:         STATUS  current
 290:         DESCRIPTION
 291:             "The VPI value for a VPL or VCL. The value VPI=0
 292:             is only allowed for a VCL. For ATM UNIs supporting
 293:             VPCs the VPI value ranges from 0 to 255.  The VPI
 294:             value 0 is supported for ATM UNIs conforming to
 295:             the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs)
 296:             specification. For ATM UNIs supporting VCCs the
 297:             VPI value ranges from 0 to 255.  For ATM NNIs the
 298:             VPI value ranges from 0 to 4095.  The maximum VPI
 299:             value cannot exceed the value allowable by
 300:             atmInterfaceMaxVpiBits defined in ATM-MIB."
 301:         SYNTAX    INTEGER (0..4095)

 302: 
 303: AtmVorXAdminStatus ::= TEXTUAL-CONVENTION

 304:         STATUS  current
 305:         DESCRIPTION
 306:             "The value determines the desired administrative
 307:             status of a virtual link or cross-connect. The up
 308:             and down states indicate that the traffic flow is
 309:             enabled or disabled respectively on the virtual
 310:             link or cross-connect."
 311:         SYNTAX   INTEGER {
 312:            up(1),
 313:            down(2)
 314:             }
 315: 
 316: AtmVorXLastChange ::= TEXTUAL-CONVENTION

 317:         STATUS  current
 318:         DESCRIPTION
 319:             "The value of MIB II's sysUpTime at the time a
 320:             virtual link or cross-connect entered its current
 321:             operational state. If the current state was
 322:             entered prior to the last re-initialization of the
 323:             agent then this object contains a zero value."
 324:         SYNTAX   TimeTicks
 325: 
 326: AtmVorXOperStatus ::= TEXTUAL-CONVENTION

 327:         STATUS  current
 328:         DESCRIPTION
 329:             "The value determines the operational status of a
 330:             virtual link or cross-connect. The up and down
 331:             states indicate that the traffic flow is enabled
 332:             or disabled respectively on the virtual link or
 333:             cross-connect. The unknown state indicates that
 334:             the state of it cannot be determined. The state
 335:             will be down or unknown if the supporting ATM
 336:             interface(s) is down or unknown respectively."
 337:         SYNTAX   INTEGER {
 338:            up(1),
 339:            down(2),
 340:            unknown(3)
 341:            }
 342: 
 343: 
 344: 
 345: 
 346: -- OBJECT-IDENTITIES:
 347: 
 348: -- The following atmTrafficDescriptorTypes has been moved
 349: -- from RFC1695 and no longer appear in the revision of
 350: -- RFC1695[3].
 351: 
 352: atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}

 353:                                             -- atmMIBObjects
 354:                                             -- See [3].
 355: 
 356: -- All other and new OBJECT IDENTITIES
 357: -- are defined under the following subtree: