FUJITSU PSWITCH
User’s Guide
118
December/2018
This feature is configurable through CLI.
3.1.8.4.1.
Switch Overlay Mode
A DCVPN-capable switch can support either VXLAN or NVGRE, or both. On the
switches that support both types, only one can be configured at a time (to prevent
contention for hardware resources). The switch must be configured with the
preferred overlay type before DCVPNs of the preferred type are created. Only
DCVPNs matching the configured overlay type can be created. To configure DCVPNs
of the other overlay type, the preferred overlay type configuration must be
changed. When the preferred overlay type on the switch is reset or disabled, the
entire existing configuration of the disabled overlay type is cleared from the
running configuration; i.e., all DCVPN configurations is removed for that type.
3.1.8.4.2.
VTEP to VN Association
The operator must configure switches that are to serve as DCVPN gateways. A
gateway may serve one or more DCVPNs. For each DCVPN, the operator specifies
the virtual network ID (VNID), the type of network (VXLAN or NVGRE), and a
method for identifying which incoming native packets belong to the VPN. The
ingress VLAN ID can be used as this classifier. Only one VLAN ID can be associated
with a specific VNID on a given router. However, the VLAN ID used has no
significance beyond that router, and so the same ID can be used on other routers.
In this case the number of tenant networks is not limited to VLAN ID space (i.e.,
4096). All ingress ports that are members of specified VLAN ID are treated as
access ports for the VPN identified by VNID. This defines the access port set for the
specified VPN. The access port set for the DCVPN can be altered by updating the
VLAN membership configuration. All incoming VLAN traffic is translated to virtual
network traffic identified by VNID. A VLAN ID that is already used or configured for
routing is not allowed to be configured as an access VLAN for DCVPN.
A source IP address (local VTEP) must be specified for each configured DCVPN. The
valid source IP interface is either a loopback interface or a routing interface
(port-based or VLAN-based) on the router. It is recommended that a loopback
interface be dedicated for DCVPN gateway purposes and configured with the
intended source IP configuration before associating it with any DCVPN. If the
configured source IP interface is down or has no IP address, all remote VTEPs in the
VPN are considered unreachable. No traffic flows to the remote VTEPs.
N
ote that the configured source IP address must correspond to an IP address
configured on each remote VTEP. Otherwise, the remote VTEPs will discard the
gateway's packets.
I