Wired Intelligent Edge

 View Only
  • 1.  Aruba CX: schedule count does not work / reset after reboot

    Posted Dec 08, 2023 02:47 AM
    Edited by r.grossmann Dec 15, 2023 02:23 PM

    I tried the job and schedule function, but if the job contains a reboot, the scheduler max trigger count option does not work or is getting resetted.
    Is this a bug or a feature?
    For my opinion the schedule count should be fix, so that after a reboot the counter is as before.

    For example I use max trigger count of 1 in the scheduler.
    But the job reboot has executed more than 1, as you can see every 7 days but not limited to max trigger count 1.

    job reboot
        10 cli boot system

    schedule reboot
        10 job reboot
        trigger every days 7 count 1 start 16:15 2023-11-16

    vw-2og-b221# sh logg -a -r |i reboot
    2023-12-07T15:20:20.881322+00:00 6100 schedulerd[2468]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-12-14 16:15, with period: 7 days
    2023-12-07T15:18:05.250577+00:00 6100 crash-tools[325]: Event|1206|LOG_CRIT|||Module rebooted. Reason : Reboot requested by user, Version: PL.10.10.1090#012, Boot-ID : a2c6ea514f7f4bbab79c671200e1644f
    2023-12-07T16:15:27.773683+01:00 vw-2og-b221 hpe-mgmtmd[676]: Event|706|LOG_INFO|AMM|1/1|Initiating system reboot
    2023-12-07T16:15:06.089496+01:00 vw-2og-b221 job-mgmtd[2462]: Event|13701|LOG_INFO|AMM|1/1|Starting Job reboot due to Schedule reboot's trigger
    2023-12-07T16:15:06.001297+01:00 vw-2og-b221 schedulerd[2480]: Event|12202|LOG_INFO|AMM|1/1|Schedule reboot triggered, trigger_count: 1
    2023-11-30T15:20:17.246904+00:00 6100 schedulerd[2480]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-12-7 16:15, with period: 7 days
    2023-11-30T15:18:04.547121+00:00 6100 crash-tools[328]: Event|1206|LOG_CRIT|||Module rebooted. Reason : Reboot requested by user, Version: PL.10.10.1090#012, Boot-ID : 18ff5224de804ae6b94ea005a77fddc0
    2023-11-30T16:15:24.780909+01:00 vw-2og-b221 hpe-mgmtmd[669]: Event|706|LOG_INFO|AMM|1/1|Initiating system reboot
    2023-11-30T16:15:02.423749+01:00 vw-2og-b221 job-mgmtd[2465]: Event|13701|LOG_INFO|AMM|1/1|Starting Job reboot due to Schedule reboot's trigger
    2023-11-30T16:15:02.304359+01:00 vw-2og-b221 schedulerd[2481]: Event|12202|LOG_INFO|AMM|1/1|Schedule reboot triggered, trigger_count: 1
    2023-11-23T15:20:40.713149+00:00 6100 schedulerd[2481]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-11-30 16:15, with period: 7 days
    2023-11-23T15:18:26.996932+00:00 6100 crash-tools[325]: Event|1206|LOG_CRIT|||Module rebooted. Reason : Reboot requested by user, Version: PL.10.10.1090#012, Boot-ID : 00cc519133444d72b2cbfa6e702ec622
    2023-11-23T16:15:51.067991+01:00 vw-2og-b221 hpe-mgmtmd[672]: Event|706|LOG_INFO|AMM|1/1|Initiating system reboot
    2023-11-23T16:15:02.603802+01:00 vw-2og-b221 job-mgmtd[2457]: Event|13701|LOG_INFO|AMM|1/1|Starting Job reboot due to Schedule reboot's trigger
    2023-11-23T16:15:02.506866+01:00 vw-2og-b221 schedulerd[2472]: Event|12202|LOG_INFO|AMM|1/1|Schedule reboot triggered, trigger_count: 1
    2023-11-16T15:21:10.952382+00:00 6100 schedulerd[2472]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-11-23 16:15, with period: 7 days
    2023-11-16T15:18:56.920709+00:00 6100 crash-tools[328]: Event|1206|LOG_CRIT|||Module rebooted. Reason : Reboot requested by user, Version: PL.10.10.1090#012, Boot-ID : cb26440153df4bb6acf34920ced98726
    2023-11-16T16:15:43.540026+01:00 vw-2og-b221 hpe-mgmtmd[669]: Event|706|LOG_INFO|AMM|1/1|Initiating system reboot
    2023-11-16T16:15:02.455873+01:00 vw-2og-b221 job-mgmtd[2454]: Event|13701|LOG_INFO|AMM|1/1|Starting Job reboot due to Schedule reboot's trigger
    2023-11-16T16:15:02.316058+01:00 vw-2og-b221 schedulerd[2474]: Event|12202|LOG_INFO|AMM|1/1|Schedule reboot triggered, trigger_count: 1
    2023-11-16T16:06:36.842979+01:00 vw-2og-b221 schedulerd[2474]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-11-16 16:15, with period: 7 days
    2023-11-16T16:05:40.668623+01:00 vw-2og-b221 schedulerd[2474]: Event|12201|LOG_INFO|AMM|1/1|Creating schedule reboot, trigger time(s): 2023-11-16 16:15, with period: 7 days
    2023-10-10T15:40:42.325243+00:00 6100 crash-tools[326]: Event|1206|LOG_CRIT|||Module rebooted. Reason : Reboot requested by user, Version: PL.10.10.1080#012, Boot-ID : a2937661ea4c4dfdb88fbc1f6a84c125
    vw-2og-b221#



  • 2.  RE: Aruba CX: schedule count does not work / reset after reboot

    Posted Feb 09, 2024 05:49 AM

    push




  • 3.  RE: Aruba CX: schedule count does not work / reset after reboot

    Posted Feb 12, 2024 04:53 AM

    Count in general is not persistent across reboot. This is not a bug ,it is designed to be so. Reboot scheduler with persistent count should be considered as enhancement request. If your switch is managed by a NMS , NMS will be able to schedule the reboots as well . 



    ------------------------------
    Shobana
    Aruba
    ------------------------------