[FP-EX-1] Known issues when scanning Network Switches
There are specific situations where abnormal behavior was reported when scanning some Network Switches. Reported versions:
This may be caused by specific configuration where the Switch does not know how to handle speciifc traffic pattern sent by the Internal Scanner:
 Some switches have HTTP/HTTPS management enabled. This can be verified by having:
https server enabled in the config.
"!ip http server
ip http secure-server
ip http secure-active-session-modules none
ip http active-session-modules none
This causes the switches CPU to spike based on HTTP CORE process. When a switch has sustained 100% cpu it may stop forwarding traffic in specific circumstances, for example when broadcasts are sent and the switch does not have the destination MAC in TCAM it will use an Interrupt that needs processor time.
The recommendation here is to disable http management of the switch and use cli. If this is not possible then temporarily exclude the switch management IP from scans. We have a task on our road-map to allow for port exceptions on devices with known scan problems such as switches/printers/etc. but this is not yet released.
 Kindly update the switch to the latest version. Some OS versions are old and have known bugs that can cause crash conditions.
 If the above two points do not resolve the issue then the last resort option is to exclude the switch from the Scan Surface for the time being. This is done by going to the Scan Surface, finding the Network Segment where the Switch Management IP Address segment is defined and pressing an [x] on the entry with the IP Address of the switch. This would move the IP to the Suggested Targets box and make it a scan exception.
We are still investigating scan issues with switches and will continue to update this KB