Updating Configuration

You can dynamically update the Excel platform configuration in SwitchManager using the Converged Services Administrator (CSA). Dynamic Configuration allows you to reconfigure the Excel platform , 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. The path of the new configuration file must be the same as the working directory of SwitchManager, and SwitchManager must be running.

The messages in the new configuration file are sent immediately to the switch 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 Excel platform. 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.