DISMAN-SCHEDULE-MIB.txt 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700
  1. DISMAN-SCHEDULE-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
  4. Integer32, Unsigned32, Counter32, mib-2, zeroDotZero
  5. FROM SNMPv2-SMI
  6. TEXTUAL-CONVENTION,
  7. DateAndTime, RowStatus, StorageType, VariablePointer
  8. FROM SNMPv2-TC
  9. MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  10. FROM SNMPv2-CONF
  11. SnmpAdminString
  12. FROM SNMP-FRAMEWORK-MIB;
  13. schedMIB MODULE-IDENTITY
  14. LAST-UPDATED "200201070000Z"
  15. ORGANIZATION "IETF Distributed Management Working Group"
  16. CONTACT-INFO
  17. "WG EMail: disman@dorothy.bmc.com
  18. Subscribe: disman-request@dorothy.bmc.com
  19. Chair: Randy Presuhn
  20. BMC Software, Inc.
  21. Postal: Office 1-3141
  22. 2141 North First Street
  23. San Jose, California 95131
  24. USA
  25. EMail: rpresuhn@bmc.com
  26. Phone: +1 408 546-1006
  27. Editor: David B. Levi
  28. Nortel Networks
  29. Postal: 4401 Great America Parkway
  30. Santa Clara, CA 95052-8185
  31. USA
  32. EMail: dlevi@nortelnetworks.com
  33. Phone: +1 865 686 0432
  34. Editor: Juergen Schoenwaelder
  35. TU Braunschweig
  36. Postal: Bueltenweg 74/75
  37. 38106 Braunschweig
  38. Germany
  39. EMail: schoenw@ibr.cs.tu-bs.de
  40. Phone: +49 531 391-3283"
  41. DESCRIPTION
  42. "This MIB module defines a MIB which provides mechanisms to
  43. schedule SNMP set operations periodically or at specific
  44. points in time."
  45. REVISION "200201070000Z"
  46. DESCRIPTION
  47. "Revised version, published as RFC 3231.
  48. This revision introduces a new object type called
  49. schedTriggers. Created new conformance and compliance
  50. statements that take care of the new schedTriggers object.
  51. Several clarifications have been added to remove ambiguities
  52. that were discovered and reported by implementors."
  53. REVISION "199811171800Z"
  54. DESCRIPTION
  55. "Initial version, published as RFC 2591."
  56. ::= { mib-2 63 }
  57. --
  58. -- The various groups defined within this MIB definition:
  59. --
  60. schedObjects OBJECT IDENTIFIER ::= { schedMIB 1 }
  61. schedNotifications OBJECT IDENTIFIER ::= { schedMIB 2 }
  62. schedConformance OBJECT IDENTIFIER ::= { schedMIB 3 }
  63. --
  64. -- Textual Conventions:
  65. --
  66. SnmpPduErrorStatus ::= TEXTUAL-CONVENTION
  67. STATUS current
  68. DESCRIPTION
  69. "This TC enumerates the SNMPv1 and SNMPv2 PDU error status
  70. codes as defined in RFC 1157 and RFC 1905. It also adds a
  71. pseudo error status code `noResponse' which indicates a
  72. timeout condition."
  73. SYNTAX INTEGER {
  74. noResponse(-1),
  75. noError(0),
  76. tooBig(1),
  77. noSuchName(2),
  78. badValue(3),
  79. readOnly(4),
  80. genErr(5),
  81. noAccess(6),
  82. wrongType(7),
  83. wrongLength(8),
  84. wrongEncoding(9),
  85. wrongValue(10),
  86. noCreation(11),
  87. inconsistentValue(12),
  88. resourceUnavailable(13),
  89. commitFailed(14),
  90. undoFailed(15),
  91. authorizationError(16),
  92. notWritable(17),
  93. inconsistentName(18)
  94. }
  95. --
  96. -- Some scalars which provide information about the local time zone.
  97. --
  98. schedLocalTime OBJECT-TYPE
  99. SYNTAX DateAndTime (SIZE (11))
  100. MAX-ACCESS read-only
  101. STATUS current
  102. DESCRIPTION
  103. "The local time used by the scheduler. Schedules which
  104. refer to calendar time will use the local time indicated
  105. by this object. An implementation MUST return all 11 bytes
  106. of the DateAndTime textual-convention so that a manager
  107. may retrieve the offset from GMT time."
  108. ::= { schedObjects 1 }
  109. --
  110. -- The schedule table which controls the scheduler.
  111. --
  112. schedTable OBJECT-TYPE
  113. SYNTAX SEQUENCE OF SchedEntry
  114. MAX-ACCESS not-accessible
  115. STATUS current
  116. DESCRIPTION
  117. "This table defines scheduled actions triggered by
  118. SNMP set operations."
  119. ::= { schedObjects 2 }
  120. schedEntry OBJECT-TYPE
  121. SYNTAX SchedEntry
  122. MAX-ACCESS not-accessible
  123. STATUS current
  124. DESCRIPTION
  125. "An entry describing a particular scheduled action.
  126. Unless noted otherwise, writable objects of this row
  127. can be modified independent of the current value of
  128. schedRowStatus, schedAdminStatus and schedOperStatus.
  129. In particular, it is legal to modify schedInterval
  130. and the objects in the schedCalendarGroup when
  131. schedRowStatus is active and schedAdminStatus and
  132. schedOperStatus are both enabled."
  133. INDEX { schedOwner, schedName }
  134. ::= { schedTable 1 }
  135. SchedEntry ::= SEQUENCE {
  136. schedOwner SnmpAdminString,
  137. schedName SnmpAdminString,
  138. schedDescr SnmpAdminString,
  139. schedInterval Unsigned32,
  140. schedWeekDay BITS,
  141. schedMonth BITS,
  142. schedDay BITS,
  143. schedHour BITS,
  144. schedMinute BITS,
  145. schedContextName SnmpAdminString,
  146. schedVariable VariablePointer,
  147. schedValue Integer32,
  148. schedType INTEGER,
  149. schedAdminStatus INTEGER,
  150. schedOperStatus INTEGER,
  151. schedFailures Counter32,
  152. schedLastFailure SnmpPduErrorStatus,
  153. schedLastFailed DateAndTime,
  154. schedStorageType StorageType,
  155. schedRowStatus RowStatus,
  156. schedTriggers Counter32
  157. }
  158. schedOwner OBJECT-TYPE
  159. SYNTAX SnmpAdminString (SIZE(0..32))
  160. MAX-ACCESS not-accessible
  161. STATUS current
  162. DESCRIPTION
  163. "The owner of this scheduling entry. The exact semantics of
  164. this string are subject to the security policy defined by
  165. the security administrator."
  166. ::= { schedEntry 1 }
  167. schedName OBJECT-TYPE
  168. SYNTAX SnmpAdminString (SIZE(1..32))
  169. MAX-ACCESS not-accessible
  170. STATUS current
  171. DESCRIPTION
  172. "The locally-unique, administratively assigned name for this
  173. scheduling entry. This object allows a schedOwner to have
  174. multiple entries in the schedTable."
  175. ::= { schedEntry 2 }
  176. schedDescr OBJECT-TYPE
  177. SYNTAX SnmpAdminString
  178. MAX-ACCESS read-create
  179. STATUS current
  180. DESCRIPTION
  181. "The human readable description of the purpose of this
  182. scheduling entry."
  183. DEFVAL { "" }
  184. ::= { schedEntry 3 }
  185. schedInterval OBJECT-TYPE
  186. SYNTAX Unsigned32
  187. UNITS "seconds"
  188. MAX-ACCESS read-create
  189. STATUS current
  190. DESCRIPTION
  191. "The number of seconds between two action invocations of
  192. a periodic scheduler. Implementations must guarantee
  193. that action invocations will not occur before at least
  194. schedInterval seconds have passed.
  195. The scheduler must ignore all periodic schedules that
  196. have a schedInterval value of 0. A periodic schedule
  197. with a scheduling interval of 0 seconds will therefore
  198. never invoke an action.
  199. Implementations may be forced to delay invocations in the
  200. face of local constraints. A scheduled management function
  201. should therefore not rely on the accuracy provided by the
  202. scheduler implementation.
  203. Note that implementations which maintain a list of pending
  204. activations must re-calculate them when this object is
  205. changed."
  206. DEFVAL { 0 }
  207. ::= { schedEntry 4 }
  208. schedWeekDay OBJECT-TYPE
  209. SYNTAX BITS {
  210. sunday(0),
  211. monday(1),
  212. tuesday(2),
  213. wednesday(3),
  214. thursday(4),
  215. friday(5),
  216. saturday(6)
  217. }
  218. MAX-ACCESS read-create
  219. STATUS current
  220. DESCRIPTION
  221. "The set of weekdays on which the scheduled action should
  222. take place. Setting multiple bits will include several
  223. weekdays in the set of possible weekdays for this schedule.
  224. Setting all bits will cause the scheduler to ignore the
  225. weekday.
  226. Note that implementations which maintain a list of pending
  227. activations must re-calculate them when this object is
  228. changed."
  229. DEFVAL { {} }
  230. ::= { schedEntry 5 }
  231. schedMonth OBJECT-TYPE
  232. SYNTAX BITS {
  233. january(0),
  234. february(1),
  235. march(2),
  236. april(3),
  237. may(4),
  238. june(5),
  239. july(6),
  240. august(7),
  241. september(8),
  242. october(9),
  243. november(10),
  244. december(11)
  245. }
  246. MAX-ACCESS read-create
  247. STATUS current
  248. DESCRIPTION
  249. "The set of months during which the scheduled action should
  250. take place. Setting multiple bits will include several
  251. months in the set of possible months for this schedule.
  252. Setting all bits will cause the scheduler to ignore the
  253. month.
  254. Note that implementations which maintain a list of pending
  255. activations must re-calculate them when this object is
  256. changed."
  257. DEFVAL { {} }
  258. ::= { schedEntry 6 }
  259. schedDay OBJECT-TYPE
  260. SYNTAX BITS {
  261. d1(0), d2(1), d3(2), d4(3), d5(4),
  262. d6(5), d7(6), d8(7), d9(8), d10(9),
  263. d11(10), d12(11), d13(12), d14(13), d15(14),
  264. d16(15), d17(16), d18(17), d19(18), d20(19),
  265. d21(20), d22(21), d23(22), d24(23), d25(24),
  266. d26(25), d27(26), d28(27), d29(28), d30(29),
  267. d31(30),
  268. r1(31), r2(32), r3(33), r4(34), r5(35),
  269. r6(36), r7(37), r8(38), r9(39), r10(40),
  270. r11(41), r12(42), r13(43), r14(44), r15(45),
  271. r16(46), r17(47), r18(48), r19(49), r20(50),
  272. r21(51), r22(52), r23(53), r24(54), r25(55),
  273. r26(56), r27(57), r28(58), r29(59), r30(60),
  274. r31(61)
  275. }
  276. MAX-ACCESS read-create
  277. STATUS current
  278. DESCRIPTION
  279. "The set of days in a month on which a scheduled action
  280. should take place. There are two sets of bits one can
  281. use to define the day within a month:
  282. Enumerations starting with the letter 'd' indicate a
  283. day in a month relative to the first day of a month.
  284. The first day of the month can therefore be specified
  285. by setting the bit d1(0) and d31(30) means the last
  286. day of a month with 31 days.
  287. Enumerations starting with the letter 'r' indicate a
  288. day in a month in reverse order, relative to the last
  289. day of a month. The last day in the month can therefore
  290. be specified by setting the bit r1(31) and r31(61) means
  291. the first day of a month with 31 days.
  292. Setting multiple bits will include several days in the set
  293. of possible days for this schedule. Setting all bits will
  294. cause the scheduler to ignore the day within a month.
  295. Setting all bits starting with the letter 'd' or the
  296. letter 'r' will also cause the scheduler to ignore the
  297. day within a month.
  298. Note that implementations which maintain a list of pending
  299. activations must re-calculate them when this object is
  300. changed."
  301. DEFVAL { {} }
  302. ::= { schedEntry 7 }
  303. schedHour OBJECT-TYPE
  304. SYNTAX BITS {
  305. h0(0), h1(1), h2(2), h3(3), h4(4),
  306. h5(5), h6(6), h7(7), h8(8), h9(9),
  307. h10(10), h11(11), h12(12), h13(13), h14(14),
  308. h15(15), h16(16), h17(17), h18(18), h19(19),
  309. h20(20), h21(21), h22(22), h23(23)
  310. }
  311. MAX-ACCESS read-create
  312. STATUS current
  313. DESCRIPTION
  314. "The set of hours within a day during which the scheduled
  315. action should take place.
  316. Note that implementations which maintain a list of pending
  317. activations must re-calculate them when this object is
  318. changed."
  319. DEFVAL { {} }
  320. ::= { schedEntry 8 }
  321. schedMinute OBJECT-TYPE
  322. SYNTAX BITS {
  323. m0(0), m1(1), m2(2), m3(3), m4(4),
  324. m5(5), m6(6), m7(7), m8(8), m9(9),
  325. m10(10), m11(11), m12(12), m13(13), m14(14),
  326. m15(15), m16(16), m17(17), m18(18), m19(19),
  327. m20(20), m21(21), m22(22), m23(23), m24(24),
  328. m25(25), m26(26), m27(27), m28(28), m29(29),
  329. m30(30), m31(31), m32(32), m33(33), m34(34),
  330. m35(35), m36(36), m37(37), m38(38), m39(39),
  331. m40(40), m41(41), m42(42), m43(43), m44(44),
  332. m45(45), m46(46), m47(47), m48(48), m49(49),
  333. m50(50), m51(51), m52(52), m53(53), m54(54),
  334. m55(55), m56(56), m57(57), m58(58), m59(59)
  335. }
  336. MAX-ACCESS read-create
  337. STATUS current
  338. DESCRIPTION
  339. "The set of minutes within an hour when the scheduled action
  340. should take place.
  341. Note that implementations which maintain a list of pending
  342. activations must re-calculate them when this object is
  343. changed."
  344. DEFVAL { {} }
  345. ::= { schedEntry 9 }
  346. schedContextName OBJECT-TYPE
  347. SYNTAX SnmpAdminString (SIZE(0..32))
  348. MAX-ACCESS read-create
  349. STATUS current
  350. DESCRIPTION
  351. "The context which contains the local MIB variable pointed
  352. to by schedVariable."
  353. DEFVAL { "" }
  354. ::= { schedEntry 10 }
  355. schedVariable OBJECT-TYPE
  356. SYNTAX VariablePointer
  357. MAX-ACCESS read-create
  358. STATUS current
  359. DESCRIPTION
  360. "An object identifier pointing to a local MIB variable
  361. which resolves to an ASN.1 primitive type of INTEGER."
  362. DEFVAL { zeroDotZero }
  363. ::= { schedEntry 11 }
  364. schedValue OBJECT-TYPE
  365. SYNTAX Integer32
  366. MAX-ACCESS read-create
  367. STATUS current
  368. DESCRIPTION
  369. "The value which is written to the MIB object pointed to by
  370. schedVariable when the scheduler invokes an action. The
  371. implementation shall enforce the use of access control
  372. rules when performing the set operation on schedVariable.
  373. This is accomplished by calling the isAccessAllowed abstract
  374. service interface as defined in RFC 2571.
  375. Note that an implementation may choose to issue an SNMP Set
  376. message to the SNMP engine and leave the access control
  377. decision to the normal message processing procedure."
  378. DEFVAL { 0 }
  379. ::= { schedEntry 12 }
  380. schedType OBJECT-TYPE
  381. SYNTAX INTEGER {
  382. periodic(1),
  383. calendar(2),
  384. oneshot(3)
  385. }
  386. MAX-ACCESS read-create
  387. STATUS current
  388. DESCRIPTION
  389. "The type of this schedule. The value periodic(1) indicates
  390. that this entry specifies a periodic schedule. A periodic
  391. schedule is defined by the value of schedInterval. The
  392. values of schedWeekDay, schedMonth, schedDay, schedHour
  393. and schedMinute are ignored.
  394. The value calendar(2) indicates that this entry describes a
  395. calendar schedule. A calendar schedule is defined by the
  396. values of schedWeekDay, schedMonth, schedDay, schedHour and
  397. schedMinute. The value of schedInterval is ignored. A
  398. calendar schedule will trigger on all local times that
  399. satisfy the bits set in schedWeekDay, schedMonth, schedDay,
  400. schedHour and schedMinute.
  401. The value oneshot(3) indicates that this entry describes a
  402. one-shot schedule. A one-shot schedule is similar to a
  403. calendar schedule with the additional feature that it
  404. disables itself by changing in the `finished'
  405. schedOperStatus once the schedule triggers an action.
  406. Note that implementations which maintain a list of pending
  407. activations must re-calculate them when this object is
  408. changed."
  409. DEFVAL { periodic }
  410. ::= { schedEntry 13 }
  411. schedAdminStatus OBJECT-TYPE
  412. SYNTAX INTEGER {
  413. enabled(1),
  414. disabled(2)
  415. }
  416. MAX-ACCESS read-create
  417. STATUS current
  418. DESCRIPTION
  419. "The desired state of the schedule."
  420. DEFVAL { disabled }
  421. ::= { schedEntry 14 }
  422. schedOperStatus OBJECT-TYPE
  423. SYNTAX INTEGER {
  424. enabled(1),
  425. disabled(2),
  426. finished(3)
  427. }
  428. MAX-ACCESS read-only
  429. STATUS current
  430. DESCRIPTION
  431. "The current operational state of this schedule. The state
  432. enabled(1) indicates this entry is active and that the
  433. scheduler will invoke actions at appropriate times. The
  434. disabled(2) state indicates that this entry is currently
  435. inactive and ignored by the scheduler. The finished(3)
  436. state indicates that the schedule has ended. Schedules
  437. in the finished(3) state are ignored by the scheduler.
  438. A one-shot schedule enters the finished(3) state when it
  439. deactivates itself.
  440. Note that the operational state must not be enabled(1)
  441. when the schedRowStatus is not active."
  442. ::= { schedEntry 15 }
  443. schedFailures OBJECT-TYPE
  444. SYNTAX Counter32
  445. MAX-ACCESS read-only
  446. STATUS current
  447. DESCRIPTION
  448. "This variable counts the number of failures while invoking
  449. the scheduled action. This counter at most increments once
  450. for a triggered action."
  451. ::= { schedEntry 16 }
  452. schedLastFailure OBJECT-TYPE
  453. SYNTAX SnmpPduErrorStatus
  454. MAX-ACCESS read-only
  455. STATUS current
  456. DESCRIPTION
  457. "The most recent error that occurred during the invocation of
  458. a scheduled action. The value noError(0) is returned
  459. if no errors have occurred yet."
  460. DEFVAL { noError }
  461. ::= { schedEntry 17 }
  462. schedLastFailed OBJECT-TYPE
  463. SYNTAX DateAndTime
  464. MAX-ACCESS read-only
  465. STATUS current
  466. DESCRIPTION
  467. "The date and time when the most recent failure occurred.
  468. The value '0000000000000000'H is returned if no failure
  469. occurred since the last re-initialization of the scheduler."
  470. DEFVAL { '0000000000000000'H }
  471. ::= { schedEntry 18 }
  472. schedStorageType OBJECT-TYPE
  473. SYNTAX StorageType
  474. MAX-ACCESS read-create
  475. STATUS current
  476. DESCRIPTION
  477. "This object defines whether this scheduled action is kept
  478. in volatile storage and lost upon reboot or if this row is
  479. backed up by non-volatile or permanent storage.
  480. Conceptual rows having the value `permanent' must allow
  481. write access to the columnar objects schedDescr,
  482. schedInterval, schedContextName, schedVariable, schedValue,
  483. and schedAdminStatus. If an implementation supports the
  484. schedCalendarGroup, write access must be also allowed to
  485. the columnar objects schedWeekDay, schedMonth, schedDay,
  486. schedHour, schedMinute."
  487. DEFVAL { volatile }
  488. ::= { schedEntry 19 }
  489. schedRowStatus OBJECT-TYPE
  490. SYNTAX RowStatus
  491. MAX-ACCESS read-create
  492. STATUS current
  493. DESCRIPTION
  494. "The status of this scheduled action. A control that allows
  495. entries to be added and removed from this table.
  496. Note that the operational state must change to enabled
  497. when the administrative state is enabled and the row
  498. status changes to active(1).
  499. Attempts to destroy(6) a row or to set a row
  500. notInService(2) while the operational state is enabled
  501. result in inconsistentValue errors.
  502. The value of this object has no effect on whether other
  503. objects in this conceptual row can be modified."
  504. ::= { schedEntry 20 }
  505. schedTriggers OBJECT-TYPE
  506. SYNTAX Counter32
  507. MAX-ACCESS read-only
  508. STATUS current
  509. DESCRIPTION
  510. "This variable counts the number of attempts (either
  511. successful or failed) to invoke the scheduled action."
  512. ::= { schedEntry 21 }
  513. --
  514. -- Notifications that are emitted to indicate failures. The
  515. -- definition of schedTraps makes notification registrations
  516. -- reversible (see STD 58, RFC 2578).
  517. --
  518. schedTraps OBJECT IDENTIFIER ::= { schedNotifications 0 }
  519. schedActionFailure NOTIFICATION-TYPE
  520. OBJECTS { schedLastFailure, schedLastFailed }
  521. STATUS current
  522. DESCRIPTION
  523. "This notification is generated whenever the invocation of a
  524. scheduled action fails."
  525. ::= { schedTraps 1 }
  526. -- conformance information
  527. schedCompliances OBJECT IDENTIFIER ::= { schedConformance 1 }
  528. schedGroups OBJECT IDENTIFIER ::= { schedConformance 2 }
  529. -- compliance statements
  530. schedCompliance2 MODULE-COMPLIANCE
  531. STATUS current
  532. DESCRIPTION
  533. "The compliance statement for SNMP entities which implement
  534. the scheduling MIB."
  535. MODULE -- this module
  536. MANDATORY-GROUPS {
  537. schedGroup2, schedNotificationsGroup
  538. }
  539. GROUP schedCalendarGroup
  540. DESCRIPTION
  541. "The schedCalendarGroup is mandatory only for those
  542. implementations that support calendar based schedules."
  543. OBJECT schedType
  544. DESCRIPTION
  545. "The values calendar(2) or oneshot(3) are not valid for
  546. implementations that do not implement the
  547. schedCalendarGroup. Such an implementation must return
  548. inconsistentValue error responses for attempts to set
  549. schedAdminStatus to calendar(2) or oneshot(3)."
  550. ::= { schedCompliances 2 }
  551. schedGroup2 OBJECT-GROUP
  552. OBJECTS {
  553. schedDescr, schedInterval, schedContextName,
  554. schedVariable, schedValue, schedType,
  555. schedAdminStatus, schedOperStatus, schedFailures,
  556. schedLastFailure, schedLastFailed, schedStorageType,
  557. schedRowStatus, schedTriggers
  558. }
  559. STATUS current
  560. DESCRIPTION
  561. "A collection of objects providing scheduling capabilities."
  562. ::= { schedGroups 4 }
  563. schedCalendarGroup OBJECT-GROUP
  564. OBJECTS {
  565. schedLocalTime, schedWeekDay, schedMonth,
  566. schedDay, schedHour, schedMinute
  567. }
  568. STATUS current
  569. DESCRIPTION
  570. "A collection of objects providing calendar based schedules."
  571. ::= { schedGroups 2 }
  572. schedNotificationsGroup NOTIFICATION-GROUP
  573. NOTIFICATIONS {
  574. schedActionFailure
  575. }
  576. STATUS current
  577. DESCRIPTION
  578. "The notifications emitted by the scheduler."
  579. ::= { schedGroups 3 }
  580. --
  581. -- Deprecated compliance and conformance group definitions
  582. -- from RFC 2591.
  583. --
  584. schedCompliance MODULE-COMPLIANCE
  585. STATUS deprecated
  586. DESCRIPTION
  587. "The compliance statement for SNMP entities which implement
  588. the scheduling MIB."
  589. MODULE -- this module
  590. MANDATORY-GROUPS {
  591. schedGroup, schedNotificationsGroup
  592. }
  593. GROUP schedCalendarGroup
  594. DESCRIPTION
  595. "The schedCalendarGroup is mandatory only for those
  596. implementations that support calendar based schedules."
  597. OBJECT schedType
  598. DESCRIPTION
  599. "The values calendar(2) or oneshot(3) are not valid for
  600. implementations that do not implement the
  601. schedCalendarGroup. Such an implementation must return
  602. inconsistentValue error responses for attempts to set
  603. schedAdminStatus to calendar(2) or oneshot(3)."
  604. ::= { schedCompliances 1 }
  605. schedGroup OBJECT-GROUP
  606. OBJECTS {
  607. schedDescr, schedInterval, schedContextName,
  608. schedVariable, schedValue, schedType,
  609. schedAdminStatus, schedOperStatus, schedFailures,
  610. schedLastFailure, schedLastFailed, schedStorageType,
  611. schedRowStatus
  612. }
  613. STATUS deprecated
  614. DESCRIPTION
  615. "A collection of objects providing scheduling capabilities."
  616. ::= { schedGroups 1 }
  617. END