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

  • From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Fri, 9 Oct 2009 12:06:17 +0900

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:

> Well that did not work
> Node 1 NSAP is I0001 node 2 is I0102
> Node 2's IP addresses start at 16.129
> Now both nodes can ping the opposite ATS mesh IP address but nothing on the
> opposite node
>
> Re my other question to the list we havent eliminated the switch
> configuration but its unlikley
> Shaun
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Boulay, Russ
> Sent: Friday, 9 October 2009 13:03
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] IP Communications node-mesh-node
>
> To make this work now...the Node with 001 can stay...
> The one with 002 needs to become 102 ...as well as it's ATS
>
> Can't have 001 and 101 co-exists
>
>
>
>  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

Other related posts:

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