A network engineer observes that periodic bandwidth statistics collected from a 10-GigabitEthernet interface on a Cisco router display inaccurate, negative, or wrapping byte counts during peak traffic hours. The Network Management System (NMS) currently uses SNMPv1 to poll standard 32-bit interface counters (`ifInOctets` and `ifOutOctets`). Which SNMP version capability and MIB object group should be deployed to resolve this counter rollover issue?
- Migrate to SNMPv2c or SNMPv3 to poll 64-bit High Capacity (HC) counters (`ifHCInOctets` and `ifHCOutOctets`).Answer
- BRetain SNMPv1 but increase the NMS polling frequency to poll 32-bit counters every 2 seconds.
- CConfigure SNMP Traps on the router to automatically push 32-bit counter values whenever threshold limits are exceeded.
- DEnable SNMPv3 authPriv security level to automatically encrypt and expand 32-bit counter fields into 64-bit values.
Answer
Migrate to SNMPv2c or SNMPv3 to poll 64-bit High Capacity (HC) counters (`ifHCInOctets` and `ifHCOutOctets`).
High-speed interfaces (such as GigabitEthernet and 10-GigabitEthernet) rapidly roll over standard 32-bit MIB counters (`ifInOctets`/`ifOutOctets`) supported by SNMPv1. SNMPv2c and SNMPv3 introduce IF-MIB 64-bit High Capacity (HC) counters (`ifHCInOctets`/`ifHCOutOctets`), which allow accurate traffic monitoring without counter wrapping.
Step-by-Step Solution
Key Concept
64-bit MIB High Capacity (HC) counters introduced in SNMPv2c/SNMPv3 for high-speed interface monitoring