Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c87bd7898a017be2475bca0007, userName='null'}
JIRAIDAUTHDSC-21341
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85e00fa, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc1e0747, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85f4199b1015f81e9551e0017, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c8637b11640163b0313b5e004b, userName='null'}

Prerequisites

It is assumed that before you execute the initial configuration procedure on a DSC SWe (on OpenStack), you have completed the following tasks:

...


Multiexcerpt include
MultiExcerptNamePrerequisite Initial Config
PageWithExcerptExecuting the Initial Configuration

After you have completed the initial configuration procedures described in this section, if required, you can change the default Point Code Emulator (PCE) NA values to any unique value from 1 to 99. The default PCE NA settings are recommended unless they are already in use by existing configurations and the PCE support creates a conflict. The PCE supports Basic and Enhanced licensing options. A Basic license allows for one public (NA 1) and one private (NA 2) network. The Enhanced license allows for one public (NA 1) network and two private networks (NA 2 and NA 3). The Enhanced PCE is used in networks that are migrating traffic from an existing switch to a new switch. In this configuration, the existing switch and the new switch may have the same Local Point Code (LPC) and are able to transmit SS7 signaling to one another.

For more information about PCE, see the appropriate section in the SS7 Application Guide 2.

pagebreak

Anchor
To configure pce_1 and pce_2
To configure pce_1 and pce_2

...

Configure pce_1 and pce_2


Noprint

Click to read more...

Toggle Cloak


Cloak


 

  1. SSH to one of the Routing and Management VMs.    

    Tip

    Do not use the shared IP address for logging onto the Routing and Management VMs. 


  2. From the Linux prompt of the Command Line Interface (CLI), enter startmenu.



  3. Select 2 and press ENTER.



  4. Select 2 and press ENTER.



  5. Select 1 and press ENTER.



  6. Select 1 for pkt0 and press ENTER.



  7. Select 3 and press ENTER.



  8. Do the following:
     
    1. Depending on whether you are configuring this interface for ipv4 or ipv6, enter n or y and press ENTER.
      In this example, n for ipv4.

    2. Enter the IP Address for the interface pkt0 and press ENTER.

    3. Enter pce_1 for the new alias and press ENTER.

    4. Enter the original IP address of pkt0 for the New IP and press ENTER.

      Tip

      Do not change the original IP address.


    5. Enter the appropriate Netmask and press ENTER.



  9. Enter y if the information is correct and press ENTER.

    Tip

    If the information you entered is incorrect, enter n and press ENTER. You are prompted to re-enter the information from step 8.




  10. Press ENTER.



  11. Select b-Back and press ENTER.



  12. Select 2 for pkt1 and press ENTER.



  13. Select 3 and press ENTER.



  14. Do the following:

    1. Depending on whether you are configuring this interface for ipv4 or ipv6, enter n or y and press ENTER.
      In this example, n for ipv4.

    2. Enter the IP address for the interface pkt1 and press ENTER.

    3. Enter pce_2 for the new alias and press ENTER.

    4. Enter the original IP address of pkt1 for the New IP address.

      Tip

      Do not change the original IP address.


    5. Enter the appropriate netmask and press ENTER.

  15. Enter y if the information is correct and press ENTER.

    Tip

    If the information you entered is incorrect, enter n and press ENTER. You are prompted to re-enter the information from step 14.




  16. Press ENTER.

  17. Enter b - Back twice and press ENTER after each time you selected b - Back.



  18. Enter y to restart the network.



  19. Press ENTER to return to the Main Menu.

  20. Repeat steps 3 to 19 for all Routing and Management VMs and Routing VMs.

Pagebreak

Anchor
SIGTAN only
SIGTAN only

...

Execute the Initial Configuration Procedure


Noprint

Click to read more...

Toggle Cloak


Cloak
NoteIf PCE is licensed on the system, before you can execute the initial configuration, the IP addresses have to be configured for PCE. This configuration must be done for all slots (Routing CPUs) with alias pce_1 and pce_2 (see ).

Form the Main Menu, select Set Initial Configuration, and press ENTER.

Enter y, and press ENTER.  
  
  • If your system is not licensed for PCE, the system automatically executes the initial configuration procedure. Go to step 5.
    • If it is detected that PCE has been licensed on this system, the following screen is displayed. Go to step 3.
      
      If your system is licensed for PCE, do one of the following:

  • Only one DSC SWe system is running PCE.

    1. Select 3 - Not as a Mated Pair. Go to step 4.
        

    • Two DSC SWe systems are running PCE.

  • Enter 1 - Mated Pair as Node 1, and press ENTER. 

    You are prompted to enter the IP addresses for the Routing CPU cards.
      

    • Enter the required IP Addresses for Node 2 as you configured this address in . 

    After entering each IP address, go to step 4. 

     

    Press ENTER.
    The system automatically executes the initial configuration procedure.Tip

    After the system executes the initial configuration for Node 1, you must execute this procedure for Node 2 in the mated pair configuration. Make sure to select  2 - Mated Pair as Node 2 and enter the IP addresses you configured for Node 1.

    You are prompted to decide whether EMS access should be enabled on the system that you are configuring.

    TipFor detailed information about EMS access, refer to .Do one of the following.
    If you want to have EMS access enabled, press y, and press ENTER, and go to step c.
    If you do not want EMS access enabled, go to step d.
    If you pressed y and ENTER in step a, the system enables EMS access and executes the initial configuration procedure, and restarts the Web UI.
    If you do not want to enable EMS access, enter n, and press ENTER.
    A message appears informing you that EMS access was not enabled (EMS snmprw community string was not activated), and the system continues to automatically execute the initial configuration procedure and restart the Web UI. 
    TipIf, at a later time, you want to enable EMS access, refer to .You have to wait approximately five minutes before you can access the Main Menu in Web UI after the system completes the execution of the initial configuration procedure.

    Execute Initial Config Procedure