Re: [foxboro] Running Manual Cable Test - Automatically?
- From: Barry Heap <Barry.Heap@xxxxxxxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 14 Feb 2013 15:55:04 +1100
Hi Russ,
I checked the "nbe_db.cfg" file in "/usr/fox/sp" and found the only line
to be "FOX_LI 1"
Now I am not sure if the should be "FOX_LI 0" .... but I note your
comment on NCNI's being nodebus extenders.
We DO have NCNI's in the system - we have a pair of NCNI's in each of
five 1x8 racks that connect back to our A/B nodebus switches (v7.x) ...
Our AW's and WP's connect via RCNI's back to the same switches ...
This was originally a 5 node CBLAN-connected system that was collapsed
into a single node a few years ago.
So .. in this topology, what should we be seeing in our nbe_cfg file?
If we should actually be seeing "FOX_LI 0", what should we do to correct
this?
Re: Regards,
Barry Heap
On 4/02/13 11:24 AM, Boulay, Russ wrote:
> The issue you are describing..."nodebus slowdown" under those descriptions
> sounds like false cable tests are being run.
> Often times this is caused by incorrectly configured nbe_db.cfg file in
> /usr/fox/sysmgm
> Depending on the Node structure the entries in this file are vital.
> And don't misinterpret what a Nodebus extension is...it doesn't just mean
> Nodebus Extenders...NCNI's between segments count as well.
>
> The file "nbe_db.cfg" is located in /usr/fox/sysmgm and comes from the
> committal install diskette generated by System Definition. This file is
> a global file and should be the same on every committed station in a
> system.
>
> Example 1:
> A "nbe_db.cfg" file containing four nodes with no Nodebus Extenders. The
> name for each node is the letterbug for the LAN of each node.
>
> 01CL01 0
> 02CL01 0
> 03CL01 0
> 04CL01 0
>
> Example 2:
> A "nbe_db.cfg" file containing four nodes with Nodebus Extenders on
> Nodes 1 and 3.
>
> 01CL01 1
> 02CL01 0
> 03CL01 1
> 04CL01 0
>
> Example 3:
> A "nbe_db.cfg" file for a single node system with no nodebus extenders.
>
> FOX_LI 0
>
> Example 4:
> A "nbe_db.cfg" file for a single node system with nodebus extenders.
>
> FOX_LI 1
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of Barry Heap
> Sent: Sunday, February 03, 2013 4:00 PM
> To: foxboro@xxxxxxxxxxxxx
> Cc: Goldie, Shaun S
> Subject: Re: [foxboro] Running Manual Cable Test - Automatically?
>
> Hi Shaun,
>
> Yes, the issue we have is stations being islanded ... and we have had an A/B
> crossover issue in the past, so we know the pain that this can cause.
>
> The current problem seems to be caused by a fleeting cable fault - in V6.x
> this would be rectified by the NFD (?) when it next determined that the cable
> was now good.
>
> It seems that V7.x uses the A/B cables differently - and handles the fault
> conditions (or the recovery at least) differently.
>
> This is not the only V7.x site that I have seen this behaviour - and the fix
> is always the same .. a Cable Test will fix it.
>
> It's bad enough when it happens during the day .. but worse if it results in
> a call-in. But it's a real concern when it shakes the Operator's confidence
> in the system.
>
> Thanks.
>
>
> Barry Heap
> Control Direction
>
> On 4/02/13 10:40 AM, Goldie, Shaun S wrote:
>> Hi Barry
>> We had strange problems on a V7 system that also led to islanding The
>> problem was an A/B Buss crossover, when a device fails the bus gets
>> told to switch and some were going to A while others were going to B
>> The node bus test looks like a fix because it brings both busses
>> online Shaun
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx
>> [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Barry Heap
>> Sent: Monday, 4 February 2013 12:30 PM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: [foxboro] Running Manual Cable Test - Automatically?
>>
>> Hi List,
>>
>> We have a V7.x site running with NCNI/RCNI and Enterasys switches as our
>> Nodebus.
>>
>> We have experienced the V7.x slowdown that seems to be caused by Cable
>> faults that may be fleeting or longer term. Either way, the first indication
>> we get is the Operators informing the site engineers that 'the screens are
>> running slow again'.
>>
>> The fix is to run a Manual Nodebus Cable test and the fault clears
>> immediately.
>>
>> My question is:
>>
>> Is it possible to schedule a 'manual' Cable test to be run automatically?
>>
>> I know it may be an odd request, but the V7.x systems just don't recover
>> themselves the way the old V6.x systems do .. and the screen slowdown is
>> causing some grief on site.
>>
>> Oh, a V8.x upgrade is not an option at this time, or the near future...
>>
>> Thanks.
>>
>>
>> Barry Heap
>> Control Direction
>>
>>
>> ______________________________________________________________________
>> _ 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
>>
>>
>>
>>
>> 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
>
>
>
> *** 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 3rd Floor, 40
> Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of
> European legal entities within the Invensys Group, please select the Legal
> Entities link at invensys.com.
>
>
> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> reception@xxxxxxxxxxxx. 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
>
_______________________________________________________________________
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:
