0% found this document useful (0 votes)
95 views7 pages

Connection Tests To Carriers From New Architecture: Summary

This document provides instructions for connecting carriers to a new SMSC architecture using SMSC01 and SMSC02 servers. It outlines prerequisites, resources available for support, and detailed procedures for deploying a VIP across the servers using keepalived and balancing traffic. It also includes steps for validating the connections and reverting changes if needed.

Uploaded by

Ande Vi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
95 views7 pages

Connection Tests To Carriers From New Architecture: Summary

This document provides instructions for connecting carriers to a new SMSC architecture using SMSC01 and SMSC02 servers. It outlines prerequisites, resources available for support, and detailed procedures for deploying a VIP across the servers using keepalived and balancing traffic. It also includes steps for validating the connections and reverting changes if needed.

Uploaded by

Ande Vi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Connection tests to carriers from

new architecture

Summary:
This MOP is to be executed as part of JIRA ticket MCM-282
● Use SMSC01 and SMSC02 servers for deployment
● The PAiC team will be available to validate the connection to the carriers from
both SMSC platforms.

Prerequisites

● PRQ_001: Portability database must be updated.


● PRQ_002: Tsaay test traffic https://paicbd.atlassian.net/browse/MCM-271
● PRQ_003: Metaswitch Test Traffic https://paicbd.atlassian.net/browse/MCM-276

PAiC Technical Resource


● Deployment Engineer:
○ Name: Jonathan Ventura
○ Contact Number: +503 7318 7845
○ email: [email protected]
○ Skype: ID: alexventurasv

● Support Engineer:
○ Name: Juan Carlos García Hernández
○ Contact Number: +503 6202-0398
○ email: [email protected]
○ Skype: ID: jcgardez

Execution date
● Jan. 12th, 2021. 21:00 GMT-6
Detailed procedures -

Rollout procedure:

● Connect to both Extended SMSC instances and stop keepAlived service

$ sudo service keepalived stop

● Edit /etc/keepalived/lblmaster.sh file in both SMSC nodes in order to configure VIP


172.31.255.230.

$ sudo vim /etc/keepalived/lblmaster.sh

#!/bin/bash
#this script will swap the private secondary IP which acts as the VIP
from the old master to the new master, this is done via AWS API Tools

type=$1
name=$2
state=$3

vip=172.31.255.230
region=us-east-1
aws_access_key_id=AKIAJK626GVHZP7GYSOA
aws_secret_access_key=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

#Instance_ID=`/usr/bin/curl --silent
http://169.254.169.254/latest/meta-data/instance-id`
Instance_ID="i-0134da82adce8cc34"

#ENI_ID=`ec2-describe-instances $Instance_ID --region $region


--aws-access-key $aws_access_key_id --aws-secret-key
$aws_secret_access_key | grep eni -m 1 | awk '{print $2;}'`
ENI_ID="eni-029fdf68333a41852"

case $state in
"MASTER")
logger -p user.info ***Starting***
ec2-assign-private-ip-addresses -n $ENI_ID
--secondary-private-ip-address $vip --allow-reassignment --region $region
--aws-access-key $aws_access_key_id --aws-secret-key
$aws_secret_access_key
sudo ifconfig ens3:0 $vip netmask 255.255.255.0 up

sudo screen -ls | grep lb | cut -d. -f1 | awk '{print $1}' | sudo
xargs kill
cd /opt/paic/lb/sip-balancer-8/bin
sleep 1
./run.sh
;;
*)
logger -p user.info ***Stopping***
sudo screen -ls | grep lb | cut -d. -f1 | awk '{print $1}' | sudo
xargs kill
sudo ifconfig ens3:0 down
;;
esac

● Edit /opt/paic/lb/sip-balancer-8/conf/lb-configuration.xml in both SMSC servers

<common>
<host>172.31.255.230</host>
<rmiRegistryPort>2000</rmiRegistryPort>
<rmiRemoteObjectPort>2001</rmiRemoteObjectPort>
<nodeTimeout>8400</nodeTimeout>
<heartbeatInterval>150</heartbeatInterval>
<statisticPort>2006</statisticPort>
<jmxHtmlAdapterPort>8000</jmxHtmlAdapterPort>
</common>
<smpp>
<smppHost>172.31.255.230</smppHost>
<smppPort>27761</smppPort>
<smppSslPort></smppSslPort>
<remoteServers>172.31.255.235:2776,172.31.255.236:2776</remoteServers>
<maxConnectionSize>10</maxConnectionSize>
<nonBlockingSocketsEnabled>true</nonBlockingSocketsEnabled>
<defaultSessionCountersEnabled>true</defaultSessionCountersEnabled>
<timeoutResponse>3000</timeoutResponse>
<timeoutConnection>1000</timeoutConnection>
<timeoutEnquire>50000</timeoutEnquire>
<reconnectPeriod>1000</reconnectPeriod>

<timeoutConnectionCheckClientSide>60000</timeoutConnectionCheckClientSide
>

<timeoutConnectionCheckServerSide>60000</timeoutConnectionCheckServerSide
>
<muxMode>true</muxMode>
</smpp>
● Stop both Extended HTTP-SMPP Gw services

$ sudo screen -r smpp-gw [ctrl + x]

● Unsubscribe VIP from current instances

$ sudo ifconfig ens3:0 down

● Start keepAlived services on Extended SMSC 01

$ sudo service keepalived start

● Start keepAlived services on Extended SMSC 02

$ sudo service keepalived start

● Start Cassandra Service

$ cd /opt/paic/cassandra/apache-cassandra-3.11.9/bin
$ ./start-cassandra.sh

● Start SMSC service

$ cd /opt/paic/smsc/Extended-SMSC-7.4.2-202/wildfly-10.1.0.Final/bin/
$ sudo ./start-cassandra.sh standalone 172.31.255.235

● Validate SMPP management GUI

○ Verify access to the GUI


○ Validate carriers connections
○ Validate customers BINDS
○ Check traffic at log level

● Test and validations from MCM side


Rollback Process (if needed)

● Connect to both Extended SMSC instances and stop keepAlived service

$ sudo service keepalived stop

● Edit /etc/keepalived/lblmaster.sh file in both SMSC nodes in order to configure VIP


172.31.255.250.

$ sudo vim /etc/keepalived/lblmaster.sh

#!/bin/bash
#this script will swap the private secondary IP wich acts as the VIP from
the old master to the new master, this is done via AWS API Tools

type=$1
name=$2
state=$3

vip=172.31.255.250
region=us-east-1
aws_access_key_id=AKIAJK626GVHZP7GYSOA
aws_secret_access_key=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

#Instance_ID=`/usr/bin/curl --silent
http://169.254.169.254/latest/meta-data/instance-id`
Instance_ID="i-0134da82adce8cc34"

#ENI_ID=`ec2-describe-instances $Instance_ID --region $region


--aws-access-key $aws_access_key_id --aws-secret-key
$aws_secret_access_key | grep eni -m 1 | awk '{print $2;}'`
ENI_ID="eni-029fdf68333a41852"

case $state in
"MASTER")
logger -p user.info ***Starting***
ec2-assign-private-ip-addresses -n $ENI_ID
--secondary-private-ip-address $vip --allow-reassignment --region $region
--aws-access-key $aws_access_key_id --aws-secret-key
$aws_secret_access_key
sudo ifconfig ens3:0 $vip netmask 255.255.255.0 up

sudo screen -ls | grep lb | cut -d. -f1 | awk '{print $1}' | sudo
xargs kill
cd /opt/paic/lb/sip-balancer-8/bin
sleep 1
./run.sh
;;
*)
logger -p user.info ***Stopping***
sudo screen -ls | grep lb | cut -d. -f1 | awk '{print $1}' | sudo
xargs kill
sudo ifconfig ens3:0 down
;;
esac

● Edit /opt/paic/lb/sip-balancer-8/conf/lb-configuration.xml in both SMSC servers

<common>
<host>172.31.255.250</host>
<rmiRegistryPort>2000</rmiRegistryPort>
<rmiRemoteObjectPort>2001</rmiRemoteObjectPort>
<nodeTimeout>8400</nodeTimeout>
<heartbeatInterval>150</heartbeatInterval>
<statisticPort>2006</statisticPort>
<jmxHtmlAdapterPort>8000</jmxHtmlAdapterPort>
</common>
<smpp>
<smppHost>172.31.255.250</smppHost>
<smppPort>27761</smppPort>
<smppSslPort></smppSslPort>
<remoteServers>172.31.255.235:2776,172.31.255.236:2776</remoteServers>
<maxConnectionSize>10</maxConnectionSize>
<nonBlockingSocketsEnabled>true</nonBlockingSocketsEnabled>
<defaultSessionCountersEnabled>true</defaultSessionCountersEnabled>
<timeoutResponse>3000</timeoutResponse>
<timeoutConnection>1000</timeoutConnection>
<timeoutEnquire>50000</timeoutEnquire>
<reconnectPeriod>1000</reconnectPeriod>

<timeoutConnectionCheckClientSide>60000</timeoutConnectionCheckClientSide
>

<timeoutConnectionCheckServerSide>60000</timeoutConnectionCheckServerSide
>
<muxMode>true</muxMode>
</smpp>

● Stop both Extended SMSC services

$ sudo screen -r smsc [ctrl + x]


● Unsubscribe VIP from new instances

$ sudo ifconfig ens3:0 down

● Start keepAlived services on SMPP01

$ sudo service keepalived start

● Start keepAlived services on SMPP02

$ sudo service keepalived start

● Start Cassandra Service

$ cd /opt/paic/cassandra/apache-cassandra-3.11.9/bin
$ ./start-cassandra.sh

● Start HTTP-SMPP service

$ cd /opt/paic/Extended-HTTP-SMPP-Gw/run/
$ sudo ./run.sh

● Validate traffic

○ Validate carriers connections


○ Validate customers BINDS
○ Check traffic at log level

● Test and validations from MCM side

You might also like