# Revision history [back]

Two ways: - add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs; - add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this: $neutron port-update --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 b9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b --- output skipped --- | fixed_ips | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.114"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.115"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.116"} |

This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration. This has been tested, and works as of Newton release.

 2 No.2 Revision Bernd Bausch 7457 ●43 ●77 ●158 https://www.linkedin.c...

Two ways: - ways:

• add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs; - OSs;

• add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this: this:

$neutron port-update --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 b9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b --- output skipped --- | fixed_ips | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.114"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.115"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.116"} |

This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration. This has been tested, and works as of Newton release.

 3 No.3 Revision Bernd Bausch 7457 ●43 ●77 ●158 https://www.linkedin.c...

Two ways:

• add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs;

• add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this:

$neutron port-update --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 b9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b --- output skipped --- | fixed_ips | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.114"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.115"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.116"} |

This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration. This has been tested, and works as of Newton release.

 4 No.4 Revision Bernd Bausch 7457 ●43 ●77 ●158 https://www.linkedin.c...

Two ways:

• add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs;

• add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this:

$neutron port-update --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 b9f0b04f-a729-46b0-b087-d6a546def45b b9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b --- output skipped --- | fixed_ips | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.114"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.115"} | | | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.116"} |

This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration. This has been tested, and works as of Newton release.

Two ways:

• -
add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs;

• -
add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this:

$neutron port-update \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 \ b9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b b9f0b04f-a729-46b0-b087-d6a546def45b
--- output skipped --- ---
| fixed_ips | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.114"} | |
| | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.115"} | |
| | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "ip_address": "192.168.1.116"} "192.1.116"} |

This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration. configuration.
This has been tested, and works as of Newton release.

 6 No.6 Revision Bernd Bausch 7457 ●43 ●77 ●158 https://www.linkedin.c...

Two ways:
-

add more interfaces to an instance. This way every IP will have it's own policer(if you have any), and if you're using neutron port security(iptables filters), you'll have to assure that source traffic is being sent from the interface that this IP belongs to, otherwise it will be blocked by iptables. Latter can be achieved with iproute2 in linux, no idea about other OSs;
-

add more IPs to port. Using neutron port-update you can add more than 1 fixed IP to a port, like this:

$neutron port-update \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.114 \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.115 \ --fixed-ip subnet_id=b63cb5ae-44dd-463a-b27b-686780395bee,ip_address=192.168.1.116 \ b9f0b04f-a729-46b0-b087-d6a546def45bb9f0b04f-a729-46b0-b087-d6a546def45b$ neutron port-show b9f0b04f-a729-46b0-b087-d6a546def45b b9f0b04f-a729-46b0-b087-d6a546def45b
--- output skipped --- ---
| fixed_ips         | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "b63cb5ae-...", "ip_address": "192.168.1.114"} | |
|                       | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "b63cb5ae-...", "ip_address": "192.168.1.115"} | |
|                       | {"subnet_id": "b63cb5ae-44dd-463a-b27b-686780395bee", "b63cb5ae-...", "ip_address": "192.1.116"} |"192.168.1.116"} |


This way all IPs will have shared policer, and you don't have to worry about source traffic stickiness. DHCP behaviour hasn't been tested, so either test it youself, or use static configuration.
configuration. This has been tested, and works as of Newton release.