Forum Discussion

stereo_111948's avatar
stereo_111948
Icon for Nimbostratus rankNimbostratus
Feb 20, 2015

Simplifying the editing of alert.conf on multiple devices

I'm in the process of doing email alert notifications following Sol3667: Configuring alerts to send email notifications.

 

Instead of editing all alert.conf in several BIG-IP's one by one, is it safe to edit one alert.conf, copy the file to a remote computer and paste the file to the other BIG-IP devices? The BIG-IP hardware are 3600's and 1600's. Some are running on software 11.3.0 and some are running on 11.5.1.

 

I saw some alerts intended for blades (e.g. BIGIP_SYSTEM_CHECK_E_BLADE_TEMP_HIGH_1) in the 1600 alert.conf so I was thinking that this file can be applied to any model since this alert is only applicable to the Viprion model.

 

Suggestions for simplifying the process of applying SOL3667 to multiple devices will be highly appreciated.

 

alert.conf
alerts
application delivery
LTM
management

5 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 21, 2015

    by default, /etc/alertd/alert.conf is not included in ucs. so, i think it may be better to configure /config/user_alert.conf and copy to all bigip.

     

    • stereo_111948's avatar
      stereo_111948
      Icon for Nimbostratus rankNimbostratus
      Feb 21, 2015
      Thanks Nitass. I do understand that I need to edit something in order to include the alert.conf in the ucs. My ultimate objective is to simplify the propagation of a single and edited alert.conf to all our F5 devices. Judging from your last sentence, I would like to think it's perfectly fine to: 1. Edit alert.conf on a 1600 (running on 11.5.1) to add email alerts. 2. Copy the edited alert.conf file to a laptop. 3. Upload and use it in a 3600 (running on version 11.3.0). Please correct me if I'm wrong. I worry that there might be incompatibility issues due to hardware and software differences if I do the above. Thanks in advance
  • nitass_89166's avatar
    nitass_89166
    Icon for Noctilucent rankNoctilucent
    Feb 21, 2015

    by default, /etc/alertd/alert.conf is not included in ucs. so, i think it may be better to configure /config/user_alert.conf and copy to all bigip.

     

    • stereo_111948's avatar
      stereo_111948
      Icon for Nimbostratus rankNimbostratus
      Feb 21, 2015
      Thanks Nitass. I do understand that I need to edit something in order to include the alert.conf in the ucs. My ultimate objective is to simplify the propagation of a single and edited alert.conf to all our F5 devices. Judging from your last sentence, I would like to think it's perfectly fine to: 1. Edit alert.conf on a 1600 (running on 11.5.1) to add email alerts. 2. Copy the edited alert.conf file to a laptop. 3. Upload and use it in a 3600 (running on version 11.3.0). Please correct me if I'm wrong. I worry that there might be incompatibility issues due to hardware and software differences if I do the above. Thanks in advance
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Feb 21, 2015

    what i mean is to configure /config/user_alert.conf instead of editing /etc/alertd/alert.conf. i understand if alert name is identical, configuration in user_alert.conf takes precedence.

    .1.3.6.1.4.1.3375.2.4.0.10 is configured in alert.conf but .1.3.6.1.4.1.3375.2.4.0.100 is set in user_alert.conf.

    [root@ve11d:Active:Changes Pending] config  grep -A 2 BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS\ { /etc/alertd/alert.conf
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {
        snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"
}
[root@ve11d:Active:Changes Pending] config  cat /config/user_alert.conf
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {
        snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.100"
}

    trap sends .1.3.6.1.4.1.3375.2.4.0.100.

    [root@ve11d:Active:Changes Pending] config  tcpdump -nni eth0 -s0 -X udp port 162
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
21:24:01.926783 IP 172.28.24.225.37050 > 172.28.24.1.162:  V2Trap(236)  .1.3.6.1.2.1.1.3.0=162397030 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.3375.2.4.0.100 .1.3.6.1.4.1.3375.2.4.1.1="Pool /Common/foo member /Common/200.200.200.101:80 monitor status down. [ /Common/fake: down ]  [ was unchecked for 0hr:0min:12sec ]" .1.3.6.1.6.3.1.1.4.3.0=.1.3.6.1.4.1.3375.2.4
        0x0000:  4500 0119 0000 4000 4011 b0b9 ac1c 18e1  E.....@.@.......
        0x0010:  ac1c 1801 90ba 00a2 0105 8a31 3081 fa02  ...........10...
        0x0020:  0101 0406 7075 626c 6963 a781 ec02 046b  ....public.....k
        0x0030:  aab9 aa02 0100 0201 0030 81dd 3010 0608  .........0..0...
        0x0040:  2b06 0102 0101 0300 4304 09ad fb66 3019  +.......C....f0.
        0x0050:  060a 2b06 0106 0301 0104 0100 060b 2b06  ..+...........+.
        0x0060:  0104 019a 2f02 0400 6430 8194 060b 2b06  ..../...d0....+.
        0x0070:  0104 019a 2f02 0401 0104 8184 506f 6f6c  ..../.......Pool
        0x0080:  202f 436f 6d6d 6f6e 2f66 6f6f 206d 656d  ./Common/foo.mem
        0x0090:  6265 7220 2f43 6f6d 6d6f 6e2f 3230 302e  ber./Common/200.
        0x00a0:  3230 302e 3230 302e 3130 313a 3830 206d  200.200.101:80.m
        0x00b0:  6f6e 6974 6f72 2073 7461 7475 7320 646f  onitor.status.do
        0x00c0:  776e 2e20 5b20 2f43 6f6d 6d6f 6e2f 6661  wn..[./Common/fa
        0x00d0:  6b65 3a20 646f 776e 205d 2020 5b20 7761  ke:.down.]..[.wa
        0x00e0:  7320 756e 6368 6563 6b65 6420 666f 7220  s.unchecked.for.
        0x00f0:  3068 723a 306d 696e 3a31 3273 6563 205d  0hr:0min:12sec.]
        0x0100:  3017 060a 2b06 0106 0301 0104 0300 0609  0...+...........
        0x0110:  2b06 0104 019a 2f02 04                   +...../..