smilint output for ./INFINIBAND-MIB

Messages:

INFINIBAND-MIB

   1: -- extracted from draft-ietf-ipoib-ibif-mib-00.txt
   2: -- at Fri Oct 12 06:06:33 2001

   3: 
   4: INFINIBAND-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:        experimental, MODULE-IDENTITY,
   8:        Integer32                                   FROM SNMPv2-SMI
   9:        TEXTUAL-CONVENTION                          FROM SNMPv2-TC  
  10:        ;
  11: 
  12: infinibandMIB MODULE-IDENTITY
  13:     LAST-UPDATED "200110031200Z"  -- 3 October 2001 12:00:00
  14:     ORGANIZATION
  15:                  "IETF IP over IB Working Group 
  16:          Email:   ipoverib@ietf.org"
  17:     CONTACT-INFO
  18:                  "Bill Anderson
  19:           Postal: InfiniSwitch Corporation
  20:                   134 Flanders Road
  21:                   Westborough, MA 01581
  22:                   United States
  23:           Tel:    +1 508 599 6300
  24:           Email:  banderson@infiniswitch.com
  25:                   Bill Strahm
  26:           Postal: Sanera Systems Inc
  27:                   1925 NW Amberglen Parkway
  28:                   Suite 155
  29:                   Beaverton, OR   97006
  30:                   United States
  31:           Tel:    +1 503 601-0263
  32:           Email:  bill@sanera.net"
  33:     DESCRIPTION
  34:        "This MIB contains managed object definitions and textual
  35:         conventions for managing Infiniband devices."
  36:     -- Revision history.
  37:     REVISION    "200110031200Z"  -- 3 October 2001 12:00:00
  38:     DESCRIPTION  "Initial version of this MIB."
  39: ::= { experimental  xxx } -- To be assigned by IANA

  40: 
  41: 
  42:    -- Textual Conventions
  43:    -- Note that the IBA Port TCs are one based.
  44:    -- Making the port TCs be 1 based allows for IBA port numbers to
  45:    -- possibly parallel ifIndex which is defined to start at 1. 
  46:    -- The SNMP responder must make appropriate conversions to 
  47:    -- IBA numbering scheme.
  48: 
  49: VLIdTC ::= TEXTUAL-CONVENTION

  50:     DISPLAY-HINT "d"
  51:     STATUS      current
  52:     DESCRIPTION
  53:        "Identifies a Virtual Lane instance on a given interface. This
  54:         includes both the management and data Virtual Lanes. "
  55:     SYNTAX       Integer32(0..15)
  56: 
  57: DataVLIdTC ::= TEXTUAL-CONVENTION

  58:     DISPLAY-HINT "d"
  59:     STATUS      current
  60:     DESCRIPTION
  61:        "Identifies a Data Virtual Lane instance on a given interface.
  62:         This index exludes the management Virtual Lane."
  63:     SYNTAX       Integer32(0..14)
  64: 
  65: IBPortTC ::= TEXTUAL-CONVENTION

  66:     DISPLAY-HINT "d"
  67:     STATUS      current
  68:     DESCRIPTION
  69:        "Identifies a IBA Port. Including the management and invalid
  70:         port identifier."
  71:     SYNTAX       Integer32(1..256)                                                                                  
  72: IBPhyPortTC ::= TEXTUAL-CONVENTION

  73:     DISPLAY-HINT "d"
  74:     STATUS      current
  75:     DESCRIPTION
  76:        "Identifies a non management IBA Port. Including the invalid
  77:         port identifier.
  78:        "
  79:     SYNTAX       Integer32(2..256)                                                                                  
  80: IBValidPhyPortTC ::= TEXTUAL-CONVENTION

  81:     STATUS      current
  82:     DESCRIPTION
  83:        "Identifies a valid non management IBA Port.
  84:        "
  85:     SYNTAX       Integer32(2..255)                                                                                  
  86: LIdTC ::= TEXTUAL-CONVENTION

  87:     DISPLAY-HINT "d"
  88:     STATUS      current
  89:     DESCRIPTION
  90:        "Identifies the LID of a Desitination Port. LID value
  91:         of 0x0 is considered invalid.
  92:        "
  93:     SYNTAX       Integer32 (1..65535)  
  94: 
  95: GUIDTC::= TEXTUAL-CONVENTION

  96:     DISPLAY-HINT "1x:"
  97:     STATUS      current
  98:     DESCRIPTION
  99:        "A locally  scoped EUI-64 identifier of channel adapters,
 100:         routers, and switch management port."
 101:     SYNTAX       OCTET STRING (SIZE(8))   
 102: 
 103:    --
 104:    --  Object Identifier Assignments
 105:    --  MIB writes must coordinate their use of this OID space.
 106: END
 107: 
 108: --  
 109: --    Copyright (C) The Internet Society (2000).  All Rights Reserved.
 110: --  
 111: --    This document and translations of it may be copied and furnished to
 112: --    others, and derivative works that comment on or otherwise explain it
 113: --    or assist in its implementation may be prepared, copied, published
 114: --    and distributed, in whole or in part, without restriction of any
 115: --    kind, provided that the above copyright notice and this paragraph are
 116: --    included on all such copies and derivative works.  However, this
 117: --    document itself may not be modified in any way, such as by removing
 118: --    the copyright notice or references to the Internet Society or other
 119: --    Internet organizations, except as needed for the purpose of
 120: --    developing Internet standards in which case the procedures for
 121: --    copyrights defined in the Internet Standards process must be
 122: --    followed, or as required to translate it into languages other than
 123: --    English.
 124: --  
 125: --    The limited permissions granted above are perpetual and will not be
 126: --    revoked by the Internet Society or its successors or assigns.
 127: --  
 128: --    This document and the information contained herein is provided on an
 129: --    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
 130: --    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 131: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 132: --    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 133: --    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.            
 134: -- 6.0  Intellectual Property
 135: --  
 136: --    The IETF takes no position regarding the validity or scope of any
 137: --    intellectual property or other rights that might be claimed to
 138: --    pertain to the implementation or use of the technology described in
 139: --    this document or the extent to which any license under such rights
 140: --    might or might not be available; neither does it represent that it
 141: --    has made any effort to identify any such rights.  Information on the
 142: --    IETF's procedures with respect to rights in standards-track and
 143: --    standards- related documentation can be found in BCP-11.  Copies of
 144: --    claims of rights made available for publication and any assurances of
 145: --    licenses to be made available, or the result of an attempt made to
 146: --    obtain a general license or permission for the use of such
 147: --    proprietary rights by implementors or users of this specification can
 148: --    be obtained from the IETF Secretariat. 
 149: -- 
 150: --    The IETF invites any interested party to bring to its attention any
 151: --    copyrights, patents or patent applications, or other proprietary
 152: --    rights which may cover technology that may be required to practice
 153: --    this standard.  Please address the information to the IETF Executive
 154: --    Director. 
 155: --  
 156: -- 7.0  Author's Address
 157: --  
 158: --    Name:    Bill Anderson
 159: --    Company: Infiniswitch Corporation
 160: --    Address: 134 Flanders Road
 161: --             Westborough, MA 01581
 162: --    Phone:   978-599-6336
 163: --    EMail:   banderson@infiniswitch.com
 164: -- 
 165: -- 7.1  Known Issues
 166: --      
 167: -- 1)  Need REFERENCE clauses on object definitions to point to
 168: --    definitions in InfiniBand docs.
 169: --  
 170: -- 8.0  References
 171: -- 
 172: -- [RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
 173: --             for Describing SNMP Management Frameworks", RFC 2571, April
 174: --             1999.
 175: -- 
 176: -- [RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
 177: --             of Management Information for TCP/IP-based Internets", STD
 178: --             16, RFC 1155, May 1990.
 179: -- 
 180: -- [RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
 181: --             16, RFC 1212, March 1991.
 182: -- 
 183: -- [RFC1215]   M. Rose, "A Convention for Defining Traps for use with the
 184: --             SNMP", RFC 1215, March 1991.
 185: -- 
 186: -- [RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
 187: --             Rose, M., and S. Waldbusser, "Structure of Management
 188: --             Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999
 189: -- [RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
 190: --             Rose, M., and S. Waldbusser, "Textual Conventions for
 191: --             SMIv2", STD 58, RFC 2579, April 1999.
 192: -- 
 193: -- [RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
 194: --             Rose, M., and S. Waldbusser, "Conformance Statements for
 195: --             SMIv2", STD 58, RFC 2580, April 1999.
 196: -- 
 197: -- [RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
 198: --             Network Management Protocol", STD 15, RFC 1157, May 1990.
 199: -- 
 200: -- [RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
 201: --             "Introduction to Community-based SNMPv2", RFC 1901, January
 202: --             1996.
 203: -- 
 204: -- [RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
 205: --             "Transport Mappings for Version 2 of the Simple Network
 206: --             Management Protocol (SNMPv2)", RFC 1906, January 1996.
 207: -- 
 208: -- [RFC2572]   Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
 209: --             Processing and Dispatching for the Simple Network Management
 210: --             Protocol (SNMP)", RFC 2572, April 1999.
 211: -- 
 212: -- [RFC2574]   Blumenthal, U., and B. Wijnen, "User-based Security Model
 213: --             (USM) for version 3 of the Simple Network Management
 214: --             Protocol (SNMPv3)", RFC 2574, April 1999.
 215: -- 
 216: -- [RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
 217: --             "Protocol Operations for Version 2 of the Simple Network
 218: --             Management Protocol (SNMPv2)", RFC 1905, January 1996.
 219: -- 
 220: -- [RFC2573]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
 221: --             RFC 2573, April 1999.
 222: -- 
 223: -- [RFC2575]   Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
 224: --             Access Control Model (VACM) for the Simple Network
 225: --             Management Protocol (SNMP)", RFC 2575, April 1999.
 226: -- 
 227: -- [RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart,
 228: --             "Introduction to Version 3 of the Internet-standard Network
 229: --             Management Framework", RFC 2570, April 1999.
 230: -- --- end of Framework references

 231: -- [RFC2863]   McCloghrie, K., and Kasenholz F.,
 232: --             "The Interfaces Group MIB", RFC 2863, June 2000
 233: -- 
 234: -- [RFC2665]   Flick J.,and Johnson J.,
 235: --             "Definitions of Managed Objects for the Ethernet-like
 236: --             Interface Types", RFC 2863, August 1999
 237: -- 
 238: -- [Infini v1.0a] InfiniBand Architecture Specification, 
 239: --                Volume 1.0 Version 1.0a
 240: -- 
 241: -- This Internet draft has an expiration date  of April 12, 2002
 242: