Home > Articles > CSR 1000V Software Architecture

CSR 1000V Software Architecture

Chapter Description

In this sample chapter from Virtual Routing in the Cloud, explore the software and data plane design of the CSR 1000V, a virtualized software router that runs the IOS XE operating system.

From the Book

Virtual Routing in the Cloud

Virtual Routing in the Cloud

$47.99 (Save 20%)

Installing the CSR 1000V on a VMware Hypervisor

The process for installing the CSR 1000V on a VMware hypervisor has two phases:

  1. Bring up the VM with the CSR 1000V on ESXi.

  2. Connect the VNIC with the CSR 1000V.

These phases can be subdivided into the step-by-step procedures described in the following sections. To learn about automated provisioning using the BDEO (build, deploy, execute OVF), see Chapter 7, “CSR in the SDN Framework.”

The following steps assume ESXi is already installed. Please refer to the VMware ESXi installation guide for setting up the ESXi if it is not already installed.

Bringing Up the VM with the CSR 1000V on ESXi

Assuming ESXi is already installed, you can now follow these steps in the first phase of installing the CSR 1000V:

  • Step 1. Deploy the OVF template:

    1. Download the OVF template from software.cisco.com and select CSR 1000V software.

    2. Log on to the vSphere client, as shown in Figure 4-9.

      Figure 4-9

      Figure 4-9 Installing the OVF Template for the CSR 1000V

    3. Upload the CSR OVF file you downloaded from cisco.com as shown in Figure 4-9.

    4. Select File, Deploy OVF Template, as shown in Figure 4-9.

  • Step 2. Upload the CSR OVF file as shown in Figure 4-10.

    Figure 4-10

    Figure 4-10 Deploying the OVF Template: Selecting the Source

  • Step 3. When the OVA upload is done, verify the OVF template details on the screen shown in Figure 4-11.

    Figure 4-11

    Figure 4-11 Deploying the OVF Template: Verifying the Template Details

    The release information, product, size, and so on are received from the metadata. Follow the directions for creating the VM.

    Complete the following deployment configuration, disk formatting, and network mapping screens, as shown in Figures 4-12 through 4-16:

    1. As shown in Figure 4-12, select the hardware profile: Small, Medium, or Large vCPU and RAM, based on the deployment considerations. Refer to the hypervisor documentation for the exact small, medium, and large VM configurations. (You can change this configuration for memory even after the CSR 1000V is brought up.)

      Figure 4-12

      Figure 4-12 Deploying the OVF Template: Selecting the System Memory Profile for CSR 1000V

    2. Select the appropriate type of disk formatting (see Figure 4-13), and then click Next:

      • Thick Provision Lazy Zeroed—With this option, a virtual disk is created with the amount of disk space it has asked for. However, the disk is not cleaned during virtual disk creation. It is cleaned only when you create the first VM on it.

      • Thick Provision Eager Zeroed—With this option, a virtual disk is created with the amount of disk space it has asked for. However, the disk is cleaned during virtual disk creation.

      • Thin Provision—Choose this option to save space. Initially, the space allocated to a thin disk is less. However, the virtual disk keeps growing as memory requirements grow.

      Figure 4-13

      Figure 4-13 Deploying the OVF Template: Choosing the Disk Provisioning Format

    3. On the screen shown in Figure 4-14, specify network mapping of the source networks (GigabitEthernet) to the destination networks (VM Network by default) mapping allocation.

      Figure 4-14

      Figure 4-14 Deploying the OVF Template: Network Mapping

    4. Look over the summary of the deployed CSR 1000V configuration, as shown in Figure 4-15, and click Finish.

      Figure 4-15

      Figure 4-15 Deploying the OVF Template: Checking the Settings

  • Step 4. When the deployment of the CSR 1000V is complete, boot the router by selecting the VGA console from the GRUB menu on the Console tab shown in Figure 4-16.

    Figure 4-16

    Figure 4-16 CSR 1000V Console Tab

  • Step 5. At the router prompt, enter platform console serial, as shown in Figure 4-17. (This command causes the VM to send console information on the serial port from ESXi in the later steps.)

    Figure 4-17

    Figure 4-17 CSR 1000V Command Prompt

  • Step 6. To add the serial port for console access, access the vCenter web client and select Virtual Hardware, Network Adaptor, Serial Port, as shown in Figure 4-18.

    Figure 4-18

    Figure 4-18 VM Access from the vCenter Web Client

  • Step 7. Shut down the guest OS as shown in Figure 4-19. (Note that this serial port will be used for terminal access to the CSR.)

    Figure 4-19

    Figure 4-19 Configuring the Serial Interface: Shutting Down the Router

  • Step 8. Select Add New Device, New Serial Port and provide the IP address and terminal port details to access the CSR, as shown in Figure 4-20.

    Figure 4-20

    Figure 4-20 Configuring the Serial Interface: Setting the Telnet Address

  • Step 9. Go to vCenter and select Setting, Security Profile. Edit security configuration ports 23 and 1024 as shown in Figure 4-21. This is needed because by default ESXi blocks console access.

    Figure 4-21

    Figure 4-21 Configuring the Serial Interface: Firewall Settings

  • Step 10. Enable ports 23 and 1024 as shown in Figure 4-22.

    Figure 4-22

    Figure 4-22 Configuring the Serial Interface: Security Profile Detail

  • Step 11. Use Telnet to verify the access from the PC. (It’s a good practice to use SSH for accessing the CSR VM; however, for the sake of simplicity, this example shows Telnet access setup.) The EXSi hypervisor defaults the network connections to the VM Network virtual switch connection. The network adapters are mapped to CSR interfaces. For example, GigabitEthernet1 is mapped to Network adapter 1, and so on. You can verify this by comparing the MAC address as illustrated in Figure 4-23.

    Figure 4-23

    Figure 4-23 CSR 1000V Telnet Access Screen

  • Step 12. To remap the network adapters to corresponding vNICs, you should perform the following steps. From the vSphere client in the Edit Settings window, select New Device Add, Networking and add vNICs to the CSR as assigned interfaces (from the vCenter web client), as shown in Figures 4-24 through 4-27. (Allow all VLANs and create a bridgeForVNIC1 label for this connection.)

    Figure 4-24

    Figure 4-24 vNICs and the CSR 1000V: Selecting the Connection Type

    1. Select the new vNIC, as shown in Figure 4-25, to create a new standard switch name.

      Figure 4-25

      Figure 4-25 vNICs and the CSR 1000V: Creating a Standard Switch

    2. Add VLANs and the network label assigned for the vNIC, as shown in Figure 4-26.

      Figure 4-26

      Figure 4-26 vNICs and the CSR 1000V: Setting the Connection Settings

    3. Complete the configuration of the vNIC with a VLAN and label attachment that can be referenced in a vSwitch. Click Finish to complete this step, as shown in Figure 4-27.

      Figure 4-27

      Figure 4-27 vNICs and the CSR 1000V: Completing the Configuration

  • Step 13. Go to the vSphere web client and select Virtual Machine, Network Adapter. In the Networking tab, look for the new bridgeForVNIC1 label you created earlier, as shown in Figure 4-28. You should note that this label acts as mapping between the CSR interface and the vNIC.

    Figure 4-28

    Figure 4-28 vNICs and the CSR 1000V: Editing the Settings

    Repeat Steps 12 and 13 to remap additional network adapters to vNICs available to the CSR.

    To map the network adapter to the vNIC created, select the vNIC label created in the previous step. The CSR 1000V is now configured and connected to the physical NIC, as shown in Figure 4-29.

    Figure 4-29

    Figure 4-29 vNICs and the CSR 1000V: Interface Summary Screen

4. Installing the CSR 1000V on a KVM Hypervisor | Next Section Previous Section

There are currently no related articles. Please check back later.