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

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

Oops - sorry, I read your reply better now - Understood the mesh host has
been re-committed and re-booted.
On Fri, Oct 9, 2009 at 12:47 PM, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>wrote:

> The mesh workstations have not been committed and rebooted?
>
> Need to commit and reboot the mesh workstations and then reboot the ATS
> modules - the ATS modules need to reload the new sta_bin info.
>
> Kevin
>
>   On Fri, Oct 9, 2009 at 12:41 PM, Redmond, Sean S <
> Sean.Redmond@xxxxxxxxxxxxxxxxxx> wrote:
>
>> Hi Russ,
>>
>> The NB ipaddress changed in the node 2 ATS, the info in the PDA looked ok.
>>  All but two mesh workstations have been recommitted.  The host mesh
>> workstation has been committed.
>>
>> The arp table looks strange though, whenever I ping something off node the
>> mac address of that device is the mac address of 00:00:6c:00:01:ff which is
>> the mac address of BOTH ATSi nodebuses.
>>
>> M0AP01#arp -a
>> Net to Media Table
>> Device   IP Address               Mask      Flags   Phys Addr
>> ------ -------------------- --------------- ----- ---------------
>> hme2   152.153.17.5         255.255.255.255       08:00:20:a9:ed:ff
>> hme0   151.128.8.77         255.255.255.255       00:00:6c:00:01:ff
>> hme0   K0AW01               255.255.255.255       00:00:6c:00:01:ff
>> hme0   K0WP04               255.255.255.255       00:00:6c:00:01:ff
>> hme0   IMAW01               255.255.255.255       00:00:6c:00:01:ff
>> hme2   router               255.255.255.255       00:0f:90:51:e8:e1
>> hme2   152.153.17.22        255.255.255.255       00:01:03:44:94:e9
>> hme2   SPAREAP              255.255.255.255 SP    08:00:20:89:85:94
>> hme2   152.153.17.7         255.255.255.255       00:03:ba:5c:bc:d5
>> hme0   M0AP01               255.255.255.255 SP    08:00:20:89:85:94
>> hme0   151.128.16.129       255.255.255.255       00:00:6c:00:01:ff
>> hme2   224.0.0.0            240.0.0.0       SM    01:00:5e:00:00:00
>> hme0   224.0.0.0            240.0.0.0       SM    01:00:5e:00:00:00
>>
>> pinging k0aw01 k0wp01 (node 2 stataions) does not work while pinging
>> imaw01 (P91) does work
>>
>> Sean
>>
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> On Behalf Of Boulay, Russ
>> Sent: Friday, 9 October 2009 4:12 PM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] IP Communications node-mesh-node
>>
>>
>>  perform a pda status read of the Node 2 ATS to see if it has the right
>> info in it...
>>
>> Also after making the change has all workstations been recommitted...
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> On Behalf Of Goldie, Shaun S
>> Sent: Thursday, October 08, 2009 10:48 PM
>> To: 'foxboro@xxxxxxxxxxxxx'
>> Subject: Re: [foxboro] IP Communications node-mesh-node
>>
>> 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
>>
>>
>>
>>
>>  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