smilint output for ./FORCES-MIB

Messages:

FORCES-MIB

   1: -- extracted from draft-ietf-forces-mib-05.txt
   2: -- at Sat Mar  3 06:08:23 2007

   3: 
   4:       FORCES-MIB DEFINITIONS ::= BEGIN
   5: 
   6:       IMPORTS
   7:           MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
   8:             mib-2, Integer32, Counter32
   9:             FROM SNMPv2-SMI
  10: 
  11:           TEXTUAL-CONVENTION, TimeStamp
  12:             FROM SNMPv2-TC
  13: 
  14:           MODULE-COMPLIANCE, OBJECT-GROUP,
  15:           NOTIFICATION-GROUP
  16:             FROM SNMPv2-CONF;
  17: 
  18: 
  19:       forcesMib MODULE-IDENTITY
  20:           LAST-UPDATED "200703011200Z"  -- Mar 1, 2007
  21:           ORGANIZATION "IETF Forwarding and Control Element
  22:                         Separation (ForCES) Working Group"
  23:           CONTACT-INFO
  24:               "WG Charter:
  25:                 http://www.ietf.org/html.charters/forces-charter.html
  26: 
  27:                 Mailing lists:
  28:                     General Discussion: forces@peach.ease.lsoft.com
  29:                     To Subscribe: listserv@peach.ease.lsoft.com
  30:                     In Body: subscribe forces
  31: 
  32:                 Chairs: Patrick Droz
  33:                         Email: dro@zurich.ibm.com
  34:                         David Putzolu
  35:                         Email: David.Putzolu@intel.com
  36: 
  37:                 Editor: Robert Haas
  38:                         IBM
  39:                         Email:  rha@zurich.ibm.com"
  40:           DESCRIPTION
  41:               "This MIB module contains managed object definitions
  42:                for the ForCES Protocol.
  43:                Copyright (C) The Internet Society (2007).  This
  44:                version of this MIB module is part of RFC yyyy; see
  45:                the RFC itself for full legal notices."
  46:  -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  47:           REVISION "200703011200Z"  -- Mar 01, 2007
  48:           DESCRIPTION
  49:             "Initial version, published as RFC yyyy."
  50:  -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  51:           ::= { mib-2 XXX }

  52: 
  53:  -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
  54: 
  55:  --****************************************************************
  56: 
  57:       forcesMibNotifications OBJECT IDENTIFIER ::= { forcesMib 0 }
  58:       forcesMibObjects       OBJECT IDENTIFIER ::= { forcesMib 1 }
  59:       forcesMibConformance   OBJECT IDENTIFIER ::= { forcesMib 2 }
  60: 
  61:       ForcesID ::= TEXTUAL-CONVENTION
  62:           STATUS      current
  63:           DESCRIPTION
  64:               "The ForCES identifier is a four octet quantity."
  65:           SYNTAX      OCTET STRING (SIZE (4))
  66: 
  67:       ForcesProtocolVersion ::= TEXTUAL-CONVENTION

  68:           STATUS      current
  69:           DESCRIPTION
  70:               "ForCES protocol version number.
  71:                The version numbers used are defined in the
  72:                specifications of the respective protocol:
  73:                1 - ForCESv1 [RFCzzzz]."
  74:  -- RFC Ed.: replace zzzz with actual RFC number of ForCES protocol
  75:  -- & remove this note
  76: 
  77:           SYNTAX      Integer32 (1..255)
  78:           DISPLAY-HINT "d"

  79: 
  80: -- Notifications
  81: 
  82:       forcesAssociationEntryUp NOTIFICATION-TYPE
  83:          OBJECTS     {
  84:             forcesAssociationRunningProtocolVersion
  85:          }

  86:          STATUS      current

  87:          DESCRIPTION
  88:               "This notification is generated as soon
  89:                as an association enters the UP state.
  90:                Note that these notifications are not
  91:                throttled as the CE itself should
  92:                throttle the setup of associations."
  93:          ::= { forcesMibNotifications 1 }

  94: 
  95: 
  96:        forcesAssociationEntryDown NOTIFICATION-TYPE
  97:          OBJECTS     {
  98:             forcesAssociationRunningProtocolVersion
  99:          }
 100:          STATUS      current
 101:          DESCRIPTION
 102:               "This notification is generated as soon
 103:                as an association leaves the UP state.
 104:                Note that these notifications are not
 105:                throttled as the CE itself should
 106:                throttle the setup of associations."
 107:          ::= { forcesMibNotifications 2 }
 108: 
 109:       forcesAssociationEntryUpStats NOTIFICATION-TYPE
 110:          OBJECTS     {
 111:             forcesAssociationRunningProtocolVersion,
 112:             forcesAssociationTimeUp,
 113:             forcesAssociationHBMsgSent,
 114:             forcesAssociationHBMsgReceived,
 115:             forcesAssociationOtherMsgSent,
 116:             forcesAssociationOtherMsgReceived
 117:          }
 118:          STATUS      current
 119:          DESCRIPTION
 120:               "This notification is generated as soon
 121:                as an association enters the UP state.
 122:                Note that these notifications are not
 123:                throttled as the CE itself should
 124:                throttle the setup of associations."
 125:          ::= { forcesMibNotifications 3 }
 126: 
 127:        forcesAssociationEntryDownStats NOTIFICATION-TYPE
 128:          OBJECTS     {
 129:             forcesAssociationRunningProtocolVersion,
 130:             forcesAssociationTimeUp,
 131:             forcesAssociationTimeDown,
 132:             forcesAssociationHBMsgSent,
 133:             forcesAssociationHBMsgReceived,
 134:             forcesAssociationOtherMsgSent,
 135:             forcesAssociationOtherMsgReceived
 136:             }
 137:          STATUS      current
 138:          DESCRIPTION
 139:               "This notification is generated as soon
 140:                as an association leaves the UP state.
 141:                Note that these notifications are not
 142:                throttled as the CE itself should
 143:                throttle the setup of associations."
 144:          ::= { forcesMibNotifications 4 }
 145: 
 146: -- Objects
 147: 
 148:       forcesLatestProtocolVersionSupported OBJECT-TYPE
 149:           SYNTAX      ForcesProtocolVersion
 150:           MAX-ACCESS  read-only
 151:           STATUS      current
 152:           DESCRIPTION
 153:                  "The ForCES protocol version supported by the CE.
 154:                   The current protocol version is 1.
 155:                   Note that the CE must also allow interaction
 156:                   with FEs supporting earlier versions."
 157:           ::= { forcesMibObjects 1 }
 158: 
 159:       forcesAssociations OBJECT IDENTIFIER ::= { forcesMibObjects 2 }
 160: 
 161:       forcesAssociationTable OBJECT-TYPE
 162:           SYNTAX SEQUENCE OF ForcesAssociationEntry
 163:           MAX-ACCESS not-accessible
 164:           STATUS current
 165:           DESCRIPTION
 166:                  "The (conceptual) table of associations."
 167:           ::= { forcesAssociations 1 }
 168: 
 169:       forcesAssociationEntry OBJECT-TYPE
 170:           SYNTAX ForcesAssociationEntry
 171:           MAX-ACCESS not-accessible
 172:           STATUS current
 173:           DESCRIPTION
 174:                  "A (conceptual) entry for one association."
 175:           INDEX { forcesAssociationCEID, forcesAssociationFEID }
 176:           ::= { forcesAssociationTable 1 }
 177: 
 178:       ForcesAssociationEntry ::= SEQUENCE {
 179:               forcesAssociationCEID             ForcesID,
 180:               forcesAssociationFEID             ForcesID,
 181: 
 182:               forcesAssociationRunningProtocolVersion
 183:                                           ForcesProtocolVersion,
 184: 
 185:               forcesAssociationTimeUp           TimeStamp,
 186:               forcesAssociationTimeDown         TimeStamp,
 187: 
 188:               forcesAssociationHBMsgSent        Counter32,
 189:               forcesAssociationHBMsgReceived    Counter32,
 190:               forcesAssociationOtherMsgSent     Counter32,
 191:               forcesAssociationOtherMsgReceived Counter32     }
 192: 
 193:       forcesAssociationCEID OBJECT-TYPE
 194:           SYNTAX ForcesID
 195:           MAX-ACCESS not-accessible
 196:           STATUS current
 197:           DESCRIPTION
 198:                  "The ForCES ID of the CE."
 199:           ::= { forcesAssociationEntry 1 }
 200: 
 201:       forcesAssociationFEID OBJECT-TYPE
 202:           SYNTAX ForcesID
 203:           MAX-ACCESS not-accessible
 204:           STATUS current
 205:           DESCRIPTION
 206:                  "The ForCES ID of the FE."
 207:           ::= { forcesAssociationEntry 2 }
 208: 
 209:       forcesAssociationRunningProtocolVersion OBJECT-TYPE
 210:           SYNTAX      ForcesProtocolVersion
 211:           MAX-ACCESS  read-only
 212:           STATUS      current
 213:           DESCRIPTION
 214:           "The current ForCES protocol version used in this
 215:            association.
 216:            The current protocol version is 1."
 217:           ::= { forcesAssociationEntry 3 }
 218: 
 219:       forcesAssociationTimeUp OBJECT-TYPE
 220:           SYNTAX TimeStamp
 221:           MAX-ACCESS read-only
 222:           STATUS current
 223:           DESCRIPTION
 224:                  "The value of sysUpTime at the time this
 225:                   association entered the UP state.
 226:                   If this association started prior to the last
 227:                   initialization of the network subsystem, then
 228:                   this object contains a zero value.
 229:                   This object allows to uniquely identify
 230:                   associations with the same CE and FE IDs."
 231:           ::= { forcesAssociationEntry 4 }
 232: 
 233:       forcesAssociationTimeDown OBJECT-TYPE
 234:           SYNTAX TimeStamp
 235:           MAX-ACCESS accessible-for-notify
 236:           STATUS current
 237:           DESCRIPTION
 238:                  "The value of sysUpTime at the time this
 239:                   association left the UP state."
 240:           ::= { forcesAssociationEntry 5 }
 241: 
 242:       forcesAssociationHBMsgSent OBJECT-TYPE
 243:           SYNTAX Counter32
 244:           MAX-ACCESS read-only
 245:           STATUS current
 246:           DESCRIPTION
 247:                  "A counter of how many heartbeat messages have
 248:                   have been sent by the CE on this association
 249:                   since the association entered the UP state.
 250:                   If this association started prior to the last
 251:                   initialization of the network subsystem, then
 252:                   this object contains the value since the
 253:                   initialization."
 254:           ::= { forcesAssociationEntry 6 }
 255: 
 256:       forcesAssociationHBMsgReceived OBJECT-TYPE
 257:           SYNTAX Counter32
 258:           MAX-ACCESS read-only
 259:           STATUS current
 260:           DESCRIPTION
 261:                  "A counter of how many heartbeat messages
 262:                   have been received by the CE on this association
 263:                   since the association entered the UP state.
 264:                   If this association started prior to the last
 265:                   initialization of the network subsystem, then
 266:                   this object contains the value since the
 267:                   initialization."
 268:           ::= { forcesAssociationEntry 7 }
 269: 
 270:       forcesAssociationOtherMsgSent OBJECT-TYPE
 271:           SYNTAX Counter32
 272:           MAX-ACCESS read-only
 273:           STATUS current
 274:           DESCRIPTION
 275:                  "A counter of how many messages other than
 276:                   heartbeat (i.e., config and query)
 277:                   have been sent by the CE on this association
 278:                   since the association entered the UP state.
 279:                   If this association started prior to the last
 280:                   initialization of the network subsystem, then
 281:                   this object contains the value since the
 282:                   initialization."
 283:           ::= { forcesAssociationEntry 8 }
 284: 
 285:       forcesAssociationOtherMsgReceived OBJECT-TYPE
 286:           SYNTAX Counter32
 287:           MAX-ACCESS read-only
 288:           STATUS current
 289:           DESCRIPTION
 290:                  "A counter of how many messages other than
 291:                   heartbeat (i.e., config response, query response,
 292:                   event notification, and packet redirect)
 293:                   have been received by the CE on this association
 294:                   since the association entered the UP state.
 295:                   If this association started prior to the last
 296:                   initialization of the network subsystem, then
 297:                   this object contains the value since the
 298:                   initialization."
 299:           ::= { forcesAssociationEntry 9 }
 300: 
 301: -- Conformance
 302: 
 303:       forcesMibCompliances   OBJECT IDENTIFIER
 304:                                ::= { forcesMibConformance 1 }
 305:       forcesMibGroups        OBJECT IDENTIFIER
 306:                                ::= { forcesMibConformance 2 }
 307: 
 308: -- Compliance statements
 309: 
 310:       forcesMibCompliance  MODULE-COMPLIANCE
 311:           STATUS current
 312:           DESCRIPTION
 313:             "The compliance statement for routers running ForCES and
 314:             implementing the ForCES MIB."
 315:           MODULE  -- this module
 316:             MANDATORY-GROUPS { forcesMibGroup, forcesNotificationGroup }
 317: 
 318:             GROUP forcesNotificationStatsGroup
 319:             DESCRIPTION
 320:               "Implementation of this group is recommended."
 321: 
 322:             GROUP forcesStatsGroup
 323:             DESCRIPTION
 324:               "Implementation of this group is recommended."
 325: 
 326:           ::= { forcesMibCompliances 1 }
 327: 
 328: 
 329: -- Units of conformance
 330: 
 331:       forcesNotificationGroup NOTIFICATION-GROUP
 332:           NOTIFICATIONS { forcesAssociationEntryUp,

 333:                           forcesAssociationEntryDown
 334:                         }
 335:           STATUS  current
 336:           DESCRIPTION
 337: 
 338:             "A collection of notifications for signaling important
 339:              ForCES events."
 340:           ::= { forcesMibGroups 1 }
 341: 
 342:       forcesMibGroup OBJECT-GROUP
 343:           OBJECTS { forcesLatestProtocolVersionSupported,
 344:                     forcesAssociationRunningProtocolVersion
 345:                   }
 346:           STATUS  current
 347:           DESCRIPTION
 348:             "A collection of objects to support management of ForCES
 349:              routers."
 350:         ::= { forcesMibGroups 2 }
 351: 
 352: 
 353:       forcesNotificationStatsGroup NOTIFICATION-GROUP
 354:           NOTIFICATIONS { forcesAssociationEntryUpStats,
 355:                           forcesAssociationEntryDownStats
 356:                         }
 357:           STATUS  current
 358:           DESCRIPTION
 359: 
 360:             "A collection of optional notifications for signaling
 361:              important ForCES events including statistics."
 362:           ::= { forcesMibGroups 3 }
 363: 
 364:       forcesStatsGroup OBJECT-GROUP
 365:           OBJECTS { forcesAssociationTimeUp,
 366:                     forcesAssociationTimeDown,
 367:                     forcesAssociationHBMsgSent,
 368:                     forcesAssociationHBMsgReceived,
 369:                     forcesAssociationOtherMsgSent,
 370:                     forcesAssociationOtherMsgReceived
 371:                   }
 372:           STATUS  current
 373:           DESCRIPTION
 374:             "A collection of optional objects to provide extra
 375:              information about the associations. There is no protocol
 376:              reason to keep such information, but these objects can
 377:              be very useful in debugging connectivity problems."
 378:         ::= { forcesMibGroups 4}
 379: 
 380:       END
 381: 
 382: -- 
 383: --    Copyright (C) The IETF Trust (2007).
 384: -- 
 385: --    This document is subject to the rights, licenses and restrictions
 386: --    contained in BCP 78, and except as set forth therein, the authors
 387: --    retain all their rights.
 388: -- 
 389: --    This document and the information contained herein are provided on an
 390: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 391: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
 392: --    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
 393: --    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 394: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 395: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 396: -- 
 397: -- 
 398: -- Intellectual Property
 399: -- 
 400: --    The IETF takes no position regarding the validity or scope of any
 401: --    Intellectual Property Rights or other rights that might be claimed to
 402: --    pertain to the implementation or use of the technology described in
 403: --    this document or the extent to which any license under such rights
 404: --    might or might not be available; nor does it represent that it has
 405: --    made any independent effort to identify any such rights.  Information
 406: --    on the procedures with respect to rights in RFC documents can be
 407: --    found in BCP 78 and BCP 79.
 408: -- 
 409: --    Copies of IPR disclosures made to the IETF Secretariat and any
 410: --    assurances of licenses to be made available, or the result of an
 411: --    attempt made to obtain a general license or permission for the use of
 412: --    such proprietary rights by implementers or users of this
 413: --    specification can be obtained from the IETF on-line IPR repository at
 414: --    http://www.ietf.org/ipr.
 415: -- 
 416: --    The IETF invites any interested party to bring to its attention any
 417: --    copyrights, patents or patent applications, or other proprietary
 418: --    rights that may cover technology that may be required to implement
 419: --    this standard.  Please address the information to the IETF at
 420: --    ietf-ipr@ietf.org.
 421: -- 
 422: -- 
 423: -- Acknowledgment
 424: -- 
 425: --    Funding for the RFC Editor function is provided by the IETF
 426: --    Administrative Support Activity (IASA).
 427: