Advanced Configuration Management IPWorks User Guide

Contents

1Introduction
1.1Prerequisites

2
Advanced configuration procedure
2.1Filtering the relevant IPWorks service configuration
2.2Saving IPWorks Service Configuration
2.3Creating a Node
2.4Importing a Schema
2.5Importing a Reference MPVL
2.6Importing a variable MPVL and relevant IPWorks Feature MPVL
2.7Merging a complete MPVL
2.8Creating a Site-Specific List (SSL)
2.9Adding additional specific Configurations
2.10Complete MPVL Validation
2.11Creating a Configuration Package
2.12Merging configuration

3
Validation of Advanced Configuration

4
Appendix A Adding additional specific configurations
4.1Adding a new Parameter Group for DNS
4.2Adding a new Parameter Group for ENUM
4.3Adding a new Parameter Group for AAA Diameter
4.4Adding a new Parameter Group for AAA Radius

5
Appendix B Parameter Definition of Site-Specific List
5.1Parameter Definition of Site-Specific List for DNS
5.2Parameter Definition of Site-Specific List for ENUM
5.3Parameter Definition of Site-Specific List for IPWorks Common
5.4Parameter Definition of Site-Specific List for AAA Diameter
5.5Parameter Definition of Site-Specific List for AAA Radius

Reference List

1   Introduction

This document describes how to execute a quick IPWorks configuration duplicating from the configured source site to target site which has initialized IPWorks configuration.

The document is available on DNS/ASDNS, ENUM, AAA Diameter, and AAA Radius services in IPWorks. Other services and scenarios are out of the scope.

1.1   Prerequisites

This section describes the prerequisites which must be fulfilled before IPWorks advanced configuration.

The user must have the following capabilities and access rights:

1.1.1   Documents

Ensure that the following documents have been read and understood and are accessible during the configuration:

1.1.2   Tools

Before the IPWorks advanced configuration executes, a computer meeting the following requirements is needed:

This document describes the procedure of IPWorks advanced configuration used PDBGUI. For more information, refer to PDB User Guide.

1.1.3   Configuration Environments

Before starting the procedure of IPWorks advanced configuration, ensure that the following information is available:

1.1.4   Provided Files

Before starting the procedure of IPWorks advanced configuration, ensure that the following files are stored in Advanced Configuration Packages:

2   Advanced configuration procedure

This section describes how to execute a quick IPWoks configuration duplicating from the configured source site to target site which has initialized IPWorks configuration.

The feature scopes include:

The following tasks will be done during the quick IPWorks configuration duplicating from Source Site to Target Site (see Figure 1):

Figure 1   the procedure for quick IPWorks configuration duplicating

The validation reports will be displayed after import of schema files, reference MPVL files, variable MPVL files, and during the configuration package creation.

  1. Filtering the relevant IPWorks service configuration
  2. Saving IPWorks service configuration
  3. Creating a Node
  4. Importing a Schema
  5. Importing a Reference MPVL
  6. Importing a Variable MPVL and Feature MPVL
  7. Merging a Complete MPVL
  8. Creating a Site-Specific List (SSL)
  9. Adding additional specific Configurations
  10. Completing MPVL Validation
  11. Creating a Configuration Package
  12. Migrating Configuration

2.1   Filtering the relevant IPWorks service configuration

The section describes how to filter the relevant configuration to ENB in Source Site.

For example, to filter the DNS configuration, do:

  1. Download DNS configuration IPWorks_DNS_filter.txt from Advanced Configuration Packages.
  2. Setup the Node Connection in ENB. Refer to the section Setup the Node Connection in Ericsson NETCONF Browser User Guide.

    To setup a node connection:

    • In the Connections workspace, click New connection or press Ctrl+N. The Connection dialog box opens on the NETCONF Interface tab. Select "use NETCONF subsystem" in SSH and "select get-config" in NETCONF (see figure 2).

Figure 2   Connection Dialog Box

  1. To input the file filter_IPWorks_DNS.xml, click Netconf Filter (see Figure 3). Refer to the section Apply a NETCONF Filter in Ericsson NETCONF Browser User Guide.

Figure 3   NETCONF Filter Tab

  1. Click Save.

2.2   Saving IPWorks Service Configuration

The section describes how to save the relevant IPWorks service configuration to ENB in Source Site.

To save configuration, do:

2.3   Creating a Node

The section describes how to create a Node in PDB.

To create a new Node in PDB, do:

  1. In the PDBGUI, select Nodes from the menu options on the left.
  2. Click New.
  3. Enter the required information such as: application, product number, platform and default export type.
  4. Click Apply.

For more information, refer to the section Defining a New Node in PDB User Guide.

2.4   Importing a Schema

The section describes how to import a schema to PDBGUI.

The Schema ZIP file contains all services schema.

To import a schema, do:

  1. Unzip the ZIP archive described in section 2.2. The ZIP files contains a folder named schemas and a NETCONF file named Configuration.xml.
  2. Compress the schemas folder to ZIP format.
  3. In the Schemas workspace, click Import. The Import Dialog opens (see Figure 4).
  4. Select the node which creates in section 2.3 in the field Node and select schema ZIP file created in step 2 in the field Input File. Set name and revision in the fields Schema Name and Revision.
  5. Click Import.

Figure 4   Import Dialog Tab

2.4.1   Schema Validation

The errors and several warnings in validation report can cause advanced IPWorks configuration failure.

2.5   Importing a Reference MPVL

The section describes how to import a Reference MPVL.

To import a Reference MPVL, do:

  1. In the Configurations workspace, click Import (see Figure 5).
  2. Select the File Format with "NETCONF" and Schema with the schema described in section 2.4.
  3. Select the file Configuration.xml in Unzip file from ENB in Input File.
  4. Select the file format "MPVL".
  5. Click Import.

Refer to the section Importing a Node Configuration in PDB User Guide.

Figure 5   Import dialog tab

2.5.1   Reference MPVL Validation

PDBGUI automatically validates the syntax of the reference MPVL file and examines the relationship between configuration elements.

The errors and several warnings in validation report can cause advanced IPWorks configuration failure.

2.5.2   Modification of reference MPVL

This section describes how to solve the errors and warnings of Validation Reference MPVL.

2.5.2.1   Modification for DNS Service

  1. Find the restricted directory of AsdnsSmLog attribute in the DNS reference configuration created in section 2.5in Configurations workspace.
  2. Right click the restricted directory and select Delete. The Delete dialog box opens.
  3. Click OK.
  1. Find the restricted directory of DnsSmLog attribute in the DNS reference configuration created in section 2.5in Configurations workspace.
  2. Right click the restricted directory and select Delete. The Delete dialog box opens.
  3. Click OK.

2.5.2.2   Modification for ENUM Service

  1. In the MPVL file with Configurations workspace, find the attribute inapDigitTable (see Figure 6).
  2. Right click this attribute and select Edit. The Edit dialog box opens.
  3. Add a space to the inapDigitTable value (see Figure 7).
  4. Click Apply.

    The updated value is saved.

Figure 6   Directory of the value inapDigtTable

Figure 7   Add a space to the end of value inapDigitTable

2.5.2.3   Modification for AAA Diameter Service

  1. Find the restricted directory of AAAServerManager attribute in the AAA Diameter reference configuration created in section 2.5in Configurations workspace.
  2. Right click the restricted directory and select Delete. The Delete dialog box opens.
  3. Click OK.

2.5.2.4   Modification for AAA Radius Service

2.5.2.5   Modification for IPWorks Common

  1. Find the restricted directory of StorageServer attribute in the IPWorks common reference configuration created in section 2.5 in Configurations workspace.
  2. Right click the restricted directory and select Delete. The Delete dialog box opens.
  3. Click OK.
  1. Find the restricted port of StorageServer attribute in the IPWorks common reference configuration created in section 2.5in Configurations workspace.
  2. Right click value port and select Delete. The Delete dialog box opens.
  3. Click OK.

2.6   Importing a variable MPVL and relevant IPWorks Feature MPVL

The section describes how to import a variable MPVL and a relevant IPWorks feature MPVL.

2.6.1   Importing a variable MPVL

Variable MPVL file contains the site-specific parameters relevant IPWorks service.

For example, import DNS variable MPVL:

  1. In the Configurations workspace, click Import.
  2. Select the File Format with "PVL", Import From with "FIXED", Schema with the schema described in section 2.4. Add DNS variable MPVL file DNS_variable_MPVL.xml from Advanced Configuration Packages to Input File.
  3. Select the file type with "MPVL".
  4. Click Import. This new variable MPVL is displayed in Configurations workspace (see Figure 8). Refer to the section Importing a Node Configuration in PDB User Guide.
  5. Modify the value of attribute ManagementElementId of the reference MPVL to the value {{NODE_NAME}}.
    • Open the reference MPVL described in section 2.5.
    • Click attribute ManagementElementId (see Figure 9).
    • Click Edit In-Line
    • Set {{NODE_NAME}} to value field of managedElementId.
    • Click Apply.
      Note:  
      After click Apply, a error message will be displayed, but can be ignored .

      Errors during apply/create: Key Parameter [managedElementId={{NODE_NAME}}] WARNING Format check depends on site specific values for managedElementId={{NODE_NAME}} WARNING No global variable with name 'NODE_NAME' defined. ----------------


  6. PDB automatically validates configuration files during the import a variable MPVL. This check verifies the syntax of the configuration files and validates the node configuration according to the selected schema. Refer to the section 2.5.1.

Figure 8   Import Dialog tab

Figure 9   Modify the value of ManagementElementId

2.6.2   Importing a relevant IPWorks Feature MPVL

This section describes how to import a relevant IPWorks feature MPVL.

A relevant IPWorks feature MPVL can be imported in PDB, if the relevant IPWorks feature is not enabled in source site and needs to be used in target site.

For example, to import IPWorks PKI Server feature MPVL:

  1. Import the NETCONF file IPW_AAA-DIAMETER_PKISERVICE_MPVL.xml to PDB, refer to the section 2.6.1
    Note:  
    This file contains some attributes with default and variable values.

2.6.3   Modifying some parameters for special features of AAA (option)

This section lists the parameters for special features of AAA service.

If Accounting forward or IWLAN service is enabled in AAA RADIUS service; WiFi mobility management, Non-SIM Device Support (NSDS), or EIR domain is enabled in AAA Diameter service, the following parameters listed in table below must be modified in AAA Diameter and AAA Radius reference mpvl configurations.

The procedure of manual Modifying Parameters refers to the section 9.3.3.1 in PDB User Guide.

Table 1    Parameters for special features of AAA service

ManagedElement

Attribute

Description

+-IPWorksAAARoot
  +-IPWorksDiameterAAARoot
    +-DiameterAAAService
      +-AAAPKIService

serverPrivateKeyPassword

Server private key password 

      +-WIFIMMService

 

mcc4AnonymousProxy

The specific MCC(mobile Country Code) for anonymous proxy in WiFi Mobility

mcc4HPLMN

MCC of Home PLMN(public Land Mobile network) in WiFi Mobility Management

mcc4UnknownUserLocation

Default MCC for WiFi Mobility Management. It is used if the user location is unknown.

specialMNC

The specific MNC for WiFi Mobility Management, which is negotiated with HSS.

   +-DiameterStack
     +-EirDomain

 

eirRealm

EIR Dest-Realm information

+-IPWorksAAARoot
  +-IPWorksRadiusAAARoot
    +-RadiusAAAService
      +-AccountingService
        +-AcctForward
          +-AcctForwardGroupMgr
            +-AcctForwardGroup

acctForwardDestAddr

Accounting forward remote server address list, split by ":". For example, "10.175.185.52 : 10.175.185.53".

+-IWLANService
        +-RadiusSS7Stack

cmpAddress

Specifies the CP(Connection point) management address of SS7 stack. The format is IP: port. The setting must be the same as that of CP Manager Address of the SS7 stack.

sgsnAddress

Specifies the IP address of SGSN(Serving GPRS Support Node).

2.7   Merging a complete MPVL

The section describes how to merge the content of Reference MPVL and Feature MPVL to a complete MPVL.

To merge a complete MPVL, do:

  1. In the Configurations workspace, select the node described in section 2.3 and Click Search. Make sure that the Feature MPVL and Reference MPVL are displayed, if the Feature MPVL exists.

    If only create one node and use the same schema, all MPVLs will be displayed.

  2. Click Merge. The Merge dialog box opens (see Figure 10).
  3. Push the Variable MPVL or feature MPVL in Available Box to Selected Box.
  4. Push the Reference MPVL in Available Box to Selected Box.
    Note:  
    Ensure that the Reference MPVL is lower than other MPVL in Selected Box.

  5. Select the schema described in section 2.4 to Schema and define a complete MPVL name.
  6. Click Next>. The Merge Report dialog opens (see Figure 11).
  7. Select Use Default Resolution and check if all possible values contain double curly brackets {{ and }} .
  8. Click Finish. The complete MPVL is displayed in Configurations workspace.

Refer to the section Merging Node Configurations in PDB User Guide.

Figure 10   Merge dialog tab

Figure 11   Merge Report dialog tab

2.8   Creating a Site-Specific List (SSL)

This section describes how to create a Site-Specific List (SSL), add Site-Specific variables from the complete MPVL and assign values to the variables.

To create a SSL, do:

  1. In the Site-Specific Lists workspace, click New.
  2. Enter the required information. Refer to the section Creating a New Site-Specific List in PDB User Guide
  3. Click Apply.

To add Site-Specific variables from the complete MPVL, do:

  1. In the Site-Specific Lists workspace, choose the created item. The Site Specific Parameters table is displayed.
  2. Click Add from Configuration. The Configurations dialog box opens
  3. Select the complete MPVL created in section 2.7 with the Format NETCONF in the Configuration field
  4. Click Add from Configuration (see Figure 12).
    Note:  
    The SSL contains 4 mandatory parameters <Application>_NC_HOST, <Application>_NC_PASSWORD, <Application>_NC_PORT, and <Application>_NC_USER . They are respectively target site host, target site password, target site NETCONF port and NETCONF user.

  5. The Site Specific Parameters is displayed. Click , the Usage Dialog opens.
  6. Select complete configuration to search in the Configuration field.
  7. Click Find. The name or revision level displays matching node configuration.

Refer to the section Adding Site-Specific Variables from a Node Configuration in PDB User Guide.

To assign values to the variables, do:

  1. In the Site-Specific Lists workspace, select the created SSL to work with.
  2. Click Edit.
  3. Update the site-specific information.
  4. Click Apply.

Figure 12   Example of ENUM Site Specific Parameters

For more information, refer to the section Modifying Site-Specific Variables in PDB User Guide.

2.9   Adding additional specific Configurations

For detailed information about Adding additional specific Configurations, see appendix.

2.10   Complete MPVL Validation

PDBGUI can validate that the number of instances defined for given element within a node configuration is allowed by the schema. Besides, PDBGUI can validate that the parameter values defined within a node configuration follow the type constraints and value patterns that are allowed for that element as defined by the schema.

To validate the complete MPVL, do:

  1. In the Configurations workspace, right click the complete MPVL and select Validate. The Validations dialog opens.
  2. Select Site Specific List.
  3. Click Validate.
  4. Click Download Report to save the Validation report. For the warning solution, refer to Section 2.5.1.

2.11   Creating a Configuration Package

This section describes how to create the configuration package with PDBGUI.

To manually export a node configuration, do:

  1. In the Configurations workspace, right click the complete MPVL and select Export (see Figure 13).
  2. Select the Format "NETCONF" with "Use NETCONF Subsystem '-s netconf'".
  3. Select "Resolve variables using a Site Specific List" .
  4. Select the site specific list described in section 2.8.
  5. Click Export.
  6. Click Download Configuration to save the configuration archive.

For more information, refer to the section Exporting a Node Configuration in PDB User Guide.

Figure 13   Export a Configuration Dialog Box

2.12   Merging configuration

This section describes how to merge the configuration package to the IPWorks in target Site.

To merge the configuration to Target Site, do:

  1. Unzip the configuration package in Target Site. It contains following files and folder:
    • configuration_package.zip
    • node_configuration
    • pdb-configtool.jar
    • run_configure.bat
    • run_configure.sh
  2. Execute run_configure.sh for Linux, and run_configure.bat for Windows®, to push the configurations through the NETCONF protocol into the Target Site.

The script contains the username, password, and IP address of the Target Site. This information is set in the site-specific list, which is used in the creation of the configuration package. The script deploys all configuration data present in the is.xml file, which can be found in the node_configuration folder.

3   Validation of Advanced Configuration

This function is used for check whether the configuration duplicating from source site to target site is successful.

To validate of Advanced Configuration:

  1. Check whether the relevant service reference MPVL created in section 2.5 is existed.
  2. After configuration duplicating forwards to target site, setup the Node Connection with ENB in target site, refer to section 2.1.
  3. Save IPWorks relevant service configuration of target site, refer to section 2.2.
  4. Import relevant service reference MPVL of target site, refer to section 2.5.
  5. Comparison of reference MPVL between source site and target site, refer to the section Comparing Two Configurations in PDB User Guide.

    If all relevant service configuration data of source site and target site except site-specific parameters is same, the configuration duplicating from source site to target site is successful.

4   Appendix A Adding additional specific configurations

This section describes how to add additional specific configurations corresponding IPWorks service.

4.1   Adding a new Parameter Group for DNS

This section describes how to add a new parameter group corresponding IPWorks DNS.

4.1.1   Add PmJob Parameter Group for DNS

This section describes how to add a Pm Job parameter group in PDB configuration based on requirement.

To add a Pm Job parameter group, do:

  1. Open the complete configuration in Configurations workspace.
  2. Under ManagementElement instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  3. Under the Add Parameter Group dialog box, select the filed Name System Function, set the value 1 to the filed systemFunctionId and click Apply.
  4. Under the System Function instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  5. Under the Add Parameter Group dialog box, select the field Name Pm, set the value 1 to the field name pmId and click Apply.
  6. Under the Pm instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  7. Under the Add Parameter Group dialog box, select the field Name PmJob, set the value PmJobId, such as DnsASDNSDefaultJob and click Apply
  8. Under your PmJobId instance, right click the option Add Parameter, Add Parameter dialog box opens.
  9. Under the Add Parameter dialog box, select the field name Name one by one, set the relevant value to the field name Value and click Apply.
  10. Under your PmJobId instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  11. Under the Add Parameter dialog box, select the field name MeasuremntReader instance and set the value to field name measurementReaderId.
  12. Under MeasurementReader instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  13. Under the Add Parameter dialog box, select the field name Name one by one, set the relevant value to the field name Value and click Apply.
  14. Validate the configuration after the changes are done.

4.2   Adding a new Parameter Group for ENUM

This section describes how to add a new parameter group corresponding IPWorks ENUM.

4.2.1   4.2.1 Add PmJob Instance for ENUM

Refer to section 4.1.1.

4.2.2   Add a CudbSite and a CudbNode Parameter Group

This section describes how to add a CudbSite and CudbNode parameter group.

To add a CudbSite and a CudbNode parameter group, do:

  1. Under the CudbManager instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name CudbServiceSite, set the field value cudbServiceSiteId, such as "ENUM" and click Apply.
  3. Under the CudbServiceSite instance, right click this option Add Parameter Group, Add Parameter Group dialog box opens.
  4. Under the Add Parameter Group dialog box, select the field Name CudbServiceManager, set the filed value cudbSiteManagerId, such as 1 and click Apply.
  5. Under the CudbServiceManager instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  6. Under the Add Parameter Group dialog box, select the field Name CudbSite, set the field value cudbSiteId, such as "enum_site1" and click Apply.
  7. Under the CudbSite instance, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  8. Under the Add Parameter Group dialog box, select the field Name CudbNode, set the value to the field value cudbNodeId, such as "127.0.0.1" and click Apply.

4.3   Adding a new Parameter Group for AAA Diameter

This section describes how to add a new parameter group for IPWorks AAA Diameter.

4.3.1   Add PmJob Instance for AAA Diameter

Refer to section 4.1.1.

4.3.2   Add APN Parameter Group for AAA Diameter

This section describes how to add an APN parameter group based on requirement.

If necessary, delete existed APN parameter group got from source site.

To add an APN Parameter Group:

  1. Under the AAAPKIAPNList parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name APN, set the field value apnId, such as "example-apn1" and click Apply.
  3. Under the APN parameter group, right click the option Add Parameter , Add Parameter dialog box opens.
  4. Under the Add Parameter dialog box, select the field Name apnName, Set the field value such as "example-apn1" and click Apply.
  5. Then add other parameter in the same way as apnName.
  6. If required, add EPSSubscribedQoSProfile parameter group under the APN parameter group.
  7. Under the APN parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  8. Under the Add Parameter Group dialog box, select the field Name EPSSubscribedQoSProfile, set the field value epsSubscribedQoSProfileId, such as "1" and click Apply.
  9. Under the EPSSubscribedQoSProfile parameter group, add parameters in the same way as apnName.
  10. Validate the configuration after the changes are done

4.3.3   Add OCSPServer Parameter Group for AAA Diameter

This section describes how to add an OCSPServer parameter group based on requirement.

If necessary, delete existed OCSPServer parameter group got from source site.

To add an OCSPServer parameter group:

  1. Under the OCSPMgr parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name OCSPServer, set the field value ocspServerId, such as "1" and click Apply.
  3. Under the OCSPServer parameter group, right click the option Add Parameter , Add Parameter dialog box opens.
  4. Under the Add Parameter dialog box, select the field Name responderUrl, Set the field value such as "http://127.0.0.1:12345" and click Apply.
  5. Then add other parameter in the same way as responderUrl.
  6. Validate the configuration after the changes are done.

4.3.4   Add GTConvert Parameter Group for AAA Diameter

This section describes how to add a GTConvert parameter group based on requirement.

If necessary, delete existed GTConvert parameter group got from source site.

To add a GTConvert parameter group:

  1. Under the GTConvertManager parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name GTConvert, set the field value gtConvertId, such as "1" and click Apply.
  3. Under the GTConvert parameter group, right click the option Add Parameter , Add Parameter dialog box opens.
  4. Under the Add Parameter dialog box, select the field Name digitsToAdd, Set the field value such as "86139" and click Apply.
  5. Then add other parameter in the same way as digitsToAdd.
  6. Validate the configuration after the changes are done.

4.3.5   Add CudbSite Parameter Group and CudbNode Parameter Group for AAA Diameter

This section describes how to add CudbSite parameter group and CudbNode parameter group.

Refer to section 4.2.2.

4.4   Adding a new Parameter Group for AAA Radius

This section describes how to add a new parameter group for AAA Radius.

4.4.1   Add PmJob Parameter Group for AAA Radius

This section describes how to add a PmJob Parameter Group.

Refer to section 4.1.1.

4.4.2   Add CudbSite Parameter Group and CudbNode Parameter Group for AAA Radius

This section describes how to add CudbSite parameter group and CudbNode parameter group.

Refer to section 4.2.2.

4.4.3   Add GTConvert Parameter Group for AAA Radius

This section describes how to add a GTConvert Parameter Group.

Refer to section 4.3.4.

4.4.4   Add ClientShareSecret Parameter Group for AAA Radius

This section describes how to add a ClientShareSecret parameter group.

If necessary, delete existed ClientShareSecret parameter group got from source site.

To add a ClientShareSecret parameter group:

  1. Under the ClientShareSecretMgr parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name ClientShareSecret, set the field value clientSharedSecretId, such as "1" and click Apply.
  3. Under the ClientShareSecret parameter group, right click the option Add Parameter , Add Parameter dialog box opens.
  4. Under the Add Parameter dialog box, select the field Name clientIPAddr, Set the field value such as "10.170.15.188" and click Apply.
  5. Then add other parameter in the same way as clientIPAddr.
  6. Validate the configuration after the changes are done.

4.4.5   Add ProxyTargetShareSecret Parameter Group for AAA Radius

This section describes how to add a ProxyTargetShareSecret parameter group.

If necessary, delete existed ProxyTargetShareSecret parameter group got from source site.

To add an ProxyTargetShareSecret parameter group:

  1. Under the ProxyTargetShareSecretMgr parameter group, right click the option Add Parameter Group, Add Parameter Group dialog box opens.
  2. Under the Add Parameter Group dialog box, select the field Name ProxyTargetShareSecret, set the field value sharedSecretId, such as "1" and click Apply.
  3. Under the ProxyTargetShareSecret parameter group, right click the option Add Parameter , Add Parameter dialog box opens.
  4. Under the Add Parameter dialog box, select the field Name type, Set the field value such as "ALL" and click Apply.
  5. Then add other parameter in the same way as type.
  6. Validate the configuration after the changes are done.

5   Appendix B Parameter Definition of Site-Specific List

This section describes the Site-Specific List per IPWorks service. These Site-Specific parameters define parts of the target network environment, such as IP addresses, port number, username and login credential.

5.1   Parameter Definition of Site-Specific List for DNS

This section describes the Site-Specific parameters in Site-Specific List for DNS (see Table 2).

Table 2    Site-Specific parameters for DNS

ManagedElement

Variable

Attribute

Description

+-ManagedElement

NODE_NAME

networkManagedElementId

Replaces the value component of the RDN in the COM Northbound Interface.

managedElementId

SITE_LOCATION

siteLocation

Describe the geographic location of a Managed Element.

+-IpworksFunction
  +-IpworksDnsRoot
    +-DnsServer 
      +-DnsSm

STORAGESERVER_USERNAME

ssUsername

Specifies the username that the Server Manager uses to log on to the Storage Server.

STORAGESERVER_PASSWORD

ssPassword

Specifies the password for the Storage Server username account. The password is case sensitive Note: The value can be changed when the Server Manager is running, but it will not take effect unless Server Manager is reloaded.

5.2   Parameter Definition of Site-Specific List for ENUM

This section describes the Site-Specific parameters in Site-Specific List for ENUM (see Table 3).

Table 3    Site-Specific parameters for ENUM

ManagedElement

Variable

Attribute

Description

+-ManagedElement

NODE_NAME

networkManagedElementId

Replaces the value component of the RDN in the COM Northbound Interface.

managedElementId

Specifies the user name that the Server Manager uses to log on to the Storage

SITE_LOCATION

siteLocation

Describe the geographic location of a Managed Element

+-IpworksFunction
  +-IpworksDnsRoot
    +-DnsServer 
      +-DnsSm

STORAGESERVER_USERNAME

ssUsername

Specifies the username that the Server Manager uses to log on to the Storage Server.

STORAGESERVER_PASSWORD

ssPassword

Specifies the password for the Storage Server username account. The password is case sensitive Note: The value can be changed when the Server Manager is running, but it will not take effect unless Server Manager is reloaded.

+-IpworksFunction
  +-IpworksDnsRoot
    +-IpworksEnumRoot
      +-EnumServer
        +-Erh
          +-ErhSs7

ERHSS7_REMOTESSN

remoteSSN

ERH remote SSN. Takes effect after ENUM server is restarted.

5.3   Parameter Definition of Site-Specific List for IPWorks Common

This section describes the Site-Specific parameters in Site-Specific List for IPWorks Common (see Table 4).

Table 4    Site-Specific parameters for IPWorks Common

ManagedElement

Variable

Attribute

Description

+-ManagedElement

NODE_NAME

networkManagedEleme

Replaces the value component of the RDN in the COM Northbound

managedElementId

SITE_LOCATION

siteLocation

Describe the geographic location of a Managed Element

 
 
  

+-IpworksFunction
  +-IpworksCommonRoot
    +-StorageServer
      +-SSInterface

STORAGESERVER_ADDRESS

Address

Address of the storage server, which is running and provides the provisioning service.

STORAGESERVER_USERNAME

username

Specifies the user name that the Server Manager uses to log on to the Storage Server.

STORAGESERVER_PASSWORD

password

Specifies the password for the Storage Server username account. The password is case sensitive Note: The value can be changed when the Server Manager is running, but it will not take effect unless Server Manager is reloaded..

5.4   Parameter Definition of Site-Specific List for AAA Diameter

This section describes the Site-Specific parameters in Site-Specific List for AAA Diameter (see Table 5).

Table 5    Site-Specific parameters for AAA Diameter

ManagedElement

Variable

Attribute

Description

+-ManagedElement

NODE_NAME

managedElementId

Replaces the value component of the RDN in the COM Northbound Interface.

networkManagedElementId

SITE_LOCATION

siteLocation

Describe the geographic location of a Managed Element. 

+-IPWorksAAARoot
  +-IPWorksDiameterAAARoot
    +-DiameterAAAService

HSS_REALM

hssRealm

Define the HSS Dest-Realm information.

      +-SS7Stack

 

SS7STACK_DESTSSN

destSSN

Define the dest SSN (subsystem name) for ss7stack. Takes effect: After next restart

 
 
 
 
 
 

5.5   Parameter Definition of Site-Specific List for AAA Radius

This section describes the Site-Specific parameters in Site-Specific List for AAA Radius (see Table 6).

Table 6    Site-Specific parameters for AAA Radius

ManagedElement

Variable

Attribute

Description

+-ManagedElement

NODE_NAME

networkManagedElementId

Replaces the value component of the RDN in the COM Northbound Interface.

managedElementId

SITE_LOCATION

siteLocation

Describe the geographic location of a Managed Element. 

+-IPWorksRadiusAAARoot
  +-IPWorksRadiusAAARoot
    +-RadiusAAAService
      +-AccountingService
          +-CSVFTPInformation

CSVFTP_SERVERADDRESS

ftpServerAddress

The IP address of FTP server. This is only valid for FTP push method.


Takes effect: After next restart

CSVFTP_SERVERPORT

ftpServerPort

The port of FTP server. This is only valid for FTP push method.


Takes effect: After next restart

CSVFTP_MODE

mode

IPWorks enables the user to transfer the CSV files to a remote FTP server if needed.


Specifies the FTP transfer method of CSV File: PULL_METHOD PUSH_METHOD.


The settings of the other FTP Transfer parameters take effect only when this parameter is set to PUSH_METHOD.


Takes effect: After next restart

CSVFTP_PASSWORD

password

The password of FTP server for the username. This is only valid for FTP push method.


Takes effect: After next restart

CSVFTP_USERNAME

username

The username of FTP server. This is only valid for FTP push method.


Takes effect: After next restart


Reference List

[1] PDB User Guide.
[2] Ericsson NETCONF Browser User Guide.
[3] IPWorks Configuration Management.


Copyright

© Ericsson AB 2017, 2018. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    Advanced Configuration Management IPWorks User Guide