Monitoring, Management & Location Tracking

Issue: Configuring AMP to communicate with devices using SSHv2

http://community.arubanetworks.com/t5/tkb/articleeditorpage/tkb-id/MonitoringManagementLocationTracking/template-id/freeformIn AirWave 7.1.3, there are 2.5 methods to get AirWave to use SSHv2 for devices where AirWave uses SSHv1 out of the box.

Methods 1 and 1.5 both involve manipulating the value ssh_version in the ap_groups table. setting this value to 2 (for SSHv2) will enable SSHv2 communication for all devices in the ap_groups modified.

Method 1: Direct DB manipulation

example:
airwave=> SELECT ssh_version from ap_group where id = 5;
ssh_version
-------------
1
(1 row)

airwave=> UPDATE ap_group SET ssh_version = 2 where id = 5;
UPDATE 1
airwave=> SELECT ssh_version from ap_group where id = 5;
ssh_version
-------------
2
(1 row)


Method 1.5: Under Group->Basic Enable all device configurations and modify Cisco IOS devices to use SSH and SSHv2. This sets the ssh_version flag for the entire group configuration (which in fact, could break some devices that are expecting SSHv1). You can reset the all devices flag back and the change will be retained.

Method 2: You can add an override in the individual device Sshcli.pm by adding sub ssh_version { 2 }

Example, for a Symbol 51x1 device:
/root/svn/mercury/lib/perl/Mercury/AP/Symbol/Symbol51N1/SshCLI.pm

# Copyright (c) 2001-2010, Aruba Networks, Inc.
# This material contains trade secrets and confidential information of Aruba
# Networks, Inc.
# Any use, reproduction, disclosure or dissemination is strictly prohibited
# without the explicit written permission of Aruba Networks, Inc.
# All rights reserved.

use strict;
use warnings;
no warnings 'once';
package Mercury::AP::Symbol::Symbol51N1::SshCLI;
use base qw(Mercury::CLI::SSH);

sub ssh_version { 2 }
sub telnet_prompt { '/.*?(-- ?More ?--.*|\(yes\/no\): |>)$/i' }
sub terminal_length { 100 }

1;