Hybrid cloud global services add-on customer discovery form

Customer gateway device

The physical or software device on the customers on-prem side of the VPN connection.

Office Location

The physical Office location for which the customer gateway device serves.
For Example "Cambridge"
This is used to uniquely identify each customer gateway name to which a site to site VPN is setup.

<CGW_OFFICE_LOC>

Vendor

The manufacturer of the customer gateway device.
For example, Cisco

<CGW_VENDOR>

Platform

The class of the customer gateway device.
For example, ISR Series Routers.

<CGW_PLATFORM>

Software Version

The operating system running on the customer gateway device.
For example, IOS 12.4

<CGW_SW_VERSION>

The internet-routable IP address for the device's external interface

The Internet-routable IP address for the gateways' external interface.
This public IP address value must be static. If your customer gateway is behind a network address translation (NAT) device that is enabled for NAT traversal (NAT-T), use the public IP address of your NAT device and adjust your firewall rules to unblock UDP port 4500.

<CGW_EXT_IF_IP_ADD>

The type of routing

Static or Dynamic

If your customer gateway device supports Border Gateway Protocol (BGP), specify dynamic routing.
If your customer gateway device does not support BGP, specify static routing.

<CGW_ROUTING_TYPE>

For dynamic routing, the Border Gateway Protocol (BGP) Autonomous System Number (ASN)

You can use an existing ASN assigned to your network. If you don't have one, you can use a private ASN in the 64512–65534 range.
Otherwise, the default ASN is 65000.

<CGW_BGP_ASN>

For static routing, the IP prefixes for your private network.

The following IP addresses:

For software VPN, the private /32 IP address of the software VPNhost (only required to allow keepalive script to run)

The /32 IP address of the on-prem Global server.

Note the /16 CIDR of the on-prem network must NOT overlap with the /16 CIDR of the Cloud UE VPC.

<CGW_PRIV_IP_PREFIXES>

VPN tunnels Security Options

Phase 1 Encryption Algorithms

Phase 2 Encryption Algorithms

Phase 1 Integrity Algorithms

Phase 2 Integrity Algorithms

Phase 1 DH Group Numbers

Phase 2 DH Group Numbers

IkeVersion

Customer Network

The /16 CIDR in which the on-prem Global server resides.

The /16 CIDR of the on-prem network must NOT overlap with the /16 CIDR of the Cloud UE VPC>
By default Cloud UE is setup with a 10.x/16 CIDR.

<CNW_CIDR>

AVEVA Global Daemon

Port

WCF NETtcp port for AVEVA Global daemon traffic.

Default (recommended) is 8000.

<DAEMON_PORT>

AVEVA Software

AVEVA Software versions

For the products relating to Globalized databases, the on-prem AVEVA Global, AVEVA Administration, AVEVA E3D, AVEVA Diagrams & AVEVA Engineering versions must match the versions deployed in Cloud UE. If they do not match, the customer will need to uplift their versions.

<GLOBAL_VERSION>

<ADMIN_VERSION>

<E3D_VERSION>

<DIAGS_VERSION>

<ENG_VERSION>

Projects

Customer Projects

List of projects customer wishes to Globalize.

<PROJECT_LIST>

Non-Dabacon Project Folders/Files

When generating the initial project database transfer set, by default this will include all auxiliary project folders (folders not dependent on databases).

It is usual that not all these folders and files are required, so a list of the required folders\files should be agreed in advance.

<NON_DABACON_PROJECT_FOLDER_FILE_LIST>

Tag Management

HUB location that will generate tags.

Only for projects using TMR, specify HUB location from which tags are created and managed.

<TMR_LOC>