Wired Intelligent Edge

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. :-)

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. :-)

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. :-)

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. :-)

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 !!!

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 !!!

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 !!!

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 !!!