CiscoWirelessRogue Update for Larger AP count

Was having some problems with the Rogue Detection datasource because of larger enviornments. Modified it so that the timeout values are set and to do a try catch statement in case we didn't retrieve a get value. I'm thinking there's got to be a better way to do this though, as this is a very long running script when there's 1000+ APs as part of the WLC. 

 

X7FAY3