[foxboro] FW: system management can't communicate with the current CLAN initiator

Thank you Mr. Kevin for your reply

Our architecture is 10 nodebus nodes which has an extended nodebus in CCR and 
they are connected through fiber optic by using FONBE in both sides. CCR nodes 
are connected to CLAN by using DCLIFT.
Normally the traffic in all PIB's are within average of 200 PCKT except two 
node which reached up to 700 PACT which causing freezing the CCR consoles to 
maximum 20 min. and we have 4 times freezing issue.
Each node has system monitor but now I can't initiate a cable test initiator or 
change the current initiator.
I found the current initiator by using (glof -p TBMSTR0001) and I reboot the 
current initiator (both CLAN FT cards) in same time and as a result of that the 
current initiator transferred to another node but the standing alarms still 
coming in all nodes.

the time stamp for PI server had been modified and this modification limited 
the high traffic to maximum 400 PACKT which was before modification reached up 
to 700 PACKT. We have Aspetech application but it is in another node which is 
normal.

We don't have any history of high traffic and/or LAN problems it just started 
since August 2008.

How I can look for what could have suddenly caused either high traffic or noise?

Are the points 2 & 3 will solve the issue the standing repeating alarms (MTBM 
NF8024 -00021 Failed takeover attempt by tokenbus master) & (CFRDF NF8024 
-00021 Failed takeover attempt by tokenbus master)?

Regards
Hani Ahmari


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Kevin Fitzgerrell
Sent: Monday, June 08, 2009 2:16 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] system management can't communicate with the current 
CLAN initiator

Hani,
What is your architecture?
How many nodes?
Copper, fiber or both?  Passive hubs?  Active concentrators?  Copper/fiber
converters?  Splitter/combiners?
How much traffic on each node (PDUS30 counter on each cblan)?
Do you have a system monitor on each node?

Yes, it is likely that the problem you are seeing is a result of high
traffic, possibly exacerbated by noise or fault condition.

Some ways to deal with this situation:
1) determine who is the cable test initiator and do a cable test from a
system monitor in that node
2) reboot all LAN modules (both sides together if FT) and see if you
recover.
3) try completely shutting down either the A or B side of the network and
run your LAN modules single - may be able to reduce NFD traffic by
simplifying the network.
4) shut the LAN down completely and build it back up one node at a time -
preferably from most to least important - until you hit the maximum
sustainable traffic level, or locate a fault

If traffic is high, try to reduce unnecessary traffic - if PI/Aspentech are
collecting data across nodes, shutting down the data collection may allow
you to bring the LAN up.

Have you had a history of high traffic and/or LAN problems?  If you have had
no problems previously, look for what could have suddenly caused either high
traffic or noise.

Regards,

Kevin FitzGerrell

On Mon, Jun 8, 2009 at 1:38 PM, Ahmari, Hani A <hani.ahmari@xxxxxxxxxx>wrote:

> There are standing alarms coming in all nodes every 5 minutes states that
> (MTBM NF8024 -00021 Failed takeover attempt by tokenbus master), and the
> reason of these alarms is the high traffic which is generating from one
> node. And also there is a problem with system management states that the
>  system management can't communicate with the current CLAN initiator and due
> of that; RUN CARREIER BAND CABLE TEST and CHANGE CARRIER BAND TEST INITIATOR
> cannot be executed.
> Is the problem of the system management is a result of high traffic?
>
> I need your support to resolve the issue of the system management can't
> communicate with the current CLAN initiator?
>
> Regards
> Hani
>
>
> ________________________________
> The contents of this email, including all related responses, files and
> attachments transmitted with it (collectively referred to as "this Email"),
> are intended solely for the use of the individual/entity to whom/which they
> are addressed, and may contain confidential and/or legally privileged
> information. This Email may not be disclosed or forwarded to anyone else
> without authorization from the originator of this Email. If you have
> received this Email in error, please notify the sender immediately and
> delete all copies from your system. Please note that the views or opinions
> presented in this Email are those of the author and may not necessarily
> represent those of Saudi Aramco. The recipient should check this Email and
> any attachments for the presence of any viruses. Saudi Aramco accepts no
> liability for any damage caused by any virus/error transmitted by this
> Email.
>
>
>
> _______________________________________________________________________
> 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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave


The contents of this email, including all related responses, files and 
attachments transmitted with it (collectively referred to as "this Email"), are 
intended solely for the use of the individual/entity to whom/which they are 
addressed, and may contain confidential and/or legally privileged information. 
This Email may not be disclosed or forwarded to anyone else without 
authorization from the originator of this Email. If you have received this 
Email in error, please notify the sender immediately and delete all copies from 
your system. Please note that the views or opinions presented in this Email are 
those of the author and may not necessarily represent those of Saudi Aramco. 
The recipient should check this Email and any attachments for the presence of 
any viruses. Saudi Aramco accepts no liability for any damage caused by any 
virus/error transmitted by this Email.
 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: