We've currently a data center based on Layer 2 with many inter building links blocked by STP. To simplify a little bit the layer 2 topology (and improve inter-building link usage) i would like to introduce EoMPLS inside my Data Center core.
Is that a good idea ? or something to rapidly forget ?
i beleive that if you want to increase your core network speed and make sure it is more resiliant , also to take more advantage of load balancing , that it would be alot simple to move from a L2 core to a L3 one.
Dependent on how big your core is , it will improve responce time and make routing much more efficent.
EoMPLS is overkill for the goal presented. Basically you would introduce Layer3 in the core (needed for MPLS) and then use MPLS to make the core look like Layer2 ...
More simple approaches:
Either tune your STP (or better use Rapid Per VLAN STP or MVST) to get some load balancing and also convergence speed.
Or convert to a L3 core - i.e. IP routed. The latter step might require IP readdressing, which can be a major pain. On the other hand you then have separated broadcast (and failure) domains, nice load balancing, fast convergence and no more big STP hassle.
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...