Procedures for IOC evaluation

1) bootShow - which vxWorks along with all other boot parameters

2) dbhcr > /var/iochw.txt – gives database hardware configuration report and sends it to a txt file.

3) dbior > /var/dbior.txt – tells if hardware is communicating with software.

4) Evaluate st.cmd and RELEASE files

5) Boot from common<server>.cmd

IOC Evaluation Procedures and Explanation

A script exists for this purpose. Type iocinfo in the /var directory of your IOC’s directory.

spyClkStart                                        Starts the clock for spy – Only reports when you type spyReport.

date > /var/iocdate.txt                        Tells the time-of-day on the IOC.

bootShow > /var/iocboot.txt              Gives the ioc’s boot parameters, which includes which version of vxStats

                  it is booting.

ifShow > /var/iocif.txt                         Tells the network interface statistics.

netStackSysPoolShow > /var/iocsyspool.txt             Tells the network system memory pool resources.

netStackDataPoolShow > /var/iocdatapool.txt          Tells the network data memory pool resources.

inetstatShow > /var/iocnetstat.txt      Prints the network connections, routing tables, interface statistics,

                                                           masquerade connections, and multicast memberships for vxWorks.

                                                           recq and sendq should be 0. If not, run again to make sure. If it is

                                                           not 0, there is a problem.

i > /var/ioci.txt                                    Shows the vxWorks tasks running on the ioc. If STATUS shows a task

                                                           as suspended, there is a problem.

                                                           tr TID may work to resume the task.

routeShow > /var/iocroute.txt             Gives the IP routing table on vxWorks and verifies that the gateway is

                                                           defined and setup correctly.

casr(1) > /var/ioccasr.txt                     Channel Access Server Report – tells how many connections exist and

                                                           what clients and ports are connected. Look for Channel Count

                                                           and ip:port#

spyReport > /var/iocspy.txt                Formatted version of spy. Displays the top CPU tasks/ threads on the ioc.

                                                           Look at the total %cpu being used. Contact the designer of the problem

                                                           task to decide on a resolution.

spyClkStop                                         Stops the clock for spy. spyReport is no longer active.

Running the script will produce the following files in var

-rw-r-----    1 vxuser   engr        1031 Nov 11 14:25 iocsyspool.txt

-rw-r-----    1 vxuser   engr        4122 Nov 11 14:25 iocnetstat.txt

-rw-r-----    1 vxuser   engr        1113 Nov 11 14:25 iocif.txt

-rw-r-----    1 vxuser   engr        29 Nov 11 14:25 iocdate.txt

-rw-r-----    1 vxuser   engr        1204 Nov 11 14:25 iocdatapool.txt

-rw-r-----    1 vxuser   engr        514 Nov 11 14:25 iocboot.txt

-rw-r-----    1 vxuser   engr        15040 Nov 11 14:26 iocspy.txt

-rw-r-----    1 vxuser   engr        781 Nov 11 14:26 iocroute.txt

-rw-r-----    1 vxuser   engr        42196 Nov 11 14:26 ioci.txt

-rw-r-----    1 vxuser   engr        2749 Nov 11 14:26 ioccasr.txt

-rw-r-----    1 vxuser   engr        178090 Nov 11 14:26 ioccasr2.txt

It is possible that the IOC could be having so many problems that the script does not run, but it is unlikely.