New Version WLCCA 4.4.3

Javier Contreras · ‎07-24-2017

Hello

New version WLCCA 4.4.3:

Support for 802.11FT adapative state
WLAN name for message "mDNS profile is configured in WLAN.."
Improved logic for message "General: The IPv6 Multicast/Broadcast mode is on Unicast.", to only report if IPV6 is enabled, and mcast/base fw is in use
Flex group name in message "Flex: Efficient AP upgrade is not enabled for Flex group:"
Improved logic for message "General: Aggregation scheduler disabled", now checks if 11n/ac is enabled, and the message includes band affected
Added interface name for message "General: DHCP enabled on the interface, but DHCP IP is not configured.", also improved logic to skip if the interface is a wired guest type
Added wlan name to message "General: 11v is enabled, it is recommended to have the MFP infrastructure disabled."

Incorrect parsing of DHCP proxy state
Incorrect handling of NTP sync status
Radius server parsing
Incomplete parsing of DCA/TPC/ED-RRM status
Proper detection of lag mode for UCS platforms
Typo for message 30063
Fixed parsing of 802.11b aggregation scheduler
Modified message "Platinum QoS settings are not set to 802.1p 5 or 6, check in Controller QoS Profiles" to use 5 or 6, instead of 6 or 7

https://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=wlc-conf-app-dev

framanza · ‎07-25-2017

Does it support configs from 8.2 and 8.3 Software? By the info, it says only 4.0 to 8.0.

Please confirm. Thanks.

Javier Contreras · ‎07-26-2017

hi

it will work with files up to 8.5, I forgot to update the about box, it will be modified for next version :-)

regards

FELIX MEIXNER · ‎08-07-2017

Hi Javier,

i found that this version 4.4.3 fixes an issue with the best practice checks "Controllers - <hostname> - Best Practices".

Version 4.4.1 reported some checks not to be compliant, which was wrong.

Version 4.4.2, using the same "running-Config", marks those checks compliant, representing the correct state actually configured on the system.

Do you have any info about this? Hopefully it was a known and now fixed issue.

Regards,
Felix

Javier Contreras · ‎08-07-2017

hi Felix

the version 4.4.1 introduced a parsing problem (it skipped a important section of data), which cascaded on multiple checks providing incorrect data

so yes, it would be important to migrate to 4.4.3, and report any new issues from that release

Thanks for your feedback

regards

Chahta Choctaw · ‎08-01-2018

How does one gain access to this download?

minh1 · ‎09-04-2018

Please provide download link, cisco id - cisco.rfs

Thank you