smilint output for ./PKTC-EVENT-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 9 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| basetype-unknown (error) | 2 |
| import-failed (error) | 2 |
| object-identifier-not-prefix (error) | 1 |
| sequence-type-mismatch (error) | 1 |
| type-unknown (error) | 2 |
Messages:
PKTC-EVENT-MIB
1: -- extracted from draft-ietf-ipcdn-pktc-eventmess-10.txt
2: -- at Thu Jul 12 06:08:51 2007
3:
4: PKTC-EVENT-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY,
8: OBJECT-TYPE,
9: Unsigned32,
10: NOTIFICATION-TYPE,
11: mib-2 FROM SNMPv2-SMI
12: TruthValue,
13: DateAndTime, TEXTUAL-CONVENTION
14: FROM SNMPv2-TC
15: SnmpAdminString FROM SNMP-FRAMEWORK-MIB
16: OBJECT-GROUP,
17: MODULE-COMPLIANCE,
18: NOTIFICATION-GROUP FROM SNMPv2-CONF
19: ifPhysAddress FROM IF-MIB
20: InetAddressType,
21: InetAddress,
22: InetPortNumber FROM INET-ADDRESS-MIB
23: snmpTargetBasicGroup, snmpTargetResponseGroup
24: FROM SNMP-TARGET-MIB
25: snmpNotifyGroup, snmpNotifyFilterGroup
26: FROM SNMP-NOTIFICATION-MIB
27: SyslogSeverity, SyslogFacility FROM SYSLOG-MIB;
27: error -
identifier `SyslogSeverity' cannot be imported from module `SYSLOG-MIB'
27: error -
identifier `SyslogFacility' cannot be imported from module `SYSLOG-MIB'
28:
29: pktcEventMib MODULE-IDENTITY
30: LAST-UPDATED "200707060000Z" -- July 06, 2007
31: ORGANIZATION "IETF IP over Cable Data Network Working Group"
32: CONTACT-INFO
33: "Sumanth Channabasappa
34: Cable Television Laboratories, Inc.
35: 858 Coal Creek Circle,
36: Louisville, CO 80027, USA
37: +1 303-661-3307
38: Sumanth@cablelabs.com
39:
40: Wim De Ketelaere
41: tComLabs
42: Gildestraat 8
43: 9000 Gent, Belgium
44: +32 9 269 22 90
45: deketelaere@tComLabs.com
46:
47: Eugene Nechamkin
48: Broadcom Corporation
49: 200 - 13711 International Place
50: Richmond, BC, V6V 2Z8, Canada
51: +1 604 233 8500
52: enechamkin@broadcom.com
53:
54: IETF IPCDN Working Group
55: General Discussion: ipcdn@ietf.org
56: Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
57: Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
58: Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com
59: Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com"
60:
61: DESCRIPTION
62: "This MIB module specifies the basic management objects
63: for managing events generated by the Multimedia
64: Terminal Adapter devices compliant with the PacketCable
65: and IPCablecom requirements.
66:
67: Copyright (C) The IETF Trust (2007). This version
68: of this MIB module is part of RFC nnnn; see the RFC
69: itself for full legal notices."
70: -- RFC Ed: replace nnnn with actual RFC number and remove this note.
71:
72: REVISION "200707060000Z" -- July 06, 2007
73:
74: DESCRIPTION
75: "Initial version, published as RFC yyyy."
76: -- RFC Ed: replace yyyy with actual RFC number and remove this note
77:
78: ::= { mib-2 XXX }
78: error -
`XXX' should start with a lower case letter
78: error -
Object identifier element `XXX' name only allowed as first element
79: -- RFC Ed: replace XXX with IANA-assigned number and remove this
80: -- note
81:
82:
83:
84: SyslogSeverityMask ::= TEXTUAL-CONVENTION
85: STATUS current
86: DESCRIPTION
87: "This textual convention represents a bit mask representing
88: the severity of the events that can be generated by an MTA.
89: It corresponds to the various severity levels associated
90: with syslog messages, as specified in The syslog Protocol,
91: [RFCAAA].
92:
93: emergency(0) - A condition that makes the system
94: unusable.
95: alert(1) - A service-affecting condition for which
96: immediate action must be taken.
97: critical(2) - A service-affecting critical condition.
98: error(3) - An error condition.
99: warning(4) - A warning condition.
100: notice(5) - A normal but significant condition.
101: info(6) - An informational message.
102: debug(7) - A debug message."
103: SYNTAX BITS {
104: emergency(0),
105: alert(1),
106: critical(2),
107: error(3),
108: warning(4),
109: notice(5),
110: info(6),
111: debug(7)
112: }
113:
114: --
115: --
116: pktcEventNotifications OBJECT IDENTIFIER ::= { pktcEventMib 0 }
117: pktcEventMibObjects OBJECT IDENTIFIER ::= { pktcEventMib 1 }
118: pktcEventConformance OBJECT IDENTIFIER ::= { pktcEventMib 2 }
119: --
120: --
121: pktcEventControl OBJECT IDENTIFIER ::= { pktcEventMibObjects 1 }
122: pktcEventThrottle OBJECT IDENTIFIER ::= { pktcEventMibObjects 2 }
123: pktcEventStatus OBJECT IDENTIFIER ::= { pktcEventMibObjects 3 }
124: pktcEventDescr OBJECT IDENTIFIER ::= { pktcEventMibObjects 4 }
125: pktcEventLog OBJECT IDENTIFIER ::= { pktcEventMibObjects 5 }
126:
127:
128: ---
129: -- Event Reporting control objects
130: ---
131: pktcEventReset OBJECT-TYPE
132: SYNTAX BITS {
133: resetEvLogTable(0),
134: resetEvDescrTable(1)
135: }
136: MAX-ACCESS read-write
137: STATUS current
138: DESCRIPTION
139: "This MIB object allows a management station to
140: clear the local log of generated events, reset the
141: management event descriptions, or both.
142:
143: MTAs generate management events. These events are stored
144: in the MIB table 'pktcEventLogTable'. If a management
145: station needs to clear all the current entries (e.g.,
146: after a troubleshooting operation is complete), it can
147: do so by setting the resetEvLogTable(0) bit to a value
148: of '1'.
149:
150: The MTA is pre-configured with the events that it can
151: generate. This is stored in the MIB table
152: 'pktcEventDescrTable'. This table also contains the
153: descriptions associated with these events. These
154: descriptions can be modified by a management station.
155: However, if the management station wishes to reset the
156: descriptions (to factory defaults), it can do so by
157: setting the resetEvDescrTable(1) bit to a value of '1'.
158:
159:
160: The MTA actions are summarized below:
161:
162: Bit resetEvLogTable(0) set to a value of '1'
163: - delete all entries in pktcEventLogTable;
164: - reset the value of pktcEventLogIndex to '0'.
165:
166: Bit resetEvDescrTable(1) set to a value of '1'
167: - reset the pktcEventDescrTable to the
168: factory default values.
169:
170: Bits resetEvLogTable(0) and resetEvDescrTable(1)
171: set to a value of '1'
172: - perform the above actions as though they were
173: performed individually (in any order).
174:
175: Setting a reset bit to a value of '0' MUST not
176: result in any action.
177:
178: The MTA MUST perform the above actions regardless of
179: persistence (i.e. storage in non-volatile memory).
180:
181: The MTA MUST always return a value of '00' when
182: this MIB Object is read."
183: ::= { pktcEventControl 1 }
184:
185:
186:
187: ---
188: -- syslog-specific MIB Objects
189: ---
190: pktcEventSyslog OBJECT IDENTIFIER ::= { pktcEventControl 2 }
191:
192: pktcEventSyslogCapabilities OBJECT-TYPE
193: SYNTAX BITS {
194: formatBSDSyslog(0),
195: formatSyslogProtocol(1),
196: transportUDP(2),
197: transportTLS(3)
198: }
199: MAX-ACCESS read-only
200: STATUS current
201: DESCRIPTION
202: "This MIB Object contains the MTA capabilities
203: for supporting the Syslog protocol.
204:
205: The MTA is allowed to support two Syslog message
206: formats, the BSD syslog message formats specified
207: in RFC 3164 (formatBSDSyslog), and the IETF
208: syslog protocol per [RFCAAA] (formatSyslogProtocol).
209:
210: The MTA MUST support formatBSDSyslog. The MTA
211: SHOULD support the IETF syslog standard.
212:
213: BSD syslog protocol specifies UDP as the transport
214: protocol, and the IETF syslog protocol allows
215: for multiple transport protocols. This MIB module
216: supports two transport protocols: UDP and TLS (the
217: latter is only applicable when
218: formatSyslogProtocol(2) is supported).
219:
220: The MTA MUST support UDP transport. The MTA MAY
221: support TLS for transport if it supports the IETF
222: syslog protocol.
223:
224: The MTA MUST set the appropriate bits, based on
225: its implementation."
226:
227: REFERENCE
228: "The BSD syslog Protocol, [RFC3164];
229: The syslog Protocol, [RFCAAA];
230: Transmission of syslog messages over UDP, [RFCBBB];
231: TLS Transport Mapping for Syslog, [RFCCCC]."
232: ::= { pktcEventSyslog 1 }
233:
234:
235: pktcEventSyslogAddressType OBJECT-TYPE
236: SYNTAX InetAddressType
237: MAX-ACCESS read-write
238: STATUS current
239: DESCRIPTION
240: "This MIB Object defines the Internet address type of
241: the syslog server specified by the MIB Object
242: 'pktcEventSyslogAddress' ."
243: REFERENCE
244: "PacketCable MTA Device Provisioning Specification,
245: [PKT-SP-PROV]."
246: DEFVAL { ipv4 }
247: ::= { pktcEventSyslog 2 }
248:
249: pktcEventSyslogAddress OBJECT-TYPE
250: SYNTAX InetAddress
251: MAX-ACCESS read-write
252: STATUS current
253: DESCRIPTION
254: "This MIB Object contains the IP address of the
255: syslog server to which the MTA can transmit a syslog
256: message upon the generation of a management event.
257:
258: If this MIB Object is set to a value other than
259: a routable unicast address ('0.0.0.0' or
260: 255.255.255.255 for IPv4), the MTA MUST
261: suspend the transmission of Syslog messages.
262:
263: The use of FQDNs is syntactically allowed, but
264: not recommended since a failure to resolve them in a
265: timely manner may leave the device without access to
266: the syslog daemon during critical network events.
267:
268: The type of address this object represents is defined
269: by the MIB Object pktDevEvsyslogAddressType.
270:
271: The format of the syslog message is specified by the
272: MIB Object 'pktcEventSyslogMsgFormat'."
273: REFERENCE
274: "PacketCable MTA Device Provisioning Specification,
275: [PKT-SP-PROV];
276: PacketCable Management Event Mechanism Specification,
277: [PKT-SP-MEM1.5];"
278: DEFVAL { "0.0.0.0" }
279: ::= { pktcEventSyslog 3 }
280:
281: pktcEventSyslogTransport OBJECT-TYPE
282: SYNTAX INTEGER {
283: udp(1),-- Transmission of syslog messages over UDP
284: tls(2) -- TLS Transport Mapping for Syslog
285: }
286: MAX-ACCESS read-write
287: STATUS current
288: DESCRIPTION
289: "This MIB Object specifies the transport to be
290: used to transmit syslog messages to the syslog
291: server contained in the MIB Object
292: 'pktcEventSyslogAddress'.
293:
294: Two possible transports are supported: UDP, and TLS.
295:
296: If the MTA does not support TLS, then an SNMP SET
297: operation to set the value to tls(2) MUST result in
298: an 'inconsistentValue' response."
299: REFERENCE
300: "Transmission of syslog messages over UDP, [RFCBBB];
301: TLS Transport Mapping for Syslog, [RFCCCC]."
302: DEFVAL {udp}
303: ::= { pktcEventSyslog 4 }
304:
305: pktcEventSyslogPort OBJECT-TYPE
306: SYNTAX InetPortNumber
307: MAX-ACCESS read-write
308: STATUS current
309: DESCRIPTION
310: "This MIB Object contains the port number of the
311: syslog Server to which the syslog messages are to
312: be transmitted.
313: The MTA MUST use the specified value to transmit
314: to the syslog Server."
315: REFERENCE
316: "Transmission of syslog messages over UDP, [RFCBBB];
317: TLS Transport Mapping for Syslog, [RFCCCC]."
318: DEFVAL { 514 }
319: ::= { pktcEventSyslog 5 }
320:
321:
322: pktcEventSyslogMsgFormat OBJECT-TYPE
323: SYNTAX INTEGER {
324: formatBSDSyslog(1), -- The BSD syslog Protocol
325: formatSyslogProtocol(2) -- The syslog Protocol
326: }
327: MAX-ACCESS read-write
328: STATUS current
329: DESCRIPTION
330: "This MIB Object contains the syslog message format to
331: be used for transmitting syslog messages to the server
332: contained in the MIB Object 'pktcEventSyslogServer'.
333:
334: Two formats are supported: formatBSDSyslog(1) as
335: specified in [RFC3164] and formatSyslogProtocol(2) as
336: specified in [RFCAAA].
337:
338: MTAs MUST support formatBSDSyslog(1). MTAs SHOULD
339: support formatSyslogProtocol(2)."
340: REFERENCE
341: "The BSD syslog Protocol, [RFC3164];
342: The syslog Protocol, [RFCAAA]."
343: DEFVAL { formatBSDSyslog }
344: ::= { pktcEventSyslog 6 }
345:
346:
347: ---
348: -- Event classes
349: ---
350: pktcEventClassReportTable OBJECT-TYPE
351: SYNTAX SEQUENCE OF PktcEventClassReportEntry
352: MAX-ACCESS not-accessible
353: STATUS current
354: DESCRIPTION
355: "This MIB table allows for management events that can be
356: generated by an MTA to be classified into categories,
357: or 'event classes'. For example, all the configuration
358: related events can be associated with an event class
359: titled 'configuration'. Such as a classification allows
360: for a management station to affect changes on a common
361: group of events, at once. Two operations are specified
362: on an event class: enabling or disabling of all the
363: events in an event class, and selective enabling or
364: disabling based on the severity level."
365: ::= { pktcEventControl 3 }
366:
367: pktcEventClassReportEntry OBJECT-TYPE
368: SYNTAX PktcEventClassReportEntry
369: MAX-ACCESS not-accessible
370: STATUS current
371: DESCRIPTION
372: "Each entry in this table specifies an event class as
373: identified by the MTA manufacturer, based on the events
374: supported.
375:
376: The MTA MUST create one entry (index=100) for the event
377: class titled 'generic'. This event class MUST contain
378: all the events that do not belong to a vendor specified
379: event class.
380:
381: In the case of events belonging to multiple categories,
382: event classes with lower indices take priority over
383: others."
384: INDEX { pktcEventClassIndex }
385: ::= { pktcEventClassReportTable 1 }
386:
387: PktcEventClassReportEntry::= SEQUENCE {
388: pktcEventClassIndex Unsigned32,
389: pktcEventClassName SnmpAdminString,
390: pktcEventClassReportStatus TruthValue,
391: pktcEventClassSeverityLevel SyslogSeverityMask
392: }
393:
394: pktcEventClassIndex OBJECT-TYPE
395: SYNTAX Unsigned32 (1..100)
396: MAX-ACCESS not-accessible
397: STATUS current
398: DESCRIPTION
399: "This MIB Object is an index into the event
400: class table."
401: ::= { pktcEventClassReportEntry 1 }
402:
403:
404: pktcEventClassName OBJECT-TYPE
405: SYNTAX SnmpAdminString (SIZE (1..100))
406: MAX-ACCESS read-only
407: STATUS current
408: DESCRIPTION
409: "This MIB Object contains the event class
410: name of an event class supported by the device.
411:
412: Vendors MAY define different event classes
413: (e.g. DHCP, SNMP, DEBUG) to group together
414: management events of a particular category."
415: ::= { pktcEventClassReportEntry 2 }
416:
417: pktcEventClassReportStatus OBJECT-TYPE
418: SYNTAX TruthValue
419: MAX-ACCESS read-write
420: STATUS current
421: DESCRIPTION
422: "This MIB Object indicates if events belonging
423: to a particular event class are to be enabled
424: or disabled for event reporting.
425:
426: Setting this object to a value of 'true' enables
427: reporting of all the events in the event class.
428: When enabled, the means of reporting is specified
429: by the MIB Object 'pktcEventDescrReporting'.
430:
431: Setting this object to a value of 'false' disables
432: any reporting, irrespective of the value of the
433: MIB Object 'pktcEventDescrReporting' for a specific
434: event.
435:
436: The default value of this MIB Object is vendor
437: specific. However, the vendor SHOULD enable all
438: event categories defined by PacketCable or
439: IPCableCom, by default."
440: ::= { pktcEventClassReportEntry 3 }
441:
442: pktcEventClassSeverityLevel OBJECT-TYPE
443: SYNTAX SyslogSeverityMask
444: MAX-ACCESS read-write
445: STATUS current
446: DESCRIPTION
447: "This MIB Object defines the severity level
448: of events belonging to a specific event class,
449: that are enabled for event reporting.
450:
451: This MIB Object has no effect on the event
452: reporting unless the MIB Object
453: 'pktcEventClassReportStatus' is set to a value
454: of 'true', for the corresponding event class.
455:
456: Setting a bit to a value of '1' implies that
457: events corresponding to that severity level MUST be
458: reported as defined by the corresponding
459: value of 'pktcEventDescrReporting' for events
460: in the event class.
461:
462: Setting a bit to a value of '0' implies that
463: events corresponding to that level MUST NOT be
464: reported, irrespective of the corresponding
465: value of 'pktcEventDescrReporting' for events
466: in the event class.
467:
468: It is recommended that the bits corresponding
469: to emergency(0), alert(1), critical(2) and error(3)
470: always be set to a value of '1'. "
471: REFERENCE
472: "The syslog Protocol, [RFCAAA];
473: Syslog Management Information Base, [RFCABC]."
474: ::= { pktcEventClassReportEntry 4 }
475:
476: ---
477: -- Event throttling control
478: ---
479:
480: pktcEventThrottleAdminStatus OBJECT-TYPE
481: SYNTAX INTEGER {
482: unconstrained(1),
483: maintainBelowThreshold(2),
484: stopAtThreshold(3),
485: inhibited(4)
486: }
487: MAX-ACCESS read-write
488: STATUS current
489: DESCRIPTION
490: "This MIB Object controls the throttling of the
491: transmitted messages upon generation of an event
492: (SNMP/syslog).
493:
494: A value of unconstrained(1) causes event messages
495: to be transmitted without regard to the threshold
496: settings.
497: A value of maintainBelowThreshold(2) causes event
498: messages to be suppressed if the number of transmissions
499: would otherwise exceed the threshold.
500: A value of stopAtThreshold(3) causes event message
501: transmission to cease at the threshold, and not
502: resume until directed to do so.
503:
504: A value of inhibited(4) causes all event message
505: Transmission to be suppressed.
506:
507: An event causing both an SNMP and a syslog message
508: is still treated as a single event.
509:
510: Writing to this object resets the thresholding state.
511:
512: Refer to MIB Objects pktcEventThrottleThreshold and
513: pktcEventThrottleInterval for information on
514: throttling."
515: DEFVAL { unconstrained }
516: ::= { pktcEventThrottle 1 }
517:
518:
519: pktcEventThrottleThreshold OBJECT-TYPE
520: SYNTAX Unsigned32
521: MAX-ACCESS read-write
522: STATUS current
523: DESCRIPTION
524: "This MIB Object contains the number of events per
525: pktcEventThrottleInterval to be transmitted before
526: throttling.
527:
528: An event causing both an SNMP and a syslog message is
529: still treated as a single event."
530: DEFVAL { 2 }
531: ::= { pktcEventThrottle 2 }
532:
533: pktcEventThrottleInterval OBJECT-TYPE
534: SYNTAX Unsigned32
535: UNITS "seconds"
536: MAX-ACCESS read-write
537: STATUS current
538: DESCRIPTION
539:
540: "This MIB Object contains the interval over which
541: the throttle threshold applies."
542: DEFVAL { 1 }
543: ::= { pktcEventThrottle 3 }
544:
545: ---
546: -- Reporting of transmission status
547: ---
548:
549: pktcEventTransmissionStatus OBJECT-TYPE
550: SYNTAX BITS {
551: syslogThrottled(0),
552: snmpThrottled(1),
553: validsyslogServerAbsent(2),
554: validSnmpManagerAbsent(3),
555: syslogTransmitError(4),
556: snmpTransmitError(5)
557: }
558: MAX-ACCESS read-only
559: STATUS current
560: DESCRIPTION
561: "This MIB Object reflects the status of the event
562: transmissions.
563:
564: If a bit corresponding to a state is set to a value
565: of:
566: '1', it indicates that the state is true
567: '0', it indicates that the state is false
568:
569: 'Event throttling' is based on thresholds and the
570: current setting of pktcEventThrottleAdminStatus.
571:
572: 'Server/Manager' indicators must be based on the
573: availability of valid syslog server/SNMP managers.
574:
575: 'Transmit Errors' must only be used in cases where the
576: MTA can identify unavailable servers."
577:
578:
579: ::= { pktcEventStatus 1 }
580:
581:
582:
583: ---
584: -- Description of events
585: ---
586:
587: pktcEventDescrTable OBJECT-TYPE
588: SYNTAX SEQUENCE OF PktcEventDescrEntry
589: MAX-ACCESS not-accessible
590: STATUS current
591: DESCRIPTION
592: "This MIB table contains all possible management events
593: that can be generated by the device. This includes
594: both PacketCable and IPCableCom defined, and
595: vendor-specific events."
596: ::= { pktcEventDescr 1 }
597:
598: pktcEventDescrEntry OBJECT-TYPE
599: SYNTAX PktcEventDescrEntry
600: MAX-ACCESS not-accessible
601: STATUS current
602: DESCRIPTION
603: "An entry in this table is created for each
604: event the MTA implementing this MIB is
605: capable of reporting."
606: INDEX { pktcEventDescrOrg, pktcEventDescrId }
607: ::= { pktcEventDescrTable 1 }
608:
609: PktcEventDescrEntry::= SEQUENCE {
610: pktcEventDescrOrg Unsigned32,
611: pktcEventDescrId Unsigned32,
612: pktcEventDescrFacility INTEGER,
613: pktcEventDescrSeverityLevel SyslogSeverity,
613: error -
unknown type `SyslogSeverity'
614: pktcEventDescrReporting BITS,
615: pktcEventDescrText SnmpAdminString,
616: pktcEventDescrClass SnmpAdminString
617: }
618:
619: pktcEventDescrOrg OBJECT-TYPE
620: SYNTAX Unsigned32(1..4294967295)
621: MAX-ACCESS not-accessible
622: STATUS current
623: DESCRIPTION
624: "This MIB Object provides the IANA enterprise number of
625: the Organization defining the event. Thus, all
626: PacketCable or IPCableCom defined events will contain
627: the PacketCable or IPCableCom IANA enterprise
628: number and for vendor-specific events it will contain
629: the IANA enterprise number of the defining
630: organization."
631: ::= { pktcEventDescrEntry 1 }
632:
633: pktcEventDescrId OBJECT-TYPE
634: SYNTAX Unsigned32(1..4294967295)
635: MAX-ACCESS not-accessible
636: STATUS current
637: DESCRIPTION
638: "This MIB Object contains the event identifier for the
639: specific event to which the priority and display
640: strings belong."
641: REFERENCE
642: "PacketCable Management Event Mechanism Specification,
643: [PKT-SP-MEM1.5];
644: PacketCable MTA Device Provisioning Specification,
645: [PKT-SP-PROV]."
646: ::= { pktcEventDescrEntry 2 }
647:
648: pktcEventDescrFacility OBJECT-TYPE
648: error -
type `SyslogFacility' of node `pktcEventDescrFacility' does not resolve to a known base type
649: SYNTAX SyslogFacility
650: MAX-ACCESS read-only
650: error -
unknown type `SyslogFacility'
651: STATUS current
652: DESCRIPTION
653: "This MIB Object contains the facility
654: for the event.
655: For PacketCable, IPCableCom or ETSI events
656: this MUST be set to a value of local0(16)."
657: REFERENCE
658: "The syslog Protocol, [RFCAAA]."
659: ::= { pktcEventDescrEntry 3 }
659: error -
type of `pktcEventDescrFacility' in sequence and object type definition do not match
660:
661: pktcEventDescrSeverityLevel OBJECT-TYPE
661: error -
type `SyslogSeverity' of node `pktcEventDescrSeverityLevel' does not resolve to a known base type
662: SYNTAX SyslogSeverity
663: MAX-ACCESS read-write
664: STATUS current
665: DESCRIPTION
666: "This MIB Object contains the severity level that
667: is applicable to the specified event."
668: REFERENCE
669: "The syslog Protocol, [RFCAAA];
670: Syslog Management Information Base, [RFCABC]."
671: ::= { pktcEventDescrEntry 4 }
672:
673: pktcEventDescrReporting OBJECT-TYPE
674: SYNTAX BITS {
675: local(0),
676: syslog(1),
677: snmpTrap(2),
678: snmpInform(3)
679: }
680: MAX-ACCESS read-write
681: STATUS current
682: DESCRIPTION
683: "This MIB Object defines the action to be taken on
684: occurrence of this event. Bit local(0) refers to local
685: logging of events, bit sylog(1) refers to the
686: transmission of events using syslog, bit snmpTrap(2)
687: refers to the transmission of events using SNMP Traps
688: (SNMPv2-Trap-PDU) and bit snmpInform(3)refers to the
689: transmission of events using SNMP INFORMs.
690: Setting a bit to a value of '1' indicates that the
691: corresponding action will be taken upon occurrence of
692: this event. If none of the bits are set then no action
693: is taken upon occurrence of the event. The success of
694: transmission using syslog and SNMP depends on the
695: MTA configuration. For example, a valid syslog server
696: address is required for syslog message transmission.
697:
698: Specification of a management event does not necessarily
699: include the actions to be taken upon its generation,
700: i.e., it does not need to specify if a generated event
701: needs to be transmitted via SNMP, syslog or locally
702: stored.
703:
704: Thus, certain default values of this MIB OBject is
705: are specified, based on the event's severity level
706: (refer to the MIB Object 'pktcEventDescrSeverityLevel'.)
707:
708: If the severity level of an event is emergency(0),
709: alert(1), critical(2) or error(3), the MTA MUST set the
710: bits for local(0), syslog(1) and snmpInform(3) to a
711: value of '1', and the remaining bits to a value of '0'.
712: For an event with any other severity level the MTA MUST
713: set the bits for local(0) and syslog(1) to a value of
714: '1' and the rest of the bits to a value of '0'."
715: ::= { pktcEventDescrEntry 5 }
716:
717:
718: pktcEventDescrText OBJECT-TYPE
719: SYNTAX SnmpAdminString(SIZE (0..127))
720: MAX-ACCESS read-write
721: STATUS current
722: DESCRIPTION
723: "This MIB Object provides a human-readable description
724: of the event."
725: ::= { pktcEventDescrEntry 6 }
726:
727: pktcEventDescrClass OBJECT-TYPE
728: SYNTAX SnmpAdminString(SIZE (1..100))
729: MAX-ACCESS read-only
730: STATUS current
731: DESCRIPTION
732: "This MIB Object represents an event class
733: associated with the corresponding event.
734:
735: See the MIB table 'pktcEventClassReportTable'
736: for a description of event classes and usage.
737:
738: If the event is not categorized into a specific
739: vendor-specified event class, it will be
740: associated with the event class 'generic'."
741:
742: ::= { pktcEventDescrEntry 7 }
743:
744: ---
745: -- Log of generated events
746: ---
747: pktcEventLogTable OBJECT-TYPE
748: SYNTAX SEQUENCE OF PktcEventLogEntry
749: MAX-ACCESS not-accessible
750: STATUS current
751: DESCRIPTION
752: "This MIB table contains a log of the events
753: generated by the MTA.
754: A description of all the events that can be
755: generated by the device can be obtained from the
756: MIB table 'pktcEventDescrTable'.
757: The contents of this table MAY persist in non-volatile
758: memory."
759: ::= { pktcEventLog 1 }
760:
761: pktcEventLogEntry OBJECT-TYPE
762: SYNTAX PktcEventLogEntry
763: MAX-ACCESS not-accessible
764: STATUS current
765: DESCRIPTION
766: "Each entry in this table describes an event that
767: has occurred, indexed in the chronological order of
768: generation. The details of the event are borrowed
769: from the parameters associated with the corresponding
770: event entry in 'pktcEventDescrTable', at the
771: time of the event generation.
772: While all entries created as such can be cleared using
773: the MIB Object pktcEventReset, the Event entries
774: themselves cannot be individually deleted."
775:
776: INDEX { pktcEventLogIndex }
777: ::= { pktcEventLogTable 1 }
778:
779: PktcEventLogEntry ::= SEQUENCE {
780: pktcEventLogIndex Unsigned32,
781: pktcEventLogTime DateAndTime,
782: pktcEventLogOrg Unsigned32,
783: pktcEventLogId Unsigned32,
784: pktcEventLogText SnmpAdminString,
785: pktcEventLogEndpointName SnmpAdminString,
786: pktcEventLogType BITS,
787: pktcEventLogTargetInfo SnmpAdminString,
788: pktcEventLogCorrelationId Unsigned32,
789: pktcEventLogAdditionalInfo SnmpAdminString
790: }
791:
792: pktcEventLogIndex OBJECT-TYPE
793: SYNTAX Unsigned32(1..4294967295)
794: MAX-ACCESS not-accessible
795: STATUS current
796: DESCRIPTION
797: "This MIB Object provides relative ordering of the
798: objects in the event log.
799:
800: This object will always increase except when
801: (a) the log is reset via pktcEventReset,
802: (b) the device reboots and does not implement
803: non-volatile storage for this log,
804: (c) it reaches the value 2^31.
805:
806: In all the above, newer events will be stored starting
807: with an index value of '1' (cyclic rotation)."
808: ::= { pktcEventLogEntry 1 }
809:
810:
811: pktcEventLogTime OBJECT-TYPE
812: SYNTAX DateAndTime
813: MAX-ACCESS read-only
814: STATUS current
815: DESCRIPTION
816: "This MIB Object provides a human-readable description
817: of the time at which the event occurred. The actual time
818: used SHOULD be defined by the architecture using this
819: MIB definition. If unspecified, this MUST be the local
820: time."
821: REFERENCE
822: "The BSD syslog Protocol, [RFC3164];
823: The syslog Protocol, [RFCAAA]."
824: ::= { pktcEventLogEntry 2 }
825:
826:
827: pktcEventLogOrg OBJECT-TYPE
828: SYNTAX Unsigned32(1..4294967295)
829: MAX-ACCESS read-only
830: STATUS current
831: DESCRIPTION
832: "This MIB Object provides the IANA enterprise number of
833: the Organization defining the event. Thus, all
834: PacketCable or IPCableCom defined events will contain
835: the CableLabs or IPCableCom IANA enterprise number and
836: for vendor-specific events it will contain the IANA
837: enterprise number of the defining organization."
838: ::= { pktcEventLogEntry 3 }
839:
840: pktcEventLogId OBJECT-TYPE
841: SYNTAX Unsigned32
842: MAX-ACCESS read-only
843: STATUS current
844: DESCRIPTION
845: "This MIB Object contains the event identifier for the
846: specific event to which the priority and display strings
847: belong."
848: ::= { pktcEventLogEntry 4 }
849:
850: pktcEventLogText OBJECT-TYPE
851: SYNTAX SnmpAdminString
852: MAX-ACCESS read-only
853: STATUS current
854: DESCRIPTION
855: "This MIB Object contains the contents of
856: the MIB Object 'pktcEventDescrText', corresponding
857: to the event, at the moment of generation."
858: ::= { pktcEventLogEntry 5 }
859:
860:
861: pktcEventLogEndpointName OBJECT-TYPE
862: SYNTAX SnmpAdminString
863: MAX-ACCESS read-only
864: STATUS current
865: DESCRIPTION
866: "This MIB Object provides the endpoint identifier
867: followed by the PacketCable MTA's Fully Qualified
868: Domain Name (FQDN) and the IP Address (IP)
869: of the PacketCable MTA device.
870:
871: This will be denoted as follows:
872: aaln/n:<FQDN>/<IP>, where 'n' is the Endpoint number.
873: or
874: <FQDN>/<IP> if it is not specific to an endpoint."
875: ::= { pktcEventLogEntry 6 }
876:
877: pktcEventLogType OBJECT-TYPE
878: SYNTAX BITS {
879: local(0),
880: syslog (1),
881: trap (2),
882: inform (3)
883: }
884: MAX-ACCESS read-only
885: STATUS current
886: DESCRIPTION
887: "This MIB Object contains the kind of actions taken by
888: the MTA when the event occurred.
889:
890: A bit with a value of '1' indicates the corresponding
891: action was taken. Setting it to a value of '0'
892: indicates that the corresponding action was not taken.
893:
894: An event may trigger one or more actions (e.g.: syslog
895: and SNMP) or may remain as a local event since
896: transmissions could be disabled or inhibited as defined
897: by the Throttle MIB Objects."
898:
899: ::= { pktcEventLogEntry 7 }
900:
901: pktcEventLogTargetInfo OBJECT-TYPE
902: SYNTAX SnmpAdminString
903: MAX-ACCESS read-only
904: STATUS current
905: DESCRIPTION
906: "This MIB Object contains a comma separated list of the
907: actions taken for external notifications, along with the
908: target IP address for the generated events. Locally
909: stored events must not be recorded in this MIB Object.
910:
911: The syntax is as:
912: <action-1/IP>,<action-2/IP>,<action-3/IP>
913:
914: Where <action-n/IP> is to be denoted as follows:
915: For syslog events:
916: syslog/<IP address of the syslog Server>
917: For SNMP traps:
918: snmpTrap/<IP address of the SNMP Server>
919: For SNMP INFORMS:
920: snmpInform/<IP address of the SNMP Server>
921:
922: If there are multiple targets for the same type (SNMP
923: Traps sent to multiple IP addresses) or if there are
924: multiple messages sent to the same IP (syslog and SNMP
925: sent to the same IP address) they need to be reported
926: individually."
927: ::= { pktcEventLogEntry 8 }
928:
929:
930: pktcEventLogCorrelationId OBJECT-TYPE
931: SYNTAX Unsigned32
932: MAX-ACCESS read-only
933: STATUS current
934: DESCRIPTION
935: "This MIB Object contains the correlation ID
936: generated by the MTA during the initiation of the
937: last provisioning flow, within or following which
938: the event occurred.
939:
940: Although a Correlation-ID, once generated after MTA
941: reset, does not change until next MTA reset, the
942: value of this object will differ for the events
943: preserved across MTA resets in case of a persistent
944: pktcEventLogTable.
945:
946: For more information on the generation of correlation
947: ids, refer to the corresponding PacketCable/IPCableCom
948: Device Provisioning specifications."
949: REFERENCE
950: "PacketCable MTA Device Provisioning Specification,
951: [PKT-SP-PROV]."
952: ::= { pktcEventLogEntry 9 }
953:
954: pktcEventLogAdditionalInfo OBJECT-TYPE
955: SYNTAX SnmpAdminString
956: MAX-ACCESS read-only
957: STATUS current
958: DESCRIPTION
959: "This MIB Object contains additional, useful
960: information in relation to the corresponding event that
961: an MTA might wish to report (for example: parameterized
962: data or debugging information). The format is
963: vendor-specific.
964: If MTA cannot provide any additional information for
965: the particular event generated, it MUST populate this
966: MIB Object with a string of zero-length."
967: ::= { pktcEventLogEntry 10 }
968:
969:
970: ---
971: -- Notifications
972: ---
973:
974: pktcEventInform NOTIFICATION-TYPE
975: OBJECTS {
976: pktcEventLogTime,
977: pktcEventLogOrg,
978: pktcEventLogId,
979: pktcEventLogEndpointName,
980: pktcEventLogCorrelationId,
981: ifPhysAddress
982: }
983: STATUS current
984: DESCRIPTION
985: "This Notification MIB Objects contains the SNMP Inform
986: contents for event reporting.
987:
988: It contains the event log time, the organization
989: ID, the event identifier, the endpoint identifier, the
990: correlation id, and the MTA MAC address."
991: ::= { pktcEventNotifications 1 }
992:
993:
994: pktcEventTrap NOTIFICATION-TYPE
995: OBJECTS {
996: pktcEventLogTime,
997: pktcEventLogOrg,
998: pktcEventLogId,
999: pktcEventLogEndpointName,
1000: pktcEventLogCorrelationId,
1001: ifPhysAddress}
1002: STATUS current
1003: DESCRIPTION
1004: "This Notification MIB Objects contains the SNMP Trap
1005: (SNMPv2-Trap-PDU) contents for event reporting.
1006:
1007: It contains the event log time, the organization
1008: ID, the event identifier, the endpoint identifier,
1009: the correlation id, and the MTA MAC address."
1010: ::= { pktcEventNotifications 2 }
1011:
1012:
1013: ---
1014: -- Conformance/Compliance
1015: ---
1016:
1017:
1018: pktcEventCompliances OBJECT IDENTIFIER ::=
1019: { pktcEventConformance 1 }
1020: pktcEventGroups OBJECT IDENTIFIER ::=
1021: { pktcEventConformance 2 }
1022:
1023:
1024: pktcEventBasicCompliance MODULE-COMPLIANCE
1025: STATUS current
1026: DESCRIPTION
1027: "The compliance statement for devices that implement
1028: Event reporting feature."
1029: MODULE --pktcEventMib
1030:
1031:
1032: MANDATORY-GROUPS {
1033: pktcEventGroup,
1034: pktcEventNotificationGroup
1035: }
1036:
1037: MODULE SNMP-TARGET-MIB
1038: MANDATORY-GROUPS {
1039: snmpTargetBasicGroup,
1040: snmpTargetResponseGroup
1041: }
1042:
1043: MODULE SNMP-NOTIFICATION-MIB
1044: MANDATORY-GROUPS {
1045: snmpNotifyGroup,
1046: snmpNotifyFilterGroup
1047: }
1048:
1049: ::= { pktcEventCompliances 3 }
1050:
1051: pktcEventGroup OBJECT-GROUP
1052: OBJECTS {
1053: pktcEventReset,
1054: pktcEventSyslogCapabilities,
1055: pktcEventSyslogAddressType,
1056: pktcEventSyslogAddress,
1057: pktcEventSyslogTransport,
1058: pktcEventSyslogPort,
1059: pktcEventSyslogMsgFormat,
1060: pktcEventThrottleAdminStatus,
1061: pktcEventThrottleThreshold,
1062: pktcEventThrottleInterval,
1063: pktcEventTransmissionStatus,
1064: pktcEventDescrFacility,
1065: pktcEventDescrSeverityLevel,
1066: pktcEventDescrReporting,
1067: pktcEventDescrText,
1068: pktcEventLogTime,
1069: pktcEventLogOrg,
1070: pktcEventLogId,
1071: pktcEventLogText,
1072: pktcEventLogEndpointName,
1073: pktcEventLogType,
1074: pktcEventLogTargetInfo,
1075: pktcEventLogCorrelationId,
1076: pktcEventLogAdditionalInfo,
1077: pktcEventDescrClass,
1078: pktcEventClassName,
1079: pktcEventClassReportStatus,
1080: pktcEventClassSeverityLevel
1081: }
1082:
1083: STATUS current
1084: DESCRIPTION
1085: "Group of MIB objects for PacketCable Management Event
1086: MIB."
1087: ::= { pktcEventGroups 1 }
1088:
1089:
1090: pktcEventNotificationGroup NOTIFICATION-GROUP
1091: NOTIFICATIONS { pktcEventInform, pktcEventTrap }
1092: STATUS current
1093: DESCRIPTION
1094: "Group of MIB objects for notifications related to
1095: change in status of the MTA Device."
1096: ::= { pktcEventGroups 2 }
1097: END
1098:
1099: --
1100: -- Copyright (C) The IETF Trust (2007).
1101: --
1102: -- This document is subject to the rights, licenses and restrictions
1103: -- contained in BCP 78, and except as set forth therein, the authors
1104: -- retain all their rights.
1105: --
1106: -- This document and the information contained herein are provided on
1107: -- an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
1108: -- REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
1109: -- IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
1110: -- WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
1111: -- WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
1112: -- ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
1113: -- FOR A PARTICULAR PURPOSE.
1114: --
1115: -- Intellectual Property
1116: --
1117: -- The IETF takes no position regarding the validity or scope of any
1118: -- Intellectual Property Rights or other rights that might be claimed
1119: -- to pertain to the implementation or use of the technology described
1120: -- in this document or the extent to which any license under such
1121: -- rights might or might not be available; nor does it represent that
1122: -- it has made any independent effort to identify any such rights.
1123: -- Information on the procedures with respect to rights in RFC
1124: -- documents can be found in BCP 78 and BCP 79.
1125: --
1126: -- Copies of IPR disclosures made to the IETF Secretariat and any
1127: -- assurances of licenses to be made available, or the result of an
1128: -- attempt made to obtain a general license or permission for the use
1129: -- of such proprietary rights by implementers or users of this
1130: -- specification can be obtained from the IETF on-line IPR repository
1131: -- at http://www.ietf.org/ipr.
1132: --
1133: -- The IETF invites any interested party to bring to its attention any
1134: -- copyrights, patents or patent applications, or other proprietary
1135: -- rights that may cover technology that may be required to implement
1136: -- this standard. Please address the information to the IETF at ietf-
1137: -- ipr@ietf.org.
1138: --
1139: