smilint output for ./SNMPv2-USEC-MIB

Messages:

SNMPv2-USEC-MIB

   1: -- extracted from rfc1910.txt
   2: -- at Mon Nov 15 17:11:48 1999

  15: 
  16: usecMIB MODULE-IDENTITY
  17:     LAST-UPDATED "9601120000Z"
  18:     ORGANIZATION "IETF SNMPv2 Working Group"
  19:     CONTACT-INFO
  20:             "        Glenn W. Waters
  21: 
  22:              Postal: Bell-Northern Research, Ltd.
  23:                      P.O. Box 3511, Station C
  24:                      Ottawa, ON, K1Y 4H7
  25:                      Canada
  26: 
  27:                 Tel: +1 613 763 3933
  28: 
  29:              E-mail: gwaters@bnr.ca"
  30:     DESCRIPTION
  31:             "The MIB module for SNMPv2 entities implementing the user-
  32:             based security model."
  33:     ::= { snmpModules 6 }

  34: 
...
  40: 
  41: AgentID ::= TEXTUAL-CONVENTION

  42:     STATUS       current
  43:     DESCRIPTION
  44:             "An agent's administratively-unique identifier.
  45: 
  46:             The value for this object may not be all zeros or all 'ff'H.
  47: 
  48:             The initial value for this object may be configured via an
  49:             operator console entry or via an algorithmic function.  In
  50:             the later case, the following guidelines are recommended:
  51: 
  52:               1) The first four octets are set to the binary equivalent
  53:                  of the agent's SNMP network management private
  54:                  enterprise number as assigned by the Internet Assigned
  55:                  Numbers Authority (IANA).  For example, if Acme
  56:                  Networks has been assigned { enterprises 696 }, the
  57:                  first four octets would be assigned '000002b8'H.
  58: 
  59:               2) The remaining eight octets are the cookie whose
  60:                  contents are determined via one or more enterprise-
  61:                  specific methods.  Such methods must be designed so as
  62:                  to maximize the possibility that the value of this
  63:                  object will be unique in the agent's administrative
  64:                  domain.  For example, the cookie may be the IP address
  65:                  of the agent, or the MAC address of one of the
  66:                  interfaces, with each address suitably padded with
  67:                  random octets.  If multiple methods are defined, then
  68:                  it is recommended that the cookie be further divided
  69:                  into one octet that indicates the method being used and
  70:                  seven octets which are a function of the method."
  71:     SYNTAX     OCTET STRING (SIZE (12))
  72: 
  73: 
  74: -- the USEC Basic group
  75: --
  76: -- a collection of objects providing basic instrumentation of
  77: -- the SNMPv2 entity implementing the user-based security model
  78: 
...
  81: 
  82: agentID OBJECT-TYPE

  83:     SYNTAX     AgentID
  84:     MAX-ACCESS read-only
  85:     STATUS     current
  86:     DESCRIPTION
  87:             "The agent's administratively-unique identifier."
  88:     ::= { usecAgent 1 }
...
 108: 
 109: agentSize OBJECT-TYPE
 110:     SYNTAX     INTEGER (484..65507)

 111:     MAX-ACCESS read-only
 112:     STATUS     current
 113:     DESCRIPTION
 114:             "The maximum length in octets of an SNMPv2 message which
 115:             this agent will accept using any transport mapping."
 116:     ::= { usecAgent 4 }
 117: 
 118: 
 119: -- USEC statistics
 120: --
 121: -- a collection of objects providing basic instrumentation of
 122: -- the SNMPv2 entity implementing the user-based security model