Network Management

Reply
Highlighted
Occasional Contributor I

Failed upgrade from 8.2.4.1 to 8.2.5.1

Upgrade package AMP-8.2.5.1-x86_64-cvs.tar.gz was not found in local cache.

Checking iptables.


Checking the database schema.

*********************************************************
Run fix_missing_indices to fix the missing indices.
*********************************************************

Upgrade aborted!

Restarting menu

Hit enter to continue

I am running AMP on 8.2.4.1 and trying to upgrade to 8.2.5.1.

The problem is, I don't have access to run "fix_missing_indices" as far as I can tell since shell access was changed in 8.2.4.1. Is there a method to run this still in 8.2.4.1 or do I need to contact TAC?

Thanks!

Occasional Contributor I

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

Contacting TAC to resolve. It looks like there is an option in the new version to allow entering commands like this. 

"The AMP CLI allows you to run the Enter commands described in Table 2. These commands are available when selecting 11 from the CLI."

New Contributor

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

Nordman-

I'm encountering this EXACT same issue (Verbatim) when upgrading from current 8.2.4.1--->8.2.5.1.  Where did TAC tell you in this new (limited) CLI to select Option 11?  At the root of the new 8.4.4.1 CLI the only option goes up to 10 as shown belowCapture.JPG

Occasional Contributor I

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

I called TAC and they were able to remote in and fix it. 

I suggest opening a ticket. I couldn't fix it myself in this version unfortunetly. 

 

In 8.2.5.1 there is an option 11 that lets you input the commands. 

8.2.4.1 the only solution is to call TAC. 

New Contributor

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

So a limitation of the current AirWave 8.2.4.1 code. Gotcha. I'm sure they have access to the regular Linux Kernel via a backdoor as the platform is still there. Thanks!  I'll log a case and let you know how it goes.  I'd stay on 8.2.4.1 for now but the annoying lack of modifying system time/timezone in this 8.2.4.1 release is preventing me from having correct timestamps in the system logs!  Apparently 8.2.5.x enables setting time/timezone in the CLI.

Moderator

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

Actually, the 'enter commands' option doesn't let you run scripts.  It lets you currently perform some routine data collection that support might ask when debugging.  The list of options will see some additions in 8.2.6.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

Good to know. I just made the assumption. I hadn't needed to touch my servers since the upgrade. 

Does that mean the eventual plan is to have all the scripts put as options within the menu? Or is that being pulled back as only TAC accsible?

Moderator

Re: Failed upgrade from 8.2.4.1 to 8.2.5.1

Any existing script requirement will have to be handled in a TAC case.  Though as TAC cases have progressed, the enter cmds feature set was introduced to re-add some of the functionality lost by AMPCLI, so we might see something with the scripts in the future.  8.2.5.1 is the initial offering, and we've got plans to add more to the list in 8.2.6.  So perhaps we might see the scripts come back, but it's not on the roadmap yet.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: