smilint output for ./AGGREGATE-MIB


Message Severities
SeverityCount
change recommended2
Message Types
TypeCount
opaque-smiv2 (change recommended)2

Messages:

AGGREGATE-MIB

   1: -- extracted from rfc4498.txt
   2: -- at Tue May 23 06:06:19 2006
  41: 
  42:       AggrMOErrorStatus ::= TEXTUAL-CONVENTION
  43:         STATUS       current
  44:         DESCRIPTION
  45:           "This data type is used to model the error status of the
  46:            constituent MO instances.  The error status for a
  47:            constituent MO instance is given in terms of two elements:
  48:              o The moIndex, which indicates the position of the MO
  49:                instance (starting at 1) in the value of the aggregated
  50:                MO instance.
  51:              o The moError, which indicates the error that was
  52:                encountered in fetching that MO instance.
  53:            The syntax in ASN.1 Notation will be
  54:            ErrorStatus :: = SEQUENCE {
  55:               moIndex  Integer32,
  56:               moError  SnmpPduErrorStatus
  57:            }
  58:            AggrMOErrorStatus ::= SEQUENCE OF {
  59:               ErrorStatus
  60:            }
  61:            Note1: The command responder will supply values for all
  62:                   constituent MO instances, in the same order in
  63:                   which the MO instances are specified for the AgMO.
  64:                   If an error is encountered for an MO instance, then
  65:                   the corresponding value will have an ASN.1 value NULL,
  66:                   and an error will be flagged in the corresponding
  67:                   AggrMOErrorStatus object.
  68:                   Only MOs for which errors have been encountered will
  69:                   have their corresponding moIndex and moError values
  70:                   set.
  71:            Note2: The error code for the component MO instances will be
  72:                   in accordance with the SnmpPduErrorStatus TC defined
  73:                   in the DISMAN-SCHEDULE-MIB [RFC3231].
  74:            Note3: The command generator will need to know
  75:                   constituent MO instances and their order to correctly
  76:                   interpret AggrMOErrorStatus.
  77:           "
  78:         SYNTAX      Opaque (SIZE (0..1024))
  78: change recommended - warning: SMIv2 provides Opaque solely for backward-compatibility

  79: 
  80:       AggrMOValue ::= TEXTUAL-CONVENTION
  81:         STATUS       current
  82:         DESCRIPTION
  83:           "This data type is used to model the aggregate
  84:            MOs.  It will have a format dependent on the constituent
  85:            MOs, a sequence of values.  The syntax in ASN.1 Notation will
  86:            be
  87:            MOValue :: = SEQUENCE {
  88:                 value ObjectSyntax
  89:            }
  90:            where 'value' is the value of a constituent MO instance.
  91:            AggrMOValue :: = SEQUENCE OF {
  92:                MOValue
  93:            }
  94: 
  95:            Note: The command generator will need to know the
  96:            constituent MO instances and their order to
  97:            correctly interpret AggrMOValue."
  98:         SYNTAX      Opaque (SIZE (0..1024))
  98: change recommended - warning: SMIv2 provides Opaque solely for backward-compatibility