If you are seeing any SNMP information at all from the switch, then the configuration of community public ro is working fine. The error you are seeing is probably working as designed. Not all public MIB oids are implemented on every switch. If you are walking a MIB that comes with the firmware that was downloaded for the PC6224, then you are less likely to see this issue. It can largely depend on the OID you are trying to access. Even a MIB for the PC6224 is the same as that of the PC6248, which may also exhibit such behavior. For example, if you are trying to do a walk across all ports, it may go fine for ports 1 through 24, but then hiccup on port 25. This would be due to the same MIB being used on both the 24-port and 48-port switches. Bottom line, "no such object" is common if using MIBs that don't come with the switch, but may also occasionally be found even with the included MIBs. Here is something to try:
1. Make sure you have the latest firmware loaded.
2. Unpack the MIBs that come with the latest firmware, and import those MIBs into your monitoring system.
3. Don't use any other MIBs that come with the monitoring system.
If you have further questions, please provide the name of the monitoring software you are using, the firmware version of the switch, and the exact MIB and OID you are walking, and maybe someone has seen it and can provide a more precise explanation.
vt1012
212 Posts
1
August 7th, 2018 07:00
If you are seeing any SNMP information at all from the switch, then the configuration of community public ro is working fine. The error you are seeing is probably working as designed. Not all public MIB oids are implemented on every switch. If you are walking a MIB that comes with the firmware that was downloaded for the PC6224, then you are less likely to see this issue. It can largely depend on the OID you are trying to access. Even a MIB for the PC6224 is the same as that of the PC6248, which may also exhibit such behavior. For example, if you are trying to do a walk across all ports, it may go fine for ports 1 through 24, but then hiccup on port 25. This would be due to the same MIB being used on both the 24-port and 48-port switches. Bottom line, "no such object" is common if using MIBs that don't come with the switch, but may also occasionally be found even with the included MIBs. Here is something to try:
1. Make sure you have the latest firmware loaded.
2. Unpack the MIBs that come with the latest firmware, and import those MIBs into your monitoring system.
3. Don't use any other MIBs that come with the monitoring system.
If you have further questions, please provide the name of the monitoring software you are using, the firmware version of the switch, and the exact MIB and OID you are walking, and maybe someone has seen it and can provide a more precise explanation.
Hope this helps