Michael, I think the ones that say "No Response" but don't have a C:B.P are not an issue and will disappear whenever the CP is rebooted or may get reused when you add new connections. They seem to be place holders for connections that have previously been removed. If you see entries that have a valid C:B.P and say "No Response" or "Disconnected" those are a problem. It has been awhile but it seems there is a way to use dbvu to find which blocks are trying to sink those variables and you can then look at the blocks to see if they show bad connections. Tom Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Michael Kessler <mkessler@xxxxxxxxxxxxx> Sender: foxboro-bounce@xxxxxxxxxxxxx Date: Mon, 27 Aug 2012 14:50:48 To: <foxboro@xxxxxxxxxxxxx> Reply-To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Peer to Peer connection good but not updating Thanks for the fix, connections restored. I've poked around in rsom and see a number of points labelled "No response 0000". Does this mean I have more broken connections that I don't yet know about. If so is there any way to figure out what tags these are referring to. mk On Mon, Aug 27, 2012 at 12:55 PM, Johnson, Alex P (IOM) < Alex.Johnson@xxxxxxxxxxxx> wrote: > I hit send to quickly: > > Before you do that, would you: > > 1) Break the problem link or links > 2) Checkpoint > 3) Restore the problem link or links > 4) Checkpoint > > The checkpoint command among other things reconnects OM p2p. The procedure > above is likely going to solve the problem without requiring a station > reboot. > > Checkpointing the source CP should not be necessary, but it shouldn't hurt > either. :) > > Regards, > > Alex Johnson > Invensys Operations Management > 10900 Equity Drive > Houston, TX 77041 > +1 713 329 8472 (desk) > +1 713 329 1600 (operator) > +1 713 329 1700 (Central Fax) > alex.johnson@xxxxxxxxxxxx > > > -----Original Message----- > From: Johnson, Alex P (IOM) > Sent: Monday, August 27, 2012 11:54 AM > To: 'foxboro' > Subject: RE: [foxboro] Peer to Peer connection good but not updating > > A reboot of both stations will definitely clear the OM lists out, but you > have to reboot both sides at once. > > Before you do that, would you: > > 1) Break the problem link or links > 2) Checkpoint > 3) Restore the problem link or links > 4) Checkpoint > > The checkpoint command among other things reconnects OM p2p. The procedure > above is likely going to solve the problem without requiring a station > reboot. > > > > Regards, > > Alex Johnson > Invensys Operations Management > 10900 Equity Drive > Houston, TX 77041 > +1 713 329 8472 (desk) > +1 713 329 1600 (operator) > +1 713 329 1700 (Central Fax) > alex.johnson@xxxxxxxxxxxx > > > -----Original Message----- > From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] > On Behalf Of Michael Kessler > Sent: Monday, August 27, 2012 11:46 AM > To: foxboro > Subject: [foxboro] Peer to Peer connection good but not updating > > I have some peer to peer connections between calcA blocks in ZCP's that are > not updating. (XXX.BO01 > YYY.BI01) I've deleted/undeleted the blocks, > with no success. Deleting the source block does not turn the sink point > Cyan which should normally be the case. > I am able to see the status of the source using omget. > I suspect corrupt OM lists. Will a re-boot clear these up or is a CP > initialize/loadall required? > > Anyone experienced this type of problem? > > mk > > > > > _______________________________________________________________________ > 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 > > > > *** Confidentiality Notice: This e-mail, including any associated or > attached files, is intended solely for the individual or entity to which it > is addressed. This e-mail is confidential and may well also be legally > privileged. If you have received it in error, you are on notice of its > status. Please notify the sender immediately by reply e-mail and then > delete this message from your system. Please do not copy it or use it for > any purposes, or disclose its contents to any other person. This email > comes from a division of the Invensys Group, owned by Invensys plc, which > is a company registered in England and Wales with its registered office at > 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). > For a list of European legal entities within the Invensys Group, please go > to http://www.invensys.com/en/legal/default.aspx. > > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail > reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries and > affiliates). > > > > > _______________________________________________________________________ > 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 > > -- Michael Kessler,P.Eng KIC Engineered Systems 435 Huron St, London, On N5Y 4J4 (519) 488-5317 Office (519) 672-2299 Fax www.kicsystems.ca _______________________________________________________________________ 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 _______________________________________________________________________ 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