Network Management

last person joined: 2 days ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Back to discussions
Expand all | Collapse all

Airwave won't do Configuration Change Jobs for periodic reboots every 3 months.

This thread has been viewed 0 times

  • 1.  Airwave won't do Configuration Change Jobs for periodic reboots every 3 months.

    Posted Mar 24, 2020 03:48 PM
      |   view attached

    I've configured a batch of switches to reboot every 3 months on the second Saturday of that month but it simply won't reboot.

     

    All switches are in Monitoring + Firmware updates only but I have enabled the "Allow Rebooting Monitor Only APs/Devices" setting under Firmware upgrade/reboot option. 

    Setting the Desired Start Date option for a time before or on the date I want it to restart (2nd saturday every 3 months at 3am) doesn't seem to do anything either as the switches simply won't reboot.

    If I set the Change Job to occur One Time and set a specific date and time, it does reboot just fine. I changed it to the third Saturday of the month to test it and it didn't do it. Now I changed it to the forth but I'm not confident it will do either. 

    We are running Airwave 8.2.6

     

    What could I be missing here? 

     

     



  • 2.  RE: Airwave won't do Configuration Change Jobs for periodic reboots every 3 months.

    EMPLOYEE
    Posted Mar 25, 2020 07:11 AM

    We need to check device telnet logs to find whether Airwave have sent reboot command to switches.

     

    You can download diagnostic.tar.gz file from AMPCLI or system status page and look for that specific Switch ID log, you can get id of switch from Devices>Monitor page URL of switch in Airwave.

     

    If Airwave sent reboot command but switch didn't responded then its switch issue but if Airwave itself didn't triggered command then its a defect.

     

    since server is in old 8.2.6 code, I would recommend to upgrade server to latest 8.2.10.1 code first and check, if issue still persist then open TAC ticket to file defect, if reboot command is not initiated in telnet log.