RE: Adding new AW51E to nodebus
Hi Norm, I'm glad you mentioned the possibility of FBMs not matching the System Definition. I found four FBMs that don't exist, four extras, and one mislabled. I also looked at the new committal disk and found the following: -- NWFALT NWFALT NWFALT NWFALT NOTYET ba97 00 00 0 . . . 2CCAW1 2CCAW1 2CCAW1 ASMON6 AW51 PCHANG 74e1 00 00 0 . . . 2CCAW3 2CCAW3 2CCAW3 OS6AW1 AW51 NOTYET 7e64 00 00 0 2CCAW3 2CCAW3 2CCAW3 ASMDW6 AW51 NOTYET 7be5 00 00 0 2CCAW3 2CCAW3 2CCAW3 ARPWR6 AW51 NOTYET 24e5 00 00 0 2CCAW3 2CCAW3 2CCAW3 AICC6 AW51 NOTYET f7e5 00 00 0 2CCAW3 2CCAW3 2CCAW3 AH2006 AW51 NOTYET d0e4 00 00 0 2CCAW3 2CCAW3 2CCAW3 ADM6 AW51 NOTYET 5be5 00 00 0 2CCAW3 DM0025 DM0025 AADM6 -- NOTYET ae85 00 00 0 I did not find a NFD, but the rest looked OK. Thanks, Stephen Murray Asarco -Original Message- From: Tessier, Norm [mailto:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 1:29 PM To: 'Foxboro DCS Mail List' Subject: RE: Adding new AW51E to nodebus NFD is always 'NOTYET'. Watch out for anything else that may be different than you expect. 'NOTYET" in the wrong places will give unexpected results, and if Stations and/or FBMs and devices are not in the list, they may be deleted. This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by ASARCO Inc. unless expressly stated otherwise. --- 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: Adding new AW51E to nodebus
Hi Norm, The AW51B I plan to replace does not hold the CSA, but since the MAC address will change I would want to make sure that the CP's will be able to find and boot off the new AW51E. I do not know if I have to reboot the CPs right away or if they could stay on line for a few hours while I made sure the AW was working properly. I should be able to do the load-all prior to connecting the new AW to the node while I am loading the rest of the software and doing the loadh50 for the historian. Thanks, Stephen Murray Asarco -Original Message- From: Tessier, Norm [mailto:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 1:46 PM To: 'Foxboro DCS Mail List' Subject: RE: Adding new AW51E to nodebus Yes, if you are replacing the 'B' box the CPs and Gateways will all have to be rebooted. The 'E' box will have 'Initialized' day0 images for all of the hosted CPs and Gateways. These should have a 'LoadAll' done on an off-line test bed done for all of the CPs and Gateways. Do this with a SaveAll made after an UpLoad done just before you wish to change out the Host. If you cannot do this, a LoadAll must be performed on the running system for the Stations hosted by this 'E' box. It will require significantly more down time to do it on-line. CSA saves and merges may be required, as well. Especially if the 'B' box you are replacing hosts CSA. If it gets this complicated, you should get assistance from Field Service. Norm Tessier Regional Lifeline Specialist District 7 This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by ASARCO Inc. unless expressly stated otherwise. --- 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: Adding new AW51E to nodebus
Hi Norm, Thanks for your quick reply! Our system was upgraded in 1999 to I/A 6.1 and the System Definition has not been touched since then. The last reconcile log was 4-28-99, and I don't believe anything has changed since then, but I will grab a reconcile disk off one of the existing AW's to check against the reconcile disk off the new AW. I made two copies of all the existing System Definition files from 1999 just in case I hosed something up. I did not think about the possibility of wiping out any FBMs that may have been added since then, so I'm glad you warned me. I will compare the two reconciles against each other and against our running system. Thanks again, Stephen Murray Asarco -Original Message- From: Tessier, Norm [mailto:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 1:29 PM To: 'Foxboro DCS Mail List' Subject: RE: Adding new AW51E to nodebus If the committal you now have in hand was made from a 'reconciled System Definition', the install should be uneventful. I always tar the commit disk into a temporary directory (/opt/tmp). The files on the floppy are "." Relative, and if you cd to the temporary directory and do a 'tar xvf /dev/fd0' the files will load from there down. I then do a 'more' on the file called 'IIF.pkg'. This will give the 'status' of everything in the system (on the commit disk). The indicator in the files should be 'DONE' for all of the other stations and packages except the station with the System Monitor (smon should be 'PCHANG'). NFD is always 'NOTYET'. Watch out for anything else that may be different than you expect. 'NOTYET" in the wrong places will give unexpected results, and if Stations and/or FBMs and devices are not in the list, they may be deleted. I find it a good practice to do a 'reconcile' to the system before making any changes to the System Definition. This will insure that the proper 'current status' is reflected in the commit. I do this even when I believe that nothing has been done, but others have access to the system Norm Tessier Regional Lifeline Specialist District 7 -Original Message- From: Murray, Steve [SMTP:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 3:41 PM To: Foxboro DCS Mail List (E-mail) Subject:Adding new AW51E to nodebus Hi All, I am adding an AW51E to our existing 6.1 system. This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by ASARCO Inc. unless expressly stated otherwise. --- 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: Adding new AW51E to nodebus
Yes, if you are replacing the 'B' box the CPs and Gateways will all have to
be rebooted. The 'E' box will have 'Initialized' day0 images for all of the
hosted CPs and Gateways. These should have a 'LoadAll' done on an off-line
test bed done for all of the CPs and Gateways. Do this with a SaveAll made
after an UpLoad done just before you wish to change out the Host. If you
cannot do this, a LoadAll must be performed on the running system for the
Stations hosted by this 'E' box. It will require significantly more down
time to do it on-line.
CSA saves and merges may be required, as well. Especially if the 'B' box you
are replacing hosts CSA. If it gets this complicated, you should get
assistance from Field Service.
Norm Tessier
Regional Lifeline Specialist
District 7
-Original Message-
From: Tessier, Norm [SMTP:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 4:29 PM
To: 'Foxboro DCS Mail List'
Subject:RE: Adding new AW51E to nodebus
If the committal you now have in hand was made from a 'reconciled
System
Definition', the install should be uneventful. I always tar the
commit disk
into a temporary directory (/opt/tmp).
The files on the floppy are "." Relative, and if you cd to the
temporary
directory and do a 'tar xvf /dev/fd0' the files will load from there
down.
I then do a 'more' on the file called 'IIF.pkg'. This will give the
'status' of everything in the system (on the commit disk). The
indicator in
the files should be 'DONE' for all of the other stations and
packages except
the station with the System Monitor (smon should be 'PCHANG'). NFD
is always
'NOTYET'. Watch out for anything else that may be different than
you
expect. 'NOTYET" in the wrong places will give unexpected results,
and if
Stations and/or FBMs and devices are not in the list, they may be
deleted.
I find it a good practice to do a 'reconcile' to the system before
making
any changes to the System Definition. This will insure that the
proper
'current status' is reflected in the commit. I do this even when I
believe
that nothing has been done, but others have access to the system
Norm Tessier
Regional Lifeline Specialist
District 7
-Original Message-
From: Murray, Steve [SMTP:[EMAIL PROTECTED]]
Sent: Monday, April 02, 2001 3:41 PM
To: Foxboro DCS Mail List (E-mail)
Subject:Adding new AW51E to nodebus
Hi All,
I am adding an AW51E to our existing 6.1 system. Our
current
system
consists of four AW51Bs, four WP51Bs, and three X-terminals
on three
nodes
connected with a carrier band LAN.
I have updated the System Definition and created a new
committal
disk,
installed the 6.1 software on the new AW51E, and created the
reconcile disk.
I then installed FoxView 99.2.1.
I have done the installation in stand-alone mode (not
connected to
the
DNBI) and everything seems to be installed and working
correctly. I
now
want to plug the DNBI into the nodebus and connect the new
AW to the
DNBI.
*** A few questions ***
1. The Foxboro documentation covers installing or upgrading
the
entire
system, but I am just adding one AW. When do I use the new
committal disk
in the other existing AW/WPs? Before or after I plug the
new DNBI
and AW
into the nodebus?
The new AW will not host any CPs or WPs, so it might not
matter.
The
existing System Monitor that will be watching the new AW
does not
know about
it yet, so should I use the committal disk in at least that
AW prior
to
plugging in the new DNBI & AW? Or plug in the DNBI and boot
up the
new AW
first?
2. Will I have to reboot each of the other AWs & WPs after
running
the
committal disk through them? I am only adding a station and
not
upgrading
the I/A software, so I am unsure if I need to reboot the
existing
stations.
3. What should I look for to indicate problems on the
nodebus after
installing the new AW? I would rather see a problem
developing
before the
nodebus just locks up!
4. What
RE: Adding new AW51E to nodebus
If the committal you now have in hand was made from a 'reconciled System Definition', the install should be uneventful. I always tar the commit disk into a temporary directory (/opt/tmp). The files on the floppy are "." Relative, and if you cd to the temporary directory and do a 'tar xvf /dev/fd0' the files will load from there down. I then do a 'more' on the file called 'IIF.pkg'. This will give the 'status' of everything in the system (on the commit disk). The indicator in the files should be 'DONE' for all of the other stations and packages except the station with the System Monitor (smon should be 'PCHANG'). NFD is always 'NOTYET'. Watch out for anything else that may be different than you expect. 'NOTYET" in the wrong places will give unexpected results, and if Stations and/or FBMs and devices are not in the list, they may be deleted. I find it a good practice to do a 'reconcile' to the system before making any changes to the System Definition. This will insure that the proper 'current status' is reflected in the commit. I do this even when I believe that nothing has been done, but others have access to the system Norm Tessier Regional Lifeline Specialist District 7 -Original Message- From: Murray, Steve [SMTP:[EMAIL PROTECTED]] Sent: Monday, April 02, 2001 3:41 PM To: Foxboro DCS Mail List (E-mail) Subject:Adding new AW51E to nodebus Hi All, I am adding an AW51E to our existing 6.1 system. Our current system consists of four AW51Bs, four WP51Bs, and three X-terminals on three nodes connected with a carrier band LAN. I have updated the System Definition and created a new committal disk, installed the 6.1 software on the new AW51E, and created the reconcile disk. I then installed FoxView 99.2.1. I have done the installation in stand-alone mode (not connected to the DNBI) and everything seems to be installed and working correctly. I now want to plug the DNBI into the nodebus and connect the new AW to the DNBI. *** A few questions *** 1. The Foxboro documentation covers installing or upgrading the entire system, but I am just adding one AW. When do I use the new committal disk in the other existing AW/WPs? Before or after I plug the new DNBI and AW into the nodebus? The new AW will not host any CPs or WPs, so it might not matter. The existing System Monitor that will be watching the new AW does not know about it yet, so should I use the committal disk in at least that AW prior to plugging in the new DNBI & AW? Or plug in the DNBI and boot up the new AW first? 2. Will I have to reboot each of the other AWs & WPs after running the committal disk through them? I am only adding a station and not upgrading the I/A software, so I am unsure if I need to reboot the existing stations. 3. What should I look for to indicate problems on the nodebus after installing the new AW? I would rather see a problem developing before the nodebus just locks up! 4. What is the likelihood of causing problems on the nodebus with a new station? 5. After I get the bugs worked out of this new station I intend to replace an existing AW51B with another AW51E. That station WILL host CPs and WPs and have a System Monitor. Do I need to reboot each hosted CP during that process? 6. Any other tips or suggestions? Thanks, Stephen Murray Asarco [EMAIL PROTECTED] (520) 356-4230 This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by ASARCO Inc. unless expressly stated otherwise. --- 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 li
