Creating Network Ports for the NO Network Interfaces

A.3.2 Creating Network Ports for the NO Network Interfaces

Each network interface on an instance must have an associated network port.

An instance usually has at least eth0 and eth1 for a public and private network respectively.

Some configurations require six or more interfaces and corresponding network ports.

Determine the IP address for the interface.
For eth0, the IP might be 10.x.x.157.
For eth1, the IP might be 192.168.x.157
Identify the neutron network ID associated with each IP or interface using the neutron command line tool.
```
$ neutron net-list
```
Identify the neutron subnet ID associated with each IP or interface using the neutron command line tool.
```
$ neutron subnet-list
```
Create the network port using the neutron command line tool, being sure to choose an informative name. Note the use of the subnet ID and the network ID (final argument).
Port names are usually a combination of instance name and network name.
NOAM-A-xmi

SO2-imi

MP5-xsi2

The ports must be owned by the DSR tenant user, not the admin user. Either source the credentials of the DSR tenant user or use the DSR tenant user ID as the value for the —tenant-id argument.
```
$ . keystonerc_dsr_user
$ keystone user-list
$ neutron port-create --name=NO1-xmi –-tenant-id <tenant id> --fixed-ip subnet_id=<subnet id>,ip_address=10.x.x.157 <network id>
$ neutron port-create --name=NO1-imi -–tenant-id <tenant id> --fixed-ip subnet_id=<subnet id>,ip_address=192.168.x.157 <network id>
```
View your newly created ports using the neutron tool.
```
$ neutron port-list
```