save_all.sh failers on new node
One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 DONE 6 EXIT CP0102!: Thu May 3 08:52:12 2001 upload/checkpoint Complete Save_all for CP0102 started Save-all for CP0102 successfully completed. # # Save_all starting for: AB0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:52:33 GMT 2001 --- upload and checkpoint AB0101 DONE 1 OPEN AB0101!: Thu May 3 08:52:33 2001 DONE 2 UPLOAD AB0101!: Thu May 3 09:16:33 2001 DONE 3 SHRINK AB0101!: Thu May 3 09:16:34 2001 DONE 4 CHECKPOINT AB0101!: Thu May 3 09:19:49 2001 DONE 5 CLOSE AB0101!: Thu May 3 09:19:49 2001 DONE 6 EXIT AB0101!: Thu May 3 09:19:49 2001 upload/checkpoint Complete Save_all for AB0101 started There were errors for AB0101. FAIL 1 open AB0101!: Thu May 3 09:19:50 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem # # Save_all starting for: FOXW01 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 09:19:58 GMT 2001 --- upload and checkpoint FOXW01 FAIL 1 OPEN FOXW01!: Thu May 3 09:19:58 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem DONE 6 EXIT FOXW01!: Thu May 3 09:19:58 2001 upload/checkpoint Complete Save_all for FOXW01 started There were errors for FOXW01. FAIL 1 open FOXW01!: Thu May 3 09:19:59 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem # # Automatic save-all procedure finished # Date:Thu May 3 09:20:07 GMT 2001 # Can anyone provide any insight as to where to start troubleshooting this? -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings
Re: CP30 to CP60 upgrade
We have two FT pair of CP60s installed in our operating units and in both cases the Fieldbus has caused us numerous headaches until we figured out the correct installation. In fact we are still having some problems. We thought the coax ethernet cabling would be easy, but we discovered otherwise. We have seen a lot of problems similar to yours. The coax ethernet installation is very different from the previous Fieldbus cabling. Basis our experience, the way the terminators were installed or connection problems, is our best guess as to the source of your problem.Here is what some of what we have learned the hard way: 1. Don't branch (split) the coax ethernet signal with tees. Wire in a serial path - go in one leg of a FBI10E and then out the other (every FBI10E has 2 cables). Put a terminator only at the end of the serially wired leg. There should be only a total of 2 terminators on each coax Fieldbus (A/B) segment - one is probably at the CP end and the other is probably at the field (FBM) end. 2. If you are using coax to fiber media converters, the BNC connection at each of the media converters has to be terminated. In our case using the Black Box media converters provided by Foxboro, we had to put a tee with a terminator. 3. We have a CP60FT installation that connects via coax to about 17 old style FBMs using 3 pair of FBI10Es (3 different Field8 enclosures). These have not been a problem after we got the terminators and Fieldbus cabling installed correctly. 4. We have another CP60FT installation that connects to about 26 old style FBMs (in an IE32) using a pair of FBI10Es and four 200 series I/O using a pair of FCMs. A fiber optic segment (using 2 coax to fiber media converters each) is used in the middle of each of the Fieldbus A B cabling. This installation has been a very big headache. Now that we are cabled serially and have terminators installed in the correct places, we are still experiencing intermittent Fieldbus B problems (usually only with the 200 series I/O which is at the end of the leg). We punted on the problem and called in Foxboro yesterday to look at it, the only thing noticeably wrong with the installation is that we need a newer rev of Fieldbus terminators that go on the 200 series I/O back plate. I am not sure if the new terminators will solve our problem, but I hope so. One of the early problems with this installation was that we had problems with some of the FBMs in the IE32 enclosure and it was before we installed the 200 series I/O segment. The FBMs in the enclosure were originally split between 2 pair of FBI10Es and they were cabled serially. To solve the problem, I removed 1 pair of FBI10Es and used local extension cables to connect the Fieldbus in the upper portion of the cabinet to the lower portion of the cabinet. Once we added the 200 series I/O then we had a new set of problems. 5. Is your Fieldbus properly terminated within your I/O rack/enclosure. If it is not properly terminated, you are more apt to have a problem with the new Fieldbus than you previously did with the older slower one. 6. A bad coax terminator or tee could cause the problem. I have heard of a few problems with the FBI10E heads - I guess the cables might get strained. 7. Depending on your available slots, the number of FBMs involved, and the number of different remote Fieldbus connections involved, I have found that you can keep the old Fieldbus intact on the back end and only convert the front end (CP end) by using both a Fieldbus Isolator and a FBI10E. For instance, you can take a I/O rack and put an FBI10E in slot 1 and a FBI in slot 2. Wire the FBI10E to your CP60 and wire your FBI to the old style FBMs with the old style Fieldbus cabling. Even if Foxboro supported this arrangement, they would probably tell you not to have communications for more than 21 FBMs going through a single FBI. I hope there is something in this list that can help you. Campbell John C [EMAIL PROTECTED] To: Foxboro Casandra (E-mail) Sent by: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: oject.org Subject: CP30 to CP60 upgrade
RE: Remote Displays using Exceed
We have been using eXceeds for years now without to many problems. The only issues we have had, occurred with some changes Hummingbird has implemented in various software revs. Exceed has been installed on a number of PCs that have Windows2000 with out any problems and we still use the original xstart script we developed years ago. If you are getting connection closed it would indicate a security issue. My first question would be was the IP address of the PC being upgraded change? If this was a base install versus and upgrade from NT 4.0 then the IP address might have changed. Does the site use DHCP or static IP addresses? If static was the same IP address reassigned to the back to the upgraded PC? Do you use the IP address versus the domain name for security validation? There are a number of addition things might effect security but it would be helpful to get a better understanding in how clients are validated by the Foxboro Sun boxes. -Original Message- From: Joe Gale (MP) [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 5:27 AM To: Foxboro DCS Mail List (E-mail) Subject: Remote Displays using Exceed We have been using exceed for years to open remote display managers using the telnet start method without much for problems. The IT people have been upgrading the PC's in the plant with new PC's that are running Windows2000 and have been having problems opening a DM after installing exceed. Several have worked by installing exceed while logged in as Power User, while some didn't work that way either. The error they get is a connection closed(3) when trying to open a DM. They are able to open a x-window into another application (a unit optimization program) running on a non Foxboro sun box without a problem. The new installs are using the same xstart and xconfig setups as the older installs are using. Does anyone have any ideas on what may be the conflict here? Thank You, Joe Gale DCS Administrator Minnesota Power Boswell Energy Center --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] The information in this email, and in any attachments, may contain confidential information and is intended solely for the attention and use of the named addressee(s). It must not be disclosed to any person without authorization. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are not authorized to, and must not, disclose, copy, distribute, or retain this message or any part of it. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: save_all.sh failers on new node
Hi Stan, Wat type of module is the FoxWatch module? I would not expect a comms processor to be in /etc/cplns on the system. (FOXWATCH is usually a COMM10 and does not contain a control database) Was the system configuration passed through all stations? (just to sync the system files like /etc/cplns, /etc/aplns, the hosts table, System Monitor files and the like, on all of them). I do not have an Allen-Bradly station at hand and of course the thing you cannot test will fail! Can it be CSA died on you? I will have to check tomorrow since I don't have a lab at home, sorry. The log will be of some help. Ron Deen@home Stan Brown wrote: One of the other groups here, has just put in a new Foxboro node, and I was seting up save_all.sh to autobackup the control config's for them. However, much to my suprise it failed to bacxkup the AB integrator, and FoxWatch modules on that node. Her's the log: Save-all for all stations in /etc/cplns selected Stations selected for save_all: Station Host name CP0101 AW0101 CP0102 AW0101 AB0101 AW0101 FOXW01 AW0101 Checking directories... Creating directory /opt/SAVEALLS Creating directory /opt/SAVEALLS/backup Creating directory for CP0101... Creating directory for CP0102... Creating directory for AB0101... Creating directory for FOXW01... All directories OK. Checking for available diskspace Available space on system: 12910445 Space required on system: 8000 Enough space available, continuing... # # Automatic save-all procedure started # Date: Thu May 3 07:58:48 GMT 2001 # Started on: AW0101 # Save-all Location: /opt/SAVEALLS # Backup location:/opt/SAVEALLS/backup # # # Save_all starting for: CP0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 07:58:48 GMT 2001 --- upload and checkpoint CP0101 DONE 1 OPEN CP0101!: Thu May 3 07:58:48 2001 DONE 2 UPLOAD CP0101!: Thu May 3 08:30:25 2001 DONE 3 SHRINK CP0101!: Thu May 3 08:30:27 2001 DONE 4 CHECKPOINT CP0101!: Thu May 3 08:32:57 2001 DONE 5 CLOSE CP0101!: Thu May 3 08:32:57 2001 DONE 6 EXIT CP0101!: Thu May 3 08:32:57 2001 upload/checkpoint Complete Save_all for CP0101 started Save-all for CP0101 successfully completed. # # Save_all starting for: CP0102 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:33:22 GMT 2001 --- upload and checkpoint CP0102 DONE 1 OPEN CP0102!: Thu May 3 08:33:22 2001 DONE 2 UPLOAD CP0102!: Thu May 3 08:51:03 2001 DONE 3 SHRINK CP0102!: Thu May 3 08:51:04 2001 DONE 4 CHECKPOINT CP0102!: Thu May 3 08:52:12 2001 DONE 5 CLOSE CP0102!: Thu May 3 08:52:12 2001 DONE 6 EXIT CP0102!: Thu May 3 08:52:12 2001 upload/checkpoint Complete Save_all for CP0102 started Save-all for CP0102 successfully completed. # # Save_all starting for: AB0101 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 08:52:33 GMT 2001 --- upload and checkpoint AB0101 DONE 1 OPEN AB0101!: Thu May 3 08:52:33 2001 DONE 2 UPLOAD AB0101!: Thu May 3 09:16:33 2001 DONE 3 SHRINK AB0101!: Thu May 3 09:16:34 2001 DONE 4 CHECKPOINT AB0101!: Thu May 3 09:19:49 2001 DONE 5 CLOSE AB0101!: Thu May 3 09:19:49 2001 DONE 6 EXIT AB0101!: Thu May 3 09:19:49 2001 upload/checkpoint Complete Save_all for AB0101 started There were errors for AB0101. FAIL 1 open AB0101!: Thu May 3 09:19:50 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem # # Save_all starting for: FOXW01 on AW0101 # No previously stored save-all found to backup. Continuing... Starting upload/checkpoint... Thu May 3 09:19:58 GMT 2001 --- upload and checkpoint FOXW01 FAIL 1 OPEN FOXW01!: Thu May 3 09:19:58 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem DONE 6 EXIT FOXW01!: Thu May 3 09:19:58 2001 upload/checkpoint Complete Save_all for FOXW01 started There were errors for FOXW01. FAIL 1 open FOXW01!: Thu May 3 09:19:59 2001 -14 ICCopen error: class= 1 error= 0 text= icConnectCp: icCpConnect problem # # Automatic save-all procedure finished # Date:Thu May 3 09:20:07 GMT 2001
Re: AW: AW: Problems with concatenated and mirrored disks on AW51B
I am surprised that Foxboro support did not tell you to do a dft replace_sys ESPx SCSI3 this is a front end command to the metareplace command that is mentioned in the output. wb From: Weiss, Andreas [EMAIL PROTECTED] Reply-To: Foxboro DCS Mail List [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Subject: AW: AW: Problems with concatenated and mirrored disks on AW51B Date: Thu, 3 May 2001 09:44:52 +0200 MIME-Version: 1.0 Received: from [64.212.3.197] by hotmail.com (3.2) with ESMTP id MHotMailBCBA577900504004375440D403C5CE860; Thu May 03 00:45:02 2001 Received: from erdoelchemie.de by lists.CyberSpaces.net with SMTP; Thu, 3 May 2001 00:44:57 -0700 From [EMAIL PROTECTED] Thu May 03 00:46:22 2001 Message-ID: [EMAIL PROTECTED] X-Mailer: Internet Mail Service (5.5.2653.19) Sender: [EMAIL PROTECTED] Precedence: Bulk List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc. List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] Thanks a lot!!! E5511U# metastat d0 d0: Mirror Submirror 0: d10 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 76000 blocks d10: Submirror of d0 State: Needs maintenance Invoke: after replacing Maintenance components: metareplace d0 c0t3d0s0 new device Size: 76000 blocks Stripe 0: Device Start Block Dbase StateHot Spare c0t3d0s0 0 NoLast Erred EC Erdoelchemie GmbH Abt. PLS Andreas Weiss Geb. P13 Alte Str. 201 50769 Koeln Tel.: +49-2133-55-7804 Fax: +49-2133-55-7133 mailto:[EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: Warren Brown [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 2. Mai 2001 16:38 An: [EMAIL PROTECTED] Betreff: Re: AW: Problems with concatenated and mirrored disks on AW51B What kind of results do you get when you type metastat d0 this will print out a more detailed set of diagnostics that may give a clue as to what is going wrong. Sounds like a d/b needs to be cleared and mirroring re-initiated to me. warren From: Weiss, Andreas [EMAIL PROTECTED] Reply-To: Foxboro DCS Mail List [EMAIL PROTECTED] To: 'Foxboro DCS Mail List' [EMAIL PROTECTED] Subject: AW: Problems with concatenated and mirrored disks on AW51B Date: Wed, 2 May 2001 12:14:32 +0200 MIME-Version: 1.0 Received: from [64.212.3.197] by hotmail.com (3.2) with ESMTP id MHotMailBCB9294E00B84004379140D403C5B9760; Wed May 02 03:15:44 2001 Received: from erdoelchemie.de by lists.CyberSpaces.net with SMTP; Wed, 2 May 2001 03:14:45 -0700 From [EMAIL PROTECTED] Wed May 02 03:17:36 2001 Message-ID: [EMAIL PROTECTED] X-Mailer: Internet Mail Service (5.5.2653.19) Sender: [EMAIL PROTECTED] Precedence: Bulk List-Software: LetterRip Pro 3.0.7 by Fog City Software, Inc. List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] Hi! We have also problems with the disks Partition Size Usage Status --- / 3507158% Nds_Maint /var 2667954% Nds_Maint /usr 578455 69% Nds_Maint /opt 1094414 68% Nds_Maint --- We have no solution. Regards, Andreas EC Erdoelchemie GmbH Abt. PLS Andreas Weiss Geb. P13 Alte Str. 201 50769 Koeln Tel.: +49-2133-55-7804 Fax: +49-2133-55-7133 mailto:[EMAIL PROTECTED] privat: mailto:[EMAIL PROTECTED] privat: http://www.sicherheitstraining.org -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 2. Mai 2001 11:58 An: [EMAIL PROTECTED] Betreff: Problems with concatenated and mirrored disks on AW51B Hello At our site we have an AW51B with 4x 2.1GB disks (2 concatenated main, 2 concatenated mirror). In addition we have one set of 2x 2.1GB disks spare; these are exchanged for safekeeping as a backup. Some time ago one of the disks (on ESP1) gave us problems while doing the mirroring process. (Error messages listed below) d5: d15: 6478240ESP0 / SCSI3 Okay d25: 6478240ESP1 / SCSI3 Nds_Maint I have tried to replace the disk several times(the disk has been given SCSI address 2 and 3 on ESP1). I have tried HH835, but I'm still having the same problem. The exchange disk is a 18.2GB 1rpm Disk UniPack purchased from a local vendor. The disk has been labeled and made to look like 2.1GB as prescribed by Foxboro. Foxboro recommends us at this time to exchange the 3 sets of concatenated disks with one single disk with a larger size. Has anyone solved a similar problem? Thanks for any response. Per-Erik -- Per-Erik
Re: /etc/wplns and /etc/aplns or Sigh... I fired off withoutthin king
There's always an excuse Ron Johnson, Alex (Foxboro) wrote: I forgot about AWs. Sigh... I'm in the UK, think I can blame jet lag? Regards, Alex Johnson 10707 Haddington Houston, TX 77043 713.722.2859 (office) 713.722.2700 (switchboard) 713.932.0222 (fax) [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Ron Deen [SMTP:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 6:41 PM To: Foxboro DCS Mail List Subject:Re: /etc/wplns and /etc/aplns The /etc/wplns file contains the logical names of the WP's on your system. The /etc/aplns contains (you might have guessed) the logical names of the AP in you system. If you have only AP's and WP's you would normally use the letterbug as the logical name. If you have AW's you have a problem: the AW containss a logical AP AND a logical WP and only one can be be letterbug name. This is why you may see strange names on you system. Some time you can have a letterbug AW0101 which will have aplns: AW0101 and wplns: AWWP01 for instance. Solved problem?? Ron Deen Stan Brown wrote: I have some utilites thta check varios system stauses on a given Foxboro node. I am trying to deploy these on a newly installed node, here. These utilites use the files /etc/wplns and /etc/aplns to determine what computers are supposed to exist on the node. On this node there seem to be 2 entries for non existent machines in /etc/wplns. Should this not be a reliable way to determine this? -- Stan Brown [EMAIL PROTECTED] 843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this
RE: CP30 to CP60 upgrade
Yes they were all updated. This doesn't seem to be the problem, but we'll keep checking. Thanks for your assistance. John I know all FBM's require EEPROM update for version 6.2.1. But you have done that I guess... Ron Deen Campbell John C wrote: We are currently upgrading one of our sites from a CP30FT to a CP60FT and are experiencing some difficulties. The actual upgrade went relatively smoothly but after the AW was placed back on line with the new CP60's we started to receive numerous fieldbus failure alarms (PIOBUS A/B) that would randomly come in and out. Sometimes we would have no alarms for about 1/2 hour and then continuous alarms for the next 20 minutes. There was no pattern as to when the alarms would occur. Occasionally when the alarms occurred we would lose communication to the fieldbus altogether (blue flu on the operator screen). Until we do some more detail investigations (with Fox Mass.) we have gone back to the old CP30 system. Has anyone else experienced similar problems and what did you do to get around it. Some back ground information: The switchover is being performed at the same time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system. All fieldbus modules are of the traditional rack mounted type (no din rail mounted modules). Much appreciation for any assistance. John Campbell Dofasco [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
/etc/wplns /etc/aplns
I have a question about /etc/wplns and /etc/aplns I have some scripts which check various things about a givrn Foxboro node, and mail the results to the people concerned. These scripts use /etc/wplns, and /etc/aplns respectivly to determine what wp's, and ap's should exist on a systesm (aw's appear in both). A new node is being started up, so I added these scripts to it. At this time, I found out there there are a couple of entries in /etc/wplns for machines (computers) taht don't even exist on this node! Is this normal? -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: AIM AT extraction
Stefano Persico wrote: Hi list is it possible to estract data from AIM*Historian samples and convert them in some easy format ( ASCII ) ??? In other words is it possible to read into an ms office application samples from AIM*AT ?? Thanks Have a look at gethist on the Cassandra site. It can extract data from AIM* to a text file. Be careful though. The version on the site is for the legacy historian and must be recompiled for AIM*. You can download a C compiler from www.sunfreeware.com if you don't already have it. Darryl Bond --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
RE: Monitoring system variables
Eudilson, You can try to use remv/remd tools Gook Luck Chiaju -Original Message- From: Eudilson Nunez Cossio [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 02, 2001 9:56 PM To: Foxboro DCS Mail List Subject: Monitoring system variables Hi, I would like to monitoring some variables supplied by SMDH. The idea is to read in a normal block like the AIN, the PERFormace of one station like a CP40, your SISTEM MANAGEMENT COUNTERS, in TRANSPORT LAYER, the value of DISCONNECT DUE TO ERRORS. Someone knows how to do this? Thanks in advance. --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
Re: CP30 to CP60 upgrade
I noticed you have CP60FT. The filedbus cabling can be confusing and you may have both fieldbusses connected to eachother. Take care of termination and as mentioned here: do not branch. Termination will not be correct. Only two must be installed per fieldbus. Ron Campbell John C wrote: Yes they were all updated. This doesn't seem to be the problem, but we'll keep checking. Thanks for your assistance. John I know all FBM's require EEPROM update for version 6.2.1. But you have done that I guess... Ron Deen Campbell John C wrote: We are currently upgrading one of our sites from a CP30FT to a CP60FT and are experiencing some difficulties. The actual upgrade went relatively smoothly but after the AW was placed back on line with the new CP60's we started to receive numerous fieldbus failure alarms (PIOBUS A/B) that would randomly come in and out. Sometimes we would have no alarms for about 1/2 hour and then continuous alarms for the next 20 minutes. There was no pattern as to when the alarms would occur. Occasionally when the alarms occurred we would lose communication to the fieldbus altogether (blue flu on the operator screen). Until we do some more detail investigations (with Fox Mass.) we have gone back to the old CP30 system. Has anyone else experienced similar problems and what did you do to get around it. Some back ground information: The switchover is being performed at the same time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system. All fieldbus modules are of the traditional rack mounted type (no din rail mounted modules). Much appreciation for any assistance. John Campbell Dofasco [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
AIM AT extraction
Hi list is it possible to estract data from AIM*Historian samples and convert them in some easy format ( ASCII ) ??? In other words is it possible to read into an ms office application samples from AIM*AT ?? Thanks --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
RE: AW: AW: Problems with concatenated and mirrored disks on AW51 B
Hi All, We have two AWs with mirrored concatenated drives. I got curious yesterday and ran dft show_status was amazed and embarrassed to find one of the AWs had been un-mirrored for quite some time. I read HH745 and HH835, the entire section on mirrored drives in the Foxboro System Admin Guide (BO193ND rev F), and was still a bit mystified. I then went to the Sun documentation web site at docs.sun.com and found a few manuals on the DiskSuite software. I'm not sure what version of DiskSuite we have but the manual for 4.0 looked pretty good. The main thing I was looking for was an explanation of Needs Maintenance, and I found the following: Okay - The component is operating properly. Resyncing - The component is actively being resync'ed. Maintenance - The component has encountered an I/O error or an open error. All reads and writes to and from this component have been discontinued. See Replacing and Enabling Submirror Components on page 96 for information on component replacement. Last Erred - The component has encountered an I/O error or an open error, however, the data is not replicated elsewhere due to another component failure. I/O is still performed on the component. If I/O errors result, the mirror I/O will fail. See Replacing and Enabling Submirror Components on page 96 for information on component replacement. The entire manual can be viewed online or apparently downloaded as a pdf file and is chock-full of information. On our AW metastat -t showed one submirror needing maintenance on each metamirror, and I tracked the date down to a day when we did a dump 0 on the AW. I used the procedure in HH835 to metadetach each Nds_Maint submirror from its metamirror, and then metattach it back. The entire procedure took about 45 minutes because I waited until each submirror was resynced before doing the next one. Everything seemed to go well and the different status checks (dft show_status, metastat -t, metadb -i) indicate everything is mirrored and okay. I guess mirroring will be added to my list of gotchas to monitor from now on! Thanks for tipping me off to a problem I had, Steve Murray Asarco -Original Message- From: Warren Brown [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 03, 2001 11:16 AM To: [EMAIL PROTECTED] Subject: Re: AW: AW: Problems with concatenated and mirrored disks on AW51B I am surprised that Foxboro support did not tell you to do a dft replace_sys ESPx SCSI3 this is a front end command to the metareplace command that is mentioned in the output. wb From: Weiss, Andreas [EMAIL PROTECTED] Thanks a lot!!! E5511U# metastat d0 d0: Mirror Submirror 0: d10 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 76000 blocks d10: Submirror of d0 State: Needs maintenance Invoke: after replacing Maintenance components: metareplace d0 c0t3d0s0 new device Size: 76000 blocks Stripe 0: Device Start Block Dbase StateHot Spare c0t3d0s0 0 NoLast Erred --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
RE: CP30 to CP60 upgrade
We use single CP60's and got the same problem (we are using 200 series I/O) the problem went away when we went to 24 FBM's. When we had 23 FBM's the fault was as you explained regardless of FBM location. The errors predominantly reported to an individual location and usually to a FBM204 (output fbm) We have 4 identical process streams and the symptom was the same on all 4 I sent off CAR#1001152 and the reply stated the errors are not a problem and the fix would be in 6.3 The errors are a problem as they make the system button flash While I am mentioning FBM204's I have found 50% are not up to calibration specification -Original Message- From: Campbell John C [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 12:44 AM To: Foxboro Casandra (E-mail) Subject: CP30 to CP60 upgrade We are currently upgrading one of our sites from a CP30FT to a CP60FT and are experiencing some difficulties. The actual upgrade went relatively smoothly but after the AW was placed back on line with the new CP60's we started to receive numerous fieldbus failure alarms (PIOBUS A/B) that would randomly come in and out. Sometimes we would have no alarms for about 1/2 hour and then continuous alarms for the next 20 minutes. There was no pattern as to when the alarms would occur. Occasionally when the alarms occurred we would lose communication to the fieldbus altogether (blue flu on the operator screen). Until we do some more detail investigations (with Fox Mass.) we have gone back to the old CP30 system. Has anyone else experienced similar problems and what did you do to get around it. Some back ground information: The switchover is being performed at the same time as a revision upgrade from 6.1 to 6.2.1 on a AW/WP51B system. All fieldbus modules are of the traditional rack mounted type (no din rail mounted modules). Much appreciation for any assistance. John Campbell Dofasco [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED] --- This list is neither sponsored nor endorsed by the Foxboro Company. All postings from this list are the work of list subscribers and no warranty is made or implied as to the accuracy of any information disseminated through this medium. By subscribing to this list you agree to hold the list sponsor(s) blameless for any and all mishaps which might occur due to your application of information received from this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] with unsubscribe foxboro in the Subject. Or, send any mail to [EMAIL PROTECTED]
