Re: [foxboro] New topic: Gradual smurf all WP's
- From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 13:59:41 +1200 (NZST)
Robin,
What do you get when you do snoop from one of the AWs or WPs? Any traffic? If
you just want to count packets do "snoop -d hme0 -o /dev/null" on a D/E or
"snoop -d le0 -o /dev/null" for a B box.
What do netstat -i and ifconfig -a show from AW and/or WPs?
Does a workstation come back from a reboot still smurfed?
Are the workstations smurfed for data from all control stations or just from
particular ones?
You should be able to use a DNBT to connect a laptop to the nodebus, use CA or
CB as a letterbug (CA - listen on both, send on A). For snooping the network,
you can use any of a wide variety of sniff.exe or snoop.exe tools, however it's
very likely that these will be considered spyware by most corporate security
systems (for good reason - spyware often uses these tools for various nefarious
purposes). My personal preference is to use one of the Linux Live CDs with a
set of network tools (especially Ethereal) in a laptop for doing network
analysis and a memory stick or flash card for collecting the data and reports.
Foxboro have a good solution - a laptop with a version of NAI's Sniffer Pro with
drivers and tools specifically for sniffing the Nodebus - TAC or Fox Service
should have more details.
Regards,
Kevin FitzGerrell
Quoting "Burnham, Robin" <robin.burnham@xxxxxxxxxxxxxxxx>:
> Isolated nodebus with CP's and Gateways, 8 workstations. IA 4.3
>
> Apparent nodebus problem, One workstation starts smurfing and after a
> few
> days all workstations are smurfed. Everything is still green and CP's
> still
> going, just no interface to workstations.
> There are OM overruns and Mac Sublayer counts, CP OM overruns range
> from
> 23 to 264 for a 48 hour period.
> grep jabber on /var/adm came back with nothing.
>
> Thinking of snoop on Nodebus but due to a Comm10 connection that is
> only
> as good as the nodebus connection which is unreliable.
>
> Has anyone run a snoop from a laptop? If so, can you tell me how to
> connect?
>
> Anyone got anything?
>
> Any response is appreciated.
>
> Burnbomb
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Johnson, Alex P (IPS)
> Sent: Wednesday, September 27, 2006 3:22 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Display Manager fonts for FoxView
>
> Re: Also, a new 'feature' in our case seems to be an 'extra' window
> (minimized small in the upper left area of the desktop). It is non
> functional and there's nothing in it but you can't close it or
> otherwise
> get rid of it
> This issue came up as a CAR against FoxCTS somewhere or another. After
> some investigation, we received a copy of the following e-mail.
>
> ---------
> It seems that the little window in the top left hand corner of Foxview
> 9.02 is seen on more sites.
>
> The problem is this:
> If Foxview uses an environment that has the display bar at the left
> hand
> side disabled by putting the command "dmcmd display_bar off" in the
> *.env file AND also the reference to the display bar file
> "$ENV_DIR/Operator.dbr" is removed then the little window in the top
> left hand corner will appear.
>
> The workaround is to put the reference to the display bar file back in
> the *.env file: "$ENV_DIR/Operator.dbr".
>
> Even if this *.dbr file does not exist, the reference alone should be
> enough to make the little window disappear.
>
> The problem is also documented in car 1008496.
>
> Can you confirm that you are also seeing this problem?
>
> ------
>
> As you can see, it seems to be a specific combination of things. Try
> the
> fix.
>
>
> AJ
>
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx on behalf of Johnson, Theodore (Ted)
> S
> Sent: Wed 9/27/2006 12:35 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Display Manager fonts for FoxView
> =20
> Just an update for those who might be interested...
>
> We did not try to reconvert (second time) using the 9.0.2 utility
> because we felt at that time we had already 'invested' too much time
> into the graphics migration effort after the first conversion to start
> over.
>
> The FoxView 9.0.2 did solve some of our concerns (fast blink rate on
> colors is actually fast now, we use this to indicate at a glance which
> loops are in alarm; and rapid input via use of ramping arrow buttons
> works much better), however we still have issues with window sizing,
> fonts/readability, etc. Some of it seems to be product issues and some
> seem to be configuration related. Also, a new 'feature' in our case
> seems to be an 'extra' window (minimized small in the upper left area
> of
> the desktop). It is non functional and there's nothing in it but you
> can't close it or otherwise get rid of it.=3D20
>
> Foxboro personnel have left the site. I am told and being reassured by
> the folks in Foxboro Houston and our local service rep that they are
> working on all our issues with TAC and are doing some more testing
> before they return. We are trying to work through the 'proper channels'
> but are still waiting for final resolution.=3D20
>
> Meanwhile, we have reverted back (temporarily?) to using Display
> Manager. The workstations have been changed back to boot up into
> Display Manager instead of Foxview and the alarm annunciator keyboards
> have been reconfigured to call up the DM graphics (instead of
> FoxView).=3D20
>
>
> =3D20
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of tom.vandewater@xxxxxxxxxxxxxx
> Sent: Wednesday, August 30, 2006 6:40 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Display Manager fonts for FoxView
>
> Ted,
> Thanks for that information. Please let the list know if/when
> the new DM > FV conversion tool meets your expectation in regard to the
> font conversion issue.
> Cheers,
> Tom VandeWater
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Johnson, Theodore (Ted) S
> Sent: Tuesday, August 29, 2006 1:42 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Display Manager fonts for FoxView
>
> Over the last two years we have gone from 51B->F, v4.3->v7.1/8.1,
> cp30/40->CP60/270, legacy Historian->Aim*, Nodebus/CLAN->Mesh/ATS) and
> are now working on DM->FoxView. We have also experienced issues with
> fonts and other items not working/looking/acting the same after the
> conversion. Foxboro has had various folks (on & off site) working on
> our converted graphics so that they function as our operators
> rightfully
> expect them to. Fortunately DM and FoxView peacefully co-exist.
> Anyway, there are still a couple of things that we're hoping (led to
> believe) will be fixed in FoxView v9.0.2. We have just received a copy
> and a Foxboro engineer and field service rep are on-site
> testing/loading
> the new version.
>
> The FoxView v9.0.2 Release Notes (P/N B0193WL Rev L, dated July 18
> 2006) Section 6.1.2 (entitled 'DM Font Conversion') states on page 33:
>
> "Previously, when DM displays were converted to FoxView
> displays using conversion tools, the text indicated in displays were
> sometimes of incorrect size and misaligned. FoxView 9.0.2 includes the
> functionality to handle DM conversion correctly for Solaris platforms."
> =3D3D3D20
> Also FYI the release notes Appendix B (entitled 'Problems Resolved in
> V9.0.1') details 70 items (mainly CARs) in FoxView (40), FoxSelect (1),
> FoxDraw (18), DEdit, (5), and Enhanced Detail Displays (6) that have
> been addressed.
>
> The User Notes are not yet posted on the Invensys GPS (ex-CSC) website
> (controlled release?), so check with your friendly neighborhood Foxboro
> service organization and/or call TAC.
>
> =3D3D3D20
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of stan
> Sent: Tuesday, August 29, 2006 12:40 AM
> To: Foxboro List
> Subject: [foxboro] Display Manager fonts for FoxView
>
> Does anyone know if anything ever came of the project to create a set
> of
> fonts for FoxView that matches the Display Manager fonts?
>
> We are converting one node, and th operators are complaining that the
> resultant converted graphics are hard to read.
>
> --
> Unix is very simple, but it takes a genius to understand the
> simplicity.
> (Dennis Ritchie)
> =3D3D3D20
> =3D3D3D20
> ________________________________________
> _______________________________
> 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
> =3D3D3D20
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: =3D3D3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Djoin
> to unsubscribe: =3D3D3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Dleave
> =3D 3D3D20
> =3D3D20
> =3D3D20
> ______________________________________________
> _________________________
> 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
> =3D3D20
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: =3D3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
> to unsubscribe: =3D3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
> =3D3D20
> =3D20
> =3D20
> ________________________________________________________
> _______________
> 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
> =3D20
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe: =3D
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
> =20
> =20
> __________________________________________________________________
> _____
> 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
> =20
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>
>
> -- No attachments (even text) are allowed --
> -- Type: application/ms-tnef
> -- File: winmail.dat
>
>
> =20
> =20
> _____________________________________________
> __________________________
> 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
> =20
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>
>
>
> ______________________________________________________________________
> _
> 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:
