Copyright 2016 Avaya Inc. All rights reserved. Use pursuant to the terms of your signed agreement or Avaya policy

Transcription

1 Device Enrollment Service (2.0 Sprint#4) Installation Guide Compass ID: Issue 1.0 Created Date: October 2018 Last Modified Date: 12 October 2018

2 Table of contents 1. DOCUMENT HISTORY PURPOSE ARCHITECTURE OVERVIEW PLANNING PREDEPLOYMENT AND CONFIGURATION TASK DEPLOYMENT OF DEVICE ENROLLMENT SERVICE POST DEPLOYMENT VERIFICATION MAINTENANCE... 11

3 1. DOCUMENT HISTORY Issue Change Summary Author(s) Date 1 DES Installation Guide Amol Bagul and Manish Adkar 12 th October 2018

4 2. PURPOSE This document: describes the procedures for deploying the Device Enrollment Service application on AWS platform. includes deployment, configuration, deployment verification, troubleshooting, and basic maintenance checklists and procedures. does not include optional or customized aspects of a configuration. The primary audience for this document is anyone who deploys, configures, and verifies DES.

5 3. ARCHITE CTURE OVE RVIEW DES Overview The existing secure deployment model for our phones includes an expensive staging step which requires the customer or reseller to setup a secure staging network to prepare the phones for deployment into harsh environments. Our customers would like to avoid this expensive step and instead ship the phone directly to the end user and still allow the phone to be securely attached to its network and later properly configure to allow it to get service. Some customers might still require the staging step, but they would like to dramatically reduce and simplify the steps needed at this stage. The DES is a server that sits in the Internet and provides a mechanism for Avaya phones to be securely redirected to the correct configuration server that will be serving the phones. When phones are unpacked out of a box and plugged in, the phone is hardcoded to contact the DES and retrieve information that will redirect them to the proper configuration server via HTTPS.

6 DES Architecture

7 4. PLANNING Resource Requirement for DES AWS Service Resource Configuration No of Instances require Comments EC2 Instance (Application Server) 2 Default storage space is 40 GB, for Production we should be using more ~100 GB storage RDS (Database Instace) 1 (RDS should be of type Productio n with Multizone feature enabled for failover) Postgres RDS instance default storage is 100 GB. Load Balancer NA Only configuration.

8 Auto Scaling Group Launch Configuratio n NA NA Only configuration. Only configuration. 1. Preparing EC2 Instance Amazon Linux AMI Type of EC2 instance needs to launch to deploy DES Server. Follow steps mentioned on to prepare DES Server EC2 instance. 2. Preparing Remote Database Service A postgresql Database Server Instance needs to be launch for DES Server. Follow steps mentioned on to prepare Postgresql Remote Database Service.

9 5. PREDEPLOYME NT AND CONFIGURATION TASK Installating prerequisite software All require software can be downloaded using yum software package installer on EC2 Instance. YUM in installed as part of Amazon Linux AMI instance. 1. Java JRE 1.8 $ su -c "yum install java openjdk" 2. Docker Follow steps mentioned on to install Docker Service. 3. AWS Cli Prerequisite Configuration 1. Installing RDS Certificate Download this attached RDS certificate and run the following command rds-combined-ca-b undle.pem $ sudo keytool -import -alias <alias_name> -keystore $JAVA_HOME/jre/lib/security/cacerts - file <rds_certificate_file_path> -storepass changeit -noprompt 2. Configuring AWS credentials After installing aws-cli, run the following command

10 $ aws configure AWS Access Key ID [None]: <accesskey> AWS Secret Access Key [None]: <secretkey> Default region name [None]: us-east-2 Default output format [None]: json Installation & Upgrade BIN Download the installation/upgrade script from the following attachment des-installer sh

11 6. DEPLOYME NT OF DEVICE ENROLLMENT SERVICE DES Fresh Installation $ sudo sh <install/upgrade_script_path> -- -m install -h <hostname/ip_of_database> -u <database_username> -p <database_user_password> -e AWS -c <identity_certificate_path> DES Upgrade $ sudo sh <install/upgrade_script_path> -- -m upgrade -h <hostname/ip_of_database> -u <database_username> -p <database_user_password> -e AWS -c <identity_certificate_path> -f 7. POST DE PLOYMENT VE RI FICATION Success of deployment can be verified by login in to or by verifying whether $ docker logs -f des-server contains the log WFSWARM99999: WildFly Swarm is Ready 8. MAINTENANCE Path for logs is /var/avaya/des/logs/