Note: Don’t forget to change relay_host if you change hostname or IP on your email server.
SMS modem: /etc/smsd.conf
Editing this file is optional.
This file configures the smsd program that sends SMS messages. This file is only needed if your system is equipped with a GSM/GPRS modem.
If you don’t want to edit this file make sure to disable the PIN-code control on your SIM card.
If you want to use a PIN code you need to uncomment and edit the variable ‘pin’
Example:
pin=1234
Depending on what sms gateway you have you may need to change the baudrate.
baudrate=38400
The table below describes what baudrate need for each sms gateway.
Sms gateway | Baudrate |
TC35 | 38400 |
TC65 | 115200 |
To test your settings you can issue the command ‘sendsms’
monitor!root:~# sendsms
Destination: 46733123456
Text: Testing to send SMS.
If you want to see whats happening you can issue the command ‘tail -f /var/log/smsd.log’ which will show you the conversation between the sms program and the gsm modem.
NRPE: /etc/nrpe.conf
Editing this file is optional, but highly recommended.
NRPE is the UNIX/Linux agent that op5 products use to gather information about the op5 System. To allow an op5 System to communicate with NRPE the ‘allowed_hosts’ variable needs to be edited.
Example:
allowed_hosts=127.0.0.1,192.168.1.10
SSL certificates: /etc/httpd/mksslcrt.sh
This is a script that can be used to generate a self signed SSL certificate for the op5 webbserver. Run the script by issuing the command /etc/httpd/mksslcrt.sh
Note: If you select to encrypt the CA and SERVER keys on STEP 7 and 8 you will have to enter the pass phrase every time you start apache. op5 recommend you not to encrypt keys.
System backup: /etc/op5-backup/main.conf
op5 recommends that you configure backup for your system.
op5backup is a simple but efficient backup utility for the op5 System. It can backup the configuration of op5 System, op5 Monitor, op5 Statistics and op5 Logserver. If you configure op5backup it is very easy to restore a failed system. Read more on
Backing up the System.
Static routes: /etc/sysconfig/network-scripts/route-<ifname>
This is optional.
Persistent routes are configured by creating a file for each interface that you wish to route traffic out from. The file should be named /etc/sysconfig/network-scripts/route-<ifname>
Example: /etc/sysconfig/network-scripts/routes-eth0
The syntax for this file is
<network> via <gateway> dev <ifname>
Example:
172.27.76.0/24 via 192.168.1.1 dev eth0
Patch management
The op5 System is RPM based, therefore all patches is distributed as RPM packages. Starting with op5 System version 3.0 the yum update manager is supported and the recommended method to update your system. More information regarding yum is found at: