Re: [foxboro] CP40B won't download FBM's
- From: "Den Haese Patrick" <phaese@xxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 11 Feb 2008 22:46:59 +0100
Tim,
As Russ mentioned it's the romload server who detects the OS type on pre 6.2
systems.
so ds_stasict doesn't reflex the correct OS on these pre 6.2 systems
Is in SMDH disable download not active (just another hint).
iom files in place in /usr/fox/sp/files.
just to be sure
cp_utl -gm -oh -p[CP lbug]_STA:STATION.APPSAP
The result is the PSAP address: xx xx xx xx xx xx xx xx xx xx xx xx xx xx
xx xx xx xx xx xx xx xx xx xx xx xx.
this command extract the MAC out of the CP memory.
Patrick
----- Original Message -----
From: "Timothy J Barron" <tjb6@xxxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Monday, February 11, 2008 10:03 PM
Subject: Re: [foxboro] CP40B won't download FBM's
> No, the host has not been changed. I also ran prtconf -vp to verify that
> the NVRAM contents matched what was saved previously, and it's good.
> Thanks for the suggestion though.
> I should mention that ALL(4)other CP40B's on V4.3 nodes at our site (one
> on the same node
> and three on other nodes) are all showing OS1C40 references when running
> ds_stasict. The nodes are independant, not tied together. They have been
> in operation
> for many years and were installed by Foxboro. We have added/downloaded
> FBM's many times without issues.
>
> I should also clarify that OS1C4B exists in /usr/fox/sp/files. However,
> there
> is no OS1C4B directory and pkginfo file in /usr/opt. This is what I was
> referring to
> when I said it didn't exist. Sorry about the confusion.
>
> Can someone tell me what the significance of the /usr/opt/.../pkginfo file
> is?
>
>
> Tim
>
>
>
>
>> Just a question. Has the host been changed after CP boot-up?
>> The booted CP loads his host MAC address in memory.
>> and will only talk to the associated MAC for downloading FBM IOM files
>>
>>
>> HH845 has the complete instruction to extract the MAC out of the CP
> Memory.
>>
>> Patrick Den Haese
>>
>> ----- Original Message -----
>> From: "Boulay, Russ" <russ.boulay@xxxxxxxxxxxxxxxx>
>> To: <foxboro@xxxxxxxxxxxxx>
>> Sent: Monday, February 11, 2008 8:18 PM
>> Subject: Re: [foxboro] CP40B won't download FBM's
>>
>>
>> > OS1C4B has to be loaded on the host. /usr/fox/sp/files
>> >
>> > When the CP40B boots up on pre v6.2 systems the updated romload_svr
>> > (K0200SZ)identifies it as a CP40B requesting bootup.
>> > The romload_svr then points the boot request to the OS1C4B image to
>> > boot.
>> > If romload_svr identifies a station as CP40A, then gets pointed to
>> > OS1C40 image.
>> >
>> >
>> > -----Original Message-----
>> > From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> > On Behalf Of Timothy J Barron
>> > Sent: Monday, February 11, 2008 2:10 PM
>> > To: foxboro@xxxxxxxxxxxxx
>> > Subject: Re: [foxboro] CP40B won't download FBM's
>> >
>> > Looks like CP40A files...
>> > IMAGE records: OS1C40, OS1C40.GDT
>> >
>> > EEPROM records: eu_c40.bin
>> > Do you need more output info?
>> >
>> >
>> > As I mentioned, OS1C4B does not exist on this AW, =
>> >
>> > but on floppy disk (the one NOT loaded):
>> > /usr/opt/OS1C4B sum is: 1507
>> > /usr/opt/OS1C4B/pkginfo file sum is: 1255
>> >
>> > contents of pkginfo file (on floppy):
>> >
>> > VERSION=3DK0200SF-D-6
>> >
>> >
>> > Any tricks to get out of this??
>> >
>> > Thanks Again,
>> > Tim
>> >
>> >
>> >
>> >
>> >
>> >> =
>> >
>> >> On host:
>> >> cd /usr/fox/swi
>> >> ds_stasict CPXXXX
>> >> =
>> >
>> >> what files are the sict tables pointed to....
>> >> =
>> >
>> >> also sum the OS1C4B file =3D
>> >> =
>> >
>> >> =
>> >
>> >> =
>> >
>> >> -----Original Message-----
>> >> From: foxboro-bounce@xxxxxxxxxxxxx
>> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> >> On Behalf Of Timothy J Barron
>> >> Sent: Monday, February 11, 2008 12:42 PM
>> >> To: foxboro@xxxxxxxxxxxxx
>> >> Subject: Re: [foxboro] CP40B won't download FBM's
>> >> =
>> >
>> >> Thanks for the response Russ.
>> >> We already have a CP40B running on this node. We have a few on 4.3
> in
>> > =3D
>> >>
>> >> other parts of the plant as well.
>> >> For some reason, this CP40B would not boot up until we loaded the
>> > #49101
>> >> =
>> >
>> >> (part #K0175LH-D)disk.
>> >> Maybe this was the wrong move as it looks like it's for CP40A's. =3D
>> >> =
>> >
>> >> =
>> >
>> >> It looks like the other disks I mentioned [#'s 71501 =3D
>> >> =
>> >
>> >> (part #K0200SF-D) and 71502/71602 (part # K0200SF/K0200SE)]
>> >> are for CP40B's and have been utilized on this AW before(contains a
>> > new =
>> >
>> > =3D
>> >> =
>> >
>> >> romload
>> >> server as you mentioned, probably not the latest though)as all files
> =3D
>> >> =
>> >
>> >> shown on the floppies exist on the system, EXCEPT for =3D
>> >> =
>> >
>> >> /usr/opt/OS1C4B/pkginfo. =3D
>> >> =
>> >
>> >> =
>> >
>> >> So does my CP40B think it's a CP40A because of loading the #49101
>> > disk?
>> >> If so, can you expound on how that is triggered?
>> >> =
>> >
>> >> Do you recommend tarring in the /usr/opt/OS1C4B/pkginfo file? =3D
>> >> =
>> >
>> >> =
>> >
>> >> Does this require an initialize/reboot?
>> >> =
>> >
>> >> Sorry for my ignorance - I've never dealt with this end of the
>> > beast...
>> >> =
>> >
>> >> Tim
>> >> =
>> >
>> >> > =3D
>> >> =
>> >
>> >> > At 4.3 you need more than a CP40B image.
>> >> > B style processors weren't supported at 4.3
>> >> > You also need to update the romload server with diskette..K0200SZ
>> >> > =3D
>> >> =
>> >
>> >> > Basically your B is booting as an A without that diskette and won't
>> >> run
>> >> > =3D
>> >> =
>> >
>> >> > Must also configure as an "A" in sysdef
>> >> > =3D
>> >> =
>> >
>> >> > =3D
>> >> =
>> >
>> >> > -----Original Message-----
>> >> > From: foxboro-bounce@xxxxxxxxxxxxx
>> >> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> >> > On Behalf Of Timothy J Barron
>> >> > Sent: Monday, February 11, 2008 9:32 AM
>> >> > To: foxboro@xxxxxxxxxxxxx
>> >> > Subject: [foxboro] CP40B won't download FBM's
>> >> > =3D
>> >> =
>> >
>> >> > Hello List
>> >> > We just installed a CP40B on a 4.3 system (purchased 2 years ago
>> >> waiting
>> >> > =3D
>> >> =
>> >
>> >> > for an opportunity). We moved the majority of the FBM's and
>> >> compounds =3D
>> >> =
>> >
>> >> =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > from an overloaded CP30A into the CP40B. FBM's downloaded fine
>> > except
>> >> > for =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > one that had an apparent nosecone failure, which was proven by
>> > moving
>> >> > the =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > nosecone from the adjacent FBM and changing the letterbug. A new
>> >> > nosecone =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > was installed the next day and the FBM would not go online or
>> >> download. =3D
>> >> =
>> >
>> >> =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > Tried the adjacent nosecone again and it still would not go online
>> > or
>> >> =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > download. Adjacent nosecone was reinstalled back to original FBM
>> > and
>> >> it
>> >> > =3D
>> >> =
>> >
>> >> > will now not go online or download either. Hardware was tested on
>> >> > another =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > node and is fine.
>> >> > =3D
>> >> =
>> >
>> >> > The CP40B was configured in SysDef as a CP40A and software floppy
>> >> #49101
>> >> > =3D
>> >> =
>> >
>> >> > (part #K0175LH-D) was installed to get CP running. =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > =3D
>> >> =
>> >
>> >> > We also have software on floppy labeled "CP40B" with Foxboro #'s
>> > 71501
>> >> =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > (part #K0200SF-D) and 71502/71602 (part # K0200SF/K0200SE). These
>> >> were =3D
>> >> =
>> >
>> >> =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > NOT installed. =3D3D
>> >> > =3D
>> >> =
>> >
>> >> > =3D
>> >> =
>> >
>> >> > Does anyone have any suggestions or ideas?
>> >> > =3D
>> >> =
>> >
>> >> > Thanks
>> >> > =3D
>> >> =
>> >
>> >> > Tim Barron
>> >> > NewPage Paper
>
>
> This electronic message contains information from NewPage
> Corporation or subsidiary companies, which may be confidential,
> privileged or otherwise protected from disclosure. The
> information is intended to be used solely by the recipient(s)
> named. If you are not an intended recipient, be aware that
> any review, disclosure, copying, distribution or use of this
> transmission or its contents is prohibited. If you have
> received this transmission in error, please notify NewPage
> immediately at postmaster@xxxxxxxxxxxxxxxx
>
>
>
> _______________________________________________________________________
> 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:
