Professional Documents
Culture Documents
System Tips
Technical Reference Manual
Last Updated on October 24, 2014
These are my personal notes, which include published helpful hints, CAR responses, etc. so use
at your own risk. If youre not sure about a command, dont use it! You can download the latest
version of the Practical System Tips manual from the following Invensys website:
http://support.ips.invensys.com. After logging in, select the "Documents" menu at the top of
the page, then select "I/A Series", then "Practical System Tips". The latest version of the manual
will always be at this location. Julie Monsour
Email: support@ips.invensys.com
julie.monsour@schneider-electric.com
Internet: http://support.ips.invensys.com
The technical information provided in this booklet is proprietary and confidential information for use only by personnel of
Invensys Process Systems and authorized users of Invensys Process Systems' I/A Series systems. The information has been
compiled in this booklet for your convenience as an authorized user of I/A Series systems. You agree you will not copy or
otherwise provide the information herein in whole or in part to any third party such as any unauthorized user of I/A Series
systems, including competitors of Invensys. It is important to note the information contained herein may be modified or
superceded at any time by Invensys. Therefore, before using the information herein it must be checked for current accuracy on
the Invensys Customer Satisfaction Center technical website http://support.ips.invensys.com. Thus, no warranty is made or
implied as to the accuracy of information disseminated through this medium, and you use the information at your own risk.
admintool
Starts graphical user interface for adding and administering user accounts and printer configuration.
Customer would like a way to dump the contents of the AIM messages files (m*.fdb files) collected in the AIM
Historian database into a text file from a command line. While it is possible using one of the other AIM client
packages such as AIMInform or AIMDatalink, those packages are not currently installed or licensed.
Fix/Resolution
You may use the apitst utility from the command window (shell). This is an undocumented/unsupported utility
which provides functions allowing a method of retrieving the message data and directing the output to a text file on
the local hard drive.
1) Open a DOS window and change to the D: partition and enter the shell (sh). Change directories to /opt/aim/bin
($cd /opt/aim/bin)
2) Launch the apitst utility
3) At the function menu, enter 700 for the AIM*Historian.
4) Next enter 11 at the function menu to access fh_FdbMsgQuery.
5) You will then be stepped through a series of prompts; during this you will notice the default value if applicable is
always displayed in brakets [ ]. To accept the default value, simply hit return to accept the value.
When prompted for Bulk output to file enter y (otherwise the output will just be displayed in current window only)
When prompted for Historian Enter your instance name
Output File msg.txt is the default, you can simply hit return to take the default value as shown.
Start Time enter time and date, when prompted to Accept, type y (lower case).
End Time - enter time and date or type "Now" to use the "current" time and date.
When prompted for filter [*], hit return to accept the default value.
When prompted Ok to add enter y
You will see the alarms scroll on the screen. Once completed you should be able to locate the msg.txt file in either
/opt/aim/bin or D:. If needed perform a search to locate on your local hard drive.
It is suggested to run some simple tests/queries first, to retrieve only the last few hours of data, prior
to attempting to retrieve a significant amount of message data. After the first time you run through the prompts you
will see the previous value entered retained in [brackets]; as stated previously just hit return if you want to use that
value again. These values will be retained as long as the apitst utiltiy is open; once it is closed the default values
will be returned.
After locating the msg.txt fle try opening the file in wordpad. The downside of this method is there is no way to
eliminate columns in the messages and there is no easy way to import the data into excel so it can easily be sorted,
etc.
A commit will have to be run only if you are saving/historizing system monitor messages)
Save the configuration from hist manager (I chose to save to /opt/aim/myfiles/ with the name of my historian and
the date (hist01_mydate) and these two files are created: hist01_mydate.inp and hist01_mydate_del.inp then
saved to the Lacie external drive.
Stop the historian and collector on AW0001. Backup the /opt/aim/inst/hist01 directory to the Lacie (just copy).
Backup /opt/aim/bin/an_init.tcp, aimapi.cfg, alias.cfg (if it exists).
Stop the historian and collector from histmgr. From control panel, stop the AIMAPI. From task manager, stop any
aim processes still running (fetchdog, ipchisti, apimgr, etc.).
You will need to remove the AIM historian from starting on this AW on boot. Go to /usr/fox/bin and edit the
fox_apps.dat file to remove the historian, in my case there was a line in fox_apps.dat that read AIMHISTORIAN
with an associated go_AIMHISTORIAN. Remove this line completely so that the historian doesnt start up on boot
or youll have issues with the new historian on AW0002.
On AW0002
Install AIM on AW0002 v3.3.x. From Apiadmin, edit server connections and add alias, ipaddress of alias and
disable broadcast requests (added AW0002 151.128.152.1).
Start Aimapi on AW0002 and record the hostid from histmgr (to get a new permanent license associated with this
AW) also add temp license info in Apiadmin. From histmgr, select Tools > Batch Config > and batch in the
hist01_mydate_del.inp file that we saved earlier. Stop the historian from task manager and copy /opt/aim/inst/hist01
from the Lacie (that we saved earlier).
Verify that an_init.tcp has same authorization and users. Start aimapi and historian. Make sure Aimapi is on.
From histmgr, make sure that the instance and collector are selected to restart on reboot.
Im not sure that its necessary to run xrebuild and msgfix at this point because were doing a straight copy from the
historian that was running on the other AW, but I did it anyway. I ran xrebuild hist01 and msgfix hist01 to have it
rebuild the indexes for RTPs and message files.
cd /opt/aim/bin
start_server STOP
apistop
The above commands will stop the AIM processes and the API processes.
Histps
The histps command will list the remaining processes and identify their PID#s. On 51 stations, you do not want to
kill the windu processes if they are running.
(where PID is the number determined from the histps step above. As the example shows, you may list more than
one PID at a time.)
Histps
These 3 commands will change to the C Shell, start the API server, and start the historian processes. You can now
open the histmanager and turn the instance on.
rtpcheck hist01
(Where hist01 is the name of your instance. This utility is used to check .fdb files, if it finds any corrupt files they will
be displayed on the screen as well as in a log file /opt/aim/inst/hist01/rtpcheck.log.)
rtpfix hist01 10
(Where hist01 is the name of your instance, r10 is the name of the file marked as corrupt {r10.fdb}. Run this on
each file flagged as corrupt. If the file cannot be repaired you will want to delete the corrupt files from the
/opt/aim/inst/hist01 directory).
xrebuild hist01
(This will rebuild the cross-reference file for the instance. Select yes when prompted to commit changes. If you
have errors or results that you are unsure of, you should consult the Schneider-Electric Customer Satisfaction
Center prior to committing the updated cross reference file.)
The next step is to restart the processes. Use the method above for starting the AIM historian and API processes.
Alarm History Issue Not purging old messages and not showing complete
list of alarms
In this case, the alarm history shows that we have 40,000 messages but only displays a few thousand. The Alarm
Manager should purge the old messages and continually update with the newest ones so you should see the last
40,000 messages. Installing QF1105171B solved the problem. Shutdown the AW to install this QF so that the
apiserv32.dll file is not in use to get overwritten. After installing this QF, check the properties of all files named
apiserv32.dll (there are multiple in various directories) to see which has v3.3.x. and which have v3.2.x. This quick
fix probably updated the file located in c:\program files\aim\common\apiserv32.dll. In this case, you would replace
all of the files named apiserv32.dll whose properties show v3.2.x with the updated one whose properties are v3.3.x.
Example:
I created an instance in the Display Alarm Configurator and I saved it as mycompany.am and I created alarm
managers and display managers for three stations called AW5101, WP5101 and WP5102. Looking in the
/usr/fox/customer/config directory, I will see the file: mycompany.am and a directory called mycompany.dir. If I
change directories to mycompany.dir, I will see the file dmcfg and the directories AW5101, WP5101, and
WP5102. Newer versions have the ability to transfer files from within the DispAlmCfg program. The following is
how I would transfer my files manually on the AW5101 which I am currently using:
From a VT100 or command tool window:
cd /usr/fox/customer/config/mycompany.dir
cp dmcfg /usr/fox/customer/hi
cd AW5101
cp *.cfg /usr/fox/customer/alarms/cfg
You can also use the scripts below to copy these remotely. If you do not have an alarm manager configured, there
will be no yourAMname.cfg file. Use the rmount command to remotely mount and copy files to the appropriate
remote workstation directories.
The following is a script to copy the modified/new configuration files that are located in /usr/fox/customer/alarms/cfg
to all AW/WPs in the .rhosts file. This script is named copyc and is located in /usr/fox/customer/alarms/cfg and is to
be run from there. The second script is called copyd and will copy the dmcfg file to all AWs/WPs in the .rhosts file.
It is located in /usr/fox/customer/hi and is to be executed from there.
Script 1 copyc
for x in `cat /.rhosts`
do
echo rcp $x/*.cfg $x:/usr/fox/customer/alarms/cfg
rcp $x/*.cfg $x:/usr/fox/customer/alarms/cfg
done
Script 2 copyd
for x in `cat /.rhosts`
do
echo rcp dmcfg $x:/usr/fox/customer/hi
rcp dmcfg $x:/usr/fox/customer/hi
done
(where AW0000 is the Alarm Manager name) The DM will now be free.
(where AM0000 is your Alarm Manager name) To restart the Alarm Manager, simply go to the Display Manager
and click on the Alarms button on the menu bar.
(If cmd is not specified, print the alias for name; if name also is not specified, print all aliases. Also, the alias will be
gone when you exit the shell, therefore you must put it in the .profile, .cshrc, etc.) To display the current list of
aliases:
alias
unalias name
Example (use the following in /.cshrc to change your prompt to read the station letterbug and the current directory)
alias cd cd \!*;set prompt=`hostname`:`echo $cwd`#
Then, the next time you type in cd /usr/fox you will obtain:
AW5101:/usr/fox#
Annunciator Configurator
The annunciator Configurator generates the following configuration files for 50 series:
/usr/fox/customer/alarms/cfg/<WPLNAM>.acr (main config. file)
/usr/fox/customer/alarms/cfg/<WPLNAM>AApan
/usr/fox/customer/alarms/cfg/<WPLNAM>AAtab
/usr/fox/customer/alarms/cfg/horn.cfg
<WPLNAM> = WP Logical Name NOT the WP Letterbug
The .acr file is the main configuration file from which the AApan and AAtab files are built. In earlier versions of
software, you would need to manually move the files above to /usr/fox/alarms (all except .acr).
x1
x2
x3
x4
x5
x6
x7
x8
x9
xa
xb
xc
xd
xe
xf
12
0123456789abcdef
00:
47
32
42
4f
4f
54
32
30
32
G2BOOT...2...02.
01:
47
33
42
4f
4f
54
32
30
32
G3BOOT...2...02.
02:
47
34
42
4f
4f
54
32
30
32
G4BOOT...2...02.
03:
33
41
57
42
30
31
3AWB01..........
04:
33
41
57
43
30
31
3AWC01..........
05:
33
41
57
45
30
31
50
31
3AWE01...P1..... <-
06:
34
57
50
32
30
31
4WP201..........
07:
34
57
50
33
30
31
4WP301..........
08:
32
57
50
32
30
31
50
31
31
30
32
2WP201...P1.102.
09:
32
57
50
33
30
31
50
31
31
30
32
2WP301...P1.102.
0a:
32
41
57
42
30
31
2AWB01..........
0b:
33
41
57
42
49
31
3AWBI1..........
0c:
33
41
57
44
30
31
3AWD01..........
0d:
33
57
50
35
30
31
3WP501..........
... you might need to press RETURN to see the next page...
4)
If it is NOT running, most probably is because the file "local_printer" was found.
10) Be sure the configuration files in /usr/fox/alarms: AApan and AAtab, are preceded by the "WP LOGICAL
NAME" and not the WP/AW Letterbug!. WP LN can be found in column 6 of the result of:
grep AWLBUG /usr/fox/sp/IIF.prm | grep MSGLN
11) Since 1993 (v3.2) an undocumented development tool: gcio_test , can be used to test the hardware. (Caution
with its use. See CAR4973) This tool is for AW/WP/50/51 only and is located in: /usr/fox/sp/files/gcio_test With
gcio_test you can test/reset Touchscreen, EEPROM, LEDs, GCIO, etc. This tool supports the following options:
"S" - GCIO Socket Status
13) Verify EEPROM settings. If "ttyb-ignore-cd" is False, the station will not talk to the serial port.
eeprom | grep ttyb
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttyb-mode=9600,8,n,1,If it is "false", change it to "true" at the ok prompt:
setenv ttyb-ignore-cd true
14) If still doesn't work, check if you are using the right cable:
P0904AK 50 Series GCIO Interface w/o TS
P0904AL 50 Series GCIO Interface w/TS
P0904AH WP20/30 Series GCIO wo/TS w/Tabletop
P0904AJ WP20/30 Series GCIO w/TS W/Tabletop
P0904BP WP20/30 Series GCIO w/TS
P0904BQ WP20/30 Series GCIO w/o TS
P0922AD WP20/30 GCIO w/TS For Sony 5402 (MIW Top)
P0922AF WP20/30 GCIO w/TS w/Tabletop For Sony 5402 (EC96)
P0922AE MIW GCIO w/TS For Sony 5402 (EC96)
P0922AG 50/70 Series GCIO w/TS For Sony 5402 (EC96)
***********************************************************************
*
*
*
*
***********************************************************************
<<< Opening GCIO Device Channel "/dev/gcio" >>>
Unit #0 ("Primary GCIO
Unit #1 ("Secondary GCIO
1.. It is best for the user to be on the local console of the AIM*API Server AW (where AIM*API is running).
2.. Start > Run > cmd
3.. d:
4.. ncenv
5.. sh
6.. cd /opt/aim/bin
7.. apitst
8.. 300
9.. 30
10.. Type in a Compound, Block and Parameter that you want to investigate
11.. If step 9 returns an index number, then the C:B.P exists in the AIM*API list.
32 to read the value from the AIM*API list.
12.. If step 9 does not return an index number (it returns a -1), then you can try manually adding it via a 10 and
then adding the Compound, Block and Parameter manually to attempt to open a new index point. Then you can
try starting back at step 8.
If the AIM*API cannot open a new index number in step 11 above, then confirm that there are no typos in the
Compound, Block and Parameter by trying to read the value straight from the Object Manager (OM) with an omget.
Here are the steps to do an omget:
1.. Start > Run > cmd
2.. d:
3.. ncenv
4.. sh
5.. cd /opt/fox/bin/tools
6.. omget COMPOUND:BLOCK.PARAMETER (where COMPOUND:BLOCK.PARAMETER is a valid tag in the
system)
7.. Did this return a value?
exist in a CP.
If not, then even the Object Manager (OM) is unaware of this tag, and it does not
8.. If the omget did return a value, and the AIM*API cannot add a new index number via step 11 in the section
above, then you may need to either refresh the restore_index.dat file or increase the maxobj, or do both. For the
steps to do either or both of these suggestions, reference the section titled: Here are the steps to create a
refreshed restore_index.dat file, and also how to increase the maximum objects (maxobj) setting if applicable in
SOL1914.
All hosted CPs need to be rebooted before their FBMs will download after a host change, unless the following
procedure is used to change the MAC addresses of CPs after replacing the AW/AP. This procedure does not work
with the CP30B, CP40B and CP60B.
Change to the /opt/fox/bin/tools/directory and for each CP, get the PSAP address of the CP by typing the following:
cp_utl -gm -oh -p<lbug>_STA:STATION.APPSAP
Each AWs MAC address will be printed at runtime. Record each AWs MAC address. Note that this utility will
produce two reports: ckmacadr.ok and ckmacadr.err and the AW MAC addresses should also be in one of these
two files.
Set each control stations PSAP address using the following command:
cp_utl -sm -oh -p<lbug>_STA:STATION.APPSAP xx xx xx xx xx xx xx xx xx xx xx xx xx yy yy yy yy yy
yy xx xx xx xx xx xx xx (continuation of line above)
The only thing that changes in the line above are the spaces where the yys are. Where yy yy yy yy yy yy
represents the new CP MAC address which must match the host AW MAC address that was retrieved in step 3.
The remaining part of the PSAP address (the xxs) is to be entered the same as it was recorded in step 1.
Verify the MAC addresses of all CPs and Aws are matched by typing:
ckmacadr
Verify that the ckmacadr.ok file contains all Aws and hosted CPs.
AP20 LOADING
Vxmon is used on AP20s to continuously report information about the usage of kernel tables, the usage of core,
swap space and Vxmon reports information about in-core running processes.
/usr/fox/bin/tools/vxmon
PID The process ID
PY The priority
ST stack size in kb
Time total amount of system and user time used by the process in minutes:seconds.
Delta number of clock ticks (1/60 second) used in between two vxmon samples.
apropos command
Search database for Unix man pages. The apropos command may be used only after the catman command has
been run.
Syntax:
apropos <name>
Example:
apropos network
The parameters were changed to the following and the archive worked properly:
TAPE=/dev/rst9
TAPE_NR=/dev/nrst9
TSIZ=12000M
The size of your tape drive and the device driver will determine parameters to use in this file.
at Command
usage:
at [-csm] [-f script] [-q queue] time [date] [+ increment]
Examples:
at now + 1 day
at 0233 now
at 0815am Jan 24
at 5 pm Friday
-c
-s
-m
-f
-q
-l
job reports all jobs scheduled for the user or a specified job
-r
-f programfile awk uses the set of commands it reads from program file
-F c separate fields with character c.
Example Usage:
To print only the second column of file1 to the screen, type:
awk F/ {print $2} file1
To print every line in file1 except the lines that have dev in column 2 to a file named file2, type:
awk F/ $2!~ /dev/ {print $0} file1 > file2
To print every line that does not have "/etc" in column 1 of file1, type:
awk '$1! ~/^\/etc/ {print $0}' file1
or
nohup cat /usr/fox/hstorian/julie/fname.ace > /dev/LP01 &
backspace function
To be able to backspace with the backspace key without having to hit the Del key: In your VT100 session, type:
stty erase ^H
(this is Ctrl+H) - Its probably more convenient to put in the .profile or .cshrc file.
Backup-to-tape Utility
See Upgrade Utilities.
***Phase 1
Background Explanation - The documented backup procedure instructs the user to bring the I/A station (51 AW/WP
or AP) into the "single user" mode from the normal or "multi-user" mode before the backup procedure is initiated.
This can be done by either clicking on the SHUTDOWN "pull-down" selection (SoftMnt - Shutdown_AW SHUTDOWN) for AWs/WPs, or by initiating the shutdown sequence from a "VT- 100" session screen (shutdown -y
-g0 -is). Because this "state change" method does not consistently stop all processes and close all system files as
intended, the "backup" process is not performed with the box in a true "quiescent" state. Making the backup with a
system not in a true 'quiescent' state, can cause the station to: 1) not work properly during this process in a way that
might affect other stations on the network 2) unable to revert to a normal operational state if restoring from this tape
Recommended Action and resolution The proper method to perform the backup is:
*For 51 Series:
This will sync/close all files and kill all processes. If the previous step fails to bring it to the "ok" PROM prompt, type:
halt
Follow instructions to run the "backup" script. Following this procedure will insure that only those processes
necessary to operate in single user mode are running and the portion of the file system necessary for single user
are mounted. The tape backup will be completed reliably and with no effects on the Node.
***BACKUP ROUTINE
If using the backup and restore diskette, follow the instructions included to use that particular backup or restore
function.
cd /usr/local
backup
or
backup <remote station>
Input the station type to be backed up, (AP, AW, or WP). The system prompts the user with the following message:
Do you have optional RAID data Partition:[y or n], If there is a RAID data partition, respond yes, if not respond no.
(If you have RAID1 answer no, if you have RAID5 with a data partition, answer yes).
Specify the file system or partition to be dumped to tape. (Press <CR> to dump all partitions).
***RESTORE ROUTINE
to login, type:
root
This brings you to the /cdrom directory, to start the restore type:
restore
Enter the station type: (AW, AP, WP) The system prompts the user with the following message:
Were these dumptapes made using the dmp0_8MM utility?[y or n] If they were enter y, if not, n. If this station has a
RAID optional file system to be backed up, the following prompt appears: Were these dump tapes created from a
RAID drive configuration (having a RAID data partition)? [y or n]: If using a RAID1 answer no, if using a RAID5
answer yes. If you answered yes, follow the next instructions for restoring RAID partitions.
***INSTRUCTIONS TO RESTORE THE OPTIONAL RAID DATA PARTITION
Reboot the processor into single user mode. Restore the RAID data partition by running the restore_raid utility.
When the restore is complete, the following message appears:
Type reboot to return to multi-user mode
Backups - 50/51 Series To Streaming Tape using dmp0 and dmp9 scripts
/etc/dumpdates gives last date when drive was backed up.
0=all files
9=incremental
Scripts:
/usr/local/dmp0_150MB
/usr/local/dmp9_150MB
/usr/local/dmp0_8MM
/usr/local/dmp9_8MM
/usr/local/wpdmp0_150MB
/usr/local/wpdmp9_150MB
/usr/local/wpdmp0_8MM
/usr/local/wpdmp9_8MM
/usr/local/dmp0_8MM
/usr/local/dmp9_8MM
/usr/local/wpdmp0_8MM
/usr/local/wpdmp9_8MM
Can do a remote dump to another tape drive on same network but cant restore from remote tape, must be local
because it boots locally and doesnt know to look for remote stations yet. 50 and 51 stations level 0:
Tape 1
Tape 2
Tape 3
Tape 4
If backing up using the new /usr/local/backup routine, please see instructions at backup and restore.
(This script located in /usr/local but should be in the path) When script prompts for partition name press enter for all
partitions. You must wait until the tape has finished rewinding (blinking light stops) to press return after inserting the
tape. If you dont youll have some really good problems.
(This script located in /usr/local but should be in the path) When script prompts for partition name press enter for all
partitions. To return to multi-user mode type exit.
Verify that the name of the AP/AW from which the dump is to be performed is listed in the /.rhosts file of the AP/AW
with the remote tape drive by typing:
rsh <remote_host> cat /etc/motd
If permission to cat the file is denied, the AP/AW with information to be dumped is not listed in the remote AP/AW
/.rhosts file. You must then edit the /.rhosts file on the remote AP/AW to include the letterbug. Shutdown the AP/AW
station to be backed up to single user mode.
fsck
Make sure the station being backed up is shutdown, the tape host can stay in normal multi-user mode. Use the
script commands for backup with this syntax example:
/usr/local/dmp0_150MB <remote_host>
lc /dev/f0 (AP20)
ls /dev/fd0 (50 series)
The above command will copy the entire drive from the system disk to the backup (rshd4). You can also check to
see exactly how many blocks are on rshd3.
dd if=/dev/rshd3.all of=/dev/null
The number of blocks returned should be the same as when the dd was performed.
To backup an entire system drive to 5gb tape using dd: Shutdown the AW/AP.
dd if=/dev/sd0c of=/dev/rst9 bs=96b
(sd0c is primary drive, sd2c is secondary drive) To restore, swap if and of. (if=input file, of=output file)
This command will return the drive status information about the tape.
stcopy -t /dev/tape2
Create file named: /opt/savefile. This file contains only the list of directories/files to be backed up.
Example of contents of /opt/savefile:
/usr/disp
/etc/hostname.le1
/etc/hosts
/usr/dispgrp
Create file named: /opt/saveit. This file should include the following line:
tar cvf /dev/rst9 `cat /opt/savefile`
This is the only line in the file and it should be made executable after creating. Determine which tape drive device
name that you should be using and use in place of /dev/rst9.
***METHOD 2
or
tar cvf /dev/rst9 /usr/menus
This method spaces forward to the end of file mark using the MT command.
boot s
If the system fails to boot to single user mode, use the boot vs command (from ok prompt) to display detailed
startup messages.
boot vs
Check to see where in this sequence the system fails. If the system seems to fail immediately after the kernel loads,
then it is possible there is a corrupt or missing systems file. For example, if the /etc/system file contains an invalid
entry you can perform an interactive boot using boot as. The boot program prompts for the location and the name
of all of the important system files it needs to boot. If the /etc/system file is backed up to an alternate file,
/etc/system.orig, this name can be given instead of the default. Note that you must also enter the physical name of
the root device to match what is in the /etc /system file.
boot as
You will be asked for filename [kernel/unix]: just press return here to accept the default. Then you will be asked the
name of the system file [/etc/system]: type:
/etc/system.orig
Then youll be asked for the physical name of the root device
[/iommu@0,10000000/sbus@0,10001000/espdma@5,8400000/esp@5, 8800000/sd@3, 0:a]: you will then type:
/pseudo/md@0:0,blk
Determine what /etc/rcS.d startup script the system is failing on. Use the output messages from these scripts listed
earlier to isolate the systems point of failure. It may be necessary to boot from the day 0 cdrom to correct the
problem as you will not have access to the system if it is not booting to single user mode. If at this point the system
can boot to single user mode but fails before fully booting to multi-user mode. Boot the system using boot vr.
These options will cause the system to display detailed startup messages and reconfigure the system. If the system
starts the Open Look Window Manager (OLWM indicative of the blue background on the screen) check the
S99FOXBORO script for failures. If not, check the /etc/rc2.d scripts. Use the output messages from these scripts
listed earlier to isolate the systems point of failure. Additionally a suspect script can be edited with set x to trace
commands. For example, insert the line set x at the top of the /et/r2.d/S801p script to trace each command being
executed. The output will display each command in the script preceded by a plus sign.
Boot Problems WP51E will not boot after v6.4 day0 install
Issue:
***Upgrading a system to 6.4 w/WP51E's
After performing the ia_install with the 6.4 day0 cdrom the WP51E will not boot.
Workaround:
ia_install
cp /tmp/root/etc/path_to_inst /mnt/etc/path_to_inst
2. For Ultra-60 WP51E: Boot cdrom, mount the / file system and re-create the devices.
mount /dev/dsk/c0t0d0s0 /mnt
Boot Host Checks Troubleshooting a station (CP, COMM, etc.) that wont
boot
1. sict tables
These are the Software Information Configuration Tables. These are located in /usr/fox/sp and there are six files.
Information is placed in these files by Software Install. They can be examined by using /usr/fox/swi/ds_stasict.
Typing the command with no arguments will give you the syntax.
ds_stasict [-ffbm_lbug] station_lbug
(reboot)
DOS to Venix:
fdisk
bpatch
On AP20:
/usr/fox/bin/tools/bpatch <filename>
On AP50/51:
/usr/foxbin/bpatch <filename>
On NT stations:
There is no bpatch on NT, use fxedit (see fxedit)
Example:
/usr/foxbin/bpatch transfer01.dwf
Bypass Module
1. Write down all four output points
2. Turn module on with switch
3. Make sure knobs are set to N
4. Plug cords in correct places on module as shown below.
5. Use top knob to turn to make black needle align in the middle at zero.
6. After aligning with zero, flip the bottom knob to S. You are in control
7. Before giving control back to operator, he must put in values inside.
ESQL=/usr/informix/bin/esql
cc -c $1.c -I/usr/include/fox
$ESQL $1.o -o $1 -lhist -lisam -lfox lpw
syntax:
normal message to receive is: ld: /usr/local/lib/libpw.a: cannot open (do not be alarmed, everything went well)
If you dont have a null modem adapter, you can change the pinout on one end of the serial cable to have pins 2
and 3 swapped. Therefore if your serial cable has this pinout on both ends: 1=black, 2=brown, 3=red, 4=orange,
5=yellow, 6=green, 7=blue, 8=purple, 9=gray. You can take one end and switch the number 2 pin and the number 3
pin to make 2=red and 3=brown.
Cabling - Hard Drives, Floppy, Streaming Tape Without Extra Backup Hard
Drive (AP20)
Cabling - Hard Drives, Floppy, Extra Backup Hard Drive, Without Streaming
Tape (AP20)
cal Command
Provides a calendar.
syntax:
cal [[month]year]
Print a 12 month calendar for the specified year or a single month. Without options, print calendar for the current
month.
cat Command
cat filename
catman Command
The catman command builds a database of keywords and allows the apropos command to work.
Syntax:
catman
Note: catman needs to be run once and takes about an hour to run. See apropos for more information.
cb Command
C Program beautifier.
Syntax:
cb [files]
options:
-j
-l
-s
cfgpts
This tool allows the user to configure collection points without the standard interactive historian Configurator, or to
extract point configuration data from an existing database.
AP20 located in /usr/fox/bin/tools
50 Series located in /opt/fox/hstorian/bin
Syntax:
cfgpts [-hnADGRvqxs] [histname] [<infile>] [<outfile>]
n=just checking; A=add mode; x=show indices; v=verbose; D=delete mode; s=statistics; b=brief; G=get mode;
h=help; q=quiet; R=get non-removed
To output configuration to an ASCII file
cfgpts > /tmp/filename
You should refer to the instructions in the cfgpts.doc on your system for complete details.
Checkpoint CPs
For a detailed description of the Checkpoint command, go to the section titled Utilities: Upload, Shrink, Checkpoint,
Save_all.
20 series:
/usr/fox/bin/tools/cpoint CPLBUG HOSTAPLBUG
50 series:
/opt/fox/bin/tools/cpoint CPLBUG HOSTAPLBUG
Reboot the CP
2. Make a directory to create a saveall in the /opt partition and create a saveall with cio api
mkdir /opt/SaveAll /opt/SaveAll/5CP301
cd /opt/fox/ciocfg/api
save_all 5CP301 /opt/SaveAll/5CP301
5. Exit ICC so that 5CP301 will checkpoint. Check your work by accessing 5CP301 in ICC again.
Note that any parameters (setpoints, tuning) changed since last Upload will be lost.
ckmacadr
See AP/AW 50 Series Station Replacement Changing MAC Addresses Instead of Downloading FBMs or
Rebooting CPs.
chmod Command
Usage:
chmod [-fR] [ugoa] [+-=] [rwxlstugo] file
cmp - Compare
Usage:
cmp [-l] [-s] file1 file2 [skip1] [skip2]
Compare file1 with file2 and print the differing byte and line numbers.
Syntax:
cmp [options] file1 file2
options:
-l
-s
For complete instructions for this procedure, see CAR 5692 Response from Fred Sanford. This procedure should
take care of the add_to_sys failure problems.
You are now ready to restore only the opt partition as described in the B0193ND DOC. (The following steps are
taken from the B0193ND)
Shut down into single user mode
First check the root and usr partitions
fsck /dev/md/rdsk/d0 (root)
fsck /dev/md/rdsk/d4 (usr)
(restores partition)
You will get a message stating that you have not read any volumes to specify the next volume enter 1 for the next
volume if level 9 dump
ufsrestore tfs /dev/rst9 3
ufsrestore xfs /dev/rst9 3
umount /dev/md/dsk/d5
fsck /dev/md/rdsk/d5
reboot and the 51 series box will now boot into I/A
Install three ferrite cores for each set of CP60s. The ferrites go around all 4 white coaxial cables for a single CP60.
For a fault-tolerant CP, the ferrites go around all 8 white coaxial fieldbus cables. Use two cable ties to keep the
ferrites in place. This can be done while the plant is running. Install the CP60 DIN rail insulators. Only the following
devices are to be installed on the CP60 Isolated DIN rail sections: The CP60 Fieldbus bracket and connectors; the
CP60 Fieldbus 10Base2 to fiber-optic-converter (Black Box); (optional) status tap for the respective 1x8 mounting
structure (connect the green/yellow earth wire from the status tap to the CP60 DIN rail also, the status tap may
only connect to channel isolated FBMs); Extended nodebus bracket (RG58 cables with TNC connectors).
Install the following additional earth wires: (12 AWG) for each 1x8 mounting structure: a) From the lower right hand
screw (when viewed from the rear) on the 1x8 mounting structure earth bus, to the earth-terminal on the respective
isolated DIN rail; b) From earth-terminal on the isolated DIN rail to the added insulated Earth terminals; c) From the
added insulated Earth Terminals to the power earth terminals. Install a Ring Terminal on the earth wire at the
cellbus and Isolated DIN rail earth connections.
If multiple isolated DIN rails are required for a single 1x8 mounting structure depending on the number of cp60
connector brackets, connect the first isolated DIN rail with a wire to each additional isolated DIN rail.
The contact tang on the clips (X0175GD) must be approximately +/- 15 degrees twisted to minimize contact
resistance with the Din rail.
If a Black Box 10Base2-to-fiber-optic-converter is used, mount with the BNC connector facing outside on the
bracket with the large star washer between the converter and the bracket. Make sure that a reliable contact is
obtained between the bracket and the metal converter housing/BNC connector.
Verify that the CP60 DIN rail is grounded to the respective 1x8 an to earth ground. Verify that status taps are
grounded to the CP60 DIN rail, which is isolated from the cabinet. Verify that the FCM10e, FCM10ef, WFCM10e,
and WFCM10efs are at revision F or later. Verify that the CP60 modules are at revision N or later.
QF1005124 should be installed to get all FCMs to an EEPROM level of 1.14. This QF should be installed once the
latest FCMs are in service. This software installation may be done while the system is in full operation so long as
both FCMs are not updated at the same time.
conn/sconn
See som/rsom.
(<CPLBUG> = the CP letterbug of save_all) (Be sure to include the . at the end.)
cd /
umount /dev/fh0
Put in the drive the diskette that has the tarred file from the 20 series station:
cd /
tar xvf /dev/fd0
eject
Put in this drive, a new diskette that will be your new 50 series save_all.
fdformat
newfs /dev/fd0c
mount /dev/fd0 /f0
rmdir /f0/lost+found
cd /f0
tar xvf /usr/tmp/<CPLBUG>
cd /
umount /f0
eject
Also note that the name of the script file must end in .ksh (for example, my_script.ksh).
if [ `uname n` != $x]
then
if [$x != junk]
then
if [-f $all_args]
then
echo rcp $all_args $x:$FILEDIR at `date`
rcp $all_args $x:$FILEDIR
fi
fi
fi
done
done
Syntax:
blow filename
You must be very careful using this script because the rcp command tends to take precedence over some system
calls. Care should be taken because sending large amounts of data on the Nodebus can cause other stations to be
unable to communicate. SMURFS! System management may miss heartbeats and flag them failed or the Nodebus
failed. A cable test will usually fix.
Example to remove unwanted hard carriage returns (^M) at the end of each line of a file. The following command
will globally replace the last character of each line (the carriage-return) with nothing (i.e. delete it). The hard
carriage returns are placed at the end of the line in a file saved in DOS/Windows. Thank you Bob VI and awk
Dombrowski. (Also see VI Colon Commands for a different method).
dos2unix -ascii <originalfile> <convertedfile>
Copy From One I/A Diskette to Another With One High Density Drive
Available (3 )
insert source diskette
dd if=/dev/rfh0 of=/usr/tmp/disk1 bs=8192 count=180
Copy From One I/A Diskette to Another With Two High Density Drives
Available (3 )
dd if=/dev/rfh0 of=/dev/rfh1 bs=8192 count=180
Copy From One I/A Diskette to Another With One High Density Drive
Available (5 )
insert source diskette
Copy From One I/A Diskette to Another With Two High Density Drives
Available (5 )
dd if=/dev/rfh0 of=/dev/rfh1 bs=8192 count=150
If the Media Stamp is incorrect, see the section titled Stamp-ID Changing Incorrect in this manual.
While in the directory containing the core file will identify the program that dumped the core file. Then if you type:
adb program_name core
It has been suggested that you will get an in-depth analysis of the core file if possible. Some of the options are $C
which shows you the top of the stack at the time of the core dump; and $Q quits the adb program and returns you
to where you were. These commands are case sensitive. I will have to do some exploring with this adb command
in order to add more information in this manual about it.
These counters get reset automatically upon CP station reboot. The PIOE1R or Fieldbus Retries, keeps track of the
number of Fieldbus operations that required one retry during stable system operation, a non-zero counter may
indicate Fieldbus hardware problems.
The PIOEFT or FT Mismatch, keeps track of the number of Fault Tolerant Control Processor output mismatches on
the Fieldbus. This occurs if the Primary and the Shadow have different outputs and a retry occurs. If several retries
are required, then the primary and shadow modules will perform self-diagnostics to determine if there is a hardware
problem, and the suspect module will go off-line (red/green). A non-zero number in this counter may indicate a
hardware problem with one of the two Control Processor modules or the X-bus and a mismatch may occur as a
software glitch.
The PIOEGB or FBM State Change, keeps track of the number of good to bad FBM statuses. It is common for this
counter to be non-zero during system startup and checkout, but it should not increase during stable system
operation. If this counter increases over time, the System Monitor printer should be examined for messages
indicating FBM or Fieldbus problems.
The station block provides a connectable, non-settable real ouput parameter total memory (TOTMEM) indicating
the Dynamic Free Random Access Memory (RAM) available for the Control Database. For proper operation, the
CP must have at least 20K of free memory. The CP updates this value every 30 seconds. To support various
functions, the Dynamic Free Memory required is 30 Kbytes for a CP10 and 80 Kbytes for a CP30. This means that
the minimum amount of free memory as shown on the Station block for CP10s and CP30s should always be at
least 30 Kbytes and 80 Kbytes, respectively, when the short term functions (Alarm Message transmission,
operators calling the Select screen, Get/Sets of Control Block Data, Process Summary Report, etc.) are not
occurring.
Object Manager overruns can be caused by a large number of stations trying to connect simultaneously, losing
communications to a connected station, or simply overloading the OM Scanner Task by trying to connect to too
many stations. If Object Manager overruns are occurring frequently (one per minute), check the System Monitor for
communication problems and use the Station Block to examine station loading problems. To reduce Object
Manager load:
Reduce the number of WPs accessing data from the CP.
Adjust displays to scan OM list at 2.0 seconds rather than 1.0 second.
Change the BPC of the CP to 1 second which reduces peer-to-peer load.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
NAME DESCRIPTION
<LBUG>PDUS30 Average number of Packets relayed by LAN over a 30 second average. This counter represents
the Network Layer PDUS Relayed counter.
<LBUG>VALLOCF Available memory for allocation in 16 byte buffers
<LBUG>TKNPASS Number of successful tokens passed by station
<LBUG>TKNHRD Number of tokens gone by
<LBUG>NOSCR8 Number of times the station has failed to find a successor to pass the token to after failing token
pass and who follows. This counter is the TBC statistics No Successor 8 counter.
<LBUG>WHOFLWS Number of times the station has had to find a new successor to pass the token after failing
token passing to its normal successor. This counter represents the TBC statistics Who Follows counter.
<LBUG>TKNFAIL Number of times the station has failed to pass the token to it's normal successor. This counter is
incremented by two. This counter represents the TBC statistics Token Pass Fail counter.
<LBUG>NONSIL Number of periods that the Tokenbus Controller detected a valid signal in 5-10 Mhz rage without
a Start Delimiter. This counter represents the TBC statistics Non-Silence counter.
<LBUG>FCSERRS Number of received frames with Frame Check Errors. This represents the TBC statistics FCS
Error counter.
<LBUG>EBITERR Number of received frames with the E-bit set in the End Delimiter. This should only be set by a
repeater which detects an FCS error in the frame. This counter represents the TBC statistics E-Bit Errors counter.
<LBUG>FRMFRGS Number of frames received which did not have an End Delimiter. This counter represents the
TBC statistics Frame Fragments counter.
<LBUG>FRMLONG Number of frames received which longer than 8K bytes. This counter represents the TBC
statistics Frames Too Long counter.
<LBUG>FDBDERR Number of frames that were discarded because here were no Frame Descriptors or buffers
available. This counter represents the TBC statistics No FD/BD Error counter.
<LBUG>OVERRUN Number of times that a frame has dropped because the Tokenbus Controller couldn't get DMA
access.
Counter Thresholds
NAME THRESHOLD
<LBUG>PDUS30 As traffic rates increase through a LAN this counter will skew since the STRH handler has a
lower priority than than the routing task. Use the following thresholds:
PDUS30 VALUE
APPROXIMATE RATE
0-250
0-250
250-300
250-275
300-325
275-300
<LBUG>VALLOCF Not a counter but a reference of free memory in 16 byte chunks (Normally around 300K)
<LBUG>TKNPASS N/A
<LBUG>TKNHRD N/A
<LBUG>NOSCR8 5 Per Hour
<LBUG>WHOFLWS 10 Per Hour
<LBUG>TKNFAIL 10 Per Hour
<LBUG>NONSIL 20 Per Hour
<LBUG>FCSERRS 20 Per Hour
<LBUG>EBITERR 20 Per Hour
<LBUG>FRMFRGS 240 x Number LAN"s in the token ring
<LBUG>FRMLONG 2 Per Hour
TBC STATISTICS
NO SUCCESSOR 8 - The number of times the TBC fails to pass the token and does not succeed in finding a new
successor station. This counter is incremented only when two or more LI stations are active in the network. A
significantly large value in this counter may indicate a faulty transmitter in the LI.
WHO FOLLOWS - The number of times the LI station has had to look for a new station to pass the token to. This
frame is sent as part of the TBCs effort to pass the token to its former successors successor (the successor of the
station that dropped out of the ring) if the original successor station does not respond to the tken. This counter is
incremented by two every time a failure occurs.
TOKEN PASS FAIL - The number of token pass failed transitions when the pass state is equal to pass token.
Upon failing to pass the token, the TBC tries to send a second token, where the pass state equals repeat pass
token. If this effort fails too, this counter is not incremented again; but the TBC will then send a who follows frame
and the who follows counter will be incremented.
FRAMES TOO LONG - The number of received frames that are greater than 8K bytes, an IEEE 802.4 parameter.
NO FD/BD ERRORS - The number of frames that were not received because there were not enough frame
descriptors or not enough buffers.
OVERRUNS - The number of times the TBC detected a First In First Out (FIFO) overrun during a receive
transmission.
LI MODEM STATISTICS
NON-SILENCE - The number of received periods of non-silence. In other words, the number of times the LI waited
for silence in order to communicate on the cable, but noise or collisions on the cable caused the LI to have to wait
for a silence period.
FCS ERRORS - The number of received frames with FCS or CRC errors and the E-bit reset.
E-BIT ERRORS - The number of received frames with the E-bit set in the end delimiter. The E bit, or error bit, is
set by the regenerative repeater (headend remodulator), when the headend detects a FCS error on the forward
channel.
FRAME FRAGMENTS - The number of frame fragments collected with a start delimiter (SD) not followed by a valid
end delimiter (ED). A valid frame consists of only data (zero or one MAC symbols) between the SD and the ED. If
an SD is detected and then, before a valid ED, the TBC detects either silence, non data (not part of the aligned ED),
or a bad signal, then this counter is incremented. Note that this includes abort sequences.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
Frames Transmitted and Frames Received should not exceed 50 pkts/second. DMA Underruns, Excess Collisions,
CRC Errors, Align Errors, No Receive Resources, DMA Overrun, Collisions and Transmits Deferred are not
reported on FT stations unless it is a CLI.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
Note: The values of these counters are guidelines and can be affected by system dynamics. Exceeding one of
these values is not a definite indication of a problem or system error.
cpio Command
To copy from tape to hard drive:
cpio -ivd /usr/disp/filename < /dev/rst9
Crontab
The crontab file consists of six fields: minute (0-59; hour (0-23); day of month (1-31); month of year (1-12); day of
the week (0-6 with 0=Sunday):
crontab [file]
shows whats in crontab. If no entries are shown by crontab -l then add lines to crontab by following this procedure:
To add a line to your crontab file:
echo ; * * * * /usr/prog/myfile; >> cronit
(That line will add /usr/prog/myfile to the crontab file named cronit)
To add this line to the currently scheduled crontab:
crontab cronit
If youre not sure what the name of the crontab file is, you can get the current crontab configuration and add to it
and rename it by doing the following:
crontab -l > cronit
This will add /usr/prog/myfile to the new crontab file named cronit
crontab cronit
Please see the section titled: Scheduling .ksh Files to run through Windows Scheduler in this document for the
procedure to run .ksh files from Windows workstations.
If the CSA (Compound Summary Access) is not in sync and does not match the database running on the CP, this
solution provides the steps to fix it. Usually the "check_db_sync" utility is used to detect if you have this problem.
NOTES:
Remember to always perform a Checkpoint before running "check_db_sync". This procedure does not fix
mismatches against the database in the workfile.
Fix/Resolution
This is a procedure to have a CSA CP's db that matches exactly the compound/blocks running on that specific CP.
It was written for Windows. (On Unix, you will have to create the script using vi, or converting the Notepad-created
file to Unix by using utility dos2unix).
NOTE: It doesnt fix anything on the workfile, just the CSA db for the specific CP.
It uses the command "getpars" to get the compound/block names and types, directly from the CP, and then convert
the output to CSA format.
A. Get compound/block names from CP
This is the basic command to get the compound/block names from the CP:
/opt/fox/bin/tools/getpars -n -UCPLBUG -mCMPNM:%15s -mTYPE:%7
In order to use the result for CSA we need to change the order of columns, remove some extra lines, etc.
All those changes can be accomplished with this script: "getpars2csa.txt"
------------------------#!/bin/sh
cd /opt/fox/bin/tools
getpars -n -U$1 -mCMPNM:%15s -mTYPE:%7s | sed '1,6d' | awk '{printf "%-13s\t%-13s\t%-13s\n", $2, $1,
$3}' | awk '
$1 != Lastcmpd {
Lastcmpd = $1
print $1
}
$1 == Lastcmpd {
printf "%-13s\t%-13s\t%-13s\n", $1, $2, $3 }' > $1
------------------------Copy the lines above (between dotted lines) to Notepad and save the file as "getpars2csa.txt"
Copy the file to the CSA host (preferred), into /opt/fox/bin/tools directory
How to use the script:
Once the script is in /opt/fox/bin/tools, open a command prompt and type:
d:
sh
cd /opt/fox/bin/tools
getpars2csa.txt CPLBUG
The script will create a file named "CPLBUG" in /opt/fox/bin/tools, that can be used for CSA Merge.
Open that file and verify that starts with the STATION block line and it looks like this (format):
CP6001_STA
CP6001_STA STATION STA
CP6001_ECB
CP6001_ECB PRIMARY_ECB ECBP
AC_TST001
AC_TST001 AC_IND01 IND
AC_PIDA_TEST
AC_PIDA_TEST AIN1 AIN
AC_PIDA_TEST PIDA1 PIDA
AC_PIDA_TEST AIN2 AIN
AC_PIDA_TEST PIDA2 PIDA
...
B. Remove ALL compound/blocks names from CSA Database, just for that CP
Type:
cd /usr/fox/csa
csa_fn reset CPLBUG
/opt/tmp/csa_merge
Put the CPLBUG file, for the CP that need to be merged, into that directory.
Then type:
cd /usr/fox/csa
CSA_Merge /opt/tmp/csa_merge
D. Verify CSA has now the database for the CP, by typing:
csa_stn_save CPLBUG
E. Check if that databases are in sync by running
/opt/fox/bin/tools/db_sync/check_db_sync CPLBUG
On the CSA host the csa database can get corrupted for one or more stations. This is not a common occurrence
and can happen if /tmp space fills up when an ICC operation is taking place. One symptom of this occurring is the
ICC hangs gray when entering a control station. This could be due to a corrupted stations csa database. In this
situation typing csa_fn reset CPLBUG never completes. When this occurs no ICC functions or iccdrvr.task
command can access the corrupted station.
Solution:
Ensure that the station is question is your CSA Server. This can be found by the following command:
/opt/fox/bin/tools/glof -p CSA_SERVER
Now attempt to do a CSA_Save again. After the CSA_Save completes, change to the directory where CSA was
saved and notice the LTRBUG for the offending processor should not be there. If a CSA_Save cannot be done,
Stop Call the Customer Satisfaction Center, this procedure will not fix your problem with out a good CSA_Save.
Clean out CSA by doing the following:
ps -eaf |grep CSA
Rebuild the default CSA files by doing the following: Reboot your CSA host. After the host boots do
the following to verify that the default CSA files are there.
cd /opt/fox/csa
ls
CSA Report
(HH#: HH1007)
On the Unix platforms at version 6.2 and above. At this time the CSA_Report gives the following error:
CSA_Report: csa_save: not found
This is repeated for all of the stations in the CSA configuration.
Solution:
CSA_Report is looking for csa_save and it should be looking for csa_stn_save.
cd /usr/fox/csa
cp CSA_Report CSA_Report.old
vi CSA_Report
/csa_s
Type: _stn
Key: Esc
The purpose of this is to change the csa_stn to csa_stn_save, which is needed to successfully run the CSA_Report
command.
Now you can type CSA_Report and then cd /opt/fox/csa/CSA_REPORT and read
all of the compound block information for each station CSA hosts.
dbvu/dbvu30/dbvu40
(20 series)
/usr/fox/bin/tools/dbvu -? DB[CPLBUG].UC
(50 series)
/opt/fox/bin/tools/dbvu -? DB[CPLBUG].UC
The directory that contains checkpoint files that are updated during a checkopint is /usr/fox/sp/files.
The directory that contains work files that are updated during an upload is /usr/fox/ciocfg/CPLBUG.
Options:
/usr/fox/bin/tools/dbvu
(v8.x systems)
On a MESH system, use the following to dump the result in a file called DBVU_report in /opt.
/opt/fox/bin/tools/dbvu -rs CDB<CPLetterbug>.UC CP270 > /opt/DBVU_report
On some stations, I had issues trying to run dbvu using the above command. The way that I finally was able to get it
to work was to copy the checkpoint file (/usr/fox/sp/files/DB*.UC into /opt/fox/bin/tools and run the following
command. The following command is running dbvu on a CP60 named CP0001.
dbvu spblru CDBCP0001.UC CP60 > DBCP0001.txt
dbvu_err
This command takes the output from dbvu t as its input to generate a compound-block-error report named file1.
Syntax:
dbvu_err parameter_linkage_report > file1
Example:
cd /usr/fox/sp/files
/opt/fox/bin/tools/dbvu t C DB<GatewayLetterbug>.UC M OS1MG.mp2 I OS1MG |
/opt/fox/bin/tools/dbvu_err (continuation of line above)
**(the above 2 lines are one command, please do not issue these lines separately. This command on one line.)
Where -M OS1MG.mp2 is a request for the map file, and the I (this is a capitol i ) OS1MG is the image file.
These files are found in /usr/fox/sp/files.
dd command
See also Backups.
Helpful hint using the dd command: When you have a lot of WP51s/AW51s to install using the install_AW/WP
script, you can speed up this process by doing the following. Install one WP51/AW51, about 30-40 minutes time,
shutdown the WP/AW and put a second hard disk in the SUN box, do a boot rs and see which SCSI address this
second disk is getting. Once youve determined this information, you can copy the first disk to the second with the
following command:
dd if=/dev/rdsk/c0t3d0s2 of=/dev/rdsk/c0t1d0s2 bs=16000k
Where t1 in the of is SCSI address 1 (you will enter the number determined above) and bs is the block size, the
figure stated here can be as big as 50% of the installed RAM in your Sun box (e.g. 128MB of RAM -> bs=64000k).
This takes you only 10 minutes!!
defunct Processes
A reboot is required to remove defunct processes.
A process moves in and out of various execution states throughout its lifetime. When a process terminates, it enters
what is called the zombie state. A process in the zombie state is said to be defunct. In the zombie state a process
entry in the process table is replaced with its exit status, and the user and system time required to run it. Thus a
defunct process entry exists whenever a child process terminates. After forking a child, mkzombie sleeps for a
minute. Because the child process exits immediately, it is in a zombie state for the entire minute its parent is
sleeping. A childs exit status is returned to its parent process only if the parent process waits for it by executing a
wait(2) system call. When a childs exit status is reported to its parent, the childs process table entry is removed. If
the parent never calls wait(), as in mkzombie, the zombie child stays in the process table until the parent process
terminates. Most likely, your defunct process was the child of a still-executing parent. It cant be killed because a
zombie process is never scheduled to run and, thus, will never receive the signal youre sending it.
d_edit Command
The d_edit command on windows stations provides a very user friendly menu interface. The following is for using
d_edit on older stations.
Usage:
[ENAOPT | -DISOPT | -DBASE | -DOVER | -ALARM] [-OVLPOS=FULL | UL | UR | LL | LR | UP | LOW | LEFT |
RIGHT] [-SCDELAY=0255] [-SCRATE=120] [-v[fs]] [-o] [-lrxLRX] [-ggroup_name] [-ompath]
[m[,n]]e[/search]/[search2]/[-I | -dump | -upload] [-embed -l ] [-embed [script_file_name] -del | -upd] [-embed
script_file_name -add] disp_file_name
d_edit -dump filename
(will update and re-install graphic called filename from the .dmp file)
/usr/fox/bin/tools/d_edit -l filename
for x in $*
do
if [-f $x]
then
/usr/fox/wp/bin/tools/d_edit50 dump $x
vi $x.dmp
/usr/fox/wp/bin/tools/d_edit50 upload $x
rm $x.dmp
else
echo $x is NOT a file!!!
fi
done
Syntax:
editdisp displayname
-A
-a
access level
-c
-d
delta value
-f
-m
-t
dynamic text
-T
static text
When characters such as #, $, \, ? and * are used, be sure to use a pair of single or double quotes to specify the
character (e.g. $), or entire argument (e.g., -c/?/a/).
Device Monitor
The Device Monitor monitors the status of Comm Servers for all printers attached and Graphical Consoles (WPs,
AWs, PWs)
Troubleshooting Hint:
**If a wp has a cs_devmon.cfg file with the size of 0, copy the cs_devmon.cfg from another aw/wp on the node.
Once the cs_devmon.cfg file is 0 the devmon doesnt have any stations in his list to initialize or update. (QF8410
4.2 fixed in 4.2.2 & 6.0).
**On AP20s/PWs during the software install process there was a problem. Device Monitor was started by the
p_init script before the PW/AW had configured his nodebus NSAP address. This caused Device Monitor to mark all
configured alarm destinations as failed. (QF8945)(Fixed in 4.2.3).
(glof returns a string of hex which contains the address of the master). Perform a fist on each aw/ap/wp/pw in the
system to get all file servers addresses.
/opt/fox/bin/tools/fist LID
Compare the address from the glof with the address from the fist and determine who the master is.
on the master find the pid of cs_devmon and kill it, then restart the cs_devmon process.
ps eaf | grep cs_devmon
This dumps the result of the last initialization into cs_dm.current on the DEVMON master. If a WPs cs_devmon file
has a size of 0, copy it from the AW to the WP.
(for 50 stations)
ps eaf | grep cs_devmon
(for 51 stations)
kill 9 pid
cd /opt/fox/bin/tools
omdel p DEV_MONITOR
cd /usr/fox/cs
mv cs_devmon.cfg cs_devmon.cfg.old
Device Names
PW - 3.5 F/D = /dev/fmh1 at v4.0=/dev/fh0
PW - 5.25 F/D = /dev/fh0 at v4.0=/dev/fh1
WYSE = /dev/fd0
AP/WP50 3.5 F/D = /dev/fd0
Floppy from single user mode = /dev/fd0c
Mirrored Drive = /dev/sd0
150 MB ST Drive = /dev/rst0
4MM 5GB TAPE = /dev/rst9
8MM Tape = /dev/rst1
There are instances where the newer tape drives will use the /dev/rst4 or /dev/rst36 driver. Make sure that the
thumbwheel on the back of the drive is set correctly.
Sun systems use the following naming convention to describe the logical device name for a disk:
/dev/[r]dsk/c#t#d#s#
The 1st # is the controller number.
The 2nd # is the target number.
In the above mentioned naming convention, there are also directories of the same devices known as the raw
partition. There is a /dev/sd0a as well as a /dev/rsd0a. The /dev/sd0a is accessed by blocks, is buffered, and is
mountable. The /dev/rsd0a is accessed by characters, is not buffered and is not mountable.
devnm <filesystem>
Identifies the device name associated with specified file system such as /usr, /opt, etc.
df command
df -t
on 50 stations
df -k -F ufs
df on 50 series stations reports amount of disk space occupied by currently mounted file systems, amount of used
and available space, and how much of the file systems total capacity has been used.
dft commands
To concatenate a drive:
(example is for the second drive; the one after the system disk. System disk is esp0 scsi3 and the second drive is
esp0 scsi2, the third is esp0 scsi1, etc.)
shutdown to single user mode
dft format_disk esp0 scsi2
dft add_to_sys esp0 scsi2
To mirror a drive:
(example is for the first mirrored drive; the first to hang on the second scsi port. First drive on second scsi is esp1
scsi3 and the second is esp1 scsi2, etc.) You do not have to shutdown to single user mode to mirror hard drives.
dft format_disk esp1 scsi3
dft create_sys
dft mirror_sys
dft show_status
It takes approx. 10 min. to mirror a 535 MB Hard Drive and approx. 20 min. for a 1 GB Hard Drive. Note: The
metastat command gives more information than the dft_show_status command.
diag_fist
Uses the tool fist and the files sldb and hldb creating an output with Station letterbug, station identifier, station
address, station type, host AP, system monitor host, and system monitor domain.
Use on AP20:
/usr/fox/bin/remote/diag_fist > fist_out
Use on AP50:
/opt/fox/bin/remote/diag_fist50 > fist_out
Use on AP51:
/opt/fox/bin/remote/diag_fist51 > fist_out
Report the lines that differ between file1 and file2, or if diroptions are specified, report the files that differ between
dir1 and dir2.
File options:
-b
-e
-h
-n
-C
num list of diff w/num lines of text -n produce script in opposite ord.
-D
Dir options:
-l
-s
report files that are identical -Sfile begin dir. comp. with file
If no option entered, a list is output indicating whether the file names common to both directories have the same
contents.
-d Compare contents of files with same name and output a list telling what must be changed in the 2 files to make
them the same.
-s Suppress messages about identical files
-wn Change width of output line to n characters.
The root (/) and /tmp should have at least 2000 blocks of free space (enough to tar in a floppy). The /usr partition
should have at least 4000 blocks free. Also check the number of free inodes. If files use up all the inodes free,
blocks will be inaccessible without an inode to reference the block.
50/51 Series
The Sun files system reserves 10% of total space in all partitions so when the df command shows a partition at
100% there is still space left. The recommended level for all partitions is less than 90% used for all partitions (Aps
/usr should be less than 95% used). The number of inodes should be less than 80% used.
How to find the directory or file filling up a hard drive partition. (also see HH1044)
To prevent false reports, start by taking the station down to single user, if possible. It is important that no stations
are left 'rmounted'. (Remember a WP51 always mounts its AW host)
Use the 'du' command to create a report file with the size of all directories of the partition that is full. Create report
file in a partition different from the one that is full. Suggested locations: /usr or /tmp (avoid /opt) /usr has been used
on examples below.
Example if /var partition is full:
cd /var
du > /usr/list
Look for non-familiar names at the beginning of the list, or abnormal size.
more list1
This procedure deletes UUCP, deflates the log file and stops crontab from writing to that file.
Another incremental log file that grows is online.log located in /var/tmp.
tail -100 online.log > retain.log
ln retain.log online.log
rm retain.log
Dump files on 20 series stations in /usr/fox/sysmgm/softmgr/dump can be deleted, these files will have extension
LBUG.0, LBUG.1, etc.
/opt partition problem may be historian sample files. Dir. on 20 series is u0, dir. on 50/51 is
/opt/fox/hstorian/bin/sample. Note: REMOVAL OF THESE FILES MEANS LOSS OF HISTORICAL DATA.
50 series crash files are located on AP/AW in /opt/crash/letterbug and in WPs /usr/crash/letterbug. There are 2
crash files which are created: UNIX.x and vmcore.x and vmunix.x (x=0,1, etc.)There are no crash files on
AP20/PWs.
In /var/adm there are two files wtmpx and utmpx. (log of users logging into station).
cd /var/adm
cp /dev/null wtmpx
cp /dev/null utmpx
Look in /var/adm/messages. Some of these older messages can be deleted. (These messages are report of all
messages during station bootup.
In /etc/fox/users_apps.log file there are usually no more than 2 or 3 lines in this file, however if an application is
crashing or corrupt, it may dump an enormous amount of garbage to this file.
For root space issues, a common place to look is /dev. Look in here for irregular items or typos such as someone
tried to tar off information to /dev/fo instead of /dev/f0, or redirecting a file to a printer (i.e. lp00 instead of LP00). If a
device file/Driver needs rebuilding, see Drivers Rebuilding Devices in this manual.
Check in /opt/fox/rpt_wrt/rpt_run to see if there are old report writer reports that can be deleted.
To free up space on /usr, the man pages may be moved to /opt and linked. See User notes for v4.0 B01193Q1. Rev
C 5.2.20.1.
When your root partition capacity is at 100% and you cant find any files to remove, theres the possibility that while
in single user mode, someone has tarred a file or directory that is root relative. The space increases the capacity
used by root. The system then gets rebooted and root gets mounted and the space that was used when in single
user mode is now hidden. Shutdown the AW/AP and do a boot s to go to single user mode. At the prompt in
single user mode execute the following du command: du / > /var/du.root. Examine the output file of the du
command. The space that was hidden while in the Multi User mode should now be visible. Remove the file or dir.
And reboot.
Umount all remote mounted stations and check the /rem directory for files named with the letterbugs of the
stations that could possibly be mounted. When trying to copy to a remote device that is not rmounted, a file by the
name of the station that youre copying to will be created in /rem. This file will not be visibile while that station is
rmounted, therefore it is necessary to rumount all stations to find this problem file/files.
Another way to free space on the /usr partition is by using loopback mounting to the /opt partition. An example of
this would be the /usr/disp directory:
mkdir /opt/disp
cp rp /usr/disp /opt/disp
rm r /usr/disp
mount F lofs /opt/disp /usr/disp
Caution: Make sure that directories which are being loopback mounted are not symbolically linked to other
directories. Also do not loopback mount to the / or /var partition. Usually loopbacks are only performed to the /opt
partition.
Use the du command to find what directories are using the most space.
The /proc directory exists only on 51 series. The /proc is actually a file system which provides access to the image
of the process in the system. Even though the du command will show this directory as using a lot of space in the
root partition, NOTHING should ever be removed from this directory.
If the root (/) partition fills up on a Solaris machine and you cant find the problem, try looking for a hidden file called
wastebasket. It is used by the Solaris file manager much the same way that the Recycle Bin is used on Windows
stations.
(where DM0000 is your Display Manager name) or if that doesnt work, try the commands below where W23A02 is
the DM name of the primary/first head on a dual-headed WP and W23A22 is the DMname of the secondary/second
head on a dual headed WP.
Kill first head DM
pref -W23A02 DMCMD "dmcmd dmexit"
(Where AW0001 is the letterbug of the station and DM0001 is the Display Manager Name)
If you run hi_init.cmd found in D:/usr/fox/exten, and then re-spawn the FoxView you will not need to reboot the
station to make the changes in the dmcfg take place. This is good for trouble shooting purposes so you do not need
to reboot after every little change. However, it is not the supported method of executing changes and the station
should be rebooted after trouble shooting is completed to properly execute any changes to the dmcfg.
dmesg
This command provides a listing of the systems last reboot (only on 50/51 stations). Another way to look at bootup
history is to do a more /var/adm/messages.x, where x = the message number. The higher the number, the older
the file.
dmpcfg
Historian tool:
dmpnam
Example:
dmpnam > /dev/LP01
dmpnam > filename
dmpstat
This tool prints the contents of __tdata for all sample collection points.
Example:
cd /usr/fox/bin/tools/hstorian/bin
/usr/fox/bin/tools/dmpstat
doscopy Command
doscopy filename dos!a:
(copies subdirectories)
On 50 Series there an be files greater than 1K in the /dev/directory but device drivers should never be that large. If
a devie needs to be recreated you an delete it and use the MAKEDEV script located in the /dev directory. For
example: If you wanted to create device ttyt0 you would type:
MAKEDEV ttyt
This would also try to create ttyt1-3. If they already existed you would receive a message.
51 Stations
On 51 Stations (Solaris 2.2 and up) devices are created when the box is booted with a boot r (reconfigure). Use
the boot r option to recreate a corrupted device. If the devices for tape or floppy drives need to be rebuilt, the
commands for rebuilding and linking these devices can be found in the /etc/rc2.d/S99FOXBORO script file.
be 10MB in file size or more. This is because the driver does not exist for the tape drive therefore the backup is
being written to a file in the /dev directory (/,root partition). An error is received while doing the dump that the / file
system is full. Follow the procedures below to build these drivers.
I have used the following procedure on AW51As, Bs, and Cs as well as the WPs. Following this procedure is one
that was used to rebuild drivers on an AW51E style. You also must know the device name that youre looking for.
Some dat tapes will use the rst9 and some (newer ones) will use rst4 or rst0, etc. Doing a boot r should build the
driver for you. If it is anything other than rst9, you will probably have to modify the dmp or restore script which
usually has rst9 as the device name. This method used on AW/WP 51 A,B,C:
rm /dev/nrst9
You can also stick a tape in the drive and try running the command :
/usr/local/add_periphs
Check the file /dev/nrst9 and see that it got built and is linked to nrst29. If the file still doesnt exist, type:
ln rst29 rst9
ln nrst29 nrst9
if doing a level 0 dump, substitute dmp0_8MM for the restore script above.
If mt returns status information, the tape drive is accessible, if not, correct the problem by: Verifying that /dev/rst9
is still a device driver and is linked to a rmt device driver. Verify power and cabling. Check the tape drives
adddress, A QIC tape drive uses SCSI address 4, a 4mm tape drive uses SCSI address 5. Use above method
for building drivers if necessary.
drvconfig
drvconfig creates the /devices directory tree which includes hardware devices.
drvconfig [-b][-d][-a alias_name][-c class_name][-I filename][-m major_num][-r rootdir]
-b
-d
-a
alias_name add the alias_name to list of aliases that this driver is known by.
-c
-i
-m
-r
dtree Command
dtree
du Command
Disk Usage
Syntax:
du [-asrk] [name]
AP20/PWs
cd /
du s * | more
50 Stations
cd /
du s * | more
51 Stations
cd /
du sk * | more
Dual Foxview DMs How to Display both DMs on boot on P92 Workstations
(HH1060)
The P92 workstation can accommodate dual monitors. Out of the box, only one monitor is active. This procedure
describes steps to activate the second head and make both FoxViews display on their correct monitors.
An Additional Display Manager (AADM7) must be configured in System Definition.
Add the Additional Display Manager to NAME in the /usr/fox/customer/hi/dmcfg file. The example below shows
RDM701 as the additional FoxView for the second head. Note that it must be configured as a floater (-) in the
dedicated monitor column.
# NAME [lbug] [dmname] [dedicated monitor(s)] [type]
#
NAME AAW701 AAW701 .0 NAME AAW701 RDM701 Write a script called 2nd_fv in /usr/fox/wp/data
if [ $DMNAME = $GCLBUG ]
then
/opt/fox/wp/foxview/foxview.exe
else
exit
fi
Edit /usr/fox/wp/data/fv_cmds. Place this line at the end of the file:
dmcmd wp_applic /usr/fox/wp/data/2nd_fv
Select Start, Settings, Control Panel, Display Properties. Select Settings folder. Pick and move box 2 to the
physical location (side by side or up and down) of the second monitor in reference to box 1 (primary monitor). A
message will appear to activate the second monitor. Select yes, then exit Control Panel.
Select File, Additional FoxView. (If the message "FoxView Not Available OK appears, you did not add the additional
display manager in SysDef.) If second FoxView does appear, move it to the second monitor. Then pick View,
Window Preference, Window Position, then "save now".
Shutdown and reboot.
Note: With two video cards installed, the second head can be configured as an extension of the desktop. Right
click the windows blue area of the screen > Display > Settings > click on the box with #2 > check the box that says
Extend my Windows Desktop onto this monitor for Dual Heads > Apply > OK.
Primary ECB
ECB11
Primary ECB
ECB1
Analog Input
ECB2
ECB4
ECB5
ECB6
ECB7
ECB8
ECB9
ECB11
ECB12
ECB13
ECB14
ECB15
ECB16
ECB18
ECB19
ECB21
ECB22
ECB23
ECB34
ECB36
ECB38R
ECB39
ECB41
ECB42
ECB43
ECB44
ECB46
ECB47
ECB52
DPIDA Controller
ECB53
Analog Output
ECB80
Port ECB
ECB81
ECB200
ECB200
Profibus Application
ECB201
ECB202
Method 1
Press Stop (L1) and n keys while turning the power on to the 50 series processor. This restores the default NVRAM
parameters defined by Sun.
Method 2
Performed from a Wyse terminal direct connected to a 50 series processor. These commands are used to change
parameters while in openprom mode (at ok prompt).
To get the current eeprom parameters:
printenv
Method 3
Wyse terminal:
eeprom input-device=keyboard
eeprom output-device=screen
Changing AW and WP NVRAM parameters to AP NVRAM parameters:
Method 1
In openprom mode on the AW or WP:
setenv input-device ttyb
Method 2
eeprom input-device=ttyb
eeprom output-device=ttyb
Problem: Sometimes a 51 series station may not boot up properly or send its output to the monitor due to incorrect
settings and may need to have the NVRAM reset to default values. On earlier models of SUN workstations the
NVRAM could be reset by holding down the Stop Key and the "N" key simultaneously while powering up the
station. On SUN stations that have USB peripherals the Stop "N" sequence does not work. This currently applies to
the P79 (51F) and P80 (51G) stations. In many cases the set-defaults command can be used to reset the NVRAM
parameters to their defaults but in cases where the input or output device has been changed you will need this
procedure.
Solution:
Note: The following procedure doesn't actually reset the NVRAM parameters to their default values. This procedure
enables the NVRAM parameters to be accessed to view their current and default settings as well as change them.
Resetting the NVRAM on 51F
Remove all peripheral connections to the station except for the KBD, Monitor and Mouse.
Power down the station by pressing the power button on the left front of the station and hold it for about 4-5
seconds until the display shuts down on the monitor.
Power up the station by pressing the power switch. You will have to wait any where from about 5 seconds up to 1
minute and 45 seconds until the power switch begins to blink and you hear an audible beep. The wait period
depends on which NVRAM settings have been changed. When the beep sounds, press the power switch twice
quickly like a double mouse click but a little slower.
When the monitor comes on if you were successful in pressing the power button at the proper time you will see the
following: Note the spelling of overwridden is incorrect but maintained because this is what the operator will see.
Safe NVRAM Mode, the following nvram configurations have been overwritten:
'diag-switch?' is true
'use-nvramrc?' is false
'input-device' 'output-device' are defaulted
'ttya-mode', 'ttyb-mode', are defaulted
At this point you must set the NVRAM values to the desired settings. Use the printenv command to see current and
default settings. Use the setenv command to set parameters to the desired value. See Examples at the end. Make
sure that the diag-switch? is set to false. Some NVRAM settings are set to default by this procedure and must be
manually reset in order for them to remain permanent.
If the screen comes up with the normal boot sequence information power down and repeat the procedure.
Resetting the NVRAM on 51G
Remove all peripheral connections to the station except for the KBD, Monitor and Mouse.
Power down the station by pressing the power button on the left front of the station and hold it for about 4-5
seconds until the display shuts down on the monitor.
Power up the station by pressing the power switch. The CDROM will flash after about 50 seconds the power led will
start flashing and give an audible beep. When the beep sounds press the power switch twice quickly like a double
mouse click but a little slower.
When the monitor comes on if you were successful in pressing the power button at the proper time you will see the
following: Note the spelling of overwridden is incorrect but maintained because this is what the operator will see.
Safe NVRAM Mode, the following nvram configurations have been overwridden:
'diag-switch?' is true
'use-nvramrc?' is false
'input-device' 'output-device' are defaulted
'ttya-mode', 'ttyb-mode', are defaulted
At this point you must set the NVRAM values to the desired settings. Use the printenv command to see current and
default settings. Use the setenv command to set parameters to the desired value. See Examples below. Make sure
that the diag-switch? is set to false. Some NVRAM settings are set to default by this procedure and must be
manually reset in order for them to remain permanent.
If the screen comes up with the normal boot sequence information power down and repeat the procedure. Printenv
Example:
printenv <RET>
Value
Default Value
test-args
diag-passes
pci-probe-list
1
7, c 3, 8, d, 13, 5
Setenv Example:
setenv diag-switch? true <RET>
1
7, c, 3, 8, d, 5, 13
Above messages received in control configurator going into a CP. Checkpoint process was running at the same
time - was able to kill the checkpoint process to fix. Also, if the ICC is already open in that CP/Gateway on another
AW/AP/WP, this message will be given. If the CP/Gateway is not completely booted, this message will be received.
Sometimes gateways on their first bootup will show booted green and on-line in System Management but you cant
get in them in the ICC. You get the error Database Operations In Progress. Look in /usr/fox/sp/files for a
DB<gateway letterbug>.UC file for that gateway. Copy the DB<gateway letterbug>.init file to the DB<gateway
letterbug>.UC file and it should finish booting. This usually is only a problem on the first time that a gateway boots
up or could be used when you have a corrupted checkpoint file in a CP or gateway.
The following commands are to be run on the station hosting the system monitor that is not responding.
ps -el | grep smon
find the number of the process of smon and use in the next line.
kill -9 141 (141 is the process id number)
The above error received while performing the Shrink Function. Shrink doesnt work properly after v3.0, so you
have to go into a library volume and initialize it then you can do the shrinks. Make sure youre in a library volume to
initialize or youll be looking for a new job.
h
d0f0
then press backspace
w
q
(d0f0 should be first two bytes of the display file)
The following information for the 'SP Error lck_chkpt' failure is from the Section 14. Integrated Control Configurator
B0193QL - Rev C of the 'Release Notes for Version 4.0 Operational Recommendations' document : 14.1.27
Workstation Reboot While in ICC If the Workstation Processor is inadvertently rebooted when in the Integrated
Control Configurator (ICC), the ICC attempts to clean up its database and leave the environment in a usable state.
When the system is busy, this can take a non-trivial amount of time. If the user immediately re-enters the ICC using
the WP which was rebooted, a number of Undesirable symptoms can occur.
As a result of this possibility, it is recommended that when such a WP reboot or other nonpermanent WP failure
occurs, the user should wait at least five (5) minutes before attempting to initiate a new ICC session using (1) the
same WP and (2) referencing the CP that was being edited when the reboot occurred. If the user doesn't wait long
enough, any or all of the symptoms listed below may occur. The top menu bar contains two overlapping sets of soft
keys.
When attempting to re-enter the Control Station which was being edited when the WP failure occurred, the user
may be returned to the initial display (Foxboro logo). When attempting to re-enter the Control Station which was
being edited when the WP failure occurred, the operation may be prevented due to the error "Open New
Configuration", "Remote Host Transfer", "Failure".
When attempting to re-enter the Control Station which was being edited when the WP failure occurred, the
operation may be prevented due to the error "SP Error lck_chkpt", "Failure". When any of the above symptoms
occur, the user should take the steps listed below to execute a manual recovery. To begin, the user should exit
from the ICC. Then, enter the VT100 screen from a different WP or use a Wyse terminal to log in to the host AP of
the CP which was being edited when the WP failure occurred.
The steps are as follows:
Execute the shell command "ps -auxww" if on a SunOs system or the command "ps -aef" if on a VENIX or
Solaris system. Note if a process "ciocfgtask.nhi" is active. If one or more such processes is active, note
the process id (PID) of the process where the command line contains the letterbug of the WP that failed. If
one exists, execute the following command: kill -9 PID
Execute a "cd" command to "/opt/fox/ciocfg/tmp" if on a Sun system or to "/usr/tmp" if on a VENIX system.
Perform the command "ls -CF". If you find a directory whose name is the name of the letterbug of the WP
that failed (WPLBUG), execute the command "rm -r WPLBUG" to delete that directory. (This operation
removes the left-over PASTE buffer, if it exists).
Execute a "cd" command to "/usr/fox/sp/locks", and then execute "ls -CF". If either a file with the name
fCPLBUG+ or one with the name sCPLBUG exist in this directory, delete the file(s). CPLBUG is the
letterbug of the CP that was being edited when the WP failure occurred.
Execute the command "/usr/fox/bin/rem_stop WPLBUG" where WPLBUG is the letterbug of the failed WP.
Finally, reboot the previously failed WP.
At this point the ICC may be entered for normal operations. Another thing to try is to review the
/opt/fox/ciocfg/tmp/<WPLBUG>.log file that gets generated for the AW51E on the boot host AW51.
(Find the line which reads REVISION CODE xxxx, at the end of the file. Check this with the Revision of another
CP.)
cd /
umount /dev/fh0
Above is second message received. If a load-all attempts to load ECBs when ECBs are already fixed or loaded in
the CP or Gateway, this message is returned. Picking yes causes the subsequent command to be loaded.
Error: unable to qualify my own domain name (APLBUG) using short name
(HH1035)
The following procedure is to prevent the following messages from appearing in the messages file and VT100
sessions.
Example:
Oct 25 09:31:12 20AP01 sendmail[9344]: unable to qualify my own domain name (20AP01) -- using short name
The issue was introduced by later version of sendmail installed as part of the higher patch level of that release. The
solution was from an Internet search, several hits indicated that the problem could be cleared by adding an
additional alias to the hosts file, appending a period '.' to the letterbug.
E.g.
151.128.8.65 AW51B1 AW51B1. loghost
It should also be noted that the start-up file for sendmail is renamed to /etc/rc2.d/s88sendmail (lower case s) to
prevent sendmail start-up by default.
/etc Directory
/etc/fox/loghost
/etc/aplns
/etc/cplns
/etc/histlns
/etc/histlocs
/etc/lblns
/etc/printers
/etc/wplns
File Types
Usage:
file [-c][-h][-f ffile][-m mfile] file
find
Use on AP20 and AP/AW51:
find / -name <filename> -print
To skip searching for a file in remote directories you should use the following arguments in your find command:
-fstype urfs prune o
To skip rmounted hosts
Example:
find / -fstype urfs -prune -o -name <filename> -print
Another Example:
(will locate all files that have a size greater than 2000 blocks or approximately 1MB (1 block = 512 bytes)
And Another Example:
find / -fstype urfs prune o mount mtime 2 size +100 ls
(will locate all files in root file system that were modified in the last 2 days and have a size greater than 100 blocks
@512 bytes/block=51200 bytes.)
And Another Example:
touch filename
fist
Will locate any station on the node. It prints out several identifiers and the network address of the station specified.
(Station letterbug, NSAP address, mac/ethernet address)
on AP20:
/usr/fox/bin/tools/fist <Station_Lbug>
on AP50/51:
/opt/fox/bin/tools/fist <Station_Lbug>
The AW51 (P81) doesn't recognize the USB floppy device because when the AW51 was rebooted, it didn't have
the USB floppy device connected. Do I need to reboot the AW51 (P81) to recognize my USB floppy drive?
Solution
Connect the USB floppy drive to the left bottom front USB connector.
For the Operating System Solaris 8 (On P80 and P81), the DOS 8.3 names are in upper case unless you use the -o
foldcase option. The foldcase option forces all upper case and mixed case names to lower case, in this way the
contents of the diskette will be treated as Solaris 2.5.1.
Solution 3
The below procedure is assuming that the contents of the MS-DOS diskette, is the following (Using the windows
explorer):
text1.txt
text2.txt
TEXT3.txt
TExt4.txt
Solaris 2.5.1
Mounting a DOS diskette and listing its contents:
mount -F pcfs /dev/fd0 /pcfs
ls /pcfs
(If you make a backup copy of these files before deleting, they should be stored in another directory, NOT
/usr/fox/wp/fonts) You must now tar in the custom fonts from diskette. You may get by with just tarring in the
*usr_mkr*.bdf files from the tape or floppy, but if the fonts are not correct, you will need to continue. Go into your
font_editor and load this custom file and save the font. Go back to VT100.
cd /usr/fox/wp/fonts
/usr/fox/wp/bin/tools/font_expand L o Lusr_mkr.bdf sr_mkr.bdf
/usr/fox/wp/bin/tools/font_shrink h o hhusr_mkr.bdf usr_mkr.bdf
/usr/fox/wp/bin/tools/install_fonts
Format Floppy
(20 series)
format /dev/fh0
(50 series)
fdformat -e
AIMAPI
an_init.tcp is located in d:\opt\aim\bin
an_init.cfg is located in c:\Program Files\aim\common
aimapi.cfg is located in d:\opt\aim\bin
FOXAPI
foxapi.cfg is located in d:\opt\fox\ais\bin
an_init.tcp is located in d:\opt\fox\ais\bin
an_init.cfg is located in c:\windows
When using the API Server Connection Utility, the an_init.cfg is located in the c:\Program Files\aim\common
directory.
1229
(use -1 repeatedly to exit foxtst)
FoxAPI and AIMAPI on the same station API Server Connection Utility
The following information obtained from HH1084. Note that the versions of FoxAPI/AIMAPI are important to
consider when troubleshooting API problems. See some of the other API problem/solution entries in this document
for more information when troubleshooting.
HH#: HH1084
IA Info: rss0501
Date: Mar 25, 2005
Subject: Having NetFOXAPI and NetAIMAPI on the same station.
Source: TAC, DEV
Problem:
The newer I/A networked client applications (IACC, FoxDraw, FoxCAE and 8.0 Alarm History Display) now have
the capability to configure connections to either FoxAPI or AIM*API servers using the new "API Server Connection
Utility" that is shipped with these applications. The problem occurs on I/A server stations that have both AIM*API
and FoxAPI installed and connection to the AIM*API server is already configured for the AIM clients that also reside
on that machine. All FoxAPI and AIM*API client applications identify FoxAPI and AIM*API servers by the station
name (typically the AW letterbug name). Running API Server Connection Utility will show if the named station is
configured as an AIM*API or FoxAPI server. If the user then proceeds to switch the named local server from
AIM*API to FoxAPI, then consequently this will disable the connection to the AIM server for all the AIM client
applications that are on that same station
Explanation:
There is now only one client configuration file (an_init.cfg) on the server station that is commonly shared by all AIM
and FoxAPI clients that are on the same station. The station has both FoxAPI and AIM servers installed. The
station name (typically the AW letterbug name) is used by the clients to identify both AIM and FoxAPI servers.
When the API Server Connection Utility is used the user has an option to switch the radio button to configure the
named station as either an AIM server or a FoxAPI server. Doing this switches the port number that is used for the
TCPIP networked connection to the server. The port for FoxAPI is 55555. The port number for AIM is 45678. The
associated port configurations are entered in the an_init.cfg file by the utility. Therefore switching the radio button
from AIM*API to FoxAPI will disable the connection to the AIM server for all the AIM clients that are on that same
station.
Solution :
Need to chose which server to alias, this can be done with the FOXAPI or the AIMAPI server. If you chose to alias
the AIMAPI server may run into issue of editing the an_init.tcp file from API_ADMIN utility .
Turn off FOXAPI or AIMAPI, need to turn off the server you chose to alias. This can be done for AIMAPI by
cd /opt/aim/bin and running apistop
In the AIMAPI or the FOXAPI directory make a backup copy of the an_init.tcp file called an_init.tcp.sav.
In the AIMAPI or FOXAPI directory need to edit the an_init.tcp file under the [AISNET] section the Host name will
be the letterbug, need to make this the alias name. Some times the Host parameter is not listed, in this case add
the line for Host.
Host = AW0001 change this to the alias, Host = AIM001 < /FONT >
Next is to change the an_init.cfg file. For Unix systems this is under the /opt/windu directory and for most IA NT,
XP and windows 2003 this is under the C:\windows directory. To ensure that you are using the correct an_init.cfg
file launch the API Connect Utility that comes with FOXAPI 4.3. This can be run from the START-Programs-API
Connect Utility pick that was installed. On the top of this utility it will display the Location of the an_init.cfg file. On
windows systems the location can also be found by going into regedit look in the following path. My
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SimSci\AIM\Settings.
Make a copy of the an_init.cfg file as an_init.cfg.sav.
Edit the an_init.cfg file, This can be done with the API Connect Utility. This is an example of a file that has the alias
has been set for the AIMAPI and the letterbug is being used for the FOXAPI.
[AISnet]
Printerr=0
tracelevel=0
logfileprefix=/tmp/an
Host=AW0001
MaxEnt=500
NrServer=100
Protocol=tcpip
Multiples=yes
maxlog=500
[TCPIP]
AW0001 = 151.128.16.65 55555 /dev/tcp 1024
AIM001 = 151.128.16.65 45678 /dev/tcp 1024
After these edits have been made need to restart the FOXAPI or the AIMAPI using aisstart or apistart respectively.
Issues that have been found with this solution:
Found that if the AIMAPI is aliased may not be able to edit the an_init.tcp file from the admin tool. Can change the
an_init.cfg file back to using AW0001 for 45678 and this will allow the editing of this from API Connect Utility and
then change the AW0001 back to 55555.
Can be confusing in the Historian manager, will see both the AW0001 as gray and AIM001 that is used.
When need to use the AIMServer need to use AIM001 vs. AW0001 in applications connecting to the AIMServer.
FoxAPI and AIMAPI User Cannot Connect to the API Server via IACC, the
API Admin Tool or the AIM*AT Historian Manager
The following information obtained from SOL dated 8/11/08. Note that the versions of FoxAPI/AIMAPI are important
to consider when troubleshooting API problems.
Problem Description:
v8.x P91 Windows 2003 Server with FoxAPI and AIMAPI installed. The application was working for months until the
IP address was changed on the second Ethernet card. After this change, customer could not use IACC because it
could not connect to server. It was also impossible to connect to the API Server using the API Admin Tool, which
gave the same error.
Failed to connect to server AW7101
Unable to communicate with server.
Fix/Resolution:
Open the AIM*AT applet from Control Panel and stop the AIM historians. Stop the AIM*API. Check task manager to
make sure that the apisvr.exe process eventually ends to signify that the AIMAPI has completely stopped.
When opening the API Server Connection Utility it gives the location of the an_init.cfg file as
C:\WINDOWS\an_init.cfg. This is the location of the an_init.cfg file if FoxAPI is being used. Changing the radio
button between FoxAPI and AIMAPI did not change the Location of the an_init.cfg file field at the top of the API
Server Connection Utility window. This was the problem. Every time the API Server Connection Utility is opened, it
changes the an_init.cfg file that is being used by editing the registry. To use AIMAPI you must edit the registry to
point to the AIMAPI an_init.cfg file and then NOT open the API Server Connection Utility. When you open this API
Server Connection Utility it will overwrite the registry to represent the FOXAPI files location.
Start > Run > regedit. Browse to HKEY_LOCAL_MACHINE > SOFTWARE > SIMSCI > AIM > and click on
SETTINGS so that the window on the right includes the an_init entry in the Name column. Double-click an_init and
edit the Value data field to point to the AIMAPI configuration file (C:\Program Files\aim\Common\an_init.cfg).
Close the regedit window, DO NOT open the API Server Connection Utility, restart AIMAPI via the AIM*AT applet in
the Control Panel, restart the AIM Historians if you wish to do so, and once the AIMAPI is back up and running
(apisvr.exe in Task Manager) then you will be able to connect to the API server via IACC, the API Admin Tool or
the AIM*AT Historian Manager.
How can the useaimapi=0 command string be enabled in the aimapi.cfg file so that FoxAPI will share OM lists with
AIMAPI?
Answer:
If the useaimapi=0 command string is not added to the aimapi.cfg file and both AIMAPI and FoxAPI are going to be
used, then they will both open their own Object Manager (OM) lists. This can weigh down a processor if there are
long OM lists and reduce the time to open OM connections when the I/A Series workstation is rebooted.
Edit the aimapi.cfg file to include the useaimapi=0 entry. Stop the AIM collectors and instances, stop AIMAPI and
stop FoxAPI. Go to the command line and enter the korn shell via:
d:
sh
cd /opt/aim/bin
start_server STOP
Check task manager to make sure that the foxapisvr.exe and apisvr.exe are not running anymore. These are the
processes for foxapi and aimapi.
Now, start FoxAPI via the Control Panel applet. Wait until the foxapisvr.exe process starts up in the task manager
then startup the AIMAPI via the Control Panel and AIM Historian instances and collectors.
With useaimapi=0 enabled, FoxAPI will share the OM lists with AIMAPI so that these lists will not be duplicated.
Also, you will notice that the AIM API Admin Tool correctly lists the AIM packages and their authorization codes,
configured users, etc whereas if the useaimapi=0 is not enabled properly, the AIM API Admin Tool could list
FoxAPI information. The document B0193YM Rev D describes the useaimapi=0 string on page 48.
211
Solution: This is an error with some versions of FoxAPI that keep it from communicating with I/A Objects. Proper
versions of FoxAPI along with the proper version of QFs should resolve these issues. FoxAPI v4.3.2 and v4.3.3
have this issue; however, v4.3.1 with the appropriate quick fixes works.
Select option:
900
Select option:
13
You will then be asked for a set number. Your data set will start with set 3.
Select option:
3
This will show you how many lists are open and will show their values.
Note: The 900 menu item was moved to foxspy after FoxAPI version 4.2.2. Enter foxspy instead of foxtst.
Example:
cd /opt/fox/ais/bin
foxspy
913
(will select option 900, then 13)
cd /opt/fox/ais/bin
foxtst
1200
29
tracelevel = 0
Host=2AW001
MaxEnt=500
NrServer=100
Protocol=tcpip
Multiples=yes
MaxWriteObjects=100
no_timeout=0
maxlog=50
S_STATION=2AW001
S_USER=ntdemo
;
[TCPIP]
;
;The next line should have the name of the FoxAPI server. If you
; have several servers, add them on separate lines.
;
; The line will read like this
; SERVERNAME = 152.155.28.90 55555 /dev/tcp 1024
;
2AW001 = 153.128.17.1 55555 /dev/tcp 1024
2AW002 = 153.128.17.2 45678 /dev/tcp 1024
;
[AIMServer Connections]
;
; The next line should have the name of your FoxAPI server also.
;
;
2AW002 = 2AW002 TCPIP 1 0 1 1 / 1
; make sure you remove the comment mark (;)
;
[IAServer Connections]
2AW001 = 2AW001 TCPIP 1 0 1 1 / 1
The AW with the letterbug 2AW002 in the above example hosts the AIM* historian. FoxDraw is
connecting to 2AW001.
Remove the *.DAT and *.INI files (The next time FoxSelect is selected, these files will be rebuilt). We will also
periodically get .INI and .DAT files in the (/) root directory and these are simply removed.
Foxview Files
/opt/fox/env
/opt/customer/env
*** In older versions of Foxview, the program looks to /opt/customer/env first then will use default
entry found. Can lead to customer editing /opt/fox/env and never seeing the result.
/opt/fox/env if no
We entered '264 380' into the registry and then tried to bring up the dialog box again. This time it worked: the dialog
box appeared normally and the change remained permanent in the registry.
Displays
/opt/menus/d1 default
/opt/fox/displib bitmaps, markers, faceplates, trends
Foxdraw
/opt/fox/wp/FoxDraw
FoxAPI
/opt/fox/ais/bin/an_init.tcp (on UNIX and NT)
c:\winnt/an_init.cfg (on NT)
This message appears on an NFS client that requested a service from an NFS server whose hardware is failing.
This message usually indicates server hardware failure. (See chapter on monitoring network performance in the
System Administration Guide, Volume II for more information.)
Stations CP0001 and CP0002 have checkpoint files that are approaching or have exceeded the maximum size of
1153020 and 1159463 respectively. Additional loading on these stations should be monitored.
(Both of these CPs are CP60s. The maximum checkpoint file size for a CP60 is 2.7 mb. For some reason, the
Foxwatch Report Analysis is using the wrong maximum size for CP60s.)
Also on the report was a suggestion that WP0001 had error messages occur since the last reboot. The error
messages were as follows:
"Aug 2 13:30:11 WP0001 unix: ecpp_isr: interrupt not for us.dcsr=c0800010
Aug 2 13:30:11 WP0001 unix: WARNING: interrupt level 3 not serviced"
(According to CAR# 1003863, this is a nuisance message and should be disregarded.)
The scripts (diag_frev/diag_frev50/diag_frev51) will awk station names from hldb, fist the station to find if it is on
line, identify the station type using sta_type file. It will then output the system information to standard output.
Note: Using the System Monitor Name as an argument (SYSMN1, for example) will limit the report to just the
stations contained within the indicated smon this may save time in a large configuration if you are targeting few
stations. This command can be used with no arguments.
The ftp command is the user interface to the Internet standard. File Transfer Protocol (FTP). FTP transfers files to
and from a remote network site. You can type man ftp to get more detailed instructions. Below is an example of
how I use it on an AW51 thats on the training system. This AW is not on the node, however I can transfer files
through its second ethernet port to the I/A node AW thats on the same network. The AW that Im transferring files
to is listed in both AWs /etc/hosts file as MYAW01. I am going to copy a text file (/opt/file1) and a binary file
(/opt/file2).
cd /opt
ftp MYAW01
Name/login: root
Password: password
Will get an ftp> prompt
bin
Open 51F station and install the optional Serial Expansion Card (P0971UB) in any of the 3 slots Be sure you
don't forget to put back the retainer screw!!! Connect the GCIO to the FIRST serial port of the 8 connectors. It is
marked as "0". Refer to B0400SR-C, page 34 if you need more details. See also B0400QM-A, v7.1 Release Notes,
page 22.
NOTE: Do not install the software from CDROM "SunSAI/P 2.0 and 3.0". The I/A v7.1 operating system already has
support for this card. Reboot box with "boot -r" from the ok> prompt so that the station will recognize the new
expansion card. While the box reboots, you should see lines for the new Serial Extender card:
...
saip:0 Using default configuration for saip8 #0
saip port:0x0 mem:0x4000000 ports:8 PCI SAI/8 V2.0
...
PCI serial adapter configuration initiated...
Starting saip daemon to download PCI Async firmware
...
After reboot, you should be able to see the new serial devices:
cd /dev/term
ls -l
2) SYSTEM DEFINITION
Use SysDef (2.4.1 or higher) to add the GCIOto the AW51F or WP51F station.
NOTE: You can NOT add a Serial Expansion card to a 51F!!! (See B0400QM for details). If you still try to do it you
will get: "Although physically allowed, one or more component attachments specified are not supported by I/A.
Those attachments will not be made" On Configuration Components View, add new Peripheral: GCDEV (Graphics
Controller) and attach (drag) it to the 51F station
NOTE:
On AW51F by default GCIO is connected to "Serial Port 3" (the other option is Serial Port 4). On WP51F by default
GCIO is connected to "Serial Port 1" (no more options). Add also any Modular Keyboards (M KBD) as needed. It
might look like this:
P000nn GCDEV
P000nn M KB
NOTE: Remember you can have up to 4 Modular keyboards for the same station. The first 2 are "M KB Modular
keyboard", while 3rd and 4th should be "MH KB Modular keyboard". The last 2 keyboards are to be connected to a
2nd GCIO.
Options, Utilities, Check Configuration
Options, Utilities, View Log Files
Ignore this error:
"ERROR: Station needs serial expansion board, but one not found: AW51F1"
Create Committal diskette using v7.1 10091 diskette
NOTE: Committal diskette has a file named "gcioport" with stations that have GCIO and their ports.
51F stations show as: AW51F01 ttyb
3) SOFTWARE INSTALLATION
After reboot
- Process "sxlinkd" is reported immediately after the serial ports from expansion card
If you don't see it, could be because you configured ALSO a direct serial printer The presence of
/usr/local/local_printer prevents "sxlinkd" from running S99FOXBORO starts sxlinkd as:
/usr/fox/exten/sxlinkd -f $GCIO_DEVICE where GCIO_DEVICE is: /dev/cua/a000 (51F) or /dev/ttyb (51G)
SysMgmt will show: GCIO in White If not, check /usr/fox/sp/wp_dta, verify DIP swicthes on both GCIO and modular
keyboard, etc.
NOTE: If you remove "local_printer" (or modify S99FOXBORO to ignore the presence of that file)
you might have both Serial printer (on port "1) AND GCIO (on port "0") working. This configuration is
NOT supported because Device Monitor doesn't know how to handle this situation.
=================
From B0400QM-A, v7.1 Release Notes, page 22:
1.2.12.1 Configuring a Model 51F Workstation with GCIO or Serial Printer
The Model 51F (Sun Blade 150) workstation has only one serial port, and would normally need a multiport serial
card installed and configured using System Definition in order to connect annunciator keypanels, a touchscreen, or
a directly connected serial printer. However, System Definition does not allow the configuration of a multiport serial
card on a Model 51F (Sun Blade 150) workstation. Due to remnant configuration parameters in System Definition
and software install, and the fact that the multiport serial card drivers are built in the Model 51F at boot time, you
can perform the following workaround that negates the System Definition problem.
NOTE
This problem also exists for the Model 51G workstation. However, Model 51G workstations are equipped with two
serial ports, and do not need multiport serial cards to connect annunciator keypanels, a touchscreen, or a directly
connected serial printer. The software installation process does not allow both a serial printer and a GCIO
configured through System Definition on the same machine.
To work around this issue, perform the following steps:
1. Do not configure a multiport expander card for the Model 51F workstation in System Definition. Simply create the
GCDEV or directly connected serial printer in System Definition, and physically connect the GCIO or printer to
Serial Port 1 on the workstation, as is done for a Model 51B, C, D, or E workstation.
2. Install the multiport serial card in the Model 51F station per the instructions in the workstation-specific document
shipped with your processor. When software install executes, it builds the serial port configuration parameters as it
did previously on the Model 51B, C, D, or E workstations, which have two serial ports.
3. Connect the GCIO or printer to the multiport serial card, using the first connector (0) for GCIO, or the second
connector (1) for a serial printer.
4. The multiport serial card drivers are created on bootup. When the devices are connected properly, SMDH,
Device Monitor, lpstat, and System Monitor messages show the devices as operational.
(wait until you get prompt back) (it might take longer if you have a lot of CPs)
more z
The command getpars is used to Create a formatted list with values of user defined parameters from the control
database.
SYNOPSIS getpars [-options]
Example:
To determine which PIDA blocks have the LIMOPT option set to 1 and redirect to a file named pida.list:
/opt/fox/bin/tools/getpars tpida mlimopt:%1d > /opt/fox/bin/tools/pida.list
Specifies a blocktype filter. Only blocks of the type t specified will be examined.
-m
Specifies a block parameter and how this parameter should appear in the report.
For other options and uses, see the getpars man page. The option "-n" is very useful to eliminate headers and put
everything from a block on one line. Reports created this way can be easily imported into Excel or similar
spreadsheets. The data comes directly from the control processors and gateways.
Please remember the limitations of this utility:
- Up to 20 parameters with one shot
- Can not get string parameters like: EO1, NM0, NM1, SCTXT0, SCTXT1, EU, etc
The only exceptions to this rule are name and description: NAME and DESCRP
Read /opt/fox/bin/tools/getpars.man to get more details on the use of this utility.
The following four examples show how to use this command.
Example 1: OVERVIEW DATABASE
This is the type of report advanced control companies usually request when they start their implemention. The
columns of this report are: BlockName - CompoundName - CPname - BlockType - Description
To create a report from ALL CP and Gateways in the system, type the following on a VT100 window. The report will be
saved as file 'z' on current directory.
cd /opt/fox/bin/tools
getpars -U4CP401* -n -mCMPNM:%15s -mCP:%7s -mTYPE:%7s mDESCRP:%32s
more z
Example 4:
To determine which PIDA blocks have the LIMOPT option set to 1, type:
/opt/fox/bin/tools/getpars tpida mlimopt:%1d > opt/fox/bin/tools/pida.list
glof
The glof command <global find> can be used to find a variable, global or process that is active anywhere on the
system. The glof command will search the entire I/A network.
Use AP20:
/usr/fox/bin/tools/glof -p <process>
Use AP50/51:
/opt/fox/bin/tools/glof -p <process>
The bold numbers represent the mac address and the italicized number represent the NSAP.
6C in the mac address represents a single Foxboro module
00006CC0xxxx in the mac address would represent a FT Foxboro module.
02xxxxxxxx in the mac address represents a PW station.
08xxxxxxxx in the mac address represents a 50/51 station.
glof LPXX
grep
The grep command searches files for a pattern and prints all lines that contain that pattern. The grep command can
be found in /bin.
Usage:
grep APLBUG /usr/fox/sp/hldb
(will look in hldb and print all instances of the APLBUG specified)
grep NOTYET IIF.cur
head command
Syntax:
head n <file-list>
Then, on AW0002, copy the contents of hist02.exp directory to a file for later recovery if needed:
tar cvf hist02122393.tar /opt/fox/hstorian/bin/hist02.exp/*
The next step is to change any instance of hist01 in the files to hist02.
cd hist02.exp
grep hist01 *
Do the above command in each file and save. Perform another grep for hist01 in that directory to make sure that all
instances of hist01 have been changed to hist02:
grep hist01 *
Once all instances of hist01 have been changed to hist02, a loadh50 may be performed.
Stop the historian and perform loadh50:
loadh50
2. Run foxtst
foxtst
3. From the Main Menu, select the "625 -(Menu 6) Historian" option. Enter the information requested, the example
below will give you an idea what type of information you need to type.
Note: To enter the old and end time, go to the following address to convert the regular time to UNIX time:
http://www.onlineconversion.com/unix_time.htm
Run apitst
apitst
From the Main Menu, select the "711 -(Menu 7) AIM*Historian" option.
Enter the information requested, the example below will give you an idea what type of information you need to type.
Bulk output to file? [ N]: y
Historian [ hist01 ]: hist01
Output File [ msg.txt]: smon.txt
Start time {04/17/02_06:14:13}=[1019024053]
Date? 04/16/02
Time? 12:00:00
Start time {04/16/02_12:00:00}=[1018958400]
Accept Date & Time [Y]y
End time {04/17/02_08:15:14}=[1019031314]
Enter "Now" for the current time!
Date? now
End time {04/17/02_08:15:51}=[1019031351]
Accept Date & Time [Y]y
filter [ *]: legacy:sysmommsg
ok to add? [ ]: y
APITST will provide the number of system monitor messages captures.
Historian = hist01
Start Time = 04/16/02_12:00:00 (1018958400)
End Time = 04/17/02_08:15:51 (1019031351)
Filter = *
Msg 1 legacy:sysmonmsg 04/16/02_15:28:34 to smon.txt
Msg 2 legacy:sysmonmsg 04/16/02_15:28:53 to smon.txt
2 messages printed into the smon.txt file. Note:
The smon.txt file can be create in the /opt/aim/bin or /opt/aim/inst/histname directory. Where histname is the name
of the instance
Do more on the smon.txt file.
more smon.txt
Where:
mon_msg.out is the file name and histaw is the historian name
Note: Typing fh_sacego <enter> will give all options and examples on how to use it.
3. Do more on the /opt/aim/bin/msg_mon file.
more msg_mon.out
You can use history to change the t in fint to a d and reissue the command by typing:
^fint ^find
when the VT100 window is exited. The history file is created and is named Text<pid>.<n>, where <pid> is the
process ID of the shelltool and where <n> starts at 0 and increments whenever the log file is cleared.
hldb
File that is built during the software install phase and is located in /usr/fox/sp directory. Use this file to: List all
stations on an I/A system and determine the type of the station.
more /usr/fox/sp/hldb
hopspy
Displays the contents of the OM open-point-list used by the Historian.
Usage:
cd /usr/fox/hstorian/bin
/usr/fox/bin/tools/hopspy
To determine the hostid on your Windows station, start your Aim APIAdmin and when connected to the AW will list
the hostid.
Note: If you see the process called startup in the results of running the file hps, then the historian is still starting
up, when it is completely finished starting, the startup process will disappear.
AIM* Historian:
cd /opt/aim/bin
histps
iaboot
The iaboot utility is a 50 Series version of the AP20 reboot program. Use iaboot to reboot other stations. Access
iaboot from the UNIX shell.
Use:
iaboot <station_letter_bug>
Warning:
The iaboot command used without arguments will reboot the local machine.
(to save the CP0001 database to a directory previously created named /opt/julie/cp0001)
iccprt Command
This script lets the user produce a report of all parameter names and values of all compounds and blocks in a
specified station or volume, Compounds within a station, and Blocks within a specified compound.
Location:
/opt/fox/ciocfg/api
Usage:
iccprt [-m num] [-n compound[:block]] [-o outputfile] station
where :
-n compound / block set to report on (defaults to ALL parameters of ALL compounds and blocks; wildcard
characters are supported)
-o file to which parameter data will be written
-m type of report (1,2,3 = parameter report) (4,5 = compound or block order report) (FOR BACKWARDS
COMPATABILITY TO PRIOR VERSION OF iccprt)
-p report on compound / block parameters rather than block order station control station letterbug
(required)
Examples:
To save parameters of all blocks and compounds of CP 3CP401 to ASCII file z:
iccprt p o z 3CP401
List all parameters in all compounds and all blocks to a file apicmp1.txt:
iccprt p n\* -o /tmp/apicmp1.txt C10A50
ifconfig
ifconfig is used to assign an address to a network interface and/or configure parameters.
-a apply commands to all interfaces in system
-ad apply commands to all down interfaces in system
-au apply commands to all up interfaces in system
ifconfig a
Installing fonts with the shrink & expand procedure on 50 series stations.
DO NOT TAR IN THE ENTIRE /USR/FOX/WP/FONTS DIRECTORY. YOU MUST ONLY USE THE SOURCE OF
THE FONT FILE THAT YOU CUSTOMIZED . Running install_fonts will compile. (i.e.,
/usr/fox/wp/fonts/usr_mkr.bdf)
cd /usr/fox/wp/fonts
rm usr_mkr.bdf
rm Lusr_mkr.bdf
rm hhusr_mkr.bdf
(If you make a backup copy of these files before deleting, they should be stored in another directory, NOT
/usr/fox/wp/fonts). You must now tar in the custom fonts from diskette. Go into your font_editor and load this custom
file and save the font. Go back to VT100.
cd /usr/fox/wp/fonts
/usr/fox/wp/bin/tools/font_expand L o Lusr_mkr.bdf usr_mkr.bdf
/usr/fox/wp/bin/tools/font_shrink h o hhusr_mkr.bdf usr_mkr.bdf
/usr/fox/wp/bin/tools/install_fonts
To install on v4.3 WP51 or AW51, you must first exit any open IFDC or ITMW applications.
cd /usr/fox/sp/lastinst
Copy the original REVLVL and SYSLVL files back into the recently edited versions.
If the development portion of Informix is installed, these variables will already be set.
To invoke type:
/opt/informix/bin/isql
rshd3.all -> A0A1 take jumper off R0 and put on P1 for 5 1/4 drives
rshd5.hstor -> A0A2 leave on R0 for 3 1/2 drives
rshd4.all -> A2 extra primary hard drive
Letterbug Pinouts
Last CP Reboot Determining the date and time of the last CP reboot.
To determine the date and time of a CP reboot on a 51 series station, you must determine which devices receive
system monitor messages:
cd /usr/fox/sysmgm/sysmon
/usr/foxbin/strings destact.cfg
Once youve determined which stations receive these messages, you can find the messages for that station using
the device listed.
To capture system monitor messages to a file:
See System Monitor Messages Capturing to a File.
This command lists time and date of all system reboots in the system log.
Letterbugs - Generic
WP10 G2BOOT
WP20 G3BOOT
WP30 G4BOOT
WP50 G5BOOT
COMM10 CSBOOT
Is a hard link. The two files share a common inode number. This gives you two ways to address the same file. It can
only be used in the same file system.
To cross to other file systems, you must use the symbolic link that uses the s switch as in:
ln s file1 file2
This creates a small file that creates a path to the name of the file in the other file system. When you do the ls l
command, you will see that the first character is the letter l. See the man page for more information.
loopback mounts
To create a loopback mount on a model 51 processor, use the following syntax:
mount F lofs <mount point> <special mount point>
lp Command
lp filename
will use the alternate LP00 as the default printer for the lp command.
lp n
number of copies
lpc Command
The main interface for user control is the lpc command. The lpc command will enter a command shell when it is
typed with no arguments and a Return. Use the lpc command to enable/disable, get status, clean queues and
start/stop printers.
lpc
h
lpstat Command
Usage:
lpstat [-d][-r][-R][-s][-t][-a[list]][-c[list]][-f[list][-l]]
[-o[list]][-p[list][-D][-l]][-S[list][-1]][-u[login-ID-list]][-v[list]]
-a
-d
-f
-o
-p
status of printers
-r
-R
-s
status summary
-S
-t
-u
-v
-l
long listing
lpstat -t
ls command
Syntax:
ls [-ladrsixCR] [dir-list]
-l
Long listing
-a
All files
-d
Directory information
-r
Reverse alphabetic
-s
Size in blocks
-i
I-node number
-x
-C
-R
to see how many changes will be made. IF the SYSTEM is SHORT ON DISK SPACE AND YOU ARE SHORT ON
TIME, DO NOT ENTER the catman command. You can still use the man pages without access to man -f, whatis,
and apropos commands. If there is plenty of space (17 MB)
catman
To view commands of only one section, when a command exists in many sections, enter the section number:
man -s 5 regex
If you are using truss to follow the execution of a process, a system call is listed per line. You can usually find the
call in section 2. A common command is "fcntl". Use:
man fcntl
Truss also shows errors returned to the executing program. These are all listed in intro(2). Enter:
man -s 2 intro
To read the index of all file formats documented in section four, enter:
man -s 4 intro
dmesg | more
Or
prtconf | grep mem
Mesh Constraints
Maximum of 1920 stations (1920 Legacy I/A Stations)
No more than 250 managed switches
No more than 30 system monitors
Switches are monitored by System Monitor
Switches must be configured
Maximum of 7 Switches between any 2 stations
Repeating hubs are not allowed
No routers between switches hosting Mesh stations
One port on each switch should be left for diagnostics (Sniffer attachment)
No VLANs
Mesh Generic Upgrade Plan (Starter) for Class C (no reboot of control
stations on legacy system)
The following is a summary of a generic MESH Class C upgrade plan to be used as a guideline when making your
own plan for a Class C installation. The documentation that came with your system should be followed for a
complete plan. The following is a summary, which is subject to change but may help in planning and preparations
for a major MESH expansion. (dated 5/18/07)
Pre-Installation Work to be done:
Upgrade all legacy stations to v6.5.3. If control station images are not at the v6.5.3 level, there is a chance of a
symptom called station islanding. Station islanding may become a problem after the MESH integration. See
advisory # 2007001abi for minimum revision levels. May have to disable NFD on those stations. Follow advisory
instructions.
Install switch hardware, run fibers, connect power, etc.
Install software on the P91 server and P92 stations offline. Install appropriate quick fixes.
Make appropriate System Definition Changes. (Use the Class C System Definition Changes procedure found in the
upgrade document). There is a summary of this configuration under System Definition MESH Upgrade in this
document.
Configure the switches.
Boot the ATSs to have configuration loaded into the ATS prior to cutover (both modules). We used a temporary
1x8 to configure the ATS with letterbugs.
Check peer-to-peers to make a plan to bypass if there are concerns about the loss of peer-to-peer connections.
Move CSA to a MESH station if it is to host control stations, otherwise CSA main remain on the legacy station.
Install the pre-v8.x compatability diskette on legacy stations to fix host files after the super commit. (After commit is
run through the stations, /usr/fox/bin/mkhosts.sh will need to be run to fix the /etc/hosts file.)
Cutover Procedure:
Make sure that the time is set ahead by a few minutes on the MESH host. Connect to the P MESH stations to the
network. One person is stationed at the ATS and another at the System Monitor.
Connect fiber connections to front of ATS.
Unplug the LAN module.
Install ATS as single module, boot up.
Attach the redundant connector to the backup ATS.
Connect fiber cables to the backup ATS.
Slide the backup ATS into the slot engaging both the cellbus and the Primary module.
Check System Monitor for good status on the ATS.
Go to next ATS/LAN and repeat.
(This plan is to be used only as a guide in creating your own plan. It may be helpful and used as a reference).
metastat Command
Displays current status for each metadevice (including stripes, concatenations, mirrors, etc.)
-h displays usage message
-p displays list of active metadevices and hot spare pools
-s setname specifies name of disk set on which metastat will work
-t prints current status and timestamp for MDB & hot spare pools
metadevice displays status of specific metadevice
hot_spare_pool displays status of specific hot spare pool
Example:
metastat d0
then type the following to check the status of the mirroring process:
dft show_status
It takes approx. 10 min. to mirror a 535 MB Hard Drive and approx. 20 min. for a 1 GB Hard Drive.
or
metadetach f /dev/md0g /dev/md8g
[1] 838
On 51 stations, for example:
metadetach f /dev/d0 /dev/d20
and
metattach /dev/d0 /dev/d20 &
Executing multiple dft show_status commands will show the progression of the re-sync process. The final status
should reflect a state of Okay if no errors were encountered.
mkhosts.sh
The file mkhosts.sh is on the pre-v8.x compatability diskette and should be run on legacy stations to fix host files
after the commit in a system where there are mixed Unix stations and Windows stations. (After commit is run
through the Unix stations, /usr/fox/bin/mkhosts.sh will need to be run to fix the /etc/hosts file.)
mkmact Command
Example:
/usr/foxbin/mkmact /usr/menus
Modem Commands
&v
View
atz
Displays configuration
Atz
b -r Reconfigure
more Command
Usage:
more [-cdflrsuw][-lines][+linenumber] [+/pattern][filename]
more filename
-d
-f
-l
-r
-s
-u
-w
-lines
+line
or
mount /pcfs
or
mount o ro F hsfs /dev/sr0 /cdrom
or
mount r /dev/sd6c /cdrom
Log into the remote processor as root and create the directory /cdrom if it does not exist: (you can actually use any
directory you choose as the mount point)
mkdir /cdrom
If there is no /etc/exports file, create it so that it will contain the line above. You must now export the cdrom
directory. If you modified an existing /etc/exports rather than creating one, export it by typing:
exportfs a
If you are creating /etc/exports for the first time, you must reboot the remote processor to export the /cdrom
directory, type:
sync
sync
reboot
(Root) partition:
mount o rw F ufs /dev/sd0a /mnt
(usr) partition:
mount o rw F ufs /dev/sd0g /mnt
(opt) partition:
mount o rw F ufs /dev/sd0h /mnt
Verify that all switches have the proper configuration parameters as specified in B0400DV. Use the latest revision
of the document under the User Documents for the latest release. For instance under L02-2 B0400DV-A is found
but under L03-1 B0400DV-B is found.
Verify that the status leds and links are operating properly on all RCNIs. All three link leds should be on and
blinking. There will be a difference in the blink rate for the "A" & "B" fibers since one cable will be the Primary for I/A
but there should still be activity on both.
Verify that leds on the NCNIs are operating properly. There should be a link led on for each cable connection on the
NCNI, CAT-5, Fiber or both. When there is activity on a cable the led will blink. The Nodebus led will blink when
there is a transmission to the Nodebus from the NCNI.
Verify that switches which have connections have the led on for receive. The receive led being on indicates link.
There should be activity on the receive led when a packet comes from the switch to the station. The Transmit (TX)
led will blink when the station sends a packet to the switch. Flashing red on the transmit usually indicates a transmit
problem such as a collision. Check the switch port settings for full duplex and auto-negotiation.
Symptom: Network Slowdown
1. Check for crossed cables between the "A" and "B" paths in the V7.x network. A crossed cable can also be
produced by setting the NCNI switch to the wrong position i.e. connecting the NCNI to a switch for cable "A" but
setting the Nodebus Selection switch to "B", connecting the cables from the RCNI to the wrong switch or making a
connection between a switch on the "A" cable to a switch on the "B" cable.
2. Check for bad or missing connections on the station that is the current Nodebus Test Initiator. A bad fiber link
between a RCNI and a switch on the station that is the current NFD Initiator can cause a slowdown if stations think
there is a problem with the cable that doesn't have a bad link. Note: This type of fault would have to be a fault that
does not cause a link loss but does create bad or intermittent communications on the cable with the bad link. 3.
Verify that the station is configured for redundant communications (nodebus) and not ethernet. Check the
CMX_STAND_ALONE parameter in the
/usr/fox/exten/config/loadable.cfg file. For redundant busses (Nodebus) you should see the following values.
Solaris Stations CMX_STAND_ALONE = 0
NT and XP CMX_STAND_ALONE=DNBI_PRESENT
If these values are not correct then a reconfiguration and re-committal will be necessary to properly configure the
station.
TCP/IP Communications Work But Not I/A Communications (Comex)
1. Check that the splitter cable is connected to serial port "A". IP doesn't need a certain cable to work but I/A won't
work properly if it can't switch cables and switch the "A" & "B" receivers on/off. If the Splitter Cable is properly
connected replace it. Verify that the Ethernet cable connected between the Splitter cable and the RCNI is Rev C or
higher for P0971XK, XL, XM and XN. Refer to SI 0-00528 for kits AG100WD, WE, WF & WG.
2. On XP stations verify that the Foxboro Protocol is only enabled for the NIC port connected to the RCNI. The
Foxboro Protocol should not be enabled (checked) on the Mother Board port but only on the NIC used for I/A which
is usually Local Area Connection 2.
I/A Communications Work But Not TCP/IP
1. Check that the proper subnet mask is set. Sun stations default to 255.255.0.0 NT stations 255.255.254.0 and XP
255.255.228.0. It is best to set them all to 255.255.0.0. Also verify that the Network portion of the I/A port is
151.128. Note a ping can work even if the netmask is not properly configured.
2. Verify that the Ethernet cable connected between the Splitter cable and the RCNI is Rev C or higher for
P0971XK, XL, XM and XN. Refer to SI 0-00528 for kits AG100WD, WE, WF & WG.
3. If the IP communications is going across a LAN to another node verify that the IP addresses for the destination
and source stations are in the correct IP range for the NSAP of each node. Check the CSC Web page under
Resources -> Troubleshooting Guides -> Tokenbus/Nodebus for a table of NSAP to IP ranges.
NFD thrashing between V6.x stations and V7.x stations has the potential to create cable problems. On V7.x nodes
verify that NFD has been disabled on all V6.x stations. The one exception is the LAN, which
can't be disabled at V7.0 & V7.1. A workaround is to manually select a V7.x station to be the NFD Test Initiator
even if a V7.x is already the Initiator. On V7.x hosts running NFD the utility nfd_debug can be used to determine if
there is NFD contention occurring between multiple NFD Initiators. See below for more information on nfd_debug.
To set a station as the NFD Test Initiator go to NETWORK in System Management pick NEXT LEVEL, if there are
LANs pick the LAN for the Node which hosts the station which is to be the Test Initiator, pick NEXT LEVEL and
select the station which is to be the Nodebus Test Initiator, select ONLINE DIAG and when the window opens
select CHANGE NODEBUS TEST INITIATOR. When the operation is complete use the CURRENT NODEBUS
TEST INITIATOR pick to verify.
Non Unique Letterbug Messages After Station Reboot
When a Non Unique Letterbug messages shows up in the smon_log this is usually caused by by a Network loop in
the system which allows cross communications between the "A" and "B" cables. Check for crossed cables or a
defective NCNI, RCNI. Check for crossed cables on segments other than the segment on which station reporting
the Non Unique Letterbug that won't boot is located.
Duplicate Mac Address Messages
If a station reports on Duplicate Mac Address when booting up, check for port mirroring being enabled on the switch
to which the station is attached. When the station broadcasts it's Mac Address if port mirroring is enabled on the
switch it may cause the station to hear it's own broadcast making it appear that someone else owns that Mac
Address.
Both Cables Fail or Wrong Cable Fails NFD Test After Breaking One Cable
There are several items that can cause NFD to fail a test. Verify the items in the Basic Network Checks listed
above. Usually an incorrect cable diagnosis is caused by crossed cables or a problem with the serial cable on a
station(s), preventing the station from switching cables. Check the station that is the NFD Initiator. Try changing the
NFD Initiator, running cable test and see if the same results occur.
Workstation Won't Read Letterbug
Verify that the proper letterbug is installed correctly in the RCNI. The letterbug must be installed before powering up
the RCNI in order for it to be read by the RCNI. Verify that the status leds on the RCNI are with one off and the
other on (green), on the upper right corner of the RCNI. Verify splitter cable is connected to serial port "A" on the
workstation. Verify that splitter and Ethernet cables are connected and working. Verify that the serial connection on
the splitter cable is connected to serial port A or Comm 1.
Workstation Won't Communicate Through RCNI to Other Stations.
nfd_log
Enable nfd_log on all potential V7.x NFD Test Initiators. The nfd_log will only record information on the station of
the current NFD Test Initiator. To enable nfd_log create the directory /opt/fox/sysmgm/nfd and then create the file
nfd_log. You will want to monitor the file because it will grow indefinitely. The nfd_log shows what stations are
requesting cable test and if stations are reporting Carrier Sense Errors (CRS).
nfd_debug
Enable nfd_debug for information on the current NFD Test Initiator is. This file will log information on all stations on
which it exists. You want to monitor the size of this file because it will grow indefinitely and at a fairly high rate. This
log is helpful to show how many stations each potential Initiator thinks are on the node and also who is the current
Initiator. To enable nfd_debug create the directory /opt/fox/sysmgm/nfd and create the file nfd_debug. A station that
is the NFD Initiator will report messages like the following in nfd_debug
2004-06-18 09:26:33 ev_timeout: my_state: MASTER, Not Refreshing --num_stas: 18
my_state: Master (says this station is the Master)
num_stas: 18 (Says NFD on this stations sees 18 stations on the node)
A station that is not the NFD Initiator will have a messages like the following in nfd_debug
2004-06-18 09:31:09 ev_timeout: my_state: Not Master, Not Refreshing -- num_stas: 20
(Message indicates this station is not the NFD Initiator "Not Master")
2004-06-18 09:31:16 Heartbeat Rcvd: Master: AW51F1, Override: 1,
Mast_type: 7d -- my_state: Not Master
(Message indicates that a NFD Initiator heartbeat another station "AW51F1")
2004-06-18 09:31:16 2. I_OVERRIDE: No Action
(Message indicates that no attempt has been made by this station to become the NFD Initiator by overriding)
smon_log
Enable the smon_log on all System Monitor hosts. This log along with nfd_log can help debug cable problems. You
will want to monitor the file because it will grow indefinitely. To enable smon_log create the directory
/opt/fox/sysmgm/sysmon and create the file smon_log.
get filename
netstat
Netstat shows network status. It displays the contents of various network-related data structures in various formats,
depending on the options you select.
Type:
man netstat
In /usr/fox/exten: Edit foxboro.local and add a # sign in front of the line in which nfd_8023 is started. Reboot the
station. If the station cannot be rebooted, edit the foxboro.local file as stated above and rename the nfd process:
cd /usr/fox/exten
cp nfd_8023 nfd_8023.bak
rm nfd_8023
In d:\usr\fox\exten: Edit foxboro.loc and add a # sign in front of the line in which nfd_8023 is started.
Reboot the station NOTE: renaming and killing the NFD process may cause the station to crash. If the node is part
of a multi-node system, only NFD on stations earlier than V6.5.2 in that node needs to be killed/disabled. If there is
a LAN interface in the node, NFD in this LAN interface cannot be killed/disabled unless they have the V7.1.1/6.5.2
LAN image or the associated QF1005591 for that image The
V7.1.1/6.5.2/QF1005591 LAN image is backwards compatible with other LAN images. In a node with a mix of
stations earlier than V7.1.1 and V6.5.2, the Nodebus Test Initiator will default to (one of) the V7.x station(s). There
is one exception: If there is a LAN interface in the node and it was made the Test Initiator manually (CHANGE
NODEBUS MASTER in the Network display in SMDH), the Nodebus Test initiator will stay in this LAN interface. In
all cases, the following needs to be done:
On mixed nodes with a LAN, you should manually select one of the V7.x stations to become the
NFD Initiator. This will avoid the possibility of NFD thrashing between the LAN and other V7.x stations. Every time
the V7.x NFD Test Initiator reboots, you will have to manually select it as the NFD Initiator. NFD Thrashing occurs
when a V7.x station tries to become the Master and thinks that it has but the LAN keeps taking the Mastership back
or when more than one station thinks it is the MASTER.
If the LAN image associated with V7.1.1/V6.5.2 or the associated QF1005591 has been applied, the LAN module
will not try to takeover as the NODEBUS MASTER unless there are no other potential masters available on that
node.
If a V7.x station is connected via an RCNI, the hardware between the RCNI and the nodebus is considered to be
part of the node by NFD (like a Nodebus Extender). This means, that interrupting one of the cables between the
RCNI and the nodebus will cause the complete nodebus cable (including the legacy part) to be declared BAD (BAD
CABLE x) in SMDH.
If a V7.x station is connected via a DNBT and the cable between the splitter cable and the DNBT is interrupted, the
station will be declared FAILED in SMDH (assuming it is monitored by another station), but the nodebus will not be
declared BAD.
In a multi-node system with V7.X stations on some nodes, do I have to disable the V6.x NFD processes on all V6.x
stations? No, V6.x NFD processes should only be disabled on those nodes that contain V7.x stations. The NFD
Initiator for each node is independent of the other nodes. It will process requests from other nodes for a local cable
test and forward requests to remote nodes for stations that are on another node but results of any cable test are
only applied to the local node.
Is there any advantage to connecting a Solaris 8 station (51F Or 51G) or an AW70P (XP) station to the node via an
RCNI versus a DNBT/DBNX? Yes, a Solaris 8 or XP station connected to the Nodebus using RCNIs/NCNIs will
provide a more stable Nodebus Master. Comex below NFD is responsible for finding a good cable combination for
a station to communicate on. On stations directly connected to the Nodebus, including DNBT/BX/BI connections,
cable faults such as constant carrier or Excess Collisions will cause Comex to change cable combinations in order
to find a good bus. If the NODEBUS MASTER (NFD) is running on a station with a direct connection then cable
fault reports and cable test results can be missed when Comex is changing cables. When a station is connected via
an RCNI/NCNI combination it is isolated from the collisions and constant carrier faults that station connected
directly to the nodebus see.
Does NFD run in a WP? No, in order to have NFD a station must be configured as an AW. Can I add switches to
Nodebus without adding a V7.x AW? When switches are added to a Nodebus a V7.x workstation is required in
order to have an updated version of NFD. The updated version of NFD will be able to detect and handle the type of
faults that can occur due to the multiple segments in the node created by adding switches. An exception to this
would be if there are V6.5.2 workstations on the node because they also have an updated version of NFD.
You can get the address of the NIC cards by selecting Network Connections > choose the proper connection >
Properties > general tab > move the mouse to hover over the driver name and the mac address and location are
displayed like this:
Local area connection: mac addr: 00-15-77-70-a6-5f slot 5
nd
nohup
The nohup command runs immune to quit signals and log outs. Both standard output and standard errors are sent
to nohup.out. (See also Background Running files in Background for more examples).
Usage:
nohup diag_syst r &
NSAP Addresses
NSAP of the Mesh
I000000
NSAP of Single Node System
I000001
NSAP of Multi-Node System
I000101
SET LOGNAME=%USERNAME%
SET PERLLIB=%NCDIR%\etc
D:
cd \opt\fox\bin\tools
sh
To set up so that it will execute from a dropdown pick from SftMnt:
2) Edit the /opt/fox/env/soft.mnu file so that there is an entry something similar to:
Nutcracker. run start /opt/customer/env/nutcrack.cmd
3) Change environment to one such as softw_eng that contains the SftMnt pick.
Note: Some versions of FoxView/FoxDraw have capital letters such as Softw_Eng.
4) Click the SftMnt label and select Nutcracker from the drop down menu. An MKS Korn Shell window will open
up in the /opt/fox/bin/tools directory.
right click my computer, manage > services & apps > services > double click
oma Utility
On AP20:
cd /usr/fox/bin/tools
oma
On AP50/51:
cd /opt/fox/bin/tools
oma
to add point:
a0 ffic_4401:input.pnt f
a1 ffic_4401:cntl.ma b
a2 ffic_4401:stnreq b
a3 ffic_4401:cntl.meas f
to change FFIC_4401 from manual to automatic:
s1=1
omset
Usage:
omset [-av] [-bcfils<value>]
-a alias -v variable
-b boolean -c character
-f float -I int. system performance
AW51B SPARC 5
AW51B1 SPARC 4
AW51C SPARC 20
AW51D ULTRA 5
AW51E ULTRA 30
AW51E1 (51E rev C) ULTRA 60
Optimize Displays
(20 series)
Packing the files removes the OM optimized data (OM list within the display file for quick OM connections). Once
the file is re-opened within the DM, the display file is re-optimized.
Device
Partition
50,51A,51B,51C
51D,51E
Name
/dev/md/dsk/d0
/dev/md/dsk/d0
/ (root)
/dev/md/dsk/d1
/dev/md/dsk/d1
Swap
/dev/dsk/c0t3d0s2
/dev/dsk/c0t0d0s2
Full Disk
/dev/dsk/c0t3d0s3
/dev/dsk/c0t0d0s3
MetadeviceDB
/dev/md/dsk/d2
/dev/md/dsk/d2
/var
/dev/md/dsk/d3
/dev/md/dsk/d3
INFORMIX DB
/dev/md/dsk/d4
/dev/md/dsk/d4
/usr
/dev/md/dsk/d5
/dev/md/dsk/d5
/opt
Device
SunOS
Solaris 2.5.1
Solaris 2.5.1
Partition
4.1.1
50,51A,51B,51C
51D,51E
Name
/dev/md0a
/dev/md/dsk/d0
/dev/md/dsk/d0
/dev/rmd0d
/dev/rdsk/c0t3d0s3
/dev/rdsk/c0t0d3s3
/dev/rmd0d
/dev/rdsk/c1t3d0s3
/dev/rdsk/c1t0d3s3
/dev/md0
/dev/md/dsk/d2
/dev/md/dsk/d2
/dev/rmd/0f
/dev/md/rdsk/d3
/dev/md/rdsk/d3
/dev/md0g
/dev/md/dsk/d4
/dev/md/dsk/d4
AP/AW /usr/partition
/dev/md0h
/dev/md/dsk/d5
/dev/md/dsk/d5
This will change the password to newpassword and update the dmpasswd_cfg file with the new password.
cd /
umount /dev/sd0a
Reboot the AW. After software installation, shutdown the system to single user mode, then
cd /etc
cp path_to_inst.B path_to_inst
If you are on a B then copy the path_to_inst.B instead of path_to_inst.A. The same if youre on an AW51C, copy
the path_to_inst.C instead of path_to_instA.
Period
Phase
Phase
Value
Length
Values
Value
Length
Values
0.1 sec
Not
Allowed
10 min
[0-1199]
0.5 sec
[0] default
60 min
[0-7199]
1.0 sec
[0,1]
0.2 sec
Not
Allowed
2.0 sec
[0,1,2,3]
10
5.0 sec
[0-9]
10 sec
[0-19]
11
0.6 sec
[0] default
30 sec
[0-59]
12
6.0 sec
[0-11]
1 min
[0-119]
13
0.05 sec
Not
Allowed
count, or the 3 count. A Phase value greater than three in this example exceeds the maximum modulo count and
the block will never be executed. Generally, the legal phase values are the integers from 0 to N-1, where N equals
the number of BPCs in the Period. Thus, a block having a PERIOD/PHASE assignment of 3/1 executes every 2.0
seconds in the second BPC frame of the two second period.
ping Command
The ping command is sometimes used to check the communication from one station to another via Ethernet ports.
For example, to see if communications have been established between AW5101 and WP5101 across the hme1
port, in a VT100 session on AW5101, type:
ping <Ethernet address or name assigned in /etc/hosts file>
You should be able to ping from either station to the other. Another use of ping is to capture packets to a station.
The following command will monitor the communications between the AW where the command is performed and a
WP named WP5101:
ping srv I2 WP5101 64 30
pg Command
Usage:
pg [-number][-p string][-cefnrs][+linenumber] [+/pattern][filename]
-c
-number
-r
-f
+linenumber
+/pattern
pg filename
ls | pg
pr Command
Usage:
pr
[[-columns][-width][-a]][-eck][-ick][-drtfp][+page][-nck][-ooffset][-llength][-sseparator][-h
header][-F][filename]
+page
-columns
-a
-m
-d
-eck
-ick
-nck
-wwidth
-ooffset
-llength
-hheader
-p
-f
-r
-t
-s
-F
pr filename
(file appears on screen formatted into numbered pages with header w/filename and date and time)
pr -2 filename | more
pref Command
Usage:
pref [-<lbug>] <vbl> [<value>]
Examples:
pref -WPLBUG dmcmd /usr/disp/displayname
forces station WP0001 to display the detail display for PID block COMP:BLK
Open 51F station and install the optional Serial Expansion Card (P0971UB) in any of the 3 slots. Be sure you don't
forget to put back the retainer screw. Refer to B0400SR-C for details. NOTE: Do not install the software from the
CDROM "SunSAI/P 2.0 and 3.0". The I/A operating system 7.1 already has support for this card. Reboot box with
"boot -r" from the ok> prompt so that the station will recognize the new card.
While the box reboots, you should see lines for the new Serial Extender card:
...
saip:0 Using default configuration for saip8 #0
saip port:0x0 mem:0x4000000 ports:8 PCI SAI/8 V2.0
...
PCI serial adapter configuration initiated...
Use SysDef (2.4.1) to add the new serial printer to the 51F. NOTE: Do not add a Serial Expansion card to this box!!!
(See B0400QM for details). On the Configuration Components View, add a new Peripheral. SysDef allows you to
choose only these printers:
P80BWS 80 Dot-Matrix,B&W,Ser
P132S 132 Dot-Matrix,B&W Ser
P136S 136 Dot-Matrix,Color Ser to 51F
Select "Serial Port 3" for 'Connection'. (Only other option is "Serial Port 4")
Tip: copy an existing line, paste it, and edit it. The line should look like these lines
LP01 0002 80 Dot-Matrix,B&W,Ser
LP01 0004 132 Dot-Matrix,B/W,Ser
LP01 0005 136 Dot-Matrix,Color,Ser
After copying the line and editing use the "set list" command to view invisible characters and verify
that all lines are the same length. Make sure all the columns and dollar signs line up. type
:set list
Reboot box.
7) FINAL VERIFICATIONS
System Management should now show Serial Printer (LP01) as a printer with a CLASS NAME =
OKI132 (or similar, under EQUIPMENT INFO)
You should be able now to print by redirecting files to /dev/LP01
cat /etc/printers > /dev/LP01
Printer Troubleshooting
The best printer troubleshooting guide in the world can be found on the Schneider Electric TAC Global Support
Webpage, which was authored by Angel Corbera. I cannot put all of the information in here because it is a booklet
by itself. Great job, Angel and thank you!!!
Use a text editor to add the following lines in the ps_interface file after the line that reads:
internal_lpset ${cpi}${lpi}${width}${length}
Add these lines:
####
# Set the lines/page to 66 lines
####
echo \033%-12345X@PJL DEFAULT FORMLINES=66
echo \033%-12345X
The value g.50 represents the gamma correction value. Gamma factor: 0.25 < gamma < 1: 1=normal,
0.25=brighter
Sending the HP1200C/PS printer a Postscsript file (i.e. Printscreen from a 50 series workstation) clears the setting
and requires it to be resent. However, the above command can be added to a script, or the escape sequence can
be added to the beginning of the ASCII file.
Printing from Model 51 stations
On a Model 51 station, a script file can be modified such that the lp command issues the escape sequence to the
printer prior to printing and also a Form Feed to eject the last page. To implement this, make the following change
on each AP/AW/WP51.
cd /etc/lp/interfaces
cp LPXX HP1200
disables scheduler
/usr/lib/lpsched
enables scheduler
To change default printer:
lpstat -t
/usr/lib/lpshut
/usr/lib/lpadmin -dLP02
/usr/lib/lpsched
lp /etc/inittab
(This line to check to see if you get a printout at new LP02 (new default)
then check /etc/printers to see if LP02 is there, if not, copy that file from other AP
80 Dot-Matrix,B/W,Ser
0002
80 Dot-Matrix,B/W,Ser
0002
80 Dot-Matrix,B/W,Par
0000
80 Dot-Matrix,Color,Ser
0005
132 Dot-Matrix,B/W,Ser
0004
132 Dot-Matrix,B/W,Ser
0004
132 Dot-Matrix,B/W,Par
0005
136 Dot-Matrix,Color,Ser
0004
136 Dot-Matrix,Color,Par
0006
Color Ink-Jet,Ser
0006
Color Ink-Jet,Par
0006
Deskjet Printer,Ser
0010
Deskjet Printer,Par
0006
PS Postscript Printer
0010
PS Postscript Printer
0006
PC PRINTER
Note: The description of a PostScript printer does not tell you if the interface is Serial or Parallel, however the
PORT TYPE is 0006 for Serial, and 0010 for Parallel. (Above information taken from Angel Corberas Printer
Guide) PARALLEL DIRECT CONNECT PRINTERS CONNECTED TO 50 SERIES STATIONS ARE TO BE
CONFIGURED TO PORT 2.
Printing Compounds And Blocks To Text File And Copy to Dos Formatted
Disk
1. get formatted DOS diskette
2. go into Ctrl-Cfg and select the Cp, then select print all compounds and blocks.
3. select cancel before sending to printer
4. will put in a file in directory called /usr/tmp (there will be a filed called [WPLBUG]print the
following commands are assuming the letterbug is PCAT00
5. goto VT100
doscopy -a PCAT00.print dos!a:CP0001.new
or on 50 series
mount /pcfs
cp PCAT00.print /pcfs
On a 51D, you can use probe-ide since the 51D does not use SCSI drives.
probe-ide
Note that compalarmcfg refers to the configuration file name and compalarmrpt refers to the report name.
To run the script, call it from the command prompt as follows:
cd /usr/fox/psr/files
alarmrpt.ksh
or through windows scheduler by creating a .bat file with the following replacing WP0001 and LP01 with your
AW/WP name and Printer name:
print /d:\\2WP016\LP04 d:\usr\fox\psr\files\PSR_MANUAL_RPT.txt
prtconf
This command prints system information. The output includes the total amount of memory, and the configuration of
system peripherals formatted as a device tree. To find out the port for the second ethernet port, type:
prtconf | grep le
or
prtconf | grep hme
ps Command
Shows what processes are currently running with process ID numbers.
ps -el (AP20)
ps -eaf (AW51)
ps -aux (AW50)
Example :
ps avx
Display status info. about all active processes controlled by any terminal
State of process
Running
Sleeping
Waiting
PID
PPID
TTY
TIME
CMD
Another version of the ps command can be found in /usr/ucb and will provide information such as %CPU, %MEM,
PID and more.
/usr/ucb/ps aux | more | sort nrt3 | head
This command will return the information sorted by the process using the most CPU time.
psrinfo
psrinfo v
This command prints the time of the last station reboot, and the speed of the stations process(s), in MHz. It is only
available on Solaris (51-series) machines. Note: This command can be used with no arguments.
pstat
Usage:
pstat -s
-s Print information about swap space usage. For use on 50 series systems only.
or
cd /tmp
rcp AP5101:/usr/disp/* `pwd`
or
cd /usr/disp
iaboot without specific letterbug reboots the station youre logged into.
redinfo
Allows the user to view reduction group status information.
Usage on 20 stations:
cd /usr/fox/hstorian/bin
/usr/fox/bin/tools/redinfo
Usage on 50 series:
cd /opt/fox/hstorian/bin
redinfo
remd/remv
The remv process is the operator interface (VT100) to remote administration SMDH from a WYSE terminal and
remd provides that dispatch interface to filter and determine all messages, counter information, station information,
and ECB information.
a)The remd/remv files can be located in:
On AP20:
/usr/rem/remd/remd and /usr/rem/remv/remv
On AP50/51:
/opt/rem/remd/remd and /opt/rem/remv/remv
b)To use remv, remd must first be running, remd should be running on only one AP on the entire network.
To start remd on an AP20:
nohup /usr/rem/remd/remd &
c)To examine system monitor functions from a VT100 terminal (interactive mode).
Use on AP20:
/usr/rem/remv/remv
Use on AP50/51:
/opt/rem/remv/remv
Syntax:
remv [-d<domain name>[-s<station name>[-e<ECB name>[-[c][r][t]]]]
-c
-r
Example:
remv -dSYSMO1 -sAP2100 -cr
Verify that the process mles is running on the application host station. Try running the script manually substituting
variables for $TMHST and $GCLBUG. Get TMHST and GCLBUG values from the /usr/fox/IIF.prm file
grep APLHLB IIF.prm (TMHST)
grep MSGLN IIF.prm (GCLBUG)
Example:
dmcmd script
dmcmd run /usr/fox/bin/rem_strt 5 AW0001 /usr/fox/bin/run_cio WP0001
The above sript would start up the Control Configurator on AW0001 and the Display results and user interface on
WP0001. Verify that /etc/fox/loghost contains the proper Logical Host Letterbug.
grep APLHLB IIF.prm
Verify proper rmount directories are present on Initiator station and Application Host station. Also check the
permissions of the rmount directories.
Check the sum of the rem_strt process in /usr/fox/bin
sum /usr/fox/bin/rem_strt
Remote Copy
See rcp.
(if on an AP or AW)
or
wprestore_8MM
(if on a WP)
or if using the new backup and restore utilities
restore
Change to a temporary directory and start the ufsrestore command with the interactive option. The number 3 in the
ufsrestore command is for the /usr partition on the tape. (/ =1, /var=2, /usr=3, /opt=4 on AP/AWs, On WPs its /=1,
/usr=2, /opt=3)
cd /opt/tmp
ufsrestore ifvs /dev/rst9 3
Prompt changes to ufsrestore. A ? at the ufsrestore prompt will provide help on interactive mode. Display the
contents of the directory structure on the dump volume.
ls
(This flags all files named REA* to be extracted from the directory /usr/PDEMO/HI/annunc. Marked files will show
an "* in front of them).
delete REA*
(This clears them from extraction. It does not actually delete the file)
add REA*
add .rhosts .wastebasket
extract
When it asks you to specify the next volume, specify 1. When asked to set owner/mode for .? Specify y. Set
modes anyway? Specify y. Exit the interactive restore once the files are extracted.
quit
ls R /opt/tmp
Note: The extraction of the REA* files caused the creation of the parent directories (/PDEMO/HI/annunc) under the
/opt/tmp (where we originally started). Now these files can be moved or copied wherever they may be required.
When the exact location of the files is known and/or only a few files are required, the Direct mode below proves to
be faster.
The above command looks at the 1st partition on the tape (/dev/rst9) and prints those files to screen. You may have
to change the tape device name is not using the 4MM tape. To look for a particular file in the /usr partition. The
following will look in the /usr partition on the tape for the file named /usr/disp/boiler1.
ufsrestore tfs /dev/rst9 3 ./disp/boiler1
Since the file is in the /usr partition on the tape, the paths start with ./ and looks for /usr/disp/boiler. To extract files
from the tape: (Example) To get the file named /etc/hosts off the tape, you must first change directories to / (root).
The ufsrestore command places the files starting at the current directory.
cd /
ufsrestore xfs /dev/rst9 1 ./etc/hosts
It will ask you to specify the next volume, type in 1. It will also ask if you want to change the permission/mode and
you will answer y. The last question asked is if you want to change these permissions anyway and the answer is
y. Another example: To restore the /usr/fox/sys/Change_Env directory off the tape, you must first change
directories to /usr.
cd /usr
ufsrestore xfs /dev/rst9 3 ./fox/sys/Change_Env
/var =
/usr =
/opt =
/usr =
/opt =
The above command looks at the 1st partition on the tape (/dev/rst1 which is the 8MM tape) and prints those files to
screen. You may have to change the tape device name is not using the 8MM tape. To look for a particular file in the
/usr partition. The following will look in the /usr partition on the tape for the file named /usr/disp/boiler1.
/etc/restore tfs /dev/rst1 3 ./disp/boiler1
Since the file is in the /usr partition on the tape, the paths start with ./ and looks for /usr/disp/boiler.
To extract files from the tape:
To get the file named /etc/hosts off the tape, you must first change directories to / (root). The restore command
places the files starting at the current directory.
cd /
/etc/restore xfs /dev/rst1 1 ./etc/hosts
It will ask you to specify the next volume, type in 1. It will also ask if you want to change the permission/mode and
you will answer y. The last question asked is if you want to change these permissions anyway and the answer is
y. Another example: To restore the /usr/fox/sys/Change_Env directory off the tape, you must first change
directories to /usr.
cd /usr
/etc/restore xfs /dev/rst1 3 ./fox/sys/Change_Env
/var =
/usr =
/opt =
/(root) =
/usr =
/opt =
rexec
The rexec command allows the remote execution of a command from the current AP to an AP specified in the
argument list. On AP20 it is located in /usr/bin and on AP50/51 it is in /usr/local.
Dont rmount to do this.
Use: rexec <ap_letterbug> command
Or rexec <ap_letterbug> /bin/sh
Example:
rexec APLBUG /usr/foxbin/mkmact /usr/menus
or
rexec APLBUG /bin/sh
rm Interactive
You can perform an interactive rm r by typing:
rm ri
This will ask you whether to remove each file in the directory. Answer y to the problem file and n to everything
else. Unfortunately, this command will walk through every subdirectory and does not work with many versions of
rm. You can do a chmod a-x to those directories temporarily to make them unsearchable. The best thing to do is
to use the rm command with extreme caution and you wont have to worry about it.
rmount
rmount APLBUG /rem/r0
(or)
rmount APLBUG /rem/r1
Example:
rm_station 21AP20 21CP10
In this example, 21CP10 will be removed from the SICT tables and will no longer be able to boot.
Output goes to the screen and is a combination of the V7.x nfd_debug and nfd_log.
route Command
51 series:
(HH950)
To add the default router upon an AW/AP reboot you must initiate the route add" at boot up. If you have only one
hop you can add the IP address and router name to /etc/hosts and /etc/defaultrouter. If you have more than two
hops from the AW/AP to your client machine it is recommended you use /etc/fox/user_apps.dat. Create
/etc/fox/user_apps.dat if not created using your favorite editor. Add the path for your executable:
vi /etc/fox/user_apps.dat
To add routers on the fly without initiating a reboot perform the following;
netstat -r > routetable
OR
route add {Router1 IP} {Router2 IP} 2
Above line may be added to /etc/rc2.d/S69inet for recognition of these IP addresses on bootup of the AW. Add the
above line for every PCs IP address to the end. This is helpful when your PCs obtain a new IP address on bootup.
You can add the entire range of IP addresses to this file.
rumount
rumount APLBUG
@
6. Do more on the mon_msg file.
more mon_msg
7. To verify that smon_log is capturing the system messages, perform a checkpoint on the CP Database. This can
be done from SMDH or ICC.
8. Do more on the /opt/fox/sysmgm/sysmon/smon_log file.
cd /opt/fox/sysmgm
more smon_log
9. Periodicly check the size of the smon_log file because it may grow very fast and can take some space in the /opt
partition.
samspy
Legacy Historian:
Used to display the contents of the extended sample files which are located on the extended drive /u0.
Usage on AP20:
/usr/fox/bin/tools/samspy
or for 50 series:
/opt/fox/hstorian/bin/samspy
save_all Command
For a detailed description of the save_all command, go to the section titled Utilities: Upload, Shrink, Checkpoint,
Save_all.
5. Copy all files and directories from the diskette to the new directory.
Example:
cd /f0
cp -r * /opt/unix62
cp .Compound_Dir /opt/unix62
eject /dev/fd0
ON THE NT STATION
1. Open a DOS Command Prompt window and run the Korn shell.
Example:
ncenv
d:
sh
3. Insert the diskette created on step 8 of the Method 1 Control Database On Diskette procedure.
4. Tar back all files and directories in the new directory.
cd /nt62
tar xvf a:
5.2
Select all folders and the .Compound_Dir file and copy all of them to a DOS formatted diskette
(This will be your NT SaveAll).
6. Open ICC and perform a LoadAll using the diskette created in the step 5.
ON UNIX STATION
1.
If the Control Database is loaded on a CP or Micro I/A or an AW51x use this procedure.
2.
3.
Example:
cd /opt
mkdir unix62
4.
Example:
cd /opt/fox/ciocfg/api
5.
Perform a SaveAll, running the save_all utility. ICC should not be opened.
Example:
Example:
tar cvf /dev/fd0 *
tar rvf /dev/fd0 .Compound_Dir
eject /dev/fd0
ON THE NT STATION
1. Open a DOS Command Prompt window and run the Korn shell.
Example:
ncenv
d:
sh
3. Insert the diskette created on step 6 of the METHOD 2 USING ICCAPI AND CONTROL DATABASE LOADED
ON A STATION procedure.
4. Change to the new directory and tar back all directories and the .Compound_Dir file.
Example:
cd /opt/nt62
tar xvf a:
5. Change to the /opt/fox/ciocfg/api and un the load_all utility. ICC should not be opened.
Example;
cd /opt/fox/ciocfg/api
load_all CPLBUG /opt/nt62
ON THE NT STATION
1. Open a DOS Command Prompt window and run the Korn shell.
Example:
ncenv
d:
sh
5. Eject the floppy and insert a diskette formatted in the UNIX station.
6. In the new directory, tar back all directories and the .Compound_Dir file.
Example:
cd /opt/nt62
tar cvf a:
4. Change to the new directory and tar all directories and the .Compound_Dir file.
Example:
cd /opt/unix62
tar xvf /dev/fd0
ON DISKETTE
7. Make a file System check, mount the diskette and remove the lost+found directory or formatted the diskkette
from ICC and then mount it.
Example:
newfs /dev/fd0c
8.
Example:
cd /opt/unix62
cp -r * /f0
cp .Compound_Dir /f0
10. Open ICC and perform a LoadAll using the diskette created in the step 9.
METHOD 2: U/SING ICCAPI AND CONTROL DATABASE LOADED ON A STATION
ON THE NT STATION
1.
Open a DOS Command Prompt window and run the Korn shell.
Example:
ncenv
d:
sh
Example:
cd /opt
mkdir nt62
3.
Example:
cd /opt/fox/ciocfg/api
4.
Perform a SaveAll, running the save_all utility. ICC should not be opened.
Example:
save_all CPLBUG /opt/nt62
5.
Example:
tar cvf a:
2.
Example:
cd /opt
mkdir unix62
3.
Insert the diskette created on step 5 of the METHOD 2 USING ICCAPI AND CONTROL DATABASE
LOADED ON A STATION procedure.
4.
Change to the new directory and tar back all directories and the .Compound_Dir file.
Example:
cd /opt/unix62
tar xvf /dev/fd0 *
5.
Change to the /opt/fox/ciocfg/api directory and run the load_all utility. ICC should not be opened.
Example;
cd /opt/fox/ciocfg/api
load_all CPLBUG /opt/nt62
Open ICC and verify that all compounds and blocks were loaded.
saveh50
When the saveh50 is saved to the hard drive instead of floppy or tape, a directory /opt/fox/hstorian/bin/hist01.exp is
created and can be compressed and saved to tape.
To Check saveh50 for errors:
cat saveh50.log | grep i error
Device Equivalent
SCSI Length
Model 50 processor
0.5 meters
0.71 meters
1.6 meters
1.6 meters
Size A peripheral
1.6 meters
0.16 meters
Size B peripheral
0.8 meters
0.16 meters
Size D peripheral
0.8 meters
0.4 meters
1.2 meters
0.8 meters
1.5 meters
0.56 meters
1.3 meters
0.6 meters
0.6 meters
0.8 meters
1.3 meters
1.2 meters
0.8 meters
1.5 meters
1.5 meters
0.8 meters
(where COMPOUND1 is the name of the sequence compound name) You can use vi to edit this file or it can be
edited offline. When you want to get a good printout of sequence code to work with, you can print one with line
numbers using the following command:
pr I60 n3 f filename.s | lp dLPXX
The pr command will give you line numbers that are the same as the ones you get when you edit the sequence
code in the ICC. If you want a listing of compiled sequence code where line numbers on your printout match the
ones in the select screen use the following:
strings filename.r | lp dLPXX
Usage:
sendmsg(Script Or Command) to msggrx
where script or command is to be executed on the AP hosting the CP hosting the sequence block and xc is number
of a standard message group. The logical device listed in the compound parameter of the destination standard
message group should be VSHELL which is the name of an unsupported Foxboro utility that is run from
mastercron.
setacl Command
dmcmd setacl 20 + + - + - - This display manager command says to give me access level 20, 21, not 22, give 23, not 24, 25, or 26.
Add the following command below it for the Alarm Manager.
dmcmd run /usr/local/pref -$GCLBUG amcmd
setacl 20 + + - + - - -
If other AMs are being used, you will need to send commands to them. (i.e. AM0001 in place of $GCLBUG)
Shell On 50 Series
C Shell AP50/Wyse default
/bin/sh
show_params
Used to display the current usage levels of each of the configurable operating system parameters. (Currently
configured maximum value, Quantity of that parameter free/available, and Quantity in use).
/usr/local/show_params
showrev
with a Displays all revision information for the current system.
showrev a
with p Displays all revision information on all patches applied to the current system.
showrev p
Shrink Command
For a detailed description of the SHRINK command, go to the section titled Utilities: Upload, Shrink, Checkpoint,
Save_all.
/etc/shutdown
continue? Y
will put you in single user (Maint) mode
To restart an AP:
telinit 2
NO CONDITIONING
PULSE RATE
10
20
TYPE B THERMOCOUPLE
21
TYPE E THERMOCOUPLE
22
23
TYPE J THERMOCOUPLE
24
TYPE K THERMOCOUPLE
25
TYPE N THERMOCOUPLE
26
TYPE R THERMOCOUPLE
27
TYPE S THERMOCOUPLE
28
TYPE T THERMOCOUPLE
40
COPPER RTD
41
NICKEL RTD
42
43
44
PARAMETER: SCO
ANALOG OUTPUT SIGNAL CONDITIONING:
1
sipc
This utility transfers control to a command environment in which you can view the IPC software database in the 50
series station or AP20/PW where sipc is executing. Access sipc from the shell level and from the /opt/fox/bin/tools
(50 series) or /usr/fox/bin/tools (20 series/PW).
cd /opt/fox/bin/tools
sipc
Example:
If one of the om_server entries in the dt (data transfer) table has a cmxid of 043A, then messages being sent to this
om_server connection can be identified in foxwatch messages with the first two protocol id fields having a value of
4 and 58.
dt scan_task
CP30 max= 30
CP40 max= 30
dt om_server
sldb
File that is built during the software install. File is in /usr/fox/sp directory and can be used to find a letterbug,
determine a stations host AP, and determine which System Monitor monitors a station.
more /usr/fox/sp/sldb
or
grep <STATION_LBUG> /usr/fox/sp/sldb
snapshot
The snapshot command is a procedure for saving graphics from Fox I/A Sun workstations (AW/WP51s) to
Windows compatible format such as .jpg or .gif. From VT100, type:
cd /usr/openwin/bin
snapshot
This will start the snapshot application in an X-window on your screen. To capture or snap a window on the
screen click on Snap Type: Window. If the snapshot window overlaps the window that you want to capture, click a
checkmark by the : Hide Window During Capoture box. Then click the snap button on the window. It will print a
prompt at the bottom of the snapshot window that says: SELECT Select Window, ADJUST or MENU Cancel. At
this time, left click on the window you want to capture. If you have Hide Window checkmarked the window will
disappear and you will hear beeping until the capture is complete. Shortly after the capture is complete the
snapshot application window will re-appear on the screen and you can pick the View button to start Imagetool and
vi ew what you have captured. The graphic will be displayed. If the area comes in all Black you need to
simultaneously hold down the Control and Again keys found on the keyboard to make the graphic display correctly.
You are then ready to save the graphic to the desired format by clicking the File button on the Imagetool window,
and then selecting Save_As from the pulldown menu. From here you can select the location to save the file and the
file type. It is good practice to put a .gif after the name if you are saving in GIF format, a .tif if saving as TIFF, etc.
This will identify the file type correctly when you FTP the file from the AW or WP to your PC.
CAUTION: The default selection will be Sun Raster and to select any other format you must first click on Sun
Raster and then click on the format you desire. If you dont follow this procedure Sun Raster will continue to stay
selected.
snoop
The snoop will capture network packets and displays their contents.
Usage:
snoop [-d device][-c maxcount][-i filename][-o filename]
som/rsom
som is a Foxboro utility that can be used to monitor the utilization of the I/A Object Manager subsystem. Use som to
view the object manager functions on a station.
Usage:
/usr/fox/bin/tools/som
Note: Use rsom h to get help. Use cp10 for Modicon, comm10 and comm15.
Type rsom -u to be able to enter the target station on which you want to view the OM lists. The station does not
have to be hosted by the AP.
The opdb command displays the remote stations in which the selected station is the source of data and the number
of points requested. (m opdb = more opdb)
The command opvr is used to display the points contained in an opdb entry.
The command conn and sconn while using som allows you to examine IPC connections. The conn command
displays the number of SINK connections.
Other commands used are as follows:
ADR Disp OM AddrTable
CONN Disp OM Conn.Table
DBID open id Disp opn pts db hdr
ID open id Disp omopen tbl hdr
IMP Disp import table
LIST Disp object dir
NADR open id Disp ID's netadrtbl
OBJ object name Disp obj val rec
OPDB Disp opn pts db
OPNL Disp omopen tbl
OPVR open id Disp opdb open vars
PQTBL Disp OM Process Queue Table
SCAN <start row> Disp scanner db
SCONN Disp OM Scanner Conn.Table
Execute som/rsom from the command prompt using the following syntax:
rsom i [input file] t[trace/output file] > /dev/null
or
rsom icp1_info tcp1_out > /dev/null
(This should put some new text on the screen, with an interface that asks you to enter the station
(for an FCP270 or a ZCP270.
(where CPLBUG is the letterbug of the Control Processor you wish to check at this time.)
8. The old text will now be replaced, and you will see a prompt towards the bottom left that says: Command ?"
This is the field you will use to enter the following commands.
9. OPDB
(You will see a listing of Object Manager (OM) lists that are currently open. You may see
multiple lists for the same PID. Do not be alarmed by this, because one application can open multiple
lists. Some examples of what may have opened OM lists in a CP include other CPs, FoxView, InFusion
View, an AIM Historian collector, and an InFusion/Wonderware collector, just to name a few. Compare
the PID to the PID you see in Task Manager to figure out what opened the OM list in the CP.)
10. M OPDB
(You may have more open OM lists than what appears after running the OPDB command.
Use the "M OPDB" command multiple times, if necessary, to cycle through all the open OM lists.)
11. If you care to see the actual points that exist in an OM list, you can use the following commands. This will
show you the health status of five OM points (aka objects) at a time.
12. OPVR ##
(where ## is the ID # of the OM list. Keep in mind that although there are only two digits, if
you exceed 100 open OM lists then you will need to type in a 1 in the hundredth digit to denote that it is
not ##, but rather 1##.)
13. M OPVR
(after you have typed in M OPVR once you can simply press the Enter key to continue
doing more M OPVR commands. From an OPVR list you can do an OPDB command to go back to the
list of open OM lists.)
14. Q (to quit when you are finished.)
15. Bottom of Form
sort
Usage:
sort [-cmu][-ooutput][-T directory][-ykmem][-dfiMnr][-btx][+pos1[-pos2]][fname]
-c
-m
-u
unique
-o
-T
-ykmem
-d
dictionary order
-f
-i
-M
compare as months
-n
-r
-b
-tx
Example:
sort +1 -2 input-file
(Sort contents of input-file with the second field as the sort key)
sort -r -o output-file +1.0 -1.2 input-file1 input-file2
(Sort in reverse order, contents of input-file1 and niput-file2, placing output in output-file and use first char. Of
second field as sort key.
spell command
Syntax:
spell [-bilvx] [file]
The spell command collects words from named files and looks them up in a spelling list. For more information, type:
man spell
mkdir mydir
cd mydir
tar xvf /dev/xxx
where xxx = fd0 for 50 series and xxx = fh0 for 20 series
/usr/fox/swi/tui_xfr cxxx sdiskid
where xxx = fd0 for 50 series and xxx = fh0 for 20 series and where diskid = 5 digit number prompted by Install_SW
Make sure you are in /tmp/mydir when performing the tui_xfr portion.
Station Blocks
LODSW makes display update when LODSW=white
Total CP average plus Cont. Block averages plus I/O load = Total CP Loading.
Overruns will be updated but not at the specified time.
170k of memory in CP10 - need to keep 30% free.
360k of memory in CP30 - need to keep 30% free.
There are 16 maximum peer to peer connections.
1/2 sec. BPCs are shown in station block (amount loading per 1/2 sec. BPC)
LODSW - ON Enables dynamic load processing and display Updates of
BPC sample frames
LODSYN-ON Enables sampling on a schedule basic specified by looper
starting at phase # specified by
LODPHS OFF Done on continuous basic with default looper
LODPER- Specifies freq. at which station block samples loading
for ten consecutive BPC frames DEFAULT:10*BPC
RANGE:(5sec to 1 hour)
LODPHS Specifies starting phase
sum
This command calculates and prints a 16-bit checksum for the named file, and also prints the number of 512 byte
blocks in the file.
Use on AP20:
/bin/sum <filename>
Use on AP50/51:
sum </full/path/filename>
swap
swap -s
swi_pars.cfg file
The file /usr/fox/exten/config/swi_pars.cfg gives information such as PSAP, STA_LBUG, LOG MAC ADDRESS,
etc.
Configure the AW or WP ethernet port that you have used above, with an IP address that will allow it to talk to the
switch. If the switch IP address is the default address, then set the AW or WP address:
AW/WP port address 10.1.0.2
AW/WP subnet mask 255.255.0.0
Start --> Settings --> Network Connections -> double click on your network connection
Properties --> TCP/IP (select in blue) -- > Properties
Select OK to get out of all the selections.
(Note that you will have to re-set the 70 Series IP subnet mask to 255.255.0.0 after each committed
software installation.)
Start --> Run (insert the command cmd ) which will open a cmd prompt window.
ping 10.1.0.1
This should get a response that the switch is alive. If you do not get the "alive" response then the switch has
another IP address. If the switch has the Foxboro recommended address, you can try an Invensys address in the
AW/WP (eg. 151.128.79.12) but if this address does not connect to the switch, then you need to use the serial port
on the switch.
If the above "ping" was successful, then telnet to the switch
telnet 10.1.0.1
When the switch first receives power, it will not communicate to connected devices for about 1 minute, 30 seconds.
Wait this amount of time before expecting an "alive" response from your ping command.
Serial Communication Setup
Obtain the serial communications cable (9 pin female both ends) that is shipped with the switch and connect to the
back of the switch and the 70 Series COM2.
Serial Port Settings:
A) 8 data bits
B) 1 stop bit
C) No parity
D) 19,200 baud rate
E) No flow control
At the 70 Series station, select:
Start --> Programs --> Accessories --> Communications --> Hyperterminal
Ignore any assistance from Windows.
At the window, select File --> New Connection (Cancel location items)
Name the connection "Switch" and select COM2 for the connection.
Select the Properties as specified above and pick OK. In the terminal window, hit the ENTER key. The switch
should prompt you for the User Name (admin) and Password.
Configure the switch parameters as specified above in Telnet and Serial Configuration.
G) Emulation = VT100
H) ASCII setup = force 7 bit
AW and WP Connection
Once the switch has the correct IP address and WP's or AW's are connected to it, you may use the Foxboro station
to configure or change the switch settings.
51 Series
Go to the xterm window and telnet to the switch using its IP address.
telnet <IP address>
70 Series
Start --> Run (insert the command cmd) which will open a cmd prompt window.
telnet <IP address>
If both switches are active and the RCNI is in place, the telnet session will experience delays as the RCNI switches
to the other cable. Foxboro has a new 24 port fiber-optic switch (P0972YC), which replaces the P0972MJ).
Attach a PC or workstation with emulation software to the switch console port. This is with the 9 pin serial cable
provided. The default data characteristics of the console port are 9600, 8, 1, no parity. You might need to press the
Return key several times to see the command-line prompt.
Configuring the Switch
This configuration is bare bones with none of bells and whistles that this switch is capable of. Most customers will
have a Cisco representative configure their switches and this is just a configuration to get IA back running.
Switch> enable (This enters the switch)
Switch# (This is the switch prompt)
Switch# configure terminal (This enters configuration mode)
Switch(config)# interface range fastethernet0/1 24 (Configures all ports)
Switch(config-if)# duplex full
Switch(config-if)# speed 100
Switch(config-if)# end (This has set up all ports to full duplex)
Always configure the vlan1 on all switches, must be same vlan to talk together.
Switch(config)# interface vlan1 (Setting up switch IP address)
Switch(config-if)# ip address 151.128.80.100 255.255.0.0 (ip address and masking)
Switch(config-if)# no shut
Switch(configif)# end (This setup ip address, masking and switch stays alive)
Switch(config)# end
Switch# show interfaces fastethernet0/3 (Shows port 3 setup)
Interface FastEthernet0/3
Switchport mode dynamic desirable
Duplex full
Switch# show running config (Shows all of the changed parameters)
Switch# copy running-config start-config (Loads configuration for startup)
Switch# end
Each switch needs to have a unique identifier from the range 151.128.79.1 thru 151.128.80.192
Switch Power Up
When the switch first receives power, it will not communicate to connected devices for about 1 minute.
AW and WP Connection
Once the switch has the correct IP address and WP's or AW's are connected to it the switch will communicate
across node.
Switch> enable
Switch# show ip int brief
Interface IP-Address OK? Method Status
Protocol
Vlan1 151.128.80.100 YES NVRAM up up
FastEthernet0/1 unassigned YES unset up up
FastEthernet0/2 unassigned YES unset up up
FastEthernet0/3 unassigned YES unset up down
FastEthernet0/4 unassigned YES unset up down
FastEthernet0/5 unassigned YES unset up down
FastEthernet0/6 unassigned YES unset up down
FastEthernet0/7 unassigned YES unset up down
FastEthernet0/8 unassigned YES unset up down
FastEthernet0/9 unassigned YES unset up down
FastEthernet0/10 unassigned YES unset up down
FastEthernet0/11 unassigned YES unset up down
FastEthernet0/12 unassigned YES unset up down
FastEthernet0/13 unassigned YES unset up down
FastEthernet0/14 unassigned YES unset up down
FastEthernet0/15 unassigned YES unset up down
FastEthernet0/16 unassigned YES unset up down
FastEthernet0/17 unassigned YES unset up down
FastEthernet0/18 unassigned YES unset up down
FastEthernet0/19 unassigned YES unset up down
FastEthernet0/20 unassigned YES unset up down
FastEthernet0/21 unassigned YES unset up down
FastEthernet0/22 unassigned YES unset up down
FastEthernet0/23 unassigned YES unset up down
FastEthernet0/24 unassigned YES unset up down
Switch# end
Switch>
IA INFO: trd0301
File: Ethernet Switch
Release: V7.0
Date: Mar. 11, 2003
Subject: Configuring 100 MHz Switches for IA
Source: Testing
General
The 8-port managed switch is connected into the IA system per B0400DV but before it will communicate to an
Invensys computer (AW or WP), the switch must be configured. If the switch current address is known (default from
manufacturer is 10.1.0.1) then the AW or WP ethernet port can be used to configure the switch. If the address is
not known, then the switch must be programmed via its serial port. See the manufacturer's Management Guide.
Identification
Invensys Part Number: P0972MF
Enterasys Part Number: VH-8TX1MF
Enterasys WEB site: http://www.enterasys.com/support/mibs
After configuration, you should mark each switch with its IP address and the letter A or B, as applicable, to aid in
trouble shooting the network.
Wiring for Configuration
Connect one of the AW or WP's ethernet ports directly into the switch (any port) with one of the copper cables. Do
not use the RCNI or the media converter. Once configuration is complete, re-connect per
B0400DV.
telnet 10.1.0.1
Telnet and Serial Configuration
Default User = admin
Password = none (Just hit Enter)
(Note that you should give the switch a password. If none is assigned, you should use the default Invensys
password.)
Use the arrow keys to select "Device Control Menu"
Use the arrow keys to select "Port Configuration"
Ensure that each port is set for:
Duplex Mode = Autonegotiate
Flow Control = Disable
Use the arrow keys to select "Management Setup Menu"
Use the arrow keys to select "Console Login Configuration" set the password for all users
Use the arrow keys to select "Network Configuration"
Use the arrow keys to select "IP Configuration"
Enter your switch IP (for example, 151.128.79.1 for the first switch)
Subnet Mask 255.255.0.0
Select OK and back out.
If you use telnet, the switch will immediately lose communication since it has a network IP that is different from your
network IP. Reconnect the switch per B0400DV and ping the switch. The switch must give the
"alive" response. Ensure the IA port subnet mask is set to 255.255.0.0. The RCNI will determine whether Cable A
or Cable B is talking.
Note that the switch for Cable A must have a different IP address from the Cable B switch.
Switch Power Up
When the switch first receives power, it will not communicate to connected devices for about 1 minute, 30 seconds.
Wait this amount of time before expecting an "alive" response from your ping command.
Serial Communication Setup Obtain the serial communications cable (9 pin female both ends) that is
shipped with the switch and connect to the back of the switch and the 70 Series COM2.
Serial Port Settings:
A) 8 data bits
B) 1 stop bit
C) No parity
D) 19,200 baud rate
E) No flow control
At the 70 Series station, select:
Start --> Programs --> Accessories --> Communications --> Hyperterminal
You must kill remd when finished or you will not be able to start system management.
To reset the fieldbus counters and generate a report:
cd /opt/fox/bin/remote
diag_cpload51 > /opt/tmp/file1
7. To verify that smon_log is capturing the system messages, perform a checkpoint CP Database. This can be
done from SMDH or ICC.
8. Do more on the /opt/fox/sysmgm/sysmon/smon_log file.
cd /opt/fox/sysmgm
more smon_log
Check this file to see that it is actually configured as a System Monitor WP. If it is not, you may have your field
service representative to bpatch the file by making a copy of the original first to make the necessary change adding
the AW/WP as a SMGC station. The final step is to stop and restart the system monitor.
tail command
Syntax:
tail [+n | -n] <file>
mt f /dev/rst9 status
copy diskette:
tar cvf a:
extract:
tar xvf a:
telnet - 50 series
telnet communicates with another host using the TELNET protocol. If telnet is invoked without arguments, it enters
command mode, indicated by its prompt telnet>. In this mode, it accepts and executes its associated commands. If
it is invoked with arguments, it performs an open command with those arguments.
Type man telnet more more detailed instructions.
Example: To run a VT100 type session on an AW51 thats on my network, (connected through the
AWs second ethernet port) whose name is MYAW01, type:
telnet MYAW01
login: root
password: password
touch Command
Usage:
touch [-amc][mmddhhmm[yy]] filename
This will create a file named filename.new and set the timestamp for the current date and time.
find / -newer jmm.new -print
This command line will find all files that have been updated since that time.
FBK:
TANK1:FIC100.OUT
INITI:
TANK1:FCV100.INITO
BCALCI:
TANK1:FCV100.BCALCO
TANK1:FCV100(AOUT)
PRIBLK:
1. If the status leds show the FCM in normal (see table below) but the CP60 is indicating a problem or will
not communicate with the FCM check the TX Ethernet status led.
The TX led will blink if there is any activity at all on the Ethernet connection.
If the TX led is out check the cabling between the CP60 and the FCM Check the ECB for the FCM
If cabling, ECB are good and the CP60 is communicating with other FCMs, replace the FCM
Otherwise check the CP60
2. If the Ethernet TX led is blinking check the Ethernet RX led.
The Ethernet RX led will blink when the FCM receives comms from the CP60 addressed to it.
If the Ethernet RX led doesn't blink check the letterbug on the baseplate and verify it matches the ID in
the ECB.
FCM to FBM Communication Problems
Status
==================================================
Green / Off
Normal
Green / Red
Off
/ Red
Copper FCM
00 00 6C 11 xx xx
00 00 6C 12 xx xx
FBI, DCM
00 00 6C 13 xx xx
Note: xx xx will be a unique factory burned in value. When the CP60 first communicates with an FCM it uses the
letterbug. Once the FCM responds to the CP60 the CP60 will use the MAC address of the FCM for all following
communications. If there are two FCMs with the same MAC address they will become confused and try to send
messages to FBMs, which don't belong to them. See Sec 1.2.3.4 B0400CC V6.3 Readme
PIO Bus Operations
The CP60 will select the bus (A or B) with the most FBMs. The CP60 will issue an Open Request to all the FBMs and
then a Status Request. This will be done for both busses and the bus with the most FBMs is the bus that is selected.
If both busses have the same amount of FBMs then bus A is the default. Once a bus is selected for operation the
other bus must exceed the original bus for a bus switch to take place.
The CP60 will send out a Broadcast (Bcast) message every or 1 second. The Bcast message is for compatibility
with legacy FBMs. A legacy FBM will switch busses if it doesn't hear a heartbeat. The 200 series FBMs listen to both
busses at the same time so there is no bus switching and the heartbeat doesn't apply.
The CP60 will package up all the messages for FBMs under a given FCM based on the size of the FBM responses.
Normally one message is sent to the FCM for all the FBMs. If the size of the response message from the FCM
exceeds 1400 bytes then more messages will be generated. The FCM will take the request messages from the
CP60 and send out individual messages to the FBMs. The FCM will wait for the FBM response and package them
up into a single message that will be sent back to the CP60.
MPOLL does not apply for 200 series FBMs
Note: Placing an FCM into Offline doesn't really place it into Offline. The CP60 will continue to talk to the FCM. The
only current way to stop communications to an FCM without failing it is disable switching to the cable an FCM is on.
Communications Problems
1. If an FBM is slow to answer or fails to answer the FCM will send a Timeout to the CP60.
2. If a response from an FCM to the CP is garbled or there is a CRC error the CP may restart the I/O
processor.
3. A garbled response or CRC error received by the FCM will not be answered.
4. Noise bursts can make FBMs appear as though they are not there.
1.1 msec
Legacy FBM
2.0 msec
Migration FBM
3.0 msec
DCI
5.04 msec
Troubleshooting scripts
One way to troubleshoot a script file to see what its actually doing:
sh x scriptname
This will show you the commands being executed and results of these processes.
Verify that leds on the NCNIs are operating properly. There should be a link led on for each cable connection on the
NCNI, CAT-5, Fiber or both. When there is activity on a cable the led will blink. The Nodebus led will blink when
there is a transmission to the nodebus from the NCNI.
Verify that switches which have connections have the led on for receive. The receive led being on indicates link.
There should be activity on the receive led when a packet comes from the switch to the station. The Transmit (TX)
led will blink when the station sends a packet to the switch. Flashing red on the transmit usually indicates a transmit
problem such as a collision. Check the switch port settings for full duplex and auto-negotiation.
Symptom: Network Slowdown
Check for crossed cables between the "A" and "B" paths in the V7.x network. A crossed cable can also be
produced by setting the NCNI switch to the wrong position i.e. connecting the NCNI to a switch for cable "A" but
setting the Nodebus Selection switch to "B", onnecting the cables from the RCNI to the wrong switch or making a
connection between a switch on the "A" cable to a switch on the "B" cable.
Check for bad or missing connections on the station that is the current Nodebus Test Initiator. A bad fiber link
between a RCNI and a switch on the station that is the current NFD Initiator can cause a slowdown if stations think
there is a problem with the cable that doesn't have a bad link. Note: This type of fault would have to be a fault that
does not cause a link loss but does create bad or intermittent communications on the cable with the bad link.
Verify that the station is configured for redundant communications (nodebus) and not ethernet. Check the
CMX_STAND_ALONE parameter in the /usr/fox/exten/config/loadable.cfg file. For redundant busses (Nodebus)
you should see the following values. Solaris Stations CMX_STAND_ALONE = 0 NT and XP
CMX_STAND_ALONE=DNBI_PRESENT If these values are not correct then a reconfiguration and re-committal
will be necessary to properly configure the station.
TCP/IP Communications Work But Not I/A Communications (Comex)
Check that the splitter cable is connected to serial port "A". IP doesn't need a certain cable to work but I/A won't
work properly if it can't switch cables and switch the "A" & "B" receivers on/off. If the Splitter Cable is properly
connected replace it. Verify that the Ethernet cable connected between the Splitter cable and the RCNI is Rev C or
higher for P0971XK, XL, XM and XN. Refer to SI 0-00528 for kits AG100WD, WE, WF & WG.
On XP stations verify that the Foxboro Protocol is only enabled for the NIC port connected to the RCNI. The
Foxboro Protocol should not be enabled (checked) on the Mother Board port but only on the NIC used for I/A which
is usually Local Area Connection 2.
I/A Communications Work But Not TCP/IP
Check that the proper subnet mask is set. Sun stations default to 255.255.0.0 NT stations 255.255.254.0 and XP
255.255.228.0. It is best to set them all to 255.255.0.0. Also verify that the Network portion of the I/A port is
151.128. Note a ping can work even if the netmask is not properly configured.
Verify that the Ethernet cable connected between the Splitter cable and the RCNI is Rev C or higher for P0971XK,
XL, XM and XN. Refer to SI 0-00528 for kits AG100WD, WE, WF & WG.
If the IP communications is going across a LAN to another node verify that the IP addresses for the destination
and source stations are in the correct IP range for the NSAP of each node. Check the CSC Web page under
Resources -> Troubleshooting Guides -> Tokenbus/Nodebus for a table of NSAP to IP ranges.
Intermittent Cable Failures Reported by NFD
NFD thrashing between V6.x stations and V7.x stations has the potential to create cable problems. On V7.x nodes
verify that NFD has been disabled on all V6.x stations. The one exception is the LAN, which can't be disabled at
V7.0 & V7.1. A workaround is to manually select a V7.x station to be the NFD Test Initiator even if a V7.x is already
the Initiator. On V7.x hosts running NFD the utility nfd_debug can be used to determine if there is NFD contention
occurring between multiple NFD Initiators. See below for more information on nfd_debug. To set a station as the
NFD Test Initiator go to NETWORK in System Management pick NEXT LEVEL, if there are LANs pick the LAN for
the Node which hosts the station which is to be the Test Initiator, pick NEXT LEVEL and select the station which is
to be the Nodebus Test Initiator, select ONLINE DIAG and when the window opens select CHANGE NODEBUS
TEST INITIATOR. When the operation is complete use the CURRENT NODEBUS TEST INITIATOR pick to verify.
When a Non Unique Letterbug messages shows up in the smon_log this is usually caused by by a Network loop in
the system which allows cross communications between the "A" and "B" cables. Check for crossed cables or a
defective NCNI, RCNI. Check for crossed cables on segments other than the segment on which station reporting
the Non Unique Letterbug that won't boot is located.
Duplicate Mac Address Messages
If a station reports on Duplicate Mac Address when booting up, check for port mirroring being enabled on the switch
to which the station is attached. When the station broadcasts it's Mac Address if port mirroring is enabled on the
switch it may cause the station to hear it's own broadcast making it appear that someone else owns that Mac
Address.
Both Cables Fail or Wrong Cable Fails NFD Test After Breaking One Cable There are several items that can cause
NFD to fail a test. Verify the items in the Basic Network Checks listed above. Usually an incorrect cable diagnosis is
caused by crossed cables or a problem with the serial cable on a station(s), preventing the station from switching
cables. Check the station that is the NFD Initiator. Try changing the NFD Initiator, running cable test and see if the
same results occur. Workstation Won't Read Letterbug. Verify that the proper letterbug is installed correctly in the
RCNI. The letterbug must be installed before powering up the RCNI in order for it to be read by the RCNI. Verify
that the status leds on the RCNI are with one off and the other on (green), on the upper right corner of the RCNI.
Verify splitter cable is connected to serial port "A" on the workstation. Verify that splitter and Ethernet cables are
connected and working. Verify that the serial connection on the splitter cable is connected to serial port A or Comm
1.
Workstation Won't Communicate Through RCNI to Other Stations.
nfd_log
Enable nfd_log on all potential V7.x NFD Test Initiators. The nfd_log will only record information on the station of
the current NFD Test Initiator. To enable nfd_log create the directory /opt/fox/sysmgm/nfd and then create the file
nfd_log. You will want to monitor the file because it will grow indefinitely. The nfd_log shows what stations are
requesting cable test and if stations are reporting Carrier Sense Errors (CRS).
nfd_debug
Enable nfd_debug for information on the current NFD Test Initiator is. This file will log information on all stations on
which it exists. You want to monitor the size of this file because it will grow indefinitely and at a fairly high rate. This
log is helpful to show how many stations each potential Initiator thinks are on the node and also who is the current
Initiator. To enable nfd_debug create the directory /opt/fox/sysmgm/nfd and create the file nfd_debug. A station that
is the NFD Initiator will report messages like the following in nfd_debug
2004-06-18 09:26:33 ev_timeout: my_state: MASTER, Not Refreshing --- num_stas: 18
my_state: Master (says this station is the Master)
num_stas: 18 (Says NFD on this stations sees 18 stations on the node)
A station that is not the NFD Initiator will have a messages like the following in nfd_debug
2004-06-18 09:31:09 ev_timeout: my_state: Not Master, Not Refreshing - -- num_stas: 20
(Message indicates this station is not the NFD Initiator "Not Master")
2004-06-18 09:31:16 Heartbeat Rcvd: Master: AW51F1, Override: 1,
Mast_type: 7d -- my_state: Not Master
(Message indicates that a NFD Initiator heartbeat another station "AW51F1")
2004-06-18 09:31:16 2. I_OVERRIDE: No Action
(Message indicates that no attempt has been made by this station to become the NFD Initiator by overriding)
smon_log
Enable the smon_log on all System Monitor hosts. This log along with nfd_log can help debug cable problems. You
will want to monitor the file because it will grow indefinitely. To enable smon_log create the directory
/opt/fox/sysmgm/sysmon and create the file smon_log.
Tuning
Proportional band or gain (P) Output is proportional to error. Farther away from SP, the more action youre gonna
get (Slow(100) > Fast(0.1))
Integral Time, reset time, or reset rate (I) Output repeats proportional change over time. Integrates area under error
curve. Looks at how long youve been away from SP. You dont have enough integral if it really never reaches the
setpoint. (Slow(100) > Fast(0.1))
Derivative Time or rate (D) Output repeats based on slope of error curve. Time is how long derivative action lasts.
Looks to see if youre making progress and tries to catch the measurement before it starts swinging back and forth.
(Slow(0) > Fast(5))
Turn the integral time to its highest setting (set to 10 minutes per repeat)
If used, turn the derivative time (rate time) to zero or its minimum
Decrease the proportional band until the loop maintains a small sustained cycle.
Then set the controller adjustments to:
Kc=Kcu/2 where Kc=100/Proportional Band
Pc=2Pcu where Kcu=ultimate gain, same units.
Ti=Pn where Ti=Integral time, minutes per repeat
Td=Pn/8 where Td=Derivative time, minutes
Turn off integral and derivative, set both to 0. Start with P-Band at 100 then just watch to see what happens to it. If it
starts to drift, keep changing P-Band until you get a slow kind of curve not a zigzag curve. Figure the natural period
in minutes. If Pband comes to 65 then set Pband to 130. The natural period in minutes = Integral if natural time = 30
seconds then Integral = .5. Derivative = natural period divided by 8 or .0625.
uname Command
uname [-amnprsv]
-a
-m
-n
print nodename
-p
-r
-s
-v
2. In the "old" CP30 or CP40, perform an UPLOAD and SAVEALL to save the existing control block data.
3. INITIALIZE the "old" CP and remove the CP from the cell buss.
4. Replace the Field Bus Isolator with the FBI10E. Wire up the ethernet fieldbus per the installation instructions.
The leds on the FBI10E should go RED /GREEN, then GREEN only. There may be a brief flicker on the WHITE
leds. There should be no further fieldbus activity.
5. Call the CP60 in the Integrated Control Configurator (ICC). Insert the "old" SAVEALL diskette and select SHOW
and Diskette Directory.
6. Select Load from Diskette and in the field "Current Name:" select the "old" letterbug_ECB <Enter> then in the
"New Name:" type in your CP60 letterbug_ECB <Enter> then DONE. This will load the "old" ECB's into your CP60.
You will be asked to confirm that you wish to modify the ECB's; select - Yes.
7. Select LOADALL. This will load in the remaining blocks and will notify you that it failed to load the Station
Compound and the ECB Compound.
8. Go to the ECB compound and add a new block before the "old" ECB's Name = DevID = letterbug of your
FBI10E. Type = ECB110 HW = 200 SW = 200
9. Go to System Management and select the FBI10E to go ON LINE (both) You should now see the WHITE leds
flashing on the FBI10E. Go to the SMDH Next level and you should see your old FBM's. Select DOWNLOAD for
each FBM.
10. Verify that your eeprom levels are correct for each FBM
11. Perform a SAVEALL with Format for your new CP60.
Upgrade Utilities
The Upgrade Utilities document should be read in its entirety before running these scripts. Below are just brief
descriptions and are to be used as a reference only. These notes are subject to change so its important to read the
actual manuals. Before performing a day0 upgrade, the latest upgrade scripts should be downloaded.
Tar off the install_upg utility into /tmp and run this program. This program will generate a sort of Upgrade Plan
which is to be used as a reference when actually writing your own upgrade plan. There are several reports that are
generated from this utility. All of the information contained in these reports is very useful. The install_upg utility will
then run another script called upg_util. The upg_util is an interface program which runs a series of scripts to
inventory all files and directories as well as the checksums of all Foxboro Standard System and display related
files. This utility in effect will give you three files that will be 1) a list of all custom directories that do not exist on a
day0 drive, 2) a list of all custom files that do not exist on a day0 drive, and 3) a list of the Foxboro Standard System
and Display related files that have been modified.
Backup-To-Tape and Restore-From-Tape Utilities
Again, it is very important to read the entire documents on these utilities. If the procedures are not followed
precisely, there could be problems.
The backup-to-tape utility generates a list of files to back up to streaming tape. There is a list of files in the
document that this utility automatically puts in this backup list. It also gives the user the opportunity to add
customer-specific files to the list via a text editor or the menu provided by the utility.
The restore-from-tape utility restores the files that backup-to-tape saved to the streaming tape. Upon restoring the
files, you may be informed of files in prior_release directories. The prior_release directories exist so that older files
can be restored onto the drive without overwriting files critical to proper operation or to provide information from the
older drive for reference purposes. The priorrelease directories contain only old files whose contents differ from
the new files of the same name.
These utilities are a must when trying to retrieve all custom information from a customers system to restore to a
day0 drive.
Upload Utility
For a thorough explanation of the UPLOAD utility, go to the section titled Utilities: Upload, Shrink, Checkpoint,
Save_all.
upload <type> <CP Letterbug><compound><block>]workfile.dat [<tempdir>] <CP type>
Example:
upload 4 UCE001 workfile.dat
(or)
/usr/fox/ciocfg/upload 4 UCE003 workfile.dat
<type> 1=upload compound; 2=upload block; 3=upload ECB compound; 4=upload all; 5=upload oper. status
parameters
<CP letterbug> letterbug of CP
<compound> name of compound to upload
<block> name of block to upload
workfile.dat this string is passed as is
<temp dir> name of temp dir. to be used for storage of oper. status database install command files. (argument only
appears when option 5 is chosen)
<CP type> type of CP to upload (201,2001,8001,etc)
Location of work files for CP: /usr/fox/ciocfg/CPLBUG/*.wf
uptime
This command displays the length of time the system has been up since the last reboot.
The following information was supplied by Alex Johnson and is a clarification of the relationships between
upload/shrink/checkpoint/save_all.
UPLOAD The upload operation reads unconnected, settable parameters from the control stations RAM and
stores them in the workfile for the Control Station.
SHRINK The workfile grows without bound as blocks are changed. When the DONE button is pressed, the
altered block is written to the end of the workfile (appended).
CHECKPOINT The contents of the CSs RAM are written to the host machine. This file is used to restore the
RAM after a reboot. Since this is basically a copy of the contents of RAM at the time of the checkpoint, the rebooted
box can start with the previous setpoints and block states. Parameters like INITMA are used to alter its behavior.
SAVE_ALL A directory structure using the native file system of the host is written to the floppy when a SAVE_ALL
is triggered. This directory structure contains a hidden file that holds the names of the compounds on the floppy,
directory for each compound that holds the sequence and ladder logic files for the CS, and a file (parameters) that
contains the parameter values for each parameter of each block.
LOADALL The LOADALL pick causes the ICC to read the floppy created by the SAVE_ALL. Related to this is the
fact that the ICC database is actually in four different places. The CSs RAM holds the working copy. This is the
copy that changes made at a display will alter.
The checkpoint file, which is stored in /usr/fox/sp/files on the boot host of the control station. Its name is
DB<LBUG>.UC. Its backup is BB<LBUG>.UC
The source code files used by the ICC. These are stored in /opt/fox/ciocfg. The directory <LBUG> stores the files
related to the compounds, blocks, and parameters of the objects in the CS. The directory <CMPDNAME> holds the
sequence and ladder logic files for the compounds.
The CSA database contains a list of the compounds and blocks in the system. This list is used by the ICC to
guarantee uniqueness of names.
The source code files consist of two types of files: the .O files and the .wf file. The <LBUG>.O file contains a
record for each compound in the CS. There is one <LBUG>.O file for each station. There is a <CMPDNAME>.O file
for each compound. Each <CMPDNAME>.O file contains the names of the blocks owned by that compound. The
.wf file contains all of the parameter data. The <CMPDNAME>.O records contain a pointer into the .wf file that is
used to locate the parameters of a particular block. Since changes to the block cause new records to be appended
to the file, the .O files must be updated with each change.
The SHRINK action causes the excess information in the .wf file to be squeezed out. Problems arise when these
files get out of synchronization. If the CSs RAM is lost, the checkpoint file is used to recover. (This is a reboot) If a
checkpoint file is lost, the checkpoint operation can recreate it. If the source files are lost, there is no standard
approach to recovery and the ICC cannot be used to recover with the CP running. If CSA is lost, the SAVE_ALL,
INITIALIZE, REBOOT, and LOADALL sequence may be required to recover the database or to resynchronize to a
backup.
VI - Colon Commands
:set all
:set wm=20
:set nu
:set ai
:q!
:n
:x,ymz
:x,ycoz
:x,ywfilename
:x,yw>>filename
:e
:w
:ZZ
:wq!
:%s/oldtext/newtext/g
:g/<pattern1>/s//<pattern2>/g
Substitute <pattern1> with <pattern2> globally
Example search and replace: To edit the file IIF.pkg file searching for the pattern FBM and changing the word
NOTYET to DONE, do the following:
vi IIF.pkg
:g/FBM/s/NOTYET/DONE/g
This searches for a line that has FBM in it and changes the word NOTYET on that line to DONE.
This could have been searching only for WP51s for instance:
Example:
:g/WP51/s/NOTYET/DONE/g
Example to remove unwanted hard carriage returns (^M) at the end of each line of a file. The following command
will globally replace the last character of each line (the carriage-return) with nothing (i.e. delete it). The hard
carriage returns are placed at the end of the line in a file saved in DOS/Windows. Thank you Bob VI and awk
Dombrowski. (Also see Copy - unix2dos and dos2unix (50 series) for a different method).
:g/.$/s///
replaces letter
cw
cc
dw
delete a word
dd
delete a line
3x
delete 3 characters
3dw
delete 3 words
3dd
delete 3 lines
yw/yy
y1y
repeat commands
1p
retrieves deleted text - move to space deleted text should begin and enter 1p, (.) will
repeat retrieval command
/text
searches forward
?text
searches backwards
n,N
to end of word
up one line
to beginning of line
to end of line
:set number
nG
to end of file
1G
to beginning of file
to go to top of screen
to go to middle of screen
to go to bottom of screen
Ctrl-Y
Ctrl-E
Ctrl-B
Ctrl-F
Ctrl-L
refreshes screen
Ctrl-D
Ctrl-U
VI - Opening A File
at the end of the file = vi + filename
at specific word = vi +/word filename
at specific line = vi +n filename
vmstat
For use on 50 series systems, vmstat will display certain system statistics regarding process, virtual memory, disk,
trap and CPU activity.
vmstat 5 10
(will run vmstat updating every 5 seconds displaying the first 10 lines)
For use on 50 series systems, the vmstat command will display certain system statistics regarding process, virtual
memory, disk, trap and CPU activity Note: vmstat statistics are only supported for certain devices. Without options,
vmstat displays a one-line summary of the virtual memory activity since the system was last booted. If an interval is
specified vmstat summarizes activity over the last interval in seconds, repeating forever.
Note: In the example below vmstat will update every five seconds; vmstat terminates by entering <ctrl>c Because
vmstat consumes system resources be careful about leaving vmstate running for extended periods.
Use:
vmstat 5
OPTIONS
-c Report cache flushing statistics. By default, report the total number of each kind of cache flushed since boot time.
The types are: user, context, region, segment, page, and partial-page.
/.logout
wc Command
Syntax:
wc [-cwl] <file-list>
who
The who command examines the /var/adm utmp file to obtain information of everyone logged in. /var/adm/wtmp
contains a history of all the logins since the file was created.
who -a
who am I
who -u
who -b
(who -b will show the last boot date for the system)
(who -a and who -b are not available on the 50 series systems).
/usr/fox/ciocfg/CPLBUG/*.wf
50 series:
/opt/fox/ciocfg/CPLBUG/*.wf
/
/etc Directory, 91
4
4mm tape, 81, 210
A
AApan, 10, 13
AAtab, 10, 13
Access Levels, 3
Access Levels Using the setacl Command, 3
add_periphs, 3, 80
add_periphs (50 series), 3
admintool, 3
AIM, 3, 4, 5, 6, 7, 17, 64, 99, 100, 101, 102, 104, 105, 119, 120,
122, 178, 189, 194
AIM Historian Dumping Message Data to a Text File, 3
AIM Historian Error Message Received About Number of
Entries, 4
AIM Historian Procedure to Increase the Max Number of
Alarms in Alarm History (5,000 to 40,000), 4
AIM Historian Procedure to Increase the Size (5,000 points to
10,000 points), 4
AIM Historian Procedure to Move from one AW to Another, 5
AIM Historian problem with corrupt RTP file, 6
AIM Historian Starting and Stopping, 5
AIM Historian Troubleshooting Tools, 7
AIM*Historian and apitst, 119
AIM*Historian and FH_SACEGO, 120
aimapi, 4, 5, 98, 102
AIMAPI, 4, 5, 98, 99, 100, 101, 102, 103
aimapi.cfg, 4, 5, 98, 102
AIMServer, 101, 105
Alarm History, 4, 7, 99
Alarm History Issue Not purging old messages and not
showing complete list of alarms, 7
Alarm Manager, 7, 9, 77, 188
Alarm Manager Problem with AM Display Getting Stuck on the
Screen, 9
Alarm Manager Quitting Alarm Managers that are not
quittable, 9
Alarm Manager Install Files, 7
Alarm Server Task ast Problem, 9
Alarms, 4, 9, 14
Alarms Common Alarm Group (CAG), 9
alias, 5, 9, 10, 77, 81, 91, 96, 100, 152
alias - Creating a Pseudonym for a Command, 9
am_def.cfg, 107
an_init.cfg, 98, 100, 101, 102, 104, 108
an_init.tcp, 5, 7, 27, 98, 100, 101, 108
Annunciator Configurator, 10
Annunciator Keyboard, 10, 16
Annunciator Keyboard Annunciator Will Not Work While
Direct Connect Printer is Configured, 16
B
Background - Running files in, 22
backspace, 22, 89
backspace function, 22
backup, 19, 22, 23, 24, 25, 26, 27, 28, 29, 80, 90, 97, 100, 124,
136, 149, 162, 163, 172, 177, 221, 222
Backup, 5, 19, 22, 23, 25, 26, 35, 37, 126, 155, 161, 185, 220
backup and restore Procedure, 23
Backup AP - Configuring WPs for AP Switching on 20 series
stations, 22
Backup Using A Remote 50 Series Tape Drive, 26
Backups, 25, 26, 27, 28, 66
Backups - 50/51 Series To Streaming Tape using dmp0 and
dmp9 scripts, 25
Backups - AP20 Streaming Tape, 28
Backups - Checking Save-All Diskettes Integrity, 26
Backups - Checking Tape Stamp On 50 Series, 28
Backups - Level 0 (Complete) Backup, 25
Backups - Level 9 (Incremental) Backup, 26
Backups - Recommended Directories To Back Up, 27
BACKUPS - Saving Multiple Directories/Files to Tape 50 series
stations, 29
Backups Using the dd command with bs and count, 27
Backups AP20 - Copying From Primary Hard Drive, 27
Backups AP20- Checking Streaming Tapes Integrity, 28
Backup-to-tape Utility, 23
blink, 78, 85, 144, 207, 213, 216
boot, 3, 5, 12, 24, 26, 29, 30, 31, 32, 40, 42, 66, 76, 80, 82, 85,
86, 90, 112, 113, 136, 139, 145, 154, 155, 158, 172, 176, 177,
197, 198, 217, 222, 226, 227
Boot, 24, 29, 30, 31, 32, 40, 136, 139, 154
Boot Host Checks Troubleshooting a station (CP, COMM, etc.)
that wont boot, 31
Boot Partitions On PC - Switching, 32
Boot Problems WP51E will not boot after v6.4 day0 install, 30
Boot Procedures, 29
Boot Procedures for Troubleshooting an AW/AP/WP that wont
boot, 29
bpatch, 10, 31, 32, 33, 89, 111, 209, 228
bs, 27, 28, 46, 66
Bypass Module, 33
C
C Program Compiling 20 Series, 34
Cable Pinouts, 34
Cabling, 35
Cabling - Hard Drives, Floppy, Extra Backup Hard Drive, Without
Streaming Tape (AP20), 35
Cabling - Hard Drives, Floppy, Streaming Tape Without Extra
Backup Hard Drive (AP20), 35
CAGinit, 9
cal Command, 35
Cancel Print Job, 36
cat, 8, 22, 26, 29, 36, 44, 116, 140, 160, 161, 185
cat Command, 36
catman, 19, 36, 133, 134
catman Command, 36
cb Command, 36
cfgpts, 36, 37
check_db_sync, 59, 60
checkpoint, 31, 37, 38, 43, 64, 65, 88, 90, 107, 109, 177, 179,
209, 222
Checkpoint, 37, 59, 88, 90, 93, 177, 180, 188, 209, 221, 222
Checkpoint CPs, 37
Checkpoint File Rebuilding Corrupt Checkpoint File(HH953),
37
Checkpoint File Maximum Sizes, 37
Checkpoint Files Location, 37
chgrp, 79, 160
chmod, 38, 39, 89, 176, 177
chmod Command, 38
chown, 79, 160
ckmacadr, 18, 38
cmp, 39
cmp - Compare, 39
cnvt_foxcae, 104
commgrp.cfg, 7, 9, 28, 106
Committal diskette, 10, 12, 113, 160
concatenate, 39, 72
Concatenating, 39, 40
Concatenating Drives (50 series), 39
Concatenating Drives (50 series) Restoring Problems (HH859)
Error commonly seen is SCSI 2 Already in Use, 40
D
d_edit, 66, 67
d_edit - Search and Replace, 67
d_edit Command, 66
Daylight Savings Time, 64
Daylight Savings Time Issues - Setting time back, 64
db_sync, 60
dbvu, 64, 65
dbvu/dbvu30/dbvu40, 64
dbvu_err, 65
dd, 27, 28, 40, 46, 47, 66, 224
dd command, 66
defunct, 66
defunct Processes, 66
Device Monitor, 68, 69, 70, 113, 114
Device Monitor disabling, 70
Device Monitor Master, 68, 69
Device Names, 70
devnm, 72
devnm <filesystem>, 72
df, 72, 74, 94
df command, 72
dft, 39, 40, 41, 72, 73, 137, 138
dft commands, 72
diag_fist, 73
diag_fist50, 73
diag_fist51, 73
diag_syst, 150
diff, 73
diff - file comparison utility, 73
diff3, 74
diff3 3-way file comparison, 74
dircmp, 74
Disk Space Issues, 74
Dispalmcfg, 4
DispAlmCfg, 8
Display Alarm Configurator, 8, 107
Display Manager, 9, 64, 76, 77, 82, 97, 106, 124
Display Manager Install Files, 77
Display Manager Starting Manually, 77
Display Manager or Foxview How to Invoke, 76
Display Managers Quitting Display Managers that are not
quittable, 77
Displays, 108
dm_recon, 69, 163
dmcfg, 8, 28, 77, 82, 106
dmcfg Making Changes Without Having to Reboot, 77
dmcmd, 14, 77, 82, 137, 158, 171, 188
dmesg, 78, 130, 135
dmpasswd_cfg, 106, 154
dmpcfg, 78
dmpnam, 78, 120
dmpstat, 78
dmsepass, 106, 154
DNBI blink codes, 78
domain, 73, 91, 171
DOS Files - Copying Into Venix (20 series), 79
E
ECB, 60, 65, 83, 84, 91, 93, 109, 115, 116, 170, 171, 213, 220,
221
ECB - Equipment Control Blocks, 83
echo, 8, 10, 45, 58, 67, 75, 98, 137, 162, 164, 165
eeprom, 14, 84, 85, 220
EEPROM, 13, 14, 43, 84, 85, 93, 109
EEPROM/NVRAM parameters for 50 series stations, 84
error, 13, 19, 27, 31, 40, 42, 49, 51, 52, 54, 55, 57, 63, 65, 80,
88, 89, 90, 101, 103, 108, 109, 113, 121, 133, 140, 147, 160,
185, 214, 218
Error, 4, 40, 42, 51, 52, 61, 88, 89, 91, 103, 108, 160
ERROR - Cannot Communicate With Server, 88
ERROR - Checkpoint type 5; class 8; code -24 Failed, 90
ERROR - Checkpoint Unsuccessful, 90
ERROR - Invalid File Header, 89
ERROR - Parameter Version Check Failed, 90
ERROR - SP Error - Lck_Chkpt Failed, 89
ERROR System Monitor Not Responding, 88
ERROR received doing a Load-All, 91
ERROR received trying to enter a station in the Control
Configurator, 87
Error Received While Performing Shrink, 88
Error: unable to qualify my own domain name (APLBUG) using
short name (HH1035), 91
exportfs, 141
F
FBM, 18, 42, 48, 83, 92, 93, 197, 213, 214, 215, 220, 223
FBM Types And Part Numbers Legacy, 92
FBM(200 Series) and FCM Types/Part Numbers, 93
fdformat, 44, 94, 96, 98, 183
FDSI Typical Modbus FDSI Configuration, 93
File System - Creating New On 50 Series diskette, 94
G
GCIO, 10, 11, 12, 13, 14, 15, 16, 111, 113, 114, 228, 229
GCIO adding to 51F (P79) station, 111
gcio_test, 13, 15
getpars, 59, 114, 115, 116
getpars and ucsaq utilities, 114
glof, 61, 68, 116, 117
grep, 9, 12, 13, 14, 62, 67, 68, 69, 70, 88, 117, 118, 133, 135,
142, 168, 171, 185, 189, 191, 209
H
head, 77, 82, 83, 117, 130, 157, 169
head command, 117
hi_init, 77
histbatch, 4
histmgr, 5
histonoff, 120, 189
Historian, 3, 4, 5, 6, 7, 19, 28, 64, 78, 92, 94, 99, 101, 102, 117,
118, 119, 120, 122, 131, 178, 179, 185, 194
Historian (legacy - copying from one AW to another), 117
Historian (Legacy) - Stopping And Restarting, 120
Historical Data - Retrieving From Collection Points on AP20/PW,
120
history, 7, 78, 104, 121, 227
history Scroll History Log, 121
history Command On 50 Series, 121
histps, 6, 122
hldb, 122
Hold State, 212
hopspy, 122
hostid, 5, 122
hostid determining on a 50 series station, 122
hps, 122, 189
hps Historian Command, 122
I
iaboot, 122, 123, 170
ICCAPI, 181, 182, 184, 185
iccapi save_all and loadall commands, 123
iccprt, 123, 124
ifconfig, 124
ifdc, 126
Installing fonts with the shrink & expand procedure on 50 series
stations., 124
INTEGRATED CONTROL BLOCKS, 124
Intelligent Devices Getting a List of All IFDs, 126
Intelligent Field Device Configurator, 126
IP Addressing on the Mesh, 127
IPC Connections - Getting Number Of, 127
isql, 128, 170, 178
ISQL Commands (examples), 128
ISQL Invoking on 50 Series, 128
J
jumper, 128
Jumper Settings - Hard Drives (20 series), 128
K
ksh, 44, 58, 167, 168, 185
L
LAN, 50, 51, 135, 136, 144, 145, 148, 207, 216, 217
Lan Interface, 52
Last CP Reboot Determining the date and time of the last CP
reboot., 130
last reboot Command, 130
Legacy historian and foxtst, 118
Letterbug, 10, 11, 12, 13, 50, 129, 145, 171, 217, 221, 228, 229
letterbug determining letterbug of 50 series station, 130
Letterbug Pinouts, 129
Letterbugs - Generic, 130
LI Mode, 21
Link Methods of Linking Files, 130
ln, 75, 80, 130
load_all, 38, 123, 182, 185
Load-All, 91
Loadalmpnl, 16
loadh50, 118, 131
loadh50 (Historian Restore Procedure), 131
localprinters, 16
Log file Generating from an executing file for troubleshooting
(AP20), 131
Logic, 83, 187
loopback mounts, 131
lp, 79, 131, 157, 160, 162, 164, 165, 166, 187
lp Command, 131
lpadmin, 162, 165, 166
lpc, 131
lpc Command, 131
lpsched, 79, 165, 166
lpshut, 79, 165, 166
lpstat, 114, 132, 165, 166
lpstat Command, 132
ls, 9, 13, 27, 61, 62, 79, 90, 95, 96, 97, 108, 112, 130, 132, 156,
159, 172, 173
ls command, 132
M
MAC address, 18, 149, 214
MAC Addresses, 18, 38
man, 19, 74, 76, 110, 115, 130, 133, 134, 147, 195, 212
man pages On-Line Manual pages and man Command, 133
MANUAL PAGES ON WP51, 134
Map Network Drive, 134
Mapping a Network Drive, 134
Memory Determining Physical Memory, 134
N
ncenv, 17, 119, 150, 179, 181, 182, 183, 184, 186, 208
netstat, 147, 177, 178
Network - Troubleshooting v7.x Network, 143
Networking Configuring Master Browser on Windows Station,
147
Networking AW51E with XP station, 146
newfs, 41, 44, 94, 175, 184
nfd, 21, 145, 146, 148, 177, 217, 218
NFD Guidelines when adding v7.x station to a node with v6.x,
148
NIC cards, 149
NIC Cards Changing MAC Address in the Registry, 149
nohup, 22, 77, 88, 149, 150, 171, 208, 210
NSAP, 31, 68, 95, 116, 135, 144, 150, 207, 208, 211, 212, 216
NSAP address, 31, 68, 95, 135
NSAP Addresses, 150
Nutcracker, 150, 151
Nutcracker Script to Call Nutcracker Environment Window,
150
O
Object Manager, 17, 48, 50, 102, 192, 194
oma, 50, 151
oma Utility, 151
omdel, 68, 69, 70
omget, 17, 47, 48, 50, 152
omget - Get Value Of Variables and Write To File, 152
omset, 48, 152
Operating System Determining Solaris Version and Hardware
Model, 152
Optimize Displays, 153
overruns, 48
OVERRUNS, 48, 52
P
partition, 3, 24, 25, 26, 32, 38, 40, 41, 71, 72, 74, 75, 76, 80, 96,
97, 138, 142, 154, 172, 173, 174, 175, 179, 197, 209
Partition Information (AP/AW 50 Series), 153
password, 106, 110, 154, 199, 201, 206, 212
Password Changing password for Foxview Environments, 154
path_to_inst, 31, 154, 155
path_to_inst Building Drive offline for 51B/C using 51A
processor, 154
pcfs, 45, 47, 96, 97, 140, 141, 167
pdfpack, 153
Period, 155, 156
Period And Phasing, 155
pg, 120, 156
pg Command, 156
phase, 122, 155, 156, 196
ping, 144, 156, 177, 199, 202, 205, 206, 216
ping Command, 156
Pinouts, 129
pr, 156, 157, 169, 187
pr Command, 156
pref, 9, 14, 16, 77, 137, 158, 188
pref Command, 158
printenv, 84, 86
printer, 3, 12, 16, 36, 48, 75, 113, 114, 117, 123, 131, 132, 158,
159, 160, 161, 162, 163, 164, 165, 166, 167
Printer, 16, 113, 137, 158, 160, 161, 162, 163, 164, 165, 166,
167, 168, 229
Printer Adding a printer to a 51F (P79) station (HH1061), 158
Printer And Scheduler Commands on 20 Series Stations, 165
Printer Not Showing Up In List Of Printers In Control
Configurator, 166
Printer Problem - HP1600 defaults to 60 lines/page while UNIX
defaults to 66, 162
Printer problem preventing printscreen color problems
(Models 51D and 51E), 162
Printer Problem Print Device Failure, 163
R
raid, 24
RAID, 24, 169, 175
RAID drive Connecting to Laptop, 169
rcp, 8, 44, 45, 118, 169, 170, 172
rcp Remote Copy on 50 series stations, 169
Reboot, 24, 38, 62, 77, 89, 112, 130, 145, 148, 155, 158, 160,
161, 170, 209, 217
Reboot on 20 Series Stations, 170
Reboot on 50 Series Stations, 170
Rebuilding CSA, 61
Recommended ways to free disk space.., 75
redinfo, 170
Reduction Groups, 170
Reduction Groups - Deleting Names of, 170
regedit, 100, 102, 147, 149
RegEdit, 107
rem_stop, 90
remd/remv, 50, 170
Remote Application, 171
Remote Application Troubleshooting Checklist, 171
Remote Copy, 169, 172
Remote Login, 172
Remote Login from VT100, 172
remote tape backup, 26
Remove Files, 172
Remove Files In A Directory, 172
Resetting EEPROM/NVRAM parameters for 50 series stations,
85
restore, 17, 23, 24, 25, 27, 40, 41, 80, 149, 172, 173, 174, 175,
221, 222
Restore, 24, 131, 149, 172, 220
S
samspy, 120, 179
save_all, 38, 43, 44, 123, 180, 181, 182, 184, 222
Save_all, 37, 180, 188, 221, 222
save_all Command, 180
saveall, 37, 38, 181
SAVEALL, 180, 220
saveh50, 117, 185
saveh50 (Legacy Historian Backup Procedure), 185
Scheduling .ksh files to run through Windows Scheduler, 185
SCI, 189
sconn, 43, 193
scripts, 8, 25, 30, 44, 50, 109, 215, 220
SCSI Bus Configuration, 186
SCSI Bus Configuration Guide, 186
Select Screen, 187
Select Screen - Setting up to have * in CP Name Field When
Select Screen is Called, 187
Sequence, 83, 187
Sequence Block - Editing Logic, 187
Sequence Block - Executing A Script From, 187
setacl, 3, 188
setacl Command, 188
setenv, 14, 77, 84, 85, 86, 128, 133, 178, 202
shareall, 142
Shell, 6, 20, 121, 128, 151, 178, 188, 194, 227
Shell On 50 Series, 188
show_params, 188
showrev, 188
Shrink, 37, 88, 180, 188, 221, 222
Shrink Command, 188
Shutdown, 7, 23, 24, 25, 26, 27, 76, 83, 188, 189
T
tail, 67, 75, 117, 210
tail command, 210
Tape Drive Checking the 4mm tape drive status, 210
tar Command, 210
U
ufsrestore, 41, 172, 173, 175
umount, 40, 42, 43, 44, 45, 90, 94, 126, 140, 155, 175, 180, 184
unalias, 9
uname, 45, 130, 152, 219
uname Command, 219
unix2dos, 45, 223
Upgrade, 23, 27, 136, 220
Upgrade Procedure CP30 or CP40 with legacy FBMs to
CP60(HH983), 220
Upgrade Utilities, 23, 27, 220
Upload, 37, 38, 180, 188, 221, 222
Upload Utility, 221
uptime, 221
use_displaymanager.sh, 76
use_foxview.sh, 76
useaimapi, 99, 102
usr_mkr, 28, 97, 124
Utilities: File2dsk and Dsk2file Issues with Win2000 and XP
(HH989), 221
Utilities: Upload, Shrink, Checkpoint, Save_all, 222
utmpx, 75
uucp, 75
V
VI, 46, 223, 224, 225
VI - Colon Commands, 223
VI - Inputting AND Editing Text, 224
VI - Moving Around A File, 224
VI - Opening A File, 225
vmstat, 225, 226
VT100, 8, 9, 22, 37, 38, 77, 89, 91, 96, 97, 104, 115, 118, 119,
120, 121, 124, 156, 161, 162, 164, 167, 170, 171, 172, 178,
179, 180, 181, 183, 185, 188, 191, 201, 202, 208, 212, 227
VT100 Unix Initialization Files, 227
Vxmon, 18
W
wc, 227
wc Command, 227
who, 50, 52, 64, 68, 117, 146, 217, 227
Windows Scheduler, 58, 185, 186
Work Files, 227
Work Files for Control Processors, 227
workfile, 59, 107, 221, 222
wp_dta, 10, 11, 12, 113, 228
wp_dta file AW and WP Peripheral File, 228
wtmpx, 75
Wyse Terminal, 161, 229
Wyse Terminal Settings When Used As An Alarm Printer, 229
X
xrebuild, 4, 5, 6