Version 0.7.2 - Focus on main case generators and common config issues
Changes on v.0.7.2:
July 6th:
Focus on common "case generators" around vlan, interfaces, mapping between profiles, SVI, etc
Features
- Added DTIM, QoS info to WLAN view
Features - Added vlan list parsing
- XLS: AP RF Health report now shows slot 2 when present
- XLS: Added vlan information to WLAN table
- XLS: WLAN table will flag in red if either wlan or policy profile are disabled
- XLS: Interface table, now shows vlan mapping, flags in red missing entries, and which policy profiles reference each interface
- XLS: Added Flex group to tag summary report
- New check: generates best practices error, if DHCP relay is configured, but no DHCP relay source interface has been defined in SVI
- New check: error reporting if SVI interface is configured, but no corresponding vlan has been found
- New check: warns if SVI is in use by active policy profile, but lacks IP address
- New check: validates if mDNS gateway is in use by WLAN, and policy profile is not mapped to vlan(s) with SVI interface
- New check: checks if DHCP relay is configured in policy profile, and confirm there is corresponding SVI for the mapped vlan,
- New check: warns if flex profile vlan name matches controller vlan group name, and site is local switching
- New check: validate that for all vlan IDs present on Flex profile, with matching vlan ID in controller, that the vlan name is same, if the site is local switching, CSCvn48234
- New check: notify if AP name has more than 32 characters. CSCvy11981
- These apply only SVI/VLAN is referenced by policy profile:
- New check: warns if SVI is in use by active policy profile, but is on shutdown state
- New check: warns if SVI is in use by active policy profile, but is on line protocol down state
Fixes
- XLS: if more than 1 WLANs was not in use, it would not get added properly to the report
- Enabled AP certificate expiration checks for 9800 controllers
- XLS: WLAN table is generated across all combinations of WLAN and policy profiles present in tags, regardless if they are assigned to APs, plus all unused WLAN profiles
- Error if message 230012 happened for both IPv4 and IPv6
- Corrected text for message 230041