both good points,, another thing i look at is ld 60 lcnt.. if your taking hits there, they point to the problem.. and while your in 60, ssck 0..make sure your pri's are tracking on a good loop.. 222 if i remember right is msg received in a null state.. that's usually a d that can't sync all the time... it misses some far end msgs.. ld 96 stat serv might shed some light... some providers need service msgs, others can't accept them.. that usually runs 222's and 227 msgs in pairs, at a sequential rate... every 5, 20 or 30 etc minutes depending on the error rate.. it drops when the lcnt table matches the trsh parm's in 73..
i have cleared 222 errors by reloading the msdl, not often but i usually try that
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.