I may be betraying my ignorance here in use of terminology but....
We were wondering here at work if there's a "clever" way to trawl through switches across all the networks in the organisation looking for instances of CRC errors or packet loss?
Perhaps some sort of API magic?
Solved! Go to Solution.
Yes, but you will need to create a script for this. Here are some example scripts: https://github.com/meraki/automation-scripts
API would definitely be the way to go.
There is also the switching overview page that can be enabled in early access. It shows the number of active ports with errors across all switches in a given network.
Thank you yes, the switching overview does seem like a very convenient addition to the dashboard.
@alemabrahao Thank you yes, that's the command. It takes a specific SNR or am I reading that wrong.
If this is the case you could... loop through a list of serial numbers and create a list of ports with problems that way?
Yes, but you will need to create a script for this. Here are some example scripts: https://github.com/meraki/automation-scripts
Thank you 🙂
I will give this a try when I ... a day when there are less fires to extinguish.
You can also use the API to identify ports running at 100 Mbps, which, if you can parse to exclude devices which only support 100 Mbps, will likely ID below par cabling too - which might not otherwise show errors. https://developer.cisco.com/meraki/api-v1/#!get-device-switch-ports-statuses Would be your friend in this. The returned data from this endpoint also includes LLDP/CDP, which will help.