Cisco is recommending l3 mode for vem and vsm communication.
However, we are using erspan. If we use l3 mode as cisco's recommendation, which means we have to use the same vmkernal interface for our ERSPAN traffic and VEM & VSM communication which it is not really great for us.
Security guy raise their concern about mix of the two kind of traffic (ERSPAN traffic and VEM & VSM communication);
AND the erspan and vsm&vem traffic possibly will have different next-hop because erpsan and vsm are in different domain
Any idea from cisco about the new l3 mode recommendation for 1000v
Can you try creating a new vmk port for management and then putting that into a separate vethernet port profile with l3 control?
This way you mgmt interface can be used for maanagement connectivity and you can have it in its own port profile.
The traffic will be on separate vmk but on the same vlan. Is this what you are looking for?
You can still also run layer 2 mode with version 5.1 if you would like. It's just easier with Layer 3 because the theory is if you can ping the host then the module will be online. You don't have to worry about the additional vlans and layer 2 connectivity you may need to troubleshoot.
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...