Network Element Configuration File

Name and location

The NE configuration file should have the following name and location: conf/cartNEConfig.cmt .

File syntax

The file syntax is as follows:

//  Define a first instance.
//
INSTANCE:MyFirstInstance

//  Define data common to all sub elements of MyFirstInstance:
//
  DATA:login=john

  //  Now define a sub element of MyFirstInstance. It will inherit all data
  //  from MyFirstInstance and may append some specific.
  //
  SUBELEMENT:DSLAM_east
    DATA:password=abcd

  //  Define a second sub element. It may override the main instance
  //  parameters.
  //  Also shows encryption tag.
  //
  SUBELEMENT:DSLAM_west
    DATA:login=mike|password=ENCRYPT:[encrypted password made with provadmin]

INSTANCE:MySecondInstance
[ and so on ]

The cartridge Network Element configuration is a repository of datasets related to keys. Keys are instance names or sub element names. The hierarchy of instances and sub elements may match the cartridge topology (i.e. may match the how Network Elements are reached through a dynamic cartridge) but this is not enforced.

The names defined by INSTANCE: and SUBELEMENT: are keys, and are global: one cannot define an instance with the same name as a sub element.

The syntax of DATA: information is the same as the one used in Cartridge's TST files to create and configure cartridge. Non-human readable data is also possible in the file, using the same method as in TST files.

Administration

The cartridge Network Element configuration file may be loaded, reloaded and displayed with the cart provadming command. See Fulfillment Provisioning User Guide for details.

It is recommended to load the file right before reloading checkpoints.

The file can be reloaded during Fulfillment Provisioning processing. The file is first audited against errors, then used to replace runtime values, therefore preventing data to be partially loaded: either the whole file is loaded, or the runtime data remains untouched.

Administration

The cartridge Network Element configuration file may be loaded, reloaded and displayed with the cart provadming command. See Fulfillment Provisioning User Guide for details.

It is recommended to load the file right before reloading checkpoints.

The file can be reloaded during Fulfillment Provisioning processing using provadmin loadNEConfig cart force=true command. The file is first audited against errors, then used to replace runtime values, therefore preventing data to be partially loaded: either the whole file is loaded, or the runtime data remains untouched.

Usage

To use the cartridge Network Element configuration for Work Order enrichment, users just need to load a NE config file. The WOP package will then, for each incoming Work Order, after the routing but before the datamapping:

• Resolve the element name to which the Work Order will be sent. For cartpool instances, the element name is the instance name. For cartdyn instances, the element name depends on the configuration and on the dataset of the incoming WO. If the cartdyn instance configuration defines a logical name parameter and the parameter is present in the WO dataset, then the logical name parameter value is used as the element name. If all other cases, the element name is the concatenation of get session parameters defined in the instance configuration separated by "+".

  Use this element name to query the cartridge Network Element configuration for NE specific dataset.

  Merge this dataset with the WO dataset. The merge will not override data already defined in the WO. For example, if the WO already contains a "password" entry, the "password" entry from the NE configuration will not be used.

To use the cartridge Network Element configuration for Product Order enrichment, please see the ponemapping package IDLOSDoc.