matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
a8d2d0b5cd
sonic-buildimage/files/image_config/monit/generate_monit_config

40 lines
1.4 KiB
Plaintext
Raw Normal View History

[201911][Monit] Monitor critical processes in radv and dhcp_relay containers. (#7340) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor critical processes in router advertiser and dhcp_relay containers by Monit. How I did it Router advertiser container only ran on T0 device and the T0 device should have at least one VLAN interface which was configured an IPv6 address. At the same time, router advertiser container will not run on devices of which the deployment type is 8. As such, I created a service which will dynamically generate Monit configuration file of router advertiser from a template. Similarly Monit configuration file of dhcp_relay was also generated from a template since the number of dhcrelay process in dhcp_relay container is depended on number of VLANs. How to verify it I verified this implementation on a DuT.
2021-04-16 10:40:06 -05:00
#!/bin/bash
# Generate the following files from templates:
[201911][Monit] Monitor critical processes in PMon contianer. (#7438) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor the critical processes in PMon container by Monit in 201911 branch. How I did it I created a template configuration file of Monit and it will be rendered to generate Monit configuration file of PMon container by a service generate_monit_config.service. How to verify it I verified this on a Mellanox device str-msn2700-03 and an Arista device str-a7050-acs-1. Which release branch to backport (provide reason below if selected) 201811 [x ] 201911 202006 202012
2021-04-28 19:12:21 -05:00
# 1. Monit configuration file of dhcp_relay container
# 2. Monit configuration file of PMon container
# 3. Monit configuration file of radv container
[201911][Monit] Monitor critical processes in radv and dhcp_relay containers. (#7340) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor critical processes in router advertiser and dhcp_relay containers by Monit. How I did it Router advertiser container only ran on T0 device and the T0 device should have at least one VLAN interface which was configured an IPv6 address. At the same time, router advertiser container will not run on devices of which the deployment type is 8. As such, I created a service which will dynamically generate Monit configuration file of router advertiser from a template. Similarly Monit configuration file of dhcp_relay was also generated from a template since the number of dhcrelay process in dhcp_relay container is depended on number of VLANs. How to verify it I verified this implementation on a DuT.
2021-04-16 10:40:06 -05:00
CFGGEN_PARAMS=" \
-d \
-t /usr/share/sonic/templates/monit_dhcp_relay.j2,/etc/monit/conf.d/monit_dhcp_relay \
[201911][Monit] Monitor critical processes in PMon contianer. (#7438) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor the critical processes in PMon container by Monit in 201911 branch. How I did it I created a template configuration file of Monit and it will be rendered to generate Monit configuration file of PMon container by a service generate_monit_config.service. How to verify it I verified this on a Mellanox device str-msn2700-03 and an Arista device str-a7050-acs-1. Which release branch to backport (provide reason below if selected) 201811 [x ] 201911 202006 202012
2021-04-28 19:12:21 -05:00
-t /usr/share/sonic/templates/monit_radv.j2,/etc/monit/conf.d/monit_radv \
[201911][Monit] Monitor critical processes in radv and dhcp_relay containers. (#7340) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor critical processes in router advertiser and dhcp_relay containers by Monit. How I did it Router advertiser container only ran on T0 device and the T0 device should have at least one VLAN interface which was configured an IPv6 address. At the same time, router advertiser container will not run on devices of which the deployment type is 8. As such, I created a service which will dynamically generate Monit configuration file of router advertiser from a template. Similarly Monit configuration file of dhcp_relay was also generated from a template since the number of dhcrelay process in dhcp_relay container is depended on number of VLANs. How to verify it I verified this implementation on a DuT.
2021-04-16 10:40:06 -05:00
"
sonic-cfggen $CFGGEN_PARAMS
[201911][Monit] Monitor critical processes in PMon contianer. (#7438) Signed-off-by: Yong Zhao yozhao@microsoft.com Why I did it This PR aims to monitor the critical processes in PMon container by Monit in 201911 branch. How I did it I created a template configuration file of Monit and it will be rendered to generate Monit configuration file of PMon container by a service generate_monit_config.service. How to verify it I verified this on a Mellanox device str-msn2700-03 and an Arista device str-a7050-acs-1. Which release branch to backport (provide reason below if selected) 201811 [x ] 201911 202006 202012
2021-04-28 19:12:21 -05:00
PLATFORM=$(sonic-cfggen -d -v DEVICE_METADATA.localhost.platform 2> /dev/null)
if [[ $? == 0 && $PLATFORM != "" ]]; then
SENSORS_CONF_FILE="/usr/share/sonic/device/$PLATFORM/sensors.conf"
FANCONTROL_CONF_FILE="/usr/share/sonic/device/$PLATFORM/fancontrol"
HAVE_SENSORS_CONF=0
HAVE_FANCONTROL_CONF=0
if [ -e $SENSORS_CONF_FILE ]; then
HAVE_SENSORS_CONF=1
fi
if [ -e $FANCONTROL_CONF_FILE ]; then
HAVE_FANCONTROL_CONF=1
fi
confvar="{\"HAVE_SENSORS_CONF\":$HAVE_SENSORS_CONF, \"HAVE_FANCONTROL_CONF\":$HAVE_FANCONTROL_CONF}"
if [ -e /usr/share/sonic/device/$PLATFORM/pmon_daemon_control.json ]; then
sonic-cfggen -j /usr/share/sonic/device/$PLATFORM/pmon_daemon_control.json -a "$confvar" -t /usr/share/sonic/template/monit_pmon.j2,/etc/monit/conf.d/monit_pmon
else
sonic-cfggen -a "$confvar" -t /usr/share/sonic/template/monit_pmon.j2,/etc/monit/conf.d/monit_pmon
fi
fi
Reference in New Issue Copy Permalink