Page Comparison

...

1. If not already provided by your system's installed OS image, extract the files from the archive into your ${SITECONTROLLER_HOME}/scripts folder. This is usually located at /opt/azeti/SiteController/scripts:

   Code Block
   mkdir -p /opt/azeti/SiteController/scripts tar -xvzf NIFE103-control.tar.gz -C /opt/azeti/SiteController/scripts

   
   

2. make sure the binaries have correct ownership and permissions:

   Code Block
   chown root:root /opt/azeti/SiteController/scripts/NIFE103-wdt* \ /opt/azeti/SiteController/scripts/watchdog.sh chmod 0700 /opt/azeti/SiteController/scripts/NIFE103-wdt* \ /opt/azeti/SiteController/scripts/watchdog.sh

   
   

3. Double check nct7904 is blacklisted:

   Code Block
   grep "nct7904" /etc/modprobe.d/blacklist* /etc/modprobe.d/blacklist.conf:blacklist nct7904

   If it is not blacklisted, just add a blacklist nct7904 entry to /etc/modprobe.d/blacklist.conf or remove the # in the beginning of the line, if that entry was just commented out.

4. Double check i2c_i801 is NOT blacklisted (note the #):

   Code Block
   grep "i2c_i801" /etc/modprobe.d/blacklist* /etc/modprobe.d/blacklist.conf:#blacklist i2c_i801

   If it is blacklisted, just add a # at the beginning of that line.

5. If you needed to modify a file in /etc/modprobe.d/ you need to reboot the machine for the changes to take effect.

6. modify the SiteController.cfg file a.k.a. Site configuration so that in section [remote_exec_calls] the following entries are present:

   Code Block
   [remote_exec_calls] watchdog_start = /opt/azeti/SiteController/scripts/watchdog.sh start watchdog_stop = /opt/azeti/SiteController/scripts/watchdog.sh stop watchdog_kick = /opt/azeti/SiteController/scripts/watchdog.sh kick

   
   

7. upload the watchdog-NIFE103.template.xml file as a new component template to the cloud (if it's not already available there, that is)

8. add this component template to your Site template in the usual way.

...