Re: [foxboro] Nodbus Issues V7.1.1 and 6.5.2

  • From: Omprakash Raja Gopalan <omprakash.rajagopalan@xxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Mon, 9 Mar 2015 17:06:51 +0000

Scott/Rene
NIC/SCSI combo card is in slot 1 while slot 0 (bottom most) occupied by USB/HDI 
card. Cat 5 cable between RCNI and AW51G is P0971XM Rev F. Local field service 
visited many times collected nfd_log including the last week visit. Lastly we 
are asked to install QF1008295 and QF992053, I think2nd OF is no relevance to 
us (our hardware is AW51G, AW51B, WP51B). We do not have spare Ethernet/Serial 
splitter cable, do not see stations sending extreme amount of multicast 
messages, normally nfd_log entries are with TL layer request, but suddenly see 
burst of node bus requests with CRS error and finally CPs failures reported 
with no actual failures.

We are reviewing advisory 2007001abi in addition to the HH1050, FAQ621, FAQ631 
to draw the action plan.

Best Regards

G R OMPRAKASH 

  -----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Landry, Scott
Sent: Monday, March 09, 2015 3:58 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Nodbus Issues V7.1.1 and 6.5.2




   Is your RCNI connected to the NIC/SCSI combo card in Slot1 ?  should be 
using the hme interface not bge.

   I suggest that you have Foxboro Field Service or TAC closely analyze the 
nfd_log.

   Also, refer to HH1050, FAQ621 and FAQ662.  If you are using the Foxboro 
shielded Cat5 cable for your RCNI to
   AW51G connection, ensure it is RevC or higher for P0971XK, XL, XM and XN.
   The Ethernet/Serial splitter cable on the AW51G can be source of problem if 
the serial part of the cable is malfunctioning it
   is used to read the letterbug and switch the A and B connections from the 
RCNI to the NCNIs

   Also use SMDH performance counters  to look for stations with out of bounds 
errors in the MAC sublayer.

   Do you have any stations sending extreme amounts of multicast messages ?


    Regards,


     Scott

________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of 
Omprakash Raja Gopalan [omprakash.rajagopalan@xxxxxxxxxxxx]
Sent: Saturday, March 07, 2015 12:03 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Nodbus Issues V7.1.1 and 6.5.2

Hello List

We have configuration of AW51G running IA Batch V 8.1 (Unix) with CP40A/CP60 
cluster on node bus with RCNI/NCNI combination. AW IA version V 7.1.1, WPs 
style B at 6.5.2 and one AW style B at 6.5.2.

We are facing random CPs failure report at AW51Gwhich is default node bus 
master though CPs never failure actually. Look at its nfd_log files showed CRS 
error and cable faults. However when NFD master shifted to AW51B no CRS error 
and CP failures reported in the nfd_log file. Since IA Batch is running at 
AW51G we face lot of IA Driver error and many times batch manager got stopped.

We already tried changing AW51G, new RCNI, tried different location for NCNI in 
1X8 structure, replaced FO cable between RCNI & NCNI and those between 1X8 
structures with new end terminators. But situation remain the same.

It appears that node bus alarms in nfd_log with CRS errors due to version 
mismatches between both AW (7.1.1. and 6.5.2) as AW with 7.1.1 has/require 
faster diagnostic response compared to AW with 6.5.2. We tried workaround 
suggested by TAC to kill the nfd_8023 at AW51G but end up with all CPS actually 
failing !

Is  there anyone faced similar problem and suggest work around.

Best Regards

G R OMPRAKASH



_______________________________________________________________________
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 email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

*** 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 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: