Forum Discussion

lipos_54863's avatar
lipos_54863
Icon for Nimbostratus rankNimbostratus
Jun 24, 2010

iRule affecting node state

Hi,

 

 

I need to reboot servers every 4 hours and drain the connecting before a reboot.

 

I'm thinking about an iRule that will be triggered every 4 hours and reboot disable a node 10mins before a reboot.

 

 

I think that a script running on some external server using iControl should take care of the problem, but if you have any other easy suggestions, please let me know.

 

 

Regards,

 

 

Martin

 

 

config
design

4 Replies

Sort By
  • Chris_Miller's avatar
    Chris_Miller
    Icon for Altostratus rankAltostratus
    Jun 24, 2010
    I haven't done much in linux land for awhile - but couldn't you just make a cronjob that runs on the F5 to handle this? You'd make a script to issue the node down command and to ssh into the servers to reboot them - You could just schedule that job to run every 4 hours...with the 10 minutes in between...
  • lipos_54863's avatar
    lipos_54863
    Icon for Nimbostratus rankNimbostratus
    Jun 24, 2010
    True, but our policy says that we can't do things like that on the F5s.

     

    Meaning handle something that is not supported directly by the F5s.

     

    I know that sounds funny, but they are just too important for us.

     

     

    Really good point though.

     

    I guess this is the easiest solution so far.
  • Philippe_CLOUP's avatar
    Philippe_CLOUP
    Icon for Employee rankEmployee
    Jun 24, 2010
    Hi martin, your solution seems to be the "state of the art" solution for that. You can probably imagine adding monitors to your node, that can put the node DOWN, but this will not have exactly the impact you are expecting ;-) /Phil
  • Chris_Miller's avatar
    Chris_Miller
    Icon for Altostratus rankAltostratus
    Jun 24, 2010
    Posted By lipos on 06/24/2010 10:51 AM

     

    True, but our policy says that we can't do things like that on the F5s.

     

    Meaning handle something that is not supported directly by the F5s.

     

    I know that sounds funny, but they are just too important for us.

     

     

    Really good point though.

     

    I guess this is the easiest solution so far.

     

     

    It wouldn't have to run on the F5s...it could run on another linux box too, provided you don't mind storing login credentials to a critical system in a file.