Mailing List Archive

Collecting information from Aruba wireless switches
I'm looking at collecting configs from Aruba wireless switches, which
pretty closely emulates Cisco's interface, though there are enough
differences that the collector will not succeed when treating it as a
cisco device. Has anyone worked out the differences yet so as to
collect information from an Aruba wireless switch?

Just for reference, here are the errors that I currently get from a run
with a cisco device type.

aruba-fairchild2-wsw.dartmouth.edu clogin error: Error: TIMEOUT reached
aruba-fairchild2-wsw.dartmouth.edu: missed cmd(s): write term,show
vlan,show running-config
aruba-fairchild2-wsw.dartmouth.edu: End of run not found

Thanks for any help.

-Paul Schmidt
Dartmouth College
Collecting information from Aruba wireless switches [ In reply to ]
Fri, Jul 29, 2005 at 10:39:51AM -0400, Paul Schmidt:
> I'm looking at collecting configs from Aruba wireless switches, which
> pretty closely emulates Cisco's interface, though there are enough
> differences that the collector will not succeed when treating it as a
> cisco device. Has anyone worked out the differences yet so as to
> collect information from an Aruba wireless switch?
>
> Just for reference, here are the errors that I currently get from a run
> with a cisco device type.
>
> aruba-fairchild2-wsw.dartmouth.edu clogin error: Error: TIMEOUT reached
> aruba-fairchild2-wsw.dartmouth.edu: missed cmd(s): write term,show
> vlan,show running-config
> aruba-fairchild2-wsw.dartmouth.edu: End of run not found

It is easier to begin with the expect/login script. Get it working with
and without -c 'cmd', then worry about the rancid script.