Hi all,
We had upgraded to JUNOS 5.6 recently, and implemented prefix-specific
action. And it seems that after that, we noticed that the more traffic we
policed, the amount of unaccounted cflow data increase. The normal data
level is still reflecting accurately, with the correct amount of bandwidth
utilization.
Is anyone facing such similar problems after implementing the
prefix-specific actions?
Any inputs are welcomed.
Regards,
Cheeyong
We had upgraded to JUNOS 5.6 recently, and implemented prefix-specific
action. And it seems that after that, we noticed that the more traffic we
policed, the amount of unaccounted cflow data increase. The normal data
level is still reflecting accurately, with the correct amount of bandwidth
utilization.
Is anyone facing such similar problems after implementing the
prefix-specific actions?
Any inputs are welcomed.
Regards,
Cheeyong