This counter records the raw number of framing/code-violation error events detected at the T1 path layer, counted as individual events rather than affected seconds. Because CVP counts events rather than seconds, it lets the admin distinguish a path with a few scattered, low-impact violations from one where a single second contains a dense burst of them, something the seconds-based ESP counter on the same port can't show. For example, a CVP of 500 accumulated in just 2 errored seconds (ESP=2) would indicate a very dense burst of framing violations rather than steady low-level noise.