HPE FlexNetwork VSR1000 Virtual Service Router Installation and Getting Started Guide Part number: 5998-8295R Software version: VSR1000_HPE-CMW710-E0321P01-X64 Document version: 5W101-20160106

© Copyright 2016 Hewlett Packard Enterprise Development LP

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.

Microsoft® and Windows® are trademarks of the Microsoft group of companies.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

i

Contents

Acknowledgments ···························································································· i Overview ········································································································· 1 

Installing the HPE VSR1000 ··········································································· 2 

Installation requirements ···································································································································· 2 Hardware requirements ······························································································································ 2 Software requirements ······························································································································· 2 

Installing the VSR on the VMware platform ······································································································· 3 Installing the VSR through the ISO image ································································································· 3 Installing the VSR through the OVA template ·························································································· 21 Installing a VSR through the OVA template by using the automatic deployment tool······························ 26 

Installing the VSR on the KVM platform ··········································································································· 31 Installing the VSR through the ISO image ······························································································· 31 

Deployment instructions ··································································································································· 43 Mapping VSR network interfaces to virtual NICs ····················································································· 43 Adding or deleting VSR network interfaces ······························································································ 44 Mapping VSR interfaces to vSwitch interfaces ························································································ 45 

Upgrading and recovering the VSR ······························································ 49 

Upgrading the VSR ·········································································································································· 49 Upgrading the VSR at the CLI ·················································································································· 49 Upgrading the VSR through the ISO image ····························································································· 49 

Recovering the VSR through the ISO image ··································································································· 49 Registering the software ··············································································· 51 

Registering the license ····································································································································· 51 Requesting a 90-day evaluation license ·································································································· 51 Registering a purchased license ·············································································································· 52 Uploading the device ID file ····················································································································· 53 

Installing the license key file ···························································································································· 55 Obtaining the license key file ··················································································································· 56 Installing the license key file ····················································································································· 56 

Appendix A Installing the KVM platform ························································ 58 

KVM overview ·················································································································································· 58 Installing the KVM platform ······························································································································ 58 

Appendix B Configuring the Intel 82599 VF NIC ··········································· 71 

Intel 82599 VF NIC overview ··························································································································· 71 Configuring the BIOS server ···························································································································· 71 Configuring the virtual platform ························································································································ 72 

Configuring Intel 82599 VF NICs on the VMware platform ······································································ 72 Configuring Intel 82599 VF NICs on the KVM platform ············································································ 76 

Document conventions and icons ································································· 81 

Conventions ····················································································································································· 81 Network topology icons ···································································································································· 82 

Support and other resources ········································································ 83 

Accessing Hewlett Packard Enterprise Support ······························································································ 83 Accessing updates ··········································································································································· 83 

Websites ·················································································································································· 84 Customer self repair ································································································································· 84 Remote support ········································································································································ 84 Documentation feedback ························································································································· 84 

ii

Index ············································································································· 86 

1

Overview The HPE VSR1000 virtual router is controlled by licenses. Based on a license, the HPE VSR1000 virtual router can provide the corresponding functions, performance, and usage life to meet the network requirements of users.

2

Installing the HPE VSR1000

Installation requirements Hardware requirements

Table 1 shows the minimum hardware requirements for a virtual machine (VM) to host the HPE VSR1000.

Table 1 Minimum hardware requirements for a VM to host the VSR1000

Item Minimum requirements Processor One vCPU (main frequency≥ 2.0 GHz)

Memory 1 GB

Hard disk One vHD, 8 GB

Network interface card Two virtual NICs. A maximum of 16 virtual NICs are supported.

Virtual NIC types

• E1000 (VMware ESXi and Linux KVM) • VMXNET3 (VMware ESXi) • VirtIO (Linux KVM) • InteI 82599 VF (VMware ESXi and Linux KVM)

Software requirements Table 2 shows the minimum software requirements for a VM to host the HPE VSR1000.

Table 2 Minimum software requirements for a VM to host the VSR1000

Virtual machine platform Minimum requirements VMware ESXi VMware ESXi 4.1, 5.0, 5.1, and 5.5

Linux KVM

Linux KVM (Linux Kernel > 2.6.25), the recommended Linux distributions: • CentOS 6.3 • Ubuntu 12.10 • RedHat Enterprise Linux (RHEL) 6.3 • SUSE Server 11SP2

NOTE: The virtual machine platform software versions provided in Table 2 are for reference. For more information about the software versions compatible with the HPE VSR1000 virtual router, see its release notes.

"Appendix A Installing the KVM platform" describes the CentOS 6.3 configuration and installation procedures. For more information about installing other virtual machine platform software, see the related documents for the selected virtual machine software.

3

Installing the VSR on the VMware platform You can install an HPE VSR1000 virtual router on the VMware platform by using the following methods: • Using the ISO image. • Using the OVA template. • Using the automatic deployment tool to deploy the OVA template.

Installing the VSR through the ISO image Creating a new virtual machine on the VMware virtual platform

1. On the VMware vSphere client, enter the virtual machine server address, enter the username and password for login, and then click Login, as shown in Figure 1.

Figure 1 Logging in to the virtual machine server

NOTE: • To get the username and password for logging in to the VMware virtual machine server,

contact the administrator of the server. • When the security certificate alarm page appears during the login process, click Ignore to

ignore the certificate page information.

2. Select File > New > Virtual Machine to create a new virtual machine, as shown in Figure 2.

4

Figure 2 Successfully logging in to the virtual machine server

3. Select Custom, and click Next, as shown in Figure 3.

5

Figure 3 Creating a new virtual machine

4. Enter a name for the new virtual machine in the Name field, and then click Next, as shown in Figure 4.

6

Figure 4 Naming the new virtual machine

5. Select a destination storage device for the virtual machine files, and then click Next, as shown in Figure 5.

7

Figure 5 Selecting a destination storage device for the virtual machine files

6. Select a virtual machine version, and click Next, as shown in Figure 6.

8

Figure 6 Selecting a virtual machine version

7. Select a guest operating system, select Other 2.6x Linux (64-bit) from the Version list, and then click Next, as shown in Figure 7.

9

Figure 7 Specifying the guest operating system for the virtual machine

8. Configure the total virtual CPU number by selecting the socket number and the virtual CPU number per socket, and then click Next, as shown in Figure 8. For the total virtual CPU number required, see Table 1. To configure multiple virtual CPUs, determine the number of CPUs per socket and the socket number as required. For example, to configure four virtual CPUs, set the socket number to 2 and the per-socket CPU number to 2, or the socket number to 4 and the per-socket CPU number to 1.

10

Figure 8 Selecting the number of virtual CPUs for the virtual machine

9. Configure the memory size for the virtual machine, which must be equal to or greater than the value specified in Table 1. In Figure 9, the memory size is set to 1024 MB (1 GB). Click Next.

11

Figure 9 Configuring the memory size for the virtual machine

10. Assign the specified number of NICs to the virtual machine, which must be equal to or greater than the value specified in Table 1. In this example, two NICs are configured. Click Next, as shown in Figure 10.

12

Figure 10 Specifying the number of NICs assigned to a virtual machine

11. Select a SCSI controller type, and then click Next, as shown in Figure 11.

13

Figure 11 Specifying the SCSI controller type

12. Select the type of the disk to use, and then click Next, as shown in Figure 12.

14

Figure 12 Selecting the type of the disk to use

13. Specify the virtual disk size and the disk provisioning policy. The disk size must be equal to or greater than the value specified in Table 1. In Figure 13, the disk size is set to 8 GB. Click OK.

15

Figure 13 Specifying the virtual disk size and disk provisioning policy

14. Configure the advanced options, and then click Next, as shown in Figure 14.

16

Figure 14 Configuring other advanced options

15. Click Finish to complete creating the virtual machine, as shown in Figure 15. When the virtual machine is successfully created, it is added to the navigation tree on the left side of the page.

17

Figure 15 Completing creating the virtual machine

Editing the boot options of the virtual machine to configure it to boot from CD-ROM 1. Select the newly created virtual machine from the navigation tree, and select Edit from the

right-click menu. Click the Options tab. Select the box in the Force BIOS Setup area, and then click OK, as shown in Figure 16.

18

Figure 16 Selecting Force BIOS Setup

2. Select the newly created virtual machine from the navigation tree, and click to start the virtual machine. The page in Figure 17 appears. In the Console tab, select the Boot tab, configure the virtual machine to preferentially boot from the CD-ROM drive, save the configuration, and exit.

19

Figure 17 Configuring the virtual machine to preferentially boot from the CD-ROM drive

Connecting the CD drive of the virtual machine to the ISO image of the VSR and restarting the virtual machine

Click to connect the CD drive of the virtual machine to the ISO image of the VSR and restart the virtual machine, as shown in Figure 18.

Figure 18 Connecting the CD drive of the virtual machine to the ISO image of the VSR

20

Booting the virtual machine from the ISO image and entering the installation interface 1. Select an installation type. The system will automatically install the ISO image, as shown

in Figure 19.

Figure 19 Selecting an installation type

2. Enter 1, and then enter yes, as shown in Figure 20. After the installation is finished, disconnect the CD drive as shown in Figure 21 and Figure 22. Then, enter yes to reboot the system and complete installing the VSR, as shown in Figure 20.

Figure 20 Completing the VSR installation

21

Figure 21 Disconnecting the CD drive 1

Figure 22 Disconnecting the CD drive 2

Installing the VSR through the OVA template The OVA template is created based on virtual machine version 8, which requires a host that runs VMware ESXi 5.0 or later.

Connecting to the VMware platform through the VMware vSphere Client For information about connecting to the VMware platform through the VMware vSphere Client, see step 1 of "Installing the VSR through the ISO image."

Installing the VSR 1. Select File > Deploy OVA Template. 2. Enter the OVA template path in the Deploy from a file or URL field, and then click Next, as

shown in Figure 23.

22

Figure 23 Selecting the OVA template path

3. Verify the OVA template details, and then click Next, as shown in Figure 24.

23

Figure 24 Verifying OVA template details

4. Enter a name for the new virtual machine in the Name field, and then click Next, as shown in Figure 25.

24

Figure 25 Naming the new virtual machine

5. Configure the storage format for the virtual disk by using the default settings, and then click Next, as shown in Figure 26.

25

Figure 26 Configuring the storage format for the virtual disk

6. Click Finish to complete creating the virtual machine, as shown in Figure 27.

26

Figure 27 Completing creating the virtual machine

The page in Figure 28 appears. When the virtual machine is successfully created, it is added to the navigation tree on the left side of the page.

Figure 28 Successfully creating a virtual machine

Installing a VSR through the OVA template by using the automatic deployment tool

This installation method uses the automatic deployment tool vd_deploy.sh to deploy the OVA template to the specified server under vCenter management and performs basic configurations on the VSR.

27

NOTE: • The automatic deployment tool vd_deploy.sh is available for the Linux operating system where

ovftool 3.01 or later is installed. • You can download the ovftool from www.vmware.com. • To get the username and password for logging in to the vCenter server, contact the administrator

of the server.

To install a VSR through the OVA template by using the automatic deployment tool: 1. Log in to the Linux server, as shown in Figure 29. This guides uses SSH login as an example.

Figure 29 Logging in to the Linux server

2. Access the /opt directory where the OVA template resides, as shown in Figure 30.

Figure 30 Accessing the /opt directory

28

3. Use the automatic deployment tool vd_deploy.sh to configure parameters for the OVA template. Skip this step if you are using the default settings. # Use the OVA template VSR1000_HPE-CMW710-D0292-X64.ova in the directory to create a new OVA template with the following parameter settings, and save the file in the directory /opt/results.

Number of CPUs—4. Memory size—2048 MB. Number of NICs —2.

[root@compileserver3-j01-3 opt]# ./vd_deploy.sh -s VSR1000_HPE-CMW710-D0292-X64.ova -o /opt/results -c 4 -m 2048 -ns 2

Generating OVF file with user params

------------------------------------

/usr/bin/ovftool found...

Validating OVF descriptor

----------------

Generating Manifest

---------------------

Creating OVA package

--------------------

Copying OVA package to output directory

--------------------

'/opt/results/VSR1000_HPE-CMW710-D0292-X64.ova'

Success

[root@compileserver3-j01-3 opt]#

4. Use the automatic deployment tool vd_deploy.sh to install the VSR through the OVA template and perform basic configurations on the VSR. The following parameter settings are used as examples. For more information about the parameters, see Table 3. [root@compileserver3-j01-3 opt]# ./vd_deploy.sh -s VSR1000_HPE-CMW710-D0292-X64.ova -n vsr -po -ov -d '172.31.11.124/DC-DEVP/host/172.31.2.219' -u administrator -pw P@ssw0rd -ds dstest1 -nw 'VM Network' -ip '172.31.2.222/24' -gw '172.31.2.254' -lu 'vsr-user' -lpw '123456' -ssh

/usr/bin/ovftool found...

Generating OVF file with user params

------------------------------------

Validating OVF descriptor

----------------

Generating Manifest

---------------------

Creating OVA package

29

--------------------

Deploying OVA package to '172.31.11.124/DC-DEVP/host/172.31.2.219'

------------------------------------------

/usr/bin/ovftool --powerOffTarget --diskMode=thick --datastore=dstest1 --overwrite --powerOn --name=vsr vsr.ova vi://administrator:********@172.31.11.124/DC-DEVP/host/172.31.2.219

Opening OVA source: vsr.ova

The manifest validates

Opening VI target: vi://administrator@172.31.11.124:443/DC-DEVP/host/172.31.2.219

Powering off VM: vsr

Deleting VM: vsr

Deploying to VI: vi://administrator@172.31.11.124:443/DC-DEVP/host/172.31.2.219

Transfer Completed

Powering on VM: vsr

Completed successfully

Success

After the deployment is complete, a VSR named vsr is installed on the server 172.31.2.219, as shown in Figure 31.

Figure 31 Successfully installing a VSR

Table 3 Configuration options

Configuration options Format Description

Virtual device configuration options

-sn | -sysname <string> Sysname, a string of 1 to 64 characters.

-ip | -ip_address <address/mask>IPv4 address/mask for the first interface, such as 10.1.1.100, 255.255.255.0, or 10.1.1.100/24. You can also specify the string "dhcp" to use DHCP.

30

Configuration options Format Description

-gw | -gateway <address> Default IPv4 gateway, such as 1.1.1.1.

-lu | -login_username <string> Login username, a string of 1 to 55 characters, excluding \ | / : * ?< > @, and must not be a, al, or all. It must be used with the login_password.

-lpw | -login_password <string> Login password, a string of 1 to 63 characters. It must be used with the login_username.

-ssh N/A Enables SSH. This requires the login username and password.

-telnet N/A Enables Telnet. This requires the login username and password.

-netconf_http N/A Enables NETCONF over HTTP. This requires the login username and password.

-netconf_https N/A Enables NETCONF over HTTPS. This requires the login username and password.

-snmpv2 N/A Enables SNMPv2. This requires the read_community and write_community.

-rc | -read_community <string> SNMPv2 read-only access community name, a string of 1 to 32 characters.

-wc | -write_community <string> SNMPv2 read and write access community name, a string of 1 to 32 characters.

Help

-h | -help N/A Displays help information and exits.

Input/Output options

-s | -sourcefile <file> OVA file used to deploy the virtual device.

-o | -output <directory> Destination output directory of the customized OVA file. If you do not specify the output directory, the file will be deleted after deployed.

-n | -name <string> Name of the VM to be deployed. If you do not specify the name, the source OVA filename will be used.

Virtual machine hardware options

-c | -cpus <number> Number of vCPUs.

-m | -memory <MB> Memory size. The minimum size of the memory is 1024 MB.

-ns | -nics <number> Number of vNICs.

-nt | -nic_type <string> vNIC type. The value is E1000 VMXNET3.

-nw | -network <string> Network label for all vNICs, or a comma-separated list of network labels (one network label per vNIC.) The network label must exist on the ESXi host.

31

Configuration options Format Description

ESXi/vSphere deploy options

-d | -deploy <URL> Deploys the OVA to the specified ESXi host.

-u | -username <string> ESXi login username.

-pw | -password <string> ESXi login password.

-ds | -datastore <string> Name of the database where the OVA will be deployed. The database must exist on the ESXi host.

-ov | -overwrite N/A Overwrites an existing VM with the same name.

-po | -poweron N/A Powers on the VM.

NOTE: There is no required sequence for configuration options.

Installing the VSR on the KVM platform You can install the HPE VSR1000 virtual router on the KVM platform only by using the ISO image.

Installing the VSR through the ISO image Creating a new virtual machine on the KVM virtual platform

1. Run the virtual machine manager software.

2. Click to start creating a new virtual machine on the page that appears, as shown in Figure 32.

32

Figure 32 Virtual machine manager management page

NOTE: The virtual machine manager is a GUI-based optional management software for the Linux operating system. When you install the Linux operating system on the host, enable the GUI mode and install the virtual machine manager.

3. Enter a name for the new virtual machine in the Name field, select Local install media (ISO image and CDROM), and then click Forward, as shown in Figure 33.

33

Figure 33 Creating a new virtual machine

4. Select the ISO image and click Forward, as shown in Figure 34.

34

Figure 34 Selecting an ISO image

5. Select the memory size for the virtual machine, which must be equal to or greater than the value specified in Table 1. Select the number of virtual CPUs for the virtual machine according to Table 1. In Figure 35, the memory size and the number of virtual CPUs are set to 1024 MB (1 GB) and 1, respectively. Click Forward.

35

Figure 35 Selecting the memory size and the number of virtual CPUs

6. Specify the virtual disk size, which must be equal to or greater than the value specified in Table 1, and then click Forward. In Figure 36, the disk size is set to 8 GB.

36

Figure 36 Specifying the virtual disk size

7. Configure other advanced options, select Customize configuration before install, and then click Finish, as shown in Figure 37. If you do not select Customize configuration before install, the virtual machine is created with the basic configuration, and the number of the virtual cards cannot meet the requirements in Table 1. HPE recommends that you select this option.

37

Figure 37 Configuring other advanced options

If you select Customize configuration before install, the page for customizing the configuration appears when the basic configuration finishes, as shown in Figure 38.

38

Figure 38 Customizing the configuration

8. Select Disk 1 from the navigation tree on the left, and then specify the Disk bus as IDE, as shown in Figure 39.

39

Figure 39 Specifying the disk bus

9. Select NIC from the navigation tree on the left side of the page, then and configure the virtual NIC, as shown in Figure 40.

40

Figure 40 Configuring the virtual network interface

Only one virtual NIC is configured on the virtual machine. To make sure the VSR runs correctly, the number of the virtual NICs must be equal to or greater than the value specified in Table 1.

10. Click Add Hardware in the bottom left corner of the page to add virtual NICs, as shown in Figure 40.

11. Select Device model, configure the virtual NIC, and then click Finish, as shown in Figure 41.

41

Figure 41 Adding hardware

12. Click to finish creating the virtual machine. The new virtual machine begins booting up and the VSR installation process starts.

Booting the virtual machine from the ISO image and entering the installation interface 1. Select an installation type, as shown in Figure 42. The system automatically installs the ISO

image.

42

Figure 42 Installing the ISO image

2. Enter 1 to install the VSR, enter yes to confirm the installation, and then enter yes to reboot the system and complete installing the VSR, as shown in Figure 43.

43

Figure 43 Completing the VSR installation

Deployment instructions Mapping VSR network interfaces to virtual NICs

IMPORTANT: Before you configure a VSR network interface, verify the mappings between virtual NICs and the VSR slots to ensure that the configuration on the VSR network interface applies to the correct virtualNIC.

When the VSR starts up for the first time, it scans PCI devices to identify supported virtual NICs. After a virtual NIC is identified, the VSR initializes the virtual NIC, records its MAC address, and maps it to the corresponding slot according to the order the MAC address is identified. If all slots are mapped to the MAC addresses of the virtual NICs, no additional MAC addresses are added.

44

Figure 44 Mappings between VSR network interfaces and virtual NICs

After the VSR starts up, use the display interface gigabitethernet brief command to display the quantity and slots of virtual interfaces. <Sysname> display interface gigabitethernet brief

Brief information on interface(s) under route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Main IP Description

GE1/0 UP UP --

GE2/0 UP UP 172.16.0.112

GE3/0 UP UP --

If you do not delete or add any virtual NICs, the mappings between virtual NICs and the VSR slots survive a VSR reboot.

Adding or deleting VSR network interfaces

CAUTION: When the VSR is running, you cannot add or delete virtual NICs. Before you add or delete virtual NICs, stop the VSR.

You can add or delete Ethernet interfaces on the VSR by adding or deleting virtual NICs on the VM. • After you delete a virtual NIC and start up the VSR, the slot mapped to the deleted virtual NIC is

also deleted. The mappings between other slots and virtual NICs do not change. • After you add a virtual NIC and start up the VSR, the newly added virtual NIC is mapped to a

slot that has the smallest slot number among unmapped slots.

For information about how to add or delete virtual NICs, see related VMware documents.

Use the display interface GigabitEthernet command to display the virtual interface quantity and virtual interface slots before and after you add or delete virtual NICs. <Sysname> display interface gigabitethernet brief

Brief information on interface(s) under route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Main IP Description

45

GE1/0 UP UP --

GE2/0 UP UP 172.16.0.112

GE3/0 UP UP --

After you add or delete a virtual NIC, verify the virtual interface quantity and virtual interface slots before performing any network configurations. The following example shows the quantity and slots of virtual interfaces after you add a virtual NIC. <Sysname> display interface gigabitethernet brief

Brief information on interface(s) under route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Main IP Description

GE1/0 UP UP --

GE2/0 UP UP 172.16.0.112

GE3/0 UP UP --

GE4/0 UP UP --

The output shows that the newly added virtual NIC is mapped to GigabitEthernet 4/0 on the VSR.

Mapping VSR interfaces to vSwitch interfaces Mappings on the VMware platform

You can configure the ESXi network interfaces differently to work with the VSR. The following examples illustrate common mappings between VSR interfaces and vSwitch interfaces. • As shown in Figure 45, each VSR interface is mapped to an individual physical port on the host.

Figure 45 Mapping each VSR interface to an individual physical port

• As shown in Figure 46, multiple VSR interfaces are mapped to one physical port on the host.

46

Figure 46 Mapping multiple VSR interfaces to one physical port

• As shown in Figure 47, the VSR interface is mapped to the trunk port on the vSwitch and can receive packets with any type of VLAN tag.

Figure 47 Mapping the VSR interface to the trunk port

Mappings on the KVM platform

IMPORTANT: • You can only use the bridge method to map the VSR interfaces to the physical ports of the

host. VLAN subinterfaces cannot be created on the mapped interface on the host. • To map the Virtio virtual NIC to a trunk port, the KVM virtual platform must support VHost.

You can configure the KVM network interfaces differently to work with the VSR. The following examples illustrate common mappings between VSR interfaces and vSwitch interfaces. • As shown in Figure 48, each VSR interface is mapped to a physical port on the host.

You can use the bridge or macvtap method to map the VSR interfaces to the physical ports of the host.

47

Figure 48 Mapping each VSR interface to an individual physical port

• As shown in Figure 49, multiple VSR interfaces are mapped to one physical port on the host. You can use the bridge or macvtap method to map the VSR interfaces to the physical ports of the host.

Figure 49 Mapping VSR interfaces to one physical port

• As shown in Figure 50, the VSR interface is mapped to the trunk port of the vSwitch and bound to one physical port on the host. The VSR interface can receive packets with any VLAN tags.

48

Figure 50 Mapping the VSR interface to the trunk port

49

Upgrading and recovering the VSR

Upgrading the VSR Upgrading the VSR at the CLI

1. At the CLI of the VSR, use FTP or TFTP to download the VSR IPE image of the latest version. For information about FTP and TFTP, see HPE VSR1000 Virtual Services Router Fundamentals Configuration Guide.

2. Configure the VSR IPE image as the new startup system software image. In the user view of the VSR CLI, execute the boot-loader file ipe-filename { backup | main } command. Then, the system automatically extracts all software packages in the IPE image and configures the IPE image as the startup system software image.

3. Save the configuration and restart the system to complete upgrading the software. Use the save command to save the current configurations and then use the reboot command to restart the VSR to complete upgrading the VSR. For information about the upgrade procedure, see HPE VSR1000 Virtual Services Router Fundamentals Configuration Guide.

Upgrading the VSR through the ISO image 1. Create and configure the VSR. For more information, see pre-booting steps in "Installing the

VSR on the VMware platform" or "Installing the VSR on the KVM platform." 2. After the installation interface appears, as shown in Figure 51, enter 2 to select Upgrade Install

to upgrade the VSR to the version in the ISO image.

Figure 51 Upgrading the VSR through an ISO image

3. After the installation is finished, disconnect the CD drive, as shown in Figure 21, and then reboot the system.

Recovering the VSR through the ISO image 1. Create and configure the VSR. For more information, see pre-booting steps in "Installing the

VSR on the VMware platform" or "Installing the VSR on the KVM platform." 2. After the installation interface appears, as shown in Figure 52, enter 3 to select Recovery

Install to recover the VSR to the version in the ISO image.

50

Figure 52 Recovering the VSR through an ISO image

3. After the installation is finished, disconnect the CD drive, as shown in Figure 21, and then reboot the system.

51

Registering the software IMPORTANT:

To get full performance and functionality, purchase and register a license.

The VSR software requires a license to enable full performance and functionality of the product. The license is locked and can only be installed on one device at a time.

NOTE: • The software is available for evaluation via download

at http://www.hpe.com/networking/software. While the basic evaluation software contains all the features and functionality, it has limited performance that can be used for evaluation purposes. A 90-day evaluation license is available and will enhance the limited performance of the downloaded software.

• To ensure correct router operation, restart the HPE VSR1000 after the license key file is installed, uninstalled, deleted, recovered, or updated.

To register and activate a license: 1. Download and install VSR software on your Virtual Machine. 2. Register the purchased license or request a 90 day evaluation on HPE MyNetworking Portal.

For more information, see "Registering the license." 3. Install the license key file on the VSR and reboot the VSR. For more information, see "Installing

the license key file."

Registering the license Log in to the HPE MyNetworking portal at http://hpe.com/networking/mynetworking/ and select Register license.

Requesting a 90-day evaluation license 1. Select one of the VSR evaluation licenses from the pull-down list in the Evaluation/No-charge

Licenses section, as shown in Figure 53.

Figure 53 Requesting a trial license

2. Click Next. The Upload Device ID file screen will display.

52

Registering a purchased license 1. Enter the HPE Sales Order number in the Order number or Registration ID field, and then

click Next, as shown in Figure 54.

Figure 54 Entering the HPE Sales Order Number

2. Enter an email address that is associated with the order number in the Email field, and then click Next, as shown in Figure 55.

Figure 55 Entering the email address

3. Select the license you want to register and click Next, as shown in Figure 56.

53

Figure 56 Selecting a license

Uploading the device ID file Obtaining the device ID file

1. Execute the display license device-id command on the VSR to locate the device ID file. <HPE>display license device-id

SN: 000c29240005057013091003

Device ID: flash:/license/000c29240005057013091003.did

2. Upload the Device ID file (SN.did) from the VSR to the PC by a TFTP or FTP service.

IMPORTANT: To use FTP to transfer the SN.did file, use the binary command to set the transmission mode to binary first. To use TFTP to transfer the file, use the mode binary command to set the transmission mode to binary first. If you transfer the file in ASCII mode, the file cannot be used correctly.

This document uses TFTP as an example. a. Launch a TFTP server on the PC. b. Upload the device ID file from the VSR to the PC.

tftp <ip address of TFTP server> put path/SN.did SN.did

NOTE: The path and file names are generic.

Uploading the device ID file 1. Click Browse in the Upload Device ID field to navigate to your saved device ID file, click

Upload, and then click Next, as shown in Figure 57. The device serial number is extracted from the Device ID file when it is validated by MyNetworking. If the file is valid, the serial number is auto-populated to the Device-ID Serial Number field.

54

Figure 57 Uploading the device ID file

2. Select I accept all of the above terms, and then click Finish, as shown in Figure 58.

Figure 58 License agreement

The confirmation page appears, as shown in Figure 59. The license key file will be generated in a few minutes and emailed to you.

55

Figure 59 Confirmation page

Installing the license key file While the license key file is being processed the license will remain in Pending status, as shown in Figure 60.

Figure 60 Pending status

After the license key file is generated and posted in MyNetworking, the license status changes to Active, as shown in Figure 61.

56

Figure 61 Active status

Obtaining the license key file Use either method to obtain the license key file: • Use the license key file that is attached in the registration confirmation email. • Download the license key file from the View licenses page, as shown in Figure 62.

Figure 62 View licenses page

Installing the license key file

IMPORTANT: To make the new license take effect, restart the HPE VSR1000 virtual router after the license key file has been installed.

1. On the PC, transfer the license key file (xxx.ak) to the VSR by TFTP or FTP.

57

2. On the VSR, execute the following command to install the license key file. The “flash:/xxx.ak” portion is the location of your license key file. [HPE]license activation-file install flash:/xxx.ak

3. Restart the VSR.

58

Appendix A Installing the KVM platform

KVM overview You can create a new virtual device and install an HPE VSR1000 router after you install the KVM platform. For more information about installing a VSR on the KVM platform, see "Installing the VSR on the KVM platform."

Installing the KVM platform IMPORTANT:

Make sure you install the KVM platform on a PC or server that supports hardware virtualization technologies, such as Intel VT and AMD V.

You can install the KVM platform through the installation CD-ROM or the network. • To start the CD-ROM installation, power on the device, insert the CentOS 6.3 installation

CD-ROM, and select to boot from the CD-ROM. • To start the network installation, prepare a network that provides the CentOS 6.3 installation

files, power on the device, and choose to boot from the network.

This section describes CentOS 6.3 installation through web page. 1. Enter the Welcome page, as shown in Figure 63.

Figure 63 Welcome page

2. Press Enter or wait for 59 seconds for the disk test page to appear, as shown in Figure 64.

59

Figure 64 Disk test page

3. Click OK on the disk test page to verify the CentOS 6.3 installation file on the disk, or click Skip to skip the test if the files are intact.

4. Click Next on the CentOS 6.3 installation page, as shown in Figure 65.

Figure 65 CentOS 6.3 installation page

5. Select installation language and click Next, as shown in Figure 66.

60

Figure 66 Selecting installation language

6. Select the keyboard type and click Next, as shown in Figure 67.

Figure 67 Selecting the keyboard type

7. Select the storage device type and click Next, as shown in Figure 68.

61

Figure 68 Selecting the storage device type

8. Choose to discard or keep data on the storage device and click Next, as shown in Figure 69.

Figure 69 Storage device warning page

9. Specify a name for the host and click Configure Network, as shown in Figure 70.

Figure 70 Naming the host

10. Add a network interface, or select a network interface and click Edit, as shown in Figure 71.

62

Figure 71 Adding a network interface

11. Configure IPv4 address and IPv6 address obtaining methods and click Apply, as shown in Figure 72.

Figure 72 Editing a network interface

63

12. Click Close on the Network Connections page, as shown in Figure 71. 13. Click Next on the host name configuration page, as shown in Figure 70. 14. Select your time zone and click Next, as shown in Figure 73.

Figure 73 Selecting your time zone

15. Configure the Linux root account password. If the Weak Password dialog box appears, click Cancel to change the password or click Use Anyway to use the password. Click Next on the password configuration page, as shown in Figure 74.

Figure 74 Configuring a password

64

16. Back up useful data on the storage disk before you remove them. Select Use All Space to replace all data on the storage disk or select Replace Existing Linux System(s) to replace only data in the Linux partition, and click Next, as shown in Figure 75.

Figure 75 Selecting the installation type

17. Click Write changes to disk on the prompted page and click Next, as shown in Figure 76.

Figure 76 Writing storage configuration to disk

18. Select Desktop and Customize now, and click Next, as shown in Figure 77.

65

Figure 77 Selecting the software

19. Click Virtualization, select Virtualization, Virtualization Client, Virtualization Platform, and Virtualization Tools, and click Next, as shown in Figure 78.

Figure 78 Selecting virtualization components

66

20. Verify that the installation is complete based on the installation progress page, as shown in Figure 79.

Figure 79 Installation progress page

21. Click Reboot on the installation completing page, as shown in Figure 80.

Figure 80 Installation completing page

22. Click Forward on the Welcome page, as shown in Figure 81.

67

Figure 81 Welcome page

23. Select Yes, I agree to the License Agreement and click Forward, as shown in Figure 82.

Figure 82 License information page

24. Configure the Linux non-administrative account name and password, and click Forward, as shown in Figure 83.

68

Figure 83 Creating a user

25. Configure the date and time and click Forward, as shown in Figure 84.

Figure 84 Setting the date and time

26. Use the default Kdump memory configuration and click Finish, as shown in Figure 85.

69

Figure 85 Setting the Kdump memory

27. Use the root account to log in to the system after the system is rebooted. 28. Select Applications > System Tools > Virtual Machine Manager, as shown in Figure 86.

The Virtual Machine Manager is started, as shown in Figure 87.

Figure 86 Starting the virtual machine manager

70

Figure 87 Virtual machine manager page

71

Appendix B Configuring the Intel 82599 VF NIC

Intel 82599 VF NIC overview The Intel 82599 NIC supports SR-IOV, which allows hardware-based NIC virtualization with the use of virtual function (VF). Each virtual NIC is a VF NIC, and can be added to a VM as a PCI device. VF NICs ensure higher performance than software-based virtual NICs.

VF NICs need to be configured on the BIOS server and the virtual platform (VMware or KVM) that support VT-d or SR-IOV.

Configuring the BIOS server This section uses HP 360Gen8 as an example.

To configure the BIOS server: 1. Log in to the BIOS server, and select System Options > Processor Options > Intel (R)

Virtualization Technology to enable CPU virtualization, as shown in Figure 88.

Figure 88 Enabling CPU virtualization

2. Select System Options > Processor Options > Intel (R) VT-d to enable CPU VT-d, as shown in Figure 89.

72

Figure 89 Enabling CPU VT-d

3. Select Advanced Options > SR-IOV to enable SR-IOV, as shown in Figure 90.

Figure 90 Enabling SR-IOV

Configuring the virtual platform Configuring Intel 82599 VF NICs on the VMware platform

This section uses HP 360Gen8 and VMware ESXI 5.1 as an example.

To configure Intel 82599 VF NICs on the VMware platform: 1. Make sure you have configured the BIOS server. For more information, see "Configuring the

BIOS server." 2. Start VMware ESXI 5.1 and enable ESXI Shell. For more information about ESXI Shell

configuration, see related VMware documents.

73

3. Log in to the server through ESXI Shell. 4. View information about the Intel 82599 NIC. The command output varies with NIC numbers, as

shown in Figure 91 and Figure 92. ~ # lspci | grep -i intel | grep -i 'ethernet\|network'

Figure 91 One Intel 82599 NIC, providing a total of two physical ports

Figure 92 Two Intel 82599 NICs, providing a total of four physical ports

5. Configure the VF NICs. ~ # esxcfg-module ixgbe -s max_vfs=X,Y

Use the option max_vfs to specify the number of VF NICs for each physical port. Assign the value for each port in the port display order after you execute the lspci | grep –i intel | grep -i 'ethernet\|network' command. For example, there are two Intel 82599 NICs, providing a total of four physical ports, and the ports are displayed as shown in Figure 92. If you use max_vfs=0,10,0,10, the system does not create VF NICs for vmnic0 and vmnic6, but creates 10 VF NICs for vmnic1 and vmnic7.

6. Verify the Intel 82599 NIC configuration and restart the server. ~ # esxcfg-module -g ixgbe

If the displayed values of max_vfs are the same as the values configured in step 5, the configuration succeeds, and you can restart the server.

7. Log in to the server through the VMware vSphere Client, and select Configuration > Advanced settings to verify the VF NIC configuration, as shown in Figure 93.

Figure 93 Successful VF NIC configuration

74

8. Log in to the server through the VMware vSphere Client, choose the VSR, select Edit virtual machine settings, click Add, select PCI Device, and click Next, as shown in Figure 94.

Figure 94 Adding the PCI device for the virtual machine

9. Choose the VF NIC to be added and click Next, and then click Finish, as shown in Figure 95.

Figure 95 Adding the VF NIC for the virtual machine

75

10. Click OK to save the configuration, as shown in Figure 96.

Figure 96 Saving the configuration

11. Start the VSR and use the display version command to verify the VF NIC configuration. The command output shown in Figure 97 indicates that the VF NICs are configured.

Figure 97 Output from the display version command

76

Configuring Intel 82599 VF NICs on the KVM platform This section uses HP 360Gen8 and VMware Fedora 17 as an example. You can use the same method to configure VF NICs for the CentOS system.

To configure Intel 82599 VF NICs on the KVM platform: 1. Log in to the server as a root user. 2. Log in to the virtual platform and view information about the Intel 82599 NIC. The command

output varies with NIC numbers, as shown in Figure 98 and Figure 99. ~ # lspci | grep -i intel | grep -i 'ethernet\|network'

Figure 98 One Intel 82599 NIC, providing a total of two physical ports

Figure 99 Two Intel 82599 NICs, providing a total of four physical ports

3. Add the content in the red circle to /boot/grub2/grub.cfg to enable the IOMMU on the core, as shown in Figure 100. By default, the IOMMU on the core is disabled for the Fedora17 system.

Figure 100 Changing the startup options on the core

4. Create an ixgbe.conf file in /etc/modprobe.d to configure the VF NICs. Use the max_vfs option to specify the number of VF NICs for each physical port. The default VF NIC driver supports only max_vfs=X. You can only configure the same number of VF NICs for all ports. The VF NIC driver of a later version, for example, driver 3.15.1, enables you to configure different numbers of VF NICs for ports. Assign the value for each port in the port display order after you execute the lspci | grep –i intel | grep -i 'ethernet\|network' command.

77

For example, there are two Intel 82599 NICs, providing a total of four physical ports, and the ports are displayed, as shown in Figure 92. If you use max_vfs=0,10,0,10, the system does not create VF NICs for vmnic0 and vmnic6, but creates 10 VF NICs for vmnic1 and vmnic7.

Figure 101 /etc/modprobe.d/ixgbe.conf file

5. Add the ixgbevf driver to the blacklist to disable the Fedora17 from loading the VF NIC driver, as shown in Figure 102.

Figure 102 /etc/modprobe.d/ixgbe.conf file

6. Configure MAC addresses for VF NICs. a. Create an rc.local file in /etc/rc.d/.

By default, no rc.local file exists in the Fedora17 system. b. Make the rc.local file executable.

chmod +x rc.local

c. Save the MAC address configuration for VF NICs in the rc.local file, as shown in Figure 103. Make sure you configure a unique MAC address for each VF NIC to ensure correct NIC operation. In Figure 103, em1 and em2 are the names of the physical ports on the Intel 82599 NIC.

78

Figure 103 /etc/rc.d/rc.local file

7. Restart the server. 8. Verify the VF NIC configuration.

lspci | grep 82599

Figure 104 Successful VF NIC configuration

9. Add VF NICs to the VSR. a. Start the Virtual Machine Manager on the Fedora17 system and select the VSR. b. Click Add Hardware, as shown in Figure 105. c. Select PCI Host Device, select the VF NIC listed on the right, and click Finish, as shown

in Figure 106.

79

Figure 105 Adding hardware

Figure 106 Adding the VF NIC

10. Start the VSR and use the display version command to verify the VF NIC configuration.

80

Figure 107 Output from the display version command

81

Document conventions and icons

Conventions This section describes the conventions used in the documentation.

Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device.

Command conventions

Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.

{ x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.

[ x | y | ... ] Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none.

{ x | y | ... } * Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one.

[ x | y | ... ] * Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none.

&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Description

Boldface Window names, button names, field names, and menu items are in Boldface. For example, the New User window appears; click OK.

> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.

Symbols

Convention Description

WARNING! An alert that calls attention to important information that if not understood or followed can result in personal injury.

CAUTION: An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.

IMPORTANT: An alert that calls attention to essential information.

NOTE: An alert that contains additional or supplementary information.

TIP: An alert that provides helpful information.

82

Network topology icons Convention Description

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

Represents an access controller, a unified wired-WLAN module, or the access controller engine on a unified wired-WLAN switch.

Represents an access point.

Represents a wireless terminator unit.

Represents a wireless terminator.

Represents a mesh access point.

Represents omnidirectional signals.

Represents directional signals.

Represents a security product, such as a firewall, UTM, multiservice security gateway, or load balancing device.

Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN, IPS, or ACG card.

TT

TT

 

 

 

 

83

Support and other resources

Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:

www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support

Center website: www.hpe.com/support/hpesc

Information to collect • Technical support registration number (if applicable) • Product name, model or version, and serial number • Operating system name and version • Firmware version • Error messages • Product-specific reports and logs • Add-on products or components • Third-party products or components

Accessing updates • Some software products provide a mechanism for accessing software updates through the

product interface. Review your product documentation to identify the recommended software update method.

• To download product updates, go to either of the following: Hewlett Packard Enterprise Support Center Get connected with updates page:

www.hpe.com/support/e-updates Software Depot website:

www.hpe.com/support/softwaredepot • To view and update your entitlements, and to link your contracts, Care Packs, and warranties

with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials

IMPORTANT: Access to some updates might require product entitlement when accessed through the HewlettPackard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.

84

Websites

Website Link Networking websites

Hewlett Packard Enterprise Information Library for Networking www.hpe.com/networking/resourcefinder

Hewlett Packard Enterprise Networking website www.hpe.com/info/networking

Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support

Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking

Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty

General websites

Hewlett Packard Enterprise Information Library www.hpe.com/info/enterprise/docs

Hewlett Packard Enterprise Support Center www.hpe.com/support/hpesc

Hewlett Packard Enterprise Support Services Central ssc.hpe.com/portal/site/ssc/

Contact Hewlett Packard Enterprise Worldwide www.hpe.com/assistance

Subscription Service/Support Alerts www.hpe.com/support/e-updates

Software Depot www.hpe.com/support/softwaredepot

Customer Self Repair (not applicable to all devices) www.hpe.com/support/selfrepair

Insight Remote Support (not applicable to all devices) www.hpe.com/info/insightremotesupport/docs

Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.

For more information about CSR, contact your local service provider or go to the CSR website:

www.hpe.com/support/selfrepair

Remote support Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.

For more information and device support details, go to the following website:

www.hpe.com/info/insightremotesupport/docs

Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,

85

part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

86

Index Numerics

90-day evaluation license requesting, 51

A

adding VSR network interfaces, 44

Appendix A (installing the KVM platform), 58 Appendix B (configuring the Intel 82599 VF NIC), 71

B

BIOS server configuration procedure, 71

C

CD-ROM editing boot options of the virtual machine, 17

CLI upgrading VSR, 49

configuring BIOS server, 71 Intel 82599 VF NIC, 71 virtual platform, 72

creating virtual machine on the KVM platform, 31 virtual machine on the VMware platform, 3

D

deleting VSR network interfaces, 44

deploying deployment instructions for the VSR, 43

device ID file obtaining, 53 uploading, 53, 53

H

hardware requirements VSR1000, 2

HPE VSR1000 installation procedure, 2

I

installation requirements VSR1000, 2

installing HPE VSR1000, 2 KVM platform, 58, 58

license key file, 55, 56 VSR, 21 VSR1000 on the KVM platform, 31 VSR1000 on the VMware platform, 3

installing through the ISO image VSR on the KVM platform, 31 VSR on the VMware platform, 3

Intel 82599 VF NIC configuration procedure, 71 overview, 71

Intel 82599 VF NICs KVM platform, 76 VMware platform, 72

ISO image booting the virtual machine and entering the installation interface, 20, 41 connecting the CD drive and restarting the virtual machine, 19 VSR recovering, 49 VSR upgrading, 49

K

KVM overview, 58

KVM platform configuring Intel 82599 VF NICs, 76 installation procedure, 58, 58 installing the VSR through the ISO image, 31 mapping, 46

L

license registering, 51

license key file installing, 55, 56 obtaining, 56

M

mapping KVM platform, 46 VMware platform, 45 VSR interfaces to vSwitch interfaces, 45 VSR network interfaces to virtual NICs, 43

O

obtaining device ID file, 53 license key file, 56

OVA template

87

installing VSR, 21 OVA template automatic deployment tool

installing VSR, 26 overview

Intel 82599 VF NIC, 71 KVM, 58

P

procedure adding or deleting VSR network interfaces, 44 booting from the ISO image and entering the installation interface, 20, 41 configuring the BIOS server, 71 configuring the Intel 82599 VF NIC, 71 configuring the virtual platform, 72 connecting the CD drive of the virtual machine to the ISO image of the VSR and restarting the virtual machine, 19 connecting to the VMware platform through the VMware vSphere Client, 21 creating a new virtual machine on the KVM virtual platform, 31 creating a new virtual machine on the VMware virtual platform, 3 editing the boot options for booting from CD-ROM, 17 installing the HPE VSR1000, 2 installing the KVM platform, 58 installing the license key file, 55, 56 installing the VMware platform, 58 installing the VSR, 21 installing the VSR on the KVM platform through the ISO image, 31 installing the VSR on the VMware platform through the ISO image, 3 installing the VSR through the OVA template, 21 installing the VSR through the OVA template by using the automatic deployment tool, 26 installing the VSR1000 on the KVM platform, 31 installing the VSR1000 on the VMware platform, 3 Intel 82599 VF NICs on the KVM platform, 76 Intel 82599 VF NICs on the VMware platform, 72 mapping VSR network interfaces to virtual NICs, 43 mapping VSR network interfaces to vSwitch interfaces, 45 obtaining the device ID file, 53 obtaining the license key file, 56

recovering the VSR through the ISO image, 49 registering a purchased license, 52 registering license, 51 registering VSR software, 51 requesting a 90-day evaluation license, 51 upgrading and recovering the VSR, 49 upgrading the VSR, 49 upgrading the VSR at the CLI, 49 upgrading the VSR through the ISO image, 49 uploading the device ID file, 53, 53

purchased license registering, 52

R

recovering VSR, 49

registering license, 51 purchased license, 52 VSR software, 51

requesting 90-day evaluation license, 51

S

software registering, 51

software requirements VSR1000, 2

U

upgrading VSR, 49, 49

uploading device ID file, 53, 53

V

virtual machine booting from the ISO image and entering the installation interface, 20, 41 connecting the CD drive of the virtual machine to the ISO image of the VSR and restarting the virtual machine, 19 editing the boot options for booting from CD-ROM, 17

virtual platform configuration procedure, 72

virtual router VSR1000, 1

VMware platform configuring Intel 82599 VF NICs, 72 creating virtual machine, 3, 31 installing the VSR through the ISO image, 3

88

mapping, 45 VMware vSphere Client

connecting to the VMware platform, 21 VSR

adding or deleting network interfaces, 44 connecting to the VMware platform through the VMware vSphere Client, 21 deployment instructions, 43 installation procedure, 21 installing the license key file, 55, 56 installing through the OVA template, 21 installing through the OVA template by using the automatic deployment tool, 26 mapping VSR network interfaces to virtual NICs, 43 mapping VSR network interfaces to vSwitch interfaces, 45 obtaining the device ID file, 53 obtaining the license key file, 56 recovering through the ISO image, 49 registering a purchased license, 52 registering license, 51 registering software, 51 requesting a 90-day evaluation license, 51 upgrading and recovering procedure, 49 upgrading at the CLI, 49 upgrading procedure, 49 upgrading through the ISO image, 49 uploading the device ID file, 53, 53

VSR for KVM platform installation procedure through the ISO image, 31

VSR1000 hardware requirements, 2 installation requirements, 2 software requirements, 2 virtual router, 1

VSR1000 for VMware platform installation procedure, 3