I get "snmp get failed" when I add the 1920s switches with HP Officeconnect type in Airwave, and the device shows "status down", even though it's up through ICMP. Is the 1920s supported, and if not can I add the base OID somewhere so it can be recognized?
If it is supported, could there be something I am not be configuring right? I created a community string and community group on the 1920s and configured the same in Airwave for this device.
I had a similar problem but using iMC with the new 1920S switches. It wasn't recognised by the system so I had to manually create a new switch model type etc. The OID I used was 188.8.131.52.184.108.40.206.220.127.116.11 and SNMP V2c works with it. This is for the small 8 port gig PoE+ version (JL383A) that we have. There was never an issue with the previous ones but I guess that as these are very new, the developers have still to catch up.
Hope this helps.
Thank you for your response Carrick,
I've tried to look for a similar functionality in Airwave where you can add a base OID for a new switch, but I can't find it. I suppose that this should be supported, because it's polling for standard SNMP strings and only the base IOD would change with the switch model. Anybody knows if it's supported or how to do that in Airwave?
I just tried with a 1920 (non-S) and on that, I had to switch the SNMP version to 2c in the WebUI where it was set by default to SNMP3 only. Then suddenly Airwave could reach the switch and pull it in.
In my lab, I tried to do an snmpwalk on the switch, which did not respond first, but did work after enabling SNMPv2:
% snmpwalk -v2c -c LabCommunity1 192.168.32.8
iso.18.104.22.168.22.214.171.124 = STRING: "1920-8G Switch Software Version 5.20.99, Release 1118
Copyright(c)2010-2017 Hewlett Packard Enterprise Development LP"
iso.126.96.36.199.188.8.131.52 = OID: iso.184.108.40.206.1.25506.11.1.162
It seems that the 1920S has different firmware, but it may make sense to double-check that SNMP is working. Please note that the OfficeConnect series is not officially supported by Airwave according to the Supported Infrastructure Devices guide, but my 1920 and devices connected to it even shows up in the topology view since Airwave 8.2.5.
Thank you for your response.
I was able to get the 1920s to come up today. I added it as a Universal Network Device. I had an issue on the 1920s SNMP configuration.
The SNMP configuration on the 1920s is different from that of the 1920. My community view when I created the community string was not mathing a community view entry with permissions. You either have to create one or use Default. The switch came up as soon as I fixed that. However, I am not seeing neighbors, and the Topology is empty. There are some 1920 (non S) and 1910 which are on the same Airwave but I can't see LLDP neighbors or the topology. I'm wondering if there's something I am missing.
It could be that on the 1920S the LLDP tables are not read correctly. On my 1920 it didn't work before but started when I upgraded Airwave to 8.2.5.
First prerequisite is that you need to see your other switch in the Neighbors:
And I think I added mine as an HPE OfficeConnect device. If it doesn't show neighbors, Airwave cannot make a topology.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.