# Revision history [back]

### DVR and assignment of FIP gateway IP address

Hi,

I have a routing requirement that requires each compute node that is connected to the fabric to have a FIP gateway that has had its IP address allocated from a distinct subnet. Each, FIP gw address is from 11.1.0.0/26 for compute node one, 11.2.0.0/26 for compute node 2, and so on.

I'm aware of the following:

openstack subnet create demo-floating-ip-agent-gateway-subnet \ --subnet-range 198.51.100.0/24 --no-dhcp \ --service-type 'network:floatingip_agent_gateway' \ --network demo-ext-net

Which means that for me, it might be something like this that gets me the subnets:

openstack subnet create demo-floating-ip-agent-gateway-subnet-1 \
--subnet-range 11.1.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net

openstack subnet create demo-floating-ip-agent-gateway-subnet-2 \
--subnet-range 11.2.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


But then the question is, if the above is legitimate, how do I make the association (compute node 1, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-1, compute node 2, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-2, etc..)?

Alternately, does someone have experience in using DVR in CLOS based networks that can provide some insight about configurations that support DVR? Or is DVR not a good solution, old school vRouting or something else is needed to provide support for FIP?

### DVR and assignment of FIP gateway IP address

Hi,

I have a routing requirement that requires each compute node that is connected to the fabric to have a FIP gateway that has had its IP address allocated from a distinct subnet. Each, For example, the FIP gw address is assigned from 11.1.0.0/26 for compute node one, 1, 11.2.0.0/26 for compute node 2, and so on.

I'm aware of the following:

openstack subnet create demo-floating-ip-agent-gateway-subnet \ --subnet-range 198.51.100.0/24 --no-dhcp \ --service-type 'network:floatingip_agent_gateway' \ --network demo-ext-net

Which means that for me, it might be something like this that gets me the subnets:

openstack subnet create demo-floating-ip-agent-gateway-subnet-1 \
--subnet-range 11.1.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net

openstack subnet create demo-floating-ip-agent-gateway-subnet-2 \
--subnet-range 11.2.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


But then the question is, if the above is legitimate, how do I make the association (compute node 1, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-1, compute node 2, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-2, etc..)?

Alternately, does someone have experience in using DVR in CLOS based networks that can provide some insight about configurations that support DVR? Or is DVR not a good solution, old school vRouting or something else is needed to provide support for FIP?

### DVR and assignment of FIP gateway IP address

Hi,

I have a routing requirement that requires each compute node that is connected to the fabric to have a FIP gateway that has had its IP address allocated from a distinct subnet. For example, the FIP gw address is assigned from 11.1.0.0/26 for compute node 1, 11.2.0.0/26 for compute node 2, and so on.

I'm aware of the following:

openstack subnet create demo-floating-ip-agent-gateway-subnet \
--subnet-range 198.51.100.0/24 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-netdemo-ext-net


Which means that for me, it might be something like this that gets me the subnets:

openstack subnet create demo-floating-ip-agent-gateway-subnet-1 \
--subnet-range 11.1.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net

openstack subnet create demo-floating-ip-agent-gateway-subnet-2 \
--subnet-range 11.2.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


But then the question is, if the above is legitimate, how do I make the association (compute node 1, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-1, compute node 2, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-2, etc..)?

Alternately, does someone have experience in using DVR in CLOS based networks that can provide some insight about configurations that support DVR? Or is DVR not a good solution, old school vRouting or something else is needed to provide support for FIP?

### DVR and assignment of FIP gateway IP address

Hi,

I have a routing requirement that requires each compute node that is connected to the fabric to have a FIP gateway that has had its IP address allocated from a distinct subnet. For example, the FIP gw address is assigned from 11.1.0.0/26 for compute node 1, 11.2.0.0/26 for compute node 2, and so on.

I'm aware of the following:

openstack subnet create demo-floating-ip-agent-gateway-subnet \
--subnet-range 198.51.100.0/24 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


Which means that for me, it might be something like this that gets me the subnets:

openstack subnet create demo-floating-ip-agent-gateway-subnet-1 \
--subnet-range 11.1.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net

openstack subnet create demo-floating-ip-agent-gateway-subnet-2 \
--subnet-range 11.2.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


But then the question is, if the above is legitimate, how do I make the association (compute node 1, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-1, compute node 2, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-2, etc..)?

Alternately, does someone have experience in using DVR in CLOS based networks that can provide some insight about configurations that support DVR? Or is DVR not a good solution, old school vRouting or something else is needed to provide support for FIP?

### DVR and assignment of FIP gateway IP address

Hi,

I have a routing requirement that requires each compute node that is connected to the fabric to have a FIP gateway that has had its IP address allocated from a distinct subnet. For example, the FIP gw address is assigned from 11.1.0.0/26 for compute node 1, 11.2.0.0/26 for compute node 2, and so on.

I'm aware of the following:

openstack subnet create demo-floating-ip-agent-gateway-subnet \
--subnet-range 198.51.100.0/24 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


Which means that for me, it might be something like this that gets me the subnets:

openstack subnet create demo-floating-ip-agent-gateway-subnet-1 \
--subnet-range 11.1.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net

openstack subnet create demo-floating-ip-agent-gateway-subnet-2 \
--subnet-range 11.2.0.0/26 --no-dhcp \
--service-type 'network:floatingip_agent_gateway' \
--network demo-ext-net


But then the question is, if the above is legitimate, how do I make the association (compute node 1, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-1, compute node 2, allocate the FIP gw address using demo-floating-ip-agent-gateway-subnet-2, etc..)?

Alternately, does someone have experience in using DVR in CLOS based networks that can provide some insight about configurations that support DVR? Or is DVR not a good solution, old school vRouting or something else is needed to provide support for FIP?