Re: [foxboro] IP Communications node-mesh-node

  • From: "Jones, Shelby" <shelby.jones@xxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 9 Oct 2009 07:55:31 -0500

You can only have one ATS in extender mode, that is, on the same node as a LAN 
module; all others ATSs have to be in LI mode.

Shelby Jones
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Jack.Easley@xxxxxxxxxxxx
Sent: Friday, October 09, 2009 8:52 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IP Communications node-mesh-node

I probably dreamt it, but I vaguely remember something about only 1 ATS
per system. In other words, all Nodebus CBL Interfaces tied together,
all MESH segments tied together, and these two different networks
bridged with one ATS. This is how we ran for several years & everything
worked fine.

However, I see you already have the GURUs on board, so I'm probably
wrong (again).

Jack Easley
Sr. I&C Technician
Luminant Power, Martin Lake Plant
Phone 903.836.6241
jack.easley@xxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin Fitzgerrell
Sent: Thursday, October 08, 2009 10:57 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IP Communications node-mesh-node

Sean,
As mentioned yesterday, I did have a similar problem trying to merge one
node in.  I never did figure out what was wrong, couldn't leave it
flailing
long enough to troubleshoot.

Eventually, we went through the sysdef with a fine tooth comb, updated
switch firmware and configurations, tried again and everything worked.

While we were having problems:
IP comms from one node to the other via the mesh/ATS did not work.
System mgmt did work half-way - from the problem node we could see other
nodes on sysmgmt, but other nodes couldn't see the problem one.
Peer-to-peers from one node to the other across the mesh were
intermittent.
Traffic was high and there were many retries.

Note - your mac address being the same is normal - same behavior as
CBLAN.
As far as any given nodebus is concerned, there are the mac addresses on
the
node, and the mac address for everything else.

Good luck,

Kevin

On Fri, Oct 9, 2009 at 12:26 PM, Redmond, Sean S <
Sean.Redmond@xxxxxxxxxxxxxxxxxx> wrote:

> Kevin,
>
> Yes all those statements are correct.  It is very strange, I do not
> understand why foxboro comms are working ok, but IP comms is
struggling to
> go over two ATSi.
>
> Regards,
> Sean
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Kevin Fitzgerrell
> Sent: Friday, 9 October 2009 4:06 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] IP Communications node-mesh-node
>
> Shaun,
> The way things stand now:
> Your Mesh workstation can ping everything on both nodes?
> Your Node 001 can ping everything on it's node and can ping the Mesh
IP for
> the other ATS, but cannot ping anything on node 102 including the
Nodebus
> IP
> of the Node 102 ATS?
> Your Node 102 can ping everything on it's node and can ping the Mesh
IP for
> the other ATS, but cannot ping anything on node 001 including the
Nodebus
> IP
> of the Node 001 ATS?
> Is that right?
>
> Kevin
> On Fri, Oct 9, 2009 at 11:48 AM, Goldie, Shaun S <
> Shaun.Goldie@xxxxxxxxxxxxxxxxxx> wrote:
>
>
>
>
>  NOTICE - This message and any attached files may contain information
that
> is confidential, legally privileged or proprietary. It is intended
only for
> use by the intended recipient. If you are not the intended recipient
or the
> person responsible for delivering the message to the intended
recipient, be
> advised that you have received this message in error. Any
dissemination,
> copying, use or re-transmission of this message or attachment, or the
> disclosure of any information therein, is strictly forbidden.
BlueScope
> Steel Limited does not represent or guarantee that this message or
> attachment is free of errors, virus or interference.
>
> If you have received this message in error please notify the sender
> immediately and delete the message. Any views expressed in this email
are
> not necessarily the views of BlueScope Steel Limited.
>
>
>
_______________________________________________________________________
> 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
 
 
 
_______________________________________________________________________
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 Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
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

Other related posts:

  1. Home
  2. foxboro
  3. Archive
  4. 10-2009