Security

Wondering if somebody has run into similar issues. We received a couple of brand new N3001 appliances running 6.11. I was able to configure some appliances with mgmt IP addresses, no issues. However, two appliances are having a hard time to keep the IP address after reboots. If tried, system network-reset, factory reset. Reset cluster database. I've tried to configure the most ip address via the initial configuration prompt and with configure ip mgmt, the commands run successfully with noeerors. However, when I system restart the bow, it boots up without mgmt ip address. I'm able to ping the mgmt ip address when it is asigned, but it disappears after reboot. I've read this was a common issue with hyper-v VMs. Any ideas?

Hi Jorge,

This is a known-no-known-issue, but Aruba's own defect database strongly recommends moving all appliances to 6.11.7 or later (ideally 6.11.9 + HF2 or 6.12.1+) to pick up stability fixes. After patching, reapply your mgmt IP via the CLI, run system refresh-network, save and reboot (This solution worked for systems running on Hyper-V as you mentioned but could be worth a try). If it still doesn't persist, you'll need a support ticket so TAC can dig into the hardware logs.

Take a look at these links for reference
New Known Issues in the 6.11.0 Release

Vigan