PDF(906.9 KB) View with Adobe Reader on a variety of devices
ePub(909.8 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(892.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 29, 2021
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
An active subscription to Google Cloud Platform with a project created
Bash terminal, Putty, or SecureCRT
Public and private Secure Shell (SSH) Keys
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
From 17.4.1 onwards, the CSR1000v becomes C8000v with the same functionality but new features added such as SDWAN and DNA licensing. For further reference, please verify the official products datasheet:
Select the VPC and subnet created before and choose Ephemeral in external IP, in order to have a Public IP associated with the instance as shown in the image.
After this is configured. Select the launch button.
Note: Port 22 is needed to connect to the CSR instance via SSH. The HTTP port is optional.
Once the deployment is completed, select Compute Engine > VM instances in order to verify that the new CSR1000v was deployed successfully as shown in the image.
Connect Remotely to the New Instance
The most common methods to log in to a CSR1000v/C8000V in GCP are the command line in a Bash terminal, Putty and SecureCRT. In this section, the configuration needed to connect with the previous methods.
Log in to CSR1000v/C8000v with Bash Terminal
The syntax needed to connect remotely to the new CSR is:
ssh -i private-key-path username@publicIPaddress
$ ssh -i CSR-sshkey <snip>@X.X.X.X The authenticity of host 'X.X.X.X (X.X.X.X)' can't be established. RSA key fingerprint is SHA256:c3JsVDEt68CeUFGhp9lrYz7tU07htbsPhAwanh3feC4. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'X.X.X.X' (RSA) to the list of known hosts.
If the connection is successful, CSR1000v prompt is displayed
$ ssh -i CSR-sshkey <snip>@X.X.X.X
csr-cisco# show version Cisco IOS XE Software, Version 16.09.01 Cisco IOS Software [Fuji], Virtual XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 16.9.1, RELEASE SOFTWARE (fc2) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2018 by Cisco Systems, Inc. Compiled Tue 17-Jul-18 16:57 by mcpre
Log in to CSR1000v/C8000v with PuTTY
To connect with Putty, use the PuTTYgen application in order to convert the private key from PEM to PPK format.