smilint output for ./MIOX25-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 1 |
| change recommended | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| default-too-long-smiv1 (change recommended) | 2 |
| index-element-no-range (error) | 1 |
Messages:
MIOX25-MIB
1: -- extracted from rfc1461.txt
2: -- at Mon Nov 15 17:11:56 1999
3:
4: MIOX25-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: Counter,
8: TimeTicks
9: FROM RFC1155-SMI
10: OBJECT-TYPE
11: FROM RFC-1212
12: DisplayString, transmission,
13: ifIndex
14: FROM RFC1213-MIB
15: InstancePointer
16: FROM RFC1316-MIB
17: X121Address
18: FROM RFC1382-MIB
19: PositiveInteger
20: FROM RFC1381-MIB;
21:
22: -- IP over X.25 MIB
23:
24: miox OBJECT IDENTIFIER ::= { transmission 38 }
25:
26: mioxPle OBJECT IDENTIFIER ::= { miox 1 }
27: mioxPeer OBJECT IDENTIFIER ::= { miox 2 }
28:
29: -- ###########################################################
30: -- Ple Table
31: -- ###########################################################
32:
33: -- Systems that implement RFC 1356 must also implement
34: -- all objects in this group.
35:
36: mioxPleTable OBJECT-TYPE
37: SYNTAX SEQUENCE OF MioxPleEntry
38: ACCESS not-accessible
39: STATUS mandatory
40: DESCRIPTION
41: "This table contains information relative to
42: an interface to an X.25 Packet Level Entity
43: (PLE)."
44: ::= { mioxPle 1 }
45:
46: mioxPleEntry OBJECT-TYPE
46: error -
index element `RFC1213-MIB::ifIndex' of row `mioxPleEntry' must have a range restriction
47: SYNTAX MioxPleEntry
48: ACCESS not-accessible
49: STATUS mandatory
50: DESCRIPTION
51: "These objects manage the encapsulation of
52: other protocols within X.25."
53: INDEX { ifIndex }
54: ::= { mioxPleTable 1 }
55:
56: MioxPleEntry ::= SEQUENCE {
57: mioxPleMaxCircuits
58: INTEGER,
59: mioxPleRefusedConnections
60: Counter,
61: mioxPleEnAddrToX121LkupFlrs
62: Counter,
63: mioxPleLastFailedEnAddr
64: OCTET STRING,
65: mioxPleEnAddrToX121LkupFlrTime
66: TimeTicks,
67: mioxPleX121ToEnAddrLkupFlrs
68: Counter,
69: mioxPleLastFailedX121Address
70: X121Address,
71: mioxPleX121ToEnAddrLkupFlrTime
72: TimeTicks,
73: mioxPleQbitFailures
74: Counter,
75: mioxPleQbitFailureRemoteAddress
76: X121Address,
77: mioxPleQbitFailureTime
78: TimeTicks,
79: mioxPleMinimumOpenTimer
80: PositiveInteger,
81: mioxPleInactivityTimer
82: PositiveInteger,
83: mioxPleHoldDownTimer
84: PositiveInteger,
85: mioxPleCollisionRetryTimer
86: PositiveInteger,
87: mioxPleDefaultPeerId
88: InstancePointer
89: }
90:
91: mioxPleMaxCircuits OBJECT-TYPE
92: SYNTAX INTEGER (0..2147483647)
93: ACCESS read-write
94: STATUS mandatory
95: DESCRIPTION
96: "The maximum number of X.25 circuits that
97: can be open at one time for this interface.
98: A value of zero indicates the interface will
99: not allow any additional circuits (as it may
100: soon be shutdown). A value of 2147483647
101: allows an unlimited number of circuits."
102: ::= { mioxPleEntry 1 }
103:
104: mioxPleRefusedConnections OBJECT-TYPE
105: SYNTAX Counter
106: ACCESS read-only
107: STATUS mandatory
108: DESCRIPTION
109: "The number of X.25 calls from a remote
110: systems to this system that were cleared by
111: this system. The interface instance should
112: identify the X.25 interface the call came in
113: on."
114: ::= { mioxPleEntry 2 }
115:
116: mioxPleEnAddrToX121LkupFlrs OBJECT-TYPE
117: SYNTAX Counter
118: ACCESS read-only
119: STATUS mandatory
120: DESCRIPTION
121: "The number of times a translation from an
122: Encapsulated Address to an X.121 address
123: failed to find a corresponding X.121
124: address. Encapsulated addresses can be
125: looked up in the mioxPeerTable or translated
126: via an algorithm as for the DDN. Addresses
127: that are successfully recognized do not
128: increment this counter. Addresses that are
129: not recognized (reflecting an abnormal
130: packet delivery condition) increment this
131: counter.
132:
133: If an address translation fails, it may be
134: difficult to determine which PLE entry
135: should count the failure. In such cases the
136: first likely entry in this table should be
137: selected. Agents should record the failure
138: even if they are unsure which PLE should be
139: associated with the failure."
140: ::= { mioxPleEntry 3 }
141:
142: mioxPleLastFailedEnAddr OBJECT-TYPE
143: SYNTAX OCTET STRING (SIZE(2..128))
144: ACCESS read-only
145: STATUS mandatory
146: DESCRIPTION
147: "The last Encapsulated address that failed
148: to find a corresponding X.121 address and
149: caused mioxPleEnAddrToX121LkupFlrs to be
150: incremented. The first octet of this object
151: contains the encapsulation type, the
152: remaining octets contain the address of that
153: type that failed. Thus for an IP address,
154: the length will be five octets, the first
155: octet will contain 204 (hex CC), and the
156: last four octets will contain the IP
157: address. For a snap encapsulation, the
158: first byte would be 128 (hex 80) and the
159: rest of the octet string would have the snap
160: header."
161: ::= { mioxPleEntry 4 }
162:
163: mioxPleEnAddrToX121LkupFlrTime OBJECT-TYPE
164: SYNTAX TimeTicks
165: ACCESS read-only
166: STATUS mandatory
167: DESCRIPTION
168: "The most recent value of sysUpTime when the
169: translation from an Encapsulated Address to
170: X.121 address failed to find a corresponding
171: X.121 address."
172: ::= { mioxPleEntry 5 }
173:
174:
175: mioxPleX121ToEnAddrLkupFlrs OBJECT-TYPE
176: SYNTAX Counter
177: ACCESS read-only
178: STATUS mandatory
179: DESCRIPTION
180: "The number of times the translation from an
181: X.121 address to an Encapsulated Address
182: failed to find a corresponding Encapsulated
183: Address. Addresses successfully recognized
184: by an algorithm do not increment this
185: counter. This counter reflects the number
186: of times call acceptance encountered the
187: abnormal condition of not recognizing the
188: peer."
189: ::= { mioxPleEntry 6 }
190:
191: mioxPleLastFailedX121Address OBJECT-TYPE
192: SYNTAX X121Address
193: ACCESS read-only
194: STATUS mandatory
195: DESCRIPTION
196: "The last X.121 address that caused
197: mioxPleX121ToEnAddrLkupFlrs to increase."
198: ::= { mioxPleEntry 7 }
199:
200: mioxPleX121ToEnAddrLkupFlrTime OBJECT-TYPE
201: SYNTAX TimeTicks
202: ACCESS read-only
203: STATUS mandatory
204: DESCRIPTION
205: "The most recent value of sysUpTime when the
206: translation from an X.121 address to an
207: Encapsulated Address failed to find a
208: corresponding Encapsulated Address."
209: ::= { mioxPleEntry 8 }
210:
211: mioxPleQbitFailures OBJECT-TYPE
212: SYNTAX Counter
213: ACCESS read-only
214: STATUS mandatory
215: DESCRIPTION
216: "The number of times a connection was closed
217: because of a Q-bit failure."
218: ::= { mioxPleEntry 9 }
219:
220: mioxPleQbitFailureRemoteAddress OBJECT-TYPE
221: SYNTAX X121Address
222: ACCESS read-only
223: STATUS mandatory
224: DESCRIPTION
225: "The remote address of the most recent
226: (last) connection that was closed because of
227: a Q-bit failure."
228: ::= { mioxPleEntry 10 }
229:
230: mioxPleQbitFailureTime OBJECT-TYPE
231: SYNTAX TimeTicks
232: ACCESS read-only
233: STATUS mandatory
234: DESCRIPTION
235: "The most recent value of sysUpTime when a
236: connection was closed because of a Q-bit
237: failure. This will also be the last time
238: that mioxPleQbitFailures was incremented."
239: ::= { mioxPleEntry 11 }
240:
241: mioxPleMinimumOpenTimer OBJECT-TYPE
242: SYNTAX PositiveInteger
243: ACCESS read-write
244: STATUS mandatory
245: DESCRIPTION
246: "The minimum time in milliseconds this
247: interface will keep a connection open before
248: allowing it to be closed. A value of zero
249: indicates no timer."
250: DEFVAL { 0 }
251: ::= { mioxPleEntry 12 }
252:
253: mioxPleInactivityTimer OBJECT-TYPE
254: SYNTAX PositiveInteger
255: ACCESS read-write
256: STATUS mandatory
257: DESCRIPTION
258: "The amount of time time in milliseconds
259: this interface will keep an idle connection
260: open before closing it. A value of
261: 2147483647 indicates no timer."
262: DEFVAL { 10000 }
263: ::= { mioxPleEntry 13 }
264:
265: mioxPleHoldDownTimer OBJECT-TYPE
266: SYNTAX PositiveInteger
267: ACCESS read-write
268: STATUS mandatory
269: DESCRIPTION
270: "The hold down timer in milliseconds. This
271: is the minimum amount of time to wait before
272: trying another call to a host that was
273: previously unsuccessful. A value of
274: 2147483647 indicates the host will not be
275: retried."
276: DEFVAL { 0 }
277: ::= { mioxPleEntry 14 }
278:
279: mioxPleCollisionRetryTimer OBJECT-TYPE
280: SYNTAX PositiveInteger
281: ACCESS read-write
282: STATUS mandatory
283: DESCRIPTION
284: "The Collision Retry Timer in milliseconds.
285: The time to delay between call attempts when
286: the maximum number of circuits is exceeded
287: in a call attempt."
288: DEFVAL { 0 }
289: ::= { mioxPleEntry 15 }
290:
291:
292: mioxPleDefaultPeerId OBJECT-TYPE
293: SYNTAX InstancePointer
294: ACCESS read-write
295: STATUS mandatory
296: DESCRIPTION
297: "This identifies the instance of the index
298: in the mioxPeerTable for the default
299: parameters to use with this interface.
300:
301: The entry identified by this object may have
302: a zero length Encapsulation address and a
303: zero length X.121 address.
304:
305: These default parameters are used with
306: connections to hosts that do not have
307: entries in the mioxPeerTable. Such
308: connections occur when using ddn-x25 IP-X.25
309: address mapping or when accepting
310: connections from other hosts not in the
311: mioxPeerTable.
312:
313: The mioxPeerEncTable entry with the same
314: index as the mioxPeerTable entry specifies
315: the call encapsulation types this PLE will
316: accept for peers not in the mioxPeerTable.
317: If the mioxPeerEncTable doesn't contain any
318: entries, this PLE will not accept calls from
319: entries not in the mioxPeerTable."
320: ::= { mioxPleEntry 16 }
321:
322:
323:
324: -- ###########################################################
325: -- Peer Table
326: -- ###########################################################
327: -- Systems that implement RFC 1356 must also implement
328: -- all objects in this group.
329:
330: mioxPeerTable OBJECT-TYPE
331: SYNTAX SEQUENCE OF MioxPeerEntry
332: ACCESS not-accessible
333: STATUS mandatory
334: DESCRIPTION
335: "This table contains information about the
336: possible peers this machine may exchange
337: packets with."
338: ::= { mioxPeer 1 }
339:
340: mioxPeerEntry OBJECT-TYPE
341: SYNTAX MioxPeerEntry
342: ACCESS not-accessible
343: STATUS mandatory
344: DESCRIPTION
345: "Per peer information."
346: INDEX { mioxPeerIndex }
347: ::= { mioxPeerTable 1 }
348:
349:
350: MioxPeerEntry ::= SEQUENCE {
351: mioxPeerIndex
352: PositiveInteger,
353: mioxPeerStatus
354: INTEGER,
355: mioxPeerMaxCircuits
356: PositiveInteger,
357: mioxPeerIfIndex
358: PositiveInteger,
359: mioxPeerConnectSeconds
360: Counter,
361: mioxPeerX25CallParamId
362: InstancePointer,
363: mioxPeerEnAddr
364: OCTET STRING,
365: mioxPeerX121Address
366: X121Address,
367: mioxPeerX25CircuitId
368: InstancePointer,
369: mioxPeerDescr
370: DisplayString
371: }
372:
373: mioxPeerIndex OBJECT-TYPE
374: SYNTAX PositiveInteger
375: ACCESS read-only
376: STATUS mandatory
377: DESCRIPTION
378: "An index value that distinguished one entry
379: from another. This index is independent of
380: any other index."
381: ::= { mioxPeerEntry 1 }
382:
383: -- Systems can claim conformance with this MIB without
384: -- implementing sets to mioxPeerStatus with a value of
385: -- clearCall or makeCall.
386: -- All other defined values must be accepted.
387: -- Implementors should realize that allowing these values
388: -- provides richer management, and implementations
389: -- are encouraged to accept these values.
390: mioxPeerStatus OBJECT-TYPE
391: SYNTAX INTEGER {
392: valid (1),
393: createRequest (2),
394: underCreation (3),
395: invalid (4),
396: clearCall (5),
397: makeCall (6)
398: }
399: ACCESS read-write
400: STATUS mandatory
401: DESCRIPTION
402: "This reports the status of a peer entry.
403: A value of valid indicates a normal entry
404: that is in use by the agent. A value of
405: underCreation indicates a newly created
406: entry which isn't yet in use because the
407: creating management station is still setting
408: values.
409:
410: The value of invalid indicates the entry is
411: no longer in use and the agent is free to
412: delete the entry at any time. A management
413: station is also free to use an entry in the
414: invalid state.
415:
416: Entries are created by setting a value of
417: createRequest. Only non-existent or invalid
418: entries can be set to createRequest. Upon
419: receiving a valid createRequest, the agent
420: will create an entry in the underCreation
421: state. This object can not be set to a
422: value of underCreation directly, entries can
423: only be created by setting a value of
424: createRequest. Entries that exist in other
425: than the invalid state can not be set to
426: createRequest.
427:
428: Entries with a value of underCreation are
429: not used by the system and the management
430: station can change the values of other
431: objects in the table entry. Management
432: stations should also remember to configure
433: values in the mioxPeerEncTable with the same
434: peer index value as this peer entry.
435:
436: An entry in the underCreation state can be
437: set to valid or invalid. Entries in the
438: underCreation state will stay in that state
439: until 1) the agent times them out, 2) they
440: are set to valid, 3) they are set to
441: invalid. If an agent notices an entry has
442: been in the underCreation state for an
443: abnormally long time, it may decide the
444: management station has failed and invalidate
445: the entry. A prudent agent will understand
446: that the management station may need to wait
447: for human input and will allow for that
448: possibility in its determination of this
449: abnormally long period.
450:
451: Once a management station has completed all
452: fields of an entry, it will set a value of
453: valid. This causes the entry to be
454: activated.
455:
456: Entries in the valid state may also be set
457: to makeCall or clearCall to make or clear
458: X.25 calls to the peer. After such a set
459: request the entry will still be in the valid
460: state. Setting a value of makeCall causes
461: the agent to initiate an X.25 call request
462: to the peer specified by the entry. Setting
463: a value of clearCall causes the agent to
464: initiate clearing one X.25 call present to
465: the peer. Each set request will initiate
466: another call or clear request (up to the
467: maximum allowed); this means that management
468: stations that fail to get a response to a
469: set request should query to see if a call
470: was in fact placed or cleared before
471: retrying the request. Entries not in the
472: valid state can not be set to makeCall or
473: clearCall.
474:
475: The values of makeCall and clearCall provide
476: for circuit control on devices which perform
477: Ethernet Bridging using static circuit
478: assignment without address recognition;
479: other devices which dynamically place calls
480: based on destination addresses may reject
481: such requests.
482:
483: An agent that (re)creates a new entry
484: because of a set with createRequest, should
485: also (re)create a mioxPeerEncTable entry
486: with a mioxPeerEncIndex of 1, and a
487: mioxPeerEncType of 204 (hex CC)."
488: ::= { mioxPeerEntry 2 }
489:
490: mioxPeerMaxCircuits OBJECT-TYPE
491: SYNTAX PositiveInteger
492: ACCESS read-write
493: STATUS mandatory
494: DESCRIPTION
495: "The maximum number of X.25 circuits allowed
496: to this peer."
497: DEFVAL { 1 }
498: ::= { mioxPeerEntry 3 }
499:
500: mioxPeerIfIndex OBJECT-TYPE
501: SYNTAX PositiveInteger
502: ACCESS read-write
503: STATUS mandatory
504: DESCRIPTION
505: "The value of the ifIndex object for the
506: interface to X.25 to use to call the peer."
507: DEFVAL { 1 }
508: ::= { mioxPeerEntry 4 }
509:
510: mioxPeerConnectSeconds OBJECT-TYPE
511: SYNTAX Counter
512: ACCESS read-only
513: STATUS mandatory
514: DESCRIPTION
515: "The number of seconds a call to this peer
516: was active. This counter will be
517: incremented by one for every second a
518: connection to a peer was open. If two calls
519: are open at the same time, one second of
520: elapsed real time will results in two
521: seconds of connect time."
522: ::= { mioxPeerEntry 5 }
523:
524: mioxPeerX25CallParamId OBJECT-TYPE
525: SYNTAX InstancePointer
526: ACCESS read-write
527: STATUS mandatory
528: DESCRIPTION
529: "The instance of the index object in the
530: x25CallParmTable from RFC 1382 for the X.25
531: call parameters used to communicate with the
532: remote host. The well known value {0 0}
533: indicates no call parameters specified."
534: DEFVAL { {0 0} }
534: change recommended -
warning: object identifier default values in form of sub-identifier sequences are not implemented
535: ::= { mioxPeerEntry 6 }
536:
537: mioxPeerEnAddr OBJECT-TYPE
538: SYNTAX OCTET STRING (SIZE (0..128))
539: ACCESS read-write
540: STATUS mandatory
541: DESCRIPTION
542: "The Encapsulation address of the remote
543: host mapped by this table entry. A length
544: of zero indicates the remote IP address is
545: unknown or unspecified for use as a PLE
546: default.
547:
548: The first octet of this object contains the
549: encapsulation type, the remaining octets
550: contain an address of that type. Thus for
551: an IP address, the length will be five
552: octets, the first octet will contain 204
553: (hex CC), and the last four octets will
554: contain the IP address. For a snap
555: encapsulation, the first byte would be 128
556: (hex 80) and the rest of the octet string
557: would have the snap header."
558: DEFVAL { ''h }
559: ::= { mioxPeerEntry 7 }
560:
561: mioxPeerX121Address OBJECT-TYPE
562: SYNTAX X121Address
563: ACCESS read-write
564: STATUS mandatory
565: DESCRIPTION
566: "The X.25 address of the remote host mapped
567: by this table entry. A zero length string
568: indicates the X.25 address is unspecified
569: for use as the PLE default."
570: DEFVAL { ''h }
571: ::= { mioxPeerEntry 8 }
572:
573: -- Systems can claim conformance to this MIB without
574: -- implementing sets to mioxPeerX25CircuitId.
575: -- However systems that use PVCs with RFC1356
576: -- are encouraged to implement sets.
577: mioxPeerX25CircuitId OBJECT-TYPE
578: SYNTAX InstancePointer
579: ACCESS read-write
580: STATUS mandatory
581: DESCRIPTION
582: "This object identifies the instance of the
583: index for the X.25 circuit open to the peer
584: mapped by this table entry. The well known
585: value {0 0} indicates no connection
586: currently active. For multiple connections,
587: this identifies the index of a multiplexing
588: table entry for the connections. This can
589: only be written to configure use of PVCs
590: which means the identified circuit table
591: entry for a write must be a PVC."
592: DEFVAL { {0 0} }
592: change recommended -
warning: object identifier default values in form of sub-identifier sequences are not implemented
593: ::= { mioxPeerEntry 9 }
594:
595: mioxPeerDescr OBJECT-TYPE
596: SYNTAX DisplayString (SIZE (0..255))
597: ACCESS read-write
598: STATUS mandatory
599: DESCRIPTION
600: "This object returns any identification
601: information about the peer. An agent may
602: supply the comment information found in the
603: configuration file entry for this peer. A
604: zero length string indicates no information
605: available."
606: DEFVAL { ''h }
607: ::= { mioxPeerEntry 10 }
608:
609:
610:
611: -- ###########################################################
612: -- Peer Encapsulation Table
613: -- ###########################################################
614: mioxPeerEncTable OBJECT-TYPE
615: SYNTAX SEQUENCE OF MioxPeerEncEntry
616: ACCESS not-accessible
617: STATUS mandatory
618: DESCRIPTION
619: "This table contains the list of
620: encapsulations used to communicate with a
621: peer. This table has two indexes, the first
622: identifies the peer, the second
623: distinguishes encapsulation types.
624:
625: The first index identifies the corresponding
626: entry in the mioxPeerTable. The second
627: index gives the priority of the different
628: encapsulations.
629:
630: The encapsulation types are ordered in
631: priority order. For calling a peer, the
632: first entry (mioxPeerEncIndex of 1) is tried
633: first. If the call doesn't succeed because
634: the remote host clears the call due to
635: incompatible call user data, the next entry
636: in the list is tried. Each entry is tried
637: until the list is exhausted.
638:
639: For answering a call, the encapsulation type
640: requested by the peer must be found the list
641: or the call will be refused. If there are
642: no entries in this table for a peer, all
643: call requests from the peer will be refused.
644:
645: Objects in this table can only be set when
646: the mioxPeerStatus object with the same
647: index has a value of underCreation. When
648: that status object is set to invalid and
649: deleted, the entry in this table with that
650: peer index must also be deleted."
651: ::= { mioxPeer 2 }
652:
653: mioxPeerEncEntry OBJECT-TYPE
654: SYNTAX MioxPeerEncEntry
655: ACCESS not-accessible
656: STATUS mandatory
657: DESCRIPTION
658: "Per connection information."
659: INDEX { mioxPeerIndex, mioxPeerEncIndex}
660: ::= { mioxPeerEncTable 1 }
661:
662: MioxPeerEncEntry ::= SEQUENCE {
663: mioxPeerEncIndex
664: PositiveInteger,
665: mioxPeerEncType
666: INTEGER
667: }
668:
669: mioxPeerEncIndex OBJECT-TYPE
670: SYNTAX PositiveInteger
671: ACCESS read-only
672: STATUS mandatory
673: DESCRIPTION
674: "The second index in the table which
675: distinguishes different encapsulation
676: types."
677: ::= { mioxPeerEncEntry 1 }
678:
679: mioxPeerEncType OBJECT-TYPE
680: SYNTAX INTEGER (0..256)
681: ACCESS read-write
682: STATUS mandatory
683: DESCRIPTION
684: "The value of the encapsulation type. For
685: IP encapsulation this will have a value of
686: 204 (hex CC). For SNAP encapsulated
687: packets, this will have a value of 128 (hex
688: 80). For CLNP, ISO 8473, this will have a
689: value of 129 (hex 81). For ES-ES, ISO 9542,
690: this will have a value of 130 (hex 82). A
691: value of 197 (hex C5) identifies the Blacker
692: X.25 encapsulation. A value of 0,
693: identifies the Null encapsulation.
694:
695: This value can only be written when the
696: mioxPeerStatus object with the same
697: mioxPeerIndex has a value of underCreation.
698: Setting this object to a value of 256
699: deletes the entry. When deleting an entry,
700: all other entries in the mioxPeerEncTable
701: with the same mioxPeerIndex and with an
702: mioxPeerEncIndex higher then the deleted
703: entry, will all have their mioxPeerEncIndex
704: values decremented by one."
705: ::= { mioxPeerEncEntry 2 }
706:
707: -- ###########################################################
708:
709: END