In response to Gaylon, let me muddy the water a little more. "multicast rate limiting policies. Although it works fine, it doesn't (or didn't) fall under the umbrella of officially tested configurations." Or normal refer to Comix Multicast Suppression (CMS), CMS is based on internal policy commands of the switch and the multicast MAC addresses used. The policy commands allows the switch to rate limit the traffic on ingress ports, only the DFE-Gold and DFE-Platinum switches can support this function. Due to the importance of the multicast protocol within the network, blanket multicast rate suppression is neither recommended nor practical. However, the Comix Multicast protocol used primarily between the I/A workstation and Control Processors can be rate limited without a direct impact on the MESH Network, but this rate limiting must not impede the performance of I/A communications between the end devices, because of this concern, the minimum setting is 1Mbps. Since the CMS is based on internal policy commands of the switch and the multicast MAC addresses used, only the DFE-Gold and DEF-Platinum switches can support this function. Monitoring of this function when traffic exceeds the rate limit can only be performed on the DFE-Platinum series switches via the syslog or trap servers. This function has been officially tested however when the deployment of LDP occurred the configurator software tool had limitation on it ability to deploy both CMS and LDP this has since been corrected and will be available on the next release rev 3.1.2 Thank You Mike Davis -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Hicks, Gaylon F Sent: Monday, February 09, 2009 1:02 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] network storm Let me muddy the water a little (more). VLANs are supported by Foxboro, and are part of the MESH configurator tool, and a separate network using separate switch hardware for the ZCP fieldbus is an officially supported architecture. What is not an explicitly approved architecture is using VLANs to segment the ZCP field bus(es) from the control network, although functionally it is the same as the separate switch architecture. And by "explicitely approved" I mean it isn't a documented and tested configuration by Foxboro, although it is pretty obvious that it will, and does, work fine. The problem with the separate switches on the ZCP fieldbus is that you can't monitor those switches and ports in SMDH, where the VLAN solution does let you monitor those ports. The same goes for the multicast rate limiting policies. Although it works fine, it doesn't (or didn't) fall under the umbrella of officially tested configurations. Russ? - Would you or any of the other Foxboro folks care to weigh in on this? If I have mis-stated any of this, please do. For more light reading on the subject, you can take a look at these documents - B0700AX-H - The MESH Control Network System Planning and Sizing B0700AZ-K - The MESH Control Network Architecture Guide B0700CA-H - The MESH Control Network Operation, and Switch Installation and Configuration Guide Thanks, Gaylon Hicks TVA - Browns Ferry -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jeremy Milum Sent: Saturday, February 07, 2009 4:03 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] network storm On Sat, Feb 7, 2009 at 12:01 PM, Boulay, Russ <russ.boulay@xxxxxxxxxxxxxxxx> wrote: > ** I'll have to give kudo's to Gaylon, as we reviewed his Mesh Network a few weeks back. > It was the cleanest running Mesh system that I have reviewed in the last few years. > Vlans for fieldbus, some broadcast limiting, Mesh was running at peak performance. many of the suggestions that Gaylan mentions are not supported by foxboro, yet he has the best network? that's a bit troubling. do you perhaps have some recommendations you could give us for setting up our mesh networks? _______________________________________________________________________ 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 and any associated files are intended solely for the individual or entity to whom they are addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Further, this e-mail and any associated files may be confidential and further may be legally privileged. This email is from the Invensys Process Systems business unit of Invensys plc which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Process Systems business group, please click here http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. If you have received this e-mail in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Thank you for your co-operation. You may contact our Helpdesk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@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