Objective 5.3: Configure and Manage Layer 2 Bridging

  • Determine HA for L2 Bridging
    • See Design Guid p141
    • If HA is enabled on the Logical Router and primary NSX Edge vm goes down bridge is automatically moved to host with secondary vm
    • VLAN must have been configured on the edge host that has the secondary edge vm
    • To enable HA for L2 bridging you need to enable HA for the DLR it is attached to
    • NSX edge is compatible with vSphere HA
    • If vSphere HA is not active, the standby NSX Edge HA pair will survive the single failover

 

  • Activating
  • Click Network & Security and then click NSX Edges
    • Double click Edge
    • Manage then click bridging
    • Click add icon
  • Type name for bridge
  • Select logical switch you want to create a bridge for
  • Select distributed virtual port group that you want to bridge the logical switch to
  • Creating a L2 bridge between logical switch and VLAN
    • enables you to migrate workloads to physical device with no impact on IP addresses
  • Logical network can levearge
    • physical gw
    • access existing physical network and security resources
  • by bridging logical switch broadcast domain to vlan broadcast domain
  • L2 bridge runs on host that has the NSX edge DLR
  • L2 bridge instance maps to a single VLAN
    • can have multiple bridges
  • Before 6.2 DLR could not be used as a gw for devices connected to bridge
    • had to use gw of existing vlan or via NSX edge

 

  • Hardware vs Software Bridging
    • It is possible to extend VXLAN logical switch to compatible hardware that acts as L2 gw and bridges logical switch with a VLAN network
    • the device performing this function is managed from NSX via OVSDB protocol while control plan is till managed by BSX controllers
    • L2 gw integration with NSX
    • Think on ease of deployment in software
    • VMware and hw vendor support
    • robustness of solution

 

<VCP6-NV6.2

plasebikan