Re: [foxboro] Software Install workaround?

I would have said the list is not accurate if QFs are installed by following the
instructions exactly.  Have a look at the following list:

03/01/04  20:27    Day0 for V6.4 *****
03/01/04  22:15   QF005346
-----------------------------------------------------
03/01/04   22:17  QF1005118       OS6AW1  K0175WP-A-7
----------------------------------------------------
04/15/04  13:19    Release Update for V6.5.1 *****
05/17/04  10:00   QF1003696      OS1C40    K0175VA-B-7
----------------------------------------------------
05/17/04  10:15   QF1003903B     OS6AW1    K0175DN-B-2
----------------------------------------------------
05/19/04  13:48    Release Update for V6.5.1 *****
DATE      TIME    QUICK FIX     PACKAGE   PART NUMBER
-----------------------------------------------------
05/20/04  09:30   QF1005606     OS6AW1    K0175DN-B-2
-----------------------------------------------------
05/20/04  09:32   QF1003903B     OS6AW1    K0175DN-B-2
----------------------------------------------------
05/20/04  09:52   QF1003696      OS1C40    K0175VA-B-7
----------------------------------------------------
05/20/04  10:26   QF10041      OS6AW1    K0175DN-B-2
----------------------------------------------------
11/08/04  13:29    Release Update for V6.5.1 *****
11/09/04  16:54    Release Update for V6.5.1 *****
11/10/04  10:47    Release Update for V6.5.1 *****
11/10/04  11:36    Release Update for V6.5.1 *****
05/12/05  14:50   QF10048      OS6AW1    K0175DN-B-2
----------------------------------------------------
05/12/05  14:51   QF1005606B    OS6AW1    K0175DN-B-2
------------------------------------------------------
05/12/05   14:53  QF2001685     OS6AW1    K0175DN-B-2
------------------------------------------------------
05/12/05  14:55   QF1005305     OS6AW1    K0175DN-B-2
-----------------------------------------------------
05/13/05  09:38    Release Update for V6.5.1 *****
09/20/05  15:40   QF2000489     OS6AW1    K0175DN-B-2
------------------------------------------------------
09/20/05  15:42   QF992053D      OS6AW1    K0175DN-B-2
----------------------------------------------------

So, QF005346 is QF1005346, but what are QF10041 and QF10048?  They should be
QF1004163 and QF1004890.  I've also seen QFs where the "B" on the end wasn't
included in the installed QF's list.  Many QFs install via TAR instead of
software install and so don't show up on the list.  Finally, just because a QF
is on the list doesn't mean it hasn't been written over by installing a
different QF with an older version of a file, or re-installing a package from CD
or diskette.

A number of the QFs install the same files at different revisions.  It is
critical to install the QFs in the right order so you end up with all the
correct QFs -- example:
QF1005621 is a new CP60 image
QF1006410 is a DIN FBM update, which overwrites the IOM files in the CP60 QF
with newer ones
QF1007016 is a modbus FBM update, which overwrites the IOM file for a 224 from
the DIN FBM version.

Another example is QF1003696 (CP60 OM fix) and QF1004163 (A station dumps),
which contain different versions of the same file.

Foxboro used to be pretty good about covering this sort of interaction between
QFs, but I haven't seen any mention of this on a QF recently.

What I've been doing recently is reviewing Foxboro's QFs and generating a list
of my site's "recommended QFs" about twice a year.  Then I write a script to
check the sums, what strings or revision levels of some of the files installed
by each QF so I can generate a report on each AW and WP, something like this:

P101AW# more qf_check.sh
echo "\nQF1003813 test (remv/remd)"
grep 3813 /usr/fox/sp/lastinst/QF_INFO
echo "should be 64655 1058"
sum /opt/rem/remv/remv
echo "should be  6605 554"
sum /opt/rem/remd/remd

echo "\nQF2000489 test (iccdrvr.tsk)"
grep 489 /usr/fox/sp/lastinst/QF_INFO
echo "should be 41282 376"
sum /opt/fox/ciocfg/api/iccdrvr.tsk

echo "\nQF1007016 test (fbm224)"
grep 7016 /usr/fox/sp/lastinst/QF_INFO
echo "should be 22454 383"
sum /usr/fox/sp/files/iom224

echo "\nQF1006127 test (aim apisvr.tcp)"
grep 6127 /usr/fox/sp/lastinst/QF_INFO
echo "should be 26246 1170"
sum /opt/aim/bin/apisvr.tcp

echo "\nQF1005971 test (MG30B)"
grep 5971 /usr/fox/sp/lastinst/QF_INFO
echo "should be 54627 2034"
sum /usr/fox/sp/files/OS1M3B

echo "\nQF1005621 test (New CP60 image)"
grep 5621 /usr/fox/sp/lastinst/QF_INFO
echo "should be QF1005621   CP60  2-08-05"
what /usr/fox/sp/files/OS1C60 | head -4

echo "\nQF1004163 test (A style dumps)"
grep 4163 /usr/fox/sp/lastinst/QF_INFO
echo "should be 14448 290"
sum /usr/fox/exten/upload_srvr
echo "should be 21738 128"
sum /usr/fox/sp/files/eu_gw30.bin
echo "should be 29518 128"
sum /usr/fox/sp/files/eu_c40.bin

echo "\nQF991274D test (Backups)"
echo "should be 56294 17"
sum /usr/local/backup

echo "\nQF992053D test (hme driver)"
grep 2053D /usr/fox/sp/lastinst/QF_INFO
echo "should be hme.c 1.92"
what /kernel/drv/hme | head -4

etc...


Regards,

Kevin FitzGerrell
Carter Holt Harvey, Ltd.
+64 27 460 9994

Quoting Jeremy Milum <jmilum@xxxxxxxxx>:

> On 10/27/05, stan <stanb@xxxxxxxxx> wrote:
> > On Wed, Oct 26, 2005 at 01:10:00PM -0500, Corey R Clingo wrote:
> >> I keep my QFs in a text file so I know
> > > what I put on, since that function in the installer is no longer
> accura=
> te.
> > >
> >
> > I had not heard that.
> >
> > Can you elaborate? We depend on teh QF history being accurate, here.
> 
> he means it is not accurate if you install the QF manually, i.e. not
> through the installer. Although you could also manually add the QF to
> the list to make the history be accurate after a manual install
> 
> --
> Patron saints in general are broadband connections to the Almighty
> - Michelle Delio, Wired News
>  
>  
> ______________________________________________________________________
> _
> 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

Other related posts: