I swapped reference clocks in ddb to reference a different span,same result.
I swapped csu's,same result. I monitored the span from the telco, it ran clean. We just upgraded to 5.5 and applied the latest patches,same result. Some one told me a time ago, the network swaps dchnnels in central office, not towards us..causes a slipr.
It is not service effecting but the end user wont let it go.
I swapped csu's,same result. I monitored the span from the telco, it ran clean. We just upgraded to 5.5 and applied the latest patches,same result. Some one told me a time ago, the network swaps dchnnels in central office, not towards us..causes a slipr.
It is not service effecting but the end user wont let it go.