"Local device is not AED-Capable" in "show otv site"?
I have two site doing unicast OTV. I just configured one site (config below). Understand there's no adjacency at the moment, but why in "show otv site", local device is not AED-capable? The site has only one Edge device, so shouldn't it be the AED for every extended VLAN?
Here is "show otv site" and "show otv", and the OTV configs on the device. It's a OTV VDC on Nexus 7k. Po1 is the internal interface. Po2 is the Join interface. The VDC is EIGRP with the Core VDC over the Join interface.
OTV-1# sh otv site
Dual Adjacency State Description Full - Both site and overlay adjacency up Partial - Either site/overlay adjacency down Down - Both adjacencies are down (Neighbor is down/unreachable) - Site-ID mismatch detected
Local Edge Device Information: Hostname OTV-1 System-ID e4c7.2202.42c4 Site-Identifier 0222.0222.0222 Site-VLAN 2 State is Up
Site Information for Overlay1:
Local device is not AED-Capable (No Overlay Remote Adjacency up) Neighbor Edge Devices in Site: 0
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...