Environment : All Aruba controller and Aruba AP's with two ports.
1. AP comes up as active, then goes down periodically.
2. We can also see the AP in the user table just after it comes up.
We must never enable wired profile on the AP port which will be used as uplink port. By default, Aruba APs must be uplinked using port Eth0.
1. If the AP is uplinked using Eth0 and wired profile is applied on it which untrusts the port, the controller will ignore it and the AP will come up fine on the controller.
ap wired-port-profile test-profile
aaa-profile <profile>
ap-group default
enet1-port-profile test-profile
2. If the AP is uplinked using Eth1 and wired profile is applied on it which untrusts the port, the controller will NOT ignore it. This will cause the AP to come up and then it will fall in the user table with a specified role. If the required traffic is not allowed in the role, then the AP will do down and cycle keeps on repeating.
ap wired-port-profile test-profile
aaa-profile <profile>
ap-group default
enet2-port-profile test-profile
We must make sure that the port Eth0 is used for uplink on a campus AP especially if we have put the wired profile on the port.
If we untrust port eth2 of an AP and use it an uplink, it can cause the AP to go down and come up continuously.
This is caused by AP falling in the user table and the role not allowing the mgmt traffic b/w the AP and controller.