| 2015-09-02 16:47:14 |
Nischal Sheth |
description |
If the forwarding mode for a VN is l2_l3, DM allocates IP address from
each VN subnet and configures them on an IRB IFL that belongs to the
L3 VRF for the VN. This functionality was implemented via bug 1465070.
Along similar lines, if the forwarding mode for a VN is l3, DM needs to
allocate IP address from each VN subnet and configure them on a lo0
IFL that belongs to the L3 VRF for the VN. This will be useful to test
connectivity between the VRF and a VM.
Unit number for the lo0 IFL can be calculated based on the VN index.
However, instead of using the VN index directly as the unit number,
we should calculate it using a fixed offset, say 1000 + VN index. This
is to avoid conflict with lo0.0 (which is typically configured by user)
and to have some unit numbers available for users for manual config. |
If the forwarding mode for a VN is l2_l3, DM allocates IP address from
each VN subnet and configures them on an IRB IFL that belongs to the
L3 VRF for the VN. This functionality was implemented via bug 1465070.
Along similar lines, if the forwarding mode for a VN is l3, DM needs to
allocate IP address from each VN subnet and configure them on a lo0
IFL that belongs to the L3 VRF for the VN. This will be useful to test
connectivity between the VRF and a VM.
Note that the addresses for each lo0 unit must be persisted, pretty much
the same way that IRB addresses are persisted.
Unit number for the lo0 IFL can be calculated based on the VN index.
However, instead of using the VN index directly as the unit number,
we should calculate it using a fixed offset, say 1000 + VN index. This
is to avoid conflict with lo0.0 (which is typically configured by user)
and to have some unit numbers available for users for manual config. |
|
