VC Utilization & Performance

Field	Description
VC Name	The name assigned to each VC in the list. The default value is the initial network name assigned to the VC. If you have changed the VC name, the name you assigned appears here.
Total Frames (Cells)	For FR(Frame Relay) VCs, the total Ingress Frames measured at both endpoints. For ATM VCs, the sum of Ingress cells(both Cell Loss Priority "0" and "1") measured at both endpoints. For IW(Frame-ATM Internetworking) VCs, the total Ingress and Egress Frames measured at the Frame Relay endpoint.
Total Bytes (User Cells)	In conjunction with the Total Frames or total Cells measurement, this count allows the following determinations: For FR or IW VCs, the average frame size For ATM VCs, whether the VC carries OAM Traffic.
Direction (Type)	The direction(End A to End B or End B to End A) in which traffic flows on the VC, and the protocol the VC uses to transmit data. Protocol types you may see include FR(Frame Relay), ATM(Asynchronous Transfer Mode), or IW(Frame-ATM Internetworking). This field indicates the VC as configured on your provider's Frame/ATM network. Customers accessing the network via NNI with third party carriers(also called virtual access) may be configured for Interworking Service to achieve connectivity between customer Frame Relay ports not both provisioned on the network.
TX CIR Bytes (CLP 0 Cells)	Indicated for both the A and B endpoints, the transmitted CIR volume. CIR is measured in Bytes at FR endpoints and Cells at ATM endpoints.
RX CIR Bytes (CLP 0 Cells)	Indicated for both the A and B endpoints, the received CIR volume. CIR is measured in Bytes at FR endpoints and Cells at ATM endpoints. RX counts at the B end are compared to TX counts at the A end in calculating data delivery rate in the A-B direction. Similarly, RX Counts at the A end are compared to TX counts at the B end. Note: Small timing variations between VC endpoints, the possibility that data may be en-route at the time hourly traffic counts are recorded at each VC network endpoint, and low level digital noise may sometimes result in slightly more or less "Received" bytes or cells within a time period than are "Transmitted". The effects of such variations between the independently derived counts become insignificant as the time period increases. These effects are not normally enough to affect the accuracy of delivery rate percentage calculations to two decimal points when calculated over the defined period of one calendar month. Be assured that chronic or even short term delivery rate anomalies will be represented by a marked drop in the delivery rate calculation.
TX DE Bytes (CLP 1 Cells)	Indicated for both the A and B endpoints, the transmitted BIR volume. BIR is measured in Bytes at FR endpoints and Cells at ATM endpoints.
RX DE Bytes (CLP 1 Cells)	Indicated for both the A and B endpoints, the received BIR (discard eligible) volume. BIR is measured in Bytes at FR endpoints and Cells at ATM endpoints.
TX ODE Bytes	Indicated for both the A and B endpoints, the transmitted ODE volume, measured in Bytes at FR endpoints. Note: The count is not applicable for ATM endpoints.
RX ODE Bytes	Indicated for both the A and B endpoints as applicable, the received ODE volume, measured in Bytes at FR endpoints. Note: The count is not applicable for ATM endpoints.
In Discards	The number of frames or cells (as appropriate) discarded at ingress to the network due to rate enforcement. Note: When viewing daily statistics for an individual VC, some hours may not be indicated due to incomplete or faulty record receipt. Because including records from one VC side but not the other would not support accurate delivery rate calculations, only paired endpoint statistics are loaded into the statistics database. Problems with chronically missing port or VC statistics should be reported via a trouble ticket.

Data > Reports > Statistics > VC Utilization & Performance