smilint output for ./DLSW-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 41 |
| error | 5 |
| minor error | 19 |
| warning | 68 |
| fyi | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 2 |
| comment-terminates (warning) | 33 |
| empty-description (warning) | 4 |
| identifier-external-redefined (warning) | 1 |
| index-element-no-size (minor error) | 2 |
| index-exceeds-too-large (warning) | 2 |
| integer-misuse (warning) | 23 |
| internal-flushing (warning) | 4 |
| internal-other (severe) | 4 |
| lexical (severe) | 32 |
| node-implicit (warning) | 1 |
| notification-object-access (minor error) | 16 |
| object-identifier-unknown (severe) | 5 |
| parent-row (error) | 3 |
| previous-definition (fyi) | 1 |
| revision-missing (minor error) | 1 |
Messages:
/home/fenner/mibindex/latest2/SNMPv2-TC
1: -- extracted from rfc2579.txt
2: -- at Fri Dec 24 21:34:57 1999
3:
4: SNMPv2-TC DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: TimeTicks FROM SNMPv2-SMI;
8:
9:
10: -- definition of textual conventions
11:
12: TEXTUAL-CONVENTION MACRO ::=
13: BEGIN
14: TYPE NOTATION ::=
15: DisplayPart
16: "STATUS" Status
17: "DESCRIPTION" Text
18: ReferPart
19: "SYNTAX" Syntax
20:
21: VALUE NOTATION ::=
22: value(VALUE Syntax) -- adapted ASN.1
23:
24: DisplayPart ::=
25: "DISPLAY-HINT" Text
26: | empty
27:
28: Status ::=
29: "current"
30: | "deprecated"
31: | "obsolete"
32:
33: ReferPart ::=
34: "REFERENCE" Text
35: | empty
36:
37: -- a character string as defined in [2]
38: Text ::= value(IA5String)
39:
40: Syntax ::= -- Must be one of the following:
41: -- a base type (or its refinement), or
42: -- a BITS pseudo-type
43: type
44: | "BITS" "{" NamedBits "}"
45:
46: NamedBits ::= NamedBit
47: | NamedBits "," NamedBit
48:
49: NamedBit ::= identifier "(" number ")" -- number is nonnegative
50:
51: END
52:
53:
54:
55:
56: DisplayString ::= TEXTUAL-CONVENTION
57: DISPLAY-HINT "255a"
58: STATUS current
59: DESCRIPTION
60: "Represents textual information taken from the NVT ASCII
61: character set, as defined in pages 4, 10-11 of RFC 854.
62:
63: To summarize RFC 854, the NVT ASCII repertoire specifies:
64:
65: - the use of character codes 0-127 (decimal)
66:
67: - the graphics characters (32-126) are interpreted as
68: US ASCII
69:
70: - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
71: meanings specified in RFC 854
72:
73: - the other 25 codes have no standard interpretation
74:
75: - the sequence 'CR LF' means newline
76:
77: - the sequence 'CR NUL' means carriage-return
78:
79: - an 'LF' not preceded by a 'CR' means moving to the
80: same column on the next line.
81:
82: - the sequence 'CR x' for any x other than LF or NUL is
83: illegal. (Note that this also means that a string may
84: end with either 'CR LF' or 'CR NUL', but not with CR.)
85:
86: Any object defined using this syntax may not exceed 255
87: characters in length."
88: SYNTAX OCTET STRING (SIZE (0..255))
89:
90: PhysAddress ::= TEXTUAL-CONVENTION
91: DISPLAY-HINT "1x:"
92: STATUS current
93: DESCRIPTION
94: "Represents media- or physical-level addresses."
95: SYNTAX OCTET STRING
96:
97:
98: MacAddress ::= TEXTUAL-CONVENTION
99: DISPLAY-HINT "1x:"
100: STATUS current
101: DESCRIPTION
102: "Represents an 802 MAC address represented in the
103: `canonical' order defined by IEEE 802.1a, i.e., as if it
104: were transmitted least significant bit first, even though
105: 802.5 (in contrast to other 802.x protocols) requires MAC
106: addresses to be transmitted most significant bit first."
107: SYNTAX OCTET STRING (SIZE (6))
108:
109: TruthValue ::= TEXTUAL-CONVENTION
110: STATUS current
111: DESCRIPTION
112: "Represents a boolean value."
113: SYNTAX INTEGER { true(1), false(2) }
114:
115: TestAndIncr ::= TEXTUAL-CONVENTION
116: STATUS current
117: DESCRIPTION
118: "Represents integer-valued information used for atomic
119: operations. When the management protocol is used to specify
120: that an object instance having this syntax is to be
121: modified, the new value supplied via the management protocol
122: must precisely match the value presently held by the
123: instance. If not, the management protocol set operation
124: fails with an error of `inconsistentValue'. Otherwise, if
125: the current value is the maximum value of 2^31-1 (2147483647
126: decimal), then the value held by the instance is wrapped to
127: zero; otherwise, the value held by the instance is
128: incremented by one. (Note that regardless of whether the
129: management protocol set operation succeeds, the variable-
130: binding in the request and response PDUs are identical.)
131:
132: The value of the ACCESS clause for objects having this
133: syntax is either `read-write' or `read-create'. When an
134: instance of a columnar object having this syntax is created,
135: any value may be supplied via the management protocol.
136:
137: When the network management portion of the system is re-
138: initialized, the value of every object instance having this
139: syntax must either be incremented from its value prior to
140: the re-initialization, or (if the value prior to the re-
141: initialization is unknown) be set to a pseudo-randomly
142: generated value."
143: SYNTAX INTEGER (0..2147483647)
144:
145: AutonomousType ::= TEXTUAL-CONVENTION
146: STATUS current
147: DESCRIPTION
148: "Represents an independently extensible type identification
149: value. It may, for example, indicate a particular sub-tree
150: with further MIB definitions, or define a particular type of
151: protocol or hardware."
152: SYNTAX OBJECT IDENTIFIER
153:
154:
155: InstancePointer ::= TEXTUAL-CONVENTION
156: STATUS obsolete
157: DESCRIPTION
158: "A pointer to either a specific instance of a MIB object or
159: a conceptual row of a MIB table in the managed device. In
160: the latter case, by convention, it is the name of the
161: particular instance of the first accessible columnar object
162: in the conceptual row.
163:
164: The two uses of this textual convention are replaced by
165: VariablePointer and RowPointer, respectively."
166: SYNTAX OBJECT IDENTIFIER
167:
168:
169: VariablePointer ::= TEXTUAL-CONVENTION
170: STATUS current
171: DESCRIPTION
172: "A pointer to a specific object instance. For example,
173: sysContact.0 or ifInOctets.3."
174: SYNTAX OBJECT IDENTIFIER
175:
176:
177: RowPointer ::= TEXTUAL-CONVENTION
178: STATUS current
179: DESCRIPTION
180: "Represents a pointer to a conceptual row. The value is the
181: name of the instance of the first accessible columnar object
182: in the conceptual row.
183:
184: For example, ifIndex.3 would point to the 3rd row in the
185: ifTable (note that if ifIndex were not-accessible, then
186: ifDescr.3 would be used instead)."
187: SYNTAX OBJECT IDENTIFIER
188:
189: RowStatus ::= TEXTUAL-CONVENTION
190: STATUS current
191: DESCRIPTION
192: "The RowStatus textual convention is used to manage the
193: creation and deletion of conceptual rows, and is used as the
194: value of the SYNTAX clause for the status column of a
195: conceptual row (as described in Section 7.7.1 of [2].)
196: The status column has six defined values:
197:
198: - `active', which indicates that the conceptual row is
199: available for use by the managed device;
200:
201: - `notInService', which indicates that the conceptual
202: row exists in the agent, but is unavailable for use by
203: the managed device (see NOTE below); 'notInService' has
204: no implication regarding the internal consistency of
205: the row, availability of resources, or consistency with
206: the current state of the managed device;
207:
208: - `notReady', which indicates that the conceptual row
209: exists in the agent, but is missing information
210: necessary in order to be available for use by the
211: managed device (i.e., one or more required columns in
212: the conceptual row have not been instanciated);
213:
214: - `createAndGo', which is supplied by a management
215: station wishing to create a new instance of a
216: conceptual row and to have its status automatically set
217: to active, making it available for use by the managed
218: device;
219:
220: - `createAndWait', which is supplied by a management
221: station wishing to create a new instance of a
222: conceptual row (but not make it available for use by
223: the managed device); and,
224:
225: - `destroy', which is supplied by a management station
226: wishing to delete all of the instances associated with
227: an existing conceptual row.
228:
229: Whereas five of the six values (all except `notReady') may
230: be specified in a management protocol set operation, only
231: three values will be returned in response to a management
232: protocol retrieval operation: `notReady', `notInService' or
233: `active'. That is, when queried, an existing conceptual row
234: has only three states: it is either available for use by
235: the managed device (the status column has value `active');
236: it is not available for use by the managed device, though
237: the agent has sufficient information to attempt to make it
238: so (the status column has value `notInService'); or, it is
239: not available for use by the managed device, and an attempt
240: to make it so would fail because the agent has insufficient
241: information (the state column has value `notReady').
242: NOTE WELL
243:
244: This textual convention may be used for a MIB table,
245: irrespective of whether the values of that table's
246: conceptual rows are able to be modified while it is
247: active, or whether its conceptual rows must be taken
248: out of service in order to be modified. That is, it is
249: the responsibility of the DESCRIPTION clause of the
250: status column to specify whether the status column must
251: not be `active' in order for the value of some other
252: column of the same conceptual row to be modified. If
253: such a specification is made, affected columns may be
254: changed by an SNMP set PDU if the RowStatus would not
255: be equal to `active' either immediately before or after
256: processing the PDU. In other words, if the PDU also
257: contained a varbind that would change the RowStatus
258: value, the column in question may be changed if the
259: RowStatus was not equal to `active' as the PDU was
260: received, or if the varbind sets the status to a value
261: other than 'active'.
262:
263:
264: Also note that whenever any elements of a row exist, the
265: RowStatus column must also exist.
266: To summarize the effect of having a conceptual row with a
267: status column having a SYNTAX clause value of RowStatus,
268: consider the following state diagram:
269:
270:
271: STATE
272: +--------------+-----------+-------------+-------------
273: | A | B | C | D
274: | |status col.|status column|
275: |status column | is | is |status column
276: ACTION |does not exist| notReady | notInService| is active
277: --------------+--------------+-----------+-------------+-------------
278: set status |noError ->D|inconsist- |inconsistent-|inconsistent-
279: column to | or | entValue| Value| Value
280: createAndGo |inconsistent- | | |
281: | Value| | |
282: --------------+--------------+-----------+-------------+-------------
283: set status |noError see 1|inconsist- |inconsistent-|inconsistent-
284: column to | or | entValue| Value| Value
285: createAndWait |wrongValue | | |
286: --------------+--------------+-----------+-------------+-------------
287: set status |inconsistent- |inconsist- |noError |noError
288: column to | Value| entValue| |
289: active | | | |
290: | | or | |
291: | | | |
292: | |see 2 ->D|see 8 ->D| ->D
293: --------------+--------------+-----------+-------------+-------------
294: set status |inconsistent- |inconsist- |noError |noError ->C
295: column to | Value| entValue| |
296: notInService | | | |
297: | | or | | or
298: | | | |
299: | |see 3 ->C| ->C|see 6
300: --------------+--------------+-----------+-------------+-------------
301: set status |noError |noError |noError |noError ->A
302: column to | | | | or
303: destroy | ->A| ->A| ->A|see 7
304: --------------+--------------+-----------+-------------+-------------
305: set any other |see 4 |noError |noError |see 5
306: column to some| | | |
307: value | | see 1| ->C| ->D
308: --------------+--------------+-----------+-------------+-------------
309:
310: (1) goto B or C, depending on information available to the
311: agent.
312:
313: (2) if other variable bindings included in the same PDU,
314: provide values for all columns which are missing but
315: required, and all columns have acceptable values, then
316: return noError and goto D.
317:
318: (3) if other variable bindings included in the same PDU,
319: provide legal values for all columns which are missing but
320: required, then return noError and goto C.
321:
322: (4) at the discretion of the agent, the return value may be
323: either:
324:
325: inconsistentName: because the agent does not choose to
326: create such an instance when the corresponding
327: RowStatus instance does not exist, or
328:
329: inconsistentValue: if the supplied value is
330: inconsistent with the state of some other MIB object's
331: value, or
332:
333: noError: because the agent chooses to create the
334: instance.
335:
336: If noError is returned, then the instance of the status
337: column must also be created, and the new state is B or C,
338: depending on the information available to the agent. If
339: inconsistentName or inconsistentValue is returned, the row
340: remains in state A.
341:
342: (5) depending on the MIB definition for the column/table,
343: either noError or inconsistentValue may be returned.
344:
345: (6) the return value can indicate one of the following
346: errors:
347:
348: wrongValue: because the agent does not support
349: notInService (e.g., an agent which does not support
350: createAndWait), or
351:
352: inconsistentValue: because the agent is unable to take
353: the row out of service at this time, perhaps because it
354: is in use and cannot be de-activated.
355:
356: (7) the return value can indicate the following error:
357:
358: inconsistentValue: because the agent is unable to
359: remove the row at this time, perhaps because it is in
360: use and cannot be de-activated.
361:
362: (8) the transition to D can fail, e.g., if the values of the
363: conceptual row are inconsistent, then the error code would
364: be inconsistentValue.
365:
366: NOTE: Other processing of (this and other varbinds of) the
367: set request may result in a response other than noError
368: being returned, e.g., wrongValue, noCreation, etc.
369:
370:
371: Conceptual Row Creation
372:
373: There are four potential interactions when creating a
374: conceptual row: selecting an instance-identifier which is
375: not in use; creating the conceptual row; initializing any
376: objects for which the agent does not supply a default; and,
377: making the conceptual row available for use by the managed
378: device.
379:
380: Interaction 1: Selecting an Instance-Identifier
381:
382: The algorithm used to select an instance-identifier varies
383: for each conceptual row. In some cases, the instance-
384: identifier is semantically significant, e.g., the
385: destination address of a route, and a management station
386: selects the instance-identifier according to the semantics.
387:
388: In other cases, the instance-identifier is used solely to
389: distinguish conceptual rows, and a management station
390: without specific knowledge of the conceptual row might
391: examine the instances present in order to determine an
392: unused instance-identifier. (This approach may be used, but
393: it is often highly sub-optimal; however, it is also a
394: questionable practice for a naive management station to
395: attempt conceptual row creation.)
396:
397: Alternately, the MIB module which defines the conceptual row
398: might provide one or more objects which provide assistance
399: in determining an unused instance-identifier. For example,
400: if the conceptual row is indexed by an integer-value, then
401: an object having an integer-valued SYNTAX clause might be
402: defined for such a purpose, allowing a management station to
403: issue a management protocol retrieval operation. In order
404: to avoid unnecessary collisions between competing management
405: stations, `adjacent' retrievals of this object should be
406: different.
407:
408: Finally, the management station could select a pseudo-random
409: number to use as the index. In the event that this index
410: was already in use and an inconsistentValue was returned in
411: response to the management protocol set operation, the
412: management station should simply select a new pseudo-random
413: number and retry the operation.
414:
415: A MIB designer should choose between the two latter
416: algorithms based on the size of the table (and therefore the
417: efficiency of each algorithm). For tables in which a large
418: number of entries are expected, it is recommended that a MIB
419: object be defined that returns an acceptable index for
420: creation. For tables with small numbers of entries, it is
421: recommended that the latter pseudo-random index mechanism be
422: used.
423:
424: Interaction 2: Creating the Conceptual Row
425:
426: Once an unused instance-identifier has been selected, the
427: management station determines if it wishes to create and
428: activate the conceptual row in one transaction or in a
429: negotiated set of interactions.
430:
431: Interaction 2a: Creating and Activating the Conceptual Row
432:
433: The management station must first determine the column
434: requirements, i.e., it must determine those columns for
435: which it must or must not provide values. Depending on the
436: complexity of the table and the management station's
437: knowledge of the agent's capabilities, this determination
438: can be made locally by the management station. Alternately,
439: the management station issues a management protocol get
440: operation to examine all columns in the conceptual row that
441: it wishes to create. In response, for each column, there
442: are three possible outcomes:
443:
444: - a value is returned, indicating that some other
445: management station has already created this conceptual
446: row. We return to interaction 1.
447:
448: - the exception `noSuchInstance' is returned,
449: indicating that the agent implements the object-type
450: associated with this column, and that this column in at
451: least one conceptual row would be accessible in the MIB
452: view used by the retrieval were it to exist. For those
453: columns to which the agent provides read-create access,
454: the `noSuchInstance' exception tells the management
455: station that it should supply a value for this column
456: when the conceptual row is to be created.
457: - the exception `noSuchObject' is returned, indicating
458: that the agent does not implement the object-type
459: associated with this column or that there is no
460: conceptual row for which this column would be
461: accessible in the MIB view used by the retrieval. As
462: such, the management station can not issue any
463: management protocol set operations to create an
464: instance of this column.
465:
466: Once the column requirements have been determined, a
467: management protocol set operation is accordingly issued.
468: This operation also sets the new instance of the status
469: column to `createAndGo'.
470:
471: When the agent processes the set operation, it verifies that
472: it has sufficient information to make the conceptual row
473: available for use by the managed device. The information
474: available to the agent is provided by two sources: the
475: management protocol set operation which creates the
476: conceptual row, and, implementation-specific defaults
477: supplied by the agent (note that an agent must provide
478: implementation-specific defaults for at least those objects
479: which it implements as read-only). If there is sufficient
480: information available, then the conceptual row is created, a
481: `noError' response is returned, the status column is set to
482: `active', and no further interactions are necessary (i.e.,
483: interactions 3 and 4 are skipped). If there is insufficient
484: information, then the conceptual row is not created, and the
485: set operation fails with an error of `inconsistentValue'.
486: On this error, the management station can issue a management
487: protocol retrieval operation to determine if this was
488: because it failed to specify a value for a required column,
489: or, because the selected instance of the status column
490: already existed. In the latter case, we return to
491: interaction 1. In the former case, the management station
492: can re-issue the set operation with the additional
493: information, or begin interaction 2 again using
494: `createAndWait' in order to negotiate creation of the
495: conceptual row.
496: NOTE WELL
497:
498: Regardless of the method used to determine the column
499: requirements, it is possible that the management
500: station might deem a column necessary when, in fact,
501: the agent will not allow that particular columnar
502: instance to be created or written. In this case, the
503: management protocol set operation will fail with an
504: error such as `noCreation' or `notWritable'. In this
505: case, the management station decides whether it needs
506: to be able to set a value for that particular columnar
507: instance. If not, the management station re-issues the
508: management protocol set operation, but without setting
509: a value for that particular columnar instance;
510: otherwise, the management station aborts the row
511: creation algorithm.
512:
513: Interaction 2b: Negotiating the Creation of the Conceptual
514: Row
515:
516: The management station issues a management protocol set
517: operation which sets the desired instance of the status
518: column to `createAndWait'. If the agent is unwilling to
519: process a request of this sort, the set operation fails with
520: an error of `wrongValue'. (As a consequence, such an agent
521: must be prepared to accept a single management protocol set
522: operation, i.e., interaction 2a above, containing all of the
523: columns indicated by its column requirements.) Otherwise,
524: the conceptual row is created, a `noError' response is
525: returned, and the status column is immediately set to either
526: `notInService' or `notReady', depending on whether it has
527: sufficient information to (attempt to) make the conceptual
528: row available for use by the managed device. If there is
529: sufficient information available, then the status column is
530: set to `notInService'; otherwise, if there is insufficient
531: information, then the status column is set to `notReady'.
532: Regardless, we proceed to interaction 3.
533:
534: Interaction 3: Initializing non-defaulted Objects
535:
536: The management station must now determine the column
537: requirements. It issues a management protocol get operation
538: to examine all columns in the created conceptual row. In
539: the response, for each column, there are three possible
540: outcomes:
541: - a value is returned, indicating that the agent
542: implements the object-type associated with this column
543: and had sufficient information to provide a value. For
544: those columns to which the agent provides read-create
545: access (and for which the agent allows their values to
546: be changed after their creation), a value return tells
547: the management station that it may issue additional
548: management protocol set operations, if it desires, in
549: order to change the value associated with this column.
550:
551: - the exception `noSuchInstance' is returned,
552: indicating that the agent implements the object-type
553: associated with this column, and that this column in at
554: least one conceptual row would be accessible in the MIB
555: view used by the retrieval were it to exist. However,
556: the agent does not have sufficient information to
557: provide a value, and until a value is provided, the
558: conceptual row may not be made available for use by the
559: managed device. For those columns to which the agent
560: provides read-create access, the `noSuchInstance'
561: exception tells the management station that it must
562: issue additional management protocol set operations, in
563: order to provide a value associated with this column.
564:
565: - the exception `noSuchObject' is returned, indicating
566: that the agent does not implement the object-type
567: associated with this column or that there is no
568: conceptual row for which this column would be
569: accessible in the MIB view used by the retrieval. As
570: such, the management station can not issue any
571: management protocol set operations to create an
572: instance of this column.
573:
574: If the value associated with the status column is
575: `notReady', then the management station must first deal with
576: all `noSuchInstance' columns, if any. Having done so, the
577: value of the status column becomes `notInService', and we
578: proceed to interaction 4.
579: Interaction 4: Making the Conceptual Row Available
580:
581: Once the management station is satisfied with the values
582: associated with the columns of the conceptual row, it issues
583: a management protocol set operation to set the status column
584: to `active'. If the agent has sufficient information to
585: make the conceptual row available for use by the managed
586: device, the management protocol set operation succeeds (a
587: `noError' response is returned). Otherwise, the management
588: protocol set operation fails with an error of
589: `inconsistentValue'.
590:
591: NOTE WELL
592:
593: A conceptual row having a status column with value
594: `notInService' or `notReady' is unavailable to the
595: managed device. As such, it is possible for the
596: managed device to create its own instances during the
597: time between the management protocol set operation
598: which sets the status column to `createAndWait' and the
599: management protocol set operation which sets the status
600: column to `active'. In this case, when the management
601: protocol set operation is issued to set the status
602: column to `active', the values held in the agent
603: supersede those used by the managed device.
604:
605: If the management station is prevented from setting the
606: status column to `active' (e.g., due to management station
607: or network failure) the conceptual row will be left in the
608: `notInService' or `notReady' state, consuming resources
609: indefinitely. The agent must detect conceptual rows that
610: have been in either state for an abnormally long period of
611: time and remove them. It is the responsibility of the
612: DESCRIPTION clause of the status column to indicate what an
613: abnormally long period of time would be. This period of
614: time should be long enough to allow for human response time
615: (including `think time') between the creation of the
616: conceptual row and the setting of the status to `active'.
617: In the absence of such information in the DESCRIPTION
618: clause, it is suggested that this period be approximately 5
619: minutes in length. This removal action applies not only to
620: newly-created rows, but also to previously active rows which
621: are set to, and left in, the notInService state for a
622: prolonged period exceeding that which is considered normal
623: for such a conceptual row.
624: Conceptual Row Suspension
625:
626: When a conceptual row is `active', the management station
627: may issue a management protocol set operation which sets the
628: instance of the status column to `notInService'. If the
629: agent is unwilling to do so, the set operation fails with an
630: error of `wrongValue' or `inconsistentValue'. Otherwise,
631: the conceptual row is taken out of service, and a `noError'
632: response is returned. It is the responsibility of the
633: DESCRIPTION clause of the status column to indicate under
634: what circumstances the status column should be taken out of
635: service (e.g., in order for the value of some other column
636: of the same conceptual row to be modified).
637:
638:
639: Conceptual Row Deletion
640:
641: For deletion of conceptual rows, a management protocol set
642: operation is issued which sets the instance of the status
643: column to `destroy'. This request may be made regardless of
644: the current value of the status column (e.g., it is possible
645: to delete conceptual rows which are either `notReady',
646: `notInService' or `active'.) If the operation succeeds,
647: then all instances associated with the conceptual row are
648: immediately removed."
649: SYNTAX INTEGER {
650: -- the following two values are states:
651: -- these values may be read or written
652: active(1),
653: notInService(2),
654:
655: -- the following value is a state:
656: -- this value may be read, but not written
657: notReady(3),
658:
659: -- the following three values are
660: -- actions: these values may be written,
661: -- but are never read
662: createAndGo(4),
663: createAndWait(5),
664: destroy(6)
665: }
666:
667: TimeStamp ::= TEXTUAL-CONVENTION
668: STATUS current
669: DESCRIPTION
670: "The value of the sysUpTime object at which a specific
671: occurrence happened. The specific occurrence must be
672: defined in the description of any object defined using this
673: type.
674:
675: If sysUpTime is reset to zero as a result of a re-
676: initialization of the network management (sub)system, then
677: the values of all TimeStamp objects are also reset.
678: However, after approximately 497 days without a re-
679: initialization, the sysUpTime object will reach 2^^32-1 and
680: then increment around to zero; in this case, existing values
681: of TimeStamp objects do not change. This can lead to
682: ambiguities in the value of TimeStamp objects."
683: SYNTAX TimeTicks
684:
685:
686: TimeInterval ::= TEXTUAL-CONVENTION
687: STATUS current
688: DESCRIPTION
689: "A period of time, measured in units of 0.01 seconds."
690: SYNTAX INTEGER (0..2147483647)
691:
692: DateAndTime ::= TEXTUAL-CONVENTION
693: DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
694: STATUS current
695: DESCRIPTION
696: "A date-time specification.
697:
698: field octets contents range
699: ----- ------ -------- -----
700: 1 1-2 year* 0..65536
701: 2 3 month 1..12
702: 3 4 day 1..31
703: 4 5 hour 0..23
704: 5 6 minutes 0..59
705: 6 7 seconds 0..60
706: (use 60 for leap-second)
707: 7 8 deci-seconds 0..9
708: 8 9 direction from UTC '+' / '-'
709: 9 10 hours from UTC* 0..13
710: 10 11 minutes from UTC 0..59
711:
712: * Notes:
713: - the value of year is in network-byte order
714: - daylight saving time in New Zealand is +13
715:
716: For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
717: displayed as:
718:
719: 1992-5-26,13:30:15.0,-4:0
720:
721: Note that if only local time is known, then timezone
722: information (fields 8-10) is not present."
723: SYNTAX OCTET STRING (SIZE (8 | 11))
724:
725:
726: StorageType ::= TEXTUAL-CONVENTION
727: STATUS current
728: DESCRIPTION
729: "Describes the memory realization of a conceptual row. A
730: row which is volatile(2) is lost upon reboot. A row which
731: is either nonVolatile(3), permanent(4) or readOnly(5), is
732: backed up by stable storage. A row which is permanent(4)
733: can be changed but not deleted. A row which is readOnly(5)
734: cannot be changed nor deleted.
735:
736: If the value of an object with this syntax is either
737: permanent(4) or readOnly(5), it cannot be written.
738: Conversely, if the value is either other(1), volatile(2) or
739: nonVolatile(3), it cannot be modified to be permanent(4) or
740: readOnly(5). (All illegal modifications result in a
741: 'wrongValue' error.)
742:
743: Every usage of this textual convention is required to
744: specify the columnar objects which a permanent(4) row must
745: at a minimum allow to be writable."
746: SYNTAX INTEGER {
747: other(1), -- eh?
748: volatile(2), -- e.g., in RAM
749: nonVolatile(3), -- e.g., in NVRAM
750: permanent(4), -- e.g., partially in ROM
751: readOnly(5) -- e.g., completely in ROM
752: }
753:
754: TDomain ::= TEXTUAL-CONVENTION
755: STATUS current
756: DESCRIPTION
757: "Denotes a kind of transport service.
758:
759: Some possible values, such as snmpUDPDomain, are defined in
760: the SNMPv2-TM MIB module. Other possible values are defined
761: in other MIB modules."
762: REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
763: SYNTAX OBJECT IDENTIFIER
764:
765:
766: TAddress ::= TEXTUAL-CONVENTION
766: fyi -
info: previous definition of `TAddress'
767: STATUS current
768: DESCRIPTION
769: "Denotes a transport service address.
770:
771: A TAddress value is always interpreted within the context of a
772: TDomain value. Thus, each definition of a TDomain value must
773: be accompanied by a definition of a textual convention for use
774: with that TDomain. Some possible textual conventions, such as
775: SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
776: MIB module. Other possible textual conventions are defined in
777: other MIB modules."
778: REFERENCE "The SNMPv2-TM MIB module is defined in RFC 1906."
779: SYNTAX OCTET STRING (SIZE (1..255))
780:
781:
782: END
783:
784: --
785: -- Copyright (C) The Internet Society (1999). All Rights Reserved.
786: --
787: -- This document and translations of it may be copied and furnished to
788: -- others, and derivative works that comment on or otherwise explain it
789: -- or assist in its implementation may be prepared, copied, published
790: -- and distributed, in whole or in part, without restriction of any
791: -- kind, provided that the above copyright notice and this paragraph are
792: -- included on all such copies and derivative works. However, this
793: -- document itself may not be modified in any way, such as by removing
794: -- the copyright notice or references to the Internet Society or other
795: -- Internet organizations, except as needed for the purpose of
796: -- developing Internet standards in which case the procedures for
797: -- copyrights defined in the Internet Standards process must be
798: -- followed, or as required to translate it into languages other than
799: -- English.
800: --
801: -- The limited permissions granted above are perpetual and will not be
802: -- revoked by the Internet Society or its successors or assigns.
803: --
804: -- This document and the information contained herein is provided on an
805: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
806: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
807: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
808: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
809: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
810:
DLSW-MIB
1: -- extracted from rfc2024.txt
2: -- at Mon Nov 15 17:11:48 1999
3:
4: DLSW-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: DisplayString, RowStatus,
8: RowPointer, TruthValue,
9: TEXTUAL-CONVENTION FROM SNMPv2-TC
10: Counter32, Gauge32, TimeTicks,
11: OBJECT-TYPE, MODULE-IDENTITY,
12: NOTIFICATION-TYPE FROM SNMPv2-SMI
13: MODULE-COMPLIANCE, OBJECT-GROUP,
14: NOTIFICATION-GROUP FROM SNMPv2-CONF
15: ifIndex FROM IF-MIB
16: sdlcLSAddress FROM SNA-SDLC-MIB;
17:
18: dlsw MODULE-IDENTITY
19: LAST-UPDATED "9606040900Z"
20: ORGANIZATION "AIW DLSw MIB RIGLET and IETF DLSw MIB Working Group"
21: CONTACT-INFO
22: "David D. Chen
23: IBM Corporation
24: 800 Park, Highway 54
25: Research Triangle Park, NC 27709-9990
26: Tel: 1 919 254 6182
27: E-mail: dchen@vnet.ibm.com"
28: DESCRIPTION
29: "This MIB module contains objects to manage Data Link
30: Switches."
31: ::= { mib-2 46 }
31: minor error -
revision for last update is missing
31: severe -
unknown object identifier label `mib-2'
32:
33: dlswMIB OBJECT IDENTIFIER ::= { dlsw 1 }
34: dlswDomains OBJECT IDENTIFIER ::= { dlsw 2 }
35:
36: -- *******************************************************************
37: -- Textual convention definitions
38: -- *******************************************************************
39:
40: NBName ::= TEXTUAL-CONVENTION
41: STATUS current
42: DESCRIPTION
43: "Represents a single qualified NetBIOS name, which can include
44: `don't care' and `wildcard' characters to represent a number
45: of real NetBIOS names. If an individual character position in
46: the qualified name contains a `?', the corresponding character
47: position in a real NetBIOS name is a `don't care'. If the
48: qualified name ends in `*', the remainder of a real NetBIOS
49: name is a `don't care'. `*' is only considered a wildcard if it
50: appears at the end of a name."
51: SYNTAX OCTET STRING (SIZE (0..16))
52:
53: MacAddressNC ::= TEXTUAL-CONVENTION
54: DISPLAY-HINT "1x:"
55: STATUS current
56: DESCRIPTION
57: "Represents an 802 MAC address represented in
58: non-canonical format. That is, the most significant
59: bit will be transmitted first. If this information
60: is not available, the value is a zero length string."
61: SYNTAX OCTET STRING (SIZE (0 | 6))
62:
63: TAddress ::= TEXTUAL-CONVENTION
63: warning -
warning: redefinition of identifier `SNMPv2-TC::TAddress'
64: STATUS current
65: DESCRIPTION
66: "Denotes a transport service address.
67: For dlswTCPDomain, a TAddress is 4 octets long,
68: containing the IP-address in network-byte order."
69: SYNTAX OCTET STRING (SIZE (0..255))
70:
71: EndStationLocation ::= TEXTUAL-CONVENTION
72: STATUS current
73: DESCRIPTION
74: "Representing the location of an end station related
75: to the managed DLSw node."
76: SYNTAX INTEGER {
77: other (1),
78: internal (2), -- local virtual MAC address
79: remote (3), -- via DLSw partner
80: local (4) -- locally attached
81: }
82:
83: DlcType ::= TEXTUAL-CONVENTION
84: STATUS current
85: DESCRIPTION
86: "Representing the type of DLC of an end station, if
87: applicable."
88: SYNTAX INTEGER {
89: other (1), -- not assigned yet
90: na (2), -- not applicable
91: llc (3), -- 802.2 Logical Link Control
92: sdlc (4), -- SDLC
93: qllc (5) -- QLLC
94: }
95:
96: LFSize ::= TEXTUAL-CONVENTION
97: STATUS current
98: DESCRIPTION
99: "The largest size of the INFO field (including DLC header,
100: not including any MAC-level or framing octets).
101: 64 valid values as defined by the IEEE 802.1D
102: Addendum are acceptable."
103: SYNTAX INTEGER {
104: lfs516(516), lfs635(635), lfs754(754), lfs873(873),
105: lfs993(993), lfs1112(1112), lfs1231(1231),
106: lfs1350(1350), lfs1470(1470), lfs1542(1542),
107: lfs1615(1615), lfs1688(1688), lfs1761(1761),
108: lfs1833(1833), lfs1906(1906), lfs1979(1979),
109: lfs2052(2052), lfs2345(2345), lfs2638(2638),
110: lfs2932(2932), lfs3225(3225), lfs3518(3518),
111: lfs3812(3812), lfs4105(4105), lfs4399(4399),
112: lfs4865(4865), lfs5331(5331), lfs5798(5798),
113: lfs6264(6264), lfs6730(6730), lfs7197(7197),
114: lfs7663(7663), lfs8130(8130), lfs8539(8539),
115: lfs8949(8949), lfs9358(9358), lfs9768(9768),
116: lfs10178(10178), lfs10587(10587), lfs10997(10997),
117: lfs11407(11407), lfs12199(12199), lfs12992(12992),
118: lfs13785(13785), lfs14578(14578), lfs15370(15370),
119: lfs16163(16163), lfs16956(16956), lfs17749(17749),
120: lfs20730(20730), lfs23711(23711), lfs26693(26693),
121: lfs29674(29674), lfs32655(32655), lfs38618(38618),
122: lfs41600(41600), lfs44591(44591), lfs47583(47583),
123: lfs50575(50575), lfs53567(53567), lfs56559(56559),
124: lfs59551(59551), lfs65535(65535)
125: }
126:
127: null OBJECT IDENTIFIER ::= { 0 0 }
127: warning -
warning: implicit node definition
128:
129:
130: -- *******************************************************************
131: -- DLSw Transport Domain definitions
132: -- *******************************************************************
133:
134: -- DLSw over TCP
135: dlswTCPDomain OBJECT IDENTIFIER ::= { dlswDomains 1 }
136: -- for an IP address of length 4:
137: --
138: -- octets contents encoding
139: -- 1-4 IP-address network-byte order
140: --
141: DlswTCPAddress ::= TEXTUAL-CONVENTION
142: DISPLAY-HINT "1d.1d.1d.1d"
143: STATUS current
144: DESCRIPTION
145: "Represents the IP address of a DLSw which uses
146: TCP as a transport protocol."
147: SYNTAX OCTET STRING (SIZE (4))
148:
149:
150: -- *******************************************************************
151: -- DLSw MIB Definition
152: -- *******************************************************************
153: -- The DLSw MIB module contains an object part and a conformance part.
154: -- Object part is organized in the following groups:
155: -- (1) dlswNode -- information about this DLSw
155: warning -
warning: note, -- terminates a comment
155: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
156: -- (2) dlswTConn -- about adjacent DLSw partners
157: -- (3) dlswInterface -- about which interfaces DLSw is active on
158: -- (4) dlswDirectory -- about any directory of local/remote resources
158: severe -
lexically unexpected character, skipping to end of line
159: -- (5) dlswCircuit -- about established circuits.
160: -- (6) dlswSdlc -- about SDLC data link switched devices
161:
162: dlswNode OBJECT IDENTIFIER ::= { dlswMIB 1 }
162: warning -
warning: flushing recent incorrect declaration, see previous error(s)
163: dlswTConn OBJECT IDENTIFIER ::= { dlswMIB 2 }
164: dlswInterface OBJECT IDENTIFIER ::= { dlswMIB 3 }
165: dlswDirectory OBJECT IDENTIFIER ::= { dlswMIB 4 }
166: dlswCircuit OBJECT IDENTIFIER ::= { dlswMIB 5 }
167: dlswSdlc OBJECT IDENTIFIER ::= { dlswMIB 6 } -- SDLC
168:
169: -- *******************************************************************
170: -- THE NODE GROUP
171: -- *******************************************************************
172:
173: -- -------------------------------------------------------------------
173: warning -
warning: note, -- terminates a comment
173: severe -
lexically unexpected character, skipping to end of line
174: -- DLSw Node Identity
175: -- -------------------------------------------------------------------
175: warning -
warning: note, -- terminates a comment
175: severe -
lexically unexpected character, skipping to end of line
176: dlswNodeVersion OBJECT-TYPE
177: SYNTAX OCTET STRING (SIZE (2))
178: MAX-ACCESS read-only
179: STATUS current
180: DESCRIPTION
181: "This value identifies the particular version of the DLSw
182: standard supported by this DLSw. The first octet is a
183: hexadecimal value representing the DLSw standard Version
184: number of this DLSw, and the second is a hexadecimal value
185: representing the DLSw standard Release number. This
186: information is reported in DLSw Capabilities Exchange."
187: REFERENCE
188: "DLSW: Switch-to-Switch Protocol RFC 1795"
189: ::= { dlswNode 1 }
189: severe -
unknown object identifier label `dlswNode'
190:
191: dlswNodeVendorID OBJECT-TYPE
192: SYNTAX OCTET STRING (SIZE (3))
193: MAX-ACCESS read-only
194: STATUS current
195: DESCRIPTION
196: "The value identifies the manufacturer's IEEE-assigned
197: organizationally Unique Identifier (OUI) of this DLSw.
198: This information is reported in DLSw Capabilities
199: Exchange."
200: REFERENCE
201: "DLSW: Switch-to-Switch Protocol RFC 1795"
202: ::= { dlswNode 2 }
203:
204: dlswNodeVersionString OBJECT-TYPE
205: SYNTAX DisplayString
206: MAX-ACCESS read-only
207: STATUS current
208: DESCRIPTION
209: "This string gives product-specific information about
210: this DLSw (e.g., product name, code release and fix level).
211: This flows in Capabilities Exchange messages."
212: REFERENCE
213: "DLSW: Switch-to-Switch Protocol RFC 1795"
214: ::= { dlswNode 3 }
215:
216: -- -------------------------------------------------------------------
216: warning -
warning: note, -- terminates a comment
216: severe -
lexically unexpected character, skipping to end of line
217: -- DLSw Code Capability
218: -- -------------------------------------------------------------------
218: warning -
warning: note, -- terminates a comment
218: severe -
lexically unexpected character, skipping to end of line
219: dlswNodeStdPacingSupport OBJECT-TYPE
220: SYNTAX INTEGER {
221: none (1), -- does not support DLSw
222: -- Standard pacing scheme
223: adaptiveRcvWindow (2), -- the receive window size
224: -- varies
225: fixedRcvWindow (3) -- the receive window size
226: -- remains constant
227: }
228: MAX-ACCESS read-only
229: STATUS current
230: DESCRIPTION
231: "Circuit pacing, as defined in the DLSw Standard, allows each
232: of the two DLSw nodes on a circuit to control the amount
233: of data the other is permitted to send to them. This object
234: reflects the level of support the DLSw node has for this
235: protocol. (1) means the node has no support for the standard
236: circuit pacing flows; it may use RFC 1434+ methods only, or
237: a proprietary flow control scheme. (2) means the node supports
238: the standard scheme and can vary the window sizes it grants as
239: a data receiver. (3) means the node supports the standard
240: scheme but never varies its receive window size."
241: ::= { dlswNode 4 }
242:
243: -- -------------------------------------------------------------------
243: warning -
warning: note, -- terminates a comment
243: severe -
lexically unexpected character, skipping to end of line
244: -- DLSw Node Operational Objects
245: -- -------------------------------------------------------------------
245: warning -
warning: note, -- terminates a comment
245: severe -
lexically unexpected character, skipping to end of line
246: dlswNodeStatus OBJECT-TYPE
247: SYNTAX INTEGER {
248: active (1),
249: inactive (2)
250: }
251: MAX-ACCESS read-write
252: STATUS current
253: DESCRIPTION
254: "The status of the DLSw part of the system. Changing the
255: value from active to inactive causes DLSw to take
256: the following actions - (1) it disconnects all circuits
257: through all DLSw partners, (2) it disconnects all
258: transport connections to all DLSw partners, (3) it
259: disconnects all local DLC connections, and (4) it stops
260: processing all DLC connection set-up traffic.
261: Since these are destructive actions, the user should
262: query the circuit and transport connection tables in
263: advance to understand the effect this action will have.
264: Changing the value from inactive to active causes DLSw
265: to come up in its initial state, i.e., transport
266: connections established and ready to bring up circuits."
267: ::= { dlswNode 5 }
268:
269: dlswNodeUpTime OBJECT-TYPE
270: SYNTAX TimeTicks
271: UNITS "hundredths of a second"
272: MAX-ACCESS read-only
273: STATUS current
274: DESCRIPTION
275: "The amount of time (in hundredths of a second) since
276: the DLSw portion of the system was last re-initialized.
277: That is, if dlswState is in the active state,
278: the time the dlswState entered the active state.
279: It will remain zero if dlswState is in the
280: inactive state."
281: ::= { dlswNode 6 }
282:
283: dlswNodeVirtualSegmentLFSize OBJECT-TYPE
284: SYNTAX LFSize
285: MAX-ACCESS read-write
286: STATUS current
287: DESCRIPTION
288: "The largest frame size (including DLC header and info field
289: but not any MAC-level or framing octets) this DLSw can forward
290: on any path through itself. This object can represent any box-
291: level frame size forwarding restriction (e.g., from the use
292: of fixed-size buffers). Some DLSw implementations will have
293: no such restriction.
294:
295: This value will affect the LF size of circuits during circuit
296: creation. The LF size of an existing circuit can be found in
297: the RIF (Routing Information Field)."
298: DEFVAL { lfs65535 }
299: ::= { dlswNode 7 }
300:
301: -- ...................................................................
302: -- NETBIOS Resources
303: -- ...................................................................
304:
305: dlswNodeResourceNBExclusivity OBJECT-TYPE
306: SYNTAX TruthValue
307: MAX-ACCESS read-write
308: STATUS current
309: DESCRIPTION
310: "The value of true indicates that the NetBIOS Names
311: configured in dlswDirNBTable are the only ones accessible
312: via this DLSw.
313:
314: If a node supports sending run-time capabilities exchange
315: messages, changes to this object should cause that action.
316: It is up to the implementation exactly when to start the
317: run-time capabilities exchange."
318: ::= { dlswNode 8 }
319:
320: -- ...................................................................
321: -- MAC Address List
322: -- ...................................................................
323:
324: dlswNodeResourceMacExclusivity OBJECT-TYPE
325: SYNTAX TruthValue
326: MAX-ACCESS read-write
327: STATUS current
328: DESCRIPTION
329: "The value of true indicates that the MAC addresses
330: configured in the dlswDirMacTable are the only ones
331: accessible via this DLSw.
332:
333: If a node supports sending run-time capabilities exchange
334: messages, changes to this object should cause that action.
335: It is up to the implementation exactly when to start the
336: run-time capabilities exchange."
337: ::= { dlswNode 9 }
338:
339:
340: -- *******************************************************************
341: -- TRANSPORT CONNECTION (aka: PARTNER DLSW)
342: -- *******************************************************************
343:
344: -- -------------------------------------------------------------------
344: warning -
warning: note, -- terminates a comment
344: severe -
lexically unexpected character, skipping to end of line
345: -- Transport Connection Statistics Objects
346: -- -------------------------------------------------------------------
346: warning -
warning: note, -- terminates a comment
346: severe -
lexically unexpected character, skipping to end of line
347: dlswTConnStat OBJECT IDENTIFIER ::= { dlswTConn 1 }
348:
349: dlswTConnStatActiveConnections OBJECT-TYPE
350: SYNTAX Gauge32
351: MAX-ACCESS read-only
352: STATUS current
353: DESCRIPTION
354: "The number of transport connections that are not in
355: `disconnected' state."
356: ::= { dlswTConnStat 1 }
357:
358: dlswTConnStatCloseIdles OBJECT-TYPE
359: SYNTAX Counter32
360: MAX-ACCESS read-only
361: STATUS current
362: DESCRIPTION
363: "The number of times transport connections in this node
364: exited the connected state with zero active circuits on
365: the transport connection."
366: ::= { dlswTConnStat 2 }
367:
368: dlswTConnStatCloseBusys OBJECT-TYPE
369: SYNTAX Counter32
370: MAX-ACCESS read-only
371: STATUS current
372: DESCRIPTION
373: "The number of times transport connections in this node
374: exited the connected state with some non-zero number
375: of active circuits on the transport connection. Normally
376: this means the transport connection failed unexpectedly."
377: ::= { dlswTConnStat 3 }
378:
379: -- -------------------------------------------------------------------
379: warning -
warning: note, -- terminates a comment
379: severe -
lexically unexpected character, skipping to end of line
380: -- Transport Connection Configuration Table
381: -- -------------------------------------------------------------------
381: warning -
warning: note, -- terminates a comment
381: severe -
lexically unexpected character, skipping to end of line
382: dlswTConnConfigTable OBJECT-TYPE
383: SYNTAX SEQUENCE OF DlswTConnConfigEntry
384: MAX-ACCESS not-accessible
385: STATUS current
386: DESCRIPTION
387: "This table defines the transport connections
388: that will be initiated or accepted by this
389: DLSw. Structure of masks allows wildcard
390: definition for a collection of transport
391: connections by a conceptual row. For a
392: specific transport connection, there may
393: be multiple of conceptual rows match the
394: transport address. The `best' match will
395: the one to determine the characteristics
396: of the transport connection."
397: ::= { dlswTConn 2 }
398:
399: dlswTConnConfigEntry OBJECT-TYPE
400: SYNTAX DlswTConnConfigEntry
401: MAX-ACCESS not-accessible
402: STATUS current
403: DESCRIPTION
404: "Each conceptual row defines a collection of
405: transport connections."
406: INDEX { dlswTConnConfigIndex }
407: ::= { dlswTConnConfigTable 1 }
408:
409: DlswTConnConfigEntry ::= SEQUENCE {
410: dlswTConnConfigIndex INTEGER,
411: dlswTConnConfigTDomain OBJECT IDENTIFIER,
412: dlswTConnConfigLocalTAddr TAddress,
413: dlswTConnConfigRemoteTAddr TAddress,
414: dlswTConnConfigLastModifyTime TimeTicks,
415: dlswTConnConfigEntryType INTEGER,
416: dlswTConnConfigGroupDefinition RowPointer,
417: dlswTConnConfigSetupType INTEGER,
418: dlswTConnConfigSapList OCTET STRING,
419: dlswTConnConfigAdvertiseMacNB TruthValue,
420: dlswTConnConfigInitCirRecvWndw INTEGER,
421: dlswTConnConfigOpens Counter32,
422: dlswTConnConfigRowStatus RowStatus
423: }
424:
425: dlswTConnConfigIndex OBJECT-TYPE
426: SYNTAX INTEGER (0..2147483647)
426: warning -
warning: use Integer32 instead of INTEGER in SMIv2
427: MAX-ACCESS not-accessible
428: STATUS current
429: DESCRIPTION
430: "The index to the conceptual row of the table.
431: Negative numbers are not allowed. There
432: are objects defined that point to conceptual
433: rows of this table with this index value.
434: Zero is used to denote that no corresponding
435: row exists.
436:
437: Index values are assigned by the agent, and
438: should not be reused but should continue to
439: increase in value."
440: ::= { dlswTConnConfigEntry 1 }
441:
442: dlswTConnConfigTDomain OBJECT-TYPE
443: SYNTAX OBJECT IDENTIFIER
444: MAX-ACCESS read-create
445: STATUS current
446: DESCRIPTION
447: "The object identifier which indicates the transport
448: domain of this conceptual row."
449: ::= { dlswTConnConfigEntry 2 }
450:
451: dlswTConnConfigLocalTAddr OBJECT-TYPE
452: SYNTAX TAddress
453: MAX-ACCESS read-create
454: STATUS current
455: DESCRIPTION
456: "The local transport address for this conceptual row
457: of the transport connection definition."
458: ::= { dlswTConnConfigEntry 3 }
459:
460: dlswTConnConfigRemoteTAddr OBJECT-TYPE
461: SYNTAX TAddress
462: MAX-ACCESS read-create
463: STATUS current
464: DESCRIPTION
465: "The remote transport address. Together with
466: dlswTConnConfigEntryType and dlswTConnConfigGroupDefinition,
467: the object instance of this conceptual row identifies a
468: collection of the transport connections that will be
469: either initiated by this DLSw or initiated by a partner
470: DLSw and accepted by this DLSw."
471: ::= { dlswTConnConfigEntry 4 }
472:
473: dlswTConnConfigLastModifyTime OBJECT-TYPE
474: SYNTAX TimeTicks
475: UNITS "hundredths of a second"
476: MAX-ACCESS read-only
477: STATUS current
478: DESCRIPTION
479: "The time (in hundredths of a second) since the value of
480: any object in this conceptual row except for
481: dlswTConnConfigOpens was last changed. This value
482: may be compared to dlswTConnOperConnectTime to
483: determine whether values in this row are completely
484: valid for a transport connection created using
485: this row definition."
486: ::= { dlswTConnConfigEntry 5 }
487:
488: dlswTConnConfigEntryType OBJECT-TYPE
489: SYNTAX INTEGER {
490: individual (1),
491: global (2),
492: group (3)
493: }
494: MAX-ACCESS read-create
495: STATUS current
496: DESCRIPTION
497: "The object instance signifies the type of entry in the
498: associated conceptual row. The value of `individual'
499: means that the entry applies to a specific partner DLSw
500: node as identified by dlswTConnConfigRemoteTAddr and
501: dlswTConnConfigTDomain. The value of `global'
502: means that the entry applies to all partner DLSw nodes
503: of the TDomain. The value of 'group' means that the entry
504: applies to a specific set of DLSw nodes in the TDomain.
505: Any group definitions are enterprise-specific and are pointed
506: to by dlswTConnConfigGroupDefinition. In the cases of
507: `global' and `group', the value in dlswTConnConfigRemoteTAddr
508: may not have any significance."
509: ::= { dlswTConnConfigEntry 6 }
510:
511: dlswTConnConfigGroupDefinition OBJECT-TYPE
512: SYNTAX RowPointer
513: MAX-ACCESS read-create
514: STATUS current
515: DESCRIPTION
516: "For conceptual rows of `individual' and `global' as
517: specified in dlswTConnConfigEntryType, the instance
518: of this object is `0.0'. For conceptual rows of
519: `group', the instance points to the specific
520: group definition."
521: ::= { dlswTConnConfigEntry 7 }
522:
523: dlswTConnConfigSetupType OBJECT-TYPE
524:
525: SYNTAX INTEGER {
526: other (1),
527: activePersistent (2),
528: activeOnDemand (3),
529: passive (4),
530: excluded (5)
531: }
532: MAX-ACCESS read-create
533: STATUS current
534: DESCRIPTION
535: "This value of the instance of a conceptual row
536: identifies the behavior of the collection of
537: transport connections that this conceptual row
538: defines. The value of activePersistent, activeOnDemand
539: and passive means this DLSw will accept any transport
540: connections, initiated by partner DLSw nodes, which
541: are defined by this conceptual row. The value of
542: activePersistent means this DLSw will also initiate
543: the transport connections of this conceptual row and
544: retry periodically if necessary. The value of
545: activeOnDemand means this DLSw will initiate a
546: transport connection of this conceptual row, if
547: there is a directory cache hits. The value of
548: other is implementation specific. The value of exclude
549: means that the specified node is not allowed to be
550: a partner to this DLSw node. To take a certain
551: conceptual row definition out of service, a value of
552: notInService for dlswTConnConfigRowStatus should be
553: used."
554: DEFVAL { passive }
555: ::= { dlswTConnConfigEntry 8 }
556:
557: dlswTConnConfigSapList OBJECT-TYPE
558: SYNTAX OCTET STRING (SIZE(16))
559: MAX-ACCESS read-create
560: STATUS current
561: DESCRIPTION
562: "The SAP list indicates which SAPs are advertised to
563: the transport connection defined by this conceptual
564: row. Only SAPs with even numbers are represented,
565: in the form of the most significant bit of the first
566: octet representing the SAP 0, the next most significant
567: bit representing the SAP 2, to the least significant
568: bit of the last octet representing the SAP 254. Data
569: link switching is allowed for those SAPs which have
570: one in its corresponding bit, not allowed otherwise.
571: The whole SAP list has to be changed together. Changing
572: the SAP list affects only new circuit establishments
573: and has no effect on established circuits.
574:
575: This list can be used to restrict specific partners
576: from knowing about all the SAPs used by DLSw on all its
577: interfaces (these are represented in dlswIfSapList for
578: each interface). For instance, one may want to run NetBIOS
579: with some partners but not others.
580:
581: If a node supports sending run-time capabilities exchange
582: messages, changes to this object should cause that action.
583: When to start the run-time capabilities exchange is
584: implementation-specific.
585: The DEFVAL below indicates support for SAPs 0, 4, 8, and C."
586: DEFVAL { 'AA000000000000000000000000000000'H }
587: ::= { dlswTConnConfigEntry 9 }
588:
589: dlswTConnConfigAdvertiseMacNB OBJECT-TYPE
590: SYNTAX TruthValue
591: MAX-ACCESS read-create
592: STATUS current
593: DESCRIPTION
594: "The value of true indicates that any defined local MAC
595: addresses and NetBIOS names will be advertised to a
596: partner node via initial and (if supported) run-time
597: capabilities exchange messages. The DLSw node should send
598: the appropriate exclusivity control vector to accompany
599: each list it sends, or to represent that the node is
600: explicitly configured to have a null list.
601:
602: The value of false indicates that the DLSw node should not
603: send a MAC address list or NetBIOS name list, and should
604: also not send their corresponding exclusivity control
605: vectors."
606: DEFVAL { true }
607: ::= { dlswTConnConfigEntry 10 }
608:
609: dlswTConnConfigInitCirRecvWndw OBJECT-TYPE
610: SYNTAX INTEGER (0..65535)
610: warning -
warning: use Integer32 instead of INTEGER in SMIv2
611: UNITS "SSP messages"
612: MAX-ACCESS read-create
613: STATUS current
614: DESCRIPTION
615: "The initial circuit receive pacing window size, in the unit
616: of SSP messages, to be used for future transport connections
617: activated using this table row. The managed node sends this
618: value as its initial receive pacing window in its initial
619: capabilities exchange message. Changing this value does not
620: affect the initial circuit receive pacing window size of
621: currently active transport connections. If the standard window
622: pacing scheme is not supported, the value is zero.
623:
624: A larger receive window value may be appropriate for partners
625: that are reachable only via physical paths that have longer
626: network delays."
627: DEFVAL { 1 }
628: ::= { dlswTConnConfigEntry 11 }
629:
630: dlswTConnConfigOpens OBJECT-TYPE
631: SYNTAX Counter32
632: MAX-ACCESS read-only
633: STATUS current
634: DESCRIPTION
635: "Number of times transport connections entered
636: connected state according to the definition of
637: this conceptual row."
638: ::= { dlswTConnConfigEntry 12 }
639:
640: dlswTConnConfigRowStatus OBJECT-TYPE
641: SYNTAX RowStatus
642: MAX-ACCESS read-create
643: STATUS current
644: DESCRIPTION
645: "This object is used by the manager to create
646: or delete the row entry in the dlswTConnConfigTable
647: following the RowStatus textual convention. The value
648: of notInService will be used to take a conceptual
649: row definition out of use."
650: ::= { dlswTConnConfigEntry 13 }
651:
652: -- -------------------------------------------------------------------
652: warning -
warning: note, -- terminates a comment
652: severe -
lexically unexpected character, skipping to end of line
653: -- Transport Connection Operation Table
654: -- -------------------------------------------------------------------
654: warning -
warning: note, -- terminates a comment
654: severe -
lexically unexpected character, skipping to end of line
655: -- (1) At most one transport connection can be connected between
656: -- this DLSw and one of its DLSw partners at a given time.
657: -- (2) Multiple transport types are supported.
658: -- (3) Since the entries may be reused, dlswTConnOperEntryTime
659: -- needs to be consulted for the possibility of counter reset.
660: -- -------------------------------------------------------------------
660: warning -
warning: note, -- terminates a comment
660: severe -
lexically unexpected character, skipping to end of line
661:
662: dlswTConnOperTable OBJECT-TYPE
663: SYNTAX SEQUENCE OF DlswTConnOperEntry
664: MAX-ACCESS not-accessible
665: STATUS current
666: DESCRIPTION
667: "A list of transport connections. It is optional but
668: desirable for the agent to keep an entry for some
669: period of time after the transport connection is
670: disconnected. This allows the manager to capture
671: additional useful information about the connection, in
672: particular, statistical information and the cause of the
673: disconnection."
674: ::= { dlswTConn 3 }
675:
676: dlswTConnOperEntry OBJECT-TYPE
676: warning -
warning: index of row `dlswTConnOperEntry' can exceed OID size limit by 264 subidentifier(s)
677: SYNTAX DlswTConnOperEntry
678: MAX-ACCESS not-accessible
679: STATUS current
680: DESCRIPTION
681: ""
681: warning -
warning: zero-length description string
682: INDEX { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr }
683: ::= { dlswTConnOperTable 1 }
684:
685: DlswTConnOperEntry ::= SEQUENCE {
686: dlswTConnOperTDomain OBJECT IDENTIFIER,
687: dlswTConnOperLocalTAddr TAddress,
688: dlswTConnOperRemoteTAddr TAddress,
689:
690: dlswTConnOperEntryTime TimeTicks,
691: dlswTConnOperConnectTime TimeTicks,
692: dlswTConnOperState INTEGER,
693: dlswTConnOperConfigIndex INTEGER,
694: dlswTConnOperFlowCntlMode INTEGER,
695:
696: dlswTConnOperPartnerVersion OCTET STRING,
697: dlswTConnOperPartnerVendorID OCTET STRING,
698: dlswTConnOperPartnerVersionStr DisplayString,
699: dlswTConnOperPartnerInitPacingWndw INTEGER,
700:
701: dlswTConnOperPartnerSapList OCTET STRING,
702: dlswTConnOperPartnerNBExcl TruthValue,
703: dlswTConnOperPartnerMacExcl TruthValue,
704: dlswTConnOperPartnerNBInfo INTEGER,
705: dlswTConnOperPartnerMacInfo INTEGER,
706:
707: dlswTConnOperDiscTime TimeTicks,
708: dlswTConnOperDiscReason INTEGER,
709: dlswTConnOperDiscActiveCir INTEGER,
710:
711: dlswTConnOperInDataPkts Counter32,
712: dlswTConnOperOutDataPkts Counter32,
713: dlswTConnOperInDataOctets Counter32,
714: dlswTConnOperOutDataOctets Counter32,
715:
716: dlswTConnOperInCntlPkts Counter32,
717: dlswTConnOperOutCntlPkts Counter32,
718:
719: dlswTConnOperCURexSents Counter32,
720: dlswTConnOperICRexRcvds Counter32,
721: dlswTConnOperCURexRcvds Counter32,
722: dlswTConnOperICRexSents Counter32,
723:
724: dlswTConnOperNQexSents Counter32,
725: dlswTConnOperNRexRcvds Counter32,
726: dlswTConnOperNQexRcvds Counter32,
727: dlswTConnOperNRexSents Counter32,
728: dlswTConnOperCirCreates Counter32,
729: dlswTConnOperCircuits Gauge32
730: }
731:
732: dlswTConnOperTDomain OBJECT-TYPE
732: minor error -
index element `dlswTConnOperTDomain' of row `dlswTConnOperEntry' should but cannot have a size restriction
732: minor error -
index element `dlswTConnOperTDomain' of row `dlswTConnTcpOperEntry' should but cannot have a size restriction
733: SYNTAX OBJECT IDENTIFIER
734: MAX-ACCESS not-accessible
735: STATUS current
736: DESCRIPTION
737: "The object identifier indicates the transport domain
738: of this transport connection."
739: ::= { dlswTConnOperEntry 1 }
740:
741: dlswTConnOperLocalTAddr OBJECT-TYPE
742: SYNTAX TAddress
743: MAX-ACCESS read-only
744: STATUS current
745: DESCRIPTION
746: "The local transport address for this transport connection.
747: This value could be different from dlswTConnConfigLocalAddr,
748: if the value of the latter were changed after this transport
749: connection was established."
750: ::= { dlswTConnOperEntry 2 }
751:
752: dlswTConnOperRemoteTAddr OBJECT-TYPE
753: SYNTAX TAddress
754: MAX-ACCESS not-accessible
755: STATUS current
756: DESCRIPTION
757: "The remote transport address of this transport connection."
758: ::= { dlswTConnOperEntry 3 }
759:
760: dlswTConnOperEntryTime OBJECT-TYPE
761: SYNTAX TimeTicks
762: UNITS "hundredths of a second"
763: MAX-ACCESS read-only
764: STATUS current
765: DESCRIPTION
766: "The amount of time (in hundredths of a second) since this
767: transport connection conceptual row was created."
768: ::= { dlswTConnOperEntry 4 }
769:
770: -- ...................................................................
771: -- DLSw Transport Connection Operational Objects
772: -- ...................................................................
773:
774: dlswTConnOperConnectTime OBJECT-TYPE
775: SYNTAX TimeTicks
776: UNITS "hundredths of a second"
777: MAX-ACCESS read-only
778: STATUS current
779: DESCRIPTION
780: "The amount of time (in hundredths of a second) since this
781: transport connection last entered the 'connected' state.
782: A value of zero means this transport connection has never
783: been established."
784: ::= { dlswTConnOperEntry 5 }
785:
786: dlswTConnOperState OBJECT-TYPE
787: SYNTAX INTEGER {
788: connecting (1),
789: initCapExchange (2),
790: connected (3),
791: quiescing (4),
792: disconnecting (5),
793: disconnected (6)
794: }
795: MAX-ACCESS read-write
796: STATUS current
797: DESCRIPTION
798: "The state of this transport connection. The transport
799: connection enters `connecting' state when DLSw makes
800: a connection request to the transport layer. Once initial
801: Capabilities Exchange is sent, the transport connection
802: enters enters `initCapExchange' state. When partner
803: capabilities have been determined and the transport
804: connection is ready for sending CanUReach (CUR) messages,
805: it moves to the `connected' state. When DLSw is in the
806: process of bringing down the connection, it is in the
807: `disconnecting' state. When the transport layer
808: indicates one of its connections is disconnected, the
809: transport connection moves to the `disconnected' state.
810:
811: Whereas all of the values will be returned in response
812: to a management protocol retrieval operation, only two
813: values may be specified in a management protocol set
814: operation: `quiescing' and `disconnecting'. Changing
815: the value to `quiescing' prevents new circuits from being
816: established, and will cause a transport disconnect when
817: the last circuit on the connection goes away. Changing
818: the value to `disconnecting' will force off all circuits
819: immediately and bring the connection to `disconnected'
820: state."
821: ::= { dlswTConnOperEntry 6 }
822:
823: dlswTConnOperConfigIndex OBJECT-TYPE
824: SYNTAX INTEGER (0..2147483647)
824: warning -
warning: use Integer32 instead of INTEGER in SMIv2
825: MAX-ACCESS read-only
826: STATUS current
827: DESCRIPTION
828: "The value of dlswTConnConfigIndex of the dlswTConnConfigEntry
829: that governs the configuration information used by this
830: dlswTConnOperEntry. The manager can therefore normally
831: examine both configured and operational information
832: for this transport connection.
833:
834: This value is zero if the corresponding dlswTConnConfigEntry
835: was deleted after the creation of this dlswTConnOperEntry.
836: If some fields in the former were changed but the conceptual
837: row was not deleted, some configuration information may not
838: be valid for this operational transport connection. The
839: manager can compare dlswTConnOperConnectTime and
840: dlswTConnConfigLastModifyTime to determine if this condition
841: exists."
842: ::= { dlswTConnOperEntry 7 }
843:
844: -- ...................................................................
845: -- Transport Connection Characteristics
846: -- ...................................................................
847:
848: dlswTConnOperFlowCntlMode OBJECT-TYPE
849: SYNTAX INTEGER {
850: undetermined (1),
851: pacing (2), -- DLSw standard flow control
852: other (3) -- non-DLSw standard flow control
853: }
854: MAX-ACCESS read-only
855: STATUS current
856: DESCRIPTION
857: "The flow control mechanism in use on this transport connection.
858: This value is undetermined (1) before the mode of flow control
859: can be established on a new transport connection (i.e., after
860: CapEx is sent but before Capex or other SSP control messages
861: have been received). Pacing (2) indicates that the standard
862: RFC 1795 pacing mechanism is in use. Other (3) may be either
863: the RFC 1434+ xBusy mechanism operating to a back-level DLSw,
864: or a vendor-specific flow control method. Whether it is xBusy
865: or not can be inferred from dlswTConnOperPartnerVersion."
866: ::= { dlswTConnOperEntry 8 }
867:
868: -- ...................................................................
869:
870: dlswTConnOperPartnerVersion OBJECT-TYPE
871: SYNTAX OCTET STRING (SIZE (0 | 2))
872: MAX-ACCESS read-only
873: STATUS current
874: DESCRIPTION
875: "This value identifies which version (first octet) and release
876: (second octet) of the DLSw standard is supported by this
877: partner DLSw. This information is obtained from a DLSw
878: capabilities exchange message received from the partner DLSw.
879: A string of zero length is returned before a Capabilities
880: Exchange message is received, or if one is never received.
881: A conceptual row with a dlswTConnOperState of `connected' but
882: a zero length partner version indicates that the partner is
883: a non-standard DLSw partner.
884:
885: If an implementation chooses to keep dlswTConnOperEntrys in
886: the `disconnected' state, this value should remain unchanged."
887: REFERENCE
888: "DLSW: Switch-to-Switch Protocol RFC 1795"
889: ::= { dlswTConnOperEntry 9 }
890:
891: dlswTConnOperPartnerVendorID OBJECT-TYPE
892: SYNTAX OCTET STRING (SIZE (0 | 3))
893: MAX-ACCESS read-only
894: STATUS current
895: DESCRIPTION
896: "This value identifies the IEEE-assigned organizationally
897: Unique Identifier (OUI) of the maker of this partner
898: DLSw. This information is obtained from a DLSw
899: capabilities exchange message received from the partner DLSw.
900: A string of zero length is returned before a Capabilities
901: Exchange message is received, or if one is never received.
902:
903: If an implementation chooses to keep dlswTConnOperEntrys in
904: the `disconnected' state, this value should remain unchanged."
905: ::= { dlswTConnOperEntry 10 }
906:
907: dlswTConnOperPartnerVersionStr OBJECT-TYPE
908: SYNTAX DisplayString (SIZE (0..253))
909: MAX-ACCESS read-only
910: STATUS current
911: DESCRIPTION
912: "This value identifies the particular product version (e.g.,
913: product name, code level, fix level) of this partner DLSw.
914: The format of the actual version string is vendor-specific.
915: This information is obtained from a DLSw capabilities exchange
916: message received from the partner DLSw.
917: A string of zero length is returned before a Capabilities
918: Exchange message is received, if one is never received, or
919: if one is received but it does not contain a version string.
920: If an implementation chooses to keep dlswTConnOperEntrys in
921: the `disconnected' state, this value should remain unchanged."
922: REFERENCE
923: "DLSW: Switch-to-Switch Protocol RFC 1795"
924: ::= { dlswTConnOperEntry 11 }
925:
926: dlswTConnOperPartnerInitPacingWndw OBJECT-TYPE
927: SYNTAX INTEGER (0..65535)
927: warning -
warning: use Integer32 instead of INTEGER in SMIv2
928: MAX-ACCESS read-only
929: STATUS current
930: DESCRIPTION
931: "The value of the partner initial receive pacing window. This
932: is our initial send pacing window for all new circuits on this
933: transport connection, as modified and granted by the first flow
934: control indication the partner sends on each circuit.
935: This information is obtained from a DLSw capabilities exchange
936: message received from the partner DLSw.
937: A value of zero is returned before a Capabilities
938: Exchange message is received, or if one is never received.
939:
940: If an implementation chooses to keep dlswTConnOperEntrys in
941: the `disconnected' state, this value should remain unchanged."
942: REFERENCE
943: "DLSW: Switch-to-Switch Protocol RFC 1795"
944: ::= { dlswTConnOperEntry 12 }
945:
946: -- ...................................................................
947:
948: dlswTConnOperPartnerSapList OBJECT-TYPE
949: SYNTAX OCTET STRING (SIZE (0 | 16))
950: MAX-ACCESS read-only
951: STATUS current
952: DESCRIPTION
953: "The Supported SAP List received in the capabilities
954: exchange message from the partner DLSw. This list has
955: the same format described for dlswTConnConfigSapList.
956: A string of zero length is returned before a Capabilities
957: Exchange message is received, or if one is never received.
958:
959: If an implementation chooses to keep dlswTConnOperEntrys in
960: the `disconnected' state, this value should remain unchanged."
961: ::= { dlswTConnOperEntry 13 }
962:
963: dlswTConnOperPartnerNBExcl OBJECT-TYPE
964: SYNTAX TruthValue
965: MAX-ACCESS read-only
966: STATUS current
967: DESCRIPTION
968: "The value of true signifies that the NetBIOS names received
969: from this partner in the NetBIOS name list in its capabilities
970: exchange message are the only NetBIOS names reachable by
971: that partner. `False' indicates that other NetBIOS names may
972: be reachable. `False' should be returned before a Capabilities
973: Exchange message is received, if one is never received, or if
974: one is received without a NB Name Exclusivity CV.
975:
976: If an implementation chooses to keep dlswTConnOperEntrys in
977: the `disconnected' state, this value should remain unchanged."
978: ::= { dlswTConnOperEntry 14 }
979:
980: dlswTConnOperPartnerMacExcl OBJECT-TYPE
981: SYNTAX TruthValue
982: MAX-ACCESS read-only
983: STATUS current
984: DESCRIPTION
985: "The value of true signifies that the MAC addresses received
986: from this partner in the MAC address list in its capabilities
987: exchange message are the only MAC addresses reachable by
988: that partner. `False' indicates that other MAC addresses may
989: be reachable. `False' should be returned before a Capabilities
990: Exchange message is received, if one is never received, or if
991: one is received without a MAC Address Exclusivity CV.
992:
993: If an implementation chooses to keep dlswTConnOperEntrys in
994: the `disconnected' state, this value should remain unchanged."
995: ::= { dlswTConnOperEntry 15 }
996:
997: dlswTConnOperPartnerNBInfo OBJECT-TYPE
998: SYNTAX INTEGER {
999: none (1), -- none is kept
1000: partial (2), -- partial list is kept
1001: complete (3), -- complete list is kept
1002: notApplicable (4)
1003: }
1004: MAX-ACCESS read-only
1005: STATUS current
1006: DESCRIPTION
1007: "It is up to this DSLw whether to keep either none, some,
1008: or all of the NetBIOS name list that was received in
1009: the capabilities exchange message sent by this partner DLSw.
1010: This object identifies how much information was kept by
1011: this DLSw. These names are stored as userConfigured
1012: remote entries in dlswDirNBTable.
1013: A value of (4), notApplicable, should be returned before
1014: a Capabilities Exchange message is received, or if one is
1015: never received.
1016: If an implementation chooses to keep dlswTConnOperEntrys in
1017: the `disconnected' state, this value should remain unchanged."
1018: ::= { dlswTConnOperEntry 16 }
1019:
1020: dlswTConnOperPartnerMacInfo OBJECT-TYPE
1021: SYNTAX INTEGER {
1022: none (1), -- none is kept
1023: partial (2), -- partial list is kept
1024: complete (3), -- complete list is kept
1025: notApplicable (4)
1026: }
1027: MAX-ACCESS read-only
1028: STATUS current
1029: DESCRIPTION
1030: "It is up to this DLSw whether to keep either none, some,
1031: or all of the MAC address list that was received in the
1032: capabilities exchange message sent by this partner DLSw.
1033: This object identifies how much information was kept by
1034: this DLSw. These names are stored as userConfigured
1035: remote entries in dlswDirMACTable.
1036: A value of (4), notApplicable, should be returned before
1037: a Capabilities Exchange message is received, or if one is
1038: never received.
1039:
1040: If an implementation chooses to keep dlswTConnOperEntrys in
1041: the `disconnected' state, this value should remain unchanged."
1042: ::= { dlswTConnOperEntry 17 }
1043:
1044: -- ...................................................................
1045: -- Information about the last disconnect of this transport connection.
1046: -- These objects make sense only for implementations that keep
1047: -- transport connection information around after disconnection.
1048: -- ...................................................................
1049: dlswTConnOperDiscTime OBJECT-TYPE
1050: SYNTAX TimeTicks
1051: UNITS "hundredths of a second"
1052: MAX-ACCESS read-only
1053: STATUS current
1054: DESCRIPTION
1055: "The amount of time (in hundredths of a second) since the
1056: dlswTConnOperState last entered `disconnected' state."
1057: ::= { dlswTConnOperEntry 18 }
1058:
1059: dlswTConnOperDiscReason OBJECT-TYPE
1060: SYNTAX INTEGER {
1061: other (1),
1062: capExFailed (2),
1063: transportLayerDisc (3),
1064: operatorCommand (4),
1065: lastCircuitDiscd (5),
1066: protocolError (6)
1067: }
1068: MAX-ACCESS read-only
1069: STATUS current
1070: DESCRIPTION
1071: "This object signifies the reason that either prevented the
1072: transport connection from entering the connected state, or
1073: caused the transport connection to enter the disconnected
1074: state."
1075: ::= { dlswTConnOperEntry 19 }
1076:
1077: dlswTConnOperDiscActiveCir OBJECT-TYPE
1078: SYNTAX INTEGER (0..2147483647)
1078: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1079: MAX-ACCESS read-only
1080: STATUS current
1081: DESCRIPTION
1082: "The number of circuits active (not in DISCONNECTED state)
1083: at the time the transport connection was last disconnected.
1084: This value is zero if the transport connection has never
1085: been connected."
1086: ::= { dlswTConnOperEntry 20 }
1087:
1088: -- ...................................................................
1089: -- Transport Connection Statistics
1090: -- (1) Traffic counts
1091: -- ...................................................................
1092: dlswTConnOperInDataPkts OBJECT-TYPE
1093: SYNTAX Counter32
1094: UNITS "SSP messages"
1095: MAX-ACCESS read-only
1096: STATUS current
1097: DESCRIPTION
1098: "The number of Switch-to-Switch Protocol (SSP) messages of
1099: type DGRMFRAME, DATAFRAME, or INFOFRAME received on this
1100: transport connection."
1101: ::= { dlswTConnOperEntry 21 }
1102:
1103: dlswTConnOperOutDataPkts OBJECT-TYPE
1104: SYNTAX Counter32
1105: UNITS "SSP messages"
1106: MAX-ACCESS read-only
1107: STATUS current
1108: DESCRIPTION
1109: "The number of Switch-to-Switch Protocol (SSP) messages of
1110: type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this
1111: transport connection."
1112: ::= { dlswTConnOperEntry 22 }
1113:
1114: dlswTConnOperInDataOctets OBJECT-TYPE
1115: SYNTAX Counter32
1116: UNITS "octets"
1117: MAX-ACCESS read-only
1118: STATUS current
1119: DESCRIPTION
1120: "The number octets in Switch-to-Switch Protocol (SSP) messages
1121: of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this
1122: transport connection. Each message is counted starting with
1123: the first octet following the SSP message header."
1124: ::= { dlswTConnOperEntry 23 }
1125:
1126: dlswTConnOperOutDataOctets OBJECT-TYPE
1127: SYNTAX Counter32
1128: UNITS "octets"
1129: MAX-ACCESS read-only
1130: STATUS current
1131: DESCRIPTION
1132: "The number octets in Switch-to-Switch Protocol (SSP) messages
1133: of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this
1134: transport connection. Each message is counted starting with
1135: the first octet following the SSP message header."
1136: ::= { dlswTConnOperEntry 24 }
1137:
1138: dlswTConnOperInCntlPkts OBJECT-TYPE
1139: SYNTAX Counter32
1140: UNITS "SSP messages"
1141: MAX-ACCESS read-only
1142: STATUS current
1143: DESCRIPTION
1144: "The number of Switch-to-Switch Protocol (SSP) messages
1145: received on this transport connection which were not of
1146: type DGRMFRAME, DATAFRAME, or INFOFRAME."
1147: ::= { dlswTConnOperEntry 25 }
1148:
1149: dlswTConnOperOutCntlPkts OBJECT-TYPE
1150: SYNTAX Counter32
1151: UNITS "SSP messages"
1152: MAX-ACCESS read-only
1153: STATUS current
1154: DESCRIPTION
1155: "The number of Switch-to-Switch Protocol (SSP) messages of
1156: transmitted on this transport connection which were not of
1157: type DGRMFRAME, DATAFRAME, or INFOFRAME."
1158: ::= { dlswTConnOperEntry 26 }
1159:
1160: -- ...................................................................
1161: -- (2) Directory activities (Explorer messages)
1162: -- ...................................................................
1163:
1164: dlswTConnOperCURexSents OBJECT-TYPE
1165: SYNTAX Counter32
1166: MAX-ACCESS read-only
1167: STATUS current
1168: DESCRIPTION
1169: "The number of CanUReach_ex messages sent on this transport
1170: connection."
1171: ::= { dlswTConnOperEntry 27 }
1172:
1173: dlswTConnOperICRexRcvds OBJECT-TYPE
1174: SYNTAX Counter32
1175: MAX-ACCESS read-only
1176: STATUS current
1177: DESCRIPTION
1178: "The number of ICanReach_ex messages received on this transport
1179: connection."
1180: ::= { dlswTConnOperEntry 28 }
1181:
1182: dlswTConnOperCURexRcvds OBJECT-TYPE
1183: SYNTAX Counter32
1184: MAX-ACCESS read-only
1185: STATUS current
1186: DESCRIPTION
1187: "The number of CanUReach_ex messages received on this transport
1188: connection."
1189: ::= { dlswTConnOperEntry 29 }
1190:
1191: dlswTConnOperICRexSents OBJECT-TYPE
1192: SYNTAX Counter32
1193: MAX-ACCESS read-only
1194: STATUS current
1195: DESCRIPTION
1196: "The number of ICanReach_ex messages sent on this transport
1197: connection."
1198: ::= { dlswTConnOperEntry 30 }
1199:
1200: -- ...................................................................
1201:
1202: dlswTConnOperNQexSents OBJECT-TYPE
1203: SYNTAX Counter32
1204: MAX-ACCESS read-only
1205: STATUS current
1206: DESCRIPTION
1207: "The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer)
1208: messages sent on this transport connection."
1209: ::= { dlswTConnOperEntry 31 }
1210:
1211: dlswTConnOperNRexRcvds OBJECT-TYPE
1212: SYNTAX Counter32
1213: MAX-ACCESS read-only
1214: STATUS current
1215: DESCRIPTION
1216: "The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer)
1217: messages received on this transport connection."
1218: ::= { dlswTConnOperEntry 32 }
1219:
1220: dlswTConnOperNQexRcvds OBJECT-TYPE
1221: SYNTAX Counter32
1222: MAX-ACCESS read-only
1223: STATUS current
1224: DESCRIPTION
1225: "The number of NETBIOS_NQ_ex messages received on this
1226: transport connection."
1227: ::= { dlswTConnOperEntry 33 }
1228:
1229: dlswTConnOperNRexSents OBJECT-TYPE
1230: SYNTAX Counter32
1231: MAX-ACCESS read-only
1232: STATUS current
1233: DESCRIPTION
1234: "The number of NETBIOS_NR_ex messages sent on this transport
1235: connection."
1236: ::= { dlswTConnOperEntry 34 }
1237:
1238: -- ...................................................................
1239: -- (3) Circuit activities on each transport connection
1240: -- ...................................................................
1241: dlswTConnOperCirCreates OBJECT-TYPE
1242: SYNTAX Counter32
1243: MAX-ACCESS read-only
1244: STATUS current
1245: DESCRIPTION
1246: "The number of times that circuits entered `circuit_established'
1247: state (not counting transitions from `circuit_restart')."
1248: ::= { dlswTConnOperEntry 35 }
1249:
1250: dlswTConnOperCircuits OBJECT-TYPE
1251: SYNTAX Gauge32
1252: MAX-ACCESS read-only
1253: STATUS current
1254: DESCRIPTION
1255: "The number of currently active circuits on this transport
1256: connection, where `active' means not in `disconnected' state."
1257: ::= { dlswTConnOperEntry 36 }
1258:
1259:
1260: -- -------------------------------------------------------------------
1260: warning -
warning: note, -- terminates a comment
1260: severe -
lexically unexpected character, skipping to end of line
1261: -- Transport Connection Specific
1262: -- -------------------------------------------------------------------
1262: warning -
warning: note, -- terminates a comment
1262: severe -
lexically unexpected character, skipping to end of line
1263: dlswTConnSpecific OBJECT IDENTIFIER ::= { dlswTConn 4 }
1264: dlswTConnTcp OBJECT IDENTIFIER ::= { dlswTConnSpecific 1 }
1265:
1266: -- ...................................................................
1267: -- TCP Transport Connection Specific -- Configuration
1268: -- ...................................................................
1269: dlswTConnTcpConfigTable OBJECT-TYPE
1269: error -
`Configuration' should start with a lower case letter
1269: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
1270: SYNTAX SEQUENCE OF DlswTConnTcpConfigEntry
1271: MAX-ACCESS not-accessible
1272: STATUS current
1273: DESCRIPTION
1274: "This table defines the TCP transport connections that
1275: will be either initiated by or accepted by this DSLw.
1276: It augments the entries in dlswTConnConfigTable whose domain
1277: is dlswTCPDomain."
1278: ::= { dlswTConnTcp 1 }
1278: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1279:
1280: dlswTConnTcpConfigEntry OBJECT-TYPE
1280: error -
row's parent node must be a table node
1281: SYNTAX DlswTConnTcpConfigEntry
1282: MAX-ACCESS not-accessible
1283: STATUS current
1284: DESCRIPTION
1285: "Each conceptual row defines parameters that are
1286: specific to dlswTCPDomain transport connections."
1287: INDEX { dlswTConnConfigIndex }
1288: ::= { dlswTConnTcpConfigTable 1 }
1288: severe -
unknown object identifier label `dlswTConnTcpConfigTable'
1289:
1290: DlswTConnTcpConfigEntry ::= SEQUENCE {
1291: dlswTConnTcpConfigKeepAliveInt INTEGER,
1292: dlswTConnTcpConfigTcpConnections INTEGER,
1293: dlswTConnTcpConfigMaxSegmentSize INTEGER
1294: }
1295:
1296: dlswTConnTcpConfigKeepAliveInt OBJECT-TYPE
1297: SYNTAX INTEGER (0..1800)
1297: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1298: UNITS "seconds"
1299: MAX-ACCESS read-create
1300: STATUS current
1301: DESCRIPTION
1302: "The time in seconds between TCP keepAlive messages when
1303: no traffic is flowing. Zero signifies no keepAlive protocol.
1304: Changes take effect only for new TCP connections."
1305: DEFVAL { 0 }
1306: ::= { dlswTConnTcpConfigEntry 1 }
1307:
1308: dlswTConnTcpConfigTcpConnections OBJECT-TYPE
1309: SYNTAX INTEGER (1..16)
1309: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1310: MAX-ACCESS read-create
1311: STATUS current
1312: DESCRIPTION
1313: "This is our preferred number of TCP connections within a
1314: TCP transport connection. The actual number used is negotiated
1315: at capabilities exchange time. Changes take effect only
1316: for new transport connections."
1317: DEFVAL { 2 }
1318: ::= { dlswTConnTcpConfigEntry 2 }
1319:
1320: dlswTConnTcpConfigMaxSegmentSize OBJECT-TYPE
1321: SYNTAX INTEGER (0..65535)
1321: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1322: UNITS "packets"
1323: MAX-ACCESS read-create
1324: STATUS current
1325: DESCRIPTION
1326: "This is the number of bytes that this node is
1327: willing to receive over the read TCP connection(s).
1328: Changes take effect for new transport connections."
1329: DEFVAL { 4096 }
1330: ::= { dlswTConnTcpConfigEntry 3 }
1331:
1332:
1333: -- ...................................................................
1334: -- TCP Transport Connection Specific -- Operation
1335: -- ...................................................................
1336: dlswTConnTcpOperTable OBJECT-TYPE
1336: error -
`Operation' should start with a lower case letter
1336: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
1337: SYNTAX SEQUENCE OF DlswTConnTcpOperEntry
1338: MAX-ACCESS not-accessible
1339: STATUS current
1340: DESCRIPTION
1341: "A list of TCP transport connections. It is optional
1342: but desirable for the agent to keep an entry for some
1343: period of time after the transport connection is
1344: disconnected. This allows the manager to capture
1345: additional useful information about the connection, in
1346: particular, statistical information and the cause of the
1347: disconnection."
1348: ::= { dlswTConnTcp 2 }
1348: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1349:
1350: dlswTConnTcpOperEntry OBJECT-TYPE
1350: error -
row's parent node must be a table node
1350: warning -
warning: index of row `dlswTConnTcpOperEntry' can exceed OID size limit by 260 subidentifier(s)
1351: SYNTAX DlswTConnTcpOperEntry
1352: MAX-ACCESS not-accessible
1353: STATUS current
1354: DESCRIPTION
1355: ""
1355: warning -
warning: zero-length description string
1356: INDEX { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr }
1357: ::= { dlswTConnTcpOperTable 1 }
1357: severe -
unknown object identifier label `dlswTConnTcpOperTable'
1358:
1359: DlswTConnTcpOperEntry ::= SEQUENCE {
1360: dlswTConnTcpOperKeepAliveInt INTEGER,
1361: dlswTConnTcpOperPrefTcpConnections INTEGER,
1362: dlswTConnTcpOperTcpConnections INTEGER
1363: }
1364:
1365: dlswTConnTcpOperKeepAliveInt OBJECT-TYPE
1366: SYNTAX INTEGER (0..1800)
1366: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1367: UNITS "seconds"
1368: MAX-ACCESS read-only
1369: STATUS current
1370: DESCRIPTION
1371: "The time in seconds between TCP keepAlive messages when
1372: no traffic is flowing. Zero signifies no keepAlive protocol is
1373: operating."
1374: ::= { dlswTConnTcpOperEntry 1 }
1375:
1376: dlswTConnTcpOperPrefTcpConnections OBJECT-TYPE
1377: SYNTAX INTEGER (1..16)
1377: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1378: MAX-ACCESS read-only
1379: STATUS current
1380: DESCRIPTION
1381: "This is the number of TCP connections preferred by this DLSw
1382: partner, as received in its capabilities exchange message."
1383: ::= { dlswTConnTcpOperEntry 2 }
1384:
1385:
1386: dlswTConnTcpOperTcpConnections OBJECT-TYPE
1387: SYNTAX INTEGER (1..16)
1387: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1388: MAX-ACCESS read-only
1389: STATUS current
1390: DESCRIPTION
1391: "This is the actual current number of TCP connections within
1392: this transport connection."
1393: ::= { dlswTConnTcpOperEntry 3 }
1394:
1395: -- *******************************************************************
1396: -- DLSW INTERFACE GROUP
1397: -- *******************************************************************
1398:
1399: dlswIfTable OBJECT-TYPE
1400: SYNTAX SEQUENCE OF DlswIfEntry
1401: MAX-ACCESS not-accessible
1402: STATUS current
1403: DESCRIPTION
1404: "The list of interfaces on which DLSw is active."
1405: ::= { dlswInterface 1 }
1406:
1407: dlswIfEntry OBJECT-TYPE
1408: SYNTAX DlswIfEntry
1409: MAX-ACCESS not-accessible
1410: STATUS current
1411: DESCRIPTION
1412: ""
1412: warning -
warning: zero-length description string
1413: INDEX { ifIndex }
1414: ::= { dlswIfTable 1 }
1415:
1416: DlswIfEntry ::= SEQUENCE {
1417: dlswIfRowStatus RowStatus,
1418: dlswIfVirtualSegment INTEGER,
1419: dlswIfSapList OCTET STRING
1420: }
1421:
1422: dlswIfRowStatus OBJECT-TYPE
1423: SYNTAX RowStatus
1424: MAX-ACCESS read-create
1425: STATUS current
1426: DESCRIPTION
1427: "This object is used by the manager to create
1428: or delete the row entry in the dlswIfTable
1429: following the RowStatus textual convention."
1430: ::= { dlswIfEntry 1 }
1431:
1432: dlswIfVirtualSegment OBJECT-TYPE
1433: SYNTAX INTEGER (0..4095 | 65535)
1433: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1434: MAX-ACCESS read-create
1435: STATUS current
1436: DESCRIPTION
1437: "The segment number that uniquely identifies the virtual
1438: segment to which this DLSw interface is connected.
1439: Current source routing protocols limit this value to
1440: the range 0 - 4095. (The value 0 is used by some
1441: management applications for special test cases.)
1442: A value of 65535 signifies that no virtual segment
1443: is assigned to this interface. For instance,
1444: in a non-source routing environment, segment number
1445: assignment is not required."
1446: DEFVAL { 65535 }
1447: ::= { dlswIfEntry 2 }
1448:
1449: dlswIfSapList OBJECT-TYPE
1450: SYNTAX OCTET STRING (SIZE(16))
1451: MAX-ACCESS read-create
1452: STATUS current
1453: DESCRIPTION
1454: "The SAP list indicates which SAPs are allowed to be
1455: data link switched through this interface. This list
1456: has the same format described for dlswTConnConfigSapList.
1457:
1458: When changes to this object take effect is implementation-
1459: specific. Turning off a particular SAP can destroy
1460: active circuits that are using that SAP. An agent
1461: implementation may reject such changes until there are no
1462: active circuits if it so chooses. In this case, it is up
1463: to the manager to close the circuits first, using
1464: dlswCircuitState.
1465:
1466: The DEFVAL below indicates support for SAPs 0, 4, 8, and C."
1467: DEFVAL { 'AA000000000000000000000000000000'H }
1468: ::= { dlswIfEntry 3 }
1469:
1470:
1471: -- *******************************************************************
1472: -- DIRECTORY
1473: -- Directory services caches the locations of MAC addresses
1474: -- and NetBIOS names. For resources which are attached via
1475: -- local interfaces, the ifIndex may be cached, and for
1476: -- resources which are reachable via a DLSw partner, the
1477: -- transport address of the DLSw partner is cached.
1478: -- *******************************************************************
1479:
1480: -- -------------------------------------------------------------------
1480: warning -
warning: note, -- terminates a comment
1480: severe -
lexically unexpected character, skipping to end of line
1481: -- Directory Related Statistical Objects
1482: -- -------------------------------------------------------------------
1482: warning -
warning: note, -- terminates a comment
1482: severe -
lexically unexpected character, skipping to end of line
1483: dlswDirStat OBJECT IDENTIFIER ::= { dlswDirectory 1 }
1484:
1485: dlswDirMacEntries OBJECT-TYPE
1486: SYNTAX Gauge32
1487: MAX-ACCESS read-only
1488: STATUS current
1489: DESCRIPTION
1490: "The current total number of entries in the dlswDirMacTable."
1491: ::= { dlswDirStat 1 }
1492:
1493: dlswDirMacCacheHits OBJECT-TYPE
1494: SYNTAX Counter32
1495: MAX-ACCESS read-only
1496: STATUS current
1497: DESCRIPTION
1498: "The number of times a cache search for a particular MAC address
1499: resulted in success."
1500: ::= { dlswDirStat 2 }
1501:
1502: dlswDirMacCacheMisses OBJECT-TYPE
1503: SYNTAX Counter32
1504: MAX-ACCESS read-only
1505: STATUS current
1506: DESCRIPTION
1507: "The number of times a cache search for a particular MAC address
1508: resulted in failure."
1509: ::= { dlswDirStat 3 }
1510:
1511: dlswDirMacCacheNextIndex OBJECT-TYPE
1512: SYNTAX INTEGER (0..2147483647)
1512: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1513: MAX-ACCESS read-only
1514: STATUS current
1515: DESCRIPTION
1516: "The next value of dlswDirMacIndex to be assigned by
1517: the agent. A retrieval of this object atomically reserves
1518: the returned value for use by the manager to create a row
1519: in dlswDirMacTable. This makes it possible for the agent
1520: to control the index space of the MAC address cache, yet
1521: allows the manager to administratively create new rows."
1522: ::= { dlswDirStat 4 }
1523:
1524: dlswDirNBEntries OBJECT-TYPE
1525: SYNTAX Gauge32
1526: MAX-ACCESS read-only
1527: STATUS current
1528: DESCRIPTION
1529: "The current total number of entries in the dlswDirNBTable."
1530: ::= { dlswDirStat 5 }
1531:
1532: dlswDirNBCacheHits OBJECT-TYPE
1533: SYNTAX Counter32
1534: MAX-ACCESS read-only
1535: STATUS current
1536: DESCRIPTION
1537: "The number of times a cache search for a particular NetBIOS
1538: name resulted in success."
1539: ::= { dlswDirStat 6 }
1540:
1541: dlswDirNBCacheMisses OBJECT-TYPE
1542: SYNTAX Counter32
1543: MAX-ACCESS read-only
1544: STATUS current
1545: DESCRIPTION
1546: "The number of times a cache search for a particular NetBIOS
1547: name resulted in failure."
1548: ::= { dlswDirStat 7 }
1549:
1550: dlswDirNBCacheNextIndex OBJECT-TYPE
1551: SYNTAX INTEGER (0..2147483647)
1551: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1552: MAX-ACCESS read-only
1553: STATUS current
1554: DESCRIPTION
1555: "The next value of dlswDirNBIndex to be assigned by the
1556: agent. A retrieval of this object atomically reserves
1557: the returned value for use by the manager to create
1558: a row in dlswDirNBTable. This makes it possible for the
1559: agent to control the index space for the NetBIOS name
1560: cache, yet allows the manager to administratively
1561: create new rows."
1562: ::= { dlswDirStat 8 }
1563:
1564: -- -------------------------------------------------------------------
1564: warning -
warning: note, -- terminates a comment
1564: severe -
lexically unexpected character, skipping to end of line
1565: -- Directory Cache
1566: -- -------------------------------------------------------------------
1566: warning -
warning: note, -- terminates a comment
1566: severe -
lexically unexpected character, skipping to end of line
1567: dlswDirCache OBJECT IDENTIFIER ::= { dlswDirectory 2 }
1568:
1569: -- ...................................................................
1570: -- Directory for MAC Addresses.
1571: -- All Possible combinations of values of these objects.
1572: --
1573: -- EntryType LocationType Location Status
1574: -- -------------- ------------ ------------------ --------------
1575: -- userConfigured local ifEntry or 0.0 reachable, or
1576: -- notReachable, or
1577: -- unknown
1578: -- userConfigured remote TConnConfigEntry reachable, or
1579: -- notReachable, or
1580: -- unknown
1581: -- partnerCapExMsg remote TConnOperEntry unknown
1582: -- dynamic local ifEntry or 0.0 reachable
1583: -- dynamic remote TConnOperEntry reachable
1584: --
1585: -- ...................................................................
1586: dlswDirMacTable OBJECT-TYPE
1587: SYNTAX SEQUENCE OF DlswDirMacEntry
1588: MAX-ACCESS not-accessible
1589: STATUS current
1590: DESCRIPTION
1591: "This table contains locations of MAC addresses.
1592: They could be either verified or not verified,
1593: local or remote, and configured locally or learned
1594: from either Capabilities Exchange messages or
1595: directory searches."
1596: ::= { dlswDirCache 1 }
1597:
1598: dlswDirMacEntry OBJECT-TYPE
1599: SYNTAX DlswDirMacEntry
1600: MAX-ACCESS not-accessible
1601: STATUS current
1602: DESCRIPTION
1603: "Indexed by dlswDirMacIndex."
1604: INDEX { dlswDirMacIndex }
1605: ::= { dlswDirMacTable 1 }
1606:
1607: DlswDirMacEntry ::= SEQUENCE {
1608: dlswDirMacIndex INTEGER,
1609: dlswDirMacMac MacAddressNC,
1610: dlswDirMacMask MacAddressNC,
1611: dlswDirMacEntryType INTEGER,
1612: dlswDirMacLocationType INTEGER,
1613: dlswDirMacLocation RowPointer,
1614: dlswDirMacStatus INTEGER,
1615: dlswDirMacLFSize LFSize,
1616: dlswDirMacRowStatus RowStatus
1617: }
1618:
1619: dlswDirMacIndex OBJECT-TYPE
1620: SYNTAX INTEGER (0..2147483647)
1620: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1621: MAX-ACCESS not-accessible
1622: STATUS current
1623: DESCRIPTION
1624: "Uniquely identifies a conceptual row of this table."
1625: ::= { dlswDirMacEntry 1 }
1626:
1627: dlswDirMacMac OBJECT-TYPE
1628: SYNTAX MacAddressNC
1629: MAX-ACCESS read-create
1630: STATUS current
1631: DESCRIPTION
1632: "The MAC address, together with the dlswDirMacMask,
1633: specifies a set of MAC addresses that are defined or
1634: discovered through an interface or partner DLSw nodes."
1635: ::= { dlswDirMacEntry 2 }
1636:
1637: dlswDirMacMask OBJECT-TYPE
1638: SYNTAX MacAddressNC
1639: MAX-ACCESS read-create
1640: STATUS current
1641: DESCRIPTION
1642: "The MAC address mask, together with the dlswDirMacMac,
1643: specifies a set of MAC addresses that are defined or
1644: discovered through an interface or partner DLSw nodes."
1645: DEFVAL { 'FFFFFFFFFFFF'H }
1646: ::= { dlswDirMacEntry 3 }
1647:
1648: dlswDirMacEntryType OBJECT-TYPE
1649: SYNTAX INTEGER {
1650: other (1),
1651: userConfiguredPublic (2),
1652: userConfiguredPrivate (3),
1653: partnerCapExMsg (4),
1654: dynamic (5)
1655: }
1656: MAX-ACCESS read-create
1657: STATUS current
1658: DESCRIPTION
1659: "The cause of the creation of this conceptual row.
1660: It could be one of the three methods: (1) user
1661: configured, including via management protocol
1662: set operations, configuration file, command line
1663: or equivalent methods; (2) learned from the
1664: partner DLSw Capabilities Exchange messages;
1665: and (3) dynamic, e.g., learned from ICanReach
1666: messages, or LAN explorer frames. Since only
1667: individual MAC addresses can be dynamically learned,
1668: dynamic entries will all have a mask of all FFs.
1669:
1670: The public versus private distinction for user-
1671: configured resources applies only to local resources
1672: (UC remote resources are private), and indicates
1673: whether that resource should be advertised in
1674: capabilities exchange messages sent by this node."
1675: DEFVAL { userConfiguredPublic }
1676: ::= { dlswDirMacEntry 4 }
1677:
1678: dlswDirMacLocationType OBJECT-TYPE
1679: SYNTAX INTEGER {
1680: other (1),
1681: local (2),
1682: remote (3)
1683: }
1684: MAX-ACCESS read-create
1685: STATUS current
1686: DESCRIPTION
1687: "The location of the resource (or a collection of
1688: resources using a mask) of this conceptual row
1689: is either (1) local - the resource is reachable
1690: via an interface, or (2) remote - the resource
1691: is reachable via a partner DLSw node (or a set
1692: of partner DLSw nodes)."
1693: DEFVAL { local }
1694: ::= { dlswDirMacEntry 5 }
1695:
1696: dlswDirMacLocation OBJECT-TYPE
1697: SYNTAX RowPointer
1698: MAX-ACCESS read-create
1699: STATUS current
1700: DESCRIPTION
1701: "Points to either the ifEntry, dlswTConnConfigEntry,
1702: dlswTConnOperEntry, 0.0, or something that is implementation
1703: specific. It identifies the location of the MAC address
1704: (or the collection of MAC addresses.)"
1705: DEFVAL { null }
1706: ::= { dlswDirMacEntry 6 }
1707:
1708: dlswDirMacStatus OBJECT-TYPE
1709: SYNTAX INTEGER {
1710: unknown (1),
1711: reachable (2),
1712: notReachable (3)
1713: }
1714: MAX-ACCESS read-create
1715: STATUS current
1716: DESCRIPTION
1717: "This object specifies whether DLSw currently believes
1718: the MAC address to be accessible at the specified location.
1719: The value `notReachable' allows a configured resource
1720: definition to be taken out of service when a search to
1721: that resource fails (avoiding a repeat of the search)."
1722: DEFVAL { unknown }
1723: ::= { dlswDirMacEntry 7 }
1724:
1725: dlswDirMacLFSize OBJECT-TYPE
1726: SYNTAX LFSize
1727: MAX-ACCESS read-create
1728: STATUS current
1729: DESCRIPTION
1730: "The largest size of the MAC INFO field (LLC header and data)
1731: that a circuit to the MAC address can carry through this path."
1732: DEFVAL { lfs65535 }
1733: ::= { dlswDirMacEntry 8 }
1734:
1735: dlswDirMacRowStatus OBJECT-TYPE
1736: SYNTAX RowStatus
1737: MAX-ACCESS read-create
1738: STATUS current
1739: DESCRIPTION
1740: "This object is used by the manager to create
1741: or delete the row entry in the dlswDirMacTable
1742: following the RowStatus textual convention."
1743: ::= { dlswDirMacEntry 9 }
1744:
1745: -- ...................................................................
1746: -- Directory for NetBIOS Names
1747: -- All Possible combinations of values of these objects.
1748: --
1749: -- EntryType LocationType Location Status
1750: -- -------------- ------------ ------------------ --------------
1751: -- userConfigured local ifEntry or 0.0 reachable, or
1752: -- notReachable, or
1753: -- unknown
1754: -- userConfigured remote TConnConfigEntry reachable, or
1755: -- notReachable, or
1756: -- unknown
1757: -- partnerCapExMsg remote TConnOperEntry unknown
1758: -- dynamic local ifEntry or 0.0 reachable
1759: -- dynamic remote TConnOperEntry reachable
1760: --
1761: -- ...................................................................
1762: dlswDirNBTable OBJECT-TYPE
1763: SYNTAX SEQUENCE OF DlswDirNBEntry
1764: MAX-ACCESS not-accessible
1765: STATUS current
1766: DESCRIPTION
1767: "This table contains locations of NetBIOS names.
1768: They could be either verified or not verified,
1769: local or remote, and configured locally or learned
1770: from either Capabilities Exchange messages or
1771: directory searches."
1772: ::= { dlswDirCache 2 }
1773:
1774: dlswDirNBEntry OBJECT-TYPE
1775: SYNTAX DlswDirNBEntry
1776: MAX-ACCESS not-accessible
1777: STATUS current
1778: DESCRIPTION
1779: "Indexed by dlswDirNBIndex."
1780: INDEX { dlswDirNBIndex }
1781: ::= { dlswDirNBTable 1 }
1782:
1783: DlswDirNBEntry ::= SEQUENCE {
1784: dlswDirNBIndex INTEGER,
1785: dlswDirNBName NBName,
1786: dlswDirNBNameType INTEGER,
1787: dlswDirNBEntryType INTEGER,
1788: dlswDirNBLocationType INTEGER,
1789: dlswDirNBLocation RowPointer,
1790: dlswDirNBStatus INTEGER,
1791: dlswDirNBLFSize LFSize,
1792: dlswDirNBRowStatus RowStatus
1793: }
1794:
1795: dlswDirNBIndex OBJECT-TYPE
1796: SYNTAX INTEGER (0..2147483647)
1796: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1797: MAX-ACCESS not-accessible
1798: STATUS current
1799: DESCRIPTION
1800: "Uniquely identifies a conceptual row of this table."
1801: ::= { dlswDirNBEntry 1 }
1802:
1803: dlswDirNBName OBJECT-TYPE
1804: SYNTAX NBName
1805: MAX-ACCESS read-create
1806: STATUS current
1807: DESCRIPTION
1808: "The NetBIOS name (including `any char' and `wildcard'
1809: characters) specifies a set of NetBIOS names that are
1810: defined or discovered through an interface or partner
1811: DLSw nodes."
1812: ::= { dlswDirNBEntry 2 }
1813:
1814: dlswDirNBNameType OBJECT-TYPE
1815: SYNTAX INTEGER {
1816: unknown (1),
1817: individual (2),
1818: group (3)
1819: }
1820: MAX-ACCESS read-create
1821: STATUS current
1822: DESCRIPTION
1823: "Whether dlswDirNBName represents an (or a set of) individual
1824: or group NetBIOS name(s)."
1825: DEFVAL { unknown }
1826: ::= { dlswDirNBEntry 3 }
1827:
1828: dlswDirNBEntryType OBJECT-TYPE
1829: SYNTAX INTEGER {
1830: other (1),
1831: userConfiguredPublic (2),
1832: userConfiguredPrivate (3),
1833: partnerCapExMsg (4),
1834: dynamic (5)
1835: }
1836: MAX-ACCESS read-create
1837: STATUS current
1838: DESCRIPTION
1839: "The cause of the creation of this conceptual row.
1840: It could be one of the three methods: (1) user
1841: configured, including via management protocol
1842: set operations, configuration file, command line,
1843: or equivalent methods; (2) learned from the
1844: partner DLSw Capabilities Exchange messages;
1845: and (3) dynamic, e.g., learned from ICanReach
1846: messages, or test frames. Since only actual
1847: NetBIOS names can be dynamically learned, dynamic
1848: entries will not contain any char or wildcard
1849: characters.
1850:
1851: The public versus private distinction for user-
1852: configured resources applies only to local resources
1853: (UC remote resources are private), and indicates
1854: whether that resource should be advertised in
1855: capabilities exchange messages sent by this node."
1856: DEFVAL { userConfiguredPublic }
1857: ::= { dlswDirNBEntry 4 }
1858:
1859: dlswDirNBLocationType OBJECT-TYPE
1860: SYNTAX INTEGER {
1861: other (1),
1862: local (2),
1863: remote (3)
1864: }
1865: MAX-ACCESS read-create
1866: STATUS current
1867: DESCRIPTION
1868: "The location of the resource (or a collection of resources
1869: using any char/wildcard characters) of this conceptual row
1870: is either (1) local - the resource is reachable via an
1871: interface, or (2) remote - the resource is reachable via a
1872: a partner DLSw node (or a set of partner DLSw nodes)."
1873: DEFVAL { local }
1874: ::= { dlswDirNBEntry 5 }
1875:
1876: dlswDirNBLocation OBJECT-TYPE
1877: SYNTAX RowPointer
1878: MAX-ACCESS read-create
1879: STATUS current
1880: DESCRIPTION
1881: "Points to either the ifEntry, dlswTConnConfigEntry,
1882: dlswTConnOperEntry, 0.0, or something that is implementation
1883: specific. It identifies the location of the NetBIOS name
1884: or the set of NetBIOS names."
1885: DEFVAL { null }
1886: ::= { dlswDirNBEntry 6 }
1887:
1888: dlswDirNBStatus OBJECT-TYPE
1889: SYNTAX INTEGER {
1890: unknown (1),
1891: reachable (2),
1892: notReachable (3)
1893: }
1894: MAX-ACCESS read-create
1895: STATUS current
1896: DESCRIPTION
1897: "This object specifies whether DLSw currently believes
1898: the NetBIOS name to be accessible at the specified location.
1899: The value `notReachable' allows a configured resource
1900: definition to be taken out of service when a search to
1901: that resource fails (avoiding a repeat of the search)."
1902: DEFVAL { unknown }
1903: ::= { dlswDirNBEntry 7 }
1904:
1905: dlswDirNBLFSize OBJECT-TYPE
1906: SYNTAX LFSize
1907: MAX-ACCESS read-create
1908: STATUS current
1909: DESCRIPTION
1910: "The largest size of the MAC INFO field (LLC header and data)
1911: that a circuit to the NB name can carry through this path."
1912: DEFVAL { lfs65535 }
1913: ::= { dlswDirNBEntry 8 }
1914:
1915: dlswDirNBRowStatus OBJECT-TYPE
1916: SYNTAX RowStatus
1917: MAX-ACCESS read-create
1918: STATUS current
1919: DESCRIPTION
1920: "This object is used by manager to create
1921: or delete the row entry in the dlswDirNBTable
1922: following the RowStatus textual convention."
1923: ::= { dlswDirNBEntry 9 }
1924:
1925:
1926: -- -------------------------------------------------------------------
1926: warning -
warning: note, -- terminates a comment
1926: severe -
lexically unexpected character, skipping to end of line
1927: -- Resource Locations
1928: -- -------------------------------------------------------------------
1928: warning -
warning: note, -- terminates a comment
1928: severe -
lexically unexpected character, skipping to end of line
1929: dlswDirLocate OBJECT IDENTIFIER ::= { dlswDirectory 3 }
1930:
1931: -- ...................................................................
1932: -- Locate Entries in the dlswDirMacTable for a given MAC address
1933: -- ...................................................................
1934: dlswDirLocateMacTable OBJECT-TYPE
1935: SYNTAX SEQUENCE OF DlswDirLocateMacEntry
1936: MAX-ACCESS not-accessible
1937: STATUS current
1938: DESCRIPTION
1939: "This table is used to retrieve all entries in the
1940: dlswDirMacTable that match a given MAC address,
1941: in the order of the best matched first, the
1942: second best matched second, and so on, till
1943: no more entries match the given MAC address."
1944: ::= { dlswDirLocate 1 }
1945:
1946: dlswDirLocateMacEntry OBJECT-TYPE
1947: SYNTAX DlswDirLocateMacEntry
1948: MAX-ACCESS not-accessible
1949: STATUS current
1950: DESCRIPTION
1951: "Indexed by dlswDirLocateMacMac and dlswDirLocateMacMatch.
1952: The first object is the MAC address of interest, and
1953: the second object is the order in the list of all
1954: entries that match the MAC address."
1955: INDEX { dlswDirLocateMacMac, dlswDirLocateMacMatch }
1956: ::= { dlswDirLocateMacTable 1 }
1957:
1958: DlswDirLocateMacEntry ::= SEQUENCE {
1959: dlswDirLocateMacMac MacAddressNC,
1960: dlswDirLocateMacMatch INTEGER,
1961: dlswDirLocateMacLocation RowPointer
1962: }
1963:
1964: dlswDirLocateMacMac OBJECT-TYPE
1965: SYNTAX MacAddressNC
1966: MAX-ACCESS not-accessible
1967: STATUS current
1968: DESCRIPTION
1969: "The MAC address to be located."
1970: ::= { dlswDirLocateMacEntry 1 }
1971:
1972: dlswDirLocateMacMatch OBJECT-TYPE
1973: SYNTAX INTEGER (1..255)
1973: warning -
warning: use Integer32 instead of INTEGER in SMIv2
1974: MAX-ACCESS not-accessible
1975: STATUS current
1976: DESCRIPTION
1977: "The order of the entries of dlswDirMacTable
1978: that match dlswDirLocateMacMac. A value of
1979: one represents the entry that best matches the
1980: MAC address. A value of two represents the second
1981: best matched entry, and so on."
1982: ::= { dlswDirLocateMacEntry 2 }
1983:
1984: dlswDirLocateMacLocation OBJECT-TYPE
1985: SYNTAX RowPointer
1986: MAX-ACCESS read-only
1987: STATUS current
1988: DESCRIPTION
1989: "Points to the dlswDirMacEntry."
1990: ::= { dlswDirLocateMacEntry 3 }
1991:
1992: -- ...................................................................
1993: -- Locate Entries in the dlswDirNBTable for a given NetBIOS name
1994: -- ...................................................................
1995: dlswDirLocateNBTable OBJECT-TYPE
1996: SYNTAX SEQUENCE OF DlswDirLocateNBEntry
1997: MAX-ACCESS not-accessible
1998: STATUS current
1999: DESCRIPTION
2000: "This table is used to retrieve all entries in the
2001: dlswDirNBTable that match a given NetBIOS name,
2002: in the order of the best matched first, the
2003: second best matched second, and so on, till
2004: no more entries match the given NetBIOS name."
2005: ::= { dlswDirLocate 2 }
2006:
2007: dlswDirLocateNBEntry OBJECT-TYPE
2008: SYNTAX DlswDirLocateNBEntry
2009: MAX-ACCESS not-accessible
2010: STATUS current
2011: DESCRIPTION
2012: "Indexed by dlswDirLocateNBName and dlswDirLocateNBMatch.
2013: The first object is the NetBIOS name of interest, and
2014: the second object is the order in the list of all
2015: entries that match the NetBIOS name."
2016: INDEX { dlswDirLocateNBName, dlswDirLocateNBMatch }
2017: ::= { dlswDirLocateNBTable 1 }
2018:
2019: DlswDirLocateNBEntry ::= SEQUENCE {
2020: dlswDirLocateNBName NBName,
2021: dlswDirLocateNBMatch INTEGER,
2022: dlswDirLocateNBLocation RowPointer
2023: }
2024:
2025: dlswDirLocateNBName OBJECT-TYPE
2026: SYNTAX NBName
2027: MAX-ACCESS not-accessible
2028: STATUS current
2029: DESCRIPTION
2030: "The NetBIOS name to be located (no any char or wildcards)."
2031: ::= { dlswDirLocateNBEntry 1 }
2032:
2033: dlswDirLocateNBMatch OBJECT-TYPE
2034: SYNTAX INTEGER (1..255)
2034: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2035: MAX-ACCESS not-accessible
2036: STATUS current
2037: DESCRIPTION
2038: "The order of the entries of dlswDirNBTable
2039: that match dlswDirLocateNBName. A value of
2040: one represents the entry that best matches the
2041: NetBIOS name. A value of two represents the second
2042: best matched entry, and so on."
2043: ::= { dlswDirLocateNBEntry 2 }
2044:
2045: dlswDirLocateNBLocation OBJECT-TYPE
2046: SYNTAX RowPointer
2047: MAX-ACCESS read-only
2048: STATUS current
2049: DESCRIPTION
2050: "Points to the dlswDirNBEntry."
2051: ::= { dlswDirLocateNBEntry 3 }
2052:
2053:
2054: -- *******************************************************************
2055: -- CIRCUIT
2056: -- A circuit is the end-to-end association of two DLSw entities
2057: -- through one or two DLSw nodes. It is the concatenation of
2058: -- two "data links", optionally with an intervening transport
2059: -- connection. The origin of the circuit is the end station that
2060: -- initiates the circuit. The target of the circuit is the end
2061: -- station that receives the initiation.
2062: -- *******************************************************************
2063:
2064: -- -------------------------------------------------------------------
2064: warning -
warning: note, -- terminates a comment
2064: severe -
lexically unexpected character, skipping to end of line
2065: -- Statistics Related to Circuits
2066: -- -------------------------------------------------------------------
2066: warning -
warning: note, -- terminates a comment
2066: severe -
lexically unexpected character, skipping to end of line
2067: dlswCircuitStat OBJECT IDENTIFIER ::= { dlswCircuit 1 }
2068:
2069: dlswCircuitStatActives OBJECT-TYPE
2070: SYNTAX Gauge32
2071: MAX-ACCESS read-only
2072: STATUS current
2073: DESCRIPTION
2074: "The current number of circuits in dlswCircuitTable that are
2075: not in the disconnected state."
2076: ::= { dlswCircuitStat 1 }
2077:
2078: dlswCircuitStatCreates OBJECT-TYPE
2079: SYNTAX Counter32
2080: MAX-ACCESS read-only
2081: STATUS current
2082: DESCRIPTION
2083: "The total number of entries ever added to dlswCircuitTable,
2084: or reactivated upon exiting `disconnected' state."
2085: ::= { dlswCircuitStat 2 }
2086:
2087:
2088: -- -------------------------------------------------------------------
2088: warning -
warning: note, -- terminates a comment
2088: severe -
lexically unexpected character, skipping to end of line
2089: -- Circuit Table
2090: --
2091: -- This table is the DLSw entity's view of circuits. There will be
2092: -- a conceptual row in the table associated with each data link.
2093: --
2094: -- The chart below lists the various possible combinations of
2095: -- origin and target MAC locations and the number of entries in
2096: -- this Circuit Table:
2097: --
2098: -- number of | Origin End Station Location
2099: -- entries in the |--------------------------------------
2100: -- Circuit Table | internal local remote
2101: -- -----------------------|--------------------------------------
2101: warning -
warning: note, -- terminates a comment
2101: severe -
syntax error, unexpected $undefined
2102: -- Target | internal | NA 2 1
2103: -- End | local | 2 2 1
2104: -- Station | remote | 1 1 NA
2105: -- Location | |
2106: --
2107: -- NA: Not applicable
2108: --
2109: -- Note:
2110: -- (a) IfIndex and RouteInfo are applied only if location is local.
2111: -- (b) TDomain and TAddr are applied only if location is remote.
2112: --
2113: -- Most of statistics related to circuits can be collected
2114: -- from LLC-2 Link Station Table.
2115: -- -------------------------------------------------------------------
2115: warning -
warning: note, -- terminates a comment
2115: severe -
lexically unexpected character, skipping to end of line
2116: dlswCircuitTable OBJECT-TYPE
2117: SYNTAX SEQUENCE OF DlswCircuitEntry
2118: MAX-ACCESS not-accessible
2119: STATUS current
2120: DESCRIPTION
2121: "This table is the circuit representation in the DLSw
2122: entity. Virtual data links are used to represent any internal
2123: end stations. There is a conceptual row associated with
2124: each data link. Thus, for circuits without an intervening
2125: transport connection, there are two conceptual rows
2126: for each circuit.
2127:
2128: The table consists of the circuits being established,
2129: established, and as an implementation option, circuits that
2130: have been disconnected. For circuits carried over
2131: transport connections, an entry is created after
2132: the CUR_cs was sent or received. For circuits between
2133: two locally attached devices, or internal virtual MAC
2134: addresses, an entry is created when the equivalent of
2135: CUR_cs sent/received status is reached.
2136:
2137: End station 1 (S1) and End station 2 (S2) are used to
2138: represent the two end stations of the circuit.
2139: S1 is always an end station which is locally attached.
2140: S2 may be locally attached or remote. If it is locally
2141: attached, the circuit will be represented by two rows indexed
2142: by (A, B) and (B, A) where A & B are the relevant MACs/SAPs.
2143:
2144: The table may be used to store the causes of disconnection of
2145: circuits. It is recommended that the oldest disconnected
2146: circuit entry be removed from this table when the memory
2147: space of disconnected circuits is needed."
2148: ::= { dlswCircuit 2 }
2148: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2149:
2150: dlswCircuitEntry OBJECT-TYPE
2150: error -
row's parent node must be a table node
2151: SYNTAX DlswCircuitEntry
2152: MAX-ACCESS not-accessible
2153: STATUS current
2154: DESCRIPTION
2155: ""
2155: warning -
warning: zero-length description string
2156: INDEX { dlswCircuitS1Mac,
2157: dlswCircuitS1Sap,
2158: dlswCircuitS2Mac,
2159: dlswCircuitS2Sap }
2160: ::= { dlswCircuitTable 1 }
2160: severe -
unknown object identifier label `dlswCircuitTable'
2161:
2162: DlswCircuitEntry ::= SEQUENCE {
2163: dlswCircuitS1Mac MacAddressNC,
2164: dlswCircuitS1Sap OCTET STRING,
2165: dlswCircuitS1IfIndex INTEGER,
2166: dlswCircuitS1DlcType DlcType,
2167: dlswCircuitS1RouteInfo OCTET STRING,
2168: dlswCircuitS1CircuitId OCTET STRING,
2169: dlswCircuitS1Dlc RowPointer,
2170:
2171: dlswCircuitS2Mac MacAddressNC,
2172: dlswCircuitS2Sap OCTET STRING,
2173: dlswCircuitS2Location EndStationLocation,
2174: dlswCircuitS2TDomain OBJECT IDENTIFIER,
2175: dlswCircuitS2TAddress TAddress,
2176: dlswCircuitS2CircuitId OCTET STRING,
2177:
2178: dlswCircuitOrigin INTEGER,
2179:
2180: dlswCircuitEntryTime TimeTicks,
2181: dlswCircuitStateTime TimeTicks,
2182: dlswCircuitState INTEGER,
2183:
2184: dlswCircuitPriority INTEGER,
2185:
2186: dlswCircuitFCSendGrantedUnits INTEGER,
2187: dlswCircuitFCSendCurrentWndw INTEGER,
2188: dlswCircuitFCRecvGrantedUnits INTEGER,
2189: dlswCircuitFCRecvCurrentWndw INTEGER,
2190: dlswCircuitFCLargestRecvGranted Gauge32,
2191: dlswCircuitFCLargestSendGranted Gauge32,
2192: dlswCircuitFCHalveWndwSents Counter32,
2193: dlswCircuitFCResetOpSents Counter32,
2194: dlswCircuitFCHalveWndwRcvds Counter32,
2195: dlswCircuitFCResetOpRcvds Counter32,
2196: dlswCircuitDiscReasonLocal INTEGER,
2197: dlswCircuitDiscReasonRemote INTEGER,
2198: dlswCircuitDiscReasonRemoteData OCTET STRING
2199: }
2200:
2201: -- ...................................................................
2202: -- Information related to the End Station 1 (S1).
2203: -- ...................................................................
2204: dlswCircuitS1Mac OBJECT-TYPE
2205: SYNTAX MacAddressNC
2206: MAX-ACCESS not-accessible
2207: STATUS current
2208: DESCRIPTION
2209: "The MAC Address of End Station 1 (S1) used for this circuit."
2210: ::= { dlswCircuitEntry 1 }
2211:
2212: dlswCircuitS1Sap OBJECT-TYPE
2213: SYNTAX OCTET STRING (SIZE(1))
2214: MAX-ACCESS not-accessible
2215: STATUS current
2216: DESCRIPTION
2217: "The SAP at End Station 1 (S1) used for this circuit."
2218: ::= { dlswCircuitEntry 2 }
2219:
2220: dlswCircuitS1IfIndex OBJECT-TYPE
2221: SYNTAX INTEGER (0..2147483647)
2221: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2222: MAX-ACCESS read-only
2223: STATUS current
2224: DESCRIPTION
2225: "The ifEntry index of the local interface through which S1
2226: can be reached."
2227: ::= { dlswCircuitEntry 3 }
2228:
2229: dlswCircuitS1DlcType OBJECT-TYPE
2230: SYNTAX DlcType
2231: MAX-ACCESS read-only
2232: STATUS current
2233: DESCRIPTION
2234: "The DLC protocol in use between the DLSw node and S1."
2235: ::= { dlswCircuitEntry 4 }
2236:
2237: dlswCircuitS1RouteInfo OBJECT-TYPE
2238: SYNTAX OCTET STRING (SIZE (0..30))
2239: MAX-ACCESS read-only
2240: STATUS current
2241: DESCRIPTION
2242: "If source-route bridging is in use between the DLSw
2243: node and S1, this is the routing information field
2244: describing the path between the two devices.
2245: Otherwise the value will be an OCTET STRING of
2246: zero length."
2247: ::= { dlswCircuitEntry 5 }
2248:
2249: dlswCircuitS1CircuitId OBJECT-TYPE
2250: SYNTAX OCTET STRING (SIZE (0 | 8))
2251: MAX-ACCESS read-only
2252: STATUS current
2253: DESCRIPTION
2254: "The Circuit ID assigned by this DLSw node to this circuit.
2255: The first four octets are the DLC port Id, and
2256: the second four octets are the Data Link Correlator.
2257: If the DLSw SSP was not used to establish this circuit,
2258: the value will be a string of zero length."
2259: ::= { dlswCircuitEntry 6 }
2260:
2261: dlswCircuitS1Dlc OBJECT-TYPE
2262: SYNTAX RowPointer
2263: MAX-ACCESS read-only
2264: STATUS current
2265: DESCRIPTION
2266: "Points to a conceptual row of the underlying DLC MIB,
2267: which could either be the standard MIBs (e.g., the SDLC),
2268: or an enterprise-specific DLC MIB."
2269: ::= { dlswCircuitEntry 7 }
2270:
2271: -- ...................................................................
2272: -- Information related to the End Station 2 (S2).
2273: -- ...................................................................
2274: dlswCircuitS2Mac OBJECT-TYPE
2275: SYNTAX MacAddressNC
2276: MAX-ACCESS not-accessible
2277: STATUS current
2278: DESCRIPTION
2279: "The MAC Address of End Station 2 (S2) used for this circuit."
2280: ::= { dlswCircuitEntry 8 }
2281:
2282: dlswCircuitS2Sap OBJECT-TYPE
2283: SYNTAX OCTET STRING (SIZE(1))
2284: MAX-ACCESS not-accessible
2285: STATUS current
2286: DESCRIPTION
2287: "The SAP at End Station 2 (S2) used for this circuit."
2288: ::= { dlswCircuitEntry 9 }
2289:
2290: dlswCircuitS2Location OBJECT-TYPE
2291: SYNTAX EndStationLocation
2292: MAX-ACCESS read-only
2293: STATUS current
2294: DESCRIPTION
2295: "The location of End Station 2 (S2).
2296: If the location of End Station 2 is local, the
2297: interface information will be available in the
2298: conceptual row whose S1 and S2 are the S2 and
2299: the S1 of this conceptual row, respectively."
2300: ::= { dlswCircuitEntry 10 }
2301:
2302: dlswCircuitS2TDomain OBJECT-TYPE
2303: SYNTAX OBJECT IDENTIFIER
2304: MAX-ACCESS read-only
2305: STATUS current
2306: DESCRIPTION
2307: "If the location of End Station 2 is remote,
2308: this value is the transport domain of the
2309: transport protocol the circuit is running
2310: over. Otherwise, the value is 0.0."
2311: ::= { dlswCircuitEntry 11 }
2312:
2313: dlswCircuitS2TAddress OBJECT-TYPE
2314: SYNTAX TAddress
2315: MAX-ACCESS read-only
2316: STATUS current
2317: DESCRIPTION
2318: "If the location of End Station 2 is remote,
2319: this object contains the address of the partner
2320: DLSw, else it will be an OCTET STRING of zero length."
2321: ::= { dlswCircuitEntry 12 }
2322:
2323: dlswCircuitS2CircuitId OBJECT-TYPE
2324: SYNTAX OCTET STRING (SIZE (0 | 8))
2325: MAX-ACCESS read-only
2326: STATUS current
2327: DESCRIPTION
2328: "The Circuit ID assigned to this circuit by the partner
2329: DLSw node. The first four octets are the DLC port Id, and
2330: the second four octets are the Data Link Correlator.
2331: If the DLSw SSP was not used to establish this circuit,
2332: the value will be a string of zero length."
2333: ::= { dlswCircuitEntry 13 }
2334:
2335: -- ...................................................................
2336: dlswCircuitOrigin OBJECT-TYPE
2337: SYNTAX INTEGER {
2338: s1 (1),
2339: s2 (2)
2340: }
2341: MAX-ACCESS read-only
2342: STATUS current
2343: DESCRIPTION
2344: "This object specifies which of the two end stations
2345: initiated the establishment of this circuit."
2346: ::= { dlswCircuitEntry 14 }
2347:
2348: -- ...................................................................
2349: -- Operational information related to this circuit.
2350: -- ...................................................................
2351: dlswCircuitEntryTime OBJECT-TYPE
2352: SYNTAX TimeTicks
2353: UNITS "hundredths of a second"
2354: MAX-ACCESS read-only
2355: STATUS current
2356: DESCRIPTION
2357: "The amount of time (in hundredths of a second) since this
2358: circuit table conceptual row was created."
2359: ::= { dlswCircuitEntry 15 }
2360:
2361: dlswCircuitStateTime OBJECT-TYPE
2362: SYNTAX TimeTicks
2363: UNITS "hundredths of a second"
2364: MAX-ACCESS read-only
2365: STATUS current
2366: DESCRIPTION
2367: "The amount of time (in hundredths of a second) since this
2368: circuit entered the current state."
2369: ::= { dlswCircuitEntry 16 }
2370:
2371: dlswCircuitState OBJECT-TYPE
2372: SYNTAX INTEGER {
2373: disconnected (1),
2374: circuitStart (2),
2375: resolvePending (3),
2376: circuitPending (4),
2377: circuitEstablished (5),
2378: connectPending (6),
2379: contactPending (7),
2380: connected (8),
2381: disconnectPending (9),
2382: haltPending (10),
2383: haltPendingNoack (11),
2384: circuitRestart (12),
2385: restartPending (13)
2386: }
2387: MAX-ACCESS read-write
2388: STATUS current
2389: DESCRIPTION
2390: "The current state of this circuit. The agent, implementation
2391: specific, may choose to keep entries for some period of time
2392: after circuit disconnect, so the manager can gather the time
2393: and cause of disconnection.
2394:
2395: While all of the specified values may be returned from a GET
2396: operation, the only SETable value is `disconnectPending'.
2397: When this value is set, DLSw should perform the appropriate
2398: action given its previous state (e.g., send HALT_DL if the
2399: state was `connected') to bring the circuit down to the
2400: `disconnected' state. Both the partner DLSw and local end
2401: station(s) should be notified as appropriate.
2402:
2403: This MIB provides no facility to re-establish a disconnected
2404: circuit, because in DLSw this should be an end station-driven
2405: function."
2406: ::= { dlswCircuitEntry 17 }
2407:
2408: dlswCircuitPriority OBJECT-TYPE
2409: SYNTAX INTEGER {
2410: unsupported (1),
2411: low (2),
2412: medium (3),
2413: high (4),
2414: highest (5)
2415: }
2416: MAX-ACCESS read-only
2417: STATUS current
2418: DESCRIPTION
2419: "The transmission priority of this circuit as understood by
2420: this DLSw node. This value is determined by the two DLSw
2421: nodes at circuit startup time. If this DLSw node does not
2422: support DLSw circuit priority, the value `unsupported' should
2423: be returned."
2424: ::= { dlswCircuitEntry 18 }
2425:
2426: -- ...................................................................
2427: -- Pacing Objects:
2428: -- These objects are applicable if DLSw is using the SSP circuit
2429: -- pacing protocol to control the flow between the two data links
2430: -- in this circuit.
2431: -- ...................................................................
2432: dlswCircuitFCSendGrantedUnits OBJECT-TYPE
2433: SYNTAX INTEGER (0..65535)
2433: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2434: MAX-ACCESS read-only
2435: STATUS current
2436: DESCRIPTION
2437: "The number of paced SSP messages that this DLSw is currently
2438: authorized to send on this circuit before it must stop and
2439: wait for an additional flow control indication from the
2440: partner DLSw.
2441:
2442: The value zero should be returned if this circuit is not
2443: running the DLSw pacing protocol."
2444: ::= { dlswCircuitEntry 19 }
2445:
2446: dlswCircuitFCSendCurrentWndw OBJECT-TYPE
2447: SYNTAX INTEGER (0..65535)
2447: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2448: MAX-ACCESS read-only
2449: STATUS current
2450: DESCRIPTION
2451: "The current window size that this DLSw is using in its role
2452: as a data sender. This is the value by which this DLSw would
2453: increase the number of messages it is authorized to send, if
2454: it were to receive a flow control indication with the bits
2455: specifying `repeat window'.
2456: The value zero should be returned if this circuit is not
2457: running the DLSw pacing protocol."
2458: ::= { dlswCircuitEntry 20 }
2459:
2460: dlswCircuitFCRecvGrantedUnits OBJECT-TYPE
2461: SYNTAX INTEGER (0..65535)
2461: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2462: MAX-ACCESS read-only
2463: STATUS current
2464: DESCRIPTION
2465: "The current number of paced SSP messages that this DLSw has
2466: authorized the partner DLSw to send on this circuit before
2467: the partner DLSw must stop and wait for an additional flow
2468: control indication from this DLSw.
2469:
2470: The value zero should be returned if this circuit is not
2471: running the DLSw pacing protocol."
2472: ::= { dlswCircuitEntry 21 }
2473:
2474: dlswCircuitFCRecvCurrentWndw OBJECT-TYPE
2475: SYNTAX INTEGER (0..65535)
2475: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2476: MAX-ACCESS read-only
2477: STATUS current
2478: DESCRIPTION
2479: "The current window size that this DLSw is using in its role
2480: as a data receiver. This is the number of additional paced
2481: SSP messages that this DLSw would be authorizing its DLSw
2482: partner to send, if this DLSw were to send a flow control
2483: indication with the bits specifying `repeat window'.
2484:
2485: The value zero should be returned if this circuit is not
2486: running the DLSw pacing protocol."
2487: ::= { dlswCircuitEntry 22 }
2488:
2489: dlswCircuitFCLargestRecvGranted OBJECT-TYPE
2490: SYNTAX Gauge32
2491: MAX-ACCESS read-only
2492: STATUS current
2493: DESCRIPTION
2494: "The largest receive window size granted by this DLSw during
2495: the current activation of this circuit. This is not the
2496: largest number of messages granted at any time, but the
2497: largest window size as represented by FCIND operator bits.
2498:
2499: The value zero should be returned if this circuit is not
2500: running the DLSw pacing protocol."
2501: ::= { dlswCircuitEntry 23 }
2502:
2503: dlswCircuitFCLargestSendGranted OBJECT-TYPE
2504: SYNTAX Gauge32
2505: MAX-ACCESS read-only
2506: STATUS current
2507: DESCRIPTION
2508: "The largest send (with respect to this DLSw) window size
2509: granted by the partner DLSw during the current activation of
2510: this circuit.
2511:
2512: The value zero should be returned if this circuit is not
2513: running the DLSw pacing protocol."
2514: ::= { dlswCircuitEntry 24 }
2515:
2516: dlswCircuitFCHalveWndwSents OBJECT-TYPE
2517: SYNTAX Counter32
2518: MAX-ACCESS read-only
2519: STATUS current
2520: DESCRIPTION
2521: "The number of Halve Window operations this DLSw has sent on
2522: this circuit, in its role as a data receiver.
2523:
2524: The value zero should be returned if this circuit is not
2525: running the DLSw pacing protocol."
2526: ::= { dlswCircuitEntry 25 }
2527:
2528: dlswCircuitFCResetOpSents OBJECT-TYPE
2529: SYNTAX Counter32
2530: MAX-ACCESS read-only
2531: STATUS current
2532: DESCRIPTION
2533: "The number of Reset Window operations this DLSw has sent on
2534: this circuit, in its role as a data receiver.
2535:
2536: The value zero should be returned if this circuit is not
2537: running the DLSw pacing protocol."
2538: ::= { dlswCircuitEntry 26 }
2539:
2540: dlswCircuitFCHalveWndwRcvds OBJECT-TYPE
2541: SYNTAX Counter32
2542: MAX-ACCESS read-only
2543: STATUS current
2544: DESCRIPTION
2545: "The number of Halve Window operations this DLSw has received on
2546: this circuit, in its role as a data sender.
2547:
2548: The value zero should be returned if this circuit is not
2549: running the DLSw pacing protocol."
2550: ::= { dlswCircuitEntry 27 }
2551:
2552: dlswCircuitFCResetOpRcvds OBJECT-TYPE
2553: SYNTAX Counter32
2554: MAX-ACCESS read-only
2555: STATUS current
2556: DESCRIPTION
2557: "The number of Reset Window operations this DLSw has received on
2558: this circuit, in its role as a data sender.
2559: The value zero should be returned if this circuit is not
2560: running the DLSw pacing protocol."
2561: ::= { dlswCircuitEntry 28 }
2562:
2563:
2564: -- ...................................................................
2565: -- Information about the circuit disconnection
2566: -- ...................................................................
2567: dlswCircuitDiscReasonLocal OBJECT-TYPE
2568: SYNTAX INTEGER {
2569: endStationDiscRcvd (1),
2570: endStationDlcError (2),
2571: protocolError (3),
2572: operatorCommand (4),
2573: haltDlRcvd (5),
2574: haltDlNoAckRcvd (6),
2575: transportConnClosed (7)
2576: }
2577: MAX-ACCESS read-only
2578: STATUS current
2579: DESCRIPTION
2580: "The reason why this circuit was last disconnected, as seen
2581: by this DLSw node.
2582:
2583: This object is present only if the agent keeps circuit
2584: table entries around for some period after circuit disconnect."
2585: ::= { dlswCircuitEntry 29 }
2586:
2587: dlswCircuitDiscReasonRemote OBJECT-TYPE
2588: SYNTAX INTEGER {
2589: unknown (1),
2590: endStationDiscRcvd (2),
2591: endStationDlcError (3),
2592: protocolError (4),
2593: operatorCommand (5)
2594: }
2595: MAX-ACCESS read-only
2596: STATUS current
2597: DESCRIPTION
2598: "The generic reason code why this circuit was last
2599: disconnected, as reported by the DLSw partner in a HALT_DL
2600: or HALT_DL_NOACK. If the partner does not send a reason
2601: code in these messages, or the DLSw implementation does
2602: not report receiving one, the value `unknown' is returned.
2603:
2604: This object is present only if the agent keeps circuit table
2605: entries around for some period after circuit disconnect."
2606: ::= { dlswCircuitEntry 30 }
2607:
2608: dlswCircuitDiscReasonRemoteData OBJECT-TYPE
2609: SYNTAX OCTET STRING (SIZE (0 | 4))
2610: MAX-ACCESS read-only
2611: STATUS current
2612: DESCRIPTION
2613: "Implementation-specific data reported by the DLSw partner in
2614: a HALT_DL or HALT_DL_NOACK, to help specify how and why this
2615: circuit was last disconnected. If the partner does not send
2616: this data in these messages, or the DLSw implementation does
2617: not report receiving it, a string of zero length is returned.
2618:
2619: This object is present only if the agent keeps circuit table
2620: entries around for some period after circuit disconnect."
2621: ::= { dlswCircuitEntry 31 }
2622:
2623:
2624: -- ...................................................................
2625: -- Statistics related to this circuit.
2626: -- All statistics are in LLC-2 Link Station Statistical Table.
2627: -- All SDLC statistics are in SDLC MIB
2628: -- ...................................................................
2629:
2630:
2631: -- *******************************************************************
2632: -- DLSW SDLC EXTENSION
2633: -- *******************************************************************
2634: dlswSdlcLsEntries OBJECT-TYPE
2635: SYNTAX Gauge32
2636: MAX-ACCESS read-only
2637: STATUS current
2638: DESCRIPTION
2639: "The number of entries in dlswSdlcLsTable."
2640: ::= { dlswSdlc 1 }
2641:
2642: -- ...................................................................
2643: dlswSdlcLsTable OBJECT-TYPE
2644: SYNTAX SEQUENCE OF DlswSdlcLsEntry
2645: MAX-ACCESS not-accessible
2646: STATUS current
2647: DESCRIPTION
2648: "The table defines the virtual MAC addresses for those
2649: SDLC link stations that participate in data link switching."
2650: ::= { dlswSdlc 2 }
2651:
2652: dlswSdlcLsEntry OBJECT-TYPE
2653: SYNTAX DlswSdlcLsEntry
2654: MAX-ACCESS not-accessible
2655: STATUS current
2656: DESCRIPTION
2657: "The index of this table is the ifIndex value for the
2658: SDLC port which owns this link station and the poll
2659: address of the particular SDLC link station."
2660: INDEX { ifIndex, sdlcLSAddress }
2661: ::= { dlswSdlcLsTable 1 }
2662:
2663: DlswSdlcLsEntry ::= SEQUENCE {
2664: dlswSdlcLsLocalMac MacAddressNC,
2665: dlswSdlcLsLocalSap OCTET STRING,
2666: dlswSdlcLsLocalIdBlock DisplayString,
2667: dlswSdlcLsLocalIdNum DisplayString,
2668: dlswSdlcLsRemoteMac MacAddressNC,
2669: dlswSdlcLsRemoteSap OCTET STRING,
2670: dlswSdlcLsRowStatus RowStatus
2671: }
2672:
2673: dlswSdlcLsLocalMac OBJECT-TYPE
2674: SYNTAX MacAddressNC
2675: MAX-ACCESS read-create
2676: STATUS current
2677: DESCRIPTION
2678: "The virtual MAC address used to represent the SDLC-attached
2679: link station to the rest of the DLSw network."
2680: ::= { dlswSdlcLsEntry 1 }
2681:
2682: dlswSdlcLsLocalSap OBJECT-TYPE
2683: SYNTAX OCTET STRING (SIZE(1))
2684: MAX-ACCESS read-create
2685: STATUS current
2686: DESCRIPTION
2687: "The SAP used to represent this link station."
2688: ::= { dlswSdlcLsEntry 2 }
2689:
2690: dlswSdlcLsLocalIdBlock OBJECT-TYPE
2691: SYNTAX DisplayString (SIZE (0 | 3))
2692: MAX-ACCESS read-create
2693: STATUS current
2694: DESCRIPTION
2695: "The block number is the first three digits of the node_id,
2696: if available. These 3 hexadecimal digits identify the
2697: product."
2698: DEFVAL { ''H }
2699: ::= { dlswSdlcLsEntry 3 }
2700:
2701: dlswSdlcLsLocalIdNum OBJECT-TYPE
2702: SYNTAX DisplayString (SIZE (0 | 5))
2703: MAX-ACCESS read-create
2704: STATUS current
2705: DESCRIPTION
2706: "The ID number is the last 5 digits of the node_id, if
2707: available. These 5 hexadecimal digits are
2708: administratively defined and combined with the 3 digit
2709: block number form the node_id. This node_id is used to
2710: identify the local node and is included in SNA XIDs."
2711: DEFVAL { ''H }
2712: ::= { dlswSdlcLsEntry 4 }
2713:
2714: dlswSdlcLsRemoteMac OBJECT-TYPE
2715: SYNTAX MacAddressNC
2716: MAX-ACCESS read-create
2717: STATUS current
2718: DESCRIPTION
2719: "The MAC address to which DLSw should attempt to connect
2720: this link station. If this information is not available,
2721: a length of zero for this object should be returned."
2722: DEFVAL { ''H }
2723: ::= { dlswSdlcLsEntry 5 }
2724:
2725: dlswSdlcLsRemoteSap OBJECT-TYPE
2726: SYNTAX OCTET STRING (SIZE (0 | 1))
2727: MAX-ACCESS read-create
2728: STATUS current
2729: DESCRIPTION
2730: "The SAP of the remote station to which this link
2731: station should be connected. If this information
2732: is not available, a length of zero for this object
2733: should be returned."
2734: DEFVAL { ''H }
2735: ::= { dlswSdlcLsEntry 6 }
2736:
2737: dlswSdlcLsRowStatus OBJECT-TYPE
2738: SYNTAX RowStatus
2739: MAX-ACCESS read-create
2740: STATUS current
2741: DESCRIPTION
2742: "This object is used by the manager to create
2743: or delete the row entry in the dlswSdlcLsTable
2744: following the RowStatus textual convention."
2745: ::= { dlswSdlcLsEntry 7 }
2746:
2747:
2748: -- *******************************************************************
2749: -- TRAP GENERATION CONTROL
2750: -- *******************************************************************
2751: dlswTrapControl OBJECT IDENTIFIER ::= { dlswNode 10}
2752:
2753: dlswTrapCntlTConnPartnerReject OBJECT-TYPE
2754: SYNTAX INTEGER {
2755: enabled (1),
2756: disabled (2),
2757: partial (3)
2758: }
2759: MAX-ACCESS read-write
2760: STATUS current
2761: DESCRIPTION
2762: "Indicates whether the DLSw is permitted to emit partner
2763: reject related traps. With the value of `enabled'
2764: the DLSw will emit all partner reject related traps.
2765: With the value of `disabled' the DLSw will not emit
2766: any partner reject related traps. With the value
2767: of `partial' the DLSw will only emits partner reject
2768: traps for CapEx reject. The changes take effect
2769: immediately."
2770: ::= { dlswTrapControl 1 }
2771:
2772: dlswTrapCntlTConnProtViolation OBJECT-TYPE
2773: SYNTAX TruthValue
2774: MAX-ACCESS read-write
2775: STATUS current
2776: DESCRIPTION
2777: "Indicates whether the DLSw is permitted to generate
2778: protocol-violation traps on the events such as
2779: window size violation. The changes take effect
2780: immediately."
2781: ::= { dlswTrapControl 2 }
2782:
2783: dlswTrapCntlTConn OBJECT-TYPE
2784: SYNTAX INTEGER {
2785: enabled (1),
2786: disabled (2),
2787: partial (3)
2788: }
2789: MAX-ACCESS read-write
2790: STATUS current
2791: DESCRIPTION
2792: "Indicates whether the DLSw is permitted to emit transport
2793: connection up and down traps. With the value of `enabled'
2794: the DLSw will emit traps when connections enter `connected'
2795: and `disconnected' states. With the value of `disabled'
2796: the DLSw will not emit traps when connections enter of
2797: `connected' and `disconnected' states. With the value
2798: of `partial' the DLSw will only emits transport connection
2799: down traps when the connection is closed with busy.
2800: The changes take effect immediately."
2801: ::= { dlswTrapControl 3 }
2802:
2803: dlswTrapCntlCircuit OBJECT-TYPE
2804: SYNTAX INTEGER {
2805: enabled (1),
2806: disabled (2),
2807: partial (3)
2808: }
2809: MAX-ACCESS read-write
2810: STATUS current
2811: DESCRIPTION
2812: "Indicates whether the DLSw is permitted to generate
2813: circuit up and down traps. With the value of `enabled'
2814: the DLSw will emit traps when circuits enter `connected'
2815: and `disconnected' states. With the value of `disabled'
2816: the DLSw will not emit traps when circuits enter of
2817: `connected' and `disconnected' states. With the value
2818: of `partial' the DLSw will emit traps only for those
2819: circuits that are initiated by this DLSw, e.g.,
2820: originating the CUR_CS message. The changes take effect
2821: immediately."
2822: ::= { dlswTrapControl 4 }
2823:
2824: -- *******************************************************************
2825: -- NOTIFICATIONS, i.e., TRAP DEFINITIONS
2826: -- *******************************************************************
2827: dlswTraps OBJECT IDENTIFIER ::= { dlswMIB 0 }
2828:
2829: -- -------------------------------------------------------------------
2829: warning -
warning: note, -- terminates a comment
2829: severe -
lexically unexpected character, skipping to end of line
2830: -- This section defines the well-known notifications sent by
2831: -- DLSW agents.
2832: -- Care must be taken to insure that no particular notification
2833: -- is sent to a single receiving entity more often than once
2834: -- every five seconds.
2835: --
2836: -- Traps includes:
2837: -- (1) Partner rejected (capEx rejection, not in partner list, etc.)
2838: -- (2) DLSw protocol violation (e.g., window size violation, etc.)
2839: -- (3) Transport connection up/down
2840: -- (4) Circuit up/down
2841: -- -------------------------------------------------------------------
2841: warning -
warning: note, -- terminates a comment
2841: severe -
lexically unexpected character, skipping to end of line
2842: --
2843:
2844: dlswTrapTConnPartnerReject NOTIFICATION-TYPE
2844: minor error -
object `dlswTConnOperTDomain' of notification `dlswTrapTConnPartnerReject' must not be `not-accessible'
2844: minor error -
object `dlswTConnOperRemoteTAddr' of notification `dlswTrapTConnPartnerReject' must not be `not-accessible'
2845: OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr
2846: }
2847: STATUS current
2848: DESCRIPTION
2849: "This trap is sent each time a transport connection
2850: is rejected by a partner DLSw during Capabilities
2851: Exchanges. The emission of this trap is controlled
2852: by dlswTrapCntlTConnPartnerReject."
2853: ::= { dlswTraps 1 }
2854:
2855: dlswTrapTConnProtViolation NOTIFICATION-TYPE
2855: minor error -
object `dlswTConnOperTDomain' of notification `dlswTrapTConnProtViolation' must not be `not-accessible'
2855: minor error -
object `dlswTConnOperRemoteTAddr' of notification `dlswTrapTConnProtViolation' must not be `not-accessible'
2856: OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr
2857: }
2858: STATUS current
2859: DESCRIPTION
2860: "This trap is sent each time a protocol violation is
2861: detected for a transport connection. The emission of this
2862: trap is controlled by dlswTrapCntlTConnProtViolation."
2863: ::= { dlswTraps 2 }
2864:
2865: dlswTrapTConnUp NOTIFICATION-TYPE
2865: minor error -
object `dlswTConnOperTDomain' of notification `dlswTrapTConnUp' must not be `not-accessible'
2865: minor error -
object `dlswTConnOperRemoteTAddr' of notification `dlswTrapTConnUp' must not be `not-accessible'
2866: OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr
2867: }
2868: STATUS current
2869: DESCRIPTION
2870: "This trap is sent each time a transport connection
2871: enters `connected' state. The emission of this trap
2872: is controlled by dlswTrapCntlTConn."
2873: ::= { dlswTraps 3 }
2874:
2875: dlswTrapTConnDown NOTIFICATION-TYPE
2875: minor error -
object `dlswTConnOperTDomain' of notification `dlswTrapTConnDown' must not be `not-accessible'
2875: minor error -
object `dlswTConnOperRemoteTAddr' of notification `dlswTrapTConnDown' must not be `not-accessible'
2876: OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr
2877: }
2878: STATUS current
2879: DESCRIPTION
2880: "This trap is sent each time a transport connection
2881: enters `disconnected' state. The emission of this trap
2882: is controlled by dlswTrapCntlTConn."
2883: ::= { dlswTraps 4 }
2884:
2885: dlswTrapCircuitUp NOTIFICATION-TYPE
2885: minor error -
object `dlswCircuitS1Mac' of notification `dlswTrapCircuitUp' must not be `not-accessible'
2885: minor error -
object `dlswCircuitS1Sap' of notification `dlswTrapCircuitUp' must not be `not-accessible'
2885: minor error -
object `dlswCircuitS2Mac' of notification `dlswTrapCircuitUp' must not be `not-accessible'
2885: minor error -
object `dlswCircuitS2Sap' of notification `dlswTrapCircuitUp' must not be `not-accessible'
2886: OBJECTS { dlswCircuitS1Mac, dlswCircuitS1Sap,
2887: dlswCircuitS2Mac, dlswCircuitS2Sap
2888:
2889: }
2890: STATUS current
2891: DESCRIPTION
2892: "This trap is sent each time a circuit enters `connected'
2893: state. The emission of this trap is controlled by
2894: dlswTrapCntlCircuit."
2895: ::= { dlswTraps 5 }
2896:
2897: dlswTrapCircuitDown NOTIFICATION-TYPE
2897: minor error -
object `dlswCircuitS1Mac' of notification `dlswTrapCircuitDown' must not be `not-accessible'
2897: minor error -
object `dlswCircuitS1Sap' of notification `dlswTrapCircuitDown' must not be `not-accessible'
2897: minor error -
object `dlswCircuitS2Mac' of notification `dlswTrapCircuitDown' must not be `not-accessible'
2897: minor error -
object `dlswCircuitS2Sap' of notification `dlswTrapCircuitDown' must not be `not-accessible'
2898: OBJECTS { dlswCircuitS1Mac, dlswCircuitS1Sap,
2899: dlswCircuitS2Mac, dlswCircuitS2Sap
2900: }
2901: STATUS current
2902: DESCRIPTION
2903: "This trap is sent each time a circuit enters `disconnected'
2904: state. The emission of this trap is controlled by
2905: dlswTrapCntlCircuit."
2906: ::= { dlswTraps 6 }
2907:
2908:
2909: -- *******************************************************************
2910: -- CONFORMANCE INFORMATION
2911: -- *******************************************************************
2912: dlswConformance OBJECT IDENTIFIER ::= { dlsw 3 }
2913:
2914: dlswCompliances OBJECT IDENTIFIER ::= { dlswConformance 1 }
2915: dlswGroups OBJECT IDENTIFIER ::= { dlswConformance 2 }
2916:
2917: -- -------------------------------------------------------------------
2917: warning -
warning: note, -- terminates a comment
2917: severe -
lexically unexpected character, skipping to end of line
2918: -- COMPLIANCE STATEMENTS
2919: -- -------------------------------------------------------------------
2919: warning -
warning: note, -- terminates a comment
2919: severe -
lexically unexpected character, skipping to end of line
2920:
2921: -- ...................................................................
2922: -- Core compliance for all DLSw entities
2923: -- ...................................................................
2924: dlswCoreCompliance MODULE-COMPLIANCE
2925: STATUS current
2926: DESCRIPTION
2927: "The core compliance statement for all DLSw nodes."
2928: MODULE
2929: MANDATORY-GROUPS {
2930: dlswNodeGroup,
2931: dlswTConnStatGroup,
2932: dlswTConnConfigGroup,
2933: dlswTConnOperGroup,
2934: dlswInterfaceGroup,
2935: dlswCircuitGroup,
2936: dlswCircuitStatGroup,
2937: dlswNotificationGroup }
2938:
2939: GROUP dlswNodeNBGroup
2940: DESCRIPTION
2941: "The DLSw NetBIOS Node group is mandatory only for
2942: those DLSw entities that implement NetBIOS."
2943:
2944: GROUP dlswTConnNBGroup
2945: DESCRIPTION
2946: "The DLSw NetBIOS Transport Connection group is
2947: mandatory only for those DLSw entities that
2948: implement NetBIOS."
2949:
2950: OBJECT dlswNodeStatus
2951: MIN-ACCESS read-only
2952: DESCRIPTION
2953: "Write access is not required."
2954:
2955: OBJECT dlswNodeVirtualSegmentLFSize
2956: MIN-ACCESS read-only
2957: DESCRIPTION
2958: "Write access is not required."
2959:
2960: OBJECT dlswNodeResourceNBExclusivity
2961: MIN-ACCESS read-only
2962: DESCRIPTION
2963: "Write access is not required."
2964:
2965: OBJECT dlswNodeResourceMacExclusivity
2966: MIN-ACCESS read-only
2967: DESCRIPTION
2968: "Write access is not required."
2969:
2970: OBJECT dlswTrapCntlTConnPartnerReject
2971: MIN-ACCESS read-only
2972: DESCRIPTION
2973: "Write access is not required."
2974:
2975: OBJECT dlswTrapCntlTConnProtViolation
2976: MIN-ACCESS read-only
2977: DESCRIPTION
2978: "Write access is not required."
2979:
2980: OBJECT dlswTrapCntlTConn
2981: MIN-ACCESS read-only
2982: DESCRIPTION
2983: "Write access is not required."
2984:
2985: OBJECT dlswTrapCntlCircuit
2986: MIN-ACCESS read-only
2987: DESCRIPTION
2988: "Write access is not required."
2989:
2990: OBJECT dlswTConnConfigTDomain
2991: MIN-ACCESS read-only
2992: DESCRIPTION
2993: "Write access is not required."
2994:
2995: OBJECT dlswTConnConfigLocalTAddr
2996: MIN-ACCESS read-only
2997: DESCRIPTION
2998: "Write access is not required."
2999:
3000: OBJECT dlswTConnConfigRemoteTAddr
3001: MIN-ACCESS read-only
3002: DESCRIPTION
3003: "Write access is not required."
3004:
3005: OBJECT dlswTConnConfigEntryType
3006: MIN-ACCESS read-only
3007: DESCRIPTION
3008: "Write access is not required."
3009:
3010: OBJECT dlswTConnConfigGroupDefinition
3011: MIN-ACCESS read-only
3012: DESCRIPTION
3013: "Write access is not required."
3014:
3015: OBJECT dlswTConnConfigSetupType
3016: MIN-ACCESS read-only
3017: DESCRIPTION
3018: "Write access is not required."
3019:
3020: OBJECT dlswTConnConfigSapList
3021: MIN-ACCESS read-only
3022: DESCRIPTION
3023: "Write access is not required."
3024:
3025: OBJECT dlswTConnConfigAdvertiseMacNB
3026: MIN-ACCESS read-only
3027: DESCRIPTION
3028: "Write access is not required."
3029:
3030: OBJECT dlswTConnConfigInitCirRecvWndw
3031: MIN-ACCESS read-only
3032: DESCRIPTION
3033: "Write access is not required."
3034:
3035: OBJECT dlswTConnConfigRowStatus
3036: MIN-ACCESS read-only
3037: DESCRIPTION
3038: "Write access is not required."
3039:
3040: OBJECT dlswTConnOperState
3041: MIN-ACCESS read-only
3042: DESCRIPTION
3043: "Write access is not required."
3044:
3045: OBJECT dlswIfRowStatus
3046: MIN-ACCESS read-only
3047: DESCRIPTION
3048: "Write access is not required."
3049:
3050: OBJECT dlswIfVirtualSegment
3051: MIN-ACCESS read-only
3052: DESCRIPTION
3053: "Write access is not required."
3054:
3055: OBJECT dlswIfSapList
3056: MIN-ACCESS read-only
3057: DESCRIPTION
3058: "Write access is not required."
3059:
3060: OBJECT dlswCircuitState
3061: MIN-ACCESS read-only
3062: DESCRIPTION
3063: "Write access is not required."
3064:
3065: ::= { dlswCompliances 1 }
3066:
3067: -- ...................................................................
3068: -- Compliance for all DLSw entities that provide TCP transport.
3069: -- ...................................................................
3070: dlswTConnTcpCompliance MODULE-COMPLIANCE
3071: STATUS current
3072: DESCRIPTION
3073: "Compliance for DLSw nodes that use TCP as a
3074: transport connection protocol."
3075: MODULE
3076: MANDATORY-GROUPS {
3077: dlswTConnTcpConfigGroup,
3078: dlswTConnTcpOperGroup }
3079:
3080: OBJECT dlswTConnTcpConfigKeepAliveInt
3081: MIN-ACCESS read-only
3082: DESCRIPTION
3083: "Write access is not required."
3084:
3085: OBJECT dlswTConnTcpConfigTcpConnections
3086: MIN-ACCESS read-only
3087: DESCRIPTION
3088: "Write access is not required."
3089:
3090: OBJECT dlswTConnTcpConfigMaxSegmentSize
3091: MIN-ACCESS read-only
3092: DESCRIPTION
3093: "Write access is not required."
3094:
3095: ::= { dlswCompliances 2 }
3096:
3097: -- ...................................................................
3098: -- Compliance for all DLSw Entities that implement a directory
3099: -- ...................................................................
3100: dlswDirCompliance MODULE-COMPLIANCE
3101: STATUS current
3102: DESCRIPTION
3103: "Compliance for DLSw nodes that provide a directory
3104: function."
3105: MODULE
3106: MANDATORY-GROUPS {
3107: dlswDirGroup }
3108:
3109: GROUP dlswDirNBGroup
3110: DESCRIPTION
3111: "The DLSw NetBIOS group is mandatory only for
3112: those DLSw entities that implement NetBIOS."
3113:
3114: OBJECT dlswDirMacMac
3115: MIN-ACCESS read-only
3116: DESCRIPTION
3117: "Write access is not required."
3118:
3119: OBJECT dlswDirMacMask
3120: MIN-ACCESS read-only
3121: DESCRIPTION
3122: "Write access is not required."
3123:
3124: OBJECT dlswDirMacEntryType
3125: MIN-ACCESS read-only
3126: DESCRIPTION
3127: "Write access is not required."
3128:
3129: OBJECT dlswDirMacLocationType
3130: MIN-ACCESS read-only
3131: DESCRIPTION
3132: "Write access is not required."
3133:
3134: OBJECT dlswDirMacLocation
3135: MIN-ACCESS read-only
3136: DESCRIPTION
3137: "Write access is not required."
3138:
3139: OBJECT dlswDirMacStatus
3140: MIN-ACCESS read-only
3141: DESCRIPTION
3142: "Write access is not required."
3143:
3144: OBJECT dlswDirMacLFSize
3145: MIN-ACCESS read-only
3146: DESCRIPTION
3147: "Write access is not required."
3148:
3149: OBJECT dlswDirMacRowStatus
3150: MIN-ACCESS read-only
3151: DESCRIPTION
3152: "Write access is not required."
3153:
3154: OBJECT dlswDirNBName
3155: MIN-ACCESS read-only
3156: DESCRIPTION
3157: "Write access is not required."
3158:
3159: OBJECT dlswDirNBNameType
3160: MIN-ACCESS read-only
3161: DESCRIPTION
3162: "Write access is not required."
3163:
3164: OBJECT dlswDirNBEntryType
3165: MIN-ACCESS read-only
3166: DESCRIPTION
3167: "Write access is not required."
3168:
3169: OBJECT dlswDirNBLocationType
3170: MIN-ACCESS read-only
3171: DESCRIPTION
3172: "Write access is not required."
3173:
3174: OBJECT dlswDirNBLocation
3175: MIN-ACCESS read-only
3176: DESCRIPTION
3177: "Write access is not required."
3178:
3179: OBJECT dlswDirNBStatus
3180: MIN-ACCESS read-only
3181: DESCRIPTION
3182: "Write access is not required."
3183:
3184: OBJECT dlswDirNBLFSize
3185: MIN-ACCESS read-only
3186: DESCRIPTION
3187: "Write access is not required."
3188:
3189: OBJECT dlswDirNBRowStatus
3190: MIN-ACCESS read-only
3191: DESCRIPTION
3192: "Write access is not required."
3193:
3194: ::= { dlswCompliances 3 }
3195:
3196: -- ...................................................................
3197: -- Compliance for all DLSw entities that provide an ordered
3198: -- list of directory entries that match a resource
3199: -- ...................................................................
3200: dlswDirLocateCompliance MODULE-COMPLIANCE
3201: STATUS current
3202: DESCRIPTION
3203: "Compliance for DLSw nodes that provide an ordered
3204: list of directory entries for a given resource."
3205: MODULE
3206: MANDATORY-GROUPS {
3207: dlswDirLocateGroup }
3208:
3209: GROUP dlswDirLocateNBGroup
3210: DESCRIPTION
3211: "The DLSw NetBIOS group is mandatory only for
3212: those DLSw entities that implement NetBIOS."
3213:
3214: ::= { dlswCompliances 4 }
3215:
3216: -- ...................................................................
3217: -- Compliance for all DLSw entities that support SDLC end stations
3218: -- ...................................................................
3219: dlswSdlcCompliance MODULE-COMPLIANCE
3220: STATUS current
3221: DESCRIPTION
3222: "Compliance for DLSw nodes that support SDLC."
3223: MODULE
3224: MANDATORY-GROUPS {
3225: dlswSdlcGroup }
3226:
3227: OBJECT dlswSdlcLsLocalMac
3228: MIN-ACCESS read-only
3229: DESCRIPTION
3230: "Write access is not required."
3231:
3232: OBJECT dlswSdlcLsLocalSap
3233: MIN-ACCESS read-only
3234: DESCRIPTION
3235: "Write access is not required."
3236:
3237: OBJECT dlswSdlcLsLocalIdBlock
3238: MIN-ACCESS read-only
3239: DESCRIPTION
3240: "Write access is not required."
3241:
3242: OBJECT dlswSdlcLsLocalIdNum
3243: MIN-ACCESS read-only
3244: DESCRIPTION
3245: "Write access is not required."
3246:
3247: OBJECT dlswSdlcLsRemoteMac
3248: MIN-ACCESS read-only
3249: DESCRIPTION
3250: "Write access is not required."
3251:
3252: OBJECT dlswSdlcLsRemoteSap
3253: MIN-ACCESS read-only
3254: DESCRIPTION
3255: "Write access is not required."
3256:
3257: OBJECT dlswSdlcLsRowStatus
3258: MIN-ACCESS read-only
3259: DESCRIPTION
3260: "Write access is not required."
3261:
3262: ::= { dlswCompliances 5 }
3263:
3264: -- -------------------------------------------------------------------
3264: warning -
warning: note, -- terminates a comment
3264: severe -
lexically unexpected character, skipping to end of line
3265: -- CONFORMANCE GROUPS
3266: -- -------------------------------------------------------------------
3266: warning -
warning: note, -- terminates a comment
3266: severe -
lexically unexpected character, skipping to end of line
3267:
3268: -- ...................................................................
3269: -- Node Conformance Group
3270: -- ...................................................................
3271: dlswNodeGroup OBJECT-GROUP
3272: OBJECTS {
3273: dlswNodeVersion,
3274: dlswNodeVendorID,
3275: dlswNodeVersionString,
3276: dlswNodeStdPacingSupport,
3277: dlswNodeStatus,
3278: dlswNodeUpTime,
3279: dlswNodeVirtualSegmentLFSize,
3280: dlswNodeResourceMacExclusivity,
3281: dlswTrapCntlTConnPartnerReject,
3282: dlswTrapCntlTConnProtViolation,
3283: dlswTrapCntlTConn,
3284: dlswTrapCntlCircuit
3285: }
3286: STATUS current
3287: DESCRIPTION
3288: "Conformance group for DLSw node general information."
3289: ::= { dlswGroups 1 }
3290:
3291: -- ...................................................................
3292: dlswNodeNBGroup OBJECT-GROUP
3293: OBJECTS {
3294: dlswNodeResourceNBExclusivity
3295: }
3296: STATUS current
3297: DESCRIPTION
3298: "Conformance group for DLSw node general information
3299: specifically for nodes that support NetBIOS."
3300: ::= { dlswGroups 2 }
3301:
3302: -- ...................................................................
3303: dlswTConnStatGroup OBJECT-GROUP
3304: OBJECTS {
3305: dlswTConnStatActiveConnections,
3306: dlswTConnStatCloseIdles,
3307: dlswTConnStatCloseBusys
3308: }
3309: STATUS current
3310: DESCRIPTION
3311: "Conformance group for statistics for transport
3312: connections."
3313: ::= { dlswGroups 3 }
3314:
3315: -- ...................................................................
3316: dlswTConnConfigGroup OBJECT-GROUP
3317: OBJECTS {
3318: dlswTConnConfigTDomain,
3319: dlswTConnConfigLocalTAddr,
3320: dlswTConnConfigRemoteTAddr,
3321: dlswTConnConfigLastModifyTime,
3322: dlswTConnConfigEntryType,
3323: dlswTConnConfigGroupDefinition,
3324: dlswTConnConfigSetupType,
3325: dlswTConnConfigSapList,
3326: dlswTConnConfigAdvertiseMacNB,
3327: dlswTConnConfigInitCirRecvWndw,
3328: dlswTConnConfigOpens,
3329: dlswTConnConfigRowStatus
3330: }
3331: STATUS current
3332: DESCRIPTION
3333: "Conformance group for the configuration of
3334: transport connections."
3335: ::= { dlswGroups 4 }
3336:
3337: -- ...................................................................
3338: dlswTConnOperGroup OBJECT-GROUP
3339: OBJECTS {
3340: dlswTConnOperLocalTAddr,
3341: dlswTConnOperEntryTime,
3342: dlswTConnOperConnectTime,
3343: dlswTConnOperState,
3344: dlswTConnOperConfigIndex,
3345: dlswTConnOperFlowCntlMode,
3346: dlswTConnOperPartnerVersion,
3347: dlswTConnOperPartnerVendorID,
3348: dlswTConnOperPartnerVersionStr,
3349: dlswTConnOperPartnerInitPacingWndw,
3350: dlswTConnOperPartnerSapList,
3351: dlswTConnOperPartnerMacExcl,
3352: dlswTConnOperPartnerMacInfo,
3353: dlswTConnOperDiscTime,
3354: dlswTConnOperDiscReason,
3355: dlswTConnOperDiscActiveCir,
3356: dlswTConnOperInDataPkts,
3357: dlswTConnOperOutDataPkts,
3358: dlswTConnOperInDataOctets,
3359: dlswTConnOperOutDataOctets,
3360: dlswTConnOperInCntlPkts,
3361: dlswTConnOperOutCntlPkts,
3362: dlswTConnOperCURexSents,
3363: dlswTConnOperICRexRcvds,
3364: dlswTConnOperCURexRcvds,
3365: dlswTConnOperICRexSents,
3366: dlswTConnOperCirCreates,
3367: dlswTConnOperCircuits
3368: }
3369:
3370: STATUS current
3371: DESCRIPTION
3372: "Conformance group for operation information for
3373: transport connections."
3374: ::= { dlswGroups 5 }
3375: -- ...................................................................
3376: dlswTConnNBGroup OBJECT-GROUP
3377: OBJECTS {
3378: dlswTConnOperPartnerNBExcl,
3379: dlswTConnOperPartnerNBInfo,
3380: dlswTConnOperNQexSents,
3381: dlswTConnOperNRexRcvds,
3382: dlswTConnOperNQexRcvds,
3383: dlswTConnOperNRexSents
3384: }
3385: STATUS current
3386: DESCRIPTION
3387: "Conformance group for operation information for
3388: transport connections, specifically for nodes
3389: that support NetBIOS."
3390: ::= { dlswGroups 6 }
3391:
3392: -- ...................................................................
3393: dlswTConnTcpConfigGroup OBJECT-GROUP
3394: OBJECTS {
3395: dlswTConnTcpConfigKeepAliveInt,
3396: dlswTConnTcpConfigTcpConnections,
3397: dlswTConnTcpConfigMaxSegmentSize
3398: }
3399: STATUS current
3400: DESCRIPTION
3401: "Conformance group for configuration information for
3402: transport connections using TCP."
3403: ::= { dlswGroups 7 }
3404:
3405: -- ...................................................................
3406: dlswTConnTcpOperGroup OBJECT-GROUP
3407: OBJECTS {
3408: dlswTConnTcpOperKeepAliveInt,
3409: dlswTConnTcpOperPrefTcpConnections,
3410: dlswTConnTcpOperTcpConnections
3411: }
3412: STATUS current
3413: DESCRIPTION
3414: "Conformance group for operation information for
3415: transport connections using TCP."
3416: ::= { dlswGroups 8 }
3417:
3418: -- ...................................................................
3419: dlswInterfaceGroup OBJECT-GROUP
3420: OBJECTS {
3421: dlswIfRowStatus,
3422: dlswIfVirtualSegment,
3423: dlswIfSapList
3424: }
3425: STATUS current
3426: DESCRIPTION
3427: "Conformance group for DLSw interfaces."
3428: ::= { dlswGroups 9 }
3429:
3430: -- ...................................................................
3431: dlswDirGroup OBJECT-GROUP
3432: OBJECTS {
3433: dlswDirMacEntries,
3434: dlswDirMacCacheHits,
3435: dlswDirMacCacheMisses,
3436: dlswDirMacCacheNextIndex,
3437: dlswDirMacMac,
3438: dlswDirMacMask,
3439: dlswDirMacEntryType,
3440: dlswDirMacLocationType,
3441: dlswDirMacLocation,
3442: dlswDirMacStatus,
3443: dlswDirMacLFSize,
3444: dlswDirMacRowStatus
3445: }
3446: STATUS current
3447: DESCRIPTION
3448: "Conformance group for DLSw directory using MAC
3449: addresses."
3450: ::= { dlswGroups 10 }
3451:
3452: -- ...................................................................
3453: dlswDirNBGroup OBJECT-GROUP
3454: OBJECTS {
3455: dlswDirNBEntries,
3456: dlswDirNBCacheHits,
3457: dlswDirNBCacheMisses,
3458: dlswDirNBCacheNextIndex,
3459: dlswDirNBName,
3460: dlswDirNBNameType,
3461: dlswDirNBEntryType,
3462: dlswDirNBLocationType,
3463: dlswDirNBLocation,
3464: dlswDirNBStatus,
3465: dlswDirNBLFSize,
3466: dlswDirNBRowStatus
3467: }
3468: STATUS current
3469: DESCRIPTION
3470: "Conformance group for DLSw directory using NetBIOS
3471: names."
3472: ::= { dlswGroups 11 }
3473:
3474: -- ...................................................................
3475: dlswDirLocateGroup OBJECT-GROUP
3476: OBJECTS {
3477: dlswDirLocateMacLocation
3478: }
3479: STATUS current
3480: DESCRIPTION
3481: "Conformance group for a node that can return directory
3482: entry order for a given MAC address."
3483: ::= { dlswGroups 12 }
3484:
3485: -- ...................................................................
3486: dlswDirLocateNBGroup OBJECT-GROUP
3487: OBJECTS {
3488: dlswDirLocateNBLocation
3489: }
3490: STATUS current
3491: DESCRIPTION
3492: "Conformance group for a node that can return directory
3493: entry order for a given NetBIOS name."
3494: ::= { dlswGroups 13 }
3495:
3496: -- ...................................................................
3497: dlswCircuitStatGroup OBJECT-GROUP
3498: OBJECTS {
3499: dlswCircuitStatActives,
3500: dlswCircuitStatCreates
3501: }
3502: STATUS current
3503: DESCRIPTION
3504: "Conformance group for statistics about circuits."
3505: ::= { dlswGroups 14 }
3506:
3507: -- ...................................................................
3508: dlswCircuitGroup OBJECT-GROUP
3509: OBJECTS {
3510: dlswCircuitS1IfIndex,
3511: dlswCircuitS1DlcType,
3512: dlswCircuitS1RouteInfo,
3513: dlswCircuitS1CircuitId,
3514: dlswCircuitS1Dlc,
3515: dlswCircuitS2Location,
3516: dlswCircuitS2TDomain,
3517: dlswCircuitS2TAddress,
3518: dlswCircuitS2CircuitId,
3519: dlswCircuitOrigin,
3520: dlswCircuitEntryTime,
3521: dlswCircuitStateTime,
3522: dlswCircuitState,
3523: dlswCircuitPriority,
3524: dlswCircuitFCSendGrantedUnits,
3525: dlswCircuitFCSendCurrentWndw,
3526: dlswCircuitFCRecvGrantedUnits,
3527: dlswCircuitFCRecvCurrentWndw,
3528: dlswCircuitFCLargestRecvGranted,
3529: dlswCircuitFCLargestSendGranted,
3530: dlswCircuitFCHalveWndwSents,
3531: dlswCircuitFCResetOpSents,
3532: dlswCircuitFCHalveWndwRcvds,
3533: dlswCircuitFCResetOpRcvds,
3534: dlswCircuitDiscReasonLocal,
3535: dlswCircuitDiscReasonRemote,
3536: dlswCircuitDiscReasonRemoteData
3537: }
3538: STATUS current
3539: DESCRIPTION
3540: "Conformance group for DLSw circuits."
3541: ::= { dlswGroups 15 }
3542:
3543: -- ...................................................................
3544: dlswSdlcGroup OBJECT-GROUP
3545: OBJECTS {
3546: dlswSdlcLsEntries,
3547: dlswSdlcLsLocalMac,
3548: dlswSdlcLsLocalSap,
3549: dlswSdlcLsLocalIdBlock,
3550: dlswSdlcLsLocalIdNum,
3551: dlswSdlcLsRemoteMac,
3552: dlswSdlcLsRemoteSap,
3553: dlswSdlcLsRowStatus
3554: }
3555: STATUS current
3556: DESCRIPTION
3557: "Conformance group for DLSw SDLC support."
3558: ::= { dlswGroups 16 }
3559:
3560: -- ...................................................................
3561: dlswNotificationGroup NOTIFICATION-GROUP
3562: NOTIFICATIONS {
3563: dlswTrapTConnPartnerReject,
3564: dlswTrapTConnProtViolation,
3565: dlswTrapTConnUp,
3566: dlswTrapTConnDown,
3567: dlswTrapCircuitUp,
3568: dlswTrapCircuitDown
3569: }
3570: STATUS current
3571: DESCRIPTION
3572: "Conformance group for DLSw notifications."
3573: ::= { dlswGroups 17 }
3574:
3575: END