Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

AP 134/135 eth1 behaviour

This thread has been viewed 0 times
  • 1.  AP 134/135 eth1 behaviour

    Posted Mar 04, 2015 07:30 AM

    I wonder if someone could detail for me, or point me towards documentation of, how the ethernet ports behave on the AP134/135 if both are active in their default settings.

     

    It seems they operate in a bonded mode, but I'm not clear which mode. 

     

    Thanks



  • 2.  RE: AP 134/135 eth1 behaviour

    Posted Mar 04, 2015 10:07 AM

    Hi,

     

     

    eth1 config for ArubaOS 6.4 is as below.

     

    (Controller) (config) #show ap wired-port-profile default

    AP wired port profile "default"
    -------------------------------
    Parameter Value
    --------- -----
    Wired AP profile default
    Ethernet interface link profile default
    AP LLDP profile default
    Shut down No
    Remote-AP Backup Enabled
    AAA Profile N/A
    Bridge Role N/A
    Time to wait for authentication to succeed 20 sec
    Spanning Tree Disabled

     

    (Controller) (config) #show ap wired-ap-profile default

    Wired AP profile "default"
    --------------------------
    Parameter Value
    --------- -----
    Wired AP enable Disabled
    Trusted Not Trusted
    Forward mode tunnel
    Switchport mode access
    Access mode VLAN 1
    Trunk mode native VLAN 1
    Trunk mode allowed VLANs 1-4094
    Broadcast Broadcast

     

     Adding new snip



  • 3.  RE: AP 134/135 eth1 behaviour

    Posted Mar 04, 2015 12:18 PM

    I realise one can be a downlink, we make use of the hospitality units so I'm familiar with that config.

     

    Our AP134/135 units are configured with both ethernet ports as uplinks. The AP sets up an interface of bond0 and it's mode of this bond0 interface I'm interested in. Does anybody know how this should behave?