Cellcom Omg
Cellcom Omg
Cra. 12 #93-08
Zip Code, Bogota
Colombia
Tel.: +00 (0) 00 00 00 00
Fax: +00 (0) 00 00 00 00
www.thalesgroup.com
O P E R AT I O N A N D M A I N T E N A N C E G U I D E ( O M G )
LOG OF CHANGES
003
APPROVAL
Written by
Verified by
Approved by
Approved by
the customer
if necessary
Template: 87202584-DOC-GRP-EN-006
2 / 70
CONTENTS
1. INTRODUCTION............................................................................................................................................ 8
1.4 Terminology............................................................................................................................................ 9
2. SOLUTION DESCRIPTION.......................................................................................................................... 10
2.1 Overview.............................................................................................................................................. 10
2.2.1 Configuration.................................................................................................................................... 10
2.2.2 Connection....................................................................................................................................... 16
2.5 Customs............................................................................................................................................... 19
2.6 Architecture.......................................................................................................................................... 19
2.9.1 Overview.......................................................................................................................................... 36
Template: 87202584-DOC-GRP-EN-006
3 / 70
3.2.2 Provisioning..................................................................................................................................... 38
3.3.2 Provisioning..................................................................................................................................... 39
3.8 Crontabs.............................................................................................................................................. 44
4. HIGH AVAILABILITY..................................................................................................................................... 47
5. OPERATION................................................................................................................................................. 49
5.2.3 RCA................................................................................................................................................. 54
Template: 87202584-DOC-GRP-EN-006
4 / 70
Template: 87202584-DOC-GRP-EN-006
5 / 70
LIST OF TABLES
Template: 87202584-DOC-GRP-EN-006
6 / 70
LIST OF FIGURES
Template: 87202584-DOC-GRP-EN-006
7 / 70
1. INTRODUCTION
products
Folder installation installation/configuration
files
Template: 87202584-DOC-GRP-EN-006
8 / 70
files
The hardware is owned by Thales, the machines are in the AWS cloud, it uses the EC2 service that
creates the Red Hat Enterprise Linux machines for each server in the corresponding CELLCOM
architecture. The machines are from Thales, but the customer can monitor, control, and modify the
instances. Thales creates the account for the client with all the necessary permissions for its
administration.
1.4 Terminology
Table 2 - Terminology
Template: 87202584-DOC-GRP-EN-006
9 / 70
Template: 87202584-DOC-GRP-EN-006
10 / 70
2. SOLUTION DESCRIPTION
2.1 Overview
The use cases are HTTP only, API RUM, LPM batch file provisioning.
Once you log in, you are redirected to the main page of the aws console. In the part there is the search bar in it
the "IAM" service will be searched, and we click.
Template: 87202584-DOC-GRP-EN-006
11 / 70
Once in the iam service interface, in the center left part we look for the users section
Template: 87202584-DOC-GRP-EN-006
12 / 70
Once in the user interface, we must search for our user and click on it.
Within the detail of our user's information, we will click on the "Security credentials" section
Template: 87202584-DOC-GRP-EN-006
13 / 70
Then we go down the page and look for the "Multi-factor authentication (MFA)" section and click on the "Assign
MFA device" button, this service is to activate 2-factor authentication, the services require that this token be
active, to try to mitigate any impersonation problems, it is recommended to download a token tool like "Google
authenticator" or the tool of your choice.
To continue with the process we assign a name "Device name" this will be how we will save our token, then we
select the option "Authenticator app" to use an application as a token, then we go down the page and click on
the next button.
Template: 87202584-DOC-GRP-EN-006
14 / 70
To activate the token, we follow the steps that the interface describes, once we successfully complete the
activation, our account will be linked to that token, that is, every time we log in, in addition to entering the
credentials, it will request the token for access.
Template: 87202584-DOC-GRP-EN-006
15 / 70
To assign the roles to our AWS account, click on the upper right where the account name is located, click on the
arrow and it will display a menu which we must click on the "Switch role" button.
Once we see the interface to assign the role, we fill in the help fields from the role table (Table 3 - List of Roles)
fill in the fields and click on the "Switch role" button.
Template: 87202584-DOC-GRP-EN-006
16 / 70
With that, the role would be created, if we have more roles, the process must be repeated as many times as
there are roles.
2.2.2 Connection
For the connection directly with the AWS console we must click on the following link. This will display an
interface which we must fill out with our connection data, our username and password. Then we click on the
"Sign in" button
Template: 87202584-DOC-GRP-EN-006
17 / 70
Then in the following interface we must type our authentication code that we configured previously (), once we
type the token we click on the "Submit" button and if our credentials are correct it will redirect us to the AWS
main page.
Template: 87202584-DOC-GRP-EN-006
18 / 70
Thales Products
DELIVERY_ID
Name Description
or Version (*)
Template: 87202584-DOC-GRP-EN-006
19 / 70
2.5 Customs
Table 6 - Custom
Custom Software/Services
2.6 Architecture
Template: 87202584-DOC-GRP-EN-006
20 / 70
Template: 87202584-DOC-GRP-EN-006
21 / 70
The Livelab and Prod Application servers “app1-2” are equipped with 3 volumes (Elastic Block Store) as can
find below:
10GB 16 GB 30GB
lsblk command:
Template: 87202584-DOC-GRP-EN-006
22 / 70
These instances are also connected to EFS (Elastic File System) dedicated to preserve the Logs files for each
availability zone.
fs- XXXXXXX.efs.us-east-1.amazonaws.com
fs- XXXXXXX.efs.us-east-1.amazonaws.com
Server APP1
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed1/logs ->
/mnt/efs/app1/gemalto/gemapp/wls/gemalto_domain/servers/managed1/logs/
Template: 87202584-DOC-GRP-EN-006
23 / 70
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed2/logs->
/mnt/efs/app1/gemalto/gemapp/wls/gemalto_domain/servers/managed2/logs/
/opt/gemalto/gemapp/wls/gemalto_domain/servers/AdminServer/logs>
/mnt/efs/app1/gemalto/gemapp/wls/gemalto_domain/servers/AdminServer/logs/
Server APP2
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed3/logs >
/mnt/efs/app2/gemalto/gemapp/wls/gemalto_domain/servers/managed3/logs/
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed4/logs >
/mnt/efs/app2/gemalto/gemapp/wls/gemalto_domain/servers/managed4/logs/
fs-XXX.efs.us-east- 755
/mnt/efs NA root:root
1.amazonaws.com:/
Template: 87202584-DOC-GRP-EN-006
24 / 70
The Staging and Prod Application servers “GWAF1-2 and PUBGWAF1-2” are equipped with 3 volumes (Elastic
Block Store) as can find below:
10GB 16 GB 15GB
lsblk command:
These instances are also connected to EFS (Elastic File System) dedicated to preserve the Logs files for each
availability zone.
fs- XXXXXXX.efs.us-east-1.amazonaws.com
Template: 87202584-DOC-GRP-EN-006
25 / 70
fs-XXXXXXX.efs.us-east-1.amazonaws.com
Server GWAF1
Server PUBGWAF1
Server GWAF2
Server PUBGWAF2
fs-XXX.efs.us-east- 755
/mnt/efs NA root:root
1.amazonaws.com:/
Template: 87202584-DOC-GRP-EN-006
26 / 70
Template: 87202584-DOC-GRP-EN-006
27 / 70
Template: 87202584-DOC-GRP-EN-006
28 / 70
2.6.3.1 Production
Table 9 - Host machine production
Environment Environment
Source IP address Destination IP address Port Protocol Description
Source Destination
990
ec2-mcs-p- 172.25.105.77/27 Allynis
AOTA CCPR – Allynis SFTP service to share files
ue1-otausa1- Connect 10.147.2.121 50000- TCP
Allynis Prd 172.25.105.122/27 connect with customer
CCPR-APP-1 Production
50100
172.25.105.77/27
ec2-mcs-p-
Allynis AOTA CCPR 1024- FTP service to share files
Allynis – AOTA Prd 10.147.2.121 ue1-otausa1- ip-X-X-X- TCP
connect Production 65535 with customer
CCPR-APP-1 X.otausa1.ue1.msi-
prd29.private.gemalto.com
AOTA CCPR
elb-mcs-p-
Production Cards HTTPs traffic-
Public GWAF Internet 0.0.0.0/0 ue1-otausa1- TBD 1443 TCP
(Load Polling
CCPR-pub
Balancer)
OSD Stats ec2-mcs-d- 172.25.105.77/27 OSDStats Prd OSDSTLS rds-mcs-p-ew1-m-rptcell- 1325 TCP Reporting cell - OSD
ue1-otausa1- oracle-dwh- RDS oracle
172.25.105.122/27
CCPR-APP- ora19.cuwzqpkud3n9.eu-
Template: 87202584-DOC-GRP-EN-006
29 / 70
1,2 west-
1.rds.amazonaws.com
AOTA SCI
SCI Access from elb-mcs-p-
CCPR AOTA CCPR- Flow might also present for
Customer 192.168.0.0/24 ue1-otausa1- TBD 7200 TCP
Network AWS VPC Peering and Private
Premises CCPR-nlb
Link
Template: 87202584-DOC-GRP-EN-006
30 / 70
Template: 87202584-DOC-GRP-EN-006
31 / 70
2.6.3.2 LIVELAB
rds-mcs-p-ew1-m-
rptcell-oracle-dwh-
ec2-mcs-d-ue1-
ora19.cuwzqpkud3n9. Reporting cell - OSD
AOTA CCLL- AWS otausa1-ccll- OSDStats Prd OSDSTLS 1325
eu-west- RDS oracle
APP-1,2 1.rds.amazonaws.co
m
Template: 87202584-DOC-GRP-EN-006
32 / 70
To access the platform GUI interfaces it is strongly recommended to forward appropriate TCP ports and then
access the platform URLs via Power Shell or Cmder :
Example :
Now, we can do a new port forwarding using anywhere ssh client (Putty, xshell,Mobaxterm,WinSCP)
Interfaces URLs
WebLogic Admin Console http://localhost:7001/console/
2.8.1.1 Production
Table 12 - IP Address
Template: 87202584-DOC-GRP-EN-006
33 / 70
us-east-1b : 172.25.105.16/28
us-east-1c : 172.25.105.32/28
App1 - 172.25.105.77
App2 -172.25.105.122
ue1a : 172.25.105.64/27
Gwaf1 – 172.25.105.76
Private1 Subnets ue1b : 172.25.105.96/27
Gwaf2 - 172.25.105.105
ue1c : 172.25.105.128/27
Pubgwaf1 - 172.25.105.90
Pubgwaf2 - 172.25.105.121s
ue2a : 172.25.105.160/27
rds-mcs-p-ue1-m-otausa1-mysql-
Private2 Subnets ue2b : 172.25.105.192/27 ccpr.czg4puivnkbq.us-east-
1.rds.amazonaws.com
ue2c : 172.25.105.224/27
us-east-1a : 172.25.105.0/28
us-east-1c : 172.25.105.32/28
Template: 87202584-DOC-GRP-EN-006
34 / 70
Gwaf2 - 172.25.105.117
Pubgwaf1 - 172.25.105.80
Pubgwaf2 - 172.25.105.111
ue2a : 172.25.105.160/27
rds-mcs-p-ue1-m-otausa1-mysql-
Private2 Subnets ue2b : 172.25.105.192/27 ccll.czg4puivnkbq.us-east-
1.rds.amazonaws.com
ue2c : 172.25.105.224/27
description port
Template: 87202584-DOC-GRP-EN-006
35 / 70
Template: 87202584-DOC-GRP-EN-006
36 / 70
2.9.1 Overview
According this, the only way to connect it is through mysql commands from anywhere of the ec2 instances.
Connection string:
Sized for
Estimated
SID Port Description (in number of size
cards)
GEMASTER GTODB1
RCAADMIN GTODB1
FRWKADMIN GTODB1
ADMGEMALTO GTODB1
Template: 87202584-DOC-GRP-EN-006
37 / 70
MGRGEMALTO GTODB1
TECHADMGEMALTO GTODB1
MBADMIN GTODB1
GCCMADMIN GTODB1
PMSEEADMIN GTODB1
Template: 87202584-DOC-GRP-EN-006
38 / 70
3.2.2 Provisioning
For provisioning the LPM files should be moved to the following path on application server #1:
/opt/gemalto/gemapp/PM/PM/batch_home/server/input_for_files
They will be automatically processed and can be followed from the server or from the application.
Template: 87202584-DOC-GRP-EN-006
39 / 70
Product,
Installation directory User
component
Linqus Provisioning
/opt/gemalto/gemapp/PM/PM/batch_home/server/input_for_files gemapp
Manager
3.3.2 Provisioning
Standard CCI was used for provisioning and standard LPM interfaces:
Webservice
Batch_loader
Product,
Installation directory User
component
Weblogic /opt/gemalto/gemapp/wls
gemapp
Weblogic logs /opt/gemalto/gemapp/wls/gemalto_domain/servers/managed1/logs
Template: 87202584-DOC-GRP-EN-006
40 / 70
Product,
Installation directory User
component
GWAF /product/GWAF/GWAF_4.2.15
gwaf
GWAF logs /product/GWAF/GWAF_4.2.15/logs
Cattp.Generic0348.2+.03_48
Sms.Gemaltosimera2.2+.03_48
Wir.Gemaltosimera2.2+.03_48
Template: 87202584-DOC-GRP-EN-006
41 / 70
Certifi
Kind Requir
cate
of ed
reque Expira
Flo Location of securi Certificate validity domain parame Common Name Issuer / self
ster / tion
w certificate ty & (specific to each...) ters & (mandatory) signed
privat date
certifi comme
e key
cate nts
owner
ccll- 10/11/25
SCI
and
WS Private and Public
Acce Gwafs :
LIVELAB environment-ccll
ss /product/GWAF/GWAF_4.2. Thales certificate.automation@th
troug
SSL
MCS
*.mcs29.acloud.thalescloud.io
15/conf/vhosts-key alesgroup.com
*.mcs29.acloud.thalescloud.io
h
GW
AF
Serv
ers
Template: 87202584-DOC-GRP-EN-006
42 / 70
ccpr- 10/11/25
SCI
and
WS Private and Public
Acce Gwafs : Prod environment-ccpr
ss /product/GWAF/GWAF_4.2. Thales *.ccpr.pub.otausa1.ue1.mcs29.acl certificate.automation@th
SSL *.ccpr.pub.otausa1.ue1.mcs29.acl
troug 15/conf/vhosts-key MCS oud.thalescloud.io alesgroup.com
h oud.thalescloud.io
GW
AF
Serv
ers
Template: 87202584-DOC-GRP-EN-006
43 / 70
To sign Thales Certificate you can request the new one in the page :
https://ee-bpkiv2.gemalto.com
Category:
Template: 87202584-DOC-GRP-EN-006
44 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To view the files (depending on the format, they are usually pem)
PEM to DER
DER to PEm
openssl x509 -in cert.crt -inform der -outform pem -out cert.pem
3.8 Crontabs
[Provide all information on installed cron, with details on purpose of the command
that is run, and this for each type of machine of the solution]
The GWAF server logs are been collected in a route hosted in the EFS (Elastic File System).
Accordingly there are not any purge log script, because the EFS don´t have a limited space.
Template: 87202584-DOC-GRP-EN-006
45 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
The AOTA application server logs are been collected in a route hosted in the EFS (Elastic File
System). Accordingly there are not any purge log script, because the EFS don´t have a limited space.
Application1 :
Template: 87202584-DOC-GRP-EN-006
46 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
/opt/gemalto/gemapp/wls/gemalto_domain/servers/AdminServer/logs ->
/mnt/efs/app1/gemalto/gemapp/wls/gemalto_domain/servers/AdminServer/logs/
Application2:
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed3/logs ->
/mnt/efs/app2/gemalto/gemapp/wls/gemalto_domain/servers/managed3/logs/
/opt/gemalto/gemapp/wls/gemalto_domain/servers/managed4/logs ->
/mnt/efs/app2/gemalto/gemapp/wls/gemalto_domain/servers/managed4/logs/
The database is as an AWS (RDS) service and therefore it is not necessary to perform any filesystem
purge or similar process.
Template: 87202584-DOC-GRP-EN-006
47 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
4. HIGH AVAILABILITY
Reference for related information are located into SIP document, refers to
MKS/MERCURIAL/Mercurial
For information:
For AWS deployment the High availability is given for the multi Availability zone that means that each
AOTA layer (Priv GWAFs, Pub Gwafs and Application servers) has one server identical in other
availability zone. (b for our case) as image below shows:
Template: 87202584-DOC-GRP-EN-006
48 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Template: 87202584-DOC-GRP-EN-006
49 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
5. OPERATION
To start, stop or validity the status of the AOTA is created 3 scripts for facility the execution of these 3
statuses, the scripts are in the path of the machine of the AOTA in
/opt/gemalto/gemapp/scripts_custom_aota the files that you'll find are:
1) aota_status.sh
This script informs us which services are running and which services are stopped, to run the
script you must go to the path /opt/gemalto/gemapp/scripts_custom_aota/ to execute it you
must execute the script as sh aota_status.sh or ./aota_status.sh. An example of what you
will see on the screen is the following:
Template: 87202584-DOC-GRP-EN-006
50 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
2) aota_start.sh
This script informs us and allows us to set up the entire AOTA system. To set up the AOTA it
must set up some services in a specific order, the script checks this order and one by one
checks which services are running and which are not, the services that are not is running or
executing, it will run them to start the AOTA, to run the script you must go to the path
/opt/gemalto/gemapp/scripts_custom_aota/ to execute it you must execute the script as sh
aota_start.sh or ./aota_start.sh. An example of what you will see on the screen is the
following:
3) aota_stop.sh
Template: 87202584-DOC-GRP-EN-006
51 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
This script informs us which services are running and which are not, and allows us to stop the
entire AOTA system. The script checks the services that are stopped one by one and the services
that are running, it will stop them until the AOTA system stops, to run the script you must go to the
path /opt/gemalto/gemapp/scripts_custom_aota/ to execute it you must execute the script as sh
aota_stop.sh or ./aota_stop.sh. An example of what you will see on the screen is the following:
Template: 87202584-DOC-GRP-EN-006
52 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To start the AOTA mysql database, you have to do it clicking start in the AWS console:
To verify status of Veritas Cluster service group for OTADB2 database, type:
To verify the AOTA mysql database status, you have to do it selecting the database in the AWS
console (RDS service):
To stop the AOTA mysql database, you have to do it clicking ‘Stop temporarily’ in the AWS console:
Template: 87202584-DOC-GRP-EN-006
53 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To start the OTA framework execute the follow commands in the application server with gemapp user
(in order) :
To verify the OTA framework status execute the follow commands in the application server with
gemapp user:
Template: 87202584-DOC-GRP-EN-006
54 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To stop the OTA framework execute the follow commands in the application server with gemapp user
(in order):
5.1.3 RCA
To start the OTA framework execute the follow commands in the application server with gemapp user:
To verify the OTA RCA status execute the follow commands in the application server with gemapp
user:
Template: 87202584-DOC-GRP-EN-006
55 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To stop the OTA framework execute the follow commands in the application server with gemapp user
(in order):
To start the LPM webserver execute the follow commands in the application server with gemapp user:
/opt/gemalto/gemapp/FRWK/bin/gemconnect –v –p PM start
To verify the LPM webserver status execute the follow commands in the application server with
gemapp user:
/opt/gemalto/gemapp/FRWK/bin/gemconnect –p PM status
Template: 87202584-DOC-GRP-EN-006
56 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To stop the LPM webserver execute the follow commands in the application server with gemapp user
(in order):
To start the Weblogic admin server execute the follow commands in the application server with
gemapp user:
/opt/gemalto/gemapp/wls/gemalto_domain/gemaltobin/startAdminServer.sh &
To verify the Weblogic admin server status execute the follow commands in the application server with
gemapp user:
To stop the Weblogic admin server execute the follow commands in the application server with
gemapp user:
/opt/gemalto/gemapp/wls/gemalto_domain/gemaltobin/stopAdminServer.sh &
Template: 87202584-DOC-GRP-EN-006
57 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To start the Weblogic Node manager and managed servers execute the follow commands in the
application server with gemapp user as appropriate:
Node Manager :
/opt/gemalto/gemapp/wls/nodemanager/startNodeManager.sh &
Managed servers :
#* Managed number (1 and 2 hosted on Application server1. 3 and 4 hosted on Application server2)
To verify the Weblogic Node manager and managed servers status, execute the follow commands in
the application server with gemapp user as appropriate:
Node Manager :
Managed servers :
#* Managed number (1 and 2 are hosted on Application server1. 3 and 4 are hosted on Application
server2)
To stop the Weblogic Node manager and managed servers execute the follow commands in the
application server with gemapp user as appropriate:
Node Manager :
/opt/gemalto/gemapp/wls/nodemanager/stopNodeManager.sh &
Managed servers :
#* Managed number (1 and 2 hosted on Application server1. 3 and 4 hosted on Application server2)
Template: 87202584-DOC-GRP-EN-006
58 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
To start the GWAF application layer execute the follow commands in the GWAF or PubGWAF server
with gwaf user as appropriate:
/product/GWAF/GWAF_4.2.15/bin/gwafmgr start
To verify the GWAF application layer status, execute the follow commands in the GWAF or PubGWAF
server with gwaf user as appropriate:
/product/GWAF/GWAF_4.2.15/bin/gwafmgr status
To stop the GWAF application layer execute the follow commands in the GWAF or PubGWAF server
with gwaf user as appropriate:
/product/GWAF/GWAF_4.2.15/bin/gwafmgr stop
5.2 Monitoring
Datadog agents are gathering information on each machine thanks to NGM agents, and there is an
autonomous Datadog platform centralizing all information about system, databases, products…
So PRODUCTION and LIVELAB thanks to Datadog you can have a quick look to:
Template: 87202584-DOC-GRP-EN-006
59 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Filesystems monitoring
Applications monitoring
Database statistics
GWAF statistics
To check the datadog agent status execute the commands in each server :
Still in green, services percentage but not equal to 100, because few services raise warning alarms :
Template: 87202584-DOC-GRP-EN-006
60 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Therefore, here is the list of file systems to be backed up per machine as advised by Thales:
Template: 87202584-DOC-GRP-EN-006
61 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
For Cellcom, we have deployed some scripts to exchange files with Cellcom’s Allynis Account.
You can find this directory to process the Allynis data (Aplication server #1)
/opt/gemalto/OPERATION/Allynis
The main script is called download_files.sh and It’s executed automatically using this crontab:
Template: 87202584-DOC-GRP-EN-006
62 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Firstly, uses a connection FTP to Login and download the .xml and .XML
Change the extension from the XML files to xml if the case. Makes a copy of the files previously
downloaded.
And finally, the files are going to move the LPM folder to be provisioned.
To verify the script and crontab funtionallity, you can check the download_files.log where all the
executions are going to write their own log with the date and hour of execution.
To get the statistics, was configured the OSD integration with the AOTA Solution hosted on AWS.
AOTA SCRIPTS :
USER="osdstats" and PASS="XXXXXXXXX", credential for the ETL to login and perform the
queries at the Platform MySQL database
Template: 87202584-DOC-GRP-EN-006
63 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
DWH_HOST="10.19.32.64", IP (or host name) that the ETL can reach the DWH database
PLATFORM_ID=0, this one needs to be configured for the new DWH deployment by the RC
engineer, this id is given by RC when deploying the new MNO at the DWH database;
RM SCRIPTS :
HOST="gtodbvip" ; can we have always the same hostname to connect to the platform db (for
all installations / deployments)
PORT="3306"
DB="gtodb1"
DWH_HOST="10.19.32.64"
All the OSD scripts are going to be executed using the crontab shown below :
Template: 87202584-DOC-GRP-EN-006
64 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Template: 87202584-DOC-GRP-EN-006
65 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
CCO_01.00 Gemalto
CCO_01.00_04 Gemalto
CCO_02.00 Gemalto
GEN_G178_RP Gemalto
Template: 87202584-DOC-GRP-EN-006
66 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
CCO_01.00 Gemalto
CCO_01.01 Gemalto
CCO_01.02 Gemalto
CCO_02.00 Gemalto
CCO_02.01 Gemalto
CCO_03.00 Gemalto
CCO_04.00 Gemalto
Template: 87202584-DOC-GRP-EN-006
67 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Template: 87202584-DOC-GRP-EN-006
68 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Call Local
+33(4)42 +33(4)42
center support Ggs support mailto:[email protected]
36 66 00 36 66 00
contact center
DTS global
manager +33(4)
Bertrand
42 36 58 +33(6) mailto:[email protected]
CHARBONNIER 87 75 18
44
will be also 07
Escalation informed :
level 3 BU manager
TBD
Account
TBD
Manager
TBD
Product
Manager
Template: 87202584-DOC-GRP-EN-006
69 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE
OPERATIONS AND MAINTENANCE GUIDE
SUBJECT OF THE TECHNICAL DOCUMENT
Project Contacts
Thales
CUSTOMER
END OF DOCUMENT
Template: 87202584-DOC-GRP-EN-006
70 / 70
THALES GROUP LIMITED DISTRIBUTION - SCOPE