i have a Mobility Controller Aruba 7030 version 126.96.36.199.I have a 303H access point with some Ethernet ports on the bottom of the AP.
I'm trying to set these Ethernet ports (E1, E2 and E3) from the Aruba Mobility Controller.
I'm able to set up correctly only on port E1; instead port E2 and E3 stay in disable state (no link).
Here attached the setting I did on the policy:- first of all I created a new Wired Ap Profile (immagine1.PNG)- than i linked it to the AP Wired port (immagine2.PNG)
I'm not able to see the setting for the other ports E2 and E3.
Thank you in advance for your help
You configure the port settings in the AP-group, this is how it looks in the CLI:
ap-group "your-AP-Group" virtual-ap "Your-VAPs" dot11a-radio-profile "RP-A-RAP" dot11g-radio-profile "RP-G-RAP" enet0-port-profile "Uplink-port" enet1-port-profile "Your-wired-port" enet2-port-profile "Your-wired-port" enet3-port-profile "Your-wired-port" enet4-port-profile "Your-wired-port"
I think in 188.8.131.52 web UI you can´t go to "profiles" view under the AP-group configuration. There should be some way of doing it in the UI but I can´t seem to find it, try CLI according to above if possible.
Thank you Christoffer, via CLI worked immediately!
Great! solved in 5 mins ;-)
Is there anyway to configure a specific profiles for different AP or the changes is pushed to all ap within the group ? I got 10 AP 303H in the same group but i need to have different wired profile on each AP !!!
@vcourtois wrote:Is there anyway to configure a specific profiles for different AP or the changes is pushed to all ap within the group ? I got 10 AP 303H in the same group but i need to have different wired profile on each AP !!!
You can make use of "AP Specific" settings that will over-ride different settings that an AP inheritis from it's "AP-Group". You can access this in the GUI through ArubaOS 6.5, but in ArubaOS 8.X, I believe this is still only available in the CLI. I make use of ap-specific settings occassionally if i want to add an SSID to a specific AP, exclude it, max out power, or just to do a "shut/no shut" on a downstream device plugged into port 1 or a 205H - without affecting all of the APs- https://www.arubanetworks.com/techdocs/ArubaOS_85_Web_Help/content/arubaos-solutions/1cli-commands/ap-name.htm?Highlight=ap-name
Curious though, why do they have to be different? Are the wired ports meant to be access-ports on individual VLANs, what about the uplink ports that the AP plugs into?
Actually there is a possibility of 8 different untagged vlan and some place where the 303h are intstall only need access to one vlan and other place 4 different so i need to be able to specific each port on each AP
btw thanks for the fast reply really appreciate it
@vcourtois wrote:Actually there is a possibility of 8 different untagged vlan and some place where the 303h are intstall only need access to one vlan and other place 4 different so i need to be able to specific each port on each AP btw thanks for the fast reply really appreciate it
Makes sense. Wanted to double-check as we went through a similar experience several years ago in our Residence-Halls. The look my co-engineers gave me when I told them we would need at minimum 40 AP-Groups for the Residence-Halls (40 Unique Wired-Profiles) and then x2 if we were looking at disable 2.4 on some of them. :-D I actually made a diagram demonstrating how each "change" results in needing to duplicate the base AP-Group (You want an AP with Wired Ports tagging VLAN 10) x2 (an AP with Wired Port tagging VLAN 10 + 2.4 Turned Off and an AP with Wired Port tagging VLAN 10 with 2.4 Turned On) - so would have ended up with 80. We made compromises and convinced our LAN team to go with a 14 AP-Group solution after we demonstrated that argument.
Since then we've gotten down to a single base profile when it comes to the (wired ports). Instead of our APs tagging the wired ports. Our APs exist on the same Access VLAN as the wired Ports - policy enforcement is done via DACLs on the uplink port based on authentication type.
AP Specific Profiles are probably a good use-case for you as long as you and your co-engineers know about them and remember them - can be easy to forget. You "change/override" only what you need changed - and inherrit all the other settings. Although AP-Specific Configs aren't viewable in the 8.X GUI, you could just make them flat out AP-Groups (cloned from a base profile you make) - but then if you want to make changes (add an SSID to all 10 sites - you'll need to go in and add it to each AP-Group) so more of a preference for you and how you want to manage your settings I would say. :-)
Configuration for device-profile : default-ap-profile
untagged-vlan : 490
tagged-vlan : None
ingress-bandwidth : 100%
egress-bandwidth : 100%
cos : None
speed-duplex : auto
poe-max-power : Class/LLDP
poe-priority : critical
allow-jumbo-frames : Disabled
profile-mode : port-mode
poe-allocate-by : class
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.