03-14-2025 03:45 AM - edited 03-14-2025 03:47 AM
Hello Cisco 9800-Coders,
I always get confused, when it comes to Wireless profile polices on this box.
There is an annoying mismatch in naming of Your Policy profiles:
The GUi states "Policy Profile" name, while the CLi states "profile policy" instead:
Would it be possilbe to adapt the GUi represenation of wireless policy profiles accordingly ?
In my opinion the naming "Profile policy" name would be identical to the naming convention in CLi.
Another real sucking thing is the lazybone presentation of Tags and Profiles within the GUi.
The Gui is representing Tags&Profiles in a simple alphabetical and confusion order without sense of the overall concept:
Especially for beginners it would be more understandable, to group all these tags and profiles according to normal human brain thinking about Your new configuration concept instead of a brainless, alphabetial ordering:
Can You please address this imporvement proposal from a frustrated customer to Your programmers please ?
And Yes, I'm so thankful for all help in future coming from the US.
Kind regards
Wini
Solved! Go to Solution.
03-19-2025 07:26 AM
Wini there is no explanation other than sloppy programming and bad design. I could point out dozens of other inconsistencies and illogical things and some things that are just named incorrectly for the function they perform (in other words completely wrong because the coder did not understand what they were for). Unfortunately nobody in the BU will pay any attention to what you write here. These things will only get fixed if TAC or your Cisco account team raise an enhancement request (bug severity 6) into the BU. Enhancement requests are generally treated as very low priority compared to new features and actual bug fixes, so can take years to implement or often get terminated because the BU thinks they are not worth spending time/money on. Cisco puts these releases through EFT (early field trials)/beta but I've found that even when reporting issues in EFT/beta they almost never get fixed before the software is released and often just never get fixed at all so I would not hold out much hope for this type of thing ever getting addressed.
Of course there is also the GUI screen which shows the slightly more logical layout if you go to Configuration -> Wireless -> Access Points then click on the symbol for AP Operational Configuration next to the AP which pops up the logical structure for the tags and profiles attached to the AP.
03-14-2025 04:16 AM
- FYI : https://community.cisco.com/t5/wireless/c9800-ap-cdp/m-p/4728569/highlight/true#M248783
M.
03-14-2025 07:10 AM
In regards to the link @marce1000 stated, these things have been around for a while even in other platforms. Keep in mind also that the IOS-XE tried to match up with what was sort of their in AireOS so it really doesn't matter, because once you came from the AireOS side and had to learn the 9800, the whole thing was different. The CLI was always lower case except when you specified entries/variables which is case sensitive, but on the GUI, its always proper case. I just get use to what I'm trying to do and then just grep on the cli to see where that change is placed under. What helps me a lot is the "SAVE", where you can look at the diff and see where the changes you just made is located on the CLI config.
03-16-2025 11:54 PM
Hello Scott,
I don't want to point You to the lower case writing in Cli.
I want to express the mistake of writing when I compare GUi to CLi:
GUi: Policy Profile
CLi: profile policy
Do You have a good explanation for this mess ?
Kind regards
Wini
03-19-2025 07:26 AM
Wini there is no explanation other than sloppy programming and bad design. I could point out dozens of other inconsistencies and illogical things and some things that are just named incorrectly for the function they perform (in other words completely wrong because the coder did not understand what they were for). Unfortunately nobody in the BU will pay any attention to what you write here. These things will only get fixed if TAC or your Cisco account team raise an enhancement request (bug severity 6) into the BU. Enhancement requests are generally treated as very low priority compared to new features and actual bug fixes, so can take years to implement or often get terminated because the BU thinks they are not worth spending time/money on. Cisco puts these releases through EFT (early field trials)/beta but I've found that even when reporting issues in EFT/beta they almost never get fixed before the software is released and often just never get fixed at all so I would not hold out much hope for this type of thing ever getting addressed.
Of course there is also the GUI screen which shows the slightly more logical layout if you go to Configuration -> Wireless -> Access Points then click on the symbol for AP Operational Configuration next to the AP which pops up the logical structure for the tags and profiles attached to the AP.
03-21-2025 06:12 AM
That is what I was referring to... to me, I don't care because it has never bothered me and it probably doesn't bother anyone else. The only way that will change is if you open a TAC case and they can file a change or talk to your Cisco account team. You are already talking to them since they are trying to sell you spaces. If you want something done, you need to make time for it.
GUi: Policy Profile
CLi: profile policy
03-21-2025 12:42 AM - edited 03-21-2025 12:43 AM
Hello Rich, thank You for Your open speech regarding bad programming design in the new 9800-GUi. Unfortunately, I have no time to disucss this with my Cisco Account team, which wants to sell Cisco Spaces instead on top of the 9800-WLC. I expected that the Cisco experts in this forum would take up reasonable improvement proposals from a Million-$-customer from this forum into the BU internally of Cisco to improve the product asap.
Have a nice weekend
Wini
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide