This message you are receiving from DFM is in the context of a counter on a network element, not the server hosting the CW DFM application. Generally speaking, there are two different sized counters, 32bit, and 64bit or High Capacity (HC) counters. These counters are used to store information about a particular network interface or event, such as how many packets have gone through an interface, or how many bytes.
A 32-bit signed integer counter, like the ifInOctets/ifOutOctets, will overflow or wrap at 2^31-1. Most modern NMS applications, and maybe even DFM, should have logic to figure out when a counter has overflowed or wrapped, but I think it is also dependent on DFM's polling interval (And if DFM solely relies on solicited SNMP traps, you can ignore most of what I'm about to say). If an interface is pushing an extremely large volume of bits through it, and it wraps N+1 times in a polling cycle, I don't know how you'd be able to detect that.
I personally do not have much experience with DFM, so I'm not sure exactly what you should do to resolve your issue, but hopefully this will help you understand the 32bit/64bit stuff.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...