I know the forum is full of posts about problems with the Unleashed ICX switch management feature, I apologize for creating yet another one. I wasn't able to find an existing one that quite fit the problem I'm having, though there are so many, maybe I missed one...
Unleashed 200.17.7.0.152 will not connect to an ICX7550-48ZP firmware 08.0.95m. This switch was working fine with Unleashed for a few years, until I replaced the master AP R850 with an R770. Since then, Unleashed will not connect to the switch. Logs indicate the issue is an authentication failure, incorrect password, but I am able to ssh into the switch using the Unleashed credentials for password authentication just fine. I haven't seen any other problems with the network or Unleashed since replacing the AP.
Unleashed logs
May 1 00:05:04 unleashed : Mef3002S0D0 pid=6526[32499], icxd_icx_monitor():ICXD: ICX[id=1]: Stop monitoring.
May 1 00:05:04 unleashed : Mef3002S0D0 pid=6526[32499], icxd_state_loop():ICXD: ICX[id=1]: 192.168.0.247: icx-do-logout done, result is [OK]
May 1 00:05:04 unleashed : Mef3002S0D0 pid=6526[32499], icxd_state_loop():ICXD: ICX[id=1]: 192.168.0.247: NEW_STATE=[pending-invalid-account], Pending...
May 1 00:05:04 unleashed : Mef3002S0D0 pid=6526[32499], icxd_state_loop():ICXD: ICX[id=1]: 192.168.0.247: icx-do-login done, result is [FAIL_PASSWORD_INCORRECT]
May 1 00:05:04 unleashed sys_wrapper: icx_do_login():ICXD: ICX[id=1]: 192.168.0.247: login failure, kill it.
May 1 00:05:04 unleashed sys_wrapper: icx_do_login():ICXD: ICX[id=1]: 192.168.0.247: lastline "admin@192.168.0.247's password: ", expect end with ">" or "#".
ICX Switch logs
May 1 00:04:54:I:Security: SSH access by user admin from src IP 192.168.0.237 rejected, 3 attempt(s)
May 1 00:04:34:I:Security: SSH access by user super from src IP 192.168.0.237 rejected, 1 attempt(s)
May 1 00:04:24:I:Security: SSH access by user super from src IP 192.168.0.237 rejected, 3 attempt(s)
Things I've tried...
- Manually remove and re-add the switch in Unleashed. No effect.
- Wait for Unleashed to discover the switch via LLDP and manually "Approve". No effect.
- Enable automatic switch approval, wait for unleashed to discover it. No effect.
- On the switch, manually configure the default user state that Unleashed so desperately hopes for. Create username `super` password `unleashed`, and delete all other switch users. Unleashed successfully logs in as `super`, and it creates a user matching the Unleashed `admin` user. I'm able to ssh into the switch as the `admin` user that Unleashed created using the expected password. But Unleashed itself cannot authenticate with the `admin` user it created. Same error as shown in logs above.
The nuclear option of factory resetting the switch is not something I want to do, nor should I need to do.
