You are on page 1of 9

WLC Config Analyzer - Report Controller Messages

wc-mdf-002
10011,Error parsing AP Groups, invalid line format. Line :Press Enter to continue or to abort 50020,Mobility: The number of peers is less than the total number of loaded controllers in the config file. It is strongly suggested to load all controllers in the mobility group to enable all possible checks 40013,Voice: 5.5 mbps should be disabled for voice, check in 802.11b Network Configuration. This depends on phone density versus desired cell size 40015,Voice: ACM is not enabled, check in 802.11b Voice Configuration 40028,Voice: Low data rates (6 and 9 mbps) should be disabled for voice, check in 802.11a Network Configuration (7921 recommendations) 40038,Voice: Traffic Stream Metrics collection is disabled. It is recommended, although not mandatory, to enable it in 11b/g band 40041,Voice: Depending on your RF coverage, and desired call density, it may be recommended to disable high data rates for voice services (36, 48, 54 mbps) in 11b/g band 40041,Voice: Depending on your RF coverage, and desired call density, it may be recommended to disable high data rates for voice services (36, 48, 54 mbps) in 11a band 40048,Voice: Too many clients with SNR lower than 25 has been detected, it may be indication of poor RF coverage or bad roaming in clients 40019,Voice: SSID RKVOICE does not have AP CAC limit enabled 40024,Voice: 802.11a Coverage Min Clients 3, is less than recommended value of 5 40025,Voice: 802.11b Coverage Min Clients 3, is less than recommended value of 5 40043,Voice: DCA interval is recommended to be high, to prevent channel changes during working hours., for 11a band. This may be ok depending on your RF enviroment

40043,Voice: DCA interval is recommended to be high, to prevent channel changes during working hours., for 11b band. This may be ok depending on your RF enviroment

AP Messages
WAP-21
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-21, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-22
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-22, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-23
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-23, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-24
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-24, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-25
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-25, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-26
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-26, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-27
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-27, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-28
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-28, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-29
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-29, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-30
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-30, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-31
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-31, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-32
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-32, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-33
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-33, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-34
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-34, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-35
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-35, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-36
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-36, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-37
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-37, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-38
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-38, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-39
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-39, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-40
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-40, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-41
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-41, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-42
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-42, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-43
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-43, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-44
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-44, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-45
20012,AP: Empty primary controller. It is recommended, to have a primary controller name configured, for better/more predictive AP join process. This is not mandatory 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-46
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-46, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-47
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-47, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-48
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-48, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-49
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-49, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-50
10017,Line structure error while parsing Interference profile, no interference percentage value 20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-50, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-51
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-51, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-52
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-52, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-53
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-53, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-54
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-54, Configured Secondary switch name: wc-mdf-001

20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-70
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-70, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-71
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-71, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

WAP-99
20008,AP: Possibly incorrect secondary switch configuration, not found in controller list, or controller config not loaded: WAP-99, Configured Secondary switch name: wc-mdf-001 20017,AP: Syslog messages are sent to broadcast address, if there are errors reported by many APs, and there are too many APs per vlan, this can cause broadcast storms. For best practices, it is better to configure to individual server

Use at your own risk Report Generated at:6:01:23 PM 8/4/2011 Questions?: WLC Config Analyzer Mail List.