AP 390 Dual uplink connectivity modes

Hi Mike

Curious about the link aggregation method.

I have aggregated AP 370 to cisco switch and although both ports are active and traffic is being load balanced across the interfaces from the AP, the cisco port channel indicates that it is down.

I assume that maybe there is a Aerohive proprietary mechanism at play here.
the input packets are not evenly allocated

not that link aggregation is needed for the AP370, but I wanted to see what would happen.

interface Port-channel1
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 150
 switchport mode trunk
 switchport nonegotiate
!
interface GigabitEthernet1/0/13
 description link aggregate
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 150
 switchport mode trunk
 switchport nonegotiate
 power inline never
 channel-group 1 mode active
!        
interface GigabitEthernet1/0/14
 description link aggregate
 switchport trunk encapsulation dot1q
 switchport trunk native vlan 150
 switchport mode trunk
 switchport nonegotiate
 power inline never
 channel-group 1 mode active
! 

Port-channel1 is down, line protocol is down (notconnect)

GigabitEthernet1/0/13 is up, line protocol is up (connected)
13 packets input
2975718 packets output

GigabitEthernet1/0/14 is up, line protocol is up (connected)
140594 packets input
2983450 packets output

The CAM table indicates that the Aerohive MAC addresses are only learned on one port, int gig 1/0/14

I will most likely use redundant links for the 370 APs, but was curious what made it tick.

Just to add a bit more, I changed the ethernet mode to redundant.
I unplugged the primary and the fail over was seamless
however when I plugged the primary interface in, I was disconnected from the wifi1 interface.
Log was generated
Device ETSAC:  access interface wifi1 channel power changed: channel 0, transmit power 10 dBm, beacon interval 100 ms

Event

Event Type:             wifi1
Trap Type:              Channel Power Change
Device ID:              xxxxxxxxxxxxxxx
Device Name:            ETSAC
Time:                   03-19-2014 10:13:11
Message:                 access interface wifi1 channel power changed: channel 0, transmit power 10 dBm, beacon interval 100 ms.

I have replicated this a few times

so disconnecting the primary eth0 from the redundant pair has minimal impact, but adding it back causes the radios to go down.

I am using an external power source.

HM 6.1r3a - latest build
AP 370 HiveOS HiveOS 6.0r2d
Cisco WS-C3750G-24PS ver 12.2(55)SE6

Andrew,
Our link aggregation, as of HiveOS 6.1, does static etherchannel with no signalling. It is fundamentally the same as the original Kalpana etherchannel. I believe we will use the same MAC address as source on both interfaces, and it's possible that your Cisco switch is actually learning it on both, but discarding the penultimate learned entry.

The loss of wifi1 does not make sense to me, though. When you say you are using external power on the AP, do you mean our supplied power brick, or PoE? If PoE, is it possible that your PSE doesn't provide enough for the AP370? If it's our power brick, please open a support case to find out if that is expected behavior (I don't think so).

Hi Mike

I have a loaner AP 370, but no .at switches and I did not get the Aerohive power brick, so using an adapter. Maybe it is due to the adapter.

Hi Mike

I change the port channel mode to on instead of active and the port channel interface came up.
Port-channel1 is up, line protocol is up (connected)
Members in this channel: Gi1/0/13 Gi1/0/14

  active     Enable LACP unconditionally
  auto       Enable PAgP only if a PAgP device is detected
  desirable  Enable PAgP unconditionally
  on         Enable Etherchannel only
  passive    Enable LACP only if a LACP device is detected

the CAM table shows the Aerohive mac addresses on the port-channel interface

the link aggregation does not display the radio power down when the primary interface is unplugged and then plugged in.

Device ETSAC: member interface eth0 is down now

Event

Event Type:             eth0
Trap Type:              State Change
Device ID:              xxxxxxxxxxxx
Device Name:            ETSAC
Time:                   03-20-2014 12:34:28
Message:                member interface eth0 is down now.

Device ETSAC: member interface eth0 is up now

Event

Event Type:             eth0
Trap Type:              State Change
Device ID:              xxxxxxxxxxxxxx
Device Name:            ETSAC
Time:                   03-20-2014 12:35:51
Message:                member interface eth0 is up now.

Excellent, glad to see you figured it out!

As of HiveOS 6.1, we use basically the original Kalpana etherchannel, statically defined with no signaling or dynamic addition or subtraction of links from the bundle.