installation and getting started guidelinux kvm linux kvm (linux kernel > 2.6.25), the...

HP VSR1000 Virtual Services Router Installation and Getting Started Guide

Part number: 5998-4652

Document version: 6W101-20140418

5998-4652

Legal and notice information

© Copyright 2014 Hewlett-Packard Development Company, L.P.

No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice.

HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

i

Contents

VSR overview ································································································································································ 1 Overview ············································································································································································ 1 Features ·············································································································································································· 1

Preparing for installation ············································································································································· 4 Virtual machine hardware configuration requirements ································································································· 4 Software configuration requirements ······························································································································ 4 Virtual NIC specifications ················································································································································· 5

Installing a VSR on the VMware platform ·················································································································· 7 Installation guidelines ······················································································································································· 7

Installing the VSR through an ISO image (on the VMware platform) ································································· 7 Manually installing the VSR through OVA (on the VMware platform) ···························································· 25

Mapping VSR network interfaces to virtual machine network interfaces ································································· 31 Mapping VSR network interfaces to virtual NICs ······························································································ 31 Adding or deleting VSR network interfaces ········································································································ 32 Mapping VSR interfaces to vSwitch interfaces ··································································································· 33

Installing a VSR on the KVM platform ······················································································································ 36 Installation guidelines ···················································································································································· 36 Installing the VSR through an ISO image (on the KVM platform) ············································································· 36 Mapping VSR network interfaces to virtual machine network interfaces ································································· 48

Mapping VSR interfaces to vSwitch interfaces ··································································································· 48

Upgrading and recovering the VSR ·························································································································· 51 Upgrading the VSR ························································································································································ 51

Upgrading the VSR at the CLI ······························································································································ 51 Upgrading the VSR through an ISO image ········································································································ 51

Recovering the VSR through an ISO image ················································································································ 52

Registering the software ············································································································································ 53 License registration and activation procedures ··········································································································· 53 Registering licenses ························································································································································ 53 Install the license key file ··············································································································································· 58 Posted in MyNetworking ··············································································································································· 59

Appendix A Installing the KVM platform ·················································································································· 60 KVM overview ································································································································································ 60 Installing the KVM platform ··········································································································································· 60

Appendix B Configuring the Intel 82599 VF NIC ··································································································· 74 Intel 82599 VF NIC overview ······································································································································ 74 Configuring the BIOS server ········································································································································· 74 Configuring the virtual platform ···································································································································· 75

Configuring Intel 82599 VF NICs on the VMware platform ············································································ 75 Configuring Intel 82599 VF NICs on the KVM platform ·················································································· 80

Support and other resources ····································································································································· 85 Contacting HP ································································································································································ 85

Subscription service ·············································································································································· 85 Related information ························································································································································ 85

Documents ······························································································································································ 85 Websites ································································································································································· 85

ii

Conventions ···································································································································································· 86

Index ··········································································································································································· 88

1

VSR overview

Overview With the development of the virtualization technology and the cloud computing technology, more and more cloud service providers and telecommunication carriers start to provide the public cloud service and allow users to rent resources and services to create their own virtual data centers or virtual private clouds. This service helps enterprises to save the construction costs and improve the service smartness. Therefore, more and more enterprises start migrating services to the public cloud. With the fast development of application migration to the cloud, servers, and the virtualization technology, it becomes popular to provide both network functions and IP applications on one server.

To conform to the industry trend and meet the service requirements, HP launches the new-generation virtual services router (VSR). Similar to other HP physical routers, the VSR1000 virtual router uses the Comware V7 platform and runs on the virtual machine of a standard server to provide the same function and experience as physical routers. The HP VSR1000 virtual router provides routing, firewall, VPN, QoS, and configuration management functions, and helps enterprises to construct a secure, unified, scalable mixed cloud. Also, the HP VSR1000 virtual router helps simplify the branch infrastructure. The HP VSR1000 virtual router provides the following typical applications:

• As the gateway of the enterprise network in the cloud (VPC gateway), the HP VSR1000 virtual router can be deployed on the database servers to provide the VPN and security functions. In this way, the cloud-side applications can be integrated into the enterprise network for unified management, which secures the cloud-side applications and data of the enterprise.

• As the network component of the devices in a branch of an enterprise, the HP VSR1000 virtual router can be deployed on the server of an enterprise branch to provide Ethernet access, security, firewall, and QoS functions for the branch users.

Different from HP physical routers, the HP VSR1000 virtual router is a software-only router running on the virtual machine of a standard server. The HP VSR1000 virtual router is controlled by licenses. Based on a license, the HP VSR1000 virtual router can provide the corresponding functions, performance, and usage life to meet the network requirements of users.

Features Table 1 shows the features supported by the HP VSR1000 virtual router.

Table 1 Features supported by the HP VSR1000 virtual router

Item Description

Software package

• VSR1000 software (based on Comware V7) • Supports the distribution in the format of ISO, OVA, or IPE

Virtual platform • VMware ESXi • Linux KVM

License Supports control based on the virtual CPU count and time

Ethernet Layer 3 Ethernet interface or subinterface

2

Item Description

ARP

802.1Q VLAN and VLAN termination

PPPoE Client

IP routing

Static routing

Dynamic routing: RIPv1/v2, OSPFv2, BGP, and IS-IS

Multicast routing: IGMPv1/v2/v3, PIM-DM, PIM-SM, PIM-SSM, and MSDP

Routing policy

IP services

Forwarding/Fast forwarding (unicast/multicast)

TCP, UDP, IP Option, and IP unnumbered

PBR

Ping, and Tracert

DHCP Server, DHCP Relay, and DHCP Client

DNS Client, DNS Proxy, and DDNS

FTP Server, FTP Client, and TFTP Client

Telnet Server and Telnet Client

UDP helper

NTP/SNTP

IPv6

Basic Functions: IPv6 ND, IPv6 PMTU, IPv6 FIB, IPv6 ACL, and DS-Lite

IPv6 Tunnel: IPv6 over IPv4 manual tunnel, Automatic IPv4-compatible IPv6 tunnel, 6to4 tunnel, and ISATAP tunnel

Static routing

Dynamic routing: RIPng, OSPFv3, IS-ISv6, and BGP4+

Multicast routing: MLDv1/v2, IPv6 PIM-DM, IPv6 PIM-SM, and IPv6 PIM-SSM

MPLS

LDP, LSM, Static LSP, and Static CR-LSP

L3VPN

L2VPN

MPLS TE and RSVP TE

QoS

Traffic Classification: based on port, MAC address, IP address, IP priority, DSCP priority, TCP/UDP port number, and protocol type

Traffic Policing: CAR and LR

Traffic Shaping: GTS

Congestion Management: FIFO, WFQ, and CBQ

Congestion Avoidance: Tail-Drop and WRED

MPLS QoS

Security VPN: IPSec VPN

Firewall: Packet filter and ASPF

3

Item Description

Access control: ACL, AAA (Local authentication, RADIUS, HWTACACS, and LDAP), RBAC, and Portal

Others: SSH v1.5/2.0, SSL, GRE, L2TP, NAT/NAPT, URPF, session management, connection limit, password management, FIPS/CC mode, and attack detection and protection

High availability

VRRP/VRRPv3

BFD

Load balancing

Management and maintenance

User access management: console port, SSH, Telnet, and FTP

Local management: CLI, automatic configuration, and file system

Network management: SNMPv1/v2c/v3, IMC, and NETCONF

Network monitoring: SNMPv1/v2c/v3, RMON, Syslog, NQA, NetStream, and EAA

4

Preparing for installation

Virtual machine hardware configuration requirements

Table 2 shows the minimum virtual machine hardware configuration requirements.

Table 2 Virtual machine hardware configuration requirements of the HP VSR1000 virtual router

Item VSR virtual machine

Processor One vCPU (main frequency≥ 2.0 GHz)

Memory 1 GB

Hard disk One vHD, 8 GB

Network interface card Two virtual NICs at least. Up to 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 configuration requirements • Install the virtual machine platform software, for example, VMware ESXi or Linux KVM platform, on

the physical server.

• Install the virtual machine client software, for example, VMware vSphere Client, on the local PC.

Table 3 Virtual machine platform software version requirements of the HP VSR1000 virtual router

Virtual machine platform software Software versions compatible with HP VSR1000

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 • Fedora 17 • Ubuntu 12.10 • RedHat Enterprise Linux (RHEL) 6.3 • SUSE Server 11SP2

NOTE:

The virtual machine platform software versions vary with the VSR software versions. For more informationabout the software versions compatible with an HP VSR1000 virtual router, see its release notes.

5

"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 installation and configuration guides for the selected virtual machine software.

Virtual NIC specifications Choose virtual NICs based on the compatibility matrix between features and virtual NICs, as shown in Table 4 and Table 5.

Table 4 Compatibility matrix between features and virtual NICs on the Linux KVM platform

Features E1000 in Bridge mode

VirtIO in Bridge mode

E1000 in Macvtap mode

VirtIO in Macvtap mode

InteI 82599 VF

Subinterface Supported Supported Not supported Not supported Not supported

Jumbo frame Supported

1536 bytes

Supported

1536 to 16384 bytes

Supported

1536 bytes

Supported

1536 to 16384 bytes

Not supported

VRRP/VRRPv3 Supported Supported Not supported Not supported Not supported

MPLS L2VPN Supported Supported Not supported Not supported Not supported

Multicast forwarding Not supported Not supported Supported Supported Not supported

Unicast forwarding Supported Supported Supported Supported Supported


Supported Supported Supported Supported

• Supported: RIPv1, BGP, and RIPv2 broadcast

• Not supported: OSPFv2 and RIPv2 multicast, and IS-IS


Supported Supported Supported Supported Not supported

IPv6 Supported Supported Supported Supported Not supported

6

Features E1000 in Bridge mode

VirtIO in Bridge mode

E1000 in Macvtap mode

VirtIO in Macvtap mode

InteI 82599 VF

Other services, such as IP routing, IP services, MPLS, QoS, security, availability, and management and maintenance

Supported Supported Supported Supported Supported

Table 5 Compatibility matrix between features and virtual NICs on the EXSi platform

Features E1000 VMXNET3 InteI 82599 VF

Subinterface Supported Supported Not supported

Jumbo frame Supported

1536 bytes

Supported

1536 to 16384 bytes Not supported

VRRP/VRRPv3 Supported Supported Not supported

MPLS L2VPN Supported Supported Not supported

Multicast forwarding

Supported Supported Not supported

Unicast forwarding

Supported Supported Supported


Supported Supported

• Supported: RIPv1, BGP, and RIPv2 broadcast

• Not supported: OSPFv2 and RIPv2 multicast, and IS-IS


Supported Supported Not supported

IPv6 Supported Supported Not supported

Other services, such as IP routing, IP services, MPLS, QoS, security, availability, and management and maintenance

Supported Supported Supported

7

Installing a VSR on the VMware platform

Installation guidelines Install the HP VSR1000 on the VMware platform by using a virtual drive program to load an ISO image or by using an OVA template.

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

CAUTION:

The virtual machine hardware configuration must meet the requirements in Table 2.

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

Figure 1 Logging in to the virtual machine server

8

NOTE:

• To get the username and password for logging in to the VMware virtual machine server, contact theadministrator 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.

Figure 2 Successfully logging in to the virtual machine server

3. Select Custom, and click Next.

9

Figure 3 Creating a new virtual machine

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

10

Figure 4 Naming the new virtual machine

5. Select a destination storage device for the virtual machine files, and click Next.

11

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

6. Select a virtual machine version, and click Next.

12

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 click Next.

13

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.

For the total virtual CPU number required, see Table 2. To configure multiple virtual CPUs, you can select the number of CPUs per socket and the socket number in various ways. The VSR only cares about the total virtual CPU number.

14

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 2. In Figure 9, the memory size is set to 1024 MB (1 GB). Click Next.

15

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 2. In this example, two NICs are configured. Click Next.

16

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

11. Select a SCSI controller type, and click Next.

17

Figure 11 Specifying the SCSI controller type

12. Select the type of the disk to use, and click Next.

18

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 2. In Figure 13, the disk size is set to 8 GB. Click OK.

19

Figure 13 Specifying the virtual disk size and disk provisioning policy

14. Configure other advanced options, and click Next.

20

Figure 14 Configuring other advanced options

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

21

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 click OK.

22

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.

23

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.

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

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.

24

Figure 19 Installation interface

2. Enter 1, and then enter yes. 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.

Figure 20 Completing the VSR installation

25

Figure 21 Disconnecting the CD drive 1

Figure 22 Disconnecting the CD drive 2

Manually installing the VSR through OVA (on the VMware platform)

This installation method is available only on the VMware platform.

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 1.

Installing the VSR

1. Selecting File > Deploy OVA Template.

2. Enter the OVA template path in the Deploy from a file or URL field, and click Next.

26

Figure 23 Selecting the OVA template path

3. Verify the OVA template details, and click Next.

27

Figure 24 OVA template details

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

28

Figure 25 Naming the new virtual machine

5. Configure the storage format for the virtual disk (use the default settings in this section), and click Next.

29

Figure 26 Configuring the storage format for the virtual disk

6. On the page shown in Figure 27, click Finish to complete creating the virtual machine VSR.

30

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.

Figure 28 Creating a virtual machine successfully

31

Mapping VSR network interfaces to virtual machine network interfaces

Mapping VSR network interfaces to virtual NICs 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 more MAC addresses are added.

Figure 29 Mappings between VSR network interfaces and virtual NICs

After the VSR starts up, use the display interface GigabitEthernet command to display the mappings between virtual NICs and the VSR slots. <HP>display interface GigabitEthernet

GigabitEthernet1/0

Current state: UP

Line protocol state: UP

Description: GigabitEthernet1/0 Interface

Bandwidth: 1000000kbps

Maximum Transmit Unit: 1500

Internet Address is 172.31.27.47/16 Primary

IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0050-5697-13f3

……………………………………………………………………………………………..

GigabitEthernet2/0

Current state: UP





Internet protocol processing: disabled

32

IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 0050-5697-3ebe

………………………………………………………………………………………………

IMPORTANT:

Before you configure a VSR network interface, verify the mappings between virtual NICs and the VSR slotsto make sure the configurations on the VSR network interface are assigned to a correct virtual NIC.

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, the VSR network interfaces cannot be added or deleted. Before you add or delete VSR network interfaces, stop the VSR first.

When you add or delete a virtual NIC on the VMware platform, the Ethernet interface in the VSR slot that is mapped to the virtual NIC is also added or deleted.

• 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 documents about VMware.

Use the display interface GigabitEthernet command to verify the mappings between virtual NICs and the VSR slots before and after you add or delete virtual NICs.

NOTE:

Verify the mappings between virtual NICs and the VSR slots before you perform network configuration.

For example:

# Display the mappings between virtual NICs and the VSR slots before you add a virtual NIC. <HP>display interface GigabitEthernet

GigabitEthernet1/0

Current state: UP







……………………………………………………………………………………………..

GigabitEthernet2/0

Current state: UP





33



………………………………………………………………………………………………

The output shows that two virtual NICs are mapped to GigabitEthernet 1/0 and GigabitEthernet 2/0, respectively.

# Display the mappings between virtual NICs and the VSR slots after you add a virtual NIC. <HP>display interface GigabitEthernet

GigabitEthernet1/0

Current state: UP







……………………………………………………………………………………………..

GigabitEthernet2/0

Current state: UP







……………………………………………………………………………………………..

GigabitEthernet3/0

Current state: UP






IP Packet Frame Type:PKTFMT_ETHNT_2, Hardware Address: 000c-290e-7585

……………………………………………………………………………………………..

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

Mapping VSR interfaces to vSwitch interfaces 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 30, each VSR interface is mapped to an individual physical port on the host machine.

34

Figure 30 Mapping each VSR interface to an individual physical port

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

Figure 31 Mapping multiple VSR interfaces to one physical port

• As shown in Figure 32, the VSR interface GigabitEthernet 3/0 is mapped to the trunk port on the vSwitch and can receive packets with any VLAN tags.

35

Figure 32 Mapping the VSR interface to the trunk port

36

Installing a VSR on the KVM platform

Installation guidelines You can install the HP VSR1000 virtual router by using a virtual drive program to load an ISO image.

Installing the VSR by using the OVA template is not supported on the KVM platform.

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

CAUTION:

The virtual machine hardware configuration must meet the requirements in Table 2.

1. Run the virtual machine manager software.

After the software starts up, the management interface as shown in Figure 33 appears.

37

Figure 33 Virtual machine manager management interface

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 machine, enable the GUI mode and install the virtual machine manager.

2. Click to start creating a new virtual machine.

The page as shown in Figure 34 appears.

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

38

Figure 34 Creating a new virtual machine

4. Select an ISO image, and click Forward.

39

Figure 35 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 2. Select the number of virtual CPUs for the virtual machine according to Table 2. In Figure 36, the memory size and the number of virtual CPUs are set to 1024 MB (1 GB) and 1, respectively. Click Forward.

40

Figure 36 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 2, and click Forward.

In Figure 37, the disk size is set to 8 GB.

41

Figure 37 Specifying the virtual disk size

7. Configure other advanced options, select Customize configuration before install, and click Finish.

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 2. HP recommends that you select this option.

42

Figure 38 Configuring other advanced options

After you select Customize configuration before install, the page as shown in Figure 39 appears when the basic configuration finishes.

43

Figure 39 Customizing the configuration

8. Select Disk 1 from the navigation tree on the left, and specify the Disk bus as IDE.

44

Figure 40 Specifying the disk bus

9. Select NIC from the navigation tree on the left, and configure the virtual NIC.

45

Figure 41 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 2.

10. Click Add Hardware in the bottom left corner of the page to add virtual NICs.

11. On the page that appears, select Device model, configure the virtual NIC, and click Finish.

46

Figure 42 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. The system will automatically install the ISO image.

47

Figure 43 Installation interface

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.

48

Figure 44 Completing the VSR installation

Mapping VSR network interfaces to virtual machine network interfaces

For information about the mappings between the VSR network interfaces and virtual NICs, see "Mapping VSR network interfaces to virtual NICs."

For information about how to add or delete virtual NICs, see "Adding or deleting VSR network interfaces."

Mapping VSR interfaces to vSwitch interfaces 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 45, each VSR interface is mapped to a physical port on the host machine.

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

49

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 machine.

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

Figure 46 Mapping VSR interfaces to one physical port

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

50

Figure 47 Mapping the VSR interface to the trunk port

IMPORTANT:

• You can only use the bridge method to map the VSR interfaces to the physical ports of the host machine. VLAN subinterfaces cannot be created on the mapped interface on the host machine.

• To map the Virtio virtual NIC to a trunk port, the KVM virtual platform must support VHost.

51

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 HP 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 virtual machine to complete upgrading the VSR.

For information about the upgrade procedure, see HP VSR1000 Virtual Services Router Fundamentals Configuration Guide.

Upgrading the VSR through an ISO image 1. The first several steps are the same as installing the VSR through an ISO image. For more

information, see "Installing the VSR through an ISO image (on the VMware platform)" and "Installing the VSR through an ISO image (on the KVM platform)."

2. After the installation interface appears as shown in Figure 48, enter 2 to select Upgrade Install to upgrade the VSR to the version in the ISO image.

Figure 48 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.

52

Recovering the VSR through an ISO image 1. The first several steps are the same as installing the VSR through ISO. For more information, see

"Installing the VSR through an ISO image (on the VMware platform)" and "Installing the VSR through an ISO image (on the KVM platform)."

2. After the installation interface appears as shown in Figure 49, enter 3 to select Recovery Install to recover the VSR to the version in the ISO image.

Figure 49 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.

53

Registering the software

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

NOTE: How to evaluate the software before purchasing

• The software is available for evaluation via download at the HP website. While it contains all the features and functionality, it has limited performance that can be used for evaluation purposes. A 60-day evaluation license is available upon request and will enhance the limited performance of the downloaded software.

• To ensure correct router operation, restart the HP VSR 1000 after the license is installed, uninstalled,deleted, recovered, or updated.

License registration and activation procedures These are the main steps in registering and activating the license. This document details steps 3, 4, and 5.

1. Acquire License to Use (E-LTU) (Purchase or obtain a free 60-day evaluation license from the MyNetworking portal).

2. Download and install VSR1000 on Virtual Machine

3. Register License on HP MyNetworking Portal

4. Load License Key file into VSR1000

5. Reboot and begin using

Registering licenses Log in to the HP MyNetworking portal at http://hp.com/networking/mynetworking/ and select > Register license.

To request a 60-day evaluation license

To request a 60-day evaluation license, select "Virtual Services Router - 60 Day EVAL" from the pull-down menu in the "Products without Registration ID" section and click Next.

The Upload Device ID file screen will display. (Proceed to the Upload the device ID file section for further instructions.)

54

Figure 50 Requesting a trial license

To register a purchased License-to-Use

Enter the HP Sales Order number in the Order number or Registration ID field, and then click Next.

Figure 51 Entering the HP Sales Order Number

Enter an email address that is associated with the order number in the Email box, and then click Next.

Figure 52 Entering the email address

Select the license you want to register and click Next.

55

Figure 53 Selecting a licensing

Upload the device ID file

Use the Browse button to navigate to your saved device ID file and then click the Upload button.

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.

Click Next.

To obtain your Device ID, use the “display license device-id” command.

Type the command as follows to locate the Device ID: <HP>display license device-id

SN: 000c29240005057013091003

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

56

Download the Device ID file (SN.did) to a local 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.

To launch a TFTP server

1. Launch a TFTP server on your computer.

2. Download the device information file through TFTP. tftp <ip address of TFTP server> put path/SN.did SN.did

3. Install the activation file.

4. Launch a TFTP server on your computer.

5. Upload the activation file to the device through TFTP. tftp <ip address of TFTP server> get path/xxx.ak flash:/xxx.ak

NOTE:

The path and file names are generic.

Review the license terms. If you agree to the terms, select I accept all of the above. Click Finish.

Figure 54 License agreement

The confirmation page appears. The license key will be generated in a few minutes and emailed to you.

57

Figure 55 Confirmation

58

Install the license key file While the license key file is being processed the license will remain in Pending status.

After the license key file is generated and posted in MyNetworking, the license status changes to Active. You can either download the license key file from the License Details screen in MyNetworking or use the license key file that is attached in the registration confirmation email. They are the same.

59

Posted in MyNetworking

Follow these instructions to install the license key file to activate the VSR software.

1. Upload the license key file (xxx.ak) to the VSR hard-disk by a TFTP or FTP service.

2. Type the command shown below to install license file. The “flash:/xxx.ak” is the location of your uploaded license key file.

[HP]license activation-file install flash:/xxx.ak

3. Reboot.

IMPORTANT:

To get full performance and functionality, please purchase and install a valid license. To make the new license take effect, you should restart the HP VSR1000 virtual router after the license activation file has been installed.

60

Appendix A Installing the KVM platform

KVM overview The kernel-based virtual machine (KVM) is developed in the x86-based Linux system. The KVM provides full virtualization based on hardware technologies, such as Intel VT and AMD V. KVM is integrated in major Linux releases after Linux 2.6.20 and has become one of the leading virtual machine monitors.

You can create a new virtual device and install an HP VSR1000 router after you install the KVM platform. For more information about installing a VSR on the KVM platform, see "Installing a 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 choose 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.

61

Figure 56 Welcome page

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

Figure 57 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 58.

62

Figure 58 CentOS 6.3 installation page

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

Figure 59 Language configuration page

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

63

Figure 60 Keyboard configuration page

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

Figure 61 Storage device configuration page

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

64

Figure 62 Storage device warning page

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

Figure 63 Host name configuration page

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

Figure 64 Network connections page

65

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

Figure 65 Network interface configuration page

12. Click Close on the Network Connections page, as shown in Figure 64.

13. Click Next on the host name configuration page, as shown in Figure 63.

14. Select your time zone and click Next, as shown in Figure 66.

66

Figure 66 Time zone configuration page

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 67.

Figure 67 Password configuration page

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 68.

67

Figure 68 Installation type configuration page

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

Figure 69 Writing storage configuration to disk

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

68

Figure 70 Software selection page

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

Figure 71 Virtualization component list page

69

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

Figure 72 Installation progress page

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

Figure 73 Installation completing page

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

70

Figure 74 Welcome page

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

Figure 75 License information page

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

71

Figure 76 Creating a user

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

Figure 77 Date and time page

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

72

Figure 78 Kdump page

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 79.

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

Figure 79 Starting the virtual machine manager

73

Figure 80 Virtual machine manager

74

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 81.

Figure 81 Enabling CPU virtualization

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

75

Figure 82 Enabling CPU VT-d

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

Figure 83 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."

76

2. Start VMware ESXI 5.1 and enable ESXI Shell. For more information about ESXI Shell configuration, see related VMware documents.

3. Log in to the server through ESXI Shell.

4. View information about the Intel 82599 NIC. The command output varies with NIC numbers. ~ # lspci | grep -i intel | grep -i 'ethernet\|network'

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

Figure 85 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 85. 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.

77

Figure 86 VF NIC configuration succeeded

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 87.

Figure 87 Adding the PCI device for the virtual machine

9. Choose the VF NIC to be added and click Next, and then click Finish.

78

Figure 88 Adding the VF NIC for the virtual machine

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

79

Figure 89 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 90 indicates that the VF NICs are configured.

Figure 90 display version command output

80

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. ~ # 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

3. Add the content in the red circle to /boot/grub2/grub.cfg to enable the IOMMU on the core, as shown in Figure 93.

The IOMMU on the core is disabled for the Fedora17 system by default.

Figure 93 Changing the startup options on the core

4. Create an ixgbe.conf file in /etc/modprobe.d to configure the VF NICs.

Use the option max_vfs 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.

81

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.

For example, there are two Intel 82599 NICs, providing a total of four physical ports, and the ports are displayed as shown in Figure 85. 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 94 /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 95.

Figure 95 /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 96.

Make sure you configure a unique MAC address for each VF NIC to ensure correct NIC operation. In Figure 96, em1 and em2 are the names of the physical ports on the Intel 82599 NIC.

82

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

7. Restart the server.

8. Verify the VF NIC configuration. lspci | grep 82599

Figure 97 VF NIC configuration succeeds

9. Add VF NICs to the VSR.

a. Start the Virtual Machine Manager on the Fedora17 system and choose the VSR.

b. Click Add Hardware, as shown in Figure 98.

c. Select PCI Host Device, select the VF NIC listed on the right, and click Finish, as shown in Figure 99.

83

Figure 98 Adding hardware

Figure 99 Adding the VF NIC

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

84

Figure 100 display version command output

85

Support and other resources

Contacting HP For worldwide technical support information, see the HP support website:

http://www.hp.com/support

Before contacting HP, collect the following information:

• Product model names and numbers

• Technical support registration number (if applicable)

• Product serial numbers

• Error messages

• Operating system type and revision level

• Detailed questions

Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website:

http://www.hp.com/go/wwalerts

After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.

Related information

Documents To find related documents, browse to the Manuals page of the HP Business Support Center website:

http://www.hp.com/support/manuals

• For related documentation, navigate to the Networking section, and select a networking category.

• For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.

Websites • HP.com http://www.hp.com

• HP Networking http://www.hp.com/go/networking

• HP manuals http://www.hp.com/support/manuals

• HP download drivers and software http://www.hp.com/support/downloads

• HP software depot http://www.software.hp.com

• HP Education http://www.hp.com/learn

http://www.hp.com/support�

http://www.hp.com/go/wwalerts�

http://www.hp.com/support/manuals�

http://www.hp.com/�

http://www.hp.com/go/networking�

http://www.hp.com/support/manuals�

http://www.hp.com/support/downloads�

http://www.software.hp.com/�

http://www.hp.com/learn�

86

Conventions This section describes the conventions used in this documentation set.

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


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

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

Symbols


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.

87

Network topology icons

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 switching engine on a unified wired-WLAN switch.

Represents an access point.

Represents a security product, such as a firewall, a UTM, or a load-balancing or security card that is installed in a device.

Represents a security card, such as a firewall card, a load-balancing card, or a NetStream card.

Port numbering in examples

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

88

Index

C F I K L M O P R S U V C

Configuring the BIOS server,74 Configuring the virtual platform,75 Contacting HP,85 Conventions,86

F

Features,1

I

Install the license key file,58 Installation guidelines,7 Installation guidelines,36 Installing the KVM platform,60 Installing the VSR through an ISO image (on the KVM platform),36 Intel 82599 VF NIC overview,74

K

KVM overview,60

L

License registration and activation procedures,53

M

Mapping VSR network interfaces to virtual machine network interfaces,31 Mapping VSR network interfaces to virtual machine network interfaces,48

O

Overview,1

P

Posted in MyNetworking,59

R

Recovering the VSR through an ISO image,52 Registering licenses,53 Related information,85

S

Software configuration requirements,4

U

Upgrading the VSR,51

V

Virtual machine hardware configuration requirements,4 Virtual NIC specifications,5