Going over the basics, Im sorry to go over the same again, just want to make
sure:
- Before you start modifiying the sysdef, all the software packages are DONE
- You do the sysdef modifications, then some software packages go to PCHANGE
- The changes you are making, would make all the SMON packages in the SMON
hosts go to PCHANGE, and the CSA package on CSA host to PCHANGE, also the (I
dont remember the name) OSCP70 on the host stations. The rest will remain DONE.
- Create the commit disk.
- When you are doing the Day 1, some packages (normally the ones listed above)
will ask you if you want to go to Day 0, meaning they will re-install following
whatever is in the commit disk. You have to say YES.
- On the ones you are sure you are not changing, you say NO. Whatever you put
NO, will not update.
- You have to commit as minimum, The new host, the old host (unless you are
removing it from the network), the CSA host, the Sysmon hosts. Also you need to
make sure the DEVICE MONITOR is on the newly commited stations.
- After this is done, you power reboot the CP, since it might be all crazy, you
might even want to put the letterbug NOSUCH, reboot it, and reset the letterbug
again and reboot. (Dont put the Checkpoint files in the new host yet)
- The CP should boot green, should be white on SMDH/SM and you should be able
to open it on FoxSelect, ICC, etc.
- Then you should be able to do a loadall (I wouldnt try to reboot it from the
Checkpoint, but, thats your call)
Thats all I can think of at the moment,
Good Luck
Tadeo
--------------------------------------------
El jue, 9/29/16, Joseph M. Riccardi <Joe@xxxxxxxxxxxxx> escribió:
Asunto: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes and commit
A: foxboro@xxxxxxxxxxxxx
Fecha: jueves, 29 de septiembre de 2016, 10:16 am
Yes, I agree, just working on too
many different tasks and meetings...
Packages marked DONE will do nothing during the commit
install So if IIF.pkg
says DONE for each package...nothing will happen during the
commit.
*****Sorry for the confusion, I meant that they are marked
as NOTYET in the
SysDef before the commit and reconcile, but after the
reconcile they are
marked DONE. This proves they were installed?
Sysmon...do you still have no domain files?
*****Not sure what you are calling a Domain file but in
D:/usr/fox/sysmgm/sysmon there are the following files...
destact.cfg,
dom_B03SM1.cfg, dom_SYSMON.cfg (Name of Host AW70),
smon_ech.exe, smon_exit.
In dom_B03SM1.cfg with Word I see the AW70 and CP60s
Letterbugs between some
gobbledygook.
sysdef export on its way off list.
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be
bought or
measured with money; and that is sincerity and integrity." -
Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Russell Boulay
Sent: Wednesday, September 28, 2016 1:48 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes
and commit
Too much time is going by between replies....
Packages marked DONE will do nothing during the commit
install So if IIF.pkg
says DONE for each package...nothing will happen during the
commit.
Sysmon...do you still have no domain files?
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Joseph M. Riccardi
Sent: Wednesday, September 28, 2016 1:43 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes
and commit
The Good, the Bad, and it's getting Ugly. My last
chance... If I cannot
resolve this by tomorrow I give up and will restore all to
original
configuration.
I have committed and reconciled about 1/2 dozen times, using
multiple
diskettes, with the same results. The last attempt I
removed all Stations
from the SysDef and the physical Node except (1) AW70 and
(4) CP60s to
simplify the configuration temporarily; still the same
outcome. I cannot
help but to suspect system issues, not SysDef
configuration. Why? All
files look good...
- Because as I review the SysDef
configuration before the Commit and after
the Reconcile diskette update, all looks OK,
- all checked and verified,
- all software packages DONE,
- all Stations NSAP is 000001,
- IIf.cur all software packages DONE,
- sldb shows all hosted by the correct
AW70.
But...
- System Manager screen opens, when I pick
the SYSMON (SYSMON: System
Monitor not responding & System CPU usage goes to
100%),
- can fist AW70 but not CP60s,
- if I manually start sys_ech.exe it runs
for about 20 seconds and
terminates,
- ICC shows all Compounds and lists all
CPs,
- IIf.prm shows all same NSAP (see file
content below)?
03BW02 03BW02 AADM7 NDMRW 001 3
000000
03BW02 03BW02 ASMON7 IPCNAM 001 SYSMON
000000
03BW02 03BW02 ASMON7 SMGC 001 03WB02
000000
03BW02 03BW02 ASMON7 SMSTM 005 03BW02
000000
03BW02 03BW02 ASMON7 SMSTM 001 03CP01
000000
03BW02 03BW02 ASMON7 SMSTM 004 03CP04
000000
03BW02 03BW02 ASMON7 SMSTM 003 03CP03
000000
03BW02 03BW02 ASMON7 SMSTM 002 03CP02
000000
03BW02 03BW02 OS7AW1 ADRIP1 001 008066
000000
03BW02 03BW02 OS7AW1 ADRMAC 001 C00012
000000
03BW02 03BW02 OS7AW1 ADRNSP 001 000001
000000
03BW02 03BW02 OS7AW1 APLHLB 001 03BW02
000000
03BW02 03BW02 OS7AW1 APLN 001 03BW02
000000
03BW02 03BW02 OS7AW1 APMODE 001
DNBI_PRESENT 000000
03BW02 03BW02 OS7AW1 DATIM 001 0
000000
03BW02 03BW02 OS7AW1 MSGLN 001 03WB02
000000
03BW02 03BW02 OS7AW1 P1BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P1DEV 001 4
000000
03BW02 03BW02 OS7AW1 P2BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P2DEV 001 4
000000
03BW02 03BW02 OS7AW1 P3BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P3DEV 001 4
000000
03BW02 03BW02 OS7AW1 P4BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P4DEV 001 4
000000
03BW02 03BW02 OS7AW1 P5BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P5DEV 001 4
000000
03BW02 03BW02 OS7AW1 P6BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P6DEV 001 4
000000
03BW02 03BW02 OS7AW1 P7BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P7DEV 001 4
000000
03BW02 03BW02 OS7AW1 P8BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P8DEV 001 4
000000
03BW02 03BW02 OS7AW1 P9BAU 001 9600
000000
03BW02 03BW02 OS7AW1 P9DEV 001 4
000000
03BW02 03BW02 OS7AW1 PABAU 001 9600
000000
03BW02 03BW02 OS7AW1 PADEV 001 4
000000
03BW02 03BW02 OS7AW1 PP1DEV 001 10
000000
03BW02 03BW02 OS7AW1 VOLLN 002 vol002
000000
03BW02 03BW02 OS7AW1 VOLLN 001 volwrk
000000
03BW02 03BW02 OS7AW1 VOLLN 003 vol001
000000
03BW02 03CP01 OS1C60 ADRMAC 001 C0001A
000000
03BW02 03CP01 OS1C60 ADRNSP 001 000001
000000
03BW02 03CP01 OS1C60 CPBPC 001 5
000000
03BW02 03CP02 OS1C60 ADRMAC 001 C00022
000000
03BW02 03CP02 OS1C60 ADRNSP 001 000001
000000
03BW02 03CP02 OS1C60 CPBPC 001 5
000000
03BW02 03CP03 OS1C60 ADRMAC 001 C0002A
000000
03BW02 03CP03 OS1C60 ADRNSP 001 000001
000000
03BW02 03CP03 OS1C60 CPBPC 001 5
000000
03BW02 03CP04 OS1C60 ADRMAC 001 C00036
000000
03BW02 03CP04 OS1C60 ADRNSP 001 000001
000000
03BW02 03CP04 OS1C60 CPBPC 001 5
000000
I have tried to respond to every point/suggestion.
Last chance to be a hero and save my a$$... :-)
Thanks
Joseph M. Riccardi
386-451-7607 Cell
Joe@xxxxxxxxxxxxx
"To give real service you must add something that cannot be
bought or
measured with money; and that is sincerity and integrity." -
Donald A. Adams
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Christian HORN
Sent: Monday, September 26, 2016 5:54 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Windows NT AW70 V6.4 SysDef changes
and commit
Hi Joe,
Wow you seem to have a number of issues here....
From my quick read you have at least 2 different issues. 1,
your system
monitor is not running, 2 your CPs are not booting on the
new host.
System Monitor, it is not fully running, there should be
more smon processes
running. This is very likely due to not having the domain
file, that you
mentioned is missing. When you commit a station all domain
files from the
commit disk are placed in the /usr/fox/sp/results directory,
then copied to
the /usr/fox/sysmgm/sysmon. (FYI, if you ever remove a
sysmon from a sysdef
you have to manually remove the file from here also,
otherwise it will be
copied out each time you commit) Check here for the domain
file, if its
missing something went wrong extracting the file from the
commit disk or
moving it to the new location.
Under normal circumstances new CPs will boot GREEN on a
configured host, no
need to do anything to put them online, they boot online.
Things I would check... If the old host is still online use
rm_station to
clear down the SICT tables, manually remove the old CP CMX
files and
workfiles. (backup first ;)) Log the Romload server (FAQ28),
create the file
/opt/fox/sysmgm/softmgr/file/sm_errs, look for any errors.
However, in my experience I have seen issues with corrupt
commit disks with
no errors logged, especially when using old floppies
multiple times. Try
find a new floppy disk and re-create the commit disk and try
again. And
always try, if possible to do a saveall, initialize and
loadall to move a CP
database, it's the cleanest way. Bootless CP moves need more
planning and
work....
Christian
[ Joseph M. Riccardi ]
D:/usr/fox/sysmgm/sysmon
There is a domain file for each System Monitor These are not
straight asci
files, so need to be looked at with hex reader or can use
notepad or wordpad
but will be scrambled a bit.
If you get system monitor not responding it is because smon
process is not
running.
Plus you don't need system monitor running to get a CP to
boot.
As to AW to CP communications.
I would fist the AW itself to get a node address Then fist a
CP to see if
they think they are on same node
If CP doesn't successfully fist then look in the IIF.prm
file to see what CP
NSAP is....below example would be 000002 and AW would be
000001 which means
they cant talk if this is a single node system.
AWNT01 CP6N01 OS1C60 ADRNSP 001 000002
AWNT01 AWNT01 OS7AW1 ADRNSP 001 000001
Russ Boulay
[ Joseph M. Riccardi ]
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by
Schneider Electric
(formerly The Foxboro Company). Use the info you
obtain here at your own
risks. See the disclaimer at
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 email has been scanned by the Symantec Email
Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any
associated or
attached files, is intended solely for the individual or
entity to which it
is addressed. This e-mail is confidential and may well also
be legally
privileged. If you have received it in error, you are on
notice of its
status. Please notify the sender immediately by reply e-mail
and then delete
this message from your system. Please do not copy it or use
it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by
Schneider Electric
(formerly The Foxboro Company). Use the info you
obtain here at your own
risks. See the disclaimer at
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
Schneider Electric
(formerly The Foxboro Company). Use the info you
obtain here at your own
risks. See the disclaimer at
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 Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
