Overview

You want to integrate a new STP in the network which will handle SMSC traffic.

Solution

To integrate a new STP with SMSC, complete the following instructions:

1. log in to the Traffic Element(s) with which the new STP needs to integrate.
   
   
2. Backup <hostname>_config.txt and static routes (if any) on each RTR
   
   
   • cp /usr/TextPass/etc/<hostname>_config.txt /usr/TextPass/etc/<hostname>_config.txt-YYYMMDD
   • cd /etc/sysconfig/network-scripts
   • cp -p route-<name-of-sigtran-interface1> route-<name-of-sigtran-interface1>-YYYYMMDD 
   • cp -p route-<name-of-sigtran-interface2> route-<name-of-sigtran-interface2>-YYYYMMDD
   • Example: cp -p route-eth1 route-eth1-YYYYMMDD
     
     
3. Edit the <hostname>_config.txt file to include the lines corresponding to the new STP details. i.e.: the fields in blue below must be defined:
   
   

   vi /usr/TextPass/etc/<hostname>_config.txt 
   <!-- ############################################## -->
   <!-- Sigtran Connections to <NEW STP> -->
   <!-- ############################################## -->
   <m3uasgp name="NEW_STP_link1"
   useforpointcode="true"
   useforvirtualpointcode="true"
   fillinaspidentifierfield="false"
   sctplocalport="290X"
   sctpremoteport="290X"
   >
   <remoteaddress spec="X.X.X.X"/>
   <remoteaddress spec="X.X.X.X"/>
   </m3uasgp>
   <m3uasgp name="NEW_STP_link2"
   useforpointcode="true"
   useforvirtualpointcode="true"
   fillinaspidentifierfield="false"
   sctplocalport="290X"
   sctpremoteport="290X"
   >
   <remoteaddress spec="X.X.X.X"/>
   <remoteaddress spec="X.X.X.X"/>
   </m3uasgp>
   <!-- ####################################################### -->
   <!-- # destinations # -->
   <destination name="NEW_STP" type ="stp" pointcode="XXXX">
   <route m3uasgp="NEW_STP_link1"/>
   <route m3uasgp="NEW_STP_link2"/>
   </destination>

4. If the new STP requires new IP Routes, this needs to be identified and added permanently using the utility lnxcfg or add them manually editing correspondent file for the static route configuration in /etc/sysconfig/network-scripts/route-interface. i.e.:
   
   

   # ip route add X.X.X.X/X via X.X.X.X dev <Sigtran-1-interface>
   # ip route add X.X.X.X/X via X.X.X.X dev <Sigtran-2-interface> 

5. Test network connectivity to new STP:
   
   

   #ping -I <Sigtran-1-interface> X.X.X.X 
   #ping -I <Sigtran-2-interface>  X.X.X.X

6. Add static route permanently for the new STP, and save the file with wq!:
   
   

   # vi /etc/sysconfig/network-scripts/route-<Sigtran-1-interface>  and add the necessary route 
   X.X.X.X/X via X.X.X.X dev <Sigtran-1-interface> 
   # vi /etc/sysconfig/network-scripts/route-<Sigtran-2-interface>  and add the below route 
   X.X.X.X/X via X.X.X.X dev <Sigtran-2-interface> 

7. Verify if there are no errors or typos in the new definitions of the hostname_config.txt file (no output expected – in case of errors, revise the new definitions).
   As textpass, execute: tp_config --validateonly
   
   
8. Restart the RTRs, one RTR at a time.
   
   

   tp_stop --textpass;tp_start --textpass

9. Verify the status of the textpass process. i.e. tp_status.
   
   
   * Actual output may differ depending on the configured and installed services.
   
   
10. Verify the status of newly created (and old) Sigtran links. As textpass: m3ua_link