Practical System Tips

Practical System Tips
Technical Reference Manual

Last Updated on 1/27/2011
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.
For more information, contact: Invensys Process Systems' Customer Support Services Foxboro, MA 02035 USA Telephone (USA, Canada): 1-866-PHON-IPS (1-866-746-6477) Telephone (worldwide): 1-508-549-2424 Fax: 1-508-549-4999 Email: support@ips.invensys.com julie.monsour@invensys.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.
Access Levels Using the setacl Command

See setacl Command.
add_periphs (50 series)
When a SCSI peripheral such as a tape drive or CDROM is attached to a 50 series station, you can either do a boot r at the PROM ok prompt or run add_periphs from normal user mode: /usr/local/add_periphs
admintool
Starts graphical user interface for adding and administering user accounts and printer configuration.
AIM Historian Starting and Stopping

The following method may be used to stop and restart the AIM* Historian processes. 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. Kill -9 PID PID PID (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 (confirm that the processes are no longer running) /bin/csh apistart start_server FH 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.
AIM Historian problem with corrupt RTP file
This procedure is used when the RTP file is corrupt. First, use the procedure above for stopping the historian and API services. 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 can not 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 Invensys 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.
AIM Historian Troubleshooting Tools

Below are some troubleshooting tools for AIM Historian. Clearcfg removes RW files Dumpcvs reduction buffer contents Dumprcol remote collector data Dumpred reduction info from files Histspy view data and config APItxt historian calls via menu apispy historian calls via menu Msgcheck checks m file against im file Msgfix rebuilds im files Msgtst tests message collection with canned messages Sec2asc converts unix time to ascii Rtpcheck checks integrity of rtp and reduction files Rtpfix fixes some types of corruption of rtp or reduction files Testhv tests legacy servers hsfetch, etc. Testvar uses shared variables to test historian without control d-base Xrebuild rebuilds cross reference files Fh_sacego 51 only - extracts OAJ or sysmon messages The server initialization file, an_init.tcp, is located in /opt/aim/bin. The client initialization file, an_init.tcp, is located in \Winnt, or <INSTDIR>/common
Alarm Manager Install Files
In the installation notes for v4.3 and v6.1, a file transfer utility is now available which facilitates the transfer of files from one station to another. See Display Engineering for 50 Series Workstations for instructions. The /usr/fox/alarms/commgrp.cfg and the /usr/fox/alarms/horn.cfg may be the same on each 50 series workstation. The install file will contain at most one AM property scheme, at least one user interface scheme, and at least one alarm format scheme. They reside in /usr/fox/customer/alarms/cfg. Under /usr/fox/customer/config, a directory is created based upon the name of the database filename, e.g., myname.am causes myname.dir to get created. For each letterbug referenced in the database, an additional subdirectory is created. (The default letterbug is XXXXXX). Example: I created an instance in the DispAlarm 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. The following is how I would transfer my files 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 To copy to the WP5101, (if remote mounted as /rem/WP5101) cd /usr/fox/customer/config cp r mycompany.dir /rem/WP5101/usr/fox/customer/config cd /usr/fox/customer/config/mycompany.dir cp dmcfg /rem/WP5101/usr/fox/customer/hi 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
Alarm Manager Problem with AM Display Getting Stuck on the Screen
An AM display may get stuck on the screen, Cursor can move but nothing can be picked. If you can get into a vt100 session from remote station, enter the following: pref AW0000 amcmd quitam on; exit (where AW0000 is the Alarm Manager name) The DM will now be free.
Alarm Managers Quitting Alarm Managers that are not quittable
From VT100: pref AM0000 amcmd quitam on; exit (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.
Alarms Common Alarm Group (CAG)
To append workstation letterbugs to the common alarm group, you must invoke: /usr/fox/alarms/CAGinit This will append the WP names to /usr/fox/alarms/commgrp.cfg.
Alarm Server Task ast Problem

The ast seems to stop working sometimes when the time changes, if this happens do the following: ps eaf | grep ast kill 9 PID The process will respawn.
alias - Creating a Pseudonym for a Command

alias [name] [cmd] (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 (Remove name from the alias list) Example (assigning ls l to have the alias l:
alias l ls l 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`# (the 2 lines above are a single command. There is NO space between prompt and =) 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).
Annunciator Keyboard Troubleshooting Annunciator Keyboard Installation Problems

NOTE: If using FoxView, the Numeric Keypad of an annunciator keyboard will not work if you have enabled the option "Windows Off" on the workstation. This problem is fixed on FoxView 8.0 1) If properly configured, System Definition must show the following items attached to the host station (Ex:3AWE01): P000nn GCDEV (Graphics Controller, 3AWE01, Serial Port 1) - P000nn M KB (Modular Keyboard, 3AWE01, Primary GCIO Bus) 2) Be sure you have selected MKYBD (Modular keyboard) on SysDef, and not AKYBD (Alphanumeric keyboard). - You can have up to 4 Modular keyboards for the same station. - The first 2 has to be SysDef's "M KB Modular keyboard", while 3rd and 4th should be "MH KB Modular keyboard". - The last 2 keyboards are to be connected to the 2nd GCIO. 3) Once you pass the Committal diskette the host station will have a new/modified file: /usr/fox/sp/wp_dta - This file has the information for ALL peripheral devices on ALL WP/AWs like: touchscreen, modular keyboards, alphanumeric keyboards. - This file is common to ALL stations. It has one line for every WP/AW on the system. - Since this file contains binary entries, it cannot be modified with a text editor. Use bpatch (/usr/foxbin/bpatch) to inspect this file. See example below. Example (from TAC Lab, station 3AWE01): /usr/foxbin/bpatch /usr/fox/sp/wp_dta FILE: wp_dta (224) - ASCII PAGE: 0 (0 - 0) x0: x1 x2 x3 x4 x5 00: 47 32 42 4f 4f 01: 47 33 42 4f 4f 02: 47 34 42 4f 4f 03: 33 41 57 42 30 04: 33 41 57 43 30 05: 33 41 57 45 30
x6 54 54 54 31 31 31
x7 0 0 0 0 0 0
x8 0 0 0 0 0 0
x9 1 1 1 1 1 1
xa 32 32 32 0 0 50
xb 0 0 0 0 0 31
xc 0 0 0 0 0 0
xd 0 0 0 0 0 0
xe 30 30 30 0 0 0
xf 32 32 32 0 0 0
12 1 1 1 0 0 0
0123456789abcdef G2BOOT...2...02. G3BOOT...2...02. G4BOOT...2...02. 3AWB01.......... 3AWC01.......... 3AWE01...P1..... <-
06: 07: 08: 09: 0a: 0b: 0c: 0d:
34 34 32 32 32 33 33 33
57 57 57 57 41 41 41 57
50 50 50 50 57 57 57 50
32 33 32 33 42 42 44 35
30 30 30 30 30 49 30 30
31 31 31 31 31 31 31 31
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
1 1 1 1 1 1 1 1
0 0 50 50 0 0 0 0
0 0 31 31 0 0 0 0
0 0 0 0 0 0 0 0
0 0 31 31 0 0 0 0
0 0 30 30 0 0 0 0
0 0 32 32 0 0 0 0
1 1 1 1 0 0 0 0
4WP201.......... 4WP301.......... 2WP201...P1.102. 2WP301...P1.102. 2AWB01.......... 3AWBI1.......... 3AWD01.......... 3WP501..........
... you might need to press RETURN to see the next page... 4) Verify if fields on wp_dta are correct. See table below. bytes 0-6 WP letterbug plus null terminator (Example: 3AWE01) byte 7 Secondary GCIO/Touchscreen Letterbug ( 50 series only) 00 (Hex) no secondary GCIO and no touchscreen S (Ascii) secondary GCIO and no touchscreen 6 (Ascii) secondary GCIO and touchscreen byte 8 WPIO Primary Station ID 01 (Hex) no multiscreen 02-7F (Hex) multiscreen present, value assigned by SysConfig/SysDef byte 9 Primary GCIO/Touchscreen Letterbug 00 (Hex) if WP20/WP30: no touchscreen if 50 series: no primary GCIO, no touchscreen ===> P (Ascii) primary GCIO and no touchscreen (50 series only) <== 2 (Ascii) if WP20/WP30 letterbug of touchscreen if 50 series primary gcio with touchscreen C-Z (Ascii) WP20/WP30 only touchscreen configured w/multiscreen byte 10 Modular Keyboard #1 Letterbug 00 (Hex) no modular keyboard ===> 1 (Ascii) modular keyboard configured, no multiscreen <== C-Z (Ascii) WP/WP30 only.. modular configured, w/multiscreen byte 11 Modular Keyboard #2 Letterbug 00 (Hex) no second modular keyboard 3 (Ascii) second modular keyboard configured C-Z (Ascii) WP20/WP30 only. Second kbd configured w/multiscreen byte 12 Numeric Keypad Letterbug 00 (Hex) no numeric keypad 1 (Ascii) numeric keypad located on keyboard #1 3 (Ascii) numeric keypad located on keyboard #2 byte 13 Alphanumeric/Third Modular Keyboard Letterbug 00 (Hex) no third modular keyboard 0 (Ascii) alpha keyboard, no multiscreen 4 (Ascii) third modular kbd lbug, ( 50 series only) byte 14 Mouse/Trackball or Fourth Modular Keyboard Letterbug 00 (Hex) no mouse, trackball or fourth modular kbd 2 (Ascii) WP20/30 only, mouse or trackball configured 5 (Ascii) fourth modular kbd lbug (50 series only) B (Ascii) WP20/30 only, mouse/trackball w/ multiscreen byte 15 Multiscreen Initial Owner of Device 00 (Hex) not initial owner of multiscreen devices. Always 00 for 50 series. 01 (Ascii) WP20/30 station is initial owner of multiscreen devices 5) Another file that comes from the Committal diskette, only on 70 Series, is: /usr/fox/sp/gcioport This file lists the stations that have GCIOs attached and to which port. Typical gcioport contents:
AW7001 COM2 AW7002 COM3 AW5001 ttyb 6) SysMgmt will show both GCIO and MKYBD only if they were properly CONFIGURED, and they will appear WHITE only if their letterbugs match the ones on wp_dta. 7) Be sure DIP switches on GCIO and kybds are configured for the right letterbug: P = 0/1 0011111 (First switch is for Horn volume, the rest are for letterbug) 1 = 0/1 0010000 (First switch is for Horn volume, the rest are for letterbug) 2 = 0/1 0001000 (First switch is for Horn volume, the rest are for letterbug) 8) If a serial printer WAS configured on this station and later removed, you have to MANUALLY remove the file: /usr/local/local_printer. This file would prevent the 'sxlinkd' process from running during station boot. 9) Verify if process "sxlinkd" (the one that talks to the GCIO/Kybd) is running: ps -ef | grep sxlinkd 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 "R" - Get GCIO ROM Info "U" - Set GCIO Unit (Ux=ID #(hex)) "C?" - Get 2nd CRT Location "C" - Set 2nd CRT Location (CL|CR|CT|CB) "GR" - GCIO Reset (GRx) "E" - Bad EEPROM Burn (Ex) "B" - Unit EEPROM Burn (Bx) "BI" - Burn & Ignore Errors (BIx) "F" - LED Flash (Fx=led #(hex)) "l" - LED On (lx=led #(hex)) "L" - LED Off (Lx=led #(hex)) "Z" - LED Test (Zx) "h" - Horn On (hx=frequency) "H" - Horn Off (Hx=frequency) "TR" - Touchscreen Reset (TRx) "TC" - Touchscreen Calibrate (TCx) "TF" - Touchscreen Config (TFx=mindelta) "TS" - Touchscreen Scale (TSx=scale) Where "x" is the unit # (0-7) "Esc" or "Q" - Exit Program If configuration is not correct, gcio_test will show continuously something like: (use CTL-C to stop) ioctl GET_UNIT error, len = 255 (should be 8) *** ..(continuously) The following devices are used by gcio_test. They exist only on AW/WP/50/51s. 3AWE01# ls -l /dev/gc* crw-rw-rw- 1 root root 132, 2 Jun 30 21:06 /dev/gcio crw-rw-rw- 1 root root 132, 3 Jun 30 21:06 /dev/gcio1 crw-rw-rw- 1 root root 132, 4 Jun 30 21:06 /dev/gcio_ecb 12) Use Annunciator debugging tool (LK HH): Turn debugger on: pref -WPLBUG dmcmd "annun -1 -1 -1" Get LED assignments: pref -WPLBUG aacmd "dump lite_assign" Check output file: /usr/fox/alarms/WPLBUGAAtab.asg
It shows: Compound-Block-Alarms-Pan-Key-AlmStatus Get LED current status: pref -WPLBUG aacmd "dump lite_state" Check output file: /usr/fox/alarms/WPLBUGAAtab.cnt It shows: Panel-Key-Count-Num-State Turn Panel 2, LED 1 on (3=on, 4=off, 5=flashing): pref -WPLBUG dmcmd "annun 2 1 3" Turn debugger OFF (Important!): pref -WPLBUG dmcmd "annun -2 -2 -2" 13) Verify EEPROM settings. If "ttyb-ignore-cd" is False, the station will not talk to the serial port. 3AWE01# 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: ok> 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) GCIO --------------------------------------------------- WP50/AW50 P0970VB/BW/HS [3/15/30m,10/50/100ft] GCIO ------------------- ---------- B------------------ WP51A/AW51A P0970XM/XN/XP P0912GU P0970XG (standalone) nullmodem split_cable or DNBX A->DNBX GCIO ------------------- ---------- B------------------ WP51A/AW51A (DNBI) P0970XM/XN/XP P0912GU P0970XL/XH/XJ/XKXG nullmodem split_cable A->DNBI GCIO --------------------------------------------------- WP51B/AW51B P0971PA/PB/PC GCIO ------------------- ---------- B------------------ AW51C/AW51B1 P0971PA/PB/PC P0912GU P0912GX WP51B1 nullmodem split_cable A->DNBX or DNBI GCIO --------------------------------------------------- WP51D/AW51D P0971SU/SV/WZ GCIO --------------------------------------------------- WP51E/AW51E P0971PA/PB/PC
Troubleshooting with gcio_test cd /usr/fox/sp/files gcio_test *********************************************************************** * * * GCIO Test Tool * * * *********************************************************************** <<< Opening GCIO Device Channel "/dev/gcio" >>> Unit #0 ("Primary GCIO "): Station #77 Unit #1 ("Secondary GCIO "): Station #E5 Unit #2 ("Annunciator Panel #1"): Station #EF Unit #3 ("Annunciator Panel #2"): Station #FB The following key commands are supported: "S" - GCIO Socket Status "R" - Get GCIO ROM Info "U" - Set GCIO Unit (Ux=ID #(hex)) "C?" - Get 2nd CRT Location "C" - Set 2nd CRT Location (CL|CR|CT|CB) "GR" - GCIO Reset (GRx) "E" - Bad EEPROM Burn (Ex) "B" - Unit EEPROM Burn (Bx) "BI" - Burn & Ignore Errors (BIx) "F" - LED Flash (Fx=led #(hex)) "l" - LED On (lx=led #(hex)) "L" - LED Off (Lx=led #(hex)) "Z" - LED Test (Zx) "h" - Horn On (hx=frequency) "H" - Horn Off (Hx=frequency) "TR" - Touchscreen Reset (TRx) "TC" - Touchscreen Calibrate (TCx) "TF" - Touchscreen Config (TFx=mindelta) "TS" - Touchscreen Scale (TSx=scale) Where "x" is the unit # (0-7) "Esc" or "Q" - Exit Program -----------------------------------------------------------------
Annunciator Keyboard Annunciator Will Not Work While Direct Connect Printer is Configured
If your direct connect printer was configured for the serial port instead of the parallel port, the annunciator panel will not work. Also, if you had a serial printer connected to the station and removed it to add an annunciator panel, you will need to do the following. A file is created in /usr/local called localprinters. This file must be removed in order for the annunciator panel to function. This file is created when a printer is configured for the serial port. If you have a direct connect printer connected to the parallel port, this file need not exist and if you want to use an annunciator on the serial port of the station, this file MUST not exist. The direct connect printer should be configured to Port 2 on 50 series stations.
Annunciator Panel WPLBUGAApan or WPLBUGAAtab Modification
Instead of rebooting the station after updating the WPLBUGAApan or WPLBUGAAtab file, you can just kill the aa_wp50 process and it will automatically restart. Also, the following pref command will reset using the new updated pan and tab files: pref WP5101 ascmd "Loadalmpnl /usr/fox/alarms/WPWP01AApan" then kill the ast process so that it will respawn.
AP/AW 50 Series Stations Replacement - Changing MAC Addresses Instead of Downloading FBMS or Rebooting CPs
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 For each CP, get the PSAP address of the CP by typing the following: cp_utl -gm -oh -p<lbug>_STA:STATION.APPSAP the result is a 26 byte PSAP address: xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx Record this number as it will be needed later in the procedure. Get the MAC address of the AW by typing the following: ckmacadr 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 PPID The parent process ID PY The priority SZ size of swappable image in kb TD top of data space in kb ST stack size in kb OF number of opened files FT number of file table entries IT number of inode table entries LT number of lock table entries 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 (will return information related to networking) apropos editor (will return information on the various editors in the system)
Archiving Historian - Backup your historian archive Message

File /etc/wparlns defines all WPs, AWs, and PWs in the system. The above message is output when archiving finishes. Use vi to edit /etc/wparlns, delete any WPs, Aws, or PWs for which you do not want the Archive Backup Required message to appear. If you prefer this message to go to the System Monitor error report printers, use vi to edit the file /etc/histpath and set ARCPRT=yes. The default value is no.
Archive to Tape (Legacy Historian) Problem Tape Drive Suddenly Not Recognized
Although archiving the legacy historian to tape has worked in the past, a file gets edited that makes the tape device unrecognizable to complete the backup. If youve previously been able to archive to tape, check the following parameters of the file: /opt/fox/historian/bin/histadev. TAPE= TAPE_NR= TSIZ= When this problem occurred, the parameters were set as follows: TAPE=/dev/rst5 TAPE_NR=/dev/nrst9 TSIZ=150M 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 C Shell is used to execute script -s Standard Bourne shell is used to execute -m sends mail to user after job has been completed -f script reads commands to be executed from named script file -q queue submit jobs in a queue other than default queue a. -l job reports all jobs scheduled for the user or a specified job -r job removes specified jobs
ATS Information - (Address Translation Station)

ATS Image OS1A70 ats_db.cfg file contains list of stations with ATS station type 0x602 ats_lst.cfg Used by SMDH STA<LBUG>.BIN Used only when ATS Boots from host (contains MAC, IP Addresses, and Node Cfg. Info.)
The ATS is the Default NFD Initiator for the Node and only accepts Change Master requests from Mesh stations. There is no NFD for the mesh only the Nodebus side. The rnfd (remote nfd) tool causes an ATS to generate an nfd_log on the host. You can view the nfd log from the ATS (see rnfd). An ATS counts against the 64 station limit per node. Each Node can have only one ATS pair. Only one node can have both a LI and ATS. Only One Mesh Cloud per system.
ATS / Time Configuration (MESH: Class C)

If you are having problems with time issues after adding MESH stations including the ATS to an existing legacy system, check the following: Make sure that the ATS is in LI Mode (The ATS is configured to be in LI mode by System Definition configuration. See the section in these notes entitled SYSTEM DEFINITION CLASS C INSTRUCTIONS.) Check that the file /usr/fox/sp/system_time.cfg contains UTC. Make sure that the Microsoft Patch for DST has been installed (2007010ABI advisory) on all stations. There is a different patch for the P91 Server 2003 stations and the P92s. Make sure that the time is set to your local time (mine is GST-Central Time) and check the box to automatically adjust for DST. In System Management, select the DST pick from the top menu and set to Auto. (If the DST pick is not selectable in System Management, the AW/WP is not configured as a System Monitor Notification WP not to be confused with System Monitor WP. You must have at least one MESH station configured as a System Monitor Notification WP).
awk - PATTERN MATCHING PROGRAM
Use the pattern-matching program to modify the specified files. Awk is a very powerful tool, this is just a small portion of the uses of the awk command, which may be helpful. Syntax: awk [-f program file] [-Fc] [prog] [parameters] [filename] -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 has "/etc" in column 1 of file1, type: awk '$1 ~/^\/etc/ {print $0}' file1 To print every line that does not have "/etc" in column 1 of file1, type: awk '$1! ~/^\/etc/ {print $0}' file1
Background - Running files in
Example: nohup tar cvf /dev/fh0 /usr/sp/files & 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 AP - Configuring WPs for AP Switching on 20 series stations
sys Change_Env Password_Eng_Env Utlcfg AP_BACKUP select backup file server then you must reboot the WP! There is a HH on problem with 20 series not seeing 50 series APs when selecting backup.
Backup-to-tape Utility
See Upgrade Utilities.
backup and restore Procedure
Customer Advisory 2005067abi suggests following the recommended procedures below due to unreliability of tape backups due to I/A processes not shutting down completely. Please use the Phase 1 instructions before Phase 2 below. ***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 "VT100" 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: Shutdown the station by clicking on the following picks: "SftMnt - Shutdown_AW - SHUTDOWN". If on an AP, skip this step, of course. This is will bring the station to the "pseudo" single-user mode After login, at the prompt type: init 0 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 Once the "ok" PROM prompt is displayed, type: boot -s 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 The restore utility is supplied on the Day 0 CDROM. Boot on the CDROM boot cdrom 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 AP/AW50 level 0 to 1/4 tape /usr/local/dmp9_150MB AP/AW50 level 9 to 1/4 tape /usr/local/dmp0_8MM AP/AW50 level 0 to 8MM tape /usr/local/dmp9_8MM AP/AW50 level 9 to 8MM tape /usr/local/wpdmp0_150MB WP50 level 0 to 1/4 tape /usr/local/wpdmp9_150MB WP50 level 9 to 1/4 tape /usr/local/wpdmp0_8MM WP50 level 0 to 8MM tape /usr/local/wpdmp9_8MM WP50 level 9 to 8MM tape /usr/local/dmp0_8MM AP/AW51 level 0 to 4MM tape /usr/local/dmp9_8MM AP/AW51 level 9 to 4MM tape /usr/local/wpdmp0_8MM WP51 level 0 to 4MM tape /usr/local/wpdmp9_8MM WP51 level 9 to 4MM tape /usr/local/backup see backup and restore new (v6.2)
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 File systems /, /var, /usr, and /opt Tape 2 Informix raw partition Tape 3 Main Mirrored Disk raw partition Tape 4 Backup Mirrored Disk raw partition 50 series WPs will have only 1 tape. If backing up using the new /usr/local/backup routine, please see instructions at backup and restore. The following is the procedure to backup to 5GB tape:
Backups - Level 0 (Complete) Backup

Shutdown to single user mode fsck
dmp0_8MM (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.
Backups - Level 9 (Incremental) Backup
Shutdown to single user mode fsck dmp9_8MM (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.
Backup Using A Remote 50 Series Tape Drive

When performing a remote tape backup from one 51 station to another, it is important to be in single user mode to preclude the possibility of the file system being changed during the procedure. You should halt the machine and reboot into single user mode with boot s. However, in single user mode, all I/A Series communications have been halted by the shutdown procedure. For this reason, it is necessary to manually start the I/A Series software which allows communications. This is done as follows: sh mount F vfox /foxboro /dev/foxboro trap 16 trap 17 /usr/fox/exten/mac_daemon /dev/le 0 1 > /dev/null & 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> (level 0 dump to 150MB tape) Return to multi-user mode by typing exit.
Backups - Checking Save-All Diskettes Integrity

To check the integrity of your save-alls: mount the floppy and lc /dev/f0 (AP20) ls /dev/fd0 (50 series) or select Show Diskette Directory in the ICC.
Backups Using the dd command with bs and count

bs-80b means copy data in chunks of 80 blocks at a time. bs-80 means copy data in chunks of 80 bytes at a time. Using bs and count with the dd command: bs defaults to 1024 bytes/block on AP20, AW50 and AW51A; 512 on PW; and 2084 on 51B and 51C. Example: Bs=80b will copy 80 bytes at a time. Count gives the number of times to get a given number of blocks. Example: bs=512b count=2880 means to get 512 bytes/block for 2,880 times which gets a total of 1,474,560 bytes. Youll be getting 2880 blocks of data. A 5 floppy on PW has 2400 blocks at 512 bytes/block. A 5 floppy on AP20 has 1200 blocks at 1024 bytes/block. To get the count to use bs=80.
Divide 80 into 2400 or 1200 depending on which youre using. Example: Using dd on 5 floppy on PW with bs=80b, the count would be count=15360. If you use a larger count than is necessary, it will stop at the end. If theres a bad spot on the disk, it will be flagged as an error. If you use the dd command with no bs or count, it will do a bit copy of the entire disk using the defaults.
Backups AP20 - Copying From Primary Hard Drive
(rshd3.all) To Extra Hard Drive (rshd4.all) On Line. This extra hard drive is an exact mirror image of the primary to be used when the primary fails. It can be swapped out with the primary. dd if=/dev/rshd3.all of=/dev/rshd4.all 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)
Backups - Recommended Directories To Back Up

These directories are specifically 20 series. These files will be contained in different directories on the 50 series stations. (i.e., /usr/fox/sp/files/*CPNAME* will be located in /opt/fox/sp/files on the 50 series). You should consult your Installation/Users Guide also for recommended files to backup. A very good way to back up your files is using the Upgrade Utilities. See Upgrade Utilities in this manual. AIS files to backup in /opt/fox/ais/bin: opensets, an_init.tcp, an_init.dec Report Writer files in /opt/fox/rptwrt: ./rpt_c fg/*.cfg; ./sched/* Control Libraries in /usr/fox/ciocfg: sequenlibrary; plblibrary; sequeninclude Foxwatch files: /opt/rem; /opt/fox/bin/remote Display Related Files: /usr/disp; /usr/dispgrp/usr/displib; usr/fox/wp/fonts/usr_mkr*.bdf; /usr/fox/customer/hi/dmcfg; /usr/fox/customer/alarms/cfg; /usr/menus; /usr/fox/wp/data/wp*; /usr/fox/wp/data/init.user; /usr/fox/hi/init.cmds; /usr/fox/alarms/horn.cfg; /usr/fox/alarms/*AA*; /usr/fox/alarms/commgrp.cfg; /usr/fox/alarms/alarms.fmt; /usr/markers; /usr/fox/hi/sys_*.*; /usr/fox/hi/conventions; /usr/fox/hi/Dsp_Status; /usr/fox/wp/data/conventions; /usr/fox/wp/data/Dsp_Status; /usr/fox/sys/Change_Env; /usr/fox/ia16/usr/displib; /usr/fox/ia16/usr/disp; /usr/fox/ia16/usr/dispgrp; /usr/fox/ia16/usr/menus; /usr/fox/ia16/usr/fox/sys/Change_Env; /usr/fox/ia16/usr/markers System-Related Files: /etc/inittab; /etc/shadow; /etc/fstab; /etc/vfstab; /etc/hosts; /etc/hostname.le?; /etc/hostname.hme?; /etc/passwd; /etc/group; /etc/netmasks; /.cshrc; /.profile; /.rhosts; /.Xdefaults; /etc/defaultrouter; /etc/dfs/dfstab
Application Files: /usr/applic/start; /usr/applic/mastercron; /etc/fox/user_apps.dat; /etc/fox/rc.foxapps; /usr/spool/cron/crontabs; /opt/foxind Historian Files: /opt/fox/hstorian/bin/*.dbs
Backups AP20- Checking Streaming Tapes Integrity

stcopy -I /dev/rtape2
Backups - Checking Tape Stamp On 50 Series

dd if=/dev/nrst0 of=tapestamp bs=126b tar tvf /dev/rst0
Backups - AP20 Streaming Tape
Although these commands may be issued from normal user mode, you must shutdown to single user mode to do the full tape backup on the AP20s. st -f /dev/tape2 status This command will return the drive status information about the tape. stcopy -t /dev/tape2 This command will retention the tape. stcopy /dev/rshd3.all /dev/tape2 This command will copy the primary hard disk to tape. stcopy /dev/rshd5.hstor /dev/tape2 This command will copy the extended hard drive to tape.
BACKUPS - Saving Multiple Directories/Files to Tape 50 series stations

***METHOD 1 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 To backup /usr/menus, /usr/disp, and /usr/fox/sys/Change_Env to tape. tar cvf /dev/rst9 /usr/menus /usr/disp /usr/fox/sys/Change_Env or tar cvf /dev/rst9 /usr/menus (to copy one file) tar rvf /dev/rst9 /usr/disp /usr/fox/sys/Change_Env (to append more files) or you can also use the mt command to forward to end of file mark: tar cvf /dev/rst9 /usr/menus mt fsf /dev/rst9 tar rvf /dev/rst9 /usr/disp
mt fsf /dev/rst9 tar rvf /dev/rst9 /usr/fox/sys/Change_Env This method spaces forward to the end of file mark using the MT command.
Boot Procedures for Troubleshooting an AW/AP/WP that wont boot

Ask user for configuration information boot a Reconfiguration boot. Probe all attached hardware devices boot r Boot only to init level s/single user mode boot s Boot with verbose messages enabled boot v 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 an 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 physicalname 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 mu lti-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 preceeded 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 (installs baseline 6.4) Do not reboot machine. perform only the steps below: 1. For Ultra-30 WP51E: Boot cdrom, mount the / file system and copy the following files mount /dev/dsk/c0t0d0s0 /mnt cp /cdrom/name_to_major /mnt/etc/name_to_major 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 # For Internal System hard drive or mount /dev/dsk/c1t0d0s0 /mnt # For External System hard drive cd /mnt rm /mnt/dev/dsk/* rm /mnt/dev/rdsk/* drvconfig -r devices -p /tmp/root/etc/path_to_inst disks -r /mnt reboot -- -r ************* WP51E now boots *****************
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 Where f is the letterbug of the target fbm. 2. CMX<LBUG>.BIN File This file is loated in /usr/fox/sp/files directory and contains the NSAP address of the station. If a station is booting local, it must have the same NSAP address as its boot host. You must use usr/foxbin/bpatch to view this file. 3. Enable Download The Download Enabled/Disabled parameter is set through System Management by going to the Equip. Change pick for a given station. Sometimes gateways on their first bootup will show booted green and online 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 B<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.
Boot Partitions On PC - Switching
Venix to DOS: /etc/fdisk -a 0 (reboot) DOS to Venix: fdisk Change boot partitions; Non-DOS partition
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 (bpatches the file called transfer01.dwf) ! execute command in shell -x toggle command line option <cr> display next page ? display help text DEL quit program/exit edit mode \ display previous page / search for ASCII string ^f select named file ^n select next file ^p select previous file ^q quit without writing changes ^r redraw the screen ^x turn on debug ^g cursor movement home ^h cursor movement left ^j cursor movement down ^k cursor movement up ^l cursor movement right a edit ASCII portion f display first page of file h edit hexadecimal portion l display last page of file nnn direct addressing q quit program r reread current page u undo all changes to page w write out changed page
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. 8. To give control back to the operator, turn knob back to N
C Program Compiling 20 Series

Example Compiler: The following script should be named hcc: ESQL=/usr/informix/bin/esql cc -c $1.c -I/usr/include/fox $ESQL $1.o -o $1 -lhist -lisam -lfox lpw syntax: hcc <source program name> normal message to receive is: ld: /usr/local/lib/libpw.a: cannot open (do not be alarmed, everything went well)
Cable Pinouts Serial cable to null modem

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.
Cancel Print Job
cancel lp1 110 (110 being jobname)
cat Command
cat filename (print filename to screen) cat filename > /dev/LP01 (print filename to LP01 printer)
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 join split lines -l length split lines longer than length -s standardize code to style of Kernighan and Ritchie in The C Programming Language.
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 To input configuration from an ASCII file cfgpts -A hist22 < /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
Checkpoint Files Location
/usr/fox/sp/files DB(CPLBUG).UC Current DB(CPLBUG).init Initialization File BB(CPLBUG).UC Backup file
Checkpoint File Maximum Sizes
The following are approximate maximum file sizes of CP checkpoint files: CP30 = 350k CP40 = 700k CP40B = 1.3mb CP60 = 2.7mb
Checkpoint File Rebuilding Corrupt Checkpoint File(HH953)
Problem: Checkpoint file is corrupted and no saveall is available. This procedure describes how to fix a corrupt checkpoint file and create a loadall using .O and .wf files. 5CP301 is the CP letterbug being used in this example. 1. In VT100, go to /usr/fox/sp/files of CP host, copy .init to .UC and reboot the CP. a. cd /usr/fox/sp/files b. cp DB5CP301.init DB5CP301.UC c. Reboot the CP 2. Make a directory to create a saveall in the /opt partition and create a saveall with cio api a. mkdir /opt/SaveAll /opt/SaveAll/5CP301 b. cd /opt/fox/ciocfg/api c. save_all 5CP301 /opt/SaveAll/5CP301 3. Go to ICC and Initialize, then reboot CP. a.From Menu: Config, Control_Cfg, CIO_Config, Vol, Edit Station, 5CP301 b. From ICC, Select MAINT, then Initialize c. Reboot CP 4. Go to VT100 and perform loadall from the saveall created in step 2. a. cd /opt/fox/ciocfg/api b. load_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 To change the access mode of one or more files: Example: chmod +x filename (to make file executable) who u user g group o other a all opcode + add permission - remove permission = assign permission mode r read w write x execute s set user(or group) id t save text (sticky) mode u users present permission g groups present permission o others present permission chmod u+x file (will add execute by user permission to 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 print byte number and differing bytes -s print only the return codes: 0=files are identical 1=files are different 2=files are inaccessible
Concatenating Drives (50 series)
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
Concatenation Problem / add-to-sys Problem Concatenating Drives
The process of disk drive concatenation on an AP/AW 50 series station requires the /opt partition is not mounted. During the operation of the dft add_to_sys command, all loopback file systems (lofs) and /opt are unmounted. The umount will fail if any programs are accessing lofs or /opt, but the umount failure does not return an error condition to the dft add_to_sys command. Therefore, dft add_to_sys continues processing assuming that all loopback file systems and /opt are unmounted. The dft add_to_sys command issues a meta database clear command. The meta database command fails, returning an unable to clear metadb message to the user. This problem can be avoided by performing the following steps to umount lofs and /opt before issuing the dft add_to_sys command.
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. Concatenating Drives (50 series) Restoring Problems (HH859) Error commonly seen is SCSI 2 Already in Use First restore using level 0 dump tapes using either restore_8MM or restore_150MB with the exception of the OPT partition. ( As described in the B0193ND document you will be asked during the restore process if you have concatenated drives answer yes to this and the /OPT will be omitted) Under normal circumstances restoring of the /OPT partition as described in the B0193ND manual would result in the completion of the restore process, but there are times when the metadatabase becomes corrupt or does not load properly and this results in the improper loading of the /opt partition. If the following steps are followed the Metadatabase will be set to a day0 install and will always result in the proper loading of the /OPT partition. Boot the system into single-user mode (boot -rs) and follow these steps: 1. cd /usr/local/medusa/datafiles 2. cp sys.diskdata.temp sys.diskdata 3. cd /usr/local/medusa/databases 4. cp md.tab /etc/opt/SUNWmd (copies the file md.tab to directory SUNWmd) 5. cp md.cf /etc/opt/SUNWmd (copies the file md.cf to directory SUNWmd) 6. cp mddb.cf /etc/opt/SUNWmd (copies the file mddb.cf to directory SUNWmd) 7. uncompress md.db.xxx.xxxx.Z (.1050.AW51,.2100.AW51,.535.AW51)(md.db.[drive type].[system type].Z) (this is SCSI drive address =3) 8. dd if=md.db.xxx.xxxx of=/dev/rsd0d (copies day0 metadatabase to the raw partition) 9. shutdown and reboot to single user mode boot s. Reconcatenate the extra hard drives as follows: 10. cd /usr/local/medusa 11. dft format_disk esp0 scsi2 (may need to type ./dft XXXXXX) 12. dft add_to_sys esp0 scsi2 repeat the above steps for all other drives 1 then 0 You are now ready to restore only the opt partition as described in the B0193ND DOC. (The following steps are taken from the B0193ND) 1. Shut down into single user mode 2. First check the root and usr partitions fsck /dev/md/rdsk/d0 (root) fsck /dev/md/rdsk/d4 (usr) 3. Create the new partition (opt) newfs /dev/md/rdsk/d5 4. Check the newly created file system fsck /dev/md/rdsk/d5 5. Mount the partition mount -o rw -F ufs /dev/md/dsk/d5 /opt 6.a. If restoring from 150 MB tape cd /opt ufsrestore tfs /dev/rst0 1 (this views the file system Table Of Contents) ufsrestore xfs /dev/rst0 1 level 9 dump (if any) ufsrestore tfs /dev/rst0 3 ufsrestore xfs /dev/rst0 3 6.b. If restoring from 5 GB tape 4mm cd /opt
ufsrestore tfs /dev/rst9 4 (views the partition Table of contents) ufsrestore xfs /dev/rst9 4 (restores partition) 7. 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 8. Unmount the partition cd / umount /dev/md/dsk/d5 fsck /dev/md/rdsk/d5 reboot and the 51 series box will now boot into I/A
CP60 Installation/Grounding Checklist
The following checklist has been used many times when having problems with CP60 grounding issues. Problems may be fault-tolerant CP60s going single, excessive PIO bus errors, etc. After satisfying every one of the following items, problems were resolved in all cases. Each metal enclosure must have a SINGLE connection between the insulated earth terminals and the enclosure frame. 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.
CPs Control Processor Maximum Values and Loading

The maximum number of block equivalents (BEQs) for CP10s, CP30s, Gateway 10/15s and Integrator 30s are 300, 1000, 300 and 1000, respectively. In the local configuration, the maximum number of FBMs per CP10 or CP30 is 24. In the remote configuration, the maximum number of FBMs per CP10 or CP30 is 48 (w/ Remote Fieldbus Isolators). A maximum of 24 FBMs can be attached to any one (single or dual) Fieldbus Isolator, with a maximum of 16 FBIs per CP. The maximum fieldbus length is 1800m/6000ft end-to-end. Fieldbus Isolators are required when the length of any local bus exceeds 12m/40ft. The maximum checkpoint file size for a CP60 is 2.7 mb. Sometimes Foxwatch report states that a CPs checkpoint file size is reaching the maximum. Check to see if the CP is a CP60 and compare the values.
conn/sconn
See som/rsom.
Converting 20 series save-alls to 50 series save_alls

***On PW or AP20: Put in the drive the 20 series save_all diskette: mount /dev/fh0 /f0 -r cd /f0 tar cvf /usr/tmp/<CPLBUG> . (<CPLBUG> = the CP letterbug of save_all) (Be sure to include the . at the end.) cd / umount /dev/fh0 Put a new diskette in the drive: format /dev/fh0 tar cvf /dev/fh0 /usr/tmp/<CPLBUG> rm /usr/tmp/<CPLBUG> ***On 50 series station: 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
Converting Displays Problem - Unix to NT
When converting displays between UNIX and Windows NT Workstatoin 4.0, you may need to edit the display picks that contain the run command on Windows NT Workstation. If the run command
starts a script, the command must contain an sh after the run command. For example: run sh /opt/scripts/my_script Also note that the name of the script file must end in .ksh (for example, my_script.ksh).
Copy Files from one AW/WP to All Other Hosts

The following is an example script which will copy a display from the AW/WP that you are working on to every other AW/WP that is in the .rhosts file. This example script is called blow. It resides in the /usr/bin directory so that it will be in the path and can be used from any directory without a path name. It will rmount and rcp a file to all stations in the .rhosts file. DIR=`pwd` FILEDIR=`dirname $1` if [$FILEDIR = .] then FILEDIR=$DIR fi for all_args do for x in `cat /.rhosts` do 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. System management may miss heartbeats and flag them failed or the Nodebus failed. A cable test will usually fix.
Copy - unix2dos and dos2unix (50 series)

Copying files in DOS format: Format floppy (3.5) to DOS format: mount /pcfs unix2dos /dir/fn /pcfs/fn umount /pcfs eject Copying files from DOS to 50 series station: mount /pcfs dos2unix /pcfs/fn /dir/fn 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 insert target diskette dd if=/usr/tmp/disk1 of=/dev/rfh0 bs=8192 count=180 rm /usr/tmp/disk1
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 dd if=/dev/rfh0 of=/usr/tmp/disk1 bs=8192 count=150 insert target diskette dd if=/usr/tmp/disk1 of=/dev/rfh0 bs=8192 count=150 rm /usr/tmp/disk1
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
Copy From Hard Drive to Floppy
tar cvf /dev/fh0 /usr/fox/hstorian/bin/hed*.* cvf=copies rvf=appends tvf=dir of disk
Copy From Floppy to Hard Drive

tar xvf /dev/fh0 /usr/fox/hstorian/bin
Copying ASCII files to DOS diskette on 50 Series

Put in DOS formatted diskette in fd0. cd / mount /pcfs cp /usr/filename /pcfs
Copy Stamped (5.25) With One Drive Available
20 series: Stamp located in last block. dd if=/dev/rfh0 of=/usr/tmp/disk dd if=/usr/tmp/disk if=/dev/rfh0 If the Media Stamp is incorrect, see the section titled Stamp-ID Changing Incorrect in this manual.
Core Files- Reading

20 series /usr/foxbin/strings core 50 series
/usr/bin/strings core (Reads core file) By typing: file core 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.
Counters Station Block Counters
To get the Station Block counters information, where CPLBUG is the CP letterbug: omget CPLBUG_STA:STATION.PIOEFT (FT Mismatch) omget CPLBUG_STA:STATION.PIOE1R (Retries) omget CPLBUG_STA:STATION.PIOEGB (Good to bad) To reset the Station Block counters, where CPLBUG is the CP letterbug: omset b T CPLBUG_STA:STATION.PIORST 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. Some of the Station Block parameters are listed below: OMLDAV - The average CPU percentage spent on Object Manager tasks over the last 12 scans. Typically, should not exceed 30%. OMOVRN - The number of Object Manager overruns that occurred since the CP was booted or the counter was reset. IDLETM - This is the percentage of time that the main microprocessor in the CP is executing in an idle loop. This value should be at least 20% to allow tasks like alarm and I/O handling, which utilize other subsystems in the CP to occur.
MAXMEM The largest memory segment available in the CP. This largest Memory segment should be at least 10,000 bytes.
OBJECT MANAGER OVERRUNS 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.
Counters Application Sublayer Counter Thresholds

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.
Counters LAN (Network Information) -LAN Tokenbus Statistics Counters

*****This information can be found on HH960***** File: LAN Tokenbus Statistics Release: V6.2.x Date: Nov 15, 2000 Subject: LAN Tokenbus Statistics Counters Source: SD&E Carrierband LAN's and FOLAN's have a set of statistical counters which help monitor the health of the 802.4 Tokenbus. These counters represent the Primary LAN's view of the Tokenbus and are a composite
of messages heard on both the "A" or "B" cables. These counters are only reset by rebooting the LAN module. Both sides of a FT LAN must be rebooted in order to reset counters otherwise the counters read will be the Shadow's accumulated counters. Previously the only way to gather these counters was by using the mini-SMDH (remd/remv) which came with the Foxwatch scripts or by using the Lan Load Tools (pc_v42 or pc_v62). At version 6.2 the LAN image was enhanced by creating OM variables for these counters and two other counters. The OM variables are created by the Short Term Report Handler (STRH) process running in the LAN. This process will run every 30 seconds. Creating OM variables allows these counters to be read using tools such as "omget" or "oma". A display could be built which would include these OM variables but this is STRONGLY DISCOURAGED because that would create a connection to the LAN module putting an additional load on the station. I/A systems running at versions prior to V6.2.x can also get these counters by installing QF11458. The OM names are accessed by pre-pending the Letterbug Name of the LAN module to the counter root name. Example: A LAN module with a Letterbug Name of NODE04 would get the counter named <LBUG>PDUS30 and <LBUG>FDBDERR by typing: omget NODE04PDUS30 omget NODE04FDBDERR Object Manager Variables 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 EBit 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 <LBUG>FDBDERR 20 Per Hour <LBUG>OVERRUN 20 Per Hour
The LI (Lan Interface) provides both Token Bus Controller (TBC) statistics and modem counter information. These statistics and counters are updated dynamically within the LI memory space by the TBC, in its limited statistics counter mode. The TBC statistics and modem error counters cannot be reset, they are read only parameters. Also, these values are not reset upon a MAC reset or a hot remarry, they are only reset when the LI reboots. However, an LI running Single will clear the value of Non-silence whenever the value reaches or exceeds 5000. The statistics and counter values are integer vcalues and are defined as follows: Noise may be expected in some procedures of the protocol due to collisions. The Non-silence, FCS Errors, and E-Bit Error counters track the number of noise bursts detected when noise was not expected. These counters do not track expected noise bursts, only noise bursts that are due to errors or unexpected noise on the medium. 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.
Counters MAC Sublayer Counter Thresholds
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.
Counters Network Sublayer Counter Thresholds
Counters Peripheral Sublayer Counter Thresholds
Counters Station Loading Counter Information
Counters Transport Sublayer Counter Thresholds
cpio Command
To copy from tape to hard drive: cpio -ivd /usr/disp/filename < /dev/rst9 To get directory listing of tape: cpio -itv < /dev/rst9 To copy from hard drive to tape: find /usr/disp -print | cpio -o > /dev/rst9 To look on tape for certain filename: cpio -itv /usr/disp/RP* < /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] will add the file to crontab crontab -r will remove the crontab file crontab -l will list current crontab entries 20 series in /usr/lib/cron (cron.allow cron.deny must exist) Example to schedule crontab if crontab file is named somename.cron (for example) crontab somename.cron example line in crontab: 10 07 * * * /usr/fox/hstorian/bin/hpu which tells it to execute the script called hpu at 7:10 a.m. every day of every month of every year. 50 series crontab -l 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 to get crontab contents and create a file named cronit echo ; * * * * /usr/prog/myfile; >> cronit This will add /usr/prog/myfile to the new crontab file named cronit crontab cronit This is now your current crontab file.
CSA Rebuilding CSA (HH1008)
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 This will give an output as follows: Global find for process "CSA_SERVER" = 0 00 00 00 01 00 0D 49 30 30 30 30 30 31 08 00 20 A3 70 85 00 00 00 00 00 00 00 Now type the following to ensure this is the expected station: /opt/fox/bin/tools/fist APLBUG (APLBUG being your host) This will give an output as follows: Station Identifier Address (hex) Error description ----------------------------------------------------6AWE01 I000001 080020A37085 So this states that 6AWE01 is my CSA_SERVER due to the 08 00 20 A3 70 85 in the glof command matching my Address. Next thing you must have to rebuild your CSA database is a good CSA_Save. This is performed by the following set of commands: cd /usr/fox/csa mkdir save (The directory name can be other than save) CSA_Save ./save (This saves the csa files to text files) If this hangs on the control processor that is the problem the following can be done prior to a CSA_Save. cd /opt/fox/csa ls (note the directory of the bad processor) mkdir /opt/tmp (if there is not an opt/tmp already) cp -rp LTRBUG /opt/tmp (this copies files for this processor) rm -r LTRBUG (this removes the database that is corrupted) 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 (Notice the line like the following) root 1826 1 0 16:58:06 ? 0:35 /usr/fox/csa/CSA_SERVER kill the process using the PID number from the second column of the line with CSA_SERVER. kill 1826 cd /opt/fox/csa cp -rp ./* /opt/tmp (This copies all files to directory /opt/tmp) rm -r *
(This now empties CSA database) cd /opt/tmp cp -p BPARM_DEF* /opt/fox/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 (you should see the following) BPARM_DEF.dat CMPD_INDEX.dat STN_INDEX.dat drivers.chk foxblock.lic BPARM_DEF.idx CMPD_INDEX.idx STN_INDEX.idx drivers.lic Load CSA back into the system by doing the following. cd /usr/fox/csa CSA_Merge ./save (This restores the CSA database) Output will look like the following: Merge of CSA information for 6CP101 completed Merge of CSA information for 6CP302 completed Merge of CSA information for 6CP401 completed Merge of CSA information for 6CP402 completed Merge of CSA information for 6CP40B completed Merge of CSA information for 6CP601 completed Merge of CSA information for 6CP602 completed Merge of CSA information for volwrk completed CSA merge completed CSA is rebuilt !! CSA is complete except for the database of the station that was corrupted. This station needs to be initialized and rebooted and a loadall done on this station that caused the corruption to have the CSA database complete.
CSA Removing Entries from CSA

(Please dont try this at home) To remove entries for CPLBUG in CSA: csa_fn reset CPLBUG
Daylight Savings Time Issues - Setting time back

(see latest Daylight Savings Time customer advisory for more information) (The following information taken from Customer Advisory 2001015_5abi) Systems running on the Windows based platforms will not experience this issue. Setting system time forward does not result in problems with the system or applications, or loss of data. Users running historical data collection applications like AIM* or the I/A Series legacy Historian on either the Solaris or Windows platforms, will experience issues with data collection and a lack of on-screen data updates within these applications for a period equaling the length of time that the system time is set back. The following contains information on what can be done to work around the issues resulting from setting the system time back, see the Workaround section below. We are also publishing this advisory to advise you of 2 new Quick Fixes that will correct time related issues with the FoxView/FoxDraw V9.0 and V9.0.1 running on Solaris stations. In order to apply this Quick Fix, you will need to have previously installed FoxView/FoxDraw V9.0 or V9.0.1. Quick Fix 1007522 applies to stations running FoxView/FoxDraw 9.0 while Quick Fix 1005815 applies to stations running FoxView/FoxDraw 9.0.1. The Quick Fixes are available for download on the Invensys CSC web site, http://ips.csc.invensys.com. If you are at a FoxView/FoxDraw version prior to 9.0, please contact your local Service Representative to determine the terms for upgrading to V9.0.1. For those users who do not apply the Quick Fix for FoxView/FoxDraw, or have other Motif applications, the Customer Advisory contains information on what can be done to work around the issues resulting from setting the system time back in time. Users running historical data collection
applications like AIM* or the I/A Series legacy Historian on either the Solaris or Windows platforms, will experience issues with data collection for the period that the system time was set back. The most noticeable symptom is a lack of on-screen data updates within these applications for a period equaling the length of time that the system time was set back. Display Manager - The legacy Display Manager (DM) users will not experience these issues.
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: o -u print local unresolved linkages o -r print remote linkages o -s print summary of the application (period & phase) o -p print block names with period/phase o -l print block names with secured input(s)/secured linkage o -b print block names with bad data type(s)/bad input o -t print details: parameters, linkages, BPC o -T print the same as -t except light difference in lines with block names to easy file compare o -d report station parameters relating to CP loading, alarm devices, and supervisory control o -e compound block errors o -C Checkpoint filename /usr/fox/bin/tools/dbvu Run by itself will give argument screen. The block equiv. calculation in dbvu is not accurate. To document ECB blocks: /usr/fox/bin/tools/dbvu -t DB[CPLBUG].UC ECB on CP10s and Gateways use dbvu on CP30s run dbvu30 on CP40s run dbvu40 (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
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 A brief command description can be generated by: dbvu_err h 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 **(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
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 (dumps ASCII overview.dmp lists connections - vi to change) d_edit -upload filename (will update and re-install graphic called filename from the .dmp file) /usr/fox/bin/tools/d_edit -l filename (lists all connections) /usr/fox/bin/tools/d_edit -I filename (will ask for connection number to change - q quits and reinstalls. d_edit -l filename | grep FI (lists all FIs in the flows display) The following is a GREAT script using d_edit50 (which you can substitute d_edit) which when executed with the syntax below, will allow you to vi the display file and then upload it when it is finished. This is used to edit a display file in ascii format without having to do the dump and upload which the script will do for you. Great for making those minor search and replace changes. This script is named editdisp (you can name it whatever you choose). for x in $* do if [-f $x]
fi done
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!!!
Syntax: editdisp displayname To verify connections on displays: d_edit x <displayname> & .. To check the progress of the above command: tail f /usr/tmp/d_edit.log ..
d_edit - Search and Replace
A single connection attribute can be substituted within a single connection or multiple connections with one or more display files. One type of substitution per command line is allowed. You cannot change path names, deltas and access levels within the same d_edit command line. Syntax: d_edit [-g group_name] -[m[n]]AacdfmtT /[[search/]match/]replace/<filespec> -A Action name (name used in pick command) -a access level -c path name of connection -d delta value -f numeric format for contents < real connection -m momentary contact pulse function -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).
Determining Device Monitor Master

cd /opt/fox/bin/tools (for 50s and /usr for 20s) glof p DEV_MONITOR (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.
Forcing it to Change Its Master Determine who the master is, delete the current master: glof p DEV_MONITOR /opt/fox/bin/tools/fist LID run fist on all stations to determine master. omdel p DEV_MONITOR on the master find the pid of cs_devmon and kill it, then restart the cs_devmon process. ps eaf | grep cs_devmon Requesting Device Monitor Master to Initialize cd /usr/fox/cs (ap20/pw) cd /usr/fox/exten (pre v4.2) cd /usr/fox/cs (4.2) dm_recon d 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. Disabling and Removing - AP20 procedure: ps eaf | grep cs_devmon (get pid of cs_devmon). kill 9 pid cd /usr/fox/bin/tools omdel p DEV_MONITOR (delete shared object). cd /usr/fox/cs mv cs_devmon cs_devmon.old (prevent restart on reboot). Model 50 Station Procedure: ps aux | grep cs_devmon (get pid of cs_devmon). kill 9 pid cd /opt/fox/bin/tools omdel p DEV_MONITOR (delete shared object). cd /usr/fox/cs mv cs_devmon.cfg cs_devmon.cfg.old (prevent restart on reboot). Model 51 Station Procedure: ps eaf | grep cs_devmon (get pid of cs_devmon) kill 9 pid cd /opt/fox/bin/tools omdel p DEV_MONITOR (delete shared object). cd /usr/fox/cs mv cs_devmon.c fg cs_devmon.cfg.old (prevent restart on reboot).
Device Monitor disabling

AP20 Termination: ps ef | grep cs_devmon kill 9 pid cd /usr/fox/bin/tools omdel p DEV_MONITOR cd /usr/fox/cs
mv cs_devmon cs_devmon.old 50 SERIES Termination: ps aux | grep cs_devmon (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. The 3rd # is the disk or LUN number. The 4th # is the slice/partition number. The controller numbers would be c0 or c1. The target address would be t3 for a SPARC system and t0 for an Ultra system. The disk number is also known as the logical unit number (LUN) and is always set to d0 for any embedded SCSI device. The slice numbers range from 0 to 7 and are the partitions. The following is an example of the slices: s0 = / (root) s1 = swap area s2 = address of whole disk s3 = metadevice database area s4 = /var s5 = INFORMIX raw database area s6 = /usr s7 = /opt To address the root partition of a SPARC machine, the address would be as follows: /dev/dsk/c0t3d0s0 To address the root partition of an ULTRA machine the address would be as follows: /dev/dsk/c0t0d0s0 Foxboro uses another naming convention and the relationship is as follows: Foxboro Name Sun Microsystems Name /dev/sd0a /dev/dsk/c0t3d0s0 /dev/sd0b /dev/dsk/c0t3d0s1 /dev/sd0c /dev/dsk/c0t3d0s2 /dev/sd0d /dev/dsk/c0t3d0s3
/dev/sd0e /dev/dsk/c0t3d0s4 /dev/sd0f /dev/dsk/c0t3d0s5 /dev/sd0g /dev/dsk/c0t3d0s6 /dev/sd0h /dev/dsk/c0t3d0s7 The AWs use the Metadevice address to access the drives which are as follows: /dev/md/dsk/d0 = / (root) /dev/md/dsk/d1 = swap /dev/md/dsk/d2 = /var /dev/md/dsk/d3 = INFORMIX /dev/md/dsk/d4 = /usr /dev/md/dsk/d5 = /opt 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> df command
Identifies the device name associated with specified file system such as /usr, /opt, etc.
df -t on a 20 series station reports number of free blocks /bin/df on 50 stations df -k -F ufs on 51 stations 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
diff - file comparison utility
Usage: diff [-bitw] [-c | -e | -f | -h | -n] fname1 fname2 diff [-bitw] [-Cnumber] fname1 fname2 diff [-bitw] [-Dstring] fname1 fname2 diff [-bitw] [-c | -e | -f | -h | -n] [-l][-r][-s][-Sname] dir1 dir2 diff[options] file1 file2 diff[diroptions] dir1 dir2 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 ignore blank spaces and tabs -cn produce n lines of context -e produce a script of commands -f produce a scr. not in rev ord. -h perform the compare quickly -I ignore case of letters -n ignore all blanks -t expand tab characters -C num list of diff w/num lines of text -n produce script in opposite ord. -D string (creates merged version of f1 and f2) Dir options: -l long output format -r recursive for common subdrs -s report files that are identical -Sfile begin dir. comp. with file
diff3 3-way file comparison
This command reports 3-way differential file comparison. Usage: diff3 [-exEX3] fname1 fname2 fname3 For further instructions, type: man diff3
dircmp directory compare

This command reports directory differences. Syntax: dircmp [-d] [-s] [-wn] dir1 dir2 If no option entered, a list is output indicating whether the file names common to both direcytories 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.
Disk Space Issues
Acceptable Levels of Disk Space: AP20/PWs 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. Determining the problem directory/file that has filled the partition: 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) 2) 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 Sort lines in report by size, in reverse order. cd /usr sort n r +0 list > list1 Look for non-familiar names at the beginning of the list, or abnormal size. more list1
Recommended ways to free disk space.. delete unwanted core files; see find command to help locate the core files. 2. UUCP is located in /var/mail and /var/cron and is an incremental log file that grows on 50 series stations. crontab -r uucp echo > /var/cron/log rm /var/mail/uucp This procedure deletes UUCP, deflates the log file and stops crontab from writing to that file. 3. 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 4. 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. 5. /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. 6. 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. 7. 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 8. Look in /var/adm/messages. Some of these older messages can be deleted. (These messages are report of all messages during station bootup. 9. 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. 10. 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. 11. Check in /opt/fox/rpt_wrt/rpt_run to see if there are old report writer reports that can be deleted. 12. 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. 13. 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. 14. 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. 15. 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. 16. Use the du command to find what directories are using the most space. 17. 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. 18. 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.
Display Manager or Foxview How to Invoke
If youre running Display Manager and want to change to Foxview: cd /usr/fox/wp/bin/tools use_foxview.sh Then reboot the station. If youre running Foxview and want to change to Display Manager: cd /usr/fox/wp/bin/tools use_displaymanager.sh Then reboot the station.
Display Manager Install Files
See Alarm Manager Install Files in this manual.
Display Managers Quitting Display Managers that are not quittable
From VT100: pref DM0000 dmcmd quitdm on; exit (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" restart first head csh setenv DISPLAY W23A02:0.0 nohup /usr/fox/wp/bin/dm_wp50 -alias W23A02 >/dev/null & to kill second head pref -W23A22 DMCMD "dmcmd dmexit" restart second head csh setenv DISPLAY W23A02:0.1
nohup /usr/fox/wp/bin/dm_wp50 -alias W23A02 >/dev/null &
Display Manager Starting Manually

setenv DISPLAY AW0001:0.0 nohup /usr/fox/wp/bin/dm_wp50 alias DM0001 > /dev/null & (Where AW0001 is the letterbug of the station and DM0001 is the Display Manager Name)
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: To list reduction group configuration: dmpcfg r To list reduction group configuration as well as operations and member points: dmpcfg rom To list collection point configuration: dmpcfg c
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
DNBI blink codes
One green blink: Serial port cable is not connected or is inactive. Two green blinks: AUI cable is not c onnected or is inactive. Three green blinks: Jabber timeout has occurred.
doscopy Command
doscopy filename dos!a: (wildcards are allowed) doscopy -b filename dos!a: (for binary files) doscopy -a filename dos!a: (for ASCII files) doscopy -r directory dos!a: (copies subdirectories)
DOS Files - Copying Into Venix (20 series)

Syntax: doscopy dos!a:fname.ext doscopy -b dos!a:os1uc /usr/fox/sp/files/os1uc (keeps same name into current directory) doscopy -a dos!a:printers /etc (copies printers to /etc directory) doscopy -r dos!a:/wp/helpfiles /usr/help
DOS Files - Viewing On Disk In Drive 0 on 20 Series Stations

dosdir dos!a: dosdir dos!a:/dos/help
Drivers - Rebuilding Device Drivers (Print Devices - LPXX)
AP20/PWs Example: /dev/LP13 has a size of 23979 /usr/lib/lpshut ls li /dev/LP13 mknod LP13 c 23 13 chown lp LP13 chgrp sys LP13 /usr/lib/lpsched 50 Stations 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.
Drivers - Drivers not built for DAT tape drive on bootup
Sometimes drivers are not built for the tape drives and an error will be received stating that the file system is full while trying to do a tape backup. When doing a tape backup on the 51 stations, the file nrst9 will be created and can 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 reboot machine with boot -rs /usr/sbin/drvconfig /usr/sbin/devlinks /usr/sbin/disks /usr/sbin/tapes /usr/sbin/ucblinks 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 This method used on AW51E: boot cdrom cd /devices/pci*/scsi@3 ln st@5,0:lb /tmp/rst9
cd /cdrom cp restore_8MM /tmp cd /tmp vi restore_8MM Toward bottom change TAPE device from /dev/rst9 to /tmp/rst9 /tmp/restore_8MM if doing a level 0 dump, substitute dmp0_8MM for the restore script above.
Drivers Verifying Software Driver for the Tape Device
Issue the mt command to access the tape drive status. mt f /dev/rst9 status 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 add a new major number to name -d debug. Print out devices it has found. -a alias_name add the alias_name to list of aliases that this driver is known by. -c class_name added driver exports class_name -i filename only configure the devices for drivers named in filename. -m major_num specify major number for this driver -r rootdir build device tree under specified directory.
dtree Command
dtree to see directory tree
du Command
Disk Usage Syntax: du [-asrk] [name] -a generate output line -s give grand total only -r give msg about dirs. that cant be read -k print allocation in kilobytes AP20/PWs cd / du s * | more (This will give files and directories in 512 byte blocks) 50 Stations cd / du s * | more (This will give files and directories in kblocks) 51 Stations cd / du sk * | more (This will give files and directories in kblocks)
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. 1) An Additional Display Manager (AADM7) must be configured in System Definition. 2) 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 3) Write a script called 2nd_fv in /usr/fox/wp/data if [ $DMNAME = $GCLBUG ] then /opt/fox/wp/foxview/foxview.exe else exit fi 4) 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 5) 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. 6) 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". 7) Shutdown and reboot.
Dump Files - Location
Dump files are created on reboot of stations: /usr/fox/sysmgm/softmgr/dump/LBUG.0 (LBUG.1, LBUG.2, etc.) These files should be removed because of the hard disk space they consume.
ECB - Equipment Control Blocks

ECBP ECB11 ECB1 ECB2 ECB4 ECB5 ECB6 ECB7 ECB8 ECB9 ECB11 ECB12 ECB13 ECB14 ECB15 ECB16 ECB18 ECB19 ECB21 ECB22
Primary ECB Primary ECB Analog Input Analog Input and Analog Output Pulse In and Analog Output Digital In, Sustained/Momentary, and Digital Out Sequence of Events Input Digital In and Pulse Count Input Ladder Logic or DC Out/Validated Input Remote/Manual Station (Analog I/O, Digital I/O) Reserved for Primary FBM (ECBP) Intelligent Transmitter 2 Interface (Parent) Hydrostatic Tank Gauge Panel Mounted Display Allen-Bradley Programmable Logic Controller Modicon Programmable Logic Controller Intelligent Transmitter 2 (Child) 760 MICRO Controller 761 MICRO Controller Mass Flow Transmitter (Coriolis)
ECB23 ECB34 ECB36 ECB38R ECB39 ECB41 ECB42 ECB43 ECB44 ECB46 ECB47 ECB52 ECB53 ECB80 ECB81 ECB200 ECB200 ECB201 ECB202
Intelligent Transmitter 2 Interface (Parent) MDACT Feedback Lag Tristate MDACT Pulse Width Tristate Intelligent Transmitter 2 Interface (Red Parent) AMSPRI Gas Chromatograph Analog Input FBC Digital Input FBC Analog Output FBC Digital Output FBC Digital Input/Digital Output FBC FBP10 Interface to Cluster I/O (Parent) DPIDA Controller Analog Output Port ECB C50 RTU Intelligent Transmitter Foundation Fieldbus H1 Interface Profibus Application Foundation Fieldbus H1 Device Redundant DCI Fbm Interface
EEPROM/NVRAM parameters for 50 series stations
These parameters must be changed to reflect a new terminal configuration (i.e., AW to AP). To change a 50 series AP to an AW or WP, the output-device and input-device NVRAM parameters must be changed to reflect the new terminal configuration. Default EEPROM parameters can be found for each station listed in the EEPROM Information section of any SAR. Changing AP NVRAM parameters to AW/WP NVRAM parameters: 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 To set the eeprom parameters: setenv input-device keyboard setenv output-device screen 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 setenv output-device ttyb Method 2 eeprom input-device=ttyb eeprom output-device=ttyb
Resetting EEPROM/NVRAM parameters for 50 series stations
The following instructions are for pre-51F(P79) and pre-51G(P80) stations. To reset the EEPROM/NVRAM parameters, press Stop/N and hold until the boot process starts. You will then need to reset some of the EEPROM parameters as stated in the 51 processors section of the Foxwatch reports.
Example: AW51 EEPROM parameters were incorrectly set while trying to make it an AP51. At this point, theres no interface into the AW. You must reset it as stated above. It must be hooked up to the monitor (not Wyse) with Alpha Numeric keyboard attached (because this one is an AW). Restoring NVRAM To Default Settings On 51F and 51G Stations (HH1033) 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. 2. 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. 3. 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. 4. 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 5. 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. 6. 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 1 1 pci-probe-list 7, c 3, 8, d, 13, 5 7, c, 3, 8, d, 5, 13 Setenv Example: setenv diag-switch? true <RET>
ERROR received trying to enter a station in the Control Configurator
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.
ERROR - Cannot Communicate With Server

Above error received while scheduling reduction groups: Turn historian off then on again.
ERROR System Monitor Not Responding
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) (kill system monitor) nohup /usr/fox/sysmgm/sysmon/smon_ech & (restart system monitor) ps -el | grep smon will show them running
Error Received While Performing Shrink
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.
ERROR - Invalid File Header

cd /usr/disp cp overlay filename.dwf /usr/foxbin/bpatch filename.dwf h d0f0 then press backspace w q (d0f0 should be first two bytes of the display file)
ERROR - SP Error - Lck_Chkpt Failed
on AP20 cd /usr/diskless/WPLBUG rm rmnttab touch rmnttab chmod 666 rmnttab on 51 stations 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: 1) 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 2) 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). 3) 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. 4) Execute the command "/usr/fox/bin/rem_stop WPLBUG" where WPLBUG is the letterbug of the failed WP. 5) 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.
ERROR - Checkpoint Unsuccessful
For checkpoint error, one solution is as follows, which is copying the backup checkpoint file to the current checkpoint file (use with CAUTION!). /usr/fox/sp/files/contains 3 files: DBUCE001.init, DBUCE001.UC, BBUCE001.UC cp BBUCE001.UC DBUCE001.UC
ERROR - Checkpoint type 5; class 8; code -24 Failed

When trying to do a checkpoint in all CPs this message received when /usr area on hard drive has filled up. Need to delete some files and try again. /usr area should not be less than about 8000 blocks on an AP20/PW.
ERROR - Parameter Version Check Failed
When trying to loadall compounds from diskette onto a CP. mount /dev/fh0 /f0 cd /f0 lc cd COMPOUND_NAME /usr/foxbin/strings parameters | more (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
ERROR received doing a Load-All
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
Logical host of WP50/WP51 Logical names of all APs & PCs Letterbugs of all Control stations and gateways Names of all historians Historian names and letterbug of host Library volumes names List of names and types of printers Logical name of WPs
FBM Types And Part Numbers Legacy
FBM01 0-20 mA Input P0400DA FBM02 Thermocouple/mV Input P0400YC FBM03 RTD Input P0400YD FBM04 0-20 mA Input/Output P0400YE FBM05 Redundant Input/Output 0-20 mA P0400YF FBM06 Pulse Input 0-20 mA Out P0400YG FBM07 Contact/dc Input CM400YH FBM08 120 Vac Input DM400YJ
FBM09 Contact/dc Input/Output CM400YK FBM10 120 Vac Input/Output DM400YL FBM11 240 Vac Input/Output CM400YM FBM12 Contact/dc Input Expander CM400YN FBM13 120 Vac Expander Input DM400YP FBM14 Contact/dc Expander In/Out CM400YQ FBM15 120 Vac Input/Output Expander DM400YR FBM16 240 Vac Input/Output Expander CM400YS FBM17 0-10 Vdc, Contact/dc Input/Output DM400YT FBM18 Intelligent Transmitter P0400YV FBM20 240 Vac Input CM700QV FBM21 240 Vac Input Expander CM700TW FBM22 Auto/Man Station Int. P0900HS FBM24 125 Vdc Input DM900HT FBM25 125 Vdc Input Expander DM900NX FBM26 125 Vdc Input/Output DM900HU FBM27 125 Vdc Input/Output Expander DM900NY FBM33 Copper RTD Input P0912MJ FBM36 Modified FBM02 - Calted Range 0-21.1 mV P0915DX FBM37 0-20 mA Output Interface Module P0915FC FBM39 Intelligent Xmit Input/0-20 mA Output P0902UT FBM41 Contact/dc Input/High Current dc Output P0902XA FBM42 Cont/dc Input/High Current dc Out Expder P0902XB FBM43 Dualbaud Intelligent Transmitter P0950BM FBM44 Dualbaud Intelligent Transmit Int/0-20 Out P0950BN FBM46 Redundant Intelligent Transmt In/0-20 Out P0950DA
FBM(200 Series) and FCM Types/Part Numbers

FBM201 Channel Isolated 8 Input 0-20 mA P0914SQ FBM202 Channel Isolated 8 Input Thermocouple/mV P0914ST FBM203 Chan Isolated 8 Input RTD P0914SV FBM204 4 Chan 0-20 Input + 4 Chanel 0-20 Output P0914SY FBM205 Redundant 0-20 Combo Module P0914XG FBM206 Channel Isolated 8 Input Pulse P0916CQ FBM207 Chan Isolated 16 Din Voltage Monitor P0914TD FBM207b Chan Isolated 16 Din 24 Vdc Contact Sense P0914WH FBM207c Chan Isolated 16 Din 48 Vdc Contact Sense P0917GY FBM211 Differential 16 Input 0-20 mA P0914TN FBM212 Differential 14 Input Thermocouple/mV P0914XL FBM213 Differential 8 Input RTD P0914XN FBM217 Din Volt Monitor - 32 Channel P0914TR FBM219 Group Isolated Discrete Input/Output P0916RH FBM220 1 Port, H1 Foundation Fieldbus P0917HA FBM221 4 Port, H1 Foundation Fieldbus P0917HB FBM237 Channel Isolated 8 Output 0-20 mA P0914XS FBM241 Chan Isolated Vmon DI + External Source P0914TG FBM241B Chanel Isolated Vmon DI + Internal Source P0914WK FBM241C Chan Isolated CSense DI + External Source P0914WM FBM241D Chan Isolted CSense DI + Internal Source P0914WP FBM242 Channel Isolated External Source DO P0916TA FBM243 8 FoxCom Channels P0914TK FBM246 Redundant, 8 FoxCom Channels P0917XN FCM10E Fieldbus Communications Module P0914YM FCM10Ef 2KM Fieldbus Communications Module P0916CP FCM2f 10KM Fiber Optic Fieldbus Extender P0916TQ FCM2f 2KM Fiber Optic Fieldbus Extender P0914YZ FCM2f4 4KM Fiber Optic Fieldbus Extender P0917JA
File System - Creating New On 50 Series diskette

fdformat newfs /dev/fd0 mount /dev/fd0 /f0 rmdir /f0/lost+found umount /dev/fd0
File System - Creating New On Extended Historian Drive (AP20)

mkfs /dev/shd5.hstor 156360:15636 mount /dev/shd5.hstor /u0 df -t /u0 156360:15632 /usr/fox/hstorian/bin/stop
File Types
Usage: file [-c][-h][-f ffile][-m mfile] file -c check magic file for errors -h do not follow symbolic links -f ffile ffilename contains names of files to be examined -m mfile mfilename as an alternate magic file instead of /etc/magic file filename shows file type of filename file * shows file types of all files in a directory
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: find / -fstype urfs -prune -o -size +2000 -print (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 (to timestamp the file) find / -newer filename -print (to find any files newer than the timestamp on filename) More uses of the find command: To find files r* that are over 90 days old: find . mtime +90 name r* print Or to find all files that are over 90 days old: find . mtime +90 print To remove files that are over 90 days old: find . mtime +90 exec rm f {} \; To start at root and remove core named files: find / -name core exec rm {} \;
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>
Floppy Device Issues on P80 and P81 Stations

Issue 1: 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? Solution1: 1) Connect the USB floppy drive to the left bottom front USB connector. 2) Open a VT100 window and change to the /usr/local directory. 3) Run the fox_mklink script, you should see the message: USB Floppy drive Connected to c1t0dos0 Or USB Floppy drive Connected to c2t0dos0 4) Now, you could use the alias fd0 or rfd0 for the usb floppy device. 5) Issue 2 Can I format the floppy and put a DOS partition on it? Solution 2 The best procedure is to format the floppy on a PC running OS Windows. However if you want to do it on the P81, you could do the following: A) Format a floppy device. rmformat -Flong /dev/fd0 Or modify the script /usr/bin/fdformat as follows: /usr/bin/rmformat -Flong /dev/rfd0 B) Create 1.4 Mb file system. mkfs -F pcfs -o nofdisk,size=2880 /dev/rfd0 The above procedure creates a formatted DOS floppy diskette; however it cannot be mount on an AW51 with Solaris 2.5.1. Issue 3 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 text1.txt text2.txt text3.txt text4.txt Solaris 8 Mounting a DOS diskette with out the foldcase option and listing its contents: mount -F pcfs /dev/fd0 /pcfs ls /pcfs TEXT1.txt TEXT2.TXT TEXT3.txt TExt4.txt
Mounting a DOS diskette with the foldcase option and listing its contents: mount -F pcfs -o foldcase /dev/fd0 /pcfs ls /pcfs text1.txt text2.txt text3.txt text4.txt
Fonts Restoring a custom font/marker file
DO NOT TAR IN THE ENTIRE /USR/FOX/WP/FONTS DIRECTORY. YOU MUST ONLY USE THE FONT FILE THAT YOU CUSTOMIZED (i.e., /usr/fox/wp/fonts/usr_mkr.bdf). Also, do not put extra files in the directory such as a usr_mkr.bak because it will cause many problems with the install fonts routine. 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. 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 You must now restart the Display Manager.
format command 50 series
By typing format at a VT100 window or when booted on the cdrom, you will be asked to select which disk to inquire about. Select the disk number (i.e., 0 or 1, etc.). The format command enables you to format, label, repair, and analyze disks on your system. -f command-file -l log-file -x data-file -d disk-name -t disk-type -p partition-name -e enable SCSI expert menu -s silent -m enable extended messages -M enable extended and diagnostic messages
Format Floppy
(20 series) format /dev/fh0 (50 series) fdformat -e ( -e switch ejects the floppy when done formatting) fdformat -d ( -d formats the floppy in DOS format)
Form Feed IN Ace Reports
(AP20) echo `\f` > /dev/LP01 f for form feed, n for new line, t for tab (AP/AW51) echo ^L > /dev/LP01
FoxAPI Problems with ADDE6
The ADDE6 package can cause problems when assigned to a station in system definition. When ADDE6 (FoxAPI for Solaris) is added to a station it causes an addition to the fox_apps.dat file during install. This addition is a request to start FoxAPI. By default there is already an entry in fox_apps.dat named FoxAPI which will also start FoxAPI. A problem can exist where two instances of FoxAPI can get started causing problems with processes and lists and data retrieval. DO NOT ASSIGN ADDE6 package to stations.
FoxAPI Viewing Data Sets and Values

To see the sets and data within using foxtst : cd /opt/fox/ais/bin foxtst 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: foxspy 913 (will select option 900, then 13) To determine the version of FoxAPI: cd /opt/fox/ais/bin foxtst 1200 29
FoxDraw Connecting to Server
Windows NT FoxDraw uses an_init.cfg out of c:\winnt instead of /opt/fox/wp/FoxDraw. 51 Series Stations an_init.cfg is located in /opt/fox/wp/FoxDraw. The following is an example an_init.cfg that is configured for support of an AIM* AT Server and a FoxDraw Server. [AISnet] ; In this section you should change the APNT01 to your real ; machine name. Keep all parameters as they are. The only two parameters ; you might need is Printerr and tracelevel. These are used for debugging. ; Printerr takes 0 or 1 or 2 ; tracelevel takes 0 or 1 ; these two parameters will generate a file with .log extension to show ; the history of the connection and provide some debugging capability. ; Printerr = 0 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.
FoxSelect Problem FoxSelect Dies When Turning Compound On or Off.
We have experienced a problem at times using FoxSelect. When a compound is selected and turned on or off, FoxSelect dies. The problem is that FoxSelect gets corrupted and some .DAT and .INI files are created. cd /opt/fox/wp/FoxSelect 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 /opt/fox/env if no entry found. Can lead to customer editing /opt/fox/env and never seeing the result. Foxview Environment Passwords: /usr/fox/wp/bin/tools/dmsepass Operator.env -p password /usr/fox/wp/data/dmpasswd_cfg Foxview Display Manager Files: /usr/fox/wp/data/ init.user wp51.cmds wp51_glbls etc. /usr/fox/customer/hi/dmcfg
Alarming: /usr/fox/alarms WPLNAMEAApan WPLNAMEAAtab horn.cfg commgrp.cfg Alarm Manager: /usr/fox/customer/alarms/cfg/am_def.cfg (use DispAlarm cfg) Control: /opt/fox/ciocfg workfile, etc. /usr/fox/sp/files checkpoint, comex bin, etc. /opt/fox/csa csa files 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)
Foxview Problem Selecting item on Foxview causes Foxview to crash
This problem was seen to occur on some installations of pre-v9.x Fv/Fd. The following files do not get installed on occasion when installing Foxview/FoxDraw. The files can be copied from another WP or AW of the same style box (51D, 51E, etc.). cd /usr/fox/wp/data ls l dsp* The following files should appear in the list: dspblock.dat dsppdef.dat If these files are not in that directory, copy them from another station.
Foxview Problem Cannot open a Foxview; Foxview crashes when trying to open
When booting the AW51 or WP51 a problem occurs where Foxview is trying to open but crashes and a Foxview cannot be manually started. After reinstalling Foxview and the problem continued, the problem turned out to be files missing from the environment directory. The customer set the Foxview environment directory to be /opt/customer/env in one of the initialization files in /usr/fox/wp/bin/tools. Since we were using a newer version of Foxview, the default Foxview environment directory is /opt/fox/env. After copying files from the /opt/fox/customer/env directory to the /opt/fox/env directory, the station was able to call up a Foxview. By copying the files to the /opt/fox/env directory, we were able to prevent this from happening in the future.
Foxwatch Report Common Error Messages

The following are error messages commonly seen on Foxwatch Reports. "NFS getattr failed for server variable: RPC: Timed out" ("NFS read failed" often appears with this message) 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.)
frev - To Get Revision Levels Information
Use frev to find the firmware revision of all stations and ECBs that contain an EEPROM. Usage on AP20: /usr/fox/bin/tools/frev SYSMN1 Usage on AP50/51: /opt/fox/bin/tools/frev SYSMN1 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.
fsdb - (file on commit disk)
The file determines type of nodebus configured. The number after the station letterbug indicates the type of nodebus. 0=nodebus node 1=standalone 2=mixed nodebus node 3=ethernet node
ftp (file transfer protocol) on 50 Series Station
ftp [-dgintv] [hostname] 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 (will change to binary mode) put file2 (To send file2 to the remote station) asc (will change to ascii mode) put file1 (To send file1 to the remote station)
(get instead of put will get file from remote station) Note: Typing help at the ftp> prompt will give you a list of available commands. The following commands can be specified to the command interpreter: *ascii *binary *bye *cd remote-directory *close *get remote-file [ local-file ] Set the representation type to network ASCII. This is the default type. Set the representation type to image. Terminate the FTP session with the remote server and exit ftp Change the working directory on the remote machine to remote-directory. Terminate the FTP session with the remote server, and exit. Retrieve the remote-file and store it on the local machine. If the local file name is not specified, it is given the same name it has on the remote machine, subject to alteration by the current case, ntrans, and nmap settings. The current settings for representation type, file structure, and transfer mode are used while transferring the file. Change the working directory on the local machine. If no directory is specified, the user's home directory is used. Print an abbreviated listing of the contents of a directory on the remote machine. If remote directory is left unspecified, the current working directory is used. Expand the remote-files on the remote machine and do a get for each file name thus produced Files are transferred into the local working directory, which can be changed with lcd directory; new local directories can be created with mkdir command. Expand wild cards in the list of local files given as arguments and do a put for each file in the resulting list. Establish a connection to the specified host FTP server. Store a local file on the remote machine. If remote file is left unspecified, the local file name is used.
*lcd *ls
*mget
*mput *open *put
fuser (find user)
Identifies the process Ids of the processes that are using the files or remote resources specified as arguments. For example, fuser c /rem/r0 shows the process using remote mount /rem/r0.
fxedit - Used on NT instead of bpatch GCIO adding to 51F (P79) station
There is no bpatch on NT stations, you must use fxedit.exe located in c:\tools.
1) HARDWARE INSTALLATION 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 B0400QMA, 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 lrwxrwxrwx 1 root root 51 Sep 7 13:51 a000 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a000,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a001 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a001,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a002 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a002,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a003 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a003,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a004 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a004,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a005 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a005,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a006 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a006,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a007 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a007,term lrwxrwxrwx 1 root other 43 Aug 31 11:20 c -> ../../devices/pci@1f,0/isa@7/serial@0,3f8:a lrwxrwxrwx 1 root other 43 Aug 31 11:20 d -> ../../devices/pci@1f,0/isa@7/serial@0,2e8:b lrwxrwxrwx 1 root root 51 Aug 31 11:10 a -> ../../devices/pci@8,700000/ebus@5/serial@1,400000:a lrwxrwxrwx 1 root root 51 Aug 31 11:10 b -> ../../devices/pci@8,700000/ebus@5/serial@1,400000:b Same files are listed for /dev/cua 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 Pass the Committal diskette using "Install_AW" Check log files and reboot the box 4) VERIFICATIONS 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. ======================================================= B0400QM Rev A 1. Read Me First 23 Preliminary June 23, 2003 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.
getpars and ucsaq utilities
The almost unknown 'getpars' and 'ucsaq' utilities can be used to create different types of report. A) 'ucsaq' creates a report of just: CPLBUG - COMPOUND - BLOCK - BLKTYPE, but it does it from all CPs and Gateways in the system. The data comes from the CSA database. cd /opt/fox/ciocfg/ifdenv ucsaq > z (wait until you get prompt back) (it might take longer if you have a lot of CPs) more z 4CP401 103X_TK AVAIL_CALC CALC 4CP401 103X_TK BYPASS IND 4CP401 103X_TK DEP_SEQ1 STRING The 4 columns correspond to: CPLBUG COMPOUND BLOCK BLKTYPE Remember to remove output files after. B) 'getpars' can create more detailed reports, including values of most parameters. The general format for 'getpars' to get Compound parameters is: getpars -Ucpname -Ccmpdname -pcompound_Parameter:%...
The general format for 'getpars' to get Blocks parameters is: getpars -Ucpname -Ccmpdname -tblocktype -Bblockname -mBLK_PARAM:%... 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 t 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 Page 100 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 1a: 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 Wed Jun 2 17:00:48 2004 BLOCK-NAME CMPNM CP TYPE DESCRP STATION 4CP401_STA 4CP401 STA PRIMARY_ECB 4CP401_ECB 4CP401 ECBP U64001 4CP401_ECB 4CP401 ECB48R UCM_64 MAIN FBP U64102 4CP401_ECB 4CP401 ECB45 UCM64 NEST_1 SLOT_2, 2-I/O 1b: To create a report for a group of CP's with similar names, like: 4CP401, 4CP402, 4CP403, etc getpars -U4CP40\* -n -mCMPNM:%15s -mCP:%7s -mTYPE:%7s mDESCRP:%32s > z 1c: To create a report for an specific CP, like: 4CP401 getpars -U4CP401 -n -mCMPNM:%15s -mCP:%7s mTYPE:%7s mDESCRP:%32s > z Example 2: REPORT OF SOME CRITICAL PARAMETERS You might find this report useful to verify current values of important parameters like FSENAB, INITMA, etc, before an online CP reboot. Note: If a PID blocks has INITMA=0, it will come up in MANUAL after reboot. cd /opt/fox/bin/tools getpars -n -mCP:%7s -mCMPNM:%14s mTYPE:%7s -mINITMA:%ld mFSENAB:%2d > z more z Wed Jun 2 17:30:16 2004 BLOCK-NAME CP CMPNM TYPE INITMA FSENAB STATION 3CP101 3CP101_STA STA NA NA PRIMARY_ECB 3CP101 3CP101_ECB ECBP NA NA ...
Control Processor 4OM201 not accessible. Control Processor CP3000 not accessible. Example 3: REPORT OF ALL AIN BLOCKS IN THE SYSTEM cd /opt/fox/bin/tools getpars -n -tAIN -mCMPNM:%15s -mCP:%7s mPERIOD:%d mLSCO1:%11.3f mHSCO1:%11.3f -mDESCRP: %33 > z cat z Thu Jun 3 09:21:40 2004 BLOCK-NAME CMPNM CP PERIOD LSCO1 HSCO1 DESCRP 09PT0089A CP3_K1BLREF 3CP101 3 0.000 350.000 A REFINER CASING PRESSURE 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 You can then view the file 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 (will find owner of the LPXX printer). Usage 1 : glof LBUG [LBUG...] Usage 2 : glof -a ALIAS [ALIAS...] Usage 3 : glof -p PROCESS [PROCESS...] Usage 4 : glof -v VARIABLE [VARIABLE...]
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 (to look in IIF.cur and find word NOTYET) grep DNI * (look in all files in current directory for DNI)
head command
Syntax: head n <file-list> Displays the top of the files, by default the top 10 lines. -n Top n lines See tail to get the last 10 lines of the file.
Historian (legacy - copying from one AW to another)
Users who keep identical configurations of legacy historian on two different AW's use the following procedure to copy: The following is an example to copy the configuration from hist01 into hist02 (exact duplicate): AW0001 hosts hist01 AW0002 hosts hist02 Perform saveh50 on AW0001 of hist01 and on AW0002 of hist02. cd /opt/fox/hstorian/bin saveh50 Then, on AW0002, copy the contents of hist02.exp directory to a file for later recovery if needed: (filename hist02122393 has date included in filename-12-23-93). Initialize hist02 and clear contents of the hist02.exp directory: dbinit50 rm -r hist12.exp On AW0001, tar hist01.exp directory to a file to copy to AW0002: cd /opt/fox/hstorian/bin tar cvf hist01122393.tar /opt/fox/hstorian/bin/hist01.exp/* Copy hist01122393.tar (tar file on hist01) to AW0002: rcp -p hist01122393.tar AW0002:/opt/fox/hstorian/bin On AW0002, extract contents of tar file and rename/move to hist02.exp directory: cd /opt/fox/hstorian/bin tar xvf hist01122393.tar (this will extract to a hist11.exp dir on AW0002) mv hist01.exp hist02.exp The next step is to change any instance of hist01 in the files to hist02. cd hist02.exp grep hist01 * (there is a space between "01 and *") Now "vi" the listed files to change hist01 instances to hist02. The files modified may include: pnt_memb.unl, all_groups.unl, arch_cfg.unl, and unload50.sql. Use the following command in vi to globally search for hist01 and replace with hist02: :g/hist01/s//hist02/g 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 Restart the historian.
tar cvf hist02122393.tar /opt/fox/hstorian/bin/hist02.exp/*
Historian (Legacy) - Stopping And Restarting
(20 series) cd /usr/fox/hstorian/bin histonoff -v {histname} ON or histonoff -v {histname} OFF (50 series) cd /opt/fox/hstorian/bin histonoff -v {histname} ON or histonoff -v {histname} OFF
Historical Data - Retrieving From Collection Points on AP20/PW

goto VT100 mode cd /usr/fox/hstorian/bin /usr/fox/bin/tools/dmpnam | pg (get index number) cd /u0/sam/hist11
/usr/fox/bin/tools/samspy q to quit lists
history Command On 50 Series

To turn history command on (C-Shell only): set history = num (To display list of remembered commands): history (To display last n commands): history n history 5 (will show the last 5 commands) (Repeats previous command) !! ! -3 (will re-execute the 3rd last command in history) !n (will re-execute the n number in history) (-r reverses the order of printout to be the most recent first rather than the oldest first. history r (-h displays the history list without leading numbers) history h (Refer to the last command which began with character <char> !<char> !n (would repeat the last command which began with an n) If you have issued the find command in error: fint / -name core print You can use history to change the t in fint to a d and reissue the command by typing: ^fint ^find
history Scroll History Log
On the WP and AW, the Open Windows shelltool provides a window (VT100) where text scrolls upward. This scrolled text can be stored in a temporary history log. You can scroll backwards and forwards and perform searches on the text in the log file. However, the size of this file can grow rapidly and, therefore, should be monitored. The default setting is that the text is not stored to a history file when scrolled out of the window. To enable scroll history logging for text in the VT100 window, Right click the mouse button when in the window pane and select Enable Scrolling from the popup menu. Right click the mouse again to assign the log file to be created. The text is temporarily stored in a history file while the VT100 window is open and automatically deleted 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
hostid determining on a 50 series station
To determine the hostid on your 50 series station, type: Hostid
hps Historian Command

Legacy Historian: hps is a command that is executed to give a list of all of the historian processes that are currently running. 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.
Iccapi save_all and loadall commands
Syntax: save_all station path load_all station path You must first change directory to /opt/fox/ciocfg/api to run these commands. Example: cd /opt/fox/ciocfg/api/ save_all CP0001 /opt/julie/cp0001 (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 To save a list of parameters of block ZF925AI of Compound ZINC_FLASH to ASCII file z: iccprt n ZINC_FLASH:ZF925AI p o z 3CP401 List all blocks in Compound APICMP1 to printer: iccprt n APICMP1 C10A50 List all blocks in Compound APICMP1 to a file apicmp1.txt: iccprt n APICMP1 o /tmp/apicmp1.txt C10A50 List all block parameters in Compound APICMP:PLB001 to a file apicmp1.txt: iccprt p n APICMP1:PLB001 o /tmp/apicmp1.txt C10A50 List all compounds and all blocks to a file apicmp1.txt: iccprt n\* -o /tmp/apicmp1.txt C10A50 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 apply commands to all interfaces in system gives status of ethernet ports. ifconfig le1 down disable 2nd ethernet port ifconfig le1 up enable 2nd ethernet port
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 You must now restart the Display Manager.
INTEGRATED CONTROL BLOCKS

ACCUM Accumulator AIN Analog Input AINR Redundant Analog Input ALMPRI Alarm Priority Change AOUT Analog Output AOUTR Redundant Analog Output
BIAS Bias BIN Binary Input Block BINR Binary Input Block Redundant BLNALM Boolean Alarm BOOL Boolean Variable BOUT Binary Output Block CALC Calculator CALCA Advanced Calculator CHARC Characterizer CIN Contact Input COUT Contact Output DEP Dependent Sequence DGAP Differential Gap DPIDA Distributed PID with Adaptive Control Algorithm DSI Display Station Interface DTIME Dead Time Compensator ECB Equipment Control (See ECBEquip.Control Blocks section) EVENT Event EXC Exception Sequence FBTUNE Feedback Self-Tuner FFTUNE Feedforward Self Tuner GDEV General Device IND Independent Sequence LIM Limiter LLAG Lead Lag LOGIC Logic LONG Long Integer Variable MAIN Multiple Analog Input MATH Mathematics MCIN Multiple Contact Input MCOUTMultiple Contact Output MDACT Motor Driven Actuator Controller MEALM Measurement Alarm MON Monitor MOVLV Motor Operated Valve MROUTMultiple Real Output MSG Message Generator MTR Motor Control MVC Multivariable Controller MVL Multivariable Loop OUTSEL Output Select PACK Packed Long Integer Variable PAKIN Packed Input PAKOUT Packed Output PATALM Pattern Alarm PATT Pattern PID Proportional Integral Derivative PIDA Additive PID PIDE PID with Exact PIDX PID Extended PIDXE PID Extended with Exact PLB Programmable Logic PLCIO Programmable Logic Controller In/Out PLSOUT Pulse Output PTC Proportional Time Controller RAMP Ramp RATIO Ratio
REAL Real Variable REALM Real Alarm RIN Real Input RINR Real Input Redundant ROUT Real Output SIGSEL Signal Selector STALM State Alarm STATE State STRIN String Input STRING String Variable SWCH Switch TIM Timer VLV Valve
Intelligent Devices Getting a List of All IFDs
This command should return ALL compound/blocks which can have intelligent devices. To get entire list of Intelligent Devices configured on system: /opt/fox/ciocfg/ifdenv/ucsaq t ECB13|ECB22|ECB74|ECB18
Intelligent Field Device Configurator

At v4.3 and v6.1 the IFD Configurator comes on a CD separate from the Install CD. To install on v6.1, you must first exit any open IFDC or ITMW applications. mount o ro F hsfs /dev/sr0 /cdrom cd /cdrom/ifdc_sol2 6.1_ifdc After the install script is completed, cd/ umount /cdrom To install on v4.3 WP51 or AW51, you must first exit any open IFDC or ITMW applications. cd /usr/fox/sp/lastinst Backup the REVLVL and SYSLVL files. Change the first line of the REVLVL file from 4.3 to 6.1. Change the lines in the SYSLVL that say 6.1 to 4.3. Insert the IFDC CD into the CDROM. mount o ro F hsfs /dev/sr0 /cdrom cd /cdrom/ifdc_sol2 6.1_ifdc After the install script is completed: cd/ umount /cdrom Copy the original REVLVL and SYSLVL files back into the recently edited versions.
IP Addressing on the Mesh
Switches (Max. 250 on the Mesh) 151.128.81.1 151.128.81.254 Primary Network Port (WSs, CPs, FCMs, ATS) 151.128.152.1 151.128.191.254 Alternate Network Port (WSs, CPs, FMCs, ATS) 151.128.24.1 151.128.63.254 Primary IOC of ZCP 151.128.216.1 151.128.255.254 Alternate IOC of ZCP 151.128.88.1 151.128.127.254 (Alternate IPs are not in System Definition) At v8.0.x, each card in the AW has a unique IP address as well as a software virtual adapter with a
unique address. To determine the alternate, subtract 128 from the primary address. Example: Primary = 151.128.152.1 then the alternate would be 151.128.24.1. At v8.2, One virtual adapter monitors the health of both cards.
IPC Connections - Getting Number Of

See sipc.
ISQL Commands (examples)

create table tablename (tag_one char(32)) select * from tablename from prompt outside of isql: /usr/informix/bin/isql hist01 select all_points.id, red_grp_name.time_tag, red_grp_name.averages from red_grp_name, all_points where red_grp_name.status_tag=3 and red_grp_name.pt_id_key=all_points.pkey order by id, time_tag desc select * from all_points order by id
ISQL Invoking on 50 Series
The following is to make ISQL work on 50 series stations: From C Shell type: setenv INFORMIXDIR /opt/informix setenv PATH ${PATH}:/opt/informix/bin If the development portion of Informix is installed, these variables will already be set. To invoke type: /opt/informix/bin/isql
Jumper Settings - Hard Drives (20 series)
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.
last reboot Command

To find out the date and time of last reboot (also see psrinfo or dmesg. last reboot | head This command lists time and date of all system reboots in the system log.
letterbug determining letterbug of 50 series station

To determine the letterbug of the 50 series station you are on: uname n
Letterbugs - Generic
WP10 G2BOOT WP20 G3BOOT WP30 G4BOOT WP50 G5BOOT COMM10 CSBOOT
Link Methods of Linking Files
There are two types of links, symbolic and hard. The standard command: ln file 1 file 2 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.
loadh50 (Historian Restore Procedure)

Legacy historian: cd /opt/fox/hstorian/bin loadh50
Log file Generating from an executing file for troubleshooting (AP20)
If you think that a certain file is not finishing its execution, having problems, etc., you can generate a log file which will tell you what that executable file is doing and you may possibly be able to tell how far along it got. For example, one of the startup files is called S99FOXBORO. If the following lines are put at the beginning of the S99FOXBORO file and if <filename>=/S99FOXBORO.log, then there will be a log in the root directory of everything that S99FOXBORO tried to run. /bin/sh exec > <filename> 2>1& set x
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 lists files to default printer lp dLP00 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 (to get a listing of all commands)
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 reports if printers are accepting requests -d print sys. Default dest. For output -f verify forms in list are recognized -o print status of output requests -p status of printers -r status of LP request scheduler -R print number showing position of job in the queue -s status summary -S verify character sets are recognized by LP print service -t all status info. -u status of output request by users -v names of printers and path of devices -l long listing lpstat -t (gives printer status)
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 Columns across screen -C Columns down screen -R Recursively list contents of subdirectories
man pages On-Line Manual pages and man Command
The following information available in HH998. Sometimes systems are not set up correctly to read the manual pages. A few simple changes to the environment can fix the situation, and knowing a few commands can make using the man pages easier. The MANPATH environment path needs to be setup properly. If not , you will get the error:
3AWD01# man grep

No manual entry for grep. To correct in C shell enter: setenv MANPATH /opt/share/man In Bourne shell enter: MANPATH=/opt/share/man; export MANPATH
To automatically set these at every login, edit the appropriate file, and add the line in the .cshrc for C shell and .profile for Bourne shell. The Unix manual is delivered in the following sections: man -f intro (Entering "whatis intro" prints the same list.) intro Intro (1) - introduction to commands and application programs intro Intro (1m) - intro to maintenance cmds and application programs intro Intro (2) - introduction to system calls and error numbers intro Intro (3) - introduction to functions and libraries intro Intro (4) - introduction to file formats intro Intro (5) - introduction to miscellany intro Intro (6) - introduction to games and demos intro Intro (7) - introduction to special files intro Intro (9) - introduction to device driver interfaces intro Intro (9e) - introduction to device driver entry points intro Intro (9f) - introduction to DDI/DKI functions intro Intro (9s) - introduction to kernel data structures Type this command: man -f intro /opt/share/man/windex: No such file or directory /usr/openwin/man/windex: No such file or director If this error occurs, You need to convert the man pages from nroff files to preformatted versions of the on-line manual. First, enter: catman -p | more to see how many changes will be made. IF the SYSTEM is SHORT ON DISC 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 pre-format only a few sections, enter: catman 1 2 To search all sections for string "regexp", enter: apropos regexp Compare with a search for string "regex": apropos regex 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 To learn more enter: man man
MANUAL PAGES ON WP51
The man pages are not installed on the local disc of WP51s. There are instructions to access the man pages on a connected AW. The instructions are in the User Guide B0193ND title "System Administration Guide for 50 Series Stations (Solaris 2.x)", section "Miscellaneous Administrative Tasks", paragraph "man Pages". Either remote login or remote mount are specified.
Memory Determining Physical Memory
To determine the amount of physical RAM in AW51:
dmesg | more Or prtconf | grep mem
Merging Two Completely Separate 50 Series Systems

There are two major issues which need to be addressed when combining two I/A systems. CSA will have to be merged. CSA must reside on the AW with the highest level of software no matter which AW is hosting the CPs. CSA can only reside on one node. NSAP address assignments for the systems will have to be merged. A list of all current NSAP assignments for all nodes can be derived by looking at the IIF.prm file in /usr/fox/sp doing a grep for ADRNSP. If these two systems are single node systems being merged into one system, all NSAPs for all stations will change since both nodes will have NSAPs of I000001. If these two systems already have LANs, many of the NSAPs are going to change when you recommit. All stations which receive a new NSAP must be rebooted. If an AW is re-committed and receives a new NSAP address, all CPs/gateways on that node will not be able to communicate with that AW until they are rebooted.
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 Network Distances

Maximum Link Distances Station to Switch & Switch to Switch 2km Multimode Fiber (MMF) 10km Single Mode Fiber (SMF) 100km Single Mode Fiber & Repeaters (not hub repeaters) Standard maximum end to end distance 64km (Seven switches with SMF & MMF links) Possible End to End Distance 800km (Seven switches with SMF & repeaters)
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).
Messages To File - Sending
echo Dont Touch Dis$a >> /usr/julie/filename
Messages To Printer - Sending
a=`date` (prints current date on first line) echo Dont Touch Dis$a >> /dev/LP01 $a
Messages To Workstation - Sending

Since multiple display managers can send the message to the dm name, default dm name is letterbug. pref -WPLBUG dmcmd dmcmd msglin \HI THERE\ sleep 15 pref -WPLBUG dmcmd dmcmd msglin\\
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
Mirroring hard drives (50 series)
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 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.
Mirrored Drive Nds_Maint Problems
There are occasions when one partition of a mirrored disk pair will report the status of Nds_Maint. Using the metadetach and metattach commands will usually correct this problem. The following procedure was done on an AP50, the same procedure will work on a 51 series but the Metamirror and Submirror device names will be different. Run the dft show_status command to view the mirrored status of the hard drives. Example output of dft show_status of the line that shows needing maintenance. /dev/md0g: /dev/md4g: 306000 ESP0 / SCSI3 Okay /dev/md8g: 306000 ESP1 / SCSI3 Nds_Maint Note: The md0g or /usr partition on the esp1 scsi bus has a status of Nds_Maint.Type: metadetach f (metamirror) (submirror that needs maint) or metadetach f /dev/md0g /dev/md8g Metadevice /dev/md8g is now detached. metattach /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.
Mirrored Disk Drive Problems Recovering mkmact Command

Example: /usr/foxbin/mkmact /usr/menus
The procedure to help recover from a mirrored disk failure is outlined in HH745.
Modem Commands
&v View the active profile at&v View atz Exit and Save Foxwatch Setup 9600, N81, COM1 at&z1=/asecure This unsecures the modem at&v Displays configuration Atz
Modes on 50 Series Stations

Normal (Multi-User) Operating Mode Prompt: <APLBUG> Boot Command: reboot Single User Mode/Maintenance Mode Prompt: # Boot Command: reboot
PROM Monitor Mode Prompt: > Boot Command: b Forth Toolkit Mode Prompt: ok Boot Command: boot disk boot tape CTRL-P to get to Monitor mode on AP50 or Wyse <STOP>A to get to Monitor mode on WP/AW50 n to get to toolkit mode on WP/AW/AP50 and Wyse b Normal Mode b -s Single User Mode n Forth Toolbox Mode b -r Reconfigure
more Command
Usage: more [-cdflrsuw][-lines][+linenumber] [+/pattern][filename] more filename (to cat to screen one page at a time) -c clear before displaying -d display error messages -f do not fold long lines -l do not treat ff chars. as page breaks -r disp uninterpreted ctrl chars as ^C -s replace blank lines with 1 blank line -u suppress escape sequences -w prompt & wait for key before exiting -lines display indicated # lines +linenumber start up at linenumber +/pattern start up 2 lines about pattern
Mount Floppy To Copy Files on 20 Series

mount /dev/fh0 /f0 cp /f0/[path] /usr/[path] umount /dev/fh0
Mount floppy and CD- On 50 Series

To mount a floppy on 51 station: mount /dev/fd0 /f0 umount /dev/fd0 /f0 eject *NOTE: A mountable 50 series diskette will not mount on PW. To mount a DOS diskette on the 50: mount -F pcfs /dev/fd0 /pcfs or mount /pcfs To mount a DOS diskette on the 51: mount /pcfs (PC file system) If you have problems with this command try using: mount /dev/fd0 /pcfs
To mount a local CDROM on the 51: mount r F hsfs /dev/dsk/c0t6d0s0 /cdrom or mount o ro F hsfs /dev/sr0 /cdrom or mount r /dev/sd6c /cdrom To mount a remote CDROM on the 50 station: 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 Edit the file /etc/exports by adding: /cdrom ro 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 Mount the cdrom on the remote processor by typing: mount r /dev/sr0 /cdrom su root Mount the cdrom by typing: mount r <remote_machinename>:/cdrom /cdrom The following warning appears: WARNING: No network locking on <remote_machinename>:/cdrom. Contact admin to install server change. This warning is normal. You are now ready to install the software onto your local machine. To mount a remote CD on a 51 station: Edit the file /etc/dfs/dfstab by adding: share F nfs o ro d CD-ROM Directory /cdrom (CD-ROM Directory is an optional description used with the d option. Export the /cdrom directory by typing: shareall On the remote processor, mount the CD-ROM by typing: mount r /dev/sd6c /cdrom You may have to issue the mount command twice. Check to see if ufds is running by typing: ps ef | grep ufds If ufds is not running, reboot before continuing. Mount the CD-ROM by typing: mount r <remote_machinename>:/cdrom /cdrom To mount partitions on the hard drive from the local CDROM: (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
Network - Troubleshooting v7.x Network
HH#: HH1050 IA INFO: jco0204 File: V7x Network Troubleshooting Release: 7.0 & 7.1 Date: July 29, 2004 Subject: V7x. Network Troubleshooting Source: Development & TAC Basic Network Checks o Verify that all Workstations have a splitter cable o Verify that the splitter combiner is connected to serial port "A" and the proper NIC or network interface o Verify that the RCNI cables go to the proper switch ("A" or "B") o Verify that the Ethernet cable from the splitter combiner to the RCNI is good. 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. o Verify that on each NCNI pair one switch is set to "A" and the other set to "B". o Verify that the NCNI is connected to the proper switch (A or B) o If there is more than one switch in series for each cable verify that there are no crossed cables between switches. o 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. o 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. o 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. o 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. 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. 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.
Verify the link leds are active on the RCNI Verify the status led of the RCNI is green. There are two status leds in the upper right corner of the RCNI. If the status leds are red/green the RCNI will not communicate properly. Power down and up to try and correct the problem. Verify all cabling Replace the RCNI
Debugging NFD Problems (General) 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.
Networking AW51E with XP station
This procedure was used to network an AW51E with a Windows XP station not running I/A to copy certain display files from AW to XP station/laptop. Example: The AWs 2nd Ethernet port has IP address of 138.90.221.2. Assign the IP address on XP station to 138.90.21.3. Both stations connected to the same hub/network. Open command prompt window on XP station. Change directory on XP station to the directory files will reside when copied from the AW. ftp 138.90.221.2 bin cd /usr/disp (cd to dir location of files to extract) mget * (to get multiple files in the directory) (or use)
get filename (to get one particular file)
Networking Configuring Master Browser on Windows Station
This method required modifying the system registry. Please do not do this unless you know what you are doing or you may suffer the consequences if there is an error. Start Run regedit (change XP/NT registry entry of the following to yes) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\Maintain Server List (exit regedit) Right click My Computer Manage double click Services and Applications double click Services double click Computer Browser Change startup type from Disabled to Automatic OK (restart the system/reboot) After system reboots, go to My Network Places Select Add Network Place (use the wizard) Choose another network location will be highlighted Select Next and for Internet or Network Address type: \\WP5111\D$ (WP5111 is the computer name)
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 (for more details and instructions) One example of using the netstat command is as follows to capture errors on the hme0 port: netstat I hme0 5
NFD Guidelines when adding v7.x station to a node with v6.x
For v7.x Network Troubleshooting, see Troubleshooting v7.x Network in this guide or HH1050. If there is a mix of V7.x and V6.x stations on a node then NFD on stations earlier than V6.5.2 must be killed or disabled. This can be achieved as follows: NOTE: V6.5.2 NFD is equal to V7.1.1 NFD. Solaris stations: 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 Kill the running nfd_8023 process Windows NT/XP stations: 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.
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
Nutcracker Environment on Windows NT 70 Series
The nutcracker environment is where you can enter Unix commands as if you were on a 50 series
station. It emulates UNIX on Windows NT. Go to the MSDOS Command Prompt d: ncenv sh
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 to set back to manual: s1=0 b (enter) will get bulk values g2 to get value of one item (line number 2) to save sheet to file w filename to read/retrieve file r filename to set bscale to 32 on TI_4209: s ti_4209:input.bscale=32
omget - Get Value Of Variables and Write To File
If used in a script on an AP20, put sleep 1 between each omget. Usage: omget [-av] [<name>..] -a alias -v variable omget LOGIC:HEATER1.IFL_11 > julie.txt omget LOGIC:HEATER1.IFL_12 >> julie.txt location of omget: 20 series (/usr/fox/bin/tools) 50 series (/opt/fox/bin/tools)
omset
Usage: omset [-av] [-bcfils<value>] -a alias -v variable -b boolean -c character -f float -I int. system performance
Operating System Determining Solaris Version and Hardware Model
The present Solaris version is 2.5.1. By adding the number 3 to the Solaris version, you can determine the SunOS version which is 5.5.1. You can find the hardware type and version number of the operating system by issuing the uname a command at a console prompt. Foxboro Hardware Type Sun Microsystems Hardware Type AW51A CLASSIC 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) This utility used to reoptimize displays. /usr/foxbin/pdfpack r /usr/disp (50 series) /usr/foxbin/pdfpack r /usr/disp 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.
Partition Information (AP/AW 50 Series)

Partition # 0 1 2 3 4 5 6 7 Device 50,51A,51B,51C /dev/md/dsk/d0 /dev/md/dsk/d1 /dev/dsk/c0t3d0s2 /dev/dsk/c0t3d0s3 /dev/md/dsk/d2 /dev/md/dsk/d3 /dev/md/dsk/d4 /dev/md/dsk/d5 Device 51D,51E /dev/md/dsk/d0 /dev/md/dsk/d1 /dev/dsk/c0t0d0s2 /dev/dsk/c0t0d0s3 /dev/md/dsk/d2 /dev/md/dsk/d3 /dev/md/dsk/d4 /dev/md/dsk/d5 Partition Name / (root) Swap Full Disk MetadeviceDB /var INFORMIX DB /usr /opt
EIDE and SCSI Peripheral DISK Names (Sorted by OS) SunOS 4.1.1 /dev/md0a /dev/rmd0d /dev/rmd0d /dev/md0 /dev/rmd/0f /dev/md0g /dev/md0h Solaris 2.5.1 50,51A,51B,51C /dev/md/dsk/d0 /dev/rdsk/c0t3d0s3 /dev/rdsk/c1t3d0s3 /dev/md/dsk/d2 /dev/md/rdsk/d3 /dev/md/dsk/d4 /dev/md/dsk/d5 Solaris 2.5.1 51D,51E /dev/md/dsk/d0 /dev/rdsk/c0t0d3s3 /dev/rdsk/c1t0d3s3 /dev/md/dsk/d2 /dev/md/rdsk/d3 /dev/md/dsk/d4 /dev/md/dsk/d5 Partition Name AP/AW root partition AP/AW Mirror DB Primary AP/AW Mirror DB Shadow AP/AW /var partition AP/AW INFORMIX RAW AP/AW /usr/partition AP/AW /opt partition
Password Changing password for Foxview Environments

The environment directory may be specified in /usr/fox/wp/data/wp51_glbls.all file. It will look something like this: SURDIR=/opt/fox/env To change the password for the Proc_Eng_Env environment to newpassword do the following: cd /usr/fox/wp/bin/tools dmsepass Proc_Eng_Env p newpassword f /usr/fox/wp/data/dmpasswd_cfg
This will change the password to newpassword and update the dmpasswd_cfg file with the new password.
path_to_inst Building Drive offline for 51B/C using 51A processor

When building drives for an upgrade offsite, you can utilize a 51A system to build for 51B or 51C processor for version 4.2x. This is done using the path_to_inst* files located in the /etc directory and also on the boot CD. The files that exist are: /etc/path_to_inst Loaded during ia_install /etc/path_to_inst.A for 51A boxes /etc/path_to_inst.B for 51B boxes /etc/path_to_inst.C for 51C boxes Example: Build a 1.03 GB drive for a AW51B which has an internal drive. Available system: AW51A with an external 1.03 GB drive. Boot the AW51A with the Boot CD and start the IA install for AW51B processor. On completion, mount the root (/) partition of the drive. mount o rw F ufs /dev/sd0a /mnt cd /mnt/etc cp path_to_inst.A path_to_inst 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 Backup the system (dmp0). There have been instances where an AW/AP would not boot any stations that it hosts after a commit. One way that weve been able to correct this is to use the following method. If youre on an AW51A, then you would go to the /etc directory and copy the path_to_inst.A file to the path_to_inst file. Example: cd /etc cp path_to_inst.A 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 And Phasing

Period Value Length 0 1 2 3 4 5 6 0.1 sec 0.5 sec
The following table lists the phase values for a CP that has a BPC of 0.5 seconds. Phase Values Not Allowed [0] default Phase Values [0-1199]
Value 7 8
Length 10 min 60 min
[0-7199] Not 1.0 sec [0,1] 9 0.2 sec 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] Not 1 min [0-119] 13 0.05 sec Allowed *Available in CP40,CP40B & CP60 only when permitted
Relationship Between Block Period and Phase Block periods greater than the BPC are always equal to an integral number of BPCs (for example,
when the BPC is 0.5 seconds, a block period of 2.0 seconds equals 4 BPCs). Each block uses this integral multiple, N, to set up a modulo N counter that counts BPCs and triggers block execution every Nth BPC. In the example where N equals 4, the block's modulo counter cycles through the counts 0-1-2-3-0-1-2-30-1-2-3-0-, triggering block execution every fourth cycle. The block's Phase value determines whether block execution occurs at the 0 count, the 1 count, the 2 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 (Where 64 is the packet size and 30 is the # of packets to capture) See the manual for ping for more information.
pg Command
Usage: pg [-number][-p string][-cefnrs][+linenumber] [+/pattern][filename] -c clear before displaying -p use string as prompt -number size of window to use -e do not pause at end of each file -r restricted mode -s standard output mode -f no page splitting -lines display indicated # lines +linenumber start up at linenumber -n auto end of cmd -cmd ltr is ent. +/pattern start at first line with pattern expression pg filename ls | pg (view one page at a time)
pr Command
Usage: pr [[-columns][-width][-a]][-eck][-ick][-drtfp][+page][-nck][-ooffset][-llength][-sseparator][-hheader] [-F][filename] +page begin with page number -columns print cols. # of output -a print multi col. 1 line/col. -m merge/print all file 1/col. -d doublespace the output -eck expand input tabs -ick replace white space in output -nck provide k-digit line numbers -wwidth set width to (width) -ooffset offset line by (offset) -llength set length of page to (length) -hheader use header as text of header -p pause before begin of page -f use single form feed char -r print no diag reports on files that cant be opened -t dont print header/trailer -s separator separate cols. by single char
-F fold lines of input file pr filename ( list file in page form) pr filename > /dev/LP01 (same and direct to LP01) pr test > /dev/LP01 (list files that begin with test, send to LP01) pr filename | more (file appears on screen formatted into numbered pages with header w/filename and date and time) pr -2 filename | more (print file in 2 column format) pr -2h Put text header here filename | more (to change header of above formatted file) pr -2dh Put header text here filename | more (to double-space above formatted line) pr-2dh Put header text here filename | lp -dLP01 (prints formatted file to LP01) pr-2dh Put head text here filename | -d LP01 -n2 (prints two copies to LP01)
pref Command
Usage: pref [-<lbug>] <vbl> [<value>] Examples: pref -WPLBUG dmcmd /usr/disp/displayname sends /usr/disp/displayname to the WPs display manager pref WP0001 dmcmd stddisp COMP:BLK PID forces station WP0001 to display the detail display for PID block COMP:BLK
Printer Adding a printer to a 51F (P79) station (HH1061)

1) HARDWARE INSTALLATION 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... Starting saip daemon to download PCI Async firmware ... After reboot, you should see the new devices: cd /dev/term ls -l lrwxrwxrwx 1 root root 51 Sep 7 13:51 a000 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a000,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a001 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a001,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a002 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a002,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a003 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a003,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a004 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a004,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a005 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a005,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a006 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a006,term lrwxrwxrwx 1 root root 51 Sep 7 13:51 a007 -> ../../devices/pci@1f,0/pci@5/pci114f,1c@0:a007,term lrwxrwxrwx 1 root other 43 Aug 31 11:20 c -> ../../devices/pci@1f,0/isa@7/serial@0,3f8:a lrwxrwxrwx 1 root other 43 Aug 31 11:20 d -> ../../devices/pci@1f,0/isa@7/serial@0,2e8:b lrwxrwxrwx 1 root root 51 Aug 31 11:10 a -> ../../devices/pci@8,700000/ebus@5/serial@1,400000:a lrwxrwxrwx 1 root root 51 Aug 31 11:10 b -> ../../devices/pci@8,700000/ebus@5/serial@1,400000:b 2) SYSTEM DEFINITION 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") Select View, Parameter Definition Enter LP01 for 51F "Port 1 Logical Name" NOTE: Leave "Port 3 Logical Name" empty Options, Utilities, Check Configuration Options, Utilities, View Log Files Ignore all these errors: - WARNING: Port has logical name but no peripheral is connected (P1LN) OS6AW1->AW51F1 - WARNING: Printer connected to port with no logical name (P3LN) OS6AW1->AW51F1 - ERROR: Port Logical Name not 4 characters long (P3LN) OS6AW1->AW51F1 - ERROR: Station needs serial expansion board, but no one found: AW51F1 Create Committal diskette using v7.1 10091 diskette 3) SOFTWARE INSTALLATION
Pass Committal diskette using "Install_AW" Check log files and reboot the box 4) INITIAL VERIFICATIONS After reboot you should notice: - /etc/printers: doesn't show the Serial Printer (LP01) - System Management doesn't show any printers attached to this 51F - Can not print by redirection to /dev/LP01 --> can not create error - cs_alarm is not running 5) FIRST SET OF CORRECTIONS Correct "cs_alarm" file by: Changing owner to 'root' from 'nobody' Changing group to 'sys' from 'nobody' cd /usr/fox/exten chown root cs_alarm chgrp sys cs_alarm Reboot box again. After reboot you should see now: - cs_alarm is running - SysMgmt now shows: LP01 in White, but as a TERMinal - cat /etc/printers > dev/term/a001 It should print correctly - cat /etc/printers > dev/LP01 Error: can not create - lp -dLP01 /etc/printers It should print correctly 6) FINAL CORRECTIONS Change how printer shows in SysMgmt from 'Terminal' to Printer: LPTYPE = 4 (VT100 Wyse Terminal) LPTYPE = 3 (80 Dot-Matrix,B/W,Ser) LPTYPE = 5 (132 Dot-Matrix,B/W,Ser) LPTYPE = 5 (136 Dot-Matrix,Color,Ser) cd /usr/fox/sp/files vi cs_cfg.pars Change line: LPTYPE#4 To: LPTYPE#5 After the change, that section should look like this: # Printer Definition for LP01 on /dev/term/a001 # System Configuration Parameter Name: P1LN LPNAME=LP01 # System Configuration Parameter Name: P1B1 # --- No Backup device configured --PTNAME=/dev/term/a001 LPTYPE#5 # # End of P1LN parameter specifications Add the new Serial Printer LP01 to /etc/printers: cd /etc vi printers 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
The best printer troubleshooting guide in the world can be found at Angel Corberas web site located at: http://www.geocities.com/SiliconValley/Peaks/5825/ac.htm I cannot put all of the information in here because it is a booklet by itself. Great job, Angel and thank you!!! (The same document can be found on the Foxboro website if for some reason the above link doesnt work.)
Printer Troubleshooting
Printers Direct Connect Configuration

Direct connect parallel printers connected to 50 series stations are to be configured to Port 2 (parallel).
Printer Problem - HP1600 defaults to 60 lines/page while UNIX defaults to 66

Make a backup copy of ps_interface file cd /etc/lp/interfaces cp ps_interface ps_interface.org 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 After saving the file, assign interface program to printer: lpadmin -p LPXX -i /etc/lp/interfaces/ps_interface set default page length lpadmin -p LPXX -o length=66
Printer problem preventing printscreen color problems (Models 51D and 51E)
The default parameters of the Style D and Style E parallel port are different from those of other 51 stations. Change the parallel port settings to prevent printscreens from having distorted colors. (For example, printscreens sent to an HP890C printer sometimes have this problem.) To change the parallel port settings on the Model 51, invoke a VT100 window and enter the command: lpadmin p LPxx H Where xx is the printer number.
Printer Problem Print Device Failure
Print device failure after alarm burst condition: To handle a large burst of alarm messages the CMP10 has been changed to allow for backed up messages to be rerouted to a remote backup print device. When the primary print device is in the rerouting mode the status of the print device if OFFLINE and NOT FAILED in the SMDH display. Once the burst condition has subsided, to return the primary to ON-LINE and NOT FAILED the operator must manually toggle the print device off/on-line or power reset the print device.
The following information found in CAR 992163. Problem with all types of parallel printers (1200,1600and 895cxi) on Unix platforms. All of last year we were experiencing problem with printers, disabling in spooler, not printing etc. After installation of QF991068b, printers would disable after a reboot of an AW or WP. After running dm_recon and verifying the cs.dm.current file, it was notice that the printer connected to device 3 was indicating FAIL. If the second device is not configured it will fail the third device.
Printer Problem Printer Will Not Print (spooler becomes disabled)
Problem Workaround: To work around the problem a dummy printer can be added to /usr/fox/sp/files/cs_cfg.pars file. Edit the cs_cfg.pars file and copy the 10 lines for P2LN, and place the dummy copy above the real parallel printer information. Change the LPNAME parameter of the dummy entry to some unused value, like LP99, and change the PTNAME parameter of the dummy to /dev/ttyb. Save and exit the edit, and reboot the processor. Problem Action Quick Fixes 991068 and 990273 are needed to resolve this issue. The following list has the 2 Quick Fixes that are needed, and must be installed in the same sequence. 991068B - cs_devmon, etc 990273B - cs_devmon, cs_alarm, etc Revision B of 991068 (existing Quick Fix) must be installed first if it has not already been installed on the system. Revision B of 990273 should be installed next. It detects when the Foxboro Alarm queue is stalled, and causes the printer to go off line in Station Management.. It also offers much more consistent print options than the original Quick Custom. The changes will be released in version 6.3.
Printer Problem Printscreens are too dark
Printscreens on the PostScript 1200 sometimes come out too dark. To change the gamma correction go to VT100 and do the following: cd /usr/fox/wp/bin echo /usr/fox/wp/bin/xwd2ps g.50 > printscreen.cmd The value g.50 represents the gamma correction value. Gamma factor: 0.25 < gamma < 1: 1=normal, 0.25=brighter
Printer Problem Printscreens take longer
Printscreens on the PaintJet replacement, HP1200C/PS may take longer. The HP1200 waits to receive the entire image before it begins printing. It may take up to an additional 1 minute and 15 seconds to complete a printscreen. The HP supports a Negative Motion print option. The default causes the HP to wait for the data before printing it. We can change this to no manually for the HP to begin printing as soon as the data is received. Type in a VT100 window: echo \033&a1N > /dev/LPxx (LPxx is logical name of the HP1200)
Printer Problem Skewed Printing on Color Inkjet Printer
When printing to an HP PaintJet printer, the pringout may appear skewed, because the InkJet does not automatically insert carriage returns after line feeds. To correct this situation, type the following line in VT100 mode: echo \033&k2G > /dev/LPnn (where LPnn is the logical printer name).
When the line termination character in an ASCII file is a <LF> instead of a <CR><LF>, output may be skewed. That is, each line of the output begins in the column following the end of the proceeding line. Printing from AP10 or AP20 On an AP10/20 this problem is avoided by printing ASCII files with the lp command: lp dLPXX filename.txt Printing from Model 50 stations On 50 Series stations, this problem can be worked-around by instructing the printer to do a <CR><LF> each time it sees only a <LF>. This can be done sending the printer an escape sequence as follows: echo \033&k2G>/dev/LPXX 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
Printer Problem Printing Skewed ASCII Output
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 (LPXX: logical name for the HP 1200C/PS) Using a text editor find the following at or about line 709: #### #Set the page size and print spacing, but not the character set. #We will be doing the character set later (after the header). #### internal-lpset ${cpi}${lpi}${width}${length} Add the following lines after the above text: #Echo command to printer to map Newlines #as carriage-return Newline. echo \033&k2G Near the end of the file find: if [-n ${FF}-ayes=${nofilebreak}] then echo ${CR}${FF}\c fi Add the following lines after the above text: #Eject the last page out of the printer echo \014 After both of the above changes are complete issue the following lpadmin command: lpadmin p LPXX i /etc/lp/interfaces/HP1200 An lp of an ASCII file is formatted properly and the last page is ejected.
Printer And Scheduler Commands on 20 Series Stations

/usr/lib/lpshut 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)
Printer Not Showing Up In List Of Printers In Control Configurator

20 series: lpstat -t (to see if printer is in scheduler) cd /usr/lib lpshut lpadmin -pLP02 -v/dev/LP02 -i/usr/fox/eq/scoki293 (scoki293 found in /usr/spool/lp/interface) /usr/lib/lpsched enable LP02 accept LP02
then check /etc/printers to see if LP02 is there, if not, copy that file from other AP
Printers - Ports Types and Descriptions

Port Type Description 0003 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
probe-scsi and probe-scsi-all and probe-ide
To probe the SCSI bus to see equipment on the bus: At the ok> prompt only type: probe-scsi probe-scsi-all On a 51D, you can use probe-ide since the 51D does not use SCSI drives. probe-ide
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 (shows cpu and memory usage on 50 series stations.) -e Display status info. about all active processes controlled by any terminal L Long, complete status report with 14 columns S State of process R Running S Sleeping W Waiting PID Process ID of the process PPID Process ID of the parent process TTY Number of the terminal that controls this process TIME Number of seconds the process has been executing CMD Command line the process was called with. 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.
RAID drive Connecting to Laptop
Connect via COM1. Set RAID and hyperterminal to 19200 Baud with Parity at 8-None-1, and XON/XOFF. Change font to terminal in hyperterminal program. Use Ctrl+L to refresh hyperterminal screen when connected to RAID.
rcp Remote Copy on 50 series stations
The rcp command copies files between machines. Each filename or directory argument is either a remote filename of the form hostname:path or a local file name (containing no : (colon) characters, or / (slash) before any : (colon) characters). Syntax: rcp hostname:path rcp [-p] file1 file2 rcp [-pr] filenamedirectory To copy /usr/disp from remote machine AP5101 to /tmp on local machine: rcp AP5101:/usr/disp /tmp or cd /tmp rcp AP5101:/usr/disp/* `pwd`
To copy /usr/disp from local machine to /tmp on remote machine AP5101: rcp /usr/disp/* AP5101: /tmp or cd /usr/disp rcp `pwd`/* AP5101:/tmp
Reboot on 20 Series Stations Reboot on 50 Series Stations
/usr/fox/bin/tools/reboot WPLBUG
/opt/fox/bin/tools/iaboot WPLBUG 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
Reduction Groups - Deleting Names of
Legacy historian: (names still appear on list after regular deletion) from isql delete from all_groups where id=reduction group name
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 & To start remd on AP50/51: nohup /opt/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 Retrieve counters -cr Retrieve counters and then reset -r Reset counters -t show TBC statistics Example:
remv -dSYSMO1 -sAP2100 -cr (The symbol @ acts as a wild card)
Remote Application Troubleshooting Checklist
Check for rem_strt process already running on Initiating station. ps eaf | grep rem_strt 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.
Remote Login from VT100

rlogin lbug
Remove Files In A Directory
rm -r /path/directory (this command is dangerous! It removes files and directories recursively.)
Restoring Level 0 Dump Tapes on 50 Series

At ok prompt: boot cdrom While booted on the cdrom, type: restore_8MM (if on an AP or AW) or wprestore_8MM (if on a WP) or if using the new backup and restore utilities restore
Restore Interactive on 50 series
After reading in the directory information from the media, ufsrestore invokes an interactive interface that allows you to browse through the dump files directory hierarchy and select individual files to be extracted. Syntax: ufsrestore ifvs [tape device-name] [tape file-number] 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 You can change directories within the dump volume. cd PDEMO/HI/annunc ls add REA* (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.
Restoring individual files from level 0 dump tapes on 51 stations
The File Systems Tape of the level 0 dump on the 51 stations uses the command ufsrestore to restore files from this tape. To view files in the root partition on the tape: (Example)
ufsrestore tfs /dev/rst9 1

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 The partition numbers for APs/AWs are as follows: /(root) = 1 /var = 2 /usr = 3
/opt = 4 The partition numbers for WPs are: /(root) = 1 /usr = 2 /opt = 3
Restoring individual files from level 0 dump tapes on 50 stations
The File Systems Tape of the level 0 dump on the 50 stations uses the command restore to restore files from this tape. To view files in the root partition on the tape: (Example) /etc/restore tfs /dev/rst1 1 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 The partition numbers are as follows: /(root) = 1 /var = 2 /usr = 3 /opt = 4 The partition numbers for WPs are: /(root) = 1 /usr = 2 /opt = 3
Restoring Individual Partitions 50 Series

To restore only the /var partition: cd / shutdown the AP/AW Do fsck on / and /usr to check their consistency. fsck y /dev/md/rdsk/d0 fsck y /dev/md/rdsk/d4 newfs /dev/rsd0e fsck y /dev/rsd0e mount o rw F ufs /dev/sd0e /mnt The following command for RAID drives only : mount o rw F ufs /dev/dsk/c1t0d0s7 /mnt (end of for RAID drives only) cd /mnt ufsrestore xfs /dev/rst9 2 cd / umount /dev/sd0e
fsck y /dev/rsd0e To restore only the /opt partition: cd / shutdown the AP/AW Do fsck on / and /usr to check their consistency. fsck y /dev/md/rdsk/d0 fsck y /dev/md/rdsk/d4 newfs /dev/md/rdsk/d5 fsck y /dev/md/rdsk/d5 mount o rw F ufs /dev/md/dsk/d5 /opt cd /opt ufsrestore xfs /dev/rst9 4 cd / umount /dev/md/rdsk/d5 fsck y /dev/md/rdsk/d5
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
rm_station - Delete/Remove Installed Stations

Initialize the station to be deleted. The current Day 1 must be modified to detach and delete the desired station. The system monitor assignment will be removed automatically. Commit the configuration Execute Committed Install Files on all stations. Execute /usr/fox/swi/rm_station to remove SICT table entries as follows: rm_station host_id station_id Example: rm_station 21AP20 21CP10 In this example, 21CP10 will be removed from the SICT tables and will no longer be able to boot. This is a very important step! Remove the following files from /usr/fox/sp/files: DB<LBUG>.UC (Checkpoint file)
DB<LBUG>.init (initialized file) BB<LBUG>.UC (backup checkpoint file) CMX<LBUG>.BIN (cmx/boot file) If the station is not initialized as described in step 1 there will also be files left over in: /opt/fox/ciocfg/CPLBUG (50 Series) and /usr/fox/ciocfg/CPLBUG (Intel).
rnfd Tool (remote NFD ATS tool)

The rnfd tool causes an ATS to generate an nfd_log on the host. Usage: rnfd <ATS LBUG> <RET> 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 /etc/fox/go_addroute Create /etc/fox/go_addroute:
route add default 199.184.138.1 1 {for one hop} route add 199.184.138.1 199.184.138.6 2 {for two hops} (199.184.138.1 & 199.184.138.6 are the IP addresses for the additional routers.) Ensure you perform the following to make the file executable: chmod 777 /etc/fox/go_addroute To add routers on the fly without initiating a reboot perform the following; # netstat -r > routetable (redirect routing table to filename routetable) # ping {Router IP} (to ensure your AW/AP can actually talk) # netstat -f (flushes the routing table) # route add default {Router IP} 1 OR # route add {Router1 IP} {Router2 IP} 2 See HH876 for additional networking information. Example: Adding a router/hub: When trying to communicate through a router and/or hub, the following command may be executed: /usr/sbin/route add <newpcip> <newrouterip> 1 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
System Monitor Messages (viewing and sending to a file)
The following information may be obtained from HH1000. The helpful hint assumes that the name of the Historian is known and provides five options on how to get the System Monitor Messages: 1) Legacy
Historian and Informix, this procedure can be executed on the 51 series also; 2) Legacy historian and foxtst, this procedure can be executed on 51 series; 3) AIM*Historian and apitst, runs on 51 and 70 series; 4) AIM*Historian and FH_SACEGO, runs on 51 or 70 series; 5) Creating a smon_log file, works on 51 or 70 series running v6.2 or later. Legacy Historian and Informix 1. Open a VT100 window and change to the csh (C Shell). csh 2. Change to the /opt/fox/hstorian/bin directory. cd /opt/fox/hstorian/bin 3. Set the PATH variable setenv PATH ${PATH}:/opt/informix/bin 4. Set the INFORMIX variable setenv INFORMIXDIR /opt/informix 5. Send the system monitor messages to a file. isql histaw > mon_msg << @ select * from sysmonmsg order by time_tag desc; @ 6. Do more on the mon_msg file. more mon_msg
Legacy historian and foxtst
1. Open a VT100 window and change to the /opt/fox/ais/bin directory. cd /opt/fox/ais/bin 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
AIM*Historian and apitst

Open a Command Prompt window and change to korn shell (d:, ncenv and sh) or a VT100 window. Change to the /opt/aim/bin directory. cd /opt/fox/ais/bin 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
AIM*Historian and FH_SACEGO
1. Open a VT100 window and change to /opt/aim/bin directory. cd /opt/aim/bin 2. Run fh_sacego to get the system monitor messages.
fh_sacego msg_mon.out histaw "" "" "" "2002-05-02-12:00" "2002-05-06-09:30" -m

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
Creating a smon_log file
1. On NT, open a Command Prompt window and change to korn shell (d:, ncenv and sh). On UNIX, open a VT100 window. 2. Change to the /opt/fox directory: cd /opt/fox 3. If the sysmgm directory doesn't exist then create it. mkdir sysmgm 4. Change to the sysmgm directory. cd sysmgm 5. Make a sysmon directory and change it to there. mkdir sysmom cd sysmon 6. In the /opt/fox/sysmgm/sysmon directory, create a file and name it smon_log. touch smon_log 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 See Historian for details.
save_all Command
For a detailed description of the save_all command, go to the section titled Utilities: Upload, Shrink, Checkpoint, Save_all.
Moving SAVEALL Diskette between Solaris and NT Operating Systems, Including PLB Blocks (Obtained from HH912)
METHOD 1: CONTROL DATABASE ON DISKETTE ON THE UNIX STATION 1. Open a VT100 session.\ 2. Change to the /opt directory and create a new directory. Example: # cd /opt # mkdir unix62 3. Insert the UNIX Control Database (SaveAll) on the floppy drive. 4. Mount the floppy. Example: # cd / # mount /dev/fd0 /f0 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 6. Umount the floppy and eject it. Example: # cd / # umount /dev/fd0 # eject /dev/fd0 7. Insert a new diskette and format it. 8. Tar all files and directories to diskette and eject it. Example: # cd /opt/unix62 # 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: C:\> ncenv (Enter) C:\> d: (Enter) D:\> sh (Enter) Now your prompt will be $ 2. Change to the /opt directory and create a new directory. Example: $ cd /opt $ mkdir nt62 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. Making a saveall NT.
5.1. Run NT Explorer and select the D:\opt\nt62 folder. 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 and LoadAll using the diskette created in the step 5.
METHOD 2: USING ICCAPI AND CONTROL DATABASE LOADED ON A STATION ON UNIX STATION 1. If the Control Database is loaded on a CP or Micro I/A or an AW51X use this procedure. 2. Open a VT100 session. 3. Change to the /opt directory and create a new directory. Example: # cd /opt # mkdir unix62 4. Change to the /opt/fox/ciocfg/api directory. Example: # cd /opt/fox/ciocfg/api 5. Perform a SaveAll, running the save_all utility. ICC should not be opened. Example: # save_all CPLBUG /opt/unix62 Where: CPLBUG is the letterbug of the CP or Micro I/A or AW51X. 6. Tar all files and directories to diskette and eject it. 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: C:\> ncenv (Enter) C:\> d: (Enter) D:\> sh (Enter) Now your prompt will be $ 2. Change to /opt directory and create a new directory. Example: $ cd /opt $ mkdir nt62 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 Where: CPLBUG is the letterbug of the CP or Micro I/A or AW70X. 6. Open ICC and verify that all compounds and blocks were loaded. HOW TO CONVERT NT CONTROL DATA BASE TO UNIX INCLUDING PLB BLOCKS.
METHOD 1: CONTROL DATABASE ON DISKETTE ON THE NT STATION 1. Open a DOS Command Prompt window and run the Korn shell. Example: C:\> ncenv (Enter) C:\> d: (Enter) D:\> sh (Enter) Now your prompt will be $ 2. Change to /opt directory and create a new directory. Example: $ cd /opt $ cd mkdir nt62 3. Insert the NT Control Database (SaveAll) on the floppy drive. 4. Copy all files and directories from the diskette to the new directory. Example: $ cd a: $ cp -r * /opt/nt62 $ cp .Compound_Dir /opt/nt62 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: ON THE UNIX STATION 1. Open a VT100 session. 2. Change to the /opt directory and create a new directory. Example: # cd /opt # mkdir unix62 3. Insert the diskette created in the step 5 of the METHOD 1 CONTROL DATABASE ON DISKETTE procedure. 4. Change to the new directory and tar all directories and the .Compound_Dir file. Example: # cd /opt/unix62 # tar xvf /dev/fd0 5. Eject the floppy. 6. Insert a new floppy and format it. Example: # fdformat 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 newfs: construct a new file system /dev/rfd0c: (y/n)? y # mount /dev/fd0c /f0 # rmdir /f0/lost+found 8. Transfer all directories and the .Compound_Dir file. Example: # cd /opt/unix62 # cp -r * /f0 # cp .Compound_Dir /f0 9. Change to root directory and umount the diskette. Example: # cd /
# umount /dev/fd0c 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: C:\> ncenv (Enter) C:\> d: (Enter) D:\> sh (Enter) Now your prompt will be $ 2. Change to /opt directory and create a new directory. Example: $ cd /opt $ mkdir nt62 3. Change to the /opt/fox/ciocfg/api directory. 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 Where: CPLBUG is the letterbug of the CP or Micro I/A or AW70X. 5. Tar all files and directories to diskette and eject it. Example: $ tar cvf a: ON THE UNIX STATION 1. Open a VT100 session. 2. Change to the /opt directory and create a new directory. 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 Where: CPLBUG is the letterbug of the CP or Micro I/A or AW51X. 6. Open ICC and verify that all compounds and blocks were loaded.
saveh50 (Legacy Historian Backup Procedure)
50 series: cd /opt/fox/hstorian/bin 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
SCSI Bus Configuration Guide
When choosing the components on a SCSI bus, the user must be aware of the limits within which a SCSI bus properly operates. The total equivalent SCSI length must be less than or equal to 6 meters. It should be noted that the sum of the physical lengths of the interconnecting cables is only one factor in the total length. Each device on the SCSI bus, including the processor, adds a portion to the overall length. The table below gives the dquivalent SCSI length for each device and cable. In practice, the system does not cease to function at lengths just beyond six meters, but the reliability of the bus begins to erode at that point. Device Equivalent Model 50 processor Model 51A processor Model 51B processor Model 51C processor Size A peripheral Size A peripheral cable Size B peripheral Size B peripheral cable Size D peripheral Size D peripheral cable Size D 50/68 pin cable Size D 68/68 pin cable P0170NX SCSI cable 1.5 P0970JR SCSI cable P0970KF SCSI cable P0970KG SCSI cable P0970KJ SCSI cable P0970QS SCSI cable P0970FZ SCSI cable P0971MK SCSI cable P0971ML SCSI cable P0971MX SCSI cable P0971MY SCSI cable P0971RH SCSI cable SCSI Length 0.5 meters 0.71 meters 1.6 meters 1.6 meters 1.6 meters 0.16 meters 0.8 meters 0.16 meters 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
Select Screen - Setting up to have * in CP Name Field When Select Screen is Called
cd /usr/fox/wp/data Will need to edit the file named: wp50_glbls or wp51_glbls Look for line that says: SELCPSRH= and change it to read SELCPSRH=* As of v4.3 and v6.1 the file to use is wp51_glbls.all instead of wp51_glbls which gets written over at time of reboot.
Sequence Block - Editing Logic
Sequence code can be edited off line and put on the AP/AW and then compiled. The .s file is the source and the .r file is the report. cd /usr/fox/ciocfg or /opt/fox/ciocfg cd COMPOUND1 (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
Sequence Block - Executing A Script From

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 Switches you to the Bourne shell Bourne Shell AW/WP/VT100 default csh Switches you to the C shell
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
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.
Shutdown - AP20 Procedure

Operators must switch APs if on a WP30 hosted by a different AP. cd / /etc/shutdown continue? Y
will put you in single user (Maint) mode To restart an AP: telinit 2
Shutdown Problem with 51 Stations Will Not Shutdown When Shutdown Selected
If the AW51 is running AIM* historian and selecting the SHUTDOWN button in the SHUTDOWN-AW menu has no effect, the reason is that the involved shutdown.sh script in the directory /usr/fox/wp/bin contains the following command line: /opt/fox/hstorian/bin/histonoff v OFF Since there is no historian to shutdown with this command, it causes the shutdown script to hang. Use vi to edit the file usr/fox/wp/bin/shutdown.sh and change the line /opt/fox/hstorian/bin/histonoff v OFF to: hps | grep hist_srv if test $? eq 0 then /opt/fox/hstorian/bin/histonoff v OFF sleep 1 fi This problem is scheduled to be fixed in v6.3 release.
Signal Conditioning Parameters

Parameter: SCI ANALOG INPUT SIGNAL CONDITIONING INDEX NUMBER CONDITIONING 0 NO CONDITIONING 1 0-64000 RAW COUNTS LINEAR 2 (0-10VDC) 1600-64000 RAW COUNTS LINEAR 3 (4-20MA) 12800-64000 RAW COUNTS LINEAR 4 0-64000 RAW COUNTS SQ. RT. 5 12800-64000 RAW COUNTS SQ. RT. 6 LOW CUTOFF 0-64000 RAW COUNTS SQ. RT. 7 LOW CUTOFF 12800-64000 RAW COUNTS SQ. RT. 8 PULSE RATE 9 LOW CUTOFF 1600-64000 RAW COUNTS LINEAR 10 LOW CUTOFF 12800-64000 RAW COUNTS LINEAR 20 TYPE B THERMOCOUPLE 21 TYPE E THERMOCOUPLE 22 TYPE E THERMOCOUPLE EA-2 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 PLATINUM RTD (DIN) 43 PLATINUM RTD (EIC) 44 PLATINUM RTD (SAMA) PARAMETER: SCO ANALOG OUTPUT SIGNAL CONDITIONING: 1 0-64000 RAW COUNTS LINEAR 2 1600-64000 RAW COUNTS LINEAR 3 12800-64000 RAW COUNTS LINEAR
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 (gives scanner connections) CP10 max= 12 CP30 max= 30 CP40 max= 30 dt om_server (gives server connections) CP10 max= 12 CP30 max= 20 CP40 max= 20
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] -d device receive packets from network using specified device. -c maxcount Quit after capturing maxcount packets -i filename Display packets previously captured in filename -o filename Save captured packet as filename. Example: snoop -d le2 -c 2000 -o /usr/tmp/snoopinfo (To capture 2000 packets and redirect to /usr/tmp/snoopinfo) To view packets in /usr/tmp/snoopinfo: snoop -i /usr/tmp/snoopinfo (See HH907 for more information)
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
Configuring som/rsom output via crontab: Create a file with som/rsom commands you want to output to a file: CP30 CP0001 opdb f opvr 0 f conn f sconn f q 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 Create an executable file for your crontab entry: vi cp_som_out /opt/fox/bin/tools/rsom icp1_info tcp1_out > /dev/null (Should be the only line put in this file.) Add cp_som_out to crontab and test.
Usage: sort [-cmu][-ooutput][-T directory][-ykmem][-dfiMnr][-btx][+pos1[-pos2]][fname] -c Check input is sorted according to ordering rules -m Merge only, the input files are already sorted -u unique -ooutput use output filename instead of standard out -T directory name of dir to place temporary files -ykmem use kmem instead of system default memory size -d dictionary order -f fold lower-case letters to upper case -i ignore non-printable chars. -M compare as months -n sort numeric string by arithmetic value -r reverse the sense of comparisons -b ignore leading blanks -tx use x as field separator char. 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.
sort
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
Stamp-ID Changing Incorrect
If the Stamp ID is incorrect for a diskette, note the 5-digit media id requested by Software Install and perform the following steps. cd /tmp 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
Status Taps to FBM07
Status Taps are covered in B0193AC rev K (installation manual) on pages 51-53. Wiring: Status Tap A to FBM07 CS; Status Tap Comm to FBM07 + Note: If this is reversed, the point locks into alarm condition. Wiring to Other Device: Status Tap A to + of device Status Tap Comm to - of device The status tap has an internal 1/8 amp fuse. The status tap when connected to an FBM07 will show +24v between A and Comm givi ng +24v on the input of the FBM07 point. The contact light on the nose cone will be out when all is NORMAL and not in alarm. Point logial status Not True. The Status Taps internal contact closes when in alarm causing the voltage on A to Comm to drop to approximately +.82v. The FBM point goes to .82v and the indicator light on the nose cone comes on. The logical state becomes TRUE and the point is in alarm. Also Note: If an FBM07 is used for the status tap connections, then only one point of each pair point (i.e. pts 1 and 2 are paired by grounds. Pts 3 and 4 are paired by their grounds, etc .) c an be connected or both points will track each other. Therefore: Voltage High is Logical Low and no alarm Voltage Low is Logical High and in alarm Contact between status tap pt A and Comm is open for normal no alarm Contact between status tap pt A and Comm is closed for problem in alarm. If using a meter to measure the contact you must put the Positive lead on A and the negative lead on Comm.
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 Above to get a summary of swap space usage.
swap l Shows partition swap space and file swap space. To add swap space to a 51: mkfile 12m /opt/swap vi /etc/vfstab (add to file on last line) You must be certain to add the following line with the correct spaces, tabs, etc. or your machine may not boot. /opt/swap- - swap - no swap -a /opt/swap To add swap space to a 50: vi /etc/fstab (add to file on last line) You must be certain to add the following line with the correct spaces, tabs, etc. or your machine may not boot. /opt/swap swap swap rw 0 0 swapon a
swi_pars.cfg file
The file /usr/fox/exten/config/swi_pars.cfg gives information such as PSAP, STA_LBUG, LOG MAC ADDRESS, etc.
Switches v7.x 8-Port Managed Switch (P0972MF) (HH1019)
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, reconnect per B0400DV. AW70 or WP70 Setup 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 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 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.
Switches v7.x 16-Port Managed Switch (P0972MJ) (HH1023)
The 16-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 address is not known, then the switch must be programmed via its serial port. See the manufacturer's Literature. Identification Invensys Part Number: P0972MJ Smart Switch: 2200 Cabletron Systems: 2H258 - 17R (Firmware = 05.04.19) Cabletron 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 a PC (Hyper-Terminal) serial port directly into the switch's serial port using the cable and adaptor provided with the switch. This cable, adaptor and switch literature must be stored in a secure location at site. You may need it again in the future. Serial Communication Setup Set up the PC Serial Port: A) 8 data bits B) 1 stop bit C) No parity D) 19,200 baud rate E) Flow control XON - OFF F) Telnet terminal IS = ANSI G) Emulation = VT100 H) ASCII setup = force 7 bit 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. If none, just hit enter. Configuring the Switch 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 "Security" (Enter) "Passwords" (Enter) Set a password for Read Read-Write and Superuser Return (back to the Device Menu) Device Configuration Menu (Enter) General Configuration IP address = 151.128.79.XX [Valid Range 151.128.79.1 through 192] Subnet Mask = 255.255.0.0 Module Name = Cable A (or Cable B) (Set time and date if not correct) Return 802.1 Configuration Menu
Spanning Tree Configuration Menu Spanning Tree Configuration Current STP Mode = NONE Return to Device Configuration Menu Port Configuration Menu Ethernet Interface Configuration Select one port (Enter) Full Duplex Flow Control = ENABLED Half Duplex Flow Control = ENABLED Save to All Ports Return and SAVE the configuration and EXIT. Switch Power Up When the switch first receives power, it will not communicate to connected devices for about 1 minute. Wait this amount of time before expecting an "alive" response from your ping command. Note that it is possible to power the switch from two sources of electricity. There is also a reset button on the switch. Pressing it once will result in communication loss for about one minute. Pressing it a second time (within the one minute) could result in communication loss for several minutes while extensive diagnostics are run. 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 Call a VT100 terminal. csh cd /usr/openwin/bin setenv DISPLAY=0:0 xterm & 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).
Switches Cisco 24 Port Fiber Configuration Instructions (HH1039)
The 24-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. This switch must be programmed via its serial port. See the manufacturer's Literature. Identification Invensys Part Number: Not a part numbered item. Cisco Switch: 3550-24-FX-SMI Cisco WEB site http://www.cisco.com 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. Documentation for the switch can be downloaded from the Cisco website. Wiring for Configuration 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. Check Running Switch Status This is with an IP address and the first two ports in use. 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>
Switch Configuration Configuring 100 MHz

HH#: HH1019 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. AW70 or WP70 Setup 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 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 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.
SYS Key Blink Status
The sys key flashes the following: Blinking Red At least one unacknowledged equipment failure Solid Red At least one acknowledged equipment failure. Blinking Normal No equipment failed but a previous failure is unacknowledged. Solid Normal No equipment failed The default behavior of the SYS blink when one station of a fault tolerant pair fails is to blink yellow. There is a quick fix for Foxview to change this behavior to a red blink that may allow an audible alarm for priority alarming.
System Definition Configuration for MESH Class C Instructions
The following procedure was used to add a MESH system including P91s, P92s, ATSs, and FCP270s to an existing legacy system with 3 nodes without rebooting any control stations on the legacy side. Import Ccurrent SysDef into SysDef 2.8. Make sure that all stations on the existing system are marked DONE Take note of existing node NSAP addresses. Create the HPS Network. Create the Switches. Create the Stations (P91, ATS, FCP, etc.) Drag the Switches to the HPS Node Attach Switches to Switches Attach Stations to Switches Drag existing Node to the newly assigned ATS Delete the LAN Interface Delete the Carrierband Lan Network Confirm that all NSAPs are still same (NSAP for ATS modules should be 000000) Generate version specific commits (Super Commit is a Day 0 on the MESH and Day 1 on the Nodebus.
System Management Counters (getting data and resetting)
Start remd with no System Management running on this station. cd /opt/rem/remd nohup remd & run remv in batch mode cd /opt/rem/remv remv d@ -s@ -cr > /opt/tmp/file1 (the r in cr resets the counters after sending counter information to file1) This command can be run interactively. You should wait for one hour to get counter information after resetting because the thresholds for these counters are based on one hour of data. To get data without resetting counters: remv d@ -s@ -c > /opt/tmp/file2 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 FOR SYSTEM MANAGEMENT COUNTER DETAILED INFORMATION, SEE COUNTERS.
System Monitor Messages Capturing to a File
To capture all system monitor messages to a file, You can create a smon_log file which will capture date and time of all the sysmgm activities. It works in I/A v6.2 or later. However, it will capture the data from the time the smon_log file was created Here is the procedure: CREATING A "smon_log" FILE, 1. On NT, open a Command Prompt window and change to korn shell (d:, ncenv and sh). On UNIX, open a VT100 window. 2. Change to the /opt/fox cd /opt/fox 3. If the sysmgm directory doesn't exist then create it. mkdir sysmgm 4. Change to the sysmgm directory. cd sysmgm 5. Make a sysmon directory and change it to there. mkdir sysmon cd sysmon
6. In the /opt/fox/sysmgm/sysmon directory, create a file and name it smon_log. touch smon_log 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 2002-04-29 14:09:59 CP3001 Software Manager SYSMON -00021 Checkpoint Success. A CP Reboot will show: 2002-04-29 14:09:59 CP3001 Software Manager SYSMON -00021 Power up rebooted OK. 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.
System Monitor Processes

smon_ech smon_queue smon_strh smon_nm (there will be one of these (smon_nm) Network Manager processes for every switch on the system)
The AW/WP was configured as a System Monitor WP and System Monitor Notification WP, however, The WP lacks the System Monitor Notification and cannot make changes through Equip Chg. The first thing to do is to check the configuration to make sure that this WP/AW is configured properly as a System Monitor WP. We have had a station to be configured as a System Monitor WP yet still cannot select Equip Chg. cd /usr/fox/sysmgm/sysmon bpatch destact.cfg 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.
System Monitor Problem with WP/AW configured as System Monitor WP But Cannot Access Equip Chg on the Display
System Monitor - Restarting/Reinitializing

To stop and restart the system monitor: ps -eaf | grep smon kill -9 PID (PID=Process ID Number found when doing the ps -eaf) (kill both smon processes) nohup /usr/fox/sysmgm/sysmon/smon_ech & To reinitialize/reinstall the system monitor: cd /usr/fox/sysmgm/sysmon mv smon_strh smon_strh.new mv smon_ech smon_ech.new cd ./fs_util mv fs_util fs_util.new cd /usr/fox/sp/files/pkg_inits p_init.SYSMO <host station letterbug> NOTYET
tail command
Syntax: tail [+n | -n] <file> Display end of file, by default last 10 lines -n Last n lines +n Line n to end of file
Tape Drive Checking the 4mm tape drive status

mt f /dev/rst9 status This will give the online/alive status.
tar Command (on NT)

view diskette: tar tvf a: copy diskette: tar cvf a: extract: tar xvf a:
TCP/IP (valid addresses for each NSAP)
Proper TCP/IP Range for NSAP Addresses in Multinode Systems NSAP TCP/IP Address Range For Node I000101 151.128.16.65 thru 151.128.16.128 I000102 151.128.16.129 thru 151.128.16.192 I000103 151.128.16.193 thru 151.128.16.256 I000104 151.128.17.1 thru 151.128.17.64 I000105 151.128.17.65 thru 151.128.17.128 I000106 151.128.17.129 thru 151.128.17.192 I000107 151.128.17.193 thru 151.128.17.256 I000108 151.128.18.1 thru 151.128.18.64 I000109 151.128.18.65 thru 151.128.18.128 I000110 151.128.18.129 thru 151.128.18.192 I000111 151.128.18.193 thru 151.128.18.256 I000112 151.128.19.1 thru 151.128.19.64 I000113 151.128.19.65 thru 151.128.19.128 I000114 151.128.19.129 thru 151.128.19.192 I000115 151.128.19.193 thru 151.128.19.256 I000116 151.128.20.1 thru 151.128.20.64 I000117 151.128.20.65 thru 151.128.20.128 I000118 151.128.20.129 thru 151.128.20.192 I000119 151.128.20.193 thru 151.128.20.256 I000120 151.128.21.1 thru 151.128.21.64 I000121 151.128.21.65 thru 151.128.21.128 I000122 151.128.21.129 thru 151.128.21.192 I000123 151.128.21.193 thru 151.128.21.256 I000124 151.128.22.1 thru 151.128.22.64 I000125 151.128.22.65 thru 151.128.22.128 I000126 151.128.22.129 thru 151.128.22.192 I000127 151.128.22.193 thru 151.128.22.256 I000128 151.128.23.1 thru 151.128.23.64 I000129 151.128.23.65 thru 151.128.23.128 I000130 151.128.23.129 thru 151.128.23.192 I000131 151.128.23.193 thru 151.128.23.256 I000132 151.128.24.1 thru 151.128.24.64 I000133 151.128.24.65 thru 151.128.24.128 I000134 151.128.24.129 thru 151.128.24.192 Single Node System NSAP TCP/IP Address Range For Node I000001 151.128.8.65 thru 151.128.8.128
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 -a update only access time -m update only modification time -c do not create file if it doesnt exist. The touch command will change the date and time of creation of a file to the current date and time. To create a temporary file to find all files newer than. touch filename.new 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.
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.
Troubleshooting v7.x Network (HH1050)
Basic Network Checks o Verify that all Workstations have a splitter cable o Verify that the splitter combiner is connected to serial port "A" and the proper NIC or network interface o Verify that the RCNI cables go to the proper switch ("A" or "B") o Verify that the Ethernet cable from the splitter combiner to the RCNI is good. Verify that the Ethernet cable connected between the Splitter cable and the RCNI is Rev C or igher for P0971XK, XL, XM and XN. Refer to SI 0-00528 for kits AG100WD, WE, WF & WG. o Verify that on each NCNI pair one switch is set to "A" and the other set to "B". o Verify that the NCNI is connected to the proper switch (A or B) If there is more than one switch in series for each cable verify that there are no crossed cables between switches. o 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. o 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. o 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. o 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", 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. 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) 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 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. 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. 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. Verify the link leds are active on the RCNI Verify the status led of the RCNI is green. There are two status leds in the upper right corner of the RCNI. If the status leds are red/green the RCNI will not communicate properly. Power down and up to try and correct the problem. Verify all cabling Replace the RCNI Debugging NFD Problems (General) 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.
tput - Clear Screen
The tput command will clear the screen. Usage: tput clear
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)) Closed Loop Technique: 1. Turn the integral time to its highest setting (set to 10 minutes per repeat) 2. 2. If used, turn the derivative time (rate time) to zero or its minimum 3. Decrease the proportional band until the loop maintains a small sustained cycle. 4. 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 Open Loop Technique: 1. Place the controller in manual 2. 2. When the process is sufficiently stable, make a small change in the controller output called a step change. 3. Then set the controller adjustments to: Kc=1/RL where R=%change in measured var/minute divided by %change in controller output Pc=RL(100) Ti=4L where L=Apparent dead time Td=L/2 Use the open loop method on slow processes, such as temperature and composition. Also note that the L parameter is more important then R. Also note that if R continues to increase, these tuning rules do not apply. Two important things to note: As the proportional band is increased, the loop will tend to oscillate. Also, as the proportional control is decreased, the offset becomes smaller, but never reaches zero. Cascade Control: Tune the secondary controller first for tight control. The secondary controller should be faster. The primary loop will see the secondary loop as another lag. Then tune the primary loop as you would Any other loop. The amount of lag seen in the primary loop depends on the tuning of the secondary loop.
DO NOT HAVE EXACT ON BOTH MASTER AND SLAVE. Set parameters on secondary then turn it off and leave exact on master. Example tuning process: 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 print all information -m print machine hardware name -n print nodename -p print hosts processor type -r print operating system release -s print name of operating system -v print operating system version
Upgrade Procedure CP30 or CP40 with legacy FBMs to CP60(HH983)
Some clients wish to upgrade their CP30 or CP40 to a CP60 and retain their legacy FBM's. The FBI10E is used to communicate with these legacy FBM's but the procedure is not obvious. Ensure that no parameter from this CP is displayed on a CRT, anywhere in your system before STEP # 3 is performed. 1. Configure a new CP60 letterbug in System Definition and install it in the usual manner. Insert the CP60 and verify that it boots correctly. 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.
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
Upgrade Utilities
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 [<temp dir>] <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.
Utilities: File2dsk and Dsk2file Issues with Win2000 and XP (HH989)
Some users cannot get the FILE2DSK and DSK2FILE tools to work with Win 2000 and Win XP operating systems. These two operating systems have two command line windows. WINNT\System32\command.com and WINNT\System32\cmd.exe The cmd.exe program has failed to operate correctly with the tools FILE2DSK and DSK2FILE on some computers. The command.com program has been tested and confirmed to work with the tools FILE2DSK and DSK2FILE on Win NT, Win 2000 and Win XP. You should use command.com when you need to run these tools. It can be started from the Start - Run window.
Utilities: Upload, Shrink, Checkpoint, Save_all

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. 1. 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 2. 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. 3. 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. 4. 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 shows parameters settable :set wm=20 sets right margin at 20 spaces :set nu sets number display of each line :set ai indent lines until go into escape mode :q! exit without saving :n move to that line number :x,ymz move line between x & y to a position following z :x,ycoz makes copy of lines from x to y and places them after z :x,ywfilename copy lines from current file to new file :x,yw>>filename append lines to existing file :e edit another file while in vi :w save changes to current file :ZZ saves and exits :wq! writes and quits :%s/oldtext/newtext/g (global search and replace) Global Search and Replace: :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///
VI - Inputting AND Editing Text

i insert text at cursor l insert mode at beginning of line a append text after cursor A add text to end of line start new line below current one start new line above current one r replaces letter cw change a word or text cc change line of text x delete character where cursor is dw delete a word dd delete a line D delete from cursor to end of line 3x delete 3 characters 3dw delete 3 words 3dd delete 3 lines p paste deleted word/character/line after cursor
P paste deleted word/character/line before cursor yw/yy yank a word/yank a line to be pasted y1y copies entire line J joins line together . repeat commands u undoes changes to last altered text U undoes all last changes to current line 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 will search for next occurrence, previous occurrence c Change text to end of line
VI - Moving Around A File

w first letter of next word b first letter of preceding word e to end of word l forward one space h back one space k up one line j down one line 0 to beginning of line $ to end of line :set number to se numbered lines nG to specific line number G to end of file 1G to beginning of file - to previous location in file H to go to top of screen M to go to middle of screen L to go to bottom of screen Ctrl-Y scroll up one line Ctrl-E scroll down one line Ctrl-B scroll back a full screen Ctrl-F scroll forward a full screen Ctrl-L refreshes screen Ctrl-D scrolls down half a screenful Ctrl-U scrolls up half a screenful
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. -i Report the number of interrupts per device. -s Display the total number of various system events since boot. -S Report on swapping rather than paging activity. This option will change two fields in vmstat's ``paging'' procs memory page disk faults cpu r b w swap free re mf pi po fr de sr f0 s3 -- -- in sy cs us sy id 0 0 0 4188 2796 0 1 0 0 0 0 0 0 0 0 0 16 276 244 3 5 91 0 0 0 61800 2372 0 2 0 1 1 0 0 2 1 0 0 1785 322 271 10 5 85 procs - Report the number of processes in each of the three following states: r in run queue b blocked for resources (I/O, paging, and so forth) w runnable but swapped memory - Report on usage of virtual and real memory. swap amount of swap space currently available (Kbytes) free size of the free list (Kbytes) page - Report information about page faults and paging activity. The information on each of the following activities is given in units per second. re page reclaims, see the -S option for how this field is modified. mf minor faults, see the -S option for how this field is modified. pi kilobytes paged in po kilobytes paged out fr kilobytes freed de anticipated short-term memory shortfall (Kbytes) sr pages scanned by clock algorithm disk - Report the number of disk operations per second. There are slots for up to four disks, labeled with a single letter and number.The letter indicates the type of disk (s = SCSI, i = IPI, and so forth); the number is the logical unit number. Note : An idle time that is consantly below 50 percent should be investigated.
VT100 Unix Initialization Files
File executed at login into the C Shell: /.login File executed at login into the Bourne Shell: /.profile File executed each time a shell is spawned in C Shell: /.cshrc File executed upon logout of the C Shell: /.logout
wc Command
Syntax: wc [-cwl] <file-list> Counts characters, words, and lines of files -c Characters -w Words -l Lines
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).
Work Files for Control Processors

20 series: /usr/fox/ciocfg/CPLBUG/*.wf 50 series: /opt/fox/ciocfg/CPLBUG/*.wf
wp_dta file AW and WP Peripheral File
As of the v3.3 release, the System Configurator started creating the WP peripheral configuration file, /usr/fox/sp/wp_dta, with a P put in byte 9 of each record (first byte is 0). For 50 series stations a P indicates that no touchscreen is configured for the primary GCIO. While for WP20s and WP30s, a binary 0 means no touchscreen and a P would mean that a touchscreen with the letterbug of P is configured. Note, if a WP20 or WP30 is configured for a touchscreen this is not a problem. The AW and WP peripherals (Touch Screen, GCIO and Modular Kayboards) are assigned in the System Configurator. A file is transferred to the station during the Software Installation which is read by the station on bootup to determine what equipment has been specified. This binary file located in /usr/fox/sp can be read by using bpatch. You should copy your wp_dta file before using bpatch on it.
bytes 0-6 WP letterbug plus the null terminator byte 7 Secondary GCIO/Touchscreen letterbug, 50 series only 00 (Hex), no secondary GCIO and no touchscreen S (ASCII), secondary GCIO and no touchscreen 6 (ASCII), secondary and touchscreen byte 8 WPIO Primary Station ID 01 (Hex), no multiscreen 02 7F (Hex), multiscreen present, value assigned by SysCfg byte 9 Primary GCIO/Touchscreen Letterbug 00 (Hex),if WP20/30 no touchscreen, if 50 series no primary GCIO and no touchscreen P (ASCII), no touchscreen for primary GCIO, 50 series only 2 (ASCII), if 50 series, touchscreen configured for primary GCIO, and if WP20/30, letterbug of touchscreen C-Z (ASCII), touchscreen configured and Multi-screen WP20/30 Only, letterbug assigned by SysCfg byte 10 Modular Keyboard #1 Letterbug 00 (Hex), no modular keyboard
1 (ASCII), modular keyboard configured and not multiscreen C-Z (ASCII), modular keyboard configured and Multiscreen, WP20/30 Only, letterbug assigned by SysCfg byte 11 Modular Keyboard #2 Letterbug 00 (Hex), no second modular keyboard 3 (ASCII), second modular keyboard configured and not multiscreen C-Z (ASCII), second modular keyboard configured and multiscreen, WP20/30 only, letterbug assigned by SysCfg byte 12 Numeric Keypad Letterbug 00 (Hex), no numeric keyboard 1 (ASCII), numeric keypad located on first modular keyboard 2 (ASCII), numeric keypad located on second modular keyboard byte 13 Alphanumeric/Third Modular Keyboard Letterbug 00 (Hex), no keyboard 0 (ASCII), alphanumeric keyboard and no multiscreen 4 (ASCII), third modular keyboard and no multiscreen A (ASCII), alphanumeric keyboard and multiscreen, WP20/30 only C-Z (ASCII), third modular keyboard and multiscreen, WP20/30 only letterbug assigned by SysCfg byte 14 Mouse/Trackball or Fourth Modular Keyboard Letterbug 00 (Hex), no mouse, trackball, or fourth modular keyboard 2 (ASCII), mouse or trackball configured, WP20/30 only 5 (ASCII),fourth modular keyboard (50 series only) B (ASCII), alphanumeric keyboardmouse or trackball and multiscreen, WP20/30 only byte 15 Multi-Screen Initial Owner of Device 00 (Hex), not initial owner of shared dev, always 00 for 50 series 01 (Hex), if initial owner of shared devices, or WP20/30 not configured for Multi-Screen Each row represents one WP or AW. The G2BOOT, G3BOOT and G4BOOT are the default letterbugs on every I/A AW. The TESTWP is the WP for testing for this example. There is a hex portion on the left and an ASCII portion on the right. The x0 column in the hex portion 54 is the hex code for ASCII 0 column T of the letterbug. TESTWP, above is configured for a single CRT, without touch screen and no GCIO interface. The file only changes for the WP options for touch or no touch, GCIO or no GCIO and Modular Keyboards (MK) (1 or 2) for the main CRT and/or the second CRT. There are no changes for mouse or trackball, nor when the color TGX card is selected. Adding a second CRT without touch and without MK but including GCIO did not make any change to the file. If you see the S on the ASCII side or a P and you know that you do not have linked WPs, then check your System Configuration to ensure there is a GCIO for each CRT that you have MKs configured on.
Wyse Terminal Settings When Used As An Alarm Printer

DTR =instead of xoff Parity = odd instead of none
Wyse Terminal - Procedure to use laptop as Wyse Terminal

Practical System Tips

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Practical System Tips

Uploaded by

Copyright:

Available Formats

Practical System Tips

Technical Reference Manual

Access Levels Using the setacl Command

add_periphs (50 series)

AIM Historian Starting and Stopping

AIM Historian problem with corrupt RTP file

AIM Historian Troubleshooting Tools

Alarm Manager Install Files

Alarm Manager Problem with AM Display Getting Stuck on the Screen

Alarm Managers Quitting Alarm Managers that are not quittable

Alarms Common Alarm Group (CAG)

Alarm Server Task ast Problem

alias - Creating a Pseudonym for a Command

Annunciator Keyboard Troubleshooting Annunciator Keyboard Installation Problems

0123456789abcdef G2BOOT...2...02. G3BOOT...2...02. G4BOOT...2...02. 3AWB01.......... 3AWC01.......... 3AWE01...P1..... <-

06: 07: 08: 09: 0a: 0b: 0c: 0d:

4WP201.......... 4WP301.......... 2WP201...P1.102. 2WP301...P1.102. 2AWB01.......... 3AWBI1.......... 3AWD01.......... 3WP501..........

Annunciator Panel WPLBUGAApan or WPLBUGAAtab Modification

Archiving Historian - Backup your historian archive Message

ATS Information - (Address Translation Station)

ATS / Time Configuration (MESH: Class C)

awk - PATTERN MATCHING PROGRAM

Background - Running files in

Backup AP - Configuring WPs for AP Switching on 20 series stations

backup and restore Procedure

Backups - Level 0 (Complete) Backup

Backups - Level 9 (Incremental) Backup

Backup Using A Remote 50 Series Tape Drive

Backups - Checking Save-All Diskettes Integrity

Backups Using the dd command with bs and count

Backups AP20 - Copying From Primary Hard Drive

Backups - Recommended Directories To Back Up

Backups AP20- Checking Streaming Tapes Integrity

Backups - Checking Tape Stamp On 50 Series

Backups - AP20 Streaming Tape

BACKUPS - Saving Multiple Directories/Files to Tape 50 series stations

Boot Procedures for Troubleshooting an AW/AP/WP that wont boot

Boot Partitions On PC - Switching

On AP20: /usr/fox/bin/tools/bpatch <filename> On AP50/51:

C Program Compiling 20 Series

Cable Pinouts Serial cable to null modem

Cancel Print Job

cancel lp1 110 (110 being jobname)

Checkpoint Files Location

/usr/fox/sp/files DB(CPLBUG).UC Current DB(CPLBUG).init Initialization File BB(CPLBUG).UC Backup file

Checkpoint File Maximum Sizes

Checkpoint File Rebuilding Corrupt Checkpoint File(HH953)

Concatenating Drives (50 series)

Concatenation Problem / add-to-sys Problem Concatenating Drives

CP60 Installation/Grounding Checklist

CPs Control Processor Maximum Values and Loading

Converting 20 series save-alls to 50 series save_alls

Converting Displays Problem - Unix to NT

Copy Files from one AW/WP to All Other Hosts

Copy - unix2dos and dos2unix (50 series)

Copy From Hard Drive to Floppy

tar cvf /dev/fh0 /usr/fox/hstorian/bin/hed*.* cvf=copies rvf=appends tvf=dir of disk

Copy From Floppy to Hard Drive

Copying ASCII files to DOS diskette on 50 Series

Copy Stamped (5.25) With One Drive Available

Core Files- Reading

Counters Station Block Counters

Counters Application Sublayer Counter Thresholds

tar cvf /dev/fh0 /usr/fox/hstorian/bin/hed. cvf=copies rvf=appends tvf=dir of disk

mput open *put