Sample Configuration for Mellanox (HPE StoreFabric SN2100M) Switches

Switch automation script configures the following in the starter kit.

  • Management traffic and data traffic are separated by VRF.
    • Management traffic

      1. Management traffic is part of mgmt-vrf.

      2. PXE, CLM, BLS, OAM, and CAN are part of management network.

      3. PXE, CLM, and BLS IP interface are configured on leaf switch, whereas OAM and CAN are customer-provided NW which will be configured on Customer Infra Switches.

    • Data traffic

      1. Data traffic is part of data-vrf.

      2. Provider VLAN is port of data traffic, which carries the VNF traffic.

    In this example, the provider network is configured. Management VRF and Data VRF have to be configured across all the VTEP. This section provides information about L3 and L2 VNI.

    • There is a one-to-one mapping between a layer 3 VNI and a tenant (VRF).

    • The VRF to layer 3 VNI mapping has to be consistent across all VTEPs. The layer 3 VNI has to be provisioned by the operator.

    • Layer 3 VNI and layer 2 VNI cannot share the same number space; that is, you cannot have vlan10 and vxlan10 for example. Otherwise, the layer 2 VNI does not get created.

    • In an MLAG configuration, the SVI used for the layer 3 VNI cannot be part of the bridge. This ensures that traffic tagged with that VLAN ID is not forwarded on the peer link or other trunks.
      NOTE:

      • Vxlan104001 is the L3 Routed VNI which is used to enable Symmetric routing. Configure this VNI on all the VTEPs.

      • clag vxlan-anycast-ip is used when MLAG is used with VxLAN. This way, other VTEPs sees the MLAG pair as a single entity.

  • VLANs and VRF id USED for sample configuration
    VRF   VLAN
    Management VRF mgmt-vrf PXE, CLM, BLS, OAM and CAN (301-305)
    Data VRF data-vrf Provider VLAN (350-354)
Sample configurations for: