smilint output for ./DHCP-V4-RELAY-MIB

Message Severities
SeverityCount
severe19
error3
minor error1
change recommended11
warning30
Message Types
TypeCount
basetype-unknown (error)1
defval-syntax (error)1
group-membership (change recommended)11
import-unused (warning)9
inetaddress-specific (warning)2
integer-misuse (warning)2
internal-flushing (warning)17
internal-other (severe)17
object-identifier-unknown (severe)2
scalar-not-creatable (minor error)1
type-unknown (error)1

Messages:

DHCP-V4-RELAY-MIB

   1: -- extracted from draft-senthil-dhc-v4relay-mib-00.txt
   2: -- at Thu Feb 12 06:16:55 2004
   3: 
   4:         DHCP-V4-RELAY-MIB DEFINITIONS ::= BEGIN 
   5:          
   6:         IMPORTS 
   7:            Counter64, Counter32, Gauge32, Unsigned32, MODULE-IDENTITY,
   7: warning - warning: identifier `Counter64' imported from module `SNMPv2-SMI' is never used
   7: warning - warning: identifier `Gauge32' imported from module `SNMPv2-SMI' is never used 
   8:            OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE, mib-2
   8: warning - warning: identifier `NOTIFICATION-TYPE' imported from module `SNMPv2-SMI' is never used
   8: warning - warning: identifier `mib-2' imported from module `SNMPv2-SMI' is never used 
   9:               FROM SNMPv2-SMI 
  10:             
  11:            TEXTUAL-CONVENTION, DateAndTime FROM SNMPv2-TC
  11: warning - warning: identifier `TEXTUAL-CONVENTION' imported from module `SNMPv2-TC' is never used
  11: warning - warning: identifier `DateAndTime' imported from module `SNMPv2-TC' is never used 
  12:             
  13:            SnmpAdminString FROM SNMP-FRAMEWORK-MIB 
  14:            
  15:            InetAddressIPv4 FROM INET-ADDRESS-MIB 
  16:             
  17:            MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  17: warning - warning: identifier `MODULE-COMPLIANCE' imported from module `SNMPv2-CONF' is never used
  17: warning - warning: identifier `OBJECT-GROUP' imported from module `SNMPv2-CONF' is never used
  17: warning - warning: identifier `NOTIFICATION-GROUP' imported from module `SNMPv2-CONF' is never used 
  18:            FROM SNMPv2-CONF; 
  19:          
  20:          
  21:         dhcpv4Relay  MODULE-IDENTITY 
  22:            LAST-UPDATED   "200402091510Z" 
  23:            ORGANIZATION 
  24:               "IETF DHC Working Group 
  25:               General Discussion: dhcwg@ietf.org 
  26:               Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg 
  27:               Archive: http://www1.ietf.org/mailman/listinfo/dhcwg 
  28:               Chair: Ralph Droms, rdroms@cisco.com" 
  29:            CONTACT-INFO 
  30:               "        Senthil Kumar Balasubramanian
  31:                        Hewlett Packard Company,
  32:               Postal:  29 Cunnigham Road, 
  33:                        Bangalore, India 560 052 
  34:                  Tel:  +91-(80)-205-3103 
  35:                  Fax:  +91-(80)-235-2364 
  36:               E-mail:  ksenthil@india.hp.com 
  37:                
  38:                        Vijayabhaskar Annamalai Kalusivalingam,
  39:               Postal:  Hewlett Packard Company, 
  40:                        29 Cunnigham Road, 
  41:                        Bangalore, India 560 052 
  42:                  Tel:  +91-(80)-205-3085
  43:                  Fax:  +91-(80)-235-2364
  44:               E-mail:  vijayak@india.hp.com" 
  45:            DESCRIPTION 
  46:               "The MIB module for entities implementing the Relay Agent part  
  47:               of the Bootstrap Protocol (BOOTP) and the Dynamic Host 
  48:               Configuration protocol (DHCP) for Internet Protocol version 
  49:               4(IPv4).
  50:                
  51:               Copyright (C) The Internet Society (2004).  This version of 
  52:               this MIB module is part of RFC xxxx;  see the RFC itself for 
  53:               full legal notices." 
  54:               -- RFC Editor assigns xxxx and removes this comment 
  55:                
  56:            REVISION "200402091510Z" -- 09 February 2004
  57:            DESCRIPTION "Initial Version, published as RFC xxxx." 
  58:               -- RFC Editor assigns xxxx and removes this comment 
  59:            ::= { dhcp 3 } -- Work in Progress
  59: severe - unknown object identifier label `dhcp' 
  60:          
  61:         -- declare top-level MIB objects 
  62:                
  63:         dhcpv4RelayObjects  OBJECT-IDENTITY 
  64:            STATUS      current 
  65:            DESCRIPTION 
  66:               "DHCP Relay MIB identification objects are all defined 
  67:               in this branch." 
  68:         ::= { dhcpv4Relay 1 } 
  69:          
  70:         dhcpv4RelaySystem  OBJECT-IDENTITY 
  71:            STATUS      current 
  72:            DESCRIPTION 
  73:               "Group of objects that are related to the overall system." 
  74:         ::= { dhcpv4RelayObjects 1 } 
  75:          
  76:         relayCounters  OBJECT-IDENTITY 
  77:            STATUS      current 
  78:            DESCRIPTION 
  79:               "Group of objects that count various BOOTP Relay events." 
  80:         ::= { dhcpv4RelayObjects 2 } 
  81:          
  82:         dhcpv4RAIFObjects  OBJECT-IDENTITY 
  83:            STATUS      current 
  84:            DESCRIPTION 
  85:               "Objects that are associated with Relay Agent Information 
  86:               Option"
  87:            REFERENCE 
  88:               "RFC-3046 and its descendents." 
  89:         ::= { dhcpv4RelayObjects 3 } --RFC 3046 and its decesndents.
  90:         -- dhcpv4RelaySystem Group 
  91:          
  92:         dhcpv4RelaySystemDescr  OBJECT-TYPE
  92: change recommended - warning: node `dhcpv4RelaySystemDescr' must be contained in at least one conformance group 
  93:            SYNTAX      SnmpAdminString (SIZE(0..255)) 
  94:            MAX-ACCESS  read-only 
  95:            STATUS      current 
  96:            DESCRIPTION 
  97:               "A textual description of the relay.  This value should 
  98:               have the FQDN name." 
  99:            ::= { dhcpv4RelaySystem 1 } 
 100:          
 101:         dhcpv4RelaySystemObjectID  OBJECT-TYPE
 101: change recommended - warning: node `dhcpv4RelaySystemObjectID' must be contained in at least one conformance group 
 102:            SYNTAX      OBJECT IDENTIFIER 
 103:            MAX-ACCESS  read-only 
 104:            STATUS      current 
 105:            DESCRIPTION 
 106:               "The vendor's authoritative identification of the network 
 107:               management subsystem contained in this entity.  This value is 
 108:               allocated within the SMI enterprise subtree (1.3.6.1.4.1) and 
 109:               provides an easy and unambiguous means for determining what 
 110:               kind of relay is being managed.  For example, if vendor Ohso 
 111:               Soft, Inc. is assigned the subtree 1.3.6.1.4.1.4242, it may 
 112:               assign the identifier 1.3.6.1.4.1.4242.1.1 to its Ursa DHCP 
 113:               Relay." 
 114:            ::= { dhcpv4RelaySystem 2 } 
 115: 
 116: 	maxHopCountAllowed	OBJECT-TYPE
 116: change recommended - warning: node `maxHopCountAllowed' must be contained in at least one conformance group 
 117:            SYNTAX      INTEGER 
 118:            MAX-ACCESS  read-write
 118: warning - warning: use Integer32 instead of INTEGER in SMIv2 
 119:            STATUS      current 
 120:            DESCRIPTION 
 121: 	      "The maximum hop count that a DHCP/BOOTP packet can have to 
 122:  	      pass through the relay"
 123: 
 124:            ::= { dhcpv4RelaySystem 3 }          
 125:          
 126:         dhcpv4RelayandServer  OBJECT-TYPE 
 127:            SYNTAX      INTEGER { 
 128: 	               relayOnly(1), 
 129: 	               relayandServer(2),
 130:            }
 130: severe - syntax error, unexpected '}', expecting LOWERCASE_IDENTIFIER
 130: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 131:            MAX-ACCESS  read-write
 131: severe - syntax error, unexpected MAX_ACCESS 
 132:            STATUS      current 
 133:            DESCRIPTION 
 134:               "The type of the Relay. The types are:
 135:               (1) Acts only as DHCP Relay.
 136:               (2) Acts as both as DHCP Relay and Server for independent 
 137:               networks" 
 138:            ::= { dhcpv4RelaySystem 4 }
 138: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 139:            
 140: 	seconds OBJECT-TYPE
 141:            SYNTAX      Unsigned32 
 142:            MAX-ACCESS  read-write
 143:            STATUS      current 
 144:            DESCRIPTION 
 145:               "The time interval for which the relay chooses a server. In the 
 146:               subsequent "seconds" interval the relay chooses the next server
 146: severe - syntax error, unexpected LOWERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL 
 147:               in the list for relaying the packets from the clients."
 148:            ::= { dhcpv4RelaySystem 5 }
 148: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 149:      
 150:        relaySubnettoServerMapTable OBJECT-TYPE
 151: 
 152:            SYNTAX      SEQUENCE Of relaySubnettoServerMapEntry
 152: severe - syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OF or '{' 
 153:            MAX-ACCESS  read-write
 154:            STATUS      current 
 155:            DESCRIPTION 
 156:               "The list of subnets that the relay manages. This table maps the
 157:               subnets with a list of servers serving them along with the maximum
 158:               seconds value the BOOTP/DHCP packet can have to make the relay 
 159:               to choose a server, beyond which the relay chooses the next server
 160:               in the list. The server list will be an ordered list of preference."
 161:            ::= { dhcpv4RelaySystem 6 }
 161: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 162: 
 163:         relaySubnettoServerMapEntry  OBJECT-TYPE 
 164:            SYNTAX      relaySubnettoServerMapEntry
 164: severe - syntax error, unexpected LOWERCASE_IDENTIFIER 
 165:            MAX-ACCESS  read-write
 166:            STATUS      current 
 167:            DESCRIPTION 
 168:               "A logical row in the relaySubnettoServerMapEntry." 
 169:            INDEX { 
 170:               clientSubnetID
 171:            }
 171: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 172:            ::= { relaySubnettoServerMapTable 1}
 172: severe - syntax error, unexpected COLON_COLON_EQUAL
 172: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 173:          
 174:         relaySubnettoServerMapEntry ::= SEQUENCE {
 174: severe - syntax error, unexpected COLON_COLON_EQUAL, expecting OBJECT 
 175:            clientSubnetID				InetAddressIPv4,
 176: 	   serverAddress				InetAddressIPv4,
 177:            relayNetToSerMapStatus          		RowStatus
 178:         }
 178: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 179: 
 180:         clientSubnetID			OBJECT-TYPE
 180: change recommended - warning: node `clientSubnetID' must be contained in at least one conformance group
 180: warning - warning: `InetAddress' should be used instead of `InetAddressIPv4' 
 181:            SYNTAX      InetAddressIPv4 
 182:            MAX-ACCESS  read-write
 183:            STATUS      current 
 184:            DESCRIPTION 
 185:               "The subnet address of the link on which the client resides" 
 186:            ::= { relaySubnettoServerMapEntry 1 }
 186: severe - unknown object identifier label `relaySubnettoServerMapEntry' 
 187: 
 188:         serverAddress			OBJECT-TYPE
 188: change recommended - warning: node `serverAddress' must be contained in at least one conformance group
 188: warning - warning: `InetAddress' should be used instead of `InetAddressIPv4' 
 189:            SYNTAX      InetAddressIPv4 
 190:            MAX-ACCESS  read-write
 191:            STATUS      current 
 192:            DESCRIPTION 
 193:               "The address of the DHCP/BOOTP server."
 194:            ::= { relaySubnettoServerMapEntry 2 } 
 195: 
 196: 	relayNetToSerMapStatus OBJECT-TYPE
 196: error - type `RowStatus' of node `relayNetToSerMapStatus' does not resolve to a known base type
 196: change recommended - warning: node `relayNetToSerMapStatus' must be contained in at least one conformance group 
 197: 
 198:            SYNTAX      RowStatus
 199:            MAX-ACCESS  read-create
 199: error - unknown type `RowStatus' 
 200:            STATUS      current
 201:            DESCRIPTION
 202:            "The status column used for creating, modifying, and deleting instances 
 203:            of the columnar objects in the relaySubnettoServerMapEntry table."
 204:     	   DEFVAL  { active }
 204: error - default value syntax does not match object syntax 
 205:            ::= { relaySubnettoServerMapEntry 3 }
 205: minor error - scalar object must not have a `read-create' access value 
 206: 	
 207:  
 208: 
 209:      -- dhcpv4RAIFObjects Group Starts.
 210:      
 211:      dhcpv4RAIFOption  OBJECT-TYPE 
 212:            SYNTAX      INTEGER { 
 213: 	               enable(1), 
 214: 	               disable(2), 
 215:            }
 215: severe - syntax error, unexpected '}', expecting LOWERCASE_IDENTIFIER
 215: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 216:            MAX-ACCESS  read-only
 216: severe - syntax error, unexpected MAX_ACCESS 
 217:            STATUS      current 
 218:            DESCRIPTION 
 219:               "Enables/Disables addition of RAIF Option by the Relay. The values are:
 220:                (1) Enables addition of RAIF Option by the Relay.
 221:                (2) Disables addition of RAIF Option by the Relay."
 222:            REFERENCE 
 223:               "RFC-3046." 
 224:            ::= { dhcpv4RAIFObjects 1 }
 224: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 225:      
 226:      maxPktSizeWithRAIFOption OBJECT-TYPE
 226: change recommended - warning: node `maxPktSizeWithRAIFOption' must be contained in at least one conformance group 
 227:            SYNTAX      INTEGER 
 228:            MAX-ACCESS  read-write
 228: warning - warning: use Integer32 instead of INTEGER in SMIv2 
 229:            STATUS      current 
 230:            DESCRIPTION 
 231:               "Maximux size of a DHCP packet after including RAIF Option that
 232:               is allowed to pass through the Relay"
 233:            REFERENCE 
 234:               "RFC-3046." 
 235:       	   ::= { dhcpv4RAIFObjects 2 } 
 236:      	   
 237:      dhcpv4RAIFCounterObject OBJECT IDENTIFIER
 238:      	   ::= { dhcpv4RAIFObjects 3 }
 239:      	   
 240:      sizeWithRAIFExceedLimitCount 
 241:            SYNTAX      Counter32
 241: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 242:            MAX-ACCESS  read-only 
 243:            STATUS      current 
 244:            DESCRIPTION 
 245: 		"Number of DHCP packets exceeded the maximum size after including
 246: 		RAIF Option."
 247:            REFERENCE 
 248:               "RFC-2131." 
 249:       	   ::= { dhcpv4RAIFCounterObject 1 }
 249: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 250: 
 251:      relayOptionAddedCount 
 252:            SYNTAX      Counter32
 252: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 253:            MAX-ACCESS  read-only 
 254:            STATUS      current 
 255:            DESCRIPTION 
 256:               "Number of RAIF Option added by the relay while forwarding to 
 257:               the servers"
 258:            REFERENCE 
 259:               "RFC-3046." 
 260:       	   ::= { dhcpv4RAIFCounterObject 2 }
 260: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 261: 
 262:      relayOptionRemovedCount 
 263:            SYNTAX      Counter32
 263: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 264:            MAX-ACCESS  read-only 
 265:            STATUS      current 
 266:            DESCRIPTION 
 267:               "Number of RAIF Option removed by the relay while forwarding to 
 268:               the clients"
 269:            REFERENCE 
 270:               "RFC-3046." 
 271:       	   ::= { dhcpv4RAIFCounterObject 3 }
 271: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 272:       	   
 273:      incorrectRAIFOptionCount 
 274:            SYNTAX      Counter32
 274: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 275:            MAX-ACCESS  read-only 
 276:            STATUS      current 
 277:            DESCRIPTION 
 278:               "Number of incorrect RAIF Option in DHCP packet received by the
 279:               relay"
 280:            REFERENCE 
 281:               "RFC-3046." 
 282:       	   ::= { dhcpv4RAIFCounterObject 4 }
 282: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 283: 
 284: 	docsisDCISubOptionAddedCount 
 285:            SYNTAX      Counter32
 285: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 286:            MAX-ACCESS  read-only 
 287:            STATUS      current 
 288:            DESCRIPTION 
 289:               "Number of DOCSIS-DCI SubOption added by the relay while forwarding 
 290:               to the servers"
 291:            REFERENCE 
 292:               "RFC-3256." 
 293:       	   ::= { dhcpv4RAIFCounterObject 5 }
 293: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 294: 
 295: 	docsisDCISubOptionRemoved
 296:            SYNTAX      Counter32
 296: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 297:            MAX-ACCESS  read-only 
 298:            STATUS      current 
 299:            DESCRIPTION 
 300:               "Number of DOCSIS-DCI SubOption removed by the relay while forwarding 
 301:               to the servers"
 302:            REFERENCE 
 303:               "RFC-3256." 
 304:       	   ::= { dhcpv4RAIFCounterObject 6 }
 304: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 305: 
 306: 	linkSelSubOptionAddedCount	
 307:            SYNTAX      Counter32
 307: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 308:            MAX-ACCESS  read-only 
 309:            STATUS      current 
 310:            DESCRIPTION 
 311:               "Number of Link Selection SubOption added by the relay while forwarding 
 312:               to the servers"
 313:            REFERENCE 
 314:               "RFC-3527." 
 315:       	   ::= { dhcpv4RAIFCounterObject 7 }
 315: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 316: 
 317: 	linkSelSubOptionRemovedCount 
 318:            SYNTAX      Counter32
 318: severe - syntax error, unexpected SYNTAX, expecting OBJECT 
 319:            MAX-ACCESS  read-only 
 320:            STATUS      current 
 321:            DESCRIPTION 
 322:               "Number of Link Selection SubOption removed by the relay while forwarding 
 323:               to the servers"
 324:            REFERENCE 
 325:               "RFC-3527." 
 326:       	   ::= { dhcpv4RAIFCounterObject 8 }
 326: warning - warning: flushing recent incorrect declaration, see previous error(s) 
 327: 
 328:      -- relayCounters Group 
 329:          
 330:         relayToServerCount  OBJECT-TYPE
 330: change recommended - warning: node `relayToServerCount' must be contained in at least one conformance group 
 331:            SYNTAX      Counter32 
 332:            MAX-ACCESS  read-only 
 333:            STATUS      current 
 334:            DESCRIPTION 
 335:               "The number of BOOTREQUEST packets that are relayed to the servers."
 336:            REFERENCE
 337:               "RFC-2131." 
 338:            ::= { relayCounters 1 } 
 339:          
 340:         relayToClientCount  OBJECT-TYPE
 340: change recommended - warning: node `relayToClientCount' must be contained in at least one conformance group 
 341:            SYNTAX      Counter32 
 342:            MAX-ACCESS  read-only 
 343:            STATUS      current 
 344:            DESCRIPTION 
 345:               "The number of BOOTREPLY packets that are relayed back to the clients"
 346:            REFERENCE 
 347:               "RFC-2131." 
 348:            ::= { relayCounters 2 } 
 349: 
 350:         relayCountInvalids  OBJECT-TYPE
 350: change recommended - warning: node `relayCountInvalids' must be contained in at least one conformance group 
 351:            SYNTAX      Counter32 
 352:            MAX-ACCESS  read-only 
 353:            STATUS      current 
 354:            DESCRIPTION 
 355:               "The number of BOOTP packets dropped by the relay without forwarding
 356:               (e.g., hop count exceeded the limit)."
 357:            ::= { relayCounters 3 } 
 358:          
 359:      	giaddrSpoofCount OBJECT-TYPE
 359: change recommended - warning: node `giaddrSpoofCount' must be contained in at least one conformance group 
 360:            SYNTAX      Counter32
 361:            MAX-ACCESS  read-only 
 362:            STATUS      current 
 363:            DESCRIPTION 
 364:               "Number of DHCP packets arrived with giaddr spoofed the relay's 
 365:               address"
 366:        	   ::= { relayCounters 4 }
 367: 
 368:         END 
 369: 
 370: -- 
 371: --         Copyright (C), 2004, The Internet Society.  All Rights Reserved. 
 372: -- 
 373: --         This document and translations of it may be copied and furnished to 
 374: --         others, and derivative works that comment on or otherwise explain it 
 375: --         or assist in its implementation may be prepared, copied, published 
 376: --         and distributed, in whole or in part, without restriction of any 
 377: --         kind, provided that the above copyright notice and this paragraph are 
 378: --         included on all such copies and derivative works.  However, this 
 379: --         document itself may not be modified in any way, such as by removing 
 380: --         the copyright notice or references to the Internet Society or other 
 381: --         Internet organizations, except as needed for the purpose of 
 382: --         developing Internet standards in which case the procedures for 
 383: --         copyrights defined in the Internet Standards process must be 
 384: --         followed, or as required to translate it into languages other than 
 385: --         English. 
 386: -- 
 387: --         The limited permissions granted above are perpetual and will not be 
 388: --         revoked by the Internet Society or its successors or assigns. 
 389: -- 
 390: --         This document and the information contained herein is provided on an 
 391: --         "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 
 392: --         TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 
 393: --         BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 
 394: --         HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 
 395: --         MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 
 396: -- 
 397: