Network Management

Reply
Moderator

Re: AirWave 8.2.4 NO CLI


@Jafa1995 wrote:

We would like to configure NIC bonding but it seems the only method is to request TAC assistance.


In 8.2.6.1, NIC bonding can be configured from the AMPCLI -> Enter Commands:

 

$ help ether
ethernet_bonding <ip> <netmask> <gateway>
Enable ethernet bonding of two network interfaces.
If just 'ethernet_bonding' you will be prompted for the 3 IP addresses.

 

You can only bond 1 pair.

 


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

Re: AirWave 8.2.4 NO CLI

Is there any update to this on 8.2.6? I have over 20k alerts that came in before I was able to delete the default alert rule. I used to be able to clean these up with alert_cleanup.pl but am now stuck in the sandbox.

Highlighted
Moderator

Re: AirWave 8.2.4 NO CLI

@gosse

 

Open a support case, support will get into the support acct and run the script.


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

Re: AirWave 8.2.4 NO CLI

Maybe forbidden, certainly not supported, but I really need to run ping and traceroute.  The bootloader is locked with a password, so I booted the airwave VM from CentOS-6 install meda, entered rescue mode, and let it mount the Airwave filesystem.  I edited /etc/passwd and /etc/shadow, basically copied root's lines but changed the username to admin and the shell to a real shell, but no other fields (uid still 0).  Booted back to Airwave, log in as "admin" with the same password as root had before, and you have a shell.  I'm not sure if this will survive an upgrade (vs. just changing root's shell), but for now it got me what I needed.

 

This wouldn't be needed if they'd provide even a non-root shell account with access to basic tools.

Moderator

Re: AirWave 8.2.4 NO CLI

@msturtz

 

ping and traceroute are allowed -> but from the 'Enter Commands' menu.  Those tools are outlined a bit more in this airhead tip.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Guest Blogger

Re: AirWave 8.2.4 NO CLI

Still no update on how to fix the .ssh/know_hosts issue???

 

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
06:e2:38:40:27:96:f5:fd:3b:0f:8a:9a:9a:2a:0b:1c.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.

@rene_booches | AMFX #26, ACMX #438, ACCX #725, ACDX #760, CCNP R&S, CEH | Co-owner/Solution Specialist@4IP / blog owner@booches.nl
Moderator

Re: AirWave 8.2.4 NO CLI

The feature to zeroize ssh keys is still in the backlog.  This currently requires a TAC case to make changes to sshkeys.


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: