Sql Commands; Local Database Commands - Digi TransPort User Manual

SQL commands

When IPSec Egroups are used with a SQL database for dynamic Eroute configuration, there are
CLI commands that will help with configuration and troubleshooting on the Digi router.

Local Database commands

As well as using an external SQL database, the Digi can cache the SQL table entries it learns from
the SQL server in RAM so if the SQL server goes offline for any reason, the database entries are
still available to renew existing IPSec SA's.
To configure the caching options the command used is
The following parameters are available to configure the caching of database entries:
dbsrvmem <n>
This parameter is used to specify the amount of memory (RAM) the MySQL server cache should
use. Where <n> is specified in multiples of 1k. such as 10Mb = 10240
To calculate the amount of memory to specify in this parameter:
1. Look at the size of the database file (.csv) that will be loaded into the Digi memory.
2. Double this value and add 100Kb, for example, if the csv file is 200Kb, this would
make a value of 500Kb for the memory allocation. Use the command
.
500
3. Load the database file into memory and check the memory allocated and free using
the
smem
the memory in the
dbfile <name>
This is the name of the csv file that the Digi will use to store the table definitions (1st line) and
data records. This file is stored in flash and is used to populate the database stored in RAM on
power up or when a new file matching this name has just been stored. The dbfile can be
populated with records or be empty except for the definitions line. The dbfile stored in RAM will
be populated from both the dbfile stored in flash and (if configured) via caching items learnt from
the main SQL server. The dbfile in flash can then be updated from the dbfile in RAM and saved.
Digi TransPort User Guide
command. This will show the memory allocated and left available. Increase
command if required.
dbsrvmem
sql 0 <parameter> <value>
sql 0 dbsrvmem
.
549