Controller-less WLANs

View Only

last person joined: one year ago

Articles relating to existing and legacy HPE Aruba Networking products and solutions including IAP, Central / HPE Aruba Networking Central, MSR, and Outdoor Mesh

Back to Library

Instant Dual Uplink

Kudos

Jul 03, 2014 11:23 PM

AnandKumar Sukumar

Introduction : This article outlines the procedure to configure two ethernet uplinks for an Aruba Instant Cluster.

Feature Notes :

Following are the feature notes ::

At any point of time; only one port would be active i.e. forward packets

With current design (as of 6.3.1.4-4.x); the feature is intended to provide redundancy and it wouldn't be possible to route traffic thru both ports using policy based routing i.e. corp traffic thru one uplink and guest traffic thru another.

Environment : Aruba Instant cluster with two different uplink paths connected to eth0 & eth1 of the APs.

Network Topology : Configuration Steps : With ports plugged into appropriate switches with proper VLAN configuration; below is the configuration needed on IAP end.

Create a new Wired Port Profile

Ensure "Uplink" option is enabled

Configure appropriate VLAN to match switch config.

Save and map the profile to the port.

Set appropriate proirity and failover time under "System --> Uplink".

Answer : With the configuration in place; the AP would be switchover to alternate uplink in case of failure.

Verification :

6c:f3:7f:c5:13:46# show uplink status 

Uplink preemption           :enable
Uplink enforce              :none
Ethernet uplink eth0        :DHCP
Ethernet uplink eth1        :DHCP
Uplink Table
------------
Type      State  Priority  In Use
----      -----  --------  ------
eth0      UP     0         Yes       <---- Before Failure
Wifi-sta  INIT   6         No
3G/4G     INIT   7         No
eth1      UP     1         No           
Internet failover           :disable
Max allowed test packet loss:2
Secs between test packets   :2
VPN failover timeout (secs) :180
ICMP pkt sent        :0
ICMP pkt lost        :0
Continuous pkt lost  :0
VPN down time        :0



6c:f3:7f:c5:13:46# show uplink status 

Uplink preemption           :enable
Uplink enforce              :none
Ethernet uplink eth0        :DHCP
Ethernet uplink eth1        :DHCP
Uplink Table
------------
Type      State  Priority  In Use
----      -----  --------  ------
eth0      UP     0         No
Wifi-sta  INIT   6         No
3G/4G     INIT   7         No
eth1      UP     1         Yes              <---- After failure of eth0, Eth1 In Use
Internet failover           :disable
Max allowed test packet loss:2
Secs between test packets   :2
VPN failover timeout (secs) :180
ICMP pkt sent        :0
ICMP pkt lost        :0
Continuous pkt lost  :0
VPN down time        :0

Troubleshooting :

Below are the troubleshooting steps for issues related to dual uplink .

Ensure link status; using "show uplink status". If the link isn't up; then focus on troubleshooting link not coming up
If "internet failover: is enabled; ensure internet connectivity is available else link would flap over to the alternate uplink
If "internet failover" is enabled and config for ICMP check is aggressive; it may result uplink switchover when uplink has performance issues.
"show log system" would show information on link switching.

Example ::

May 30 09:54:06 cli[1742]: <341271> <ERRS> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| ethernet uplink eth0 link down.
May 30 09:54:06 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| stopping DHCP on bond0
May 30 09:54:06 cli[1742]: <341185> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Retrieving ip address from uplink, ip 192.168.4.104, mask 255.255.255.0.
May 30 09:54:06 cli[1742]: <341274> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Update election ip from br0, election ip 192.168.4.104/255.255.255.0.
May 30 09:54:06 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| build_my_ip_address: old ip and new ip same; skipping
May 30 09:54:06 cli[1742]: <341167> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Uplink eth0 type Ethernet, state UP->DOWN.
May 30 09:54:06 cli[1742]: <341177> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Try next uplink because current uplink is down - Ethernet.
May 30 09:54:06 cli[1742]: <341168> <INFO> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| get_lower_uplink,752: uplink type Ethernet, state UP.
May 30 09:54:06 cli[1742]: <341263> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| enable uplink eth3.
May 30 09:54:06 cli[1742]: <341167> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Uplink eth3 type Ethernet, state UP->PROBE.
May 30 09:54:06 cli[1742]: <341265> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| enable ethernet uplink eth3.
May 30 09:54:06 cli[1742]: <341265> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| ifenslave bond0 eth3
May 30 09:54:07 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| uplink is down, cannot be enabled.
May 30 09:54:07 cli[1742]: <341168> <INFO> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| swarm_select_uplink,1333: uplink type Ethernet, state PROBE.
May 30 09:54:10 cli[1742]: <341272> <ERRS> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| ethernet uplink eth3 link up.
May 30 09:54:10 cli[1742]: <341167> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Uplink eth3 type Ethernet, state PROBE->UP.
May 30 09:54:10 cli[1742]: <341181> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Uplink eth3, setup ip for uplink - Ethernet.
May 30 09:54:10 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| bring up dhcp client for ethernet uplink
May 30 09:55:11 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| /etc/setup_ip_swarm Ethernet 1
May 30 09:55:11 cli[1742]: <341166> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Get interface br0 ip: 0.0.0.0/0.0.0.0.
May 30 09:55:11 cli[1742]: <341005> <ERRS> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| ethernet up without ip address, setup ip now
May 30 09:55:11 cli[1742]: <341005> <ERRS> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| ethernet uplink couldn't comeup, ip not set
May 30 09:55:11 cli[1742]: <341264> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| disable uplink eth3.
May 30 09:55:11 cli[1742]: <341167> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Uplink eth3 type Ethernet, state UP->DOWN.
May 30 09:55:11 cli[1742]: <341006> <CRIT> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| route delete default
May 30 09:55:11 cli[1742]: <341185> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Retrieving ip address from uplink, ip 192.168.4.104, mask 255.255.255.0.
May 30 09:55:11 cli[1742]: <341274> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Update election ip from br0, election ip 192.168.4.104/255.255.255.0.
May 30 09:55:11 cli[1742]: <341004> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| build_my_ip_address: old ip and new ip same; skipping
May 30 09:55:11 cli[1742]: <341177> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| Try next uplink because current uplink is down - Ethernet.
May 30 09:55:11 cli[1742]: <341263> <WARN> |AP 00:0b:86:8f:38:10@192.168.4.104 cli| enable uplink .

Statistics

0 Favorited

16 Views

0 Files

0 Shares

0 Downloads

Controller-less WLANs

Instant Dual Uplink

Related Entries and Links