For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Don_22992's avatar
Don_22992
Icon for Nimbostratus rankNimbostratus
Jan 28, 2008

Email notification of node/vs down

I have searched for a while now, and have not found a solution.     Alertd appears to be the method of sending an email alert; how do I tell it a node is down?     Or a custom scripted mon...
config
design
aygitci_128716's avatar
aygitci_128716
Icon for Nimbostratus rankNimbostratus
Feb 22, 2018

Hi All

Despite the syntax used from the document K3667, I have the error ' Feb 22 19:47:42 localhost emerg logger: Re-starting alertd'.

The error is looping. I have to copy an empty user_alert.conf file in order to stop it.

Below the conf added into file /config/user_alert.conf with the rights 644: 
alert BIGIP_LIBHAL_HALERR_BLADE_POWERED_OFF {  
    snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.119";  
    lcdwarn description="Blade is about to be powered off." priority="4"  
    email toaddress="..."  
    fromaddress="..."  
    body="The test of this Solution worked!"  
}

Thanks for help

  • Kevin_K_51432's avatar
    Kevin_K_51432
    Historic F5 Account
    Feb 22, 2018

    Greeting,

    I took a quick peek at the article and didn't notice any mention of lcdwarn or description.

    I removed those and it's working:

    alert BIGIP_LIBHAL_HALERR_BLADE_POWERED_OFF {  
    snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.119";  
    email toaddress="..."  
    fromaddress="..."  
    body="The test of this Solution worked!"  
}

    Hopefully those aren't necessary for you?

    Kevin
  • aygitci_128716's avatar
    aygitci_128716
    Icon for Nimbostratus rankNimbostratus
    Feb 23, 2018

    Thanks for your reply. Yes it's working now.

     

    However I didn't receive the email. I'm wondering if I didn't choose the right SNMP OID.

     

    Do you know on where I can find the triggered OID?

     

    Thanks again :)

     

  • Kevin_K_51432's avatar
    Kevin_K_51432
    Historic F5 Account
    Feb 23, 2018

    Sure thing!

     

    So, internally, TMM is picking this message up "BIGIP_LIBHAL_HALERR_BLADE_POWERED_OFF".

     

    Then it sends the trap with that OID. You could type anything in actually.

     

    Have you following this article for configuring the SMTP mailhub on BIG-IP?

     

    https://support.f5.com/csp/article/K13180

     

    Lastly, if you are using domain names, have you set up a DNS name server on BIG-IP?

     

    Thanks,

     

    Kevin

     

  • Kevin_K_51432's avatar
    Kevin_K_51432
    Historic F5 Account
    Feb 23, 2018

    Also, you should be able to test with the following from the BIG-IP advanced shell (bash):

     

    logger -p local0.emerg "012a0012:0: Blade 2 is about to be powered off!"

     

  • aygitci_128716's avatar
    aygitci_128716
    Icon for Nimbostratus rankNimbostratus
    Feb 26, 2018

    Hi Kevin. Thanks for feedback.

     

    I already configured SMTP via WebGUI but not helped.

     

    As you advised I configured SMTP mailhub (DNS was already done).

     

    Alert by email is working now.

     

  • Kevin_K_51432's avatar
    Kevin_K_51432
    Historic F5 Account
    Feb 26, 2018

    The UI and CLI represent two different SMTP instances on BIG-IP. It's odd and I hope they fix that in the future.

     

    Glad this is working for you and thanks for letting us know!