PDF(3.3 KB) View with Adobe Reader on a variety of devices
ePub(43.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(60.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 12, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
SR-680259480 - US SG500: MIB Walk Issues
SNMP MIB walk provides much more output than the configured ports.
February 10, 2017
February 16, 2017
An SNMP MIB walk, performed on an SG500, can take an extended amount of time to complete. This is a known issue and is due to the architecture of the switch.
The output can be limited by polling the switch using the MIB files provided on cisco.com or if the SNMP server allows, limit the 'walk' to exclude OID's that are not necessary.
The walk can be limited on switches that are not stacked by changing the stack mode to standalone. For the SG500, this will reduce the number of ports reporting from 800 to 100. If you are operating just one switch, you can change switch models to an SG300 and limit the ports a little further.