Please read Script Templates section in Lighthouse manual http://ftp.opengear.com/download/manual/current/ and the following article as it explains Script Templates usage, how to upload and apply to specific nodes.
Note: Use the freely available Notepad++ which allows you to save the script with Unix (LF) line endings, not DOS (CRLF) line endings. Ensure any 'single' and "double" quotation marks have not been converted into curly “smart quotes”. Applying scripts with DOS (CRLF) line endings will break node configuration.
To disable Remote Syslog:
config -d config.syslog.servers -a
To enable Remote Syslog:
Enable Syslog via the GUI on a Node (Console Server).
SSH into the Node and run the following command to generate the configuration.
echo "config \\" ; config -g config.syslog | sed -e 's/ /=\'\''/' -e 's/$/'\'' \\/' -e 's/^/-s /'; echo "-a"
This shows example configuration for single Syslog server:
The config.syslog.loglevel=info applies only to the local logs, leave at info unless instructed by support staff for debugging purpose.
-s config.syslog.loglevel='info' \
-s config.syslog.servers.server1.address='192.168.254.30' \
-s config.syslog.servers.server1.loglevel='info' \
-s config.syslog.servers.server1.port='514' \
-s config.syslog.servers.server1.protocol='udp' \
-s config.syslog.servers.total='1' \
The various loglevel are crit, debug, emerg, error, info, notice and warning.
The commands can be copied and pasted directly on the Console Server CLI or saved in a file (attached) and deployed via Lighthouse Script Template.
Article is closed for comments.