1. LSMS Configuration Guide
  2. Completing Configuration and Starting Connections

3 Completing Configuration and Starting Connections

This chapter explains how to create and start databases, configure Service Provider contact information, work with key lists, and configure and start NPAC components, EMS components, LSMS components.

Overview

This chapter explains how to create and start databases, configure Service Provider contact information, work with key lists, and configure and start NPAC components, EMS components, LSMS components.

Currently, the following NPAC (Number Portability Administration Center) regions serve the United States and Canada:
  • Midwest
  • MidAtlantic
  • Northeast
  • Southeast
  • Southwest
  • Western
  • WestCoast
  • Canada

LSMS can support all eight NPACs simultaneously. The LSMS acts as the interface between one or more NPACs and one or more network elements (NEs). Each NE is accessed through its Element Management System (EMS).

After you have installed the LSMS (for more information, refer to the LSMS Hardware Reference Manual) and integrated it into your network (see Integrating EAGLE Application B Card (E5-APP-B) into the LSMS Network), perform the remaining configuration procedures, as shown in Table 3-1 and Table 3-2.

Completing Configuration

Perform the procedures shown in Table 3-1 in the order shown, depending on whether you are installing LSMS for the first time or adding an NPAC region at a later time. In either case, the last step in Table 3-1 directs you to perform the steps in Table 3-2.

Table 3-1 Recommended Order of Configuration Procedures

Recommended Order for Initial Installation Recommended Order for Adding New Region After Installation Procedures

1 (Only if needed)

1

“Creating Databases”

2

(Not needed)

Log into the LSMS GUI for the first time (see "Starting an LSMS GUI Session" in the Alarms and Maintenance Guide).

3

(Not needed)

Create a service provider entry for the LSMS owner in the LSMS database by performing the procedure “Adding Service Provider Contact Information”.

4

(Not needed)

Select User/Session, and then Change Service Provider and log in with the SPID you created in the previous step.

5

2 (if needed)

For each additional SPID that you desire to allow access to LSMS data, create a supported service provider entry in the LSMS database by performing the procedure “Adding Service Provider Contact Information”.

6

(Not needed)

Modify the LSMS component by performing the procedure Modifying LSMS Configuration Components.

7

(Not needed)

For each EMS to be supported, create an EMS component by performing the procedure Creating an EMS Configuration Component.

8

3

For each NPAC, perform the list of procedures described in Table 3-2.

9

4

If desired, change the default TT/SSN values by performing the procedure “Modifying Default TT/SSN Values”.

Completing Configuration and Associating with Each NPAC Region

Either as part of initial installation or to add an additional region after the initial installation, perform the procedures in the order shown below once for each NPAC region you need to support.

Table 3-2 Configuring and Associating Each NPAC Region

Step Procedure to Perform

1

Perform the procedure “Generating a Key List”.

2

Select Keys, and then NPAC Keys to load the NPAC public key list into the LSMS database by performing the procedure Loading an NPAC Key List.

For the Key File field, type the following value in the Key List File field, where <ListName> is the value used in the procedure described in “Generating a Key List” (or you can click the Browse button and select this file name):

/usr/TKLC/lsms/<ListName>.public

3

Select Keys, and then LSMS Keys to load the LSMS private key list into the LSMS database by performing the procedure Loading an LSMS Key List.

For the Key File field, type the following value in the Key List File field, where <ListName> is the value used in the procedure described in “Generating a Key List” (or you can click the Browse button and select this file name):

/usr/TKLC/lsms/<ListName>.private

4

Select Configure, and then LNP System, and then NPAC , and then Modify, and then Secondary to create a secondary NPAC component and enter the information described in “Modifying an NPAC Component”. Ensure that the Activate Region checkbox is empty.

For the Component ID field, a value that is one greater than the value entered in the procedure in row 5 is suggested.

5

Click the icon that corresponds to this region so that the icon is highlighted, and select Configure, and then LNP System, and then NPAC , and then Modify, and then Primary to create a primary NPAC component. Enter the information described in “Modifying an NPAC Component”.

Ensure that the Activate Region checkbox is filled in. When you click the OK button, the sentry utility will automatically attempt to associate with the NPAC.

Creating Databases

If you are adding a region to be supported, use the following procedure to create the database for the new region:

  1. Log in to the active server with the username lsmsadm.
    (For more information about logging into a server, refer to the Alarms and Maintenance Guide)
  2. Change to the $LSMS_DIR directory by entering the following command:
    $ cd $LSMS_DIR
  3. For each new region, enter the following command to create the regional database, where <region> is the name of the NPAC region:
    $ npac_db_setup create <region>

    If an error that indicates that the database already exists is returned, enter the following command to remove the database and then repeat this step.

    $ npac_db_setup remove <region>

Service Provider Contact Information

Adding Service Provider Contact Information

To add service provider contact information into the LSMS database, use the following procedure.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the LSMS Console window, select Configure, and then Service Provider, and then Create.

    Figure 3-1 Configure Service Provider Selection

    Configure Service Provider Selection
    The Create LSMS Service Provider window displays.

    Figure 3-2 Create LSMS Service Provider Window

    Create LSMS Service Provider Window
  3. Enter the Service Provider ID (four alphanumeric characters).
  4. Enter the Service Provider Name (maximum 40 printable characters).
  5. Enter the following Contact Information items:
    • Name – name of the person to contact for service provider network information (maximum 40 alphanumeric characters)
    • Email – email address for the service provider network contact (maximum 60 alphanumeric characters)
    • Street – street address of the service provider network contact (maximum 40 alphanumeric characters)
    • City – city address of the service provider network contact (maximum 20 alphanumeric characters)
    • State – state address of the service provider network contact (two-letter uppercase abbreviation).

      If you use the Province field, enter -- (the default).

    • ZIP Code– postal zip code of the service provider network contact (five numeric characters)
    • Province – province of the service provider network contact (two-letter uppercase abbreviation).

      If you use the State field, enter -- (the default).

    • Country – country of the service provider network contact (maximum 20 alphanumeric characters)
    • Phone Number – phone number of the service provider network contact (ten numeric characters)
    • FAX Number – FAX number of the service provider network contact (ten numeric characters)
    • Pager Number – pager number for the service provider network contact (ten numeric characters)
    • Pager PIN– pager PIN number for the service provider network contact (maximum ten numeric characters)
  6. When finished, click OK to apply the changes and return to the LSMS Console window, or Apply to apply the changes and remain in the current window.
    Click OK in the message window:

    Figure 3-3 Create Successful

    Create Successful
  7. If you clicked Apply in 6, repeat steps 3 through 6.

Modifying Service Provider Contact Information

To modify service provider contact information, use the following procedure.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the LSMS Console window, select Configure, and then Service Provider, and then Modify.

    Figure 3-4 Modify LSMS Service Provider Window

    Modify LSMS Service Provider Window
  3. Enter the Service Provider ID (4 alphanumeric characters) or click the down arrow and select the desired Service Provider ID from the listbox.
  4. Modify the service provider contact information as required.
    See “Adding Service Provider Contact Information” for detailed information.
  5. When finished, click OK to apply the changes and return to the LSMS Console window, or Apply to apply the changes and remain in the current window.
    Click OK in the message window:

    Figure 3-5 Modify Successful

    Modify Successful
  6. If you clicked Apply in 5, repeat steps 3 through 5.

Viewing Service Provider Contact Information

To view service provider contact information, use the following procedure.

  1. Log in as a user in the lsmsview, lsmsuser, lsmsuext, or lsmsadm group.
  2. From the LSMS Console window, select Configure, and then Service Provider, and then View.
    The information in this window is read-only and cannot be modified.

    Figure 3-6 View LSMS Service Provider Window

    View LSMS Service Provider Window
  3. When finished viewing the information, click OK to return to the LSMS Console window.

Deleting Service Provider Contact Information

To delete service provider contact information, use this procedure.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the LSMS Console window, select Configure, and then Service Provider, and then Delete.

    Figure 3-7 Delete LSMS Service Provider Window

    Delete LSMS Service Provider Window
  3. If the Service Provider that you wish to delete is not displayed in the Service Provider ID field, click the down arrow to the right of that field and select the Service Provider ID that you wish to delete.
  4. Verify that this is the Service Provider that you wish to delete.
  5. When finished, click OK to apply the changes and return to the LSMS Console window, or Apply to apply the changes and remain in the current window.
    In either case, the Delete Confirmation window displays.

    Figure 3-8 Delete Confirmation Window

    Delete Confirmation Window
  6. Click Yes or No to end this procedure.

LSMS Configuration Components

Use the following procedures to manage LSMS configuration components:

Modifying LSMS Configuration Components

Use the following procedure to create or modify LSMS configuration components.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the main menu, select Configure, and then LNP System, and then LSMS, and then Modify.

    Figure 3-9 LNP System Menu – Modify LSMS

    LNP System Menu – Modify LSMS
    The Modify LNP System LSMS window displays. In this example, the Primary was selected. The window usually opens with the Component Info tab displayed; if the Component Info tab is not displayed, click its tab to display it.

    Figure 3-10 Modify LNP System LSMS Component Info Tab

    Modify LNP System LSMS Component Info Tab
  3. In the NPAC Customer SPID field, enter the identification (four alphanumeric characters) by which the LSMS owner is known to the NPACs.
    This required field will be used when the LSMS associates with the NPAC.
  4. Enter the LSMS Component Info data as follows (all fields in the Component Info tab must contain data):
    • Owner ID – ID of the LSMS owner (maximum 20 alphanumeric characters)
    • Platform Type – hardware platform of the LSMS (maximum 20 alphanumeric characters)
    • Platform Supplier – name of the supplier of the LSMS hardware platform (maximum 20 alphanumeric characters)
    • Platform SW Release – release level of the software running on the LSMS platform (maximum 20 alphanumeric characters)
    • Platform Model – model number of the LSMS platform (maximum 20 alphanumeric characters)
  5. Click the Contact Info tab.

    Figure 3-11 Modify LNP System LSMS Contact Info

    img/t_lsms_configuration_components_config_fig3.jpg
  6. All fields in the Contact Info tab are optional.
    If you wish to enter LSMS Contact Info data, do so as follows:
    • Name – name of the person to contact for LSMS information (maximum 40 alphanumeric characters)
    • Email – email address of the LSMS contact person (maximum 60 alphanumeric characters)
    • Street – street address of the LSMS contact person (maximum 40 alphanumeric characters)
    • City – city address of the LSMS contact person (maximum 20 alphanumeric characters)
    • State – state address of the LSMS contact person (two-letter uppercase abbreviation).

      If you use the Province field, enter -- (the default).

    • ZIP Code – postal zip code of the LSMS contact person (five numeric characters)
    • Province – province of the LSMS contact person (two-letter uppercase abbreviation).

      If you use the State field, enter -- (the default).

    • Country – country of the LSMS contact person (maximum 20 alphanumeric characters)
    • Phone Number – phone number of the LSMS contact person (ten numeric characters required)
    • FAX Number – FAX number of the LSMS contact person (ten numeric characters required)
    • Pager Number – pager number of the LSMS contact person (ten numeric characters required)
    • Pager PIN – pager PIN number of the LSMS contact person (ten numeric characters maximum)
  7. When finished, click OK to apply the changes.
    • If the following message appears, click OK in the message window and the GUI will return to the main console window.

      Figure 3-12 Modify Successful

      img/t_lsms_configuration_components_config_fig4.jpg
    • If a message similar to the following appears, a mandatory field is empty or a field is not properly configured.

      Figure 3-13 More Fields Needed

      img/t_lsms_configuration_components_config_fig5.jpg

      Click OK in the message window and correct the appropriate field. Repeat this step until the message in Figure 3-12 displays.

You have now completed this procedure.

Viewing a Configured LSMS Component

To view configured LSMS component information, use the following procedure.

  1. Log in as a user in the lsmsadm, lsmsuser, lsmsuext, lsmsview, or lsmsall group.
  2. From the main menu, select Configure, and then LNP System, and then LSMS , and then View.

    Figure 3-14 LNP System Menu – View LSMS

    img/t_viewing_a_configured_lsms_component_config-fig1.jpg
    The View LNP System LSMS window displays. The window usually opens with the Component Info tab displayed.

    Figure 3-15 View LNP System LSMS Window

    View LNP System LSMS Window
  3. To view a different tab, click on the tab.
    For information about the fields displayed in any of the tabs, see their description in the procedure defined in Modifying LSMS Configuration Components.
  4. When finished viewing this window, click OK to return to the main LSMS console window.
You have now completed this procedure.

EMS Configuration Component

Creating an EMS Configuration Component

For each network element to be supported by the LSMS, create an EMS configuration component using the following procedure.

Note:

For each EMS configuration created, you must perform a bulk download to the associated EMS/network element. Refer to the LNP Database Synchronization User's Guide for bulk loading procedures.
  1. Log into the LSMS as a user in the lsmsadm or lsmsall group.
  2. From the LNP System menu, shown in Figure 3-16, select Configure, and then LNP System, and then EMS, and then Create.

    Figure 3-16 LNP System Menu – Create EMS

    img/t_creating_an_ems_configuration_component_config-fig1.jpg

    The EMS Configuration Component window, Figure 3-17 displays. The window usually opens with the Address Info tab displayed; if the Address Info tab is not displayed, click its tab to display it.

    Figure 3-17 Create LNP System EMS Address Info Tab

    img/figure-37-ems-address-info.jpg
  3. Ensure that the radio button for an ELAPMPS or a TekPath MPS is selected. For an ELAPMPS (ELAP version 7 or older), enter the IP addresses for MPS A and MPS B (enter a value from 0 to 255 in each of the first three octets and a value from 0 to 254 in the forth octet). For a TekPath MPS, enter the IP address for MPS A only.

    Note:

    The LSMS no longer supports connections to OAPs.
  4. Select one of the following radio buttons for the Verify MPS with PING field to specify whether the LSMS uses PING to monitor the connectivity between the LSMS and the MPS.

    Note:

    With either selection, the LSMS always monitors connectivity with the keep alive function.
    • Enabled to monitor the MPS by sending PINGs over the UDP port. This selection requires an additional port to be open (which can be a security concern), but supports previously available function.
    • Disabled to monitor the MPS using only the keep alive function. This selection reduces the number of ports required to be open inbound to the ELAP network. Security is increased when the number of open ports is decreased.

    Note:

    The LSMS/EMS PING Enhancement feature provides the following functionality:
    • Prevents intermediate devices (for example, routers and switches) from closing idle HSOP connections
    • Detects low level network faults that were previously not detectable using the TCP/IP stack alone.
  5. Click the Component Info tab, shown in Figure 3-19.

    Figure 3-18 Create LNP System EMS Component Info

    img/c_creating_an_ems_configuration_component_config-fig3.jpg
  6. Enter the Component Info data as follows (all fields in this tab must contain data):

    • Owner ID – ID of the network element owner (maximum 20 alphanumeric characters)

    • Platform Type – hardware platform of the network element (maximum 20 alphanumeric characters)

    • Platform Supplier – name of the supplier of the network element hardware platform (maximum 20 alphanumeric characters)

    • Platform SW Release – release level of the software running on the network element platform (maximum 20 alphanumeric characters)

    • Platform Model – model number of the network element platform (maximum 20 alphanumeric characters)

    • CLLI – CLLI code of the network element (maximum 11 numeric and uppercase alphabetic characters)

    • Mate CLLI– CLLI of the mate EMS component (maximum 11 numeric and uppercase alphabetic characters)

    • PC – point code of the EMS component (must contain three 3-digit octets; first octet must have a value from 1 to 255; last two octets must have a value from 0 to 255; second octet must not be 001 if the first octet has a value from 1 to 5)

    • Mate PC – point code of the mate EMS component (must contain three 3-digit octets; first octet must have a value from 1 to 255; last two octets must have a value from 0 to 255; second octet must not be 001 if the first octet has a value from 1 to 5)

    • LNP Capability PC – LNP capability point code of the network element (must contain three 3-digit octets; first octet must have a value from 1 to 255; last two octets must have a value from 0 to 255; second octet must not be 001 if the first octet has a value from 1 to 5)

  7. Click the Contact Info tab, shown in Figure 3-18.

    Figure 3-19 Create LNP System EMS Contact Info

    img/c_creating_an_ems_configuration_component_config-fig4.jpg
  8. All fields in this tab are optional. If you wish to enter the Contact Info data, do so as follows:

    • Name – name of the person to contact for network element information (maximum 40 alphanumeric characters)

    • Email – email address of the network element contact person (maximum 60 alphanumeric characters)

    • Street – street address of the network element contact person (maximum 40 alphanumeric characters)

    • City – city address of the network element contact person (maximum 20 alphanumeric characters)

    • State – state address of the network element contact person (two-letter uppercase abbreviation). If you use the Province field, enter -- (the default).

    • ZIP Code – the postal zip code of the network element contact person (five numeric characters)

    • Province – the province of the network element contact person (two-letter uppercase abbreviation). If you use the State field, enter -- (the default).

    • Country – country of the network element contact person (maximum 20 alphanumeric characters).

    • Phone Number – phone number of the network element contact person (ten numeric characters required).

    • FAX Number – FAX number of the network element contact person (ten numeric characters required).

    • Pager Number – pager number of the network element contact person (ten numeric characters required)

    • Pager PIN– pager PIN number of the network element contact person (ten numeric characters maximum)

  9. When finished, click OK to apply the changes.

    • If the Update Successful dialog, Figure 3-20 appears, click OK. The GUI returns to the main console window.

      Figure 3-20 Update Successful Dialog

      img/c_creating_an_ems_configuration_component_config-fig5.jpg

    • When a mandatory field is empty or a field is not properly configured, the Field Required Figure 3-21 dialog displays.

      Figure 3-21 Field Required Dialog

      img/c_creating_an_ems_configuration_component_config-fig6.jpg

      Click OK and correct the appropriate field.

      Repeat this step until you receive an Update Successful notification.

Modifying an EMS Configuration Component

To modify an existing EMS configuration component, use the following procedure.

Note:

For each EMS configuration created, you must perform a bulk download to the associated EMS/network element. Refer to the LNP Database Synchronization User's Guide for bulk loading procedures.
  1. Log into the LSMS as a user in the lsmsadm or lsmsall group.
  2. Click the EMS status icon for the EMS you wish to modify so that the icon is highlighted.
  3. From the Main Menu, select Configure, and then LNP System, and then EMS, and then Modify, as shown in Figure 3-22.

    Figure 3-22 LNP System Menu – Modify EMS

    img/t_modifying_an_ems_configuration_component_config-fig1.jpg
    The Modify LNP System EMS window, Figure 3-23, appears.

    Figure 3-23 Modify LNP System EMS Window

    img/c_modifying_an_ems_configuration_component_config-fig2a.jpg
    The window usually opens with the Address Info tab displayed; if the Address Info tab is not displayed, click its tab to display it.
  4. Modify the EMS data as required.
    See Creating an EMS Configuration Component for detailed field information.
  5. Click OK.
    The EMS Routing dialog appears, Figure 3-24 .

    Figure 3-24 EMS Routing Dialog

    img/t_modifying_an_ems_configuration_component_config-fig3.jpg
    Click OK.

    The Update Successful dialog displays, Figure 3-25.

    Figure 3-25 Update Successful Dialog

    img/t_modifying_an_ems_configuration_component_config-fig4.jpg
You have completed this procedure.
If a mandatory field is empty or a field is not properly configured, the More Fields Needed message is displayed, Figure 3-26.

Figure 3-26 More Fields Needed Dialog

img/t_modifying_an_ems_configuration_component_config-fig5.jpg

Click OK and correct the appropriate field.

Repeat this step until you receive an Update Successful notification.

Note:

Changes do not take effect until the eagleagent is restarted (refer to "Manually Verifying and Restarting the Eagle Agents" in the Alarms and Maintenance Guide).

Viewing an EMS Configuration Component

To view EMS configuration component information, use the following procedure.

  1. Log into the LSMS as a user in the lsmsview, lsmsuser, lsmsuext, or lsmsadm group.
  2. Click the EMS status icon for the EMS you wish to view (highlight the icon).
  3. From the Main Menu, select Configure, and then LNP System, and then EMS, and then View.
    The View LNP System EMS dialog displays, Figure 3-27.

    Figure 3-27 View LNP System EMS Dialog

    img/figure-47-view-ems.jpg
  4. Click on any of the tabs to view additional information.
    For more information about the meaning of the fields on any of the tabs, see Creating an EMS Configuration Component.

    Note:

    You cannot modify information in any of the tabs.
  5. When finished viewing, click OK.

Deleting an EMS Configuration Component

To delete an EMS configuration component, use the following procedure.

  1. Log into the LSMS as a user in the lsmsadm or lsmsall group.
  2. Click the EMS Status icon for the EMS you wish to delete (highlight the icon).
  3. From the Main Menu, select Configure, and then LNP System, and then EMS, and then Delete.
    The Delete LNP EMS dialog displays, Figure 3-28.

    Figure 3-28 Delete LNP System EMS Dialog

    img/figure-48-delete-ems.jpg
  4. View the information in this window to verify that this is the EMS you wish to delete.
    Click on any of the tabs to view additional information. For more information about the meaning of the fields on any of the tabs, see Creating an EMS Configuration Component. You cannot modify information in any of the tabs.
  5. Click OK or Cancel.
    • If you click Cancel, you are returned to the LSMS console window.
    • If you click OK, the Update Successful dialog displays, Figure 3-29.

    Figure 3-29 Update Successful Dialog

    img/t_deleting_an_ems_configuration_component_config-fig2.jpg
  6. Click OK.

Using Key Lists

LSMS maintains a list of keys for each NPAC Service Management System. You use a key list to secure encrypted communications between the LSMS and its associated NPACs.

Key lists are loaded whenever one of the following occurs:

  • LSMS is initially configured

  • The system administrator issues the appropriate key list commands

The LSMS system administrator can view any key list in his system. Key lists can be exchanged off-line to ensure security. Each key list has an assigned expiration date.

During an LSMS GUI session configuration, you load these lists as directed by the LSMS system administrator. You must fully configure one GUI session (including loading key lists) for each NPAC associated with the LSMS.

Use the following procedures to generate a key list, load an NPAC key list, and load an LSMS key list.

Generating a Key List

Each NPAC and LSMS generates a key list for use by the other side. That is, each NPAC generates a key list to be transferred to LSMS for decrypting the message signature sent from NPAC. The LSMS generates key lists that are transferred to the NPAC for decrypting LSMS message signatures sent from LSMS.

The keys in a key list are actually the public key component of a private/public key pair. The originating side keeps the private key component for encrypting the signature when transferred to the receiving side.

A key list contains exactly 1000 keys. Before an originating side can communicate with a receiving side, the receiving side must acknowledge the keys within a key list. For example, if LSMS sends a set of keys to the NPAC, the NPAC creates a file with a checksum for each of the 1000 keys in the list. This newly created file can then be used to acknowledge the keys in the list that were sent to the NPAC.

The following procedure explains how to generate a key list for the NPAC. An overview of the key list creation process is shown below.

Figure 3-30 Flowchart for Generating a Key List

img/t_generating_a_key_list_config_fig1.jpg
  1. Log in to the primary server with a username of lsmsadm.
    (For information about logging into an LSMS server, refer to the Alarms and Maintenance Guide)
  2. Change to the tools directory:
    $ cd $LSMS_TOOLS_DIR
  3. Type the lnpGenKey command, and use the following instructions.
    $ ./lnpGenKey <SPID> <ListID> <ListName> <Modulus>
    where:
    <SPID>
    Service provider ID—use the same value as specified for the NPAC Customer SPID in step 3 in the procedure described in Modifying LSMS Configuration Components.
    <ListID>
    List ID—a digit indicating which set of key lists is being created. For the first list use 1, and increment this value by 1 each time you create a new set of key list files.
    <ListName>
    Name of the key list—give the key list a name that helps identify the contents of the files. For example, KEYLIST_TKLC_2 would identify the resulting files as second key list files created for the service provider TKLC.
    <Modulus>

    Modulus size in bytes. Specify one of the following:

    • 80 for 640-bit keys

    • 128 for 1024-bit keys

    This command generates two new files, one for public use and one for private use. For example, if you specified the <ListName> as KEYLIST_TKLC_2, you would receive two files called KEYLIST_TKLC_2.public and KEYLIST_TKLC_2.private.
  4. Send the public file that was created in the previous step to the NPAC. (For example, you would send the KEYLIST_TKLC_2.public to the NPAC.)
    The key files are binary files. You must use SFTP or e-mail facilities to exchange key list files between the LSMS and the NPAC. You can use the FTP client on an LSMS server, and FTP from LSMS to the NPAC. If you use FTP, be sure to use binary mode so that the files are not corrupted.

    NPAC sends you a corresponding NPAC public key file. The NPAC determines the actual file name of this file. Store the NPAC public key file in the $LSMS_TOOLS_DIR directory.

  5. Use the lnpGenAck command to prepare an acknowledgment of the NPAC public key file by typing the following:
    $ ./lnpGenAck <NPAC_public> <file>.ack <SPID>

    where, <NPAC_public> is the name of the file you received from the NPAC, <file>.ack is the name of the acknowledgment file you are creating, and < SPID > is your service provider ID. This command generates two files: an acknowledgment file and a file for the LSMS database.

    Following is an example of the above command:

    $ ./lnpGenAck NPAC_public TKLC.ack TKLC

    This command produces an acknowledgment file, called TKLC.ack in this example, and a database file, called <NPAC_public>.key.

  6. Send the TKLC.ack to the NPAC and receive the corresponding NPAC acknowledgment file, called hash file, into the $LSMS_TOOLS_DIR directory.
  7. If NPAC is iconectiv, then repair the NPAC acknowledgment file. If NPAC is not iconectiv, skip to the next step.
    $ ./iconectivAckRepair <hash_file> <SPID>

    Where <hash_file> is the acknowledgement file received from the iconectiv NPAC and <SPID> is same as used in step 3.

    This command repairs the iconectiv acknowledgment file and replaces the NPAC region ID with the SPID. Example:

    $ ./iconectivAckRepair VL07-psel-1.keys.Public.ACK VL07

  8. Verify the received NPAC acknowledgment and generate the private key file with the command below:
    $ ./lnpVerifyAck <ListName>.private <ListName>.public <hash file>

    This command generates the second file to be loaded into the database, <ListName>.private.key.

  9. Copy <NPAC_public>.key and <ListName>.private.key to /var/TKLC/lsms/free.
    $ cp <ListName>.private.key <NPAC_public>.key /usr/TKLC/lsms/free
  10. Load the key files to the LSMS GUI. The key files are located in the /var/TKLC/lsms/free directory.
    See “Loading an NPAC Key List” and “Loading an LSMS Key List” for instructions about how to load the key files to the LSMS GUI.

Loading an NPAC Key List

To load an NPAC public key list into the LSMS database, use either of the procedures described in the following sections:

Using the keyutil Command to Load an NPAC Key List

To use the keyutil command to load an NPAC public key list into the LSMS database, use this procedure. Use this command once for the active server; the standby server will be updated with the replicated list automatically.

  1. Log into the active server with the user name lsmsadm.
  2. Enter the following command, where is <region> the name of the NPAC region and <NPAC_public> is the name of the file received from the NPAC.
    $ keyutil -r <region> -k public -l <NPAC_public>.key
Using the GUI to Load an NPAC Key List

To use the GUI to load an NPAC public key list into the LSMS database, use this procedure.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the main menu, select Keys, and then NPAC Keys.

    Figure 3-31 Keys System Menu – Load NPAC

    img/t_using_the_gui_to_load_an_npac_key_list_config-fig1.jpg
    The Load NPAC Keys window displays.

    Figure 3-32 Load NPAC Keys Window

    img/t_using_the_gui_to_load_an_npac_key_list_config-fig2.jpg
  3. Click the down arrow shown in the NPAC Region field to display the regions.
    Then click the region for which you want to load keys.

    Figure 3-33 Load NPAC Keys, Select Region Window

    img/t_using_the_gui_to_load_an_npac_key_list_config-fig3.jpg
  4. Enter the name of the Key File that you created in the procedure described in “Generating a Key List”.
    (Alternatively, click the Browse button to display all the keys files for this region, then click the file name, and then click Open; the file name then appears in the Key File field.)
  5. Click OK to load the selected key list file and return to the main LSMS console window or click Apply to load the selected key list file and keep the Load NPAC Keys window open.

Loading an LSMS Key List

To load an LSMS public key list into the LSMS database, use either of the procedures described in the following sections:

Using the keyutil Command to Load an LSMS Key List

To use the keyutil command to load an NPAC public key list into the LSMS database, use the following procedure.

  1. Log into the active server as lsmsadm.
  2. Enter the following command, where is <region> the name of the NPAC region and <ListName> is the name of the private key file generated by the lnpGenKey command.
    $ keyutil -r <region> -k private -l <ListName>.private.key
Using the GUI to Load an LSMS Key List

To use the GUI to load an LSMS private key list into the LSMS database, use the following procedure.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. From the main menu, select Keys, and then LSMS Keys.
    The Load LSMS Keys window displays.

    Figure 3-34 Load LSMS Keys Window

    img/t_using_the_gui_to_load_an_lsms_key_list_config-fig1.jpg
  3. Click the down arrow shown in the NPAC Region field to display the regions.
    Then click the region for which you want to load keys.

    Figure 3-35 Load LSMS Keys, Select Region Window

    img/t_using_the_gui_to_load_an_lsms_key_list_config-fig2.jpg
  4. Enter the name of the Key File that you created in the procedure described in “Generating a Key List”.
    (Alternatively, click the Browse button to display all the keys files for this region, then double-click the desired file name or click the file name, and then click Open; the file name then appears in the Key File field.)
  5. Click OK to load the selected key list file and return to the main LSMS console window or click Apply to load the selected key list file and keep the Load NPAC Keys window open.

NPAC Component Configuration

Use the following procedures to manage NPAC component configuration:

Configuring iconectiv NPAC

The iconectiv NPAC compatibility feature makes the LSMS compatible with the iconectiv NPAC. Configurable options allow the user to specify if a region is connected to Neustar or iconectiv NPAC. The default value of the new configuration option is "N" to signify Neustar NPAC. The end user is able to set the value of the new configuration option per region to Y (for iconectiv).

The format is as follows: <Region Name>_ICONECTIV (for example, MIDWEST_ICONECTIV). To enable a region to connect to iconectiv NPAC, complete the following steps:

  1. Use the dbcfginternal utility and set the corresponding configuration value to yes (Y): 
    $ dbcfginternal <Region Name>_ICONECTIV Y

    For example, to connect the Midwest region to iconectiv NPAC, set MIDWEST_ICONECTIV to Y: 

    $ dbcfginternal MIDWEST_ICONECTIV Y
Note: npacagent has to be restarted for this feature to take
effect.
Update complete.
  2. Restart the npacagent for the Midwest region as: 
    $ lsms stop Midwest
$ lsms start Midwest

There is an audit script to identify the number of NPACs that are connected to iconectiv and Neustar. See Database Administrator's Guide for the NPAC Audit Report.

Modifying an NPAC Component

Use the following procedure to create or modify component configuration for an NPAC. Create components for both the primary NPAC SMS and the secondary NPAC SMS of the regional NPAC.

  1. Log in as a user in the lsmsadm or lsmsall group.
  2. If you are creating an NPAC for the first time, perform this step and step 3.
    (Otherwise, skip to step 4.) Right-click anywhere in the NPAC status area; the pop-menu shown in Figure 3-36 displays.

    Figure 3-36 Displaying Inactive Regions

    img/t_modifying_an_npac_component_config_fig1.jpg
  3. Click a region for which you have purchased support.
    The main console window displays.

    Figure 3-37 NPAC Status Icons Displayed

    img/t_modifying_an_npac_component_config_fig2.jpg
  4. Click the icon that represents the NPAC you wish to create or modify so that the icon is highlighted.
  5. From the main menu, select Configure, and then LNP System, and then NPAC , and then Modify, and then Primary or Configure, and then LNP System, and then NPAC , and then Modify, and then Secondary.

    Figure 3-38 LNP System Menu – Modify NPAC

    img/t_modifying_an_npac_component_config_fig3.jpg
    The Modify LNP System NPAC window displays. In this example, the Primary was selected. The window usually opens with the Address Info tab displayed; if the Address Info tab is not displayed, click its tab to display it.

    Figure 3-39 Modify LNP System NPAC Address Info Tab

    img/t_modifying_an_npac_component_config_fig4.jpg
  6. Enter the SMS Name which represents the name by which the NPAC knows this region (maximum of 40 characters)
  7. Click the Activate Region checkbox to make this region active.

    Note:

    Ensure that you have loaded the keys for this region before performing this step. When the Activate Region checkbox is checked, the sentryd process will automatically launch the NPAC agent for this region and attempt to associate with the NPAC. If the keys have not been loaded, the association will fail.
  8. Enter the Address information as follows (all fields in the Address Info tab, except the TSEL fields, must contain data):

    Note:

    Changes on this tab will take effect only after you reassociated with the NPAC.
    • Enter the NPAC OSI Address elements with values that you have obtained from the NPAC:
      • PSEL – presentation address (one to four alphanumeric characters)
      • SSEL – session address (one to four alphanumeric characters)
      • TSEL – transport address (zero to four alphanumeric characters)
      • NSAP – network address.
        This value is the IP address of the NPAC. Example: For an IP address of 198.89.35.235, enter 0xc65923eb, as shown below:

        Table 3-3 Decimal to Hexadecimal Conversion

        Decimal

        		  

        198

        89

        35

        235

        Hexadecimal

        0x

        c6

        59

        23

        eb
    • The display of the LSMS OSI Address elements is for your information (user input is not accepted for these elements):
      • PSEL – presentation address (one to four alphanumeric characters)
      • SSEL – session address (one to four alphanumeric characters)
      • TSEL – this field must be blank
      • NSAP – network address. Enter rk6
    • Enter the NPAC FTP address as follows:
      • FTP Address – the FTP address (IP address) of this NPAC component (enter a value from 0 to 255 in each of the first three octets and a value from 0 to 254 in the fourth octet)
  9. Click the Component Info tab.

    Figure 3-40 Modify LNP System NPAC Component Info

    img/t_modifying_an_npac_component_config_fig5.jpg
  10. Enter the NPAC Component Info items as follows (all fields in the Component Info tab must contain data):
    • Owner ID – ID of the NPAC owner (maximum 20 alphanumeric characters)
    • Platform Type – hardware platform of the NPAC (maximum 20 alphanumeric characters)
    • Platform Supplier – name of the supplier of the NPAC hardware platform (maximum 20 alphanumeric characters)
    • Platform SW Release – release level of the software running on the NPAC platform (maximum 16 alphanumeric characters): enter 3.0 to connect an LSMS region with any NANC 3.x compliant NPAC
    • Platform Model – model number of the NPAC platform (maximum 20 alphanumeric characters)
  11. Click the Contact Info tab.

    Figure 3-41 Modify LNP System NPAC Contact Info

    img/t_modifying_an_npac_component_config_fig6.jpg
  12. All fields in the Contact Info tab are optional.
    If you wish to enter NPAC Contact Info data, do so as follows:
    • Name – name of the person to contact for NPAC information (maximum 40 alphanumeric characters)
    • Email – email address of the NPAC contact person (maximum 60 alphanumeric characters)
    • Street – street address of the NPAC contact person (maximum 40 alphanumeric characters)
    • City – city address of the NPAC contact person (maximum 20 alphanumeric characters)
    • State – state address of the NPAC contact person (two-letter uppercase abbreviation).

      If you use the Province field, enter -- into this mandatory field.

    • ZIP Code – postal zip code of the NPAC contact person (five numeric characters)
    • Province – province of the NPAC contact person (two-letter uppercase abbreviation).

      If you use the State field, enter -- (the default) into this mandatory field.

    • Country – country of the NPAC contact person (maximum 20 alphanumeric characters)
    • Phone Number – phone number of the NPAC contact person (ten numeric characters required)
    • FAX Number – FAX phone number of the NPAC contact person (ten numeric characters required)
    • Pager Number – pager number of the NPAC contact person (ten numeric characters required)
    • Pager PIN – pager PIN number of the NPAC contact person (ten numeric characters maximum)
  13. The Comm Info tab is for display purposes only to provide the following information.
    You cannot modify these fields.

    Figure 3-42 Modify LNP System NPAC Communication Info

    img/t_modifying_an_npac_component_config_fig7.jpg
    • All NPAC Requests
      • Retry—How many times the LSMS will retry a request that the NPAC fails to respond to
      • Retry—How long the LSMS will wait for the NPAC respond to a request
    • NPAC Recovery Request Only
      • Retry—How many times the LSMS will retry a recovery request that the NPAC fails to respond to
      • Retry—How long the LSMS will wait for the NPAC respond to a recovery request
  14. When you are finished, click OK to apply the changes and return to the LSMS Console window.
  15. When finished, click OK to apply the changes.
    • If the following message appears, click OK in the message window and the GUI will return to the main console window.

      Figure 3-43 Modify Successful

      img/t_modifying_an_npac_component_config_fig8.jpg
    • If a message similar to the following appears, a mandatory field is empty or a field is not properly configured.

      Figure 3-44 More Fields Needed

      img/t_modifying_an_npac_component_config_fig9.jpg

      Click OK in the message window and correct the appropriate field. Repeat this step until the message in Figure 3-43 displays.

      Note:

      If you changed values on the Address Info tab, you must abort and reassociate the NPAC association in order for the modifications to take effect.
You have now completed this procedure.

Viewing a Configured NPAC Component

To view configured NPAC component information, use the following procedure.

  1. Log in as a user in the lsmsadm, lsmsuser, lsmsuext, lsmsview, or lsmsall group.
  2. Click the icon that represents the NPAC you wish to view so that the icon is highlighted.
  3. From the main menu, select Configure, and then LNP System, and then NPAC , and then View, and then Primary or Configure, and then LNP System, and then NPAC , and then View, and then Secondary.

    Figure 3-45 LNP System Menu – View NPAC

    img/t_viewing_a_configured_npac_component_config-fig1.jpg
    The View LNP System NPAC window displays. In this example, the Primary was selected. The window usually opens with the Address Info tab displayed.

    Figure 3-46 View LNP System NPAC Window

    img/t_viewing_a_configured_npac_component_config-fig2.jpg
  4. To view a different tab, click on the tab.
    For information about the fields displayed in any of the tabs, see their description in the procedure defined in “Modifying an NPAC Component”.
  5. When finished viewing this window, click OK to return to the main LSMS console window.

Removing a Region

Note:

All the examples are shown for the Southeast region. Southeast can be replaced with <Region name>, which you want to remove.

Perform the following steps to remove a region from the LSMS system:

  1. Verify that the NPAC database exists for the region that we want to delete using the following command:
    $ lsmsdb -c counts | grep Southeast
0 ............. SoutheastDB.NumberPoolBlock
0 ............. SoutheastDB.ServiceProvLRN
0 ............. SoutheastDB.ServiceProvNPA_NXX
0 ............. SoutheastDB.ServiceProvNPA_NXX_X
2 ............. SoutheastDB.ServiceProvNetwork
0 ............. SoutheastDB.SubscriptionVersion
7 ............. supDB.SoutheastNpacMeasurements
1,000 ......... supDB.SoutheastPrivateKey
1,000 ......... supDB.SoutheastPublicKey
  2. Stop the region using the following command:
    $ lsms stop Southeast

Checking if npacagent is running....Yes.

Stopping npacagent....
OK.

npacagent stopped:  Wed Aug  4 08:16:02 2021

Command complete.
  3. Deactivate the region from the LSMS GUI:
    Modify the NPAC configuration:

    Figure 3-47 LSMS Console


    LSMS Console

    Uncheck Activate region and press OK

    Figure 3-48 Modify LNP System NPAC


    Modify LNP System NPAC

    The NPAC region status will get changed to Inactive.

    Figure 3-49 NPAC Region Status


    NPAC Region Status

  4. Delete the NPAC database for the region using the following command:
    $ npac_db_setup remove Southeast
------------------------------------------------------------
NPAC Region Database Setup Script

The Region Database name is SoutheastDB

WARNING: NPAC region database SoutheastDB is about to be removed.
        All data in this database will be lost.
        Do you want to continue? [Y/N]Y

Removing NPAC region database ...SoutheastDB
  5. Verify that the NPAC database is deleted for the region using the following command:
    $ lsmsdb -c counts | grep Southeast
7 ............. supDB.SoutheastNpacMeasurements
1,000 ......... supDB.SoutheastPrivateKey
1,000 ......... supDB.SoutheastPublicKey

Modifying Default TT/SSN Values

If desired, use the following procedure to modify the default Translation Type (TT) and SS7 Subsystem Number (SSN) values for a given GTT group. Using default settings can simplify the amount of data entry required when creating Default GTTs and Override GTTs (for information about managing Default GTTs and Override GTTs, refer to the Database Administrator's Guide).

  1. Log in as a user in the lsmsadm, lsmsall, or lsmsuext group (if you are logging in as a user in the lsmsuext group, you are authorized to modify only Default TT/SSN values for GTT groups that are assigned to the SPID you used when you logged in).
  2. From the main menu, select Configure, and then Default TT/SSN.

    Figure 3-50 Modify Default TT/SSN Values

    img/t_modifying_default_tt_ssn_values_config_fig1.jpg
    The Default TT/SSN Values window displays.

    Figure 3-51 Default TT/SSN Values Window

    img/t_modifying_default_tt_ssn_values_config_fig2.jpg
  3. If the GTT Group whose default values you wish to modify is not displayed in the GTT Group field, click the down arrow at the right of the field and select the desired GTT Group.
  4. To change any TT or SSN value, click in the desired table cell; the cell is highlighted while the rest of the row displays in a darker shade, as shown in the example in Figure 3-52.

    Figure 3-52 Changing Default TT/SSN Values

    img/t_modifying_default_tt_ssn_values_config_fig3.jpg
    The TT and SSN values must be as follow:
    • TT —Range 1–255
    • SSN —Range 0–255, excluding 1 (0 indicates no SSN translation)
  5. Repeat 4 for any other TT or SSN values that you wish to change.
  6. When you are finished, click Apply to apply the changes and stay in this window, or click OK to apply the changes and return to the LSMS Console window.
    • If the following message appears, click OK in the message window and the GUI will return either to the Default TT/SSN Values window or to the main console window.

    Figure 3-53 Modify Successful

    img/t_modifying_default_tt_ssn_values_config_fig4.jpg
    • If a message similar to the following appears, a mandatory field is empty or a field is not properly configured.

    Figure 3-54 More Fields Needed

    img/t_modifying_default_tt_ssn_values_config_fig5.jpg

    Click OK in the message window and correct the appropriate field. Repeat this step until the message in Figure 3-53 displays.

Working with NPAC Associations

Ordinarily, NPAC associations are managed automatically by the sentry utility, according to the setting of the Activate Region checkbox in the Modify LNP System NPAC window (see Figure 3-39). This section explains how to manually create or abort NPAC associations. You can use the LSMS GUI interface to perform both of these procedures. You can also use the command line utility, lsmsclaa, to create and abort NPAC associations.

The following topics are covered in this discussion of the NPAC associations:

Creating an NPAC Association

To create an NPAC association with the LSMS, see either of the following: For either procedure, you must be logged in to the LSMS as an lsmsadm or lsmsall user.
Creating an NPAC Association Using GUI

To create an NPAC association with the LSMS using the GUI, perform the following procedure:

  1. Log in to LSMS as a member of the permission group that is authorized to perform this operation.
  2. Click the icon that represents the NPAC that you wish to associate with; then right-click and select Associate.

    Figure 3-55 Associate with NPAC

    img/t_creating_an_npac_association_using_gui_config_fig1.jpg
    When the LSMS has finished associating with the NPAC, the NPAC status icon displays the text “Associated.”
Creating an NPAC Association Using Command-Line Interface

To create an NPAC association with the LSMS using the optional command-line interface, perform the following procedure:

  1. Ensure that the command-line interface was started for the region to association with by a user logged in as lsmsadm or lsmsall (for more information about starting the command-line interface, see “Starting the Command Line Interface”).
    The following prompt indicates that the command-line interface is started: 
    
Enter command ->
  2. Enter the following at the command-line interface prompt:Enter Command -> ASSOCIATE <NPAC>
    where <NPAC> is either PRIMARY or SECONDARY. The command-line interface utility translates this value to the proper NPACID.The command-line interface displays a message to indicate whether the association was successful. For more information about the possible messages, refer to the Alarms and Maintenance manual.
  3. If desired, you can verify the association by entering the following commands:
    • Exit the command-line interface by entering the following command:

      Enter Command -> EXIT

      The standard Linux prompt appears.

    • Verify the status of the association by entering the following command, where <REGION> is the same value as you used to start the command-line interface:

      $LSMS_DIR/lsms status <REGION>

    Output similar to the following example indicates that the association was successful:

    
Checking if npacagent is running....Yes.
npacagent Canada: mem= 24424 kbytes : pcpu 0.0 %
Log Directory: /usr/LSMS/logs/Canada
Connected to primary NPAC
Command complete.

Aborting an NPAC Association

The abort function breaks the association attempt between the LSMS and the NPAC by transmitting the abort command to the NPAC.

To abort an NPAC association attempt, see either of the following: For either procedure, you must be logged in to the LSMS as an lsmsadm or lsmsall user.
Aborting an NPAC Association Using GUI

To abort an NPAC association with the LSMS using the GUI, perform the following procedure:

  1. Log in to LSMS as a member of the permission group that is authorized to perform this operation.
  2. Click the icon that represents the NPAC whose association you wish to abort; then right-click and select Abort.
  3. When the LSMS has finished aborting the association with the NPAC, the NPAC status icon displays the text “Not Connected.”
Aborting an NPAC Association Using Command-Line Interface

To abort an NPAC association with the LSMS using the optional command-line interface, perform the following procedure:

  1. Ensure that the command-line interface was started for the region to abort the association with by a user logged in as lsmsadm or lsmsall (for information about starting the command-line interface, see “Starting the Command Line Interface”).
    The following prompt indicates that the command-line interface is started: 
    
Enter command ->
  2. Enter the following at the command-line interface prompt:
    Enter Command -> ABORT
  3. The command-line interface displays a message to indicate whether the abort was successful.
    For more information about the possible messages, refer to the Alarms and Maintenance Guide.
  4. If desired, you can verify the aborted association by entering the following commands:
    • Exit the command-line interface by entering the following command:

      Enter Command -> EXIT

      The standard Linux prompt appears.

    • Verify the status of the association by entering the following command, where <REGION> is the same value as you used to start the command-line interface:

      $LSMS_DIR/lsms status <REGION>

      
Checking if npacagent is running....Yes.
npacagent Canada: mem= 24424 kbytes : pcpu 0.0 %
Log Directory: /usr/LSMSlogs/Canada
No connection to NPAC.
Command complete.

Postfix

Postfix is an alternative mail program to the Sendmail program.

Note:

The Postfix daemon must be restarted manually after any operation that causes the host to reboot. Postfix is disabled by default.

The normal configuration of Postfix requires DNS (Domain Name System). Postfix uses fully qualified hostnames for source and destination resolution.

Note:

The Postfix configuration affects only the local server.

The following topics are covered in this discussion of Postfix.

Configuring Postfix

Modifications to the Postfix configuration files or aliases database require the Postfix utility to be restarted. To configure Postfix, perform the following procedure:

Caution:

Loss of data can result if you do not properly configure Postfix. For technical assistance, call the Customer Care Center.
  1. Add the LSMS host to the private DNS space.
  2. To configure Postfix, the /etc/resolv.conf file needs to be modified if the nameserver is needed to resolve hostnames.
    Here is an example of /etc/resolv.conf modifications.

    Table 3-4 Table of Domain and Name Server Addresses

    Information Type Sample Addresses

    domain

    nc.tekelec.com

    nameserver

    10.20.1.11
  3. The Postfix main.cf configuration file specifies a small subset of all parameters that control the operation of the Postfix mail system.
    Parameters not explicitly specified remain at their default values. The main.cf file, which is self-documenting, requires a fully qualified hostname. Table 3-5 shows the minimum required settings for the /etc/postfix/main.cf configuration file parameters.

    Table 3-5 Table of Postfix Configuration Parameters

    Parameter Sample Addresses

    myhostname

    localhost

    #myhostname

    virtual.domain.tld

    inet_interfaces

    all (or specific network Ethernet port)

    mydestination

    lsmspri.localhost

    relayhost

    #relayhost

    #relayhost

    #relayhost

    #relayhost

    #relayhost

    (optional)

    smtp.tekelec.com

    $mydomain

    [gateway.my.domain]

    [mailserver.isp.tld]

    uucphost

    [an.ip.add.ress]
  4. When you have performed the previous steps and recorded the indicated information, you have completed the required parameters.
    You may specify optional parameters if desired. Call the Customer Care Center for assistance, if needed.

    Note:

    For complete Postfix details, refer to the man pages on the LSMS system.

Starting and Stopping Postfix

To start Postfix, use this command:

# /usr/sbin/postfix start

To stop Postfix, use this command:

# /usr/sbin/postfix stop

Note:

The user must be root to start and stop Postfix.

Postfix Online Help

Refer to the following Internet address for Postfix online help:

http://www.postfix.org