Support
Accounts & Users
Backup
Blueprints
CenturyLink Private Cloud on VMware Cloud Foundation
Cloud Application Manager
Administering Your Organization
Analytics
Automating Deployments
Billing
Cloud Optimization
Core Concepts
DR Readiness
Data Center Edition
Deploying Anywhere
FAQ
Getting Started
Integrating with Jenkins
Managed Services
Monitoring
Troubleshooting
Tutorials
Compliance
Control Portal
Database
Dedicated Cloud Compute
Disaster Recovery
Overview
SafeHaven 3
SafeHaven 4
SafeHaven 5 CLC to AWS
SafeHaven 5 CLC to Azure
SafeHaven 5 CLC to CLC
SafeHaven 5 CPC-vCF to CLC
SafeHaven 5 General
SafeHaven 5 Manual to AWS
SafeHaven 5 VMware to AWS
SafeHaven Migration
General
Managed Services
Marketplace
Network
Object Storage
Release Notes
Runner
Security
Servers
Service Tasks
Support
Accounts & Users
Backup
Blueprints
CenturyLink Private Cloud on VMware Cloud Foundation
Cloud Application Manager
Administering Your Organization
Analytics
Automating Deployments
Billing
Cloud Optimization
Core Concepts
DR Readiness
Data Center Edition
Deploying Anywhere
FAQ
Getting Started
Integrating with Jenkins
Managed Services
Monitoring
Troubleshooting
Tutorials
Compliance
Control Portal
Database
Dedicated Cloud Compute
Disaster Recovery
Overview
SafeHaven 3
SafeHaven 4
SafeHaven 5 CLC to AWS
SafeHaven 5 CLC to Azure
SafeHaven 5 CLC to CLC
SafeHaven 5 CPC-vCF to CLC
SafeHaven 5 General
SafeHaven 5 Manual to AWS
SafeHaven 5 VMware to AWS
SafeHaven Migration
General
Managed Services
Marketplace
Network
Object Storage
Release Notes
Runner
Security
Servers
Service Tasks
Updated by Mahima Kumar on Dec 27, 2017
Article Code: kb/118
Article Overview
This article focusses on how to Register SRNs within the SafeHaven Console for CenturyLink Cloud and AWS.
Requirements
- SafeHaven Cluster already installed.
- CMS and SRNs to have proper network connectivity.
Assumptions
- SafeHaven Cluster already installed with proper network connectivity between CMS-SRN and SRN-SRN.
- Data centers already registered.
Register SRN
Right-click on the any registered Data Center within the Navigation Tree and select Register SRN from the drop-down menu.
Fill in the following fields:
- SRN hostname as the Node Name.
- SRN Root Password (set at the time of SRN deployment).
- Service IP: SRN IP used to communicate with other SafeHaven Nodes (SRN and CMS). Typically set as the Private IP of the SRN.
- WAN Replication IP: SRN IP used to communicate with the peer SRN for WAN replication. Typically set as the Private IP of the SRN.
- Local iSCSI IP: SRN IP used to communicate with the production/recovery servers in its native Datacenter. Typically set as the Private IP of the SRN. Note: This is not required for AWS SRN registration.
- Do not modify the Service Port (TCP) and Heartbeat Port (UDP).
NOTE: Incase SRN has multiple NIC's, Service IP and WAN Replication IP will be the Primary IP of the SRN which has proper network connectivity to other SRN's and CMS. Local iSCSI IP will be set to 0.0.0.0
NOTE: Follow the same procedure to register the all the SRN's within the SafeHaven Console. For AWS SRN the Local iSCSI IP and Service IP are the same.
The above procedure stays the same for CLC/VMWare/Manual sites as the source data centers.
Next Step is to Add SRN Peer