I am designing an environment that would need two ACE contexts (DMZ and HotDMZ). My plan is to host databases on HotDMZ while hosting the web apps on the other context. I have defined 3 VLANs (11(outside),192(Apps farm) and 195 (Inter-Context vlan)) on the DMZ context. I have also defined vlan 195 on the HotDMZ context and intend to use that as the only link between HOT and HotDMZ contexts. My problem is how do I get the inter-context vlans to talk to each other? Do I need to assign a physical interface to the inter-Context vlan or I can configure them to talk using the back plane of the ACE appliance?
In short, how do I get Inter-Context vlans to talk to each other?
Context can not talk directly to each other on the ACE. If they need to talk to each other, they must leave the ACE and route via SVI, routed ported, etc and then come back into the other context. Think of each context as a completely different piece of hardware and how you would route to/from that device.
I created a shared vlan between the two contexts and can now get the contexts to ping each other. My problem now is that I can not ping across the shared vlan when I do so on the two contexts in the same appliance but I successfully ping across the shared vlan when directed towards a context on the failover ACE.
I have the exact same issue. Is there any fix for this? I could understand the answer would be a routed SVI, etc, if the contexts were in different VLANs but I am using a shared VLAN between contexts. I see the same problem as the original poster:
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...
RBAC users like firstname.lastname@example.org may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...