smilint output for ./TUNNEL-MIB
Message Severities |
Severity | Count |
warning | 1 |
Message Types |
Type | Count |
index-exceeds-too-large (warning) | 1 |
Messages:
TUNNEL-MIB
1: -- extracted from rfc4087.txt
2: -- at Sat Jun 4 06:33:32 2005
437:
438: tunnelInetConfigEntry OBJECT-TYPE
438: warning -
warning: index of row `tunnelInetConfigEntry' can exceed OID size limit by 400 subidentifier(s)
439: SYNTAX TunnelInetConfigEntry
440: MAX-ACCESS not-accessible
441: STATUS current
442: DESCRIPTION
443: "An entry (conceptual row) containing the information
444: on a particular configured tunnel. Note that there is
445: a 128 subid maximum for object OIDs. Implementers
446: need to be aware that if the total number of octets in
447: tunnelInetConfigLocalAddress and
448: tunnelInetConfigRemoteAddress exceeds 110 then OIDs of
449: column instances in this table will have more than 128
450: sub-identifiers and cannot be accessed using SNMPv1,
451: SNMPv2c, or SNMPv3. In practice this is not expected
452: to be a problem since IPv4 and IPv6 addresses will not
453: cause the limit to be reached, but if other types are
454: supported by an agent, care must be taken to ensure
455: that the sum of the lengths do not cause the limit to
456: be exceeded."
457: INDEX { tunnelInetConfigAddressType,
458: tunnelInetConfigLocalAddress,
459: tunnelInetConfigRemoteAddress,
460: tunnelInetConfigEncapsMethod,
461: tunnelInetConfigID }
462: ::= { tunnelInetConfigTable 1 }
463:
464: TunnelInetConfigEntry ::= SEQUENCE {
465: tunnelInetConfigAddressType InetAddressType,
466: tunnelInetConfigLocalAddress InetAddress,
467: tunnelInetConfigRemoteAddress InetAddress,
468: tunnelInetConfigEncapsMethod IANAtunnelType,
469: tunnelInetConfigID Integer32,
470: tunnelInetConfigIfIndex InterfaceIndexOrZero,
471: tunnelInetConfigStatus RowStatus,
472: tunnelInetConfigStorageType StorageType
473: }