Note that "flow permanent" should be used with some degree of caution. Flow's which are not taken down cleanly (FIN,ACK,ACK) will sit in memory forever as they are not subject to garbage collection and are "permanent", eventually this can consume all the resources and lead to failure.
The workaround for this is to use the cmd scheduler to remove and re-apply the associated flow perm command on some interval.
if you have a CSS 2ng generation you can control the timeout per content rule with the command 'flow-timeout-multiplier'
You should use a timeout solution first before going for the permanent port solution which could at long term have negative effect [if you run out of resources - called FCB - you will process switch the traffic and reduce badly the performance].
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 email@example.com 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...