close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Virtual Route Reflector Overview
play_arrow Installing and Configuring Virtual Route Reflector on OpenStack
- Installing the Virtual Route Reflector Image Using OpenStack
- Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI

list Table of Contents

English

Installing the Virtual Route Reflector Image Using OpenStack

date_range 17-Aug-21

arrow_backward

arrow_forward

OpenStack is a free, open-source cloud computing platform that supports creation and management of virtual Route Reflectors (vRR). OpenStack allows you to:

Attach a VNIC to a physical NIC
Display a graphical representation of the virtual machine
Allocate a specific amount of disk space for the virtual machine
Take a snapshot of a running virtual machine
Create a new virtual machine from a snapshot

The physical and virtual machines are connected using OpenvSwitch, which eliminates the need to configure tunnels and overlays, such as MPLS over GRE and MPLS over UDP. OpenvSwitch also provides better performance than other methods, because the physical NICs are dedicated to specific VNICs.

This topic includes the following tasks:

Composing User Authentication Credentials

Appropriate user credentials are required for authentication to succeed for every OpenStack command. You can compose credentials with either of the following two methods:

Exporting User Credentials Once
Passing User Credentials Each Time You Use a Command

Exporting User Credentials Once

To avoid passing user credentials every time you use the OpenStack command line, export the credentials:

Create a keystonerc file with the following contents:
```
export ADMIN_TOKEN=token
export OS_USERNAME=username
export OS_TENANT_NAME=tenant-name 
export OS_PASSWORD=password
export OS_AUTH_URL=http://ip_address_of_keystone:portNumber/v2.0
```
where
- token—Authorization token
- username—OpenStack user name
- tenant-name—Tenant name
- password—Password for OpenStack user
- ip_address_of_keystone:portNumber—IP address of the keystone authentication server and its port number
Perform a sourcing of the keystonerc file:
```
source keystonerc
```

Passing User Credentials Each Time You Use a Command

To pass credentials on the command line every time you execute an OpenStack command:

Enter the following in the OpenStack command line:

content_copy zoom_out_map
--os-username username --os-password password --os-tenant-name tenant-name --os-auth-url http://ip_address_of_keystone:portNumber /v2.0 

where

username—OpenStack user name
tenant-name—Tenant name
password—Password for OpenStack user
ip_address_of_keystone:portNumber—IP address of the keystone authentication server and its port number

Registering an Image

Before the vRR image can be used to create a vRR instance, the image must be brought into the glance directory.

To bring the vRR image into the glance directory:

Enter the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ glance image-create  --name image-name --disk-format=qcow2 --container-format= bare --file=image-location

where

image-name—A name for the image. This name is used later when creating the vRR instance.
image-location—The location of the vRR image.

Updating the Disk, CD-ROM, and VIF Settings for the Image

By default, OpenStack uses virtio for disk, CDROM, and VIF (NIC) models, but Junos-based images do not support virtio drivers. You must update the image to change these settings.

Enter the following in the OpenStack command line:
```
stack@host$ glance image-update --property hw_disk_bus=ide --property hw_cdrom_bus=ide --property hw_vif_model=e1000 image-name
```
The image-name is the name of the image you used in Registering an Image.
Verify that the image was brought into the glance directory by entering the following in the OpenStack command line:
```
stack@host$ glance image-list
```
The image that you used in Registering an Image should be in the list of images that is displayed.

Creating a Virtual Hardware Template

A virtual hardware template in OpenStack is called a flavor. A flavor defines a set of hardware parameters, and is later applied to the vRR instance.

To create a flavor for a vRR instance:

Enter the following in the OpenStack command line:
```
stack@host$ nova flavor-create --is-public true flavor-name 6 16384 10 1
```
This makes the flavor available to the public, sets the flavor ID to 6, sets the memory size to 16384 GB, sets the disk size to 10 GB, and sets the number of virtual CPUs to one.

The flavor-name is the name of the flavor, for example VRR-flavor.
Verify that the flavor was created by entering the following in the OpenStack command line:
```
stack@host$ nova flavor-list
```
The flavor that you configured in Step 1 should be in the list of flavors that is displayed.

Creating Networks and Subnets

Create networks and subnets for internal and external communication. The virtual NICs of the vRR instances can later be attached to the subnets.

To create a private network, enter the following in the OpenStack command line:
```
stack@host$ neutron net-create private-network-name
```
The private-network-name is the name of the private network.

For example:
```
stack@host$ neutron net-create private1
```
To create a subnet for a private network, enter the following in the OpenStack command line:
```
stack@host$ neutron subnet-create --name private-subnet-name private-network-name subnet-cidr
```
where
- private-subnet-name—Name of the subnet
- private-network-name—Name of the private network to which the subnet belongs
- subnet-cidr—CIDR of the subnet
For example:
```
stack@host$ neutron subnet-create --name private1-subnet1 private1 10.0.0.0/24
```
To create a public network, enter the following in the OpenStack command line:
```
stack@host$ neutron net-create public-network-name --router:external=True
```
The public-network-name is the name of the public network.

For example:
```
stack@host$ neutron net-create public1 --router:external=True
```
To create a subnet for a public network, enter the following in the OpenStack command line:
```
stack@host$ neutron subnet-create public-network-name subnet-cidr --name public-subnet-name --enable_dhcp=False --allocation-pool start=start_ip_address,end=end_ip_address  --gateway=gateway_ip_address
```
where
- public-network-name—Name of the public network to which the subnet belongs
- subnet-cidr—CIDR of the subnet
- public-subnet-name—Name of the subnet
- start_ip_address—Lowest IP address in the allocated address range
- end_ip_address—Highest IP address in the allocated address range
- gateway_ip_address—Gateway IP address for the host machine
For example:
```
stack@host$ neutron subnet-create public1 192.168.239.90/25 --name public1-subnet1 --enable_dhcp=False --allocation-pool start=192.168.239.64,end=192.168.239.65 --gateway=192.168.239.126
```

Verify that the networks were created by entering the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ neutron net-list

The networks that you configured should be in the list that is displayed.

For example:

content_copy zoom_out_map
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| id                                    | name      | subnets                
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| 2d934de5-e29c-4fc0-9d00-de83dcfa2b89  | private1  | e9f89ec4-27d5-4d33-b552-                                                     a239173bc284 10.0.0.0/24
| d1ec3880-9823-4c28-945c-2ec77b809f1a  | public1   |c65acb85-239e-4464-add1-                                                     a0913dab0f27                                                      192.168.239.0/25
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Verify that the subnets were created by entering the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ neutron subnet-list

The subnets that you configured should be in the list that is displayed.

For example:

content_copy zoom_out_map
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| id                  |name            | cidr     | allocation_pools         
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| c65acb85-239e-4464- |public1-subnet1 |192.168. | {”start”; “192.168.239.64”,  add1-a0913dab0f27                     239.0/25  “end”: “192.168.239.65”}
| e9f89ec4-27d5-      |private1-subnet1|10.0.0.0| {”start”; “10.0.0.2”,  rd33-b552-                             /24       “end”: “192.168.239.65”}  a239173bc284
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Creating a vRR Instance

An instance is a virtual machine on which the vRR runs. To create the instance, you provide the image name, the flavor, the network ID for the virtual NIC, and a name for the instance.

To create a vRR instance:

Display the ID of the network that you want to associate with the vRR instance virtual NIC by entering the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ neutron net-list

For example:

content_copy zoom_out_map
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| id                                    | name      | subnets                
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| 2d934de5-e29c-4fc0-9d00-de83dcfa2b89  | private1  | e9f89ec4-27d5-4d33-b552-                                                     a239173bc284 10.0.0.0/24
| d1ec3880-9823-4c28-945c-2ec77b809f1a  | public1   |c65acb85-239e-4464-add1-                                                     a0913dab0f27                                                      192.168.239.0/25
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Record the ID of the network.
Enter the following in the OpenStack command line:
```
stack@host$ nova boot --image image-name flavor 6 --nic net-id=net-id “instance-name”
```
where
- image-name—Image name that you used in Registering an Image
- net-id—ID of the network that you want to associate with the vRR instance virtual NIC
- instance-name—The name for the vRR instance
For example:
```
stack@host$ nova boot --image VRR-image flavor 6 --nic net-id=2d934de5-e29c-4fc0-9d00-de83dcfa2b89 “VRR-1”
```
Verify that the vRR instance has been created by entering the following in the OpenStack command line:
```
stack@host$ nova list
```
The instance that you created should be in the list that is displayed.

Creating a Router

An OpenStack router is a logical entity that routes packets among internal subnets, forwards packets from internal networks to external networks, and accesses the vRR instances from external networks. You must create a router and create an interface on the router for each subnet with which it communicates.

Note:

The em0 interface can only function as a management interface. You cannot use the em0 interface for routing configurations.

To create a router, enter the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ neutron router-create router-name

The router-name is the name for the router.

The ID of the router is displayed.

For example:

content_copy zoom_out_map
stack@host$ neutron router-create GWR

content_copy zoom_out_map
Created a new router:
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| Field                   |Value 
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| admin_state_up          |True   
| external_gateway_info
| id                      | b93033e7-e825-40fa-811f-df72d3cd230d
| name                    | GWR 
| status                  | ACTIVE
| tenant_id               | 8d2d7bd590a14d30b4f662dbefdd8e0e      
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Record the ID of the router.

Display the ID of the subnet with which the router should communicate by entering the following in the OpenStack command line:

content_copy zoom_out_map
stack@host$ neutron subnet-list

For example:

content_copy zoom_out_map
stack@host$ neutron subnet-list

content_copy zoom_out_map
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| id                  |name            | cidr     | allocation_pools         
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| c65acb85-239e-4464- |public1-subnet1 |192.168. | {”start”; “192.168.239.64”,  add1-a0913dab0f27                     239.0/25  “end”: “192.168.239.65”}
| e9f89ec4-27d5-      |private1-subnet1|10.0.0.0| {”start”; “10.0.0.2”,  rd33-b552-                             /24       “end”: “192.168.239.65”}  a239173bc284
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Record the ID of the subnet.
Create an interface on the router for the subnet with which it communicates by entering the following in the OpenStack command line.
```
stack@host$ neutron router-interface-add router-id subnet-id
```
where
- router-id—ID of the router
- subnet-id—ID of the subnet
For example:
```
stack@host$ neutron router-interface-add b93033e7-e825-40fa-811f-df72d3cd230d e9f89ec4-27d5-rd33-b552-a239173bc284
```

Display the networks.

content_copy zoom_out_map
stack@host$ neutron net-list

For example:

content_copy zoom_out_map
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| id                                    | name      | subnets                
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| 2d934de5-e29c-4fc0-9d00-de83dcfa2b89  | private1  | e9f89ec4-27d5-4d33-b552-                                                    a239173bc284 10.0.0.0/24
| d1ec3880-9823-4c28-945c-2ec77b809f1a  | public1   |c65acb85-239e-4464-add1-                                                     a0913dab0f27                                                      192.168.239.0/25
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Record the ID of the public network that should serve as the gateway for the router.
Configure the router as an external gateway by entering the following in the OpenStack command line.
```
stack@host$ neutron router-gateway-set router-id net-id
```
where
- router-id—ID of the router
- net-id—ID of the public network that serves as the gateway for the router
For example:
```
stack@host$ neutron router-gateway-set b93033e7-e825-40fa-811f-df72d3cd230d d1ec3880-9823-4c28-945c-2ec77b809f1a
```

Assigning a Floating IP to a vRR Instance

A floating IP represents an external IP address, and provides access to the vRR instance from an external network. A floating IP can only be created for a network that has the router:external attribute.

Create a floating IP for the public network by entering the following in the OpenStack command line.

content_copy zoom_out_map
stack@host$ neutron floatingip-create public-network-name

The public-network-name is the name of the public network.

For example:

content_copy zoom_out_map
stack@host$ neutron floatingip-create public1

Information for the floating IP appears.

For example:

content_copy zoom_out_map
Created a new floatingip:
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| Field                  |Value                      
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -
| fixed_ip_address       |
| floating_ip_address    | 192.168.239.106
| floating_network_id    | b4934fe4-4664-4c61-b404-c6a63533e842
| id                     | aaa1fa59-7e20-4331-8d39-63c00aa29781
| port_id                |
| router_id              | 8d2d7bd590a14d30b4f662dbefdd8e0e      
| status                 | DOWN
| tenant_id              | e4a38502668b427c9875c591b62b76
- - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - -

Record the address of the floating IP.
Assign the floating IP to the vRR instance by entering the following in the OpenStack command line.
```
stack@host$ nova add-floating-ip instance-name floating-ip-address
```
where
- instance-name—Instance name that you used in Creating a vRR Instance
- floating-ip-address— IP address you recorded in Step 2
For example:
```
stack@host$ nova add-floating-ip VRR-1 192.168.239.106
```
Verify that the floating IP has been created by entering the following in the OpenStack command line:
```
stack@host$ nova floating-ip-list
```
The floating IP that you created should be in the list that is displayed.

Configuring Security Group Rules

To allow access to the vRR instance via SSH and ping, you must create security rules.

Create a security rule for TCP traffic and assign it to the default security group by entering the following in the OpenStack command line.
```
stack@host$ nova secgroup-add-rule default tcp start-port-range end-port-range cidr-address-range
```
where
- start-port-range—Lowest port number in the allowed port range. To allow any port, use -1 -1 for the port range.
- end-port-range—Highest port number in the allowed port range.
- cidr-address-range—CIDR of the allowed address range.
For example:
```
stack@host$ nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
```
Create a security rule for ICMP traffic and assign it to the default security group by entering the following in the OpenStack command line.
```
stack@host$ nova secgroup-add-rule default icmp start-port-range end-port-range cidr-address-range
```
For example:
```
stack@host$ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
```

arrow_backward PREVIOUS Virtual Route Reflector Software Requirements

NEXT arrow_forward Configuring Interfaces, Protocols, and Routes of the Virtual Route Reflector Using Junos CLI

vRR Getting Started Guide for OpenStack

ON THIS PAGE

Installing the Virtual Route Reflector Image Using OpenStack

Composing User Authentication Credentials

Exporting User Credentials Once

Passing User Credentials Each Time You Use a Command

Registering an Image

Updating the Disk, CD-ROM, and VIF Settings for the Image

Creating a Virtual Hardware Template

Creating Networks and Subnets

Creating a vRR Instance

Creating a Router

Assigning a Floating IP to a vRR Instance

Configuring Security Group Rules

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

vRR Getting Started Guide for OpenStack

ON THIS PAGE

Installing the Virtual Route Reflector Image Using OpenStack

Composing User Authentication Credentials

Exporting User Credentials Once

Passing User Credentials Each Time You Use a Command

Registering an Image

Updating the Disk, CD-ROM, and VIF Settings for the Image

Creating a Virtual Hardware Template

Creating Networks and Subnets

Creating a vRR Instance

Creating a Router

Assigning a Floating IP to a vRR Instance

Configuring Security Group Rules

Related Documentation

Stay in touch