Forum Discussion

Patrick_Chang_7's avatar
Patrick_Chang_7
Historic F5 Account
Jun 06, 2008

send e-mail on only some pool members down

I have the following user_alert.conf (version 9.4.2 228.18)

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP "Pool member 172.29.4.141:80

 

monitor status up." {

 

email toaddress="p.chang@f5.com"

 

fromaddress="root@vanguard.f5.com"

 

body="pool member went up"

 

}

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS "Pool member 172.29.4.141:80 mon

 

itor status down." {

 

email toaddress="p.chang@f5.com"

 

fromaddress="root@vanguard.f5.com"

 

body="pool member went down"

 

}

 

 

I only want to receive e-mails when Pool member 172.29.4.141:80 goes up or down. However, I get e-mails when any pool member goes up or down. How do I set up the alert for specific pool members?

13 Replies

  • You should be able to create a custom SNMP trap using this format:

     

     

    https://support.f5.com/kb/en-us/solutions/public/3000/700/sol3727.html?sr=826826

     

     

    alert "" {

     

    snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.XXX"

     

    }

     

     

    If you change BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS to something that's not the same as the default alert name, do you get the email notification only for that specific node?

     

     

    Aaron
  • Patrick_Chang_7's avatar
    Patrick_Chang_7
    Historic F5 Account
    I changed it like it said in the to the following:

     

    alert BIGIP_MCPD_CUSTOM_POOL_MEMBER_MON_STATUS_UP "Pool member 172.29.4.141:80 monitor status up." {

     

    snmptrap OID= ".1.3.6.1.4.1.3375.2.4.0.998";

     

    email toaddress="p.chang@f5.com"

     

    fromaddress="root@vanguard.f5.com"

     

    body="pool member went up"

     

    }

     

    alert BIGIP_MCPD_CUSTOM_POOL_MEMBER_MON_STATUS_DOWN "Pool member 172.29.4.141:80 monitor status down." {

     

    snmptrap OID= ".1.3.6.1.4.1.3375.2.4.0.999";

     

    email toaddress="p.chang@f5.com"

     

    fromaddress="root@vanguard.f5.com"

     

    body="pool member went down"

     

    }

     

     

    Now, I don't get any e-mails.

     

     

  • Hello

     

     

    personal

     

     

    I need help.

     

     

    My motificaçao shipping configuration is okay, I am getting only the status donw like me to receive the status Faso UP?, Because if he tells me fell node node status donw but if the node back up he did not inform me, I would like receiving node UP status of this how?
  • Hello

     

     

    personal

     

     

    I need help.

     

     

    My motificaçao shipping configuration is okay, I am getting only the status donw like me to receive the status Faso UP?, Because if he tells me fell node node status donw but if the node back up he did not inform me, I would like receiving node UP status of this how?
  • this is mine.

    [root@iris:Active] config  cat user_alert.conf
    alert CUSTOM_POOL_MEMBER_MON_STATUS_UP "Pool member 10.10.70.110:80 monitor status up." {
    email toaddress="xxxxx"
    fromaddress="root@bigip.ss.lab.f5.com"
    body="pool member went up"
    }
    alert CUSTOM_POOL_MEMBER_MON_STATUS_DOWN "Pool member 10.10.70.110:80 monitor status down." {
    email toaddress="xxxxx"
    fromaddress="root@bigip.ss.lab.f5.com"
    body="pool member went down"
    }
    
    [root@iris:Active] config  bigstart status postfix
    master (pid 7701) is running...
    
    [root@iris:Active] config  postconf -n
    alias_database = hash:/etc/aliases
    alias_maps = hash:/etc/aliases
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    daemon_directory = /usr/libexec/postfix
    debug_peer_level = 2
    html_directory = no
    inet_interfaces = localhost
    mail_owner = postfix
    mailq_path = /usr/bin/mailq.postfix
    manpage_directory = /usr/share/man
    mydestination = $myhostname, localhost.$mydomain, localhost
    newaliases_path = /usr/bin/newaliases.postfix
    queue_directory = /var/spool/postfix
    readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
    relayhost = [192.168.10.13]
    sample_directory = /usr/share/doc/postfix-2.3.3/samples
    sendmail_path = /usr/sbin/sendmail.postfix
    setgid_group = postdrop
    unknown_local_recipient_reject_code = 550
    
    [root@iris:Active] config  grep -i 10.10.70.110 /var/log/ltm
    Nov  3 02:23:12 local/iris notice mcpd[32723]: 01070638:5: Pool member 10.10.70.110:80 monitor status down.
    Nov  3 02:23:41 local/iris notice mcpd[32723]: 01070727:5: Pool member 10.10.70.110:80 monitor status up.
    
    -----Original Message-----
    From: root@bigip.ss.lab.f5.com [mailto:root@bigip.ss.lab.f5.com] 
    Sent: Thursday, November 03, 2011 2:23 AM
    To: xxxxx
    Subject: 01070638:5: Pool member 10.10.70.110:80 monitor status down.
    
    pool member went down
    
    -----Original Message-----
    From: root@bigip.ss.lab.f5.com [mailto:root@bigip.ss.lab.f5.com] 
    Sent: Thursday, November 03, 2011 2:24 AM
    To: xxxxx
    Subject: 01070727:5: Pool member 10.10.70.110:80 monitor status up.
    
    pool member went up
    
  • this is mine.

    [root@iris:Active] config  cat user_alert.conf
    alert CUSTOM_POOL_MEMBER_MON_STATUS_UP "Pool member 10.10.70.110:80 monitor status up." {
    email toaddress="xxxxx"
    fromaddress="root@bigip.ss.lab.f5.com"
    body="pool member went up"
    }
    alert CUSTOM_POOL_MEMBER_MON_STATUS_DOWN "Pool member 10.10.70.110:80 monitor status down." {
    email toaddress="xxxxx"
    fromaddress="root@bigip.ss.lab.f5.com"
    body="pool member went down"
    }
    
    [root@iris:Active] config  bigstart status postfix
    master (pid 7701) is running...
    
    [root@iris:Active] config  postconf -n
    alias_database = hash:/etc/aliases
    alias_maps = hash:/etc/aliases
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    daemon_directory = /usr/libexec/postfix
    debug_peer_level = 2
    html_directory = no
    inet_interfaces = localhost
    mail_owner = postfix
    mailq_path = /usr/bin/mailq.postfix
    manpage_directory = /usr/share/man
    mydestination = $myhostname, localhost.$mydomain, localhost
    newaliases_path = /usr/bin/newaliases.postfix
    queue_directory = /var/spool/postfix
    readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
    relayhost = [192.168.10.13]
    sample_directory = /usr/share/doc/postfix-2.3.3/samples
    sendmail_path = /usr/sbin/sendmail.postfix
    setgid_group = postdrop
    unknown_local_recipient_reject_code = 550
    
    [root@iris:Active] config  grep -i 10.10.70.110 /var/log/ltm
    Nov  3 02:23:12 local/iris notice mcpd[32723]: 01070638:5: Pool member 10.10.70.110:80 monitor status down.
    Nov  3 02:23:41 local/iris notice mcpd[32723]: 01070727:5: Pool member 10.10.70.110:80 monitor status up.
    
    -----Original Message-----
    From: root@bigip.ss.lab.f5.com [mailto:root@bigip.ss.lab.f5.com] 
    Sent: Thursday, November 03, 2011 2:23 AM
    To: xxxxx
    Subject: 01070638:5: Pool member 10.10.70.110:80 monitor status down.
    
    pool member went down
    
    -----Original Message-----
    From: root@bigip.ss.lab.f5.com [mailto:root@bigip.ss.lab.f5.com] 
    Sent: Thursday, November 03, 2011 2:24 AM
    To: xxxxx
    Subject: 01070727:5: Pool member 10.10.70.110:80 monitor status up.
    
    pool member went up
    
  • Patrick,

     

     

    "BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP" and "BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS" are system pre-defined "alert names" (see /etc/alertd/bigip_mcpd_error_maps.h).

     

     

    I'm not sure if it's a good idea to re-define those in user_alert.conf. Better use another alert_name, as described by nitass (CUSTOM_POOL_MEMBER_MON_STATUS_DOWN).

     

     

    Regards

     

    Kurt Knochner
  • Hello

     

     

    personal

     

     

    I need help.

     

     

    My motificaçao shipping configuration is okay, I am getting only the status donw like me to receive the status Faso UP?, Because if he tells me fell node node status donw but if the node back up he did not inform me, I would like receiving node UP status of this how?