Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Applying the Saved Signalware Configuration to the New Server


After you install Signalware 9 (as described in Installing Signalware 9 on Linux), restore the saved configuration to that installation.

To restore the Signalware configuration:

  1. Ensure that Signalware is not running. To stop Signalware, execute the terminate command:

    $OMNI_HOME/bin/Terminate 0

  2. Copy or send through FTP the archived backup copies of NODENAME. $SHM .date and cestart. $SHM to $OMNI_HOME/ulcm/bin on the new server.

  3. Create a new process.mml file from the old server’s settings.

    1. Execute DFcat on the cestart. $SHM file from the old server to create cestart.txt.

      For example, execute:

      $OMNI_HOME/bin/DFcat cestart. $SHM > cestart.txt

      Output is similar to this example:

    2. Copy the cestart.txt file to create a new file named process.mml.

      The new file should contain three lines, but DFcat might have inserted line breaks in the long string of the second line of the output that affect the appearance of the file. Delete these extra line breaks.

      Depending on the string and your text editor, you may need to insert a space where the line breaks had been, to separate the items in the command string. After you delete the line breaks, make sure the command string entry is one long, unbroken, string.

  4. Edit the new process.mml file.

    This file contains the START-PROCESS command for the new server, built from the syntax used on the old server.

    1. Add a new first line to the file that contains the string:


    2. Create a CE entry from the old server’s CE data.

      Change the line that reads (in the example):

      .CE tssunblade100

      to an attribute-and-field format that reads:


    3. Create a NAME entry.

      The first set of characters on the second line of the source file is the name of the server. Edit this line to change the string into a valid NAME entry (in the example) on its own line:


      to the attribute-and-field format:


    4. Create an EXEC entry.

      Most of the remainder of the file contents is the invocation of the authGateway program, the command syntax the program uses when it starts. If the old server was functioning correctly, do not make any changes to the string syntax. You do need to clean up the raw string.

      • Delete any characters at the beginning of the line that precede the command string (the command string begins with /opt/JNPRsbr/radius...).

        In the example, the characters to delete are:

        . 0 DEF DEF 0 0

      • Insert an EXEC=” field label before the command string.

      • Insert a closing quotation mark at the end of the command string.

      With those edits made, the file resembles this example:

    5. Delete the last line of the file, which contains the Signalware node name.

      In the example, that line reads:

      @MGW C7M3UA

    6. The file still contains both the old server’s name and CE setting (tssunblade100 and GMT). If the new server does not use those names, edit and update the CE, NAME, and EXEC fields with the new server settings.

    7. During the Signalware installation on the new server, if you changed the Signalware node name from the name used on the old server, edit and update that entry in the EXEC line (-node MGW in the example).

    8. Change the path to the SBR Carrier authGateway program from the 5.5.4 setting to the new default path for Steel-Belted Radius Carrier:


    9. Save and close the file.

  5. Use the DFcat program on the archive file to create an .mml file.

    For example:

    $OMNI_HOME/bin/DFcat archive.NODENAME. $SHM .date > archive.mml

  6. If the new Signalware installation does not inherit the same hostname and IP address used by the existing server, edit the archive.mml file to use the new server’s information. You may change other settings at this time to match the new server environment.

  7. Start Signalware.



  8. Load archive.mml first. Then load process.mml.


    $OMNI_HOME/bin/swmml -f archive.mml

    $OMNI_HOME/bin/swmml -f process.mml