Cisco CSR 1000v Deployment Guide for Microsoft Azure

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

Cisco CSR 1000v Deployment Guide for Microsoft Azure

Chapter Title

How to Deploy a Cisco CSR 1000v on Microsoft Azure

PDF - Complete Book (3.08 MB) PDF - This Chapter (1.31 MB)
View with Adobe Reader on a variety of devices

Results

Updated:: April 23, 2018

Chapter: How to Deploy a Cisco CSR 1000v on Microsoft Azure

Customize the Microsoft Azure Portal
Deploy a CSR 1000v with Multiple Interfaces on Microsoft Azure
Deploy a CSR 1000v with a Single Interface on Microsoft Azure
Access the Cisco CSR 1000v CLI

How to Deploy a Cisco CSR 1000v on Microsoft Azure

Customize the Microsoft Azure Portal
Deploy a CSR 1000v with Multiple Interfaces on Microsoft Azure
Deploy a CSR 1000v with a Single Interface on Microsoft Azure
Access the Cisco CSR 1000v CLI

Customize the Microsoft Azure Portal

You can customize the Microsoft Azure portal GUI by adding frequently used objects, such as virtual machines or virtual network to the left-hand side panel.

Note

You only need to perform these optional steps if you are going to deploy a Cisco CSR 1000v using a single interface, where the resources need to be added manually. You do not need to create these resources manually, if you are going to deploy a Cisco CSR 1000v with 2, 4 or 8 interfaces using a solution template.

Before You Begin

To customize the portal, you must have a Microsoft Azure subscription.

SUMMARY STEPS

1. Sign in to Microsoft Azure.

2. Click Browse and select an object to be added to the left hand side panel.

3. In the drop-down menu, click the star symbol for your chosen object.

DETAILED STEPS

	Command or Action	Purpose
Step 1	Sign in to Microsoft Azure.
Step 2	Click Browse and select an object to be added to the left hand side panel.
Step 3	In the drop-down menu, click the star symbol for your chosen object.	The details of this object are saved for future use. Repeat steps 2 and 3 to add a series of objects to the left-hand side panel.

Deploy a CSR 1000v with Multiple Interfaces on Microsoft Azure

Perform the following steps to deploy a Cisco CSR 1000v with multiple interfaces, on Microsoft Azure.

Command or Action

Purpose

Step 1

Select Virtual machines in the left hand side panel.

Step 2

Click Add.

Step 3

Enter "csr".

Finds Cisco CSR 1000v VM deployments in the Azure Marketplace.

Step 4

Choose a deployment.

For example, choose multiple interface deployment: Cisco CSR 1000v - XE 16.7 Deployment with 2 NICs.

Step 5

Click Create.

Step 6

Name—Select the Basics sub-menu and enter a name for the virtual machine.

Name of the cloud-based network used by Microsoft Azure to represent a private network.

Step 7

Username—Select a user name.

Username for the Cisco CSR 1000v virtual machine, which you can use to log into the Cisco CSR 1000v.

Note

For Cisco IOS XE version 3.16 and Cisco IOS XE 16.4, if you are going to enter an SSH public key as an authentication type, to access the CSR, set “Username” to “azureuser”.

Step 8

Authentication type—Enter a Password (default) or SSH public key.

Step 9

SKU—Select a Cisco IOS XE version.

Step 10

Subscription—(Optional) Change the subscription name.

Name of the subscription. A default subscription name is provided, based on the name of the virtual machine. You can change this default subscription name.

Step 11

Resource Group—Select either Create new or Use existing.

You can only create a Cisco CSR 1000v in a new Resource Group (or in a completely empty existing resource group). To remove a Resource Group, first delete the Cisco CSR 1000v VM and then delete the Resource Group.

Step 12

Click OK.

Step 13

License Type—Select the Cisco CSR Settings sub-menu and then select License Type.

Step 14

Select license type: BYOL or PAYG license.

Step 15

(Optional) For the PAYG license, select either the AX or SEC technology package.

Step 16

Network—Enter the address of the virtual network.

Example:10.4.1.0/16

Enter the address of the virtual network using Classless Inter-Domain Routing (CIDR) notation.

Step 17

Virtual machine size—Select D2_v2 or DS2_v2.

Microsoft Azure supports different image types with different performance expectations. (Search for “D-series VM size” on the Microsoft Azure website to see the D-Series Performance Expectations.)

Step 18

Managed Disk—Select Enabled.

Step 19

Availability Set—Select Yes.

Step 20

Availability Set name—Enter a name for the availability set.

Step 21

Availability Set fault domain count—Enter the availability set fault domain count.

Fault domains define the group of VMs that share a common power source and network switch. Availability sets arrange virtual machines across fault domains.

Step 22

Availability Set update domain count—Enter the availability set update domain count.

An update domain is a group of VMs and underlying physical hardware that can be rebooted at the same time.

Step 23

Storage Account—Enter a storage account name.

For more information on storage accounts, see Microsoft Azure Resources.

Step 24

Boot diagnostics—Enter the boot diagnostics.

For more information on boot diagnostics, see Microsoft Azure Resources.

Step 25

Diagnostics Storage account—Enter the storage account name.

For more information on storage accounts, see Microsoft Azure Resources.

Step 26

Public IP Address—Enter the public IP address name.

For more information on the public IP address, see Microsoft Azure Resources.

Step 27

DNS label—(Optional) Change the name of the DNS label.

The DNS label is the name of the public IP address to be assigned to the Cisco CSR 1000v. A default value for the DNS label is shown in the text box, which is the VM name followed by "-dns".

Step 28

Virtual network—Choose one of the following: Select New or Use existing.

For a new virtual network, enter the name and IP address.

Step 29

Click Subnets—Enter the subnet names and IP addresses.

For more information on subnets, see "Interfaces" in Microsoft Azure Resources.

Step 30

Click OK.

The 3 Summary sub-menu is highlighted.

Step 31

Click OK.

The 4 Buy sub-menu is highlighted.

Step 32

Click Create

The VM is created and the purchase is confirmed.

Step 33

Click Virtual machines on the left hand panel.

After a delay of a few minutes, the status of the recently created VM changes from “Creating” to “Running”. Make a note of the Public IP address name.

What to Do Next

Go to Access the Cisco CSR 1000v CLI, which explains how to ssh into the Cisco CSR 1000v.

Deploy a CSR 1000v with a Single Interface on Microsoft Azure

Perform the following steps to deploy a Cisco CSR 1000v with a single interface, on Microsoft Azure.

Note

If you are deploying a Cisco CSR 1000v with a 2-, 4- or 8- NICs solution template, the following steps are not required. Instead, go to the Microsoft Azure portal and determine the public IP address of the Cisco CSR 1000v. Then, ssh into the Cisco CSR 1000v as described in Access the Cisco CSR 1000v CLI.

	Command or Action	Purpose
Step 1	Select Virtual machines in the left hand side panel.
Step 2	Click Add.
Step 3	Enter `csr`. A search starts, to find any Cisco CSR 1000v VM deployments in the Azure Marketplace.
Step 4	Choose a deployment.	Example: Cisco CSR 1000v Bring Your Own License - XE 16.7.
Step 5	Click Create.	The Basics sub-menu is highlighted.
Step 6	Name—Enter the name of the virtual network.	The virtual network is a cloud-based network used by Microsoft Azure to represent the private network.
Step 7	VM disk type—Select a VM disk type.	The VM disk type is either SSD or HDD.
Step 8	User name	Username for the Cisco CSR 1000v virtual machine. This is the username that you will use to log into the Cisco CSR 1000v. For Cisco IOS XE version 3.16 and Cisco IOS XE 16.4, to enter an SSH public key to access the CSR set the “`Username`” field to “`azureuser`”.
Step 9	Authentication type—Enter a Password (default) or SSH public key.
Step 10	Subscription—Select the name of a subscription.	A default name based on the name of the virtual machine is provided. You can change the default name.
Step 11	Resource Group—Create a new group by selecting Create new or select an existing group by selecting Use existing.	Specifies the name of a new or existing resource group.
Step 12	Click OK.	The Size sub-menu is highlighted.
Step 13	Click Virtual machine size	For further information on virtual machine size, see Sizes for Windows virtual machines in Azure.
Step 14	Click OK.	The Settings sub-menu is highlighted.
Step 15	High Availability—Select an existing availability set or create a new availability set.	To use High Availability, select an existing availability set or create a new availability set.
Step 16	Storage—Enter the storage account name.	Enter the storage account name, if you are using Managed Disks to manage the storage accounts of VM disks.
Step 17	Virtual network—Enter the virtual network address.	Enter the address of the virtual network using Classless Inter-Domain Routing (CIDR) notation. Example: `10.4.1.0/16`
Step 18	Subnet——Enter the subnet IP address.
Step 19	Public IP address—Enter the public IP address name.	The IP address is provided by Azure.
Step 20	Network Security groups—Enter the name of a network security group.
Step 21	Auto-shutdown	To enable auto-shutdown, set Enable to "On". To disable auto-shutdown set Enable to "Off". For more information on auto-shutdown, search for "auto-shutdown" in the Microsoft Azure Documentation.
Step 22	(Optional) Monitoring—Select "Monitoring" to enable monitoring.	Enables Cisco CSR 1000v monitoring, using boot diagnostics. If you enable monitoring, you must also enter the boot diagnostics account name.
Step 23	Click OK.	The 4 Summary sub-menu is highlighted. The summary details of the VM that is about to be deployed are displayed on the screen.
Step 24	Click Create.	The VM is created and the purchase is confirmed.
Step 25	Click Virtual machines on the left hand panel.	Verifies the VM status. After a few minutes, the VM status changes from “Creating” to “Running”. Make a note of the Public IP address name.

What to Do Next

Go to Access the Cisco CSR 1000v CLI, which explains how to ssh into the Cisco CSR 1000v.

Access the Cisco CSR 1000v CLI

Access the CLI of the Cisco CSR 1000v VM via a terminal server.

Before You Begin

Before you access the CLI, perform the steps in one of the preceding deployment procedures (Deploy a CSR 1000v with a Single Interface on Microsoft Azure or Deploy a CSR 1000v with Multiple Interfaces on Microsoft Azure).

SUMMARY STEPS

1. Enter the ssh command using a command syntax from one of the two substeps below.

If you did not previously use an SSH public key (you did not specify a username of “azureuser”, then you can access the Cisco CSR 1000v CLI using the following command: ssh –o ServerAliveInterval=60 username@csr_ip_address
If you did previously use an SSH public key (you did specify a username of “azureuser”), then you can access the Cisco CSR 1000v CLI using the following command: ssh –ikey-o ServerAliveInterval=60 azureuser@csr_ip_address

DETAILED STEPS

	Command or Action	Purpose
Step 1	Enter the ssh command using a command syntax from one of the two substeps below. If you did not previously use an SSH public key (you did not specify a username of “azureuser”, then you can access the Cisco CSR 1000v CLI using the following command: ssh –o ServerAliveInterval=60 username@csr_ip_address If you did previously use an SSH public key (you did specify a username of “azureuser”), then you can access the Cisco CSR 1000v CLI using the following command: ssh –ikey-o ServerAliveInterval=60 azureuser@csr_ip_address	Enter the ssh command in a terminal server of your choice to access the CLI .

In the following example, username=“azureuser”, public IP address = 40.121.148.7 and password=xxx are used as parameters in the ssh command, before other commands such as show ip route. No ssh public key was previously specified.)

$ ssh –o ServerAliveInterval=60  azureuser@40.121.148.7 
                The authenticity of host '40.121.148.7 (40.121.148.7)' can't be established.
                RSA key fingerprint is 94:79:e9:d2:2e:85:93:d6:52:41:cc:a3:d9:14:7f:5f.
                Are you sure you want to continue connecting (yes/no)? yes
                Warning: Permanently added '40.121.148.7' (RSA) to the list of known hosts.
                Password: mypassword

# show ip int br
                Interface              IP-Address      OK? Method Status                    Protocol
                GigabitEthernet1       10.4.1.4        YES DHCP   up                        up      
                GigabitEthernet2 	unassigned     YES unset  administratively down     down

# configure terminal
                Enter configuration commands, one per line.  End with CNTL/Z.
                # interface g2
                # ip address dh
                # ip address dhcp
                # no shutdown
                # end
                # show run interface g2
                Building configuration...
                Current configuration : 69 bytes
                !
                interface GigabitEthernet2
                ip address dhcp
                negotiation auto
                end
                # show ip interface brief
                Interface              IP-Address      OK? Method Status                Protocol
                GigabitEthernet1       10.4.0.4        YES DHCP   up                    up
                GigabitEthernet2       10.4.1.4        YES DHCP   up                    up
                
                # show ip route
                <output snipped for brevity>
                Gateway of last resort is 10.4.1.1 to network 0.0.0.0
                
                S*    0.0.0.0/0 [1/0] via 10.4.1.1
                10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
                C        10.4.1.0/24 is directly connected, GigabitEthernet1
                L        10.4.1.4/32 is directly connected, GigabitEthernet1
                C        10.4.2.0/24 is directly connected, GigabitEthernet2
                L        10.4.2.4/32 is directly connected, GigabitEthernet2
                168.63.0.0/32 is subnetted, 1 subnets
                S        168.63.129.16 [254/0] via 10.4.1.1