Virtual Route Reflector Getting Started Guide for VMware Modified: 2017-12-18
Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in the United States and other countries. All other trademarks may be property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Virtual Route Reflector Getting Started Guide for VMware Copyright 2017 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ( EULA ) posted at http://www.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. ii
Table of Contents About the Documentation............................................ vii Documentation and Release Notes................................. vii Documentation Conventions...................................... vii Documentation Feedback......................................... ix Requesting Technical Support...................................... x Self-Help Online Tools and Resources............................ x Opening a Case with JTAC...................................... x Chapter 1 Virtual Route Reflector Overview.................................... 13 Understanding Virtual Route Reflector.................................. 13 Virtual Route Reflector Package Contents............................ 13 Virtual Route Reflector Restrictions................................. 14 Virtual Route Reflector Hardware and Software Requirements............... 14 Virtual Route Reflector Hardware Requirements....................... 14 Virtual Route Reflector Software Requirements....................... 15 Chapter 2 Installing and Configuring Virtual Route Reflector on VMware........... 17 Installing the Virtual Route Reflector Image on VMware..................... 17 Configuring the Network.......................................... 18 Deploying the vrr VM............................................ 19 Adding Interfaces to the vrr Instance............................... 19 Setting Up the Serial Port......................................... 20 Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI................................................. 21 iii
Getting Started Guide for VMware iv
List of Tables About the Documentation.......................................... vii Table 1: Notice Icons................................................. viii Table 2: Text and Syntax Conventions................................... viii Chapter 1 Virtual Route Reflector Overview.................................... 13 Table 3: Hardware Requirements....................................... 14 v
Getting Started Guide for VMware vi
About the Documentation Documentation and Release Notes Documentation and Release Notes on page vii Documentation Conventions on page vii Documentation Feedback on page ix Requesting Technical Support on page x Documentation Conventions To obtain the most current version of all Juniper Networks technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/. If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes. Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books. Table 1 on page viii defines notice icons used in this guide. vii
Getting Started Guide for VMware Table 1: Notice Icons Icon Meaning Description Informational note Indicates important features or instructions. Caution Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser. Tip Indicates helpful information. Best practice Alerts you to a recommended use or implementation. Table 2: Text and Syntax Conventions Table 2 on page viii defines the text and syntax conventions used in this guide. Convention Description Examples Bold text like this Represents text that you type. To enter configuration mode, type the configure command: user@host> configure Fixed-width text like this Represents output that appears on the terminal screen. user@host> show chassis alarms No alarms currently active Italic text like this Introduces or emphasizes important new terms. Identifies guide names. Identifies RFC and Internet draft titles. A policy term is a named structure that defines match conditions and actions. Junos OS CLI User Guide RFC 1997, BGP Communities Attribute Italic text like this Represents variables (options for which you substitute a value) in commands or configuration statements. Configure the machine s domain name: [edit] root@# set system domain-name domain-name viii
About the Documentation Table 2: Text and Syntax Conventions (continued) Convention Description Examples Text like this Represents names of configuration statements, commands, files, and directories; configuration hierarchy levels; or labels on routing platform components. To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level. The console port is labeled CONSOLE. < > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>; (pipe symbol) Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity. broadcast multicast (string1 string2 string3) # (pound sign) Indicates a comment specified on the same line as the configuration statement to which it applies. rsvp { # Required for dynamic MPLS only [ ] (square brackets) Encloses a variable for which you can substitute one or more values. community name members [ community-ids ] Indention and braces ( { } ) ; (semicolon) Identifies a level in the configuration hierarchy. Identifies a leaf statement at a configuration hierarchy level. [edit] routing-options { static { route default { nexthop address; retain; } } } GUI Conventions Bold text like this Represents graphical user interface (GUI) items you click or select. In the Logical Interfaces box, select All Interfaces. To cancel the configuration, click Cancel. > (bold right angle bracket) Separates levels in a hierarchy of menu selections. In the configuration editor hierarchy, select Protocols>Ospf. Documentation Feedback We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods: Online feedback rating system On any page of the Juniper Networks TechLibrary site at http://www.juniper.net/techpubs/index.html, simply click the stars to rate the content, and use the pop-up form to provide us with information about your experience. Alternately, you can use the online feedback form at http://www.juniper.net/techpubs/feedback/. ix
Getting Started Guide for VMware E-mail Send your comments to techpubs-comments@juniper.net. Include the document or topic name, URL or page number, and software version (if applicable). Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC. JTAC policies For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf. Product warranties For product warranty information, visit http://www.juniper.net/support/warranty/. JTAC hours of operation The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/ Search for known bugs: https://prsearch.juniper.net/ Find product documentation: http://www.juniper.net/documentation/ Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/ Download the latest versions of software and review release notes: http://www.juniper.net/customers/csc/software/ Search technical bulletins for relevant hardware and software notifications: http://kb.juniper.net/infocenter/ Join and participate in the Juniper Networks Community Forum: http://www.juniper.net/company/communities/ Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/ To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/ Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone. Use the Case Management tool in the CSC at http://www.juniper.net/cm/. Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico). x
About the Documentation For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html. xi
Getting Started Guide for VMware xii
CHAPTER 1 Virtual Route Reflector Overview Understanding Virtual Route Reflector Understanding Virtual Route Reflector on page 13 Virtual Route Reflector Hardware and Software Requirements on page 14 The virtual Route Reflector (vrr) feature allows you to implement route reflector capability using a general purpose virtual machine that can be run on a 64-bit Intel-based blade server or appliance. Because a route reflector works in the control plane, it can run in a virtualized environment. A virtual route reflector on an Intel-based blade server or appliance works the same as a route reflector on a router, providing a scalable alternative to full mesh internal BGP peering. The vrr feature has the following benefits: Scalability: By implementing the vrr feature, you gain scalability improvements, depending on the server core hardware on which the feature runs. Also, you can implement virtual route reflectors at multiple locations in the network, which helps scale the BGP network with lower cost. Faster and more flexible deployment: You install the vrr feature on an Intel server, using open source tools, which reduces your router maintenance. Space savings: Hardware-based route reflectors require central office space. You can deploy the vrr feature on any server that is available in the server infrastructure or in the data centers, which saves space. Virtual Route Reflector Package Contents The vrr software packages are available as these types of packages: Application package This package is for launching vrr software in a virtualized environment for the first time. Install package This package is for upgrading vrr software that is already running to the next Junos OS release. Starting with Junos OS Release 15.1, the install package for vrr (jinstall64-vrr-*.*) is no longer available. Use the install package of Junos OS for MX Series platforms (junos-install-mx-x86-64-*.tgz or junos-x86-64-*.tgz) to upgrade vrr. 13
Getting Started Guide for VMware The vrr software images are available in these flavors: KVM and OpenStack TGZ package VMware ESXi OVA package Unified 64-bit Junos OS (upgraded FreeBSD kernel) Legacy 64-bit Junos OS Starting with Junos OS Release 15.1, the legacy package (jinstall64-vrr-*.*) is no longer available. Virtual Route Reflector Restrictions The following features are not supported with the vrr feature: Graceful Routing Engine Switchover (GRES) Nonstop Active Routing (NSR) Unified in-service software upgrade (unified ISSU) vrr is qualified primarily as a route reflector with minimal data plane support. For packet forwarding, MPLS VPN, and CoS feature support, you might consider vmx. Release History Table Release Description 15.1 Starting with Junos OS Release 15.1, the install package for vrr (jinstall64-vrr-*.*) is no longer available. 15.1 Starting with Junos OS Release 15.1, the legacy package (jinstall64-vrr-*.*) is no longer available. Virtual Route Reflector Hardware and Software Requirements Virtual Route Reflector Hardware Requirements on page 14 Virtual Route Reflector Software Requirements on page 15 Virtual Route Reflector Hardware Requirements Table 3 on page 14 lists the hardware requirements. Table 3: Hardware Requirements Description Value CPU Intel Xeon Nehalem or newer generation processor Memory 8 GB for vrr to run with default settings 32 GB for vrr to achieve higher scale 14
Chapter 1: Virtual Route Reflector Overview Table 3: Hardware Requirements (continued) Description Value Storage Local or NAS Each vrr instance requires 25G of disk storage Other requirements Hyperthreading (recommended) Any ESXi HCL supported NIC Virtual Route Reflector Software Requirements For software requirements, we recommend ESXi 6.0 for VMware. 15
Getting Started Guide for VMware 16
CHAPTER 2 Installing and Configuring Virtual Route Reflector on VMware Installing the Virtual Route Reflector Image on VMware on page 17 Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI on page 21 Installing the Virtual Route Reflector Image on VMware On VMware, connectivity to the vrr VM is accomplished by two interfaces: Management interface (em0) Performs the same function as the fxp0 interface on other platforms and is connected to the out-of-band management network. Data interface (em1) Terminates all routing traffic and is connected to the data network. The vrr instance installs with these two interfaces. They can be connected to either a single vswitch or two vswitches depending on the network configuration for the host. The OVA file installs vrr with these default settings: vcpus 1 Memory 8 GB Storage vrr image 25 GB Metadata image 1 MB Network adapters Two adapters em0, em1 Hardware version Version 8 Version 10 (starting with Junos OS Release 16.1) To install vrr with the VMware vsphere Client: 1. Download the vrr software package for VMware from the Virtual Route Reflector page to a location accessible to the server. 17
Getting Started Guide for VMware 2. Launch the vsphere Client for your ESXi server and log in to the server with your credentials. To install vrr with vsphere Client, perform these tasks: Configuring the Network on page 18 Deploying the vrr VM on page 19 Adding Interfaces to the vrr Instance on page 19 Setting Up the Serial Port on page 20 Configuring the Network You must assign port groups (networks) to the vrr interfaces to have proper connectivity. You configure the VLAN ID based on how you want to handle VLAN tagged traffic for the vrr interface assigned to the port group. To configure the port group: 1. In the left navigation pane, select the ESXi server and click the Configuration tab. Select Networking under Hardware. 2. If you are using an existing vswitch, skip to the next step. In the top right corner, click Add networking to create a vswitch. a. For Connection Type, select the Create vsphere standard switch option button, select the physical NIC check box to which you want to direct traffic (for example, vmnic3), and click Next. b. For Connection Settings, name the network. 3. Select Networking and click Properties next to the Standard Switch. 4. In the vswitch Properties dialog box, select the virtual machine port group in the Ports tab and click Edit at the bottom. 5. In the Port Group Properties section, name the port group and select the appropriate VLAN ID. None (0) Used when the vrr configuration that is not set up for VLAN tagged traffic and the traffic destined for the vrr interfaces assigned to this port group will not have a VLAN tag. All (4095) Used for the vrr configuration where vrr interfaces assigned to this port group are configured with VLAN tags. VLAN ID Used for the vrr configuration where the traffic destined for the vrr interfaces assigned to this port group are tagged and the interface is configured only with the IPv4 or IPv6 address family. If you specify the VLAN ID, the traffic is untagged and delivered to the vrr interface as native IP frames. 18
Chapter 2: Installing and Configuring Virtual Route Reflector on VMware Click OK. Deploying the vrr VM To deploy the VRR VM using.ova files: 1. In the left navigation pane, select the ESXi server and select Deploy OVF Template from the File menu. 2. In the Source pane, click Browse, select the.ova file for the VM, and click Next. 3. In the OVF Template Details pane, click Next. This pane displays a summary of the OVA file contents. 4. In the Name and Location pane, specify the name of the VM and click Next. 5. In the Storage pane, select the appropriate datastore for the destination storage of the VM and click Next. 6. In the Disk Format pane, select the Thick Provision Lazy Zeroed option button and click Next. 7. In the Network Mapping pane, map the destination to the port group for the interface. If you have not created the port groups when configuring the network, you can edit the VM later. The first interface (em0) is for the management network and the second interface (em1) is for the data network. Make your selections and click Next. 8. In the Ready to Complete pane, verify your configuration and click Finish. 9. To launch vrr, select the VM in the left navigation pane and right-click Power > Power On. Adding Interfaces to the vrr Instance After deploying vrr, you can add more virtual NIC interfaces. NOTE: vrr does not support hot-plugging of interfaces. You must power down the VM before adding more interfaces. To add an interface to the VM: 1. In the left navigation pane, select the VM and and right-click Edit Settings to display the Virtual Machine Properties window. 19
Getting Started Guide for VMware 2. To add an interface, click Add in the Hardware tab of the Virtual Machine Properties window. The Add Hardware wizard is displayed. a. For Device Type, select Ethernet Adapter and click Next. b. For Network connection, select E1000 for the adapter type, select the port group for the network connection, and click Next. c. Verify your configuration and click Finish. Click OK in the Virtual Machine Properties window. 3. To launch vrr, select the VM in the left navigation pane and right-click Power > Power On. Setting Up the Serial Port You can connect to the serial console on vrr by setting up a serial port. NOTE: vrr does not support hot-plugging of the serial port. You must power down the VM before setting or changing the serial port. To set up the serial port for the VM: 1. In the left navigation pane, select the VM and and right-click Edit Settings to display the Virtual Machine Properties window. 2. To add the serial port, click Add in the Hardware tab of the Virtual Machine Properties window. The Add Hardware wizard is displayed. a. For Device Type, select Serial Port and click Next. b. For Select Port Type, select the Connect via Network button and click Next. c. For Select Network Backing, select the Server button and specify the port number in the Port URI text box in the format telnet://:port-number (for example, telnet://:8601). Click Next. d. Click Finish. Click OK in the Virtual Machine Properties window. 3. To launch vrr, select the VM in the left navigation pane and right-click Power > Power On. 20
Chapter 2: Installing and Configuring Virtual Route Reflector on VMware After you have configured the serial port connection, you can access the serial console port for the VM using the telnet esxi-server-ip-address port-number command. Related Documentation Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI on page 21 Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI 1. Using the Junos CLI in the virtual machine console, configure the interfaces that were connected to the OVS virtual switch-br (for KVM or OpenStack) or the vswitch (for VMware). Specify the IP addresses that were assigned to the VNICs while configuring OVS (KVM) or vswitch (VMware). [edit] user@host# set interfaces interface-name family inet address address user@host# set interfaces interface-name family inet6 address address 2. Configure the loopback interface with the IP address for the vrr. [edit] user@host# set interfaces lo0 unit 0 family inet address address user@host# set interfaces lo0 unit 0 family inet6 address address 3. Add a static default route to the gateway address of the management IP address: [edit] user@host# set routing-options static route 0.0.0.0/0 next-hop address 4. Configure the hostname for the vrr. [edit system] user@host# set host-name hostname 5. Configure the root password. [edit system] user@host# set root-authentication plain-text-password 6. Add a user. [edit system login] user@host# set user user-name 7. Set the user identification (UID). [edit system login user user-name] user@host# set uid uid-value 8. Assign the user to a login class. [edit system login user user-name] 21
Getting Started Guide for VMware user@host# set class class-name 9. Set the user password. [edit system login user user-name] user@host# set authentication plain-text-password 10. Enable Telnet and FTP access. [edit system services] user@host# set ftp user@host# set telnet 11. Configure the types of system log messages to send to files and to user terminals. [edit system syslog] user@host# set user * any emergency user@host# set file messages any notice user@host# set file messages authorization info user@host# set file interactive-commands interactive-commands any 12. Configure the vrr to always use 64-bit processing. [edit system processes] user@host# set routing force-64-bit 13. Configure the router ID and the autonomous system (AS) number. [edit routing-options] user@host# set router-id address user@host# set autonomous-system autonomous-system 14. Configure BGP, including the cluster identifier and the neighbor relationships with all IBGP-enabled devices in the autonomous system (AS). [edit protocols bgp group group-name] user@host# set type internal user@host# set local-address address user@host# set cluster cluster-name user@host# set neighbor address 15. (External peers only) Specify that the BGP next-hop value not be changed. [edit protocols bgp group group-name multihop] user@host# set no-nexthop-change 16. Configure a forwarding-table export policy to prevent the installation of BGP routes in the forwarding table. A vrr is not expected to be in the forwarding path for BGP service prefixes. [edit policy-options] user@host# set policy-statement policy-name term term-name from protocol bgp user@host# set policy-statement policy-name term term-name then reject 22
Chapter 2: Installing and Configuring Virtual Route Reflector on VMware 17. Apply the BGP policy to the forwarding table. [edit routing-options] user@host# set forwarding-table export policy-name 18. Configure other desired protocols for the interfaces. 23
Getting Started Guide for VMware 24