Aerohive PoE switches vs the rest of the field

  • 1
  • Question
  • Updated 4 years ago
  • Answered
Good afternoon.
Looking to integrate and revamp our PoE access layer , was keen to test Aerohive for reasons of unified device management - not necessarily simplicity .

However, despite numerous requests and due to lack of demo units I am unable to actually test drive an Aerohive switch at present and an evaluation of all other competition is more or less complete.

Not wanting Aerohive to miss the boat on this , now resorting to the community to help with the following use case

- 8 to 12 PoE ports max per switches

- all PoE ports to have a unified tagging scheme

- Insight into traffic and mass configuration.

Would be nice to have screenshots or perhaps links to videos that I can't seem to get hold of publicly.

Thanks in advance and if you need further information on the use case - please ask.
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes

Posted 5 years ago

  • 1
Photo of Anoop Dawar

Anoop Dawar

  • 26 Posts
  • 16 Reply Likes
Hi Anjanesh

We are always delighted that customers consider us for broader networking needs. Could you let me know which region/location you are in as well as your needs - # switches, # AP's and deployment scenario? It will help me get in touch with the right internal sales folks.

Thanks,
Anoop
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
Hi Anoop,
In the UK. Educational institution and a modest 40 APs but scattered all across cities requiring beyond the horizon lldp visibility on the wired segment.
We are scoping out 15 PoE Switches at least.
Price and Management is key . In that order preferably.
We have a investment spread across Cisco ,Juniper,HP , 3Com and now we are rapidly moving to a single dashboard management for wired network.
A easy to use , cost effective solution is still elusive.

thanks for the reply.
Photo of Anoop Dawar

Anoop Dawar

  • 26 Posts
  • 16 Reply Likes
Anjanesh

I will let our sales team know.

Anoop
Photo of Aaron Storey

Aaron Storey

  • 32 Posts
  • 8 Reply Likes
I would love to see smaller port switches. In our Southern California school district we are starting to look at replacing our aging access layer network. With a majority of wireless clients and very few wired clients it is becoming less necessary to have large port density with POE, and gigabit ports. Many of our schools have 5 to 8 network cabinets that feed a limited number of classrooms. With an 8 to 12 port gigabit POE switch we could provide the needed POE and gigabit speed for Aerohive access points and VOIP phones. Perhaps even a 24 port 10/100 non POE switch that would be less expensive to provide the ability to have unified management to the rest of the network as well. I could imagine many schools will start to build their networks this way as so many of our clients especially move away from the wired network and toward wireless. In education the days of labs and desktops in classrooms is almost gone. Now it is all about the Laptop and quickly moving to the tablet devices. Most of these don't even have the option to plug into a wired network.
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
Despite the complete lack of response for demo switches .- we went ahead and brought two.
I am impressed about the excellent stonewalling methods displayed by the Aeorhive supply chain when consistently being asked to provide a loaner .
Despite boast of '100s of switches in warehouses' by distributors , none was available for a hands on trial.
Arrived within a week of the PO.
Photo of Edward Nice

Edward Nice

  • 19 Posts
  • 6 Reply Likes
Please let us know your thoughts once you get the devices up and running.
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
hi Edward,
yes of course.

Initial thoughts are positive from a 'dashboard' point of view.
The switches integrate very nicely into the hivemanager and provide an excellent insight into management and configuration consistent with the Aerohive experience.

Few things are missing which are nice to have - like toggling a PoE port .
More on these later but otherwise these seem to be a good investment which brings our wired experience consistent with the wireless layer.
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
Three month field report
- Concerns about PoE port power cycling now negated with 6.1r3 which has a ready option so.
- Easy fire and forget model of deployment
  - explanation : I do not need to assign a static IP to the switch, dhcp on the same L2 network is great and switch calls home to VHM.  No more spreadsheets .
- Needless to say , best management ,dashboard and single point of control interface which integrates with existing skillset.

Not so clear
- Fallback to CLI (only ?) should it disconnect from VHM
- A rudimentary web interface to manage ports and  vlan connectivity would be nice.

Nice to have
- Mac address filters on the switch (24 Port) in line with APs.

I have not looked at 48 port models yet.


Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Thanks for following up with your operational experience! 
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
Moving into our fourth month, the discovery process continues.

1. VLAN probe on Aerohive switches does  not work. At all.

2. Switch port type to allow 'all' vlans does not work  --->* when* --> a switch has all ports set to a single port type  consisting of a native untagged and allow all tagged vlans.

the second issue has been raised via our support channel.




Photo of Andrew MacTaggart

Andrew MacTaggart, Champ

  • 483 Posts
  • 86 Reply Likes
It seems that the logic is that since 255 is the max, that they would not be able to determine what "all" actually is. So assuming you are trunking on every single port then you would need to input you vlans you want to create. the vlan range is greater then the max
AHTTSWITCHMS#vlan
    <number>    Enter a numeric value for a VLAN ID(Range: 2-4094)
So if you do not specifically define the vlans, they do not get add to the trunk, because they don't exist.

AHTTSWITCHMS#show vlan brief
VLAN ID  VLAN Name             
---------------------------
1        VLAN1                           
34       VLAN34                          
35       VLAN35                          
42       VLAN42                          
110      VLAN110                         
403      VLAN403                         
405      VLAN405

Name: eth1/6
Switchport: enable
Port Mode: trunk
Port Mirror: disable
Port User-profile ID: 0
Static Trunking Native VLAN: 35
Static Voice VLAN: 0
Dynamic Voice VLAN: 0
Dynamic Auth VLAN: 0
Trunking VLANs Enabled:
34-35   42   110 

In the cisco world you can trunk all vlans, but you still need to create the vlans on the switch or use a vtp client and server setup. The vlans do get created just because you create a trunk.

I think the "all" is specifically for access port vlans or other port vlans to be added to a trunk link.

When I select all with no vlans created and use the cli to add the vlan to the switch, it becomes part of the trunk.

AHTTSWITCHMS#vlan 407

AHTTSWITCHMS#iint eth1/2 switchport trunk allow vlan 34 - 407

AHTTSWITCHMS#int eth1/6 switchport trunk allow  all

AHTTSWITCHMS#show int eth1/6 switchport
Name: eth1/6
Switchport: enable
Port Mode: trunk
Port Mirror: disable
Port User-profile ID: 0
Static Trunking Native VLAN: 35
Static Voice VLAN: 0
Dynamic Voice VLAN: 0
Dynamic Auth VLAN: 0
Trunking VLANs Enabled:
1    34-35   42   110  403  405  407 

Anyway it is best to just allow what vlans you need instead of add all vlans

so for example for Aerohive AP
add the management vlan, the native vlan, and the user vlans to the port
nothing more and nothing less









Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
thanks for the response - pruning of vlans is done by upstream switches so no real urge for us to fiddle with AH configs here.


Allow 'all vlans' works  - if the ports are not the same type across the board. So , this is a feature albeit slightly different from what it implies  .
Photo of Andrew MacTaggart

Andrew MacTaggart, Champ

  • 483 Posts
  • 86 Reply Likes
Just ran a vlan probe with no issues

AHTTSWITCHMS#int mgt0 dhcp-probe vlan-range 34 34
AHTTSWITCHMS#
local=DHCP server configured on local device;

DHCP server probing, use CTRL-C to stop
      34-2010(ms)
DHCP Tests performed for VLANs 34-34
Status: complete
Passed for VLANs: 34

worked from HMOP and CLI

Cheers
A
Photo of Anjanesh Babu

Anjanesh Babu

  • 68 Posts
  • 7 Reply Likes
thanks for the reply but my query was centered around the GUI and not CLI.

The general understanding  being if a feature  is  present on the GUI  then this   should be available to use regardless of how useful (or cool) it may be to get the same results using   the CLI. If it is not supported on the model  that is different matter.

This command still returns no vlans on the 2024P  though.