Overview

You would like instructions on how to migrate traffic from the primary site to a second diameter host. You have two sites which are connected to two servers for online billing. Both sites have redundancy in place. You know the remote IP for both sites.

Solution

1. Login as textpass user to one Traffic Element at a time.
   
   
2. Backup current <hostname>_config.txt file
   i.e. cp /usr/TextPass/etc/<hostname>_config.txt /usr/TextPass/etc/<hostname>_config.bkp.170521
3. Edit the current <hostname>_config.txt by changing the routing costs as indicated below, i.e. for the first entry you can change from "10" to "20" vice-versa in the second entry from "20" to "10".  This will invert the primary and secondary hosts definition.
   

   <groupname1
   name="<name>"
   basespec="<basespec>"
   vendor="<vendor>"
   application="<application>"
   commonapplicationid="true"
   avpconfigfile="<native_diameter.xml>"
   querytimeout="3"
   dwrsendingperiod="30"
   maxpendingdwrs="2"
   stopconnectingafterdisconnect="false"
   originhost="<origin host"
   >
   <pbcdiamtrans
   cost="10"
   remoteip="<remote ip>"
   remoteport="<remote port>"
   localip="<local ip>"
   localport="<local port>"
   maxpendingqueries="500"
   destinationhost="<destination host>"
   destinationrealm="<destination realm>"
   />
   <groupname1
   cost="20"
   remoteip="<remote ip>"
   remoteport="<remote port>"
   localip="<local ip>"
   localport="<local port>"
   maxpendingqueries="500"
   destinationhost="<destination host>"
   destinationrealm="<destination realm>"
   />
   </groupname1>

4. Save the file and confirm the changes are OK. There should be no output for the command below, meaning there is no typo in the config file.
   

   tp_config --validateonly

5. Restart the traffic element.

   tp_stop;tp_start

6. Once all processes are operating, repeat this procedure for the next Traffic Element.