Friends,
We manage an event with the SZ300 fw 5.1. An event with 106 AP's, and we've seen some differences that are not yet clear if I should open a TAC support, or if I can get any common denominator here in the forum:
1 - Latency failures (even with few users), and connection failure constantly in distinct AP's.
2 - Constant channel change (Background Scanning) set to 600s (10 minutes).
3 - Failures without logging in AP: Where are the error logs, failure reasons (failure to join, dhcp handshake failure, open / wpa2 network failure, reassociation failure ...), have not I found them?
4 - The AP packet capture file came empty (tried 3 times, and collected in times apart), collection for approximately 15 minutes.
5 - A large amount of entries (log) of the same user in SZ that does not fit the reality. The user is on the same AP, even MAP, but is being disconnected and connected again, why? How do I find out if some channel change is due, if it is some application that it is using, and what causes wlc to log off and connect again, since it remains with the IP address. I discard roaming because it is only in 1 AP.
6 - The same user of item 5, has 5 sessions in SCI. I need to know what the metric is, because in the view of the controller this user is unique, but why in history does he report with 109 entries in the SZ300, and "only" 5 sessions in SCI? What is being evaluated? This scenario is with all my clients, and the numbers are dissenting.
NOTE: The session iddle time-out setup was for 5 minutes at this event, but wpa2 clients reported on the difficulty of connecting after the downtime, a very untypical scenario.
Regarding customer discrepancy, I've already noticed in SCG200, but with respect to the other items, I'm thinking that version 5.1 might be the offender.
We manage an event with the SZ300 fw 5.1. An event with 106 AP's, and we've seen some differences that are not yet clear if I should open a TAC support, or if I can get any common denominator here in the forum:
1 - Latency failures (even with few users), and connection failure constantly in distinct AP's.
2 - Constant channel change (Background Scanning) set to 600s (10 minutes).
3 - Failures without logging in AP: Where are the error logs, failure reasons (failure to join, dhcp handshake failure, open / wpa2 network failure, reassociation failure ...), have not I found them?
4 - The AP packet capture file came empty (tried 3 times, and collected in times apart), collection for approximately 15 minutes.
5 - A large amount of entries (log) of the same user in SZ that does not fit the reality. The user is on the same AP, even MAP, but is being disconnected and connected again, why? How do I find out if some channel change is due, if it is some application that it is using, and what causes wlc to log off and connect again, since it remains with the IP address. I discard roaming because it is only in 1 AP.
6 - The same user of item 5, has 5 sessions in SCI. I need to know what the metric is, because in the view of the controller this user is unique, but why in history does he report with 109 entries in the SZ300, and "only" 5 sessions in SCI? What is being evaluated? This scenario is with all my clients, and the numbers are dissenting.
NOTE: The session iddle time-out setup was for 5 minutes at this event, but wpa2 clients reported on the difficulty of connecting after the downtime, a very untypical scenario.
Regarding customer discrepancy, I've already noticed in SCG200, but with respect to the other items, I'm thinking that version 5.1 might be the offender.
