Hi Felippe.
Great to read that it is successfully pushed. Templates were really picky on the command sequence. Maybe they relaxed this a little bit. I have not working with templates very much, but whenever I do, I need to be very precise on order of commands. Now when we have MultiEdit and NetEdit I can check the correct placement and usually have no problems.
Or maybe it was a different problem in your case. Sometimes connection to Central have it's perks.
Original Message:
Sent: Aug 14, 2024 10:25 AM
From: felippe_ro
Subject: Aruba Central - Device internal error
Hi Gorazd,
Thank you for your feedback.
I was waiting for some downtime planned for the office so I could apply the new configuration template, edited as you suggested. As I mentioned, I had no issues with the other two stacks, but I was happy to give it a try.
However, something really unusual happened a day ago, around 3:00 AM when suddenly, Aruba Central reported that the configuration was successfully pushed to the "faulty" stack:
And the audit log:
I presume I will never fully understand what happened. The good this is that the stack behaves as nothing bad had happened.
Just one of thouse curiosities, maybe...
Original Message:
Sent: Aug 07, 2024 07:08 AM
From: GorazdKikelj
Subject: Aruba Central - Device internal error
The order of commands in template is critical.
You have "ip route" command in wrong place. It need to be after "snmp" and before "ip dns" commands.
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Guru 2024
Original Message:
Sent: Jul 22, 2024 12:10 PM
From: felippe_ro
Subject: Aruba Central - Device internal error
I think you mean the "Config comparison tool", in the "per-Device" Configuration Audit:
I checked the side-by-side the "Device Running Configuration" and the "Attempted Configuration". Aparte from the long list of highlighted interfaces (the running config shows every single interface whereas as the template has range(s) of interfaces), the only two things which may lead to the error are:
- one line in the VSF configuration:
Original Message:
Sent: Jul 22, 2024 10:14 AM
From: Herman Robers
Subject: Aruba Central - Device internal error
I don't have an out of sync device, but remember that there is a side-by-side comparison where you can see (only) the differences, or with a markup on the different lines. Don't you have that??
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 22, 2024 07:15 AM
From: felippe_ro
Subject: Aruba Central - Device internal error
Hi Herman,
Thank you for your feedback.
Indeed, the logging shows that the stack lost its connectivity to Central (on the mgmt VRF it happened when I disconnected all the MGMT interfaces from the old network; this way I did the initial configuration and I kept a "back door" in case something was going wrong on VLAN 1).
In any case, the switches are still connected to Central using the default VRF (they show "online" in the list and I can use the Aruba Central console connection to this switch to make changes (after enabling aruba-central support mode).
Here is the output of the "Configuration Status" for the "Not in Sync Device":
And this is the current running configuration taken from the switch:
All the switches are on the latest recommended firmware (ML 10.13.1010)
Original Message:
Sent: Jul 22, 2024 05:54 AM
From: Herman Robers
Subject: Aruba Central - Device internal error
The logging suggests that the switch cannot reach Central anymore (through the default VRF). Could it be that your change blocked access to Central? Or another network change (firewall?) blocked access from your switch to central?
It seems that you use template based configuration. Does the Configuration Audit (go in your config group; select switches, configuration, Configuration Audit tab) explain more about what is out of sync or what commands provide errors?
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 22, 2024 03:22 AM
From: felippe_ro
Subject: Aruba Central - Device internal error
Hello,
Last week I have rolled out five new 6200F switches for one of our customers. There are two VSF stacks of two switches each and one stand-alone switch. All the configuration is done via a template and a variable configuration file; everything went fine up to a point when, suddenly, one of the stacks went out of sync.
After each change I make to the template or after uploading a new variable configuration file, I get the error shown below.
Clicking the three dots doesn't reveal much:
I ahve also checked the events - nothing relevant there.
And here is the log from the switch console:
The error first showed on the 17/07.
I should highlight that the configuration template applies to both stacks and to the stand-alone switch. The other stack and the stand alone switch are "In sync" with no issues.
I Have opened a support case with Aruba TAC and they suggested to create a new, test group and move the "faulty" stack there, to see if the issue persists.
Has anyone else encountered this error?