Trying to setup IDM and failing

[Stephen_Stormon]

We have Extreme Management Console and ExtremeControl and we want to start off by just collecting information on what all is connected to the network, but not enforcing any policies at this point. The first step is to select the device, right-click on it, click Tasks -> Access Control -> Identity Management - Configuration, correct?

We then changed the target server IP address setting to the IP of the NAC server, changed the target server type to NAC, but then things fall apart at the username and PW. We tried using the root account that was created when NAC was installed, but that doesn't work. Looking on the switch, it shows:

Slot-2 Summit-CV-Desktops.9 # show xml-notification statistics
Target Name : nac-target_172.22.1.94
Server URL : https://172.22.1.94:8443/axis/services/event
Server Queue Size : 100
Enabled : yes
Connection Status : fail
Events Received : 3
Connection Failures : 2
Events Sent Success : 0
Events Sent Failed : 3
Events Dropped : 0

Going to that link brings up a login prompt, but the root account credentials on the NAC don't work to login. I'm guessing that is where the problem is, but I don't know at this point.

[Stephen_Stormon]

Yes, mine looks like your setup:

[TylerMarcotte]

Is the IP in your nac-target the NAC IP address or the XMC IP Address? If it's the NAC, try changing it to the XMC IP.

[TylerMarcotte]

Ok, here's a screenshot of what it should look like on the CLI of the switch. The encrypted-auth is the encrypted password. If you already had most of it working with the script from XMC, you should just be able to change the VR on the first XML notification line.

[Stephen_Stormon]

I was following what the docs said and using the IP of the NAC server. Now after dismantling the configs on one switch, and trying the IP of the XMC server (it wasn't able to connect), I have tried going back to my original config and now that isn't connecting. Must be Friday.

[Stephen_Stormon]

Sadly, I'm still missing a piece of the puzzle. Figured out that the script that runs via XMC sets things up using VR-Mgmt, but we use VR-Default. Changed that setting and now the switches are connected to the server, but they aren't showing up in the "End Systems" section.