Configuring host routes with neutron#
These sections walk you through configuring host routes by using the neutron client.
Creating a network (neutron client)#
After you create a network, copy its network ID. You use this ID to create a subnet and boot the server.
Issue the following neutron client command, substituting your own values for the ones shown.
Create network with neutron request
$ neutron net-create Rackernet
Positional argument:
The network name. In this example, the network name is
Rackernet.
Create network with neutron response
+----------------+--------------------------------------+ | Field | Value | +----------------+--------------------------------------+ | admin_state_up | True | | id | a8fde776-e80f-47bb-a050-0c057d89afc3 | | name | Rackernet | | shared | False | | status | ACTIVE | | subnets | | | tenant_id | 5831008 | +----------------+--------------------------------------+
Copy the
idvalue from the output. You will use this value when you create a subnet, provision your server, or perform other related activities. In this example, the ID isa8fde776-e80f-47bb-a050-0c057d89afc3, but use the ID from your response.
Creating a subnet with host routes (neutron client)#
To create a subnet with host routes, you specify a network, an IP address, allocation pools, and host routes for your subnet.
Issue the following cURL command, substituting your own values for the ones shown.
Create subnet with neutron request
$ neutron subnet-create \ --ip-version 4 \ --allocation-pool start=192.168.5.3,end=192.168.5.100 \ --allocation-pool start=192.168.5.103,end=192.168.5.254 \ --host-route destination=1.1.1.0/24,nexthop=192.168.5.254 \ --tenant-id 5831008 \ a8fde776-e80f-47bb-a050-0c057d89afc3 192.168.5.0/24Positional arguments:
ip-versionThe version of the subnet IP. In this example, the version is4.allocation-poolThe start and end addresses for one or more allocation pools. In this example, there are two poolsstart=192.168.5.3,end=192.168.5.100andstart=192.168.5.103,end=192.168.5.254.host-routeA list of host route dictionaries for the subnet. In this example, we used"destination": "1.1.1.0/24", "nexthop": "192.168.5.254".tenant-idThe tenant ID. In this example, we used the tenant ID5831008.The network ID or name. In this example, we used the network ID
a8fde776-e80f-47bb-a050-0c057d89afc3.The network CIDR. In this example, the CIDR is
192.168.5.0/24.
Create subnet with neutron response
+------------------+-----------------------------------------------------------+ | Field | Value | +------------------+-----------------------------------------------------------+ | allocation_pools | {"start": "192.168.5.3", "end": "192.168.5.100"} | | | {"start": "192.168.5.103", "end": "192.168.5.254"} | | cidr | 192.168.5.0/24 | | dns_nameservers | | | enable_dhcp | | | gateway_ip | | | host_routes | {"destination": "1.1.1.0/24", "nexthop": "192.168.5.254"} | | id | 98c1af30-05c9-4502-8b1f-9bffde843cba | | ip_version | 4 | | name | | | network_id | a8fde776-e80f-47bb-a050-0c057d89afc3 | | tenant_id | 5831008 | +------------------+-----------------------------------------------------------+
Note the host_routes attribute with the destination of
1.1.1.0/24and the nexthop of192.168.5.254.
Booting a Server (nova client)#
The following step shows you how to boot server with the nova client, using the network ID of the network you created in the first step of this procedure.
Note
To create your new server, you need the following information:
The name of the new server. Use a name of your choice.
The image ID.
The flavor ID.
The network ID of the network, which is
net-id=a8fde776-e80f-47bb-a050-0c057d89afc3.
Issue the following nova client command.
Boot server with nova request
$ nova boot ata --image ffa476b1-9b14-46bd-99a8-862d1d94eb7a / --flavor 2 --nic net-id=a8fde776-e80f-47bb-a050-0c057d89afc3Positional arguments
The server name. In this example, the name is
ata.image. The image ID. In this example, the ID isffa476b1-9b14-46bd-99a8-862d1d94eb7a.flavor. The flavor ID. In this example, the ID is2nic net-id. The network ID. In this example, the ID isa8fde776-e80f-47bb-a050-0c057d89afc3.
Boot server with nova response
+-------------------------+-----------------------------------------------------------------+ | Property | Value | +-------------------------+-----------------------------------------------------------------+ | OS-DCF:diskConfig | AUTO | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | scheduling | | OS-EXT-STS:vm_state | building | | accessIPv4 | | | accessIPv6 | | | adminPass | ugZmn5Le6S8y | | created | 2014-02-06T20:05:12Z | | flavor | m1.mid (2) | | hostId | | | id | a1061a57-0136-4c29-aac1-8b1a646a3001 | | image | cirros-0.3.0-x86_64-disk (82e72de5-6366-4217-8c87-a570a9b17e73) | | metadata | {} | | name | ata | | progress | 0 | | security_groups | default | | status | BUILD | | tenant_id | 5831008 | | updated | 2014-02-06T20:05:12Z | | user_id | 28be72f8fc5b45589c93f55274e459ce | +-------------------------+-----------------------------------------------------------------+
Copy the
idvalue from the output for future reference. In this example, the ID isa1061a57-0136-4c29-aac1-8b1a646a3001, but use the ID from your response.
Verifying the IP on the server port (nova client)#
The following step shows you how to verify the IP address on the server port.
In this case, the IP address should be 192.168.5.3 from the start of the
allocation pool.
Issue the following command, substituting your value for the one shown.
Show server details with nova request
$ nova list a1061a57-0136-4c29-aac1-8b1a646a3001
Positional arguments:
The server ID. In this example, the ID is
a1061a57-0136-4c29-aac1-8b1a646a3001.
Show server details with nova response
+-------------------------+------------------------------------------------------------------------------------+ | Property | Value | +-------------------------+------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | AUTO | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | accessIPv4 | 10.23.233.124 | | accessIPv6 | 2001:4801:787f:205:bccb:feff:fe00:189 | | created | 2012-08-16T16:28:18Z | | flavor | 8GB Standard Instance (6) | | hostId | 0488142a8f859cb4020234cc235f8cd8a22bee126726025d70c0b9ba | | id | a1061a57-0136-4c29-aac1-8b1a646a3001 | | image | cirros-0.3.0-x86_64-disk (82e72de5-6366-4217-8c87-a570a9b17e73) | | metadata | {} | | name | ata | | Rackernet | 192.168.5.3 | | private network | 10.181.192.114 | | progress | 100 | | public network | 2001:4801:787f:205:bccb:feff:fe00:189, 10.23.233.124 | | status | ACTIVE | | tenant_id | 5831008 | | updated | 2014-02-06T20:05:12Z | | user_id | 207638 | +-------------------------+------------------------------------------------------------------------------------+
Note the IP address on the
publicinterface (in this case,10.23.233.124). Use this to log in to the server in the next step.
Logging in to the server and verify the route (ssh)#
The following steps show you how to log in to the server and verify that the host route is configured correctly by using the command line.
Issue the following command at the prompt, substituting your own value for the one shown.
$ ssh root@10.23.233.124
The command returns output like the following example:
The authenticity of host '10.23.233.124 (10.23.233.124)' can't be established. RSA key fingerprint is 87:b6:8f:7a:44:80:a4:58:f8:9b:09:82:d4:b0:f9:bf. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.23.233.124' (RSA) to the list of known hosts. root@10.23.233.124's password:
Enter your password when prompted.
Issue the following command at the prompt:
root@ata:~# route
The command returns output like the following example:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.23.233.1 0.0.0.0 UG 100 0 0 eth0 1.1.1.0 192.168.5.254 255.255.255.0 UG 0 0 0 eth2 10.23.233.0 * 255.255.255.0 U 0 0 0 eth0 10.181.192.0 * 255.255.248.0 U 0 0 0 eth1 192.168.5.0 * 255.255.255.0 U 0 0 0 eth2
Notice the route
1.1.1.0with Gateway192.168.5.254in the preceding output. That is what was expected.
Next topic: Provisioning additional IP address and dual-stack IP addresses on an isolated network port