smilint output for ./TRIP-MIB
Message Severities |
Severity | Count |
warning | 2 |
Message Types |
Type | Count |
index-exceeds-too-large (warning) | 2 |
Messages:
TRIP-MIB
1: -- extracted from rfc3872.txt
2: -- at Sat Sep 18 06:23:14 2004
342:
343: tripRouteTypeEntry OBJECT-TYPE
343: warning -
warning: index of row `tripRouteTypeEntry' can exceed OID size limit by 144 subidentifier(s)
344: SYNTAX TripRouteTypeEntry
345: MAX-ACCESS not-accessible
346: STATUS current
347: DESCRIPTION
348: "An entry containing information about the route type
349: that a particular TRIP entity supports. Each entry
350: represents information about either the local or a remote
351: LS peer. The object tripRouteTypePeer is used to
352: distinguish this. In the case of a local LS, the
353: address/port information will reflect the values
354: configured in tripCfgTable. In the case of a remote
355: peer, the address/port information will reflect the
356: values of an entry in the tripPeerTable.
357:
358: Implementation need to be aware that if the size of
359: tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column
360: instances in this table will have more than 128 sub-IDs
361: and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3."
362: INDEX { applIndex,
363: tripRouteTypeAddrInetType,
364: tripRouteTypeAddr,
365: tripRouteTypePort,
366: tripRouteTypeProtocolId,
367: tripRouteTypeAddrFamilyId }
368: ::= { tripRouteTypeTable 1 }
369:
370: TripRouteTypeEntry ::= SEQUENCE {
371: tripRouteTypeAddrInetType InetAddressType,
372: tripRouteTypeAddr InetAddress,
373: tripRouteTypePort InetPortNumber,
374: tripRouteTypeProtocolId TripAppProtocol,
375: tripRouteTypeAddrFamilyId TripAddressFamily,
376: tripRouteTypePeer INTEGER
377: }
...
532:
533: tripPeerEntry OBJECT-TYPE
533: warning -
warning: index of row `tripPeerEntry' can exceed OID size limit by 142 subidentifier(s)
534: SYNTAX TripPeerEntry
535: MAX-ACCESS not-accessible
536: STATUS current
537: DESCRIPTION
538: "Entry containing information about the connection with
539: a TRIP peer.
540:
541: Implementation need to be aware that if the size of
542: tripPeerRemoteAddr exceeds 113 sub-IDs, then OIDs of
543: column instances in this table will have more than 128
544: sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or
545: snmpv3."
546: INDEX { applIndex,
547: tripPeerRemoteAddrInetType,
548: tripPeerRemoteAddr,
549: tripPeerRemotePort }
550: ::= {tripPeerTable 1}
551:
552: TripPeerEntry ::= SEQUENCE {
553: tripPeerRemoteAddrInetType InetAddressType,
554: tripPeerRemoteAddr InetAddress,
555: tripPeerRemotePort InetPortNumber,
556: tripPeerIdentifier TripId,
557: tripPeerState INTEGER,
558: tripPeerAdminStatus INTEGER,
559: tripPeerNegotiatedVersion TripProtocolVersion,
560: tripPeerSendReceiveMode TripSendReceiveMode,
561: tripPeerRemoteItad TripItad,
562: tripPeerConnectRetryInterval Unsigned32,
563: tripPeerMaxRetryInterval Unsigned32,
564: tripPeerHoldTime Unsigned32,
565: tripPeerKeepAlive Unsigned32,
566: tripPeerHoldTimeConfigured Unsigned32,
567: tripPeerKeepAliveConfigured Unsigned32,
568: tripPeerMaxPurgeTime Unsigned32,
569: tripPeerDisableTime Unsigned32,
570: tripPeerLearned TruthValue,
571: tripPeerStorage StorageType,
572: tripPeerRowStatus RowStatus
573: }