Updating Configuration

You can dynamically update the CSP configuration in SwitchManager using the Converged Services Administrator (CSA). Dynamic Configuration allows you to reconfigure the CSP, add new trunk groups, or download a voice prompt without restarting SwitchManager. A new configuration file is sent to the switch with the SK_DynamicConfig message.

Whenever a dynamic configuration is sent to SwitchManager, the configuration file and any attached files will be sent to the directory:

$SK_LIB_DIR/dynamicConfig/

Also, the local file name will attach a timestamp to the file name. This ensures that received dynamic configurations (and attached files) have unique and simple names. The file name uses the following format:

YYYY.MM.DD_HH.MM.SS_filename

Example of a file name:

2005.12.08_14.12.47_addnode.cfg

If the $SK_LIB_DIR/dynamicConfig directory does not exist, the file transfer will fail.You should not place your local configuration files in the dynamicConfig directory. This directory is meant for SwitchManager's use. Any local user-created configurations should be stored elsewhere.

The messages in the new configuration file are sent immediately to the CSP and the new messages merge with those in the current configuration file. You can create a merged configuration file by sending the SK_WriteCfgFile message.

Important! Dynamic configurations are stored in memory by SwitchManager. After many dynamic configurations, local memory may be consumed. You should be aware of how much memory is used by SwitchManager. If memory usage is too great, ensure that the base configuration file used is updated to reflect the correct configuration of the switch and restart SwitchManager using Smart Mode or Maintain Only options.

Configuring a Multi-Node System

Modifications to the configuration are required for running SwitchKit on a multi-node CSP. You can find an example of a multi-node configuration file in samples/cfg/exnet.cfg.

Configuration File Modifications

Modifications required for multi-node systems are as follows:

EXNET® Ring Configuration

Configure the ring with:

RingConfig(

entity=1,

slot=0xff,

data=0xff); #DeAssign all rings

RingConfig(

entity=1,

slot=10,

data=1); #Assign ring 1

RingConfig(

entity=2,

ring=1,

data=1); #Configure ring 1 for trans/rec

Logical Node ID

For each assignSpan command, you must specify the logical node ID. So, for an assignSpan, you would have:

AssignSpan(node=3, span=9, slot=3, offset=0);

Span IDs are unique across the system. An application can send a message without specifying a node ID, and the LLC will automatically fill in the appropriate Node ID.