First Published: 2017-11-16 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users are encouraged to try to correct the interference by using one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/tv technician for help. Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 2017 Cisco Systems, Inc. All rights reserved.
CHAPTER 1 Setting Up the Tetration Cluster Cisco Tetration Cloud, page 1 Preparing for the Tetration Cluster Setup, page 2 Deploying the Orchestrator, page 4 Setting Up the User Interface, page 5 Cisco Tetration Cloud The Tetration Cluster Cloud deployment option allows you to run Cisco Tetration Analytics software, which runs in a public cloud instance such as Amazon Web Services (AWS). You are responsible for purchasing the required AWS instances directly from AWS to run Cisco Tetration Analytics software. This deployment option is suitable when you need to collect and analyze telemetry from fewer than 1000 servers (virtual machine or bare metal). The monitored servers can be in AWS and an on-premises data center. If telemetry needs to be collected from the on-premises servers, then AWS Direct Connect or a VPN is required to connect to the Cisco Tetration Cloud platform. Note This release of Cisco Tetration Analytics Software supports cloud deployment only in AWS. The following table lists the number of instances, TBs, and addresses required for using Tetration. AWS Instance Type Required t2.medium 6 instances m4.large 15 instances m4.2xlarge 2 instances m4.xlarge 3 instances r4.large 13 instances 1
Preparing for the Tetration Cluster Setup Setting Up the Tetration Cluster AWS Instance Type r4.2xlarge r4.xlarge m4.4xlarge Amazon EBS: General-purpose SSD (gp2) Amazon EIP Required 23 instances 4 instances 8 instances 65 TB 50 addresses Preparing for the Tetration Cluster Setup Use a client device to complete the following steps before starting the Tetration Cluster setup. Be sure that the client device is setup with the following: The client device must be setup with the following: Microsoft Windows or Linux operating system Python software version 2.7 or later Access to the Internet Step 1 Create a new AWS account by going to https://portal.aws.amazon.com/gp/aws/developer/registration. a) Enter your userid, phone number, and password. b) Wait for a pin (typically a four-digit number). c) Receive a call from Amazon and enter the pin on the telephone. After you successfully enter the pin, Amazon announces that you have been authenticated. Online, you will be asked for a user plan. d) Select the appropriate user plan based on the amount of support that you must have, and click Continue. Step 2 On the AWS page that opens, verify that the AWS limits are set as needed by doing the following: a) On the AWS page, select the Services tab at the top of the page, and then select Compute > EC2. b) On the Resources page navigation pane, select Instances > Instances, and then select EC2 Dashboard > Limits. c) In the Support Center page that opens, do the following for each of the AWS limits that you must change (see the following table for the recommended limits): AWS Instance Type Recommended Limit Values t2.medium m4.large m4.2xlarge m4.xlarge 10 instances 20 instances 5 instances 5 instances 2
Setting Up the Tetration Cluster Preparing for the Tetration Cluster Setup AWS Instance Type r4.large r4.2xlarge r4.xlarge m4.4xlarge Amazon EBS: General-purpose SSD (gp2) Amazon EIP Recommended Limit Values 15 instances 25 instances 5 instances 10 instances 70 TB 50 addresses 1 Select your Region. 2 Select the Primary Instance Type. 3 Select the Limit type as Instance Limit. 4 Enter the New limit value. 5 If you need to change another limit, click the Add another request button and repeat steps i through iv. 6 In the Use Case Description text box, type the reason for these limit changes. 7 Click the Submit button at the bottom of the page. AWS lists a summary of your changes. Step 3 Step 4 Check for an email alert from Tetration for a password reset and other platform related events. Note See the email account that you indicated when setting up your AWS account (can use Sendgrid or Amazon CES). Create an S3 bucket in the new AWS account to be used for storing CloudFormation templates by doing the following: a) In the AWS page, click the Services tab at the top of the page. b) In the services page, click Storage > S3. c) In the Amazon S3 page, click the Create bucket button at the top of the page. d) In the Create bucket page, do the following: 1 In the Bucket name text box, type the name of the bucket. 2 In the Region box, select the appropriate region. 3 If you have settings to copy into the bucket from another bucket, in the Copy settings from an existing bucket box select the bucket with the settings that you must copy. 4 Click Create. Note Step 5 Provide your Cisco representatives with the following information so that they can install libraries and generate a set of AWS credentials: 3
Deploying the Orchestrator Setting Up the Tetration Cluster AWS IAM role API key API secret S3 bucket name What to Do Next After your Cisco representatives create the libraries and generate the AWS credentials, you are ready to run the Orchestrator deployment script. Deploying the Orchestrator Cisco provides a zip archive containing the following files: AwsHelperGuide.md config.yml This is the configuration file used to populate vital CloudFormationparameters. orchestrator.yml.j2 This is the Jinja2 template used to generate the CloudFormation template. tetration_cluster_launcher.py This script launches a Tetration cluster using the config.yml and orchestrator.yml.m2 files. vpc_peering_role.yml This file launches a CloudFormation stack that creates a VPC peering connection IAM role. Step 1 Look at the following values in the config.yml file and verify that they are set correctly: cluster_name The name of the Tetration cluster. This name must match the site name. vpc_cidr external_cidr region availability_zone s3_bucket_name The CIDR-formatted network range of the Tetration cluster VPC (string) CIDR-formatted network ranges to allow ingress to the Tetration UI (list) The AWS region where the Tetration cluster instances will be launched. The AWS availability zone where Tetration cluster instances will be launched. Currently, Tetration can be launched in only one availability zone. The name of the S3 bucket created in the Preparing for the Tetration Cluster Setup section. 4
Setting Up the Tetration Cluster Setting Up the User Interface Step 2 Execute the tetration_cluster_launcher.py script by using the tetration_cluster_launcher.py -c config.yml_path -t orchestrator.yml.j2_path command. Step 3 Follow the Tetration Setup Wizard using the link provided from running the tetration_cluster_launcher.py script. Note the IP addresses output by this script (output can also be found in the tetration_cluster_launcher.log file) for future use. 2017-05-31 09:23:43,111 - main - INFO - ****************************** 2017-05-31 09:23:43,111 - main - INFO - 2017-05-31 09:23:43,111 - main - INFO - Cluster Setup URL: http://10.0.0.1:9090/ 2017-05-31 09:23:43,111 - main - INFO - 2017-05-31 09:23:43,111 - main - INFO - ****************************** 2017-05-31 09:23:43,111 - main - INFO - Internal Network: 10.0.0.0/17 2017-05-31 09:23:43,111 - main - INFO - External Network: 10.0.128.0/17 2017-05-31 09:23:43,111 - main - INFO - External Gateway: 10.0.128.1 2017-05-31 09:23:43,111 - main - INFO - DNS Resolver: 10.0.0.2 2017-05-31 09:23:43,111 - main - INFO - NTP Servers 0.amazon.pool.nrg 1.amazon.pool.ntp.org 2.amazon.pool.ntp.org 3.amazon.pool.ntp.org 2017-05-31 09:23:43,111 - main - INFO - 2017-05-31 09:23:43,111 - main - INFO - ****************************** What to Do Next Set up the UI using the output from the Orchestrator deployment output. Setting Up the User Interface After deploying the orchestrator, you are ready to use the output of that operation to set up the Tetration user interface. Step 1 Open a new browser window and enter the Cluster Setup URL from the orchestrator deployment output. The new browser displays the TetrationSetup RPM Upload page. 1 Open a new window or tab for a window. 2 Enter the Cloud Setup URL in this field. Keep the browser window displaying the CloudFormation Manager open for use later in this process. 5
Setting Up the User Interface Setting Up the Tetration Cluster Step 2 Step 3 In the CloudFormation Manager browser window, click the Services tab. The AWS Services page opens. Click the S3 link in the Storage section of this window. 1 Click on a resource group (S3). Note The Tetration cloud supports only URL uploads (S3 or other). 6
Setting Up the Tetration Cluster Setting Up the User Interface The Amazon S3 window opens and lists bucket names. Step 4 Step 5 Click on a bucket name. The Objects page opens for that bucket. Upload RPM objects to the Tetration cloud as follows: 1 Select one or more of the listed objects. A Download as box opens and lists the URL link to the object. 2 Upload the required objects in one of the following ways: Select each required object and click the Upload button. If security requires it, upload each required object using a temporary URL for the object as follows: 1 Click the More button and click on the Download As command. A Download As box opens listing the link for the selected object. 2 Click on the object link in the Download As window. 3 Right click and select the Copy Link Address command. 4 Click the Tetration Setup browser tab. The RPM Upload window opens listing the temporary RPM URL for the object that you can use for the upload. 5 Click the Upload button. The RPM object uploads to the Tetration cluster. Step 6 Step 7 Repeat the previous step for the Mother RPM object. After you upload both objects, the Site Config window opens in the Tetration Setup browser tab. Use the General, Email, Network, Service, and UI forms on the Site Config page to set up the new site as follows: General form 1 In the Site Name field, type the unique cluster name. 2 In the SSH Public Key field, paste the authentication key. Note Generate your own SSH key pair, which can be used for cluster SSH access. 3 Click Next. Email form 1 Fill in the required email addresses. 2 Click Next. Network form 1 In the Internal network IP address field, paste the address from the orchestrator deployment output. 7
Setting Up the User Interface Setting Up the Tetration Cluster 2 In the External network IP address field, paste the address from the orchestrator deployment output. 3 In the External gateway IP address field, paste the address from the orchestrator deployment output. 4 In the DNS resolver IP address field, paste the address from the orchestrator deployment output. 5 In the DNS domain field, enter your DNS domain (for example, "cisco.com"). 6 Click Next. Service form 1 In the NTP Servers field, enter the space-separated list of NTP server names or IP addresses from the Orchestrator deployment output. 2 In the SMTP Server field, enter the name or IP address of an SMTP server that can be used by Tetration for sending email messages (this server must be accessible by Tetration). 3 In the SMTP Port field, enter the port number of the SMTP server. AWS restricts the use of ports 25 and 465. You must configure your account correctly or use port 587. 4 In the SMTP Username field, enter the user name for SMTP authentication. 5 In the SMTP Password field, enter the password for SMTP authentication. 6 Click Next. UI form 1 In the UI VRRP VRID field, enter "77" unless you need a unique VRID. 2 In the UI FQDN field, enter the fully qualified domain name where you will access the cluster. 3 In the UI Airbrake Key field, leave blank. 4 Click Continue. Step 8 In the Site Config Check page that opens, check your settings. Note These settings cannot be modified after continuing from this page. If you must change any settings, click Back. If you do not need to make any changes, click Continue. The Tetration Setup Window opens to indicate the status of the VMs. Step 9 Step 10 In the S3 Management Console browser window, click the CloudFormation link in the navigation area on the left. To check your setup, do the following: 1 Log into AWS. The CloudFormation Stacks page opens. 2 Verify that the required stacks have the CREATE_COMPLETE status. To list the stacks with a specific string of characters in their name, type the characters in the search field. 8
Setting Up the Tetration Cluster Setting Up the User Interface Step 11 Select the Tetration Setup browser tab to display the instances being deployed. When complete, Tetration indicates that the cluster is deployed and how to access it. Congratulations! Tetration Cluster Deployed. Access the cluster cluster_name using the UI VIP ip_address... 9
Setting Up the User Interface Setting Up the Tetration Cluster 10