I need your expert suggestion on how do i get rid of the fabric merging situation on my Fabrics.Below is a short description of my environment..
We have 2 Fabrics in our environment namely FAB A and FAB B, we have been running on this for the past couple of years now, Last weekend i noticed on my FM that the 2 fabrics have merged.. Under the FM view i could only see Fabric A having all the zonesets discovered for FAB B as well, can't really firgure out what went wrong..whenever i try to dicover fabric B on FM it says it has discovered as FAB A.
The VSANs haven't necessarily merged. I think what's going on is there is some path between all your switches. Maybe a transit VSAN or VSAN1 (I think down just means no active zoneset so it might still merge). So basically when you discovered Fab A it also found Fab B.
An easy way to check this would be to click on KIM_EMC_VSAN_20_A. Are only switches you expect to see listed there? Then when you click on a B fabric is it correct?
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...