For sure, for many years I have seen the problem of sleeping connections (values not changing but no Out of Service or other indication that there is a problem). As was stated it is rare. It must be manually noticed by someone before it is flagged as a problem so that might be part of the reason it is a rare problem. On a two CP system you might be able to run some scripts to check P2P but this quickly gets incredibly complex as the number of CP's increases. Even if compiled code were to be used instead of scripts I expect you can quickly bog down a processor by running checks of OM lists. When I was at sites that experienced power failures, where some or all of a system lost power, we had trouble with P2P depending on whether the network connection was restore before the CP's were booted. If the CP's (at least one) were booted before the network connectioon was working, the peer connections were flagged as Out of Service, if we looked. For that reason, we set up a practice to always perform a CHECKPOINT on every CP after all the stations had booted and the network was running. But the key difference was that the Out of Service condition was set as opposed to the sleeping connections where no Out of Service condition was set. It has been a while since I have tested a power fail condition where network is restored after CP's are booted so that problem may have been fixed. Terry _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave