Network Management

Hi All,

 

I'm just playing around with Airwave and I'm having issues adding a Aruba S2500 switch... Can anyone point me in the right direction please?

 

I've tried adding the device like I would a controller and have tripple checked that the community, IP, ports, etc are correct but I'm still getting SNMP Get failed messages..

 

Airwave 8.0.0

Switch AOS 7.2.2

 

Cheers

James

Should be nothing special  James.  I've got 8.0 monitoring switches without problem.    Sounds as though you've done the basic troubleshooting; checking IP and SNMP community string.

 

Can you try to do an SNMP Walk from AirWave?

SNMP walk is failing like so... Not sure if I'm using the correct syntax/switch at the end...

 

[root@localhost mercury]# s2w 192.168.254.249 aruba .1
Timeout: No Response from 192.168.254.249

 

and I'm using v2 as you'll see..

 

I'm no Airwave expert by the way..... Here's what I've done to attempt to add the switch...

 

On Airwave:

Added a new device via Device Setup > Add > Aruba Device > Add. Added the IP of the switch and set the SNMP community to aruba.

 

On the switch: 

(S2500-24P-1) (config) #snmp-server community aruba

(S2500-24P-1) (config) #snmp-server host 192.168.254.9 version 2c aruba
(S2500-24P-1) (config) #write me

Airwave and the switch are on the same VLAN.. In fact Airwave is patched into the switch.

 

Cheers

James

...also are you doing v2 or v3?

Take a look at this doc:

 

http://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=14108

Hi Tim, I saw that 70 page document.. It could be more useful... 

 

In particular this bit stands out..

 

Minimum Configuration
AMP will be able to communicate with your MAS device if you configure the switch using the QuickStart Wizard from
the CLI.

 

So if I didn't configure it using the cli quickstart wizard it wont work?

 

I'm still none the wiser if I should use SNMP v2 or 3? Or what I've done wrong...

I would use v2c just to see if you can get it up and running, then potentially move to v3 for security reasons.

I've been using v2 as I described but have encountered issues....

 

Think I'll speak to TAC.

James,
There was an issue in 7.2 (can't recall off the top of my head which release it was resolved in) where SNMP may not respond due to a bug. Try restarting the process then re-running the SNMP walk.

process restart snmpd

Best regards,

Madani

Hey, thanks for the tip. I tried that but still no luck doing SNMP walk..

 

Also when running NMAP from Airwave agains the switch should it show UDP 161 as open??

Does your switch multiple IPs?  Are you hitting the switch ip (controller-ip in config)?

 

show switch ip

Only 1 IP..

 

(S2500-24P-1) #show switch ip

Switch IP Address: 192.168.254.249

Switch IP is configured to be Vlan Interface: 254

 

Also I upgrade the switch to 7.3.2.0 as there was a mention of SNMP issues with a version on 7.2, still getting SNMP get failed.

 

I'll continue to investigate for a bit.. It's the last day of my current job but I'd kinda like to get this working! 

jrwhitehead,

 

If you have root access to airwave attempt to execute the following:

 

s2w <ip address of switch> <community string> wlsxUserTable –On

 That will see if Airwave even has connectivity to the switch.  If you get an error, that might give you a clue what is going on.

James,

The switch and Airwave can ping each other right?

 

I saw your command snippet for SNMP, that should be all you need but just in case can you private message me your config?

 

M.

Hi Colin,

 

The s2w fails..

 

[root@localhost mercury]# s2w 192.168.254.249 aruba wlsxUserTable –On
Timeout: No Response from 192.168.254.249

 

There is network connectivity between Airwave and the switch. The management IP are on the same VLAN and Airwave is patched into an access port on that VLAN on the switch in question..

 

Will message my config to you madjali.

 

Cheers

James

 

 

James,

Reviewing your config...this should not be there:

 

no snmp-server

 

Re-enable that.

 

Best regards,

 

Madani

Ahh! That'll be it then!

Thanks.