Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Administration Scripts Overview


You use the hadm account to execute a suite of shell scripts to manage the Steel-Belted Radius Carrier Session State Register database. The administration scripts are listed in Table 77.


Do not attempt to modify or maintain the database except by using these shell scripts, and do not edit the individual configuration files after installation, especially DBName.txt, DBPwd.txt, and DBUser.txt.

Table 77: Steel-Belted Radius Carrier High Availability Scripts

Script Type

Script Name

Database Maintenance

See See

Cache Maintenance

See See

IP Pool Maintenance

See See See See

IP Range Maintenance

See See See

IP Address Maintenance

See See

Session Maintenance

See See

User Concurrency

See See



  • Administration scripts are designed to preserve cross-table referential integrity in the face of administrator errors, such as an attempt to define overlapping ranges or an attempt to delete addresses in the middle of an address range.

  • We recommend that only one administrator perform maintenance tasks at a time. The scripts do not lock records, so running multiple scripts that individually modify the database can corrupt the database. (More than one administrator can safely read the databases simultaneously.)

  • Do not terminate any running scripts. Interrupting administration scripts that modify the database can leave the database in an invalid state. If you inadvertently run an administration script, allow the script to finish executing and then undo it.

  • IP addresses produced as output by an administration script such as, or are displayed in a modified “decimal dotted-quad” format. Spaces are added to each quad to improve readability in tables. For example, IP address is presented as 192.168. 21.  3 in script output. Spaces cannot be used as input to scripts that accept IP addresses as input arguments, such as,,,, and

  • Administration scripts that display information do not lock the database, because locking can slow down use of the database by RADIUS servers. As a consequence, dynamically changing data, such as cache-related information, is statistically accurate but is not a perfect snapshot of the database.

  • Administration scripts (especially identify servers by node ID. This node is specified in the configuration files config.ini and dbclusterndb.gen. It is also logged in the server log file (yyyymmdd.log) as NDB Node ID = value.

  • Before you execute scripts that modify the SSR database, you must put all SBR Carrier servers that use the database into management mode.

  • You can execute multiple Show scripts serially by entering each command (and its arguments, if appropriate) on the same command line, separating each command with semicolons. For example, this command executes the,, and scripts:

  • The scripts use confirmation dialogs to help avoid unintended changes. Answering no to a confirmation dialog terminates a script immediately; answering yes allows the script to continue. If you are familiar with running scripts, you can bypass all confirmation messages by using the yes command, for example: