We are moving to a new version of ArubaOS (from version 6 to 8). Our current environment is getting backed up via Cattools and works just fine. When we try to accomplish same backups on ArubaOS 8, it does not work. (We are running the latest version of Cattools - 3.11.5)
In the 6.X Aruba environment we use device.send commands to allow us to backup the flash and get the current running config. We then copy if off with via tftp. It is basically doing these commands:
copy running-config tftp: $IP_address $filename
copy flash: flashbackup.tar.gz tftp: $IP_address flashbackup.tar.gz
If you use device.backup.running config -> it does not get the entire configuration without using the command show configuration effective . Just one of the many oddities of ArubaOS 8 (?). (To clarify, you get the basic config but it is NOT complete. Aruba's new method I guess.)
And if we try to use: device.send commands it also does not work.
Taking the cli commands entered directly into Cattools works when you ssh to the controller and enter them. But they fail through the automated task in Cattools. I Tried debug but it did not shed any light on to the issue, or I'm just not reading it correctly. It appears to login ok but fails to complete any of the tasks.
The debug file does list:
<R-11:54:41 AM>backup flash
^ % Invalid input detected at '^' marker.(ARUBA-NODE) [mynode] #
(But I'm not sure what this really means.)
Has anyone gotten this to work on OS 8? If so... How? Am I missing something obvious?
Since there seems to be no takers... lets try this:
Has anyone gotten CatTools ver 3.11 to work with an Aruba OS 188.8.131.52 Controller?
Seeing mixed results, with very little actually working, but most things do not.
In particular: Device.CLI.Send commands
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.