Let me know if this guide solves the issue for you. If not please let me know where we are missing (noting the other comment about adding device to the RADIUS as well for it's own authentication tasks). u
The guide linked by dkirsch seems to be the same document that was linked earlier.
I am using the Radiator RADIUS server, not ACS or CiscoWorks.
The authentication part works, and the RADIUS server sends back a Radius-Accept to the HSE, it seems to be that the cisco-avpair that I am sending back is wrong, and the HSE doesn't know what to do with it.
I've tried sending back "HSE:groups=HSEAdmin" in the response, and several variations, but the HSE doesn't like it.
It would be great if I could work out what the HSE expects in the reply so I can make RADIUS tell the HSE what group a user belongs to.
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...