(Page 1 of 1 in this chapter) Version


Chapter 4

Verifying the Installation


4.1 Introduction
4.2 Verifying the TX 2000/TX 3000 is Installed Correctly
4.2.1 Windows NT
4.2.2 UnixWare Successful Installation 33

Unsuccessful Installation 33

4.2.3 Solaris Successful Installation 34

Unsuccessful Installation 34

4.3 Viewing the Statistics for the TX 2000/TX 3000 Boards
4.3.1 Windows NT
4.3.2 UnixWare
4.3.3 Solaris
4.4 The tx2diag and tx3diag Utilities
4.5 The cpcon Utility

4.1 Introduction

This chapter lists the procedures to verify that your TX 2000/TX 3000 board is installed and configured properly.

4.2 Verifying the TX 2000/TX 3000 is Installed Correctly

This section provides instructions for confirming your TX hardware/software is configured and working correctly.

4.2.1 Windows NT

After you have installed the TX software and rebooted your Windows NT system, you can verify that the hardware/software installation is successful with the following steps:

To run Event Viewer, click Start, point to Programs, then Administrative Tools, and then click Event Viewer. In the Event Viewer system log, you will see one or more entries from the source:

     TxNtPktD

4.2.2 UnixWare

If you are using a UnixWare system, you can check to see whether or not the TX driver loaded successfully by rebooting and watching for the driver initialization message from the TX driver. This is one of the first messages displayed and goes by fast. The initialization message can indicate whether or not the TX 2000/TX 3000 board(s) and driver are installed correctly.

Successful Installation

For each board that is installed and configured, you should see a message similar to the following:

NMS TXn000 Driver Unit(0) V(202) irq(10) addr(0x000cc000)


 Unsuccessful Installation

An unsuccessful installation will result in a message similar to this:

TXn000 driver no board for unit(0)


This indicates that the Dual Port RAM driver has not recognized the
TX 2000/TX 3000 board on the bus at the specified memory location.

Possible explanations:

Recheck the board switch settings. If they are correct, check the current configured value by looking at the contents of the configuration file, /etc/conf/sdevice.d/tx2.

The file looks similar to this:

tx2 Y 0 5 1 10 0 0 cc000 cdfff -1 0

In this example, the sixth column 10 indicates the IRQ setting and the ninth column cc000 indicates the Dual Port RAM address.

These two values must agree with the switch settings on the TX 2000/TX 3000 board. If the driver needs to be reconfigured, use txninst to delete the driver and then add it back in with the new configuration values.

Note: Do not edit /etc/conf/sdevice.d/tx2 directly; the changes will not take effect, even if the kernel has been rebuilt. If you are interested in the details of how this configuration is handled, you can examine the txninst script, which may be found in the /usr/bin directory.

4.2.3 Solaris

If you are using a Solaris system, you can check to see whether or not the TX driver loaded successfully using the following steps:

  1. Log on as root.

    
    
  2. Navigate to the /var/adm/ directory.

    
    
  3. View any of the messages.* files to see the last few pages of the system log file.

    
     Successful Installation

For each board that is installed and configured, you should see a message similar to the following:

NMS TXn000 Driver Unit(0) V(202) irq(10) addr(0x000cc000)


 Unsuccessful Installation

An unsuccessful installation will result in a message similar to this:

TXn000 driver no board for unit(0)


This indicates that the Dual Port RAM driver has not recognized the TX 2000/TX 3000 board on the bus at the specified memory location.

Possible explanations:

4.3 Viewing the Statistics for the TX 2000/TX 3000 Boards

This section provides instructions for viewing the hardware/software statistics for the TX 2000/TX 3000 family of boards.

4.3.1 Windows NT

The TX configuration utility provides an interface which allows the administrator or software developer to view driver-level statistics describing the packet flow and certain error conditions. In addition, this utility also reports the current logical state of the associated CP.

Note: You can only view the statistics using this method if you are running SS7 2.1x or later! If you are running a previous version of SS7, see Section 4.5 for information on using cpcon to view statistics for your TX CP.

To view the statistics for your TX 2000/TX 3000 under Windows NT:

  1. Click the Start button, point to Settings, and click Control Panel.

    
    
  2. Click the NMS TX CPs icon. The Configure/Install/Remove TX dialog box appears.

    
    
  3. Highlight the name of the CP for which you want to see the statistics and click Configure Selected CP. The NMS TXn000 Configuration dialog box appears.

    
    
  4. Click the Statistics tab.The Statistics dialog box appears.

    
    
    
    The Statistics dialog box is a snapshot of the current driver statistics for the selected CP. While the statistics will not automatically update themselves on the screen, the statistic counters continue to update themselves in the driver independently of the snapshots. To update this screen at any time, click Refresh. A new snapshot will be taken and the new statistics will appear on the screen. To reset all of the values to zero, click Zero Stats.
    The following table provides a brief description of each statistic:
    Statistic

    Description

    Adapter State

    The logical state of the selected CP. The following values are valid:

    · Boot - The board is ready for a kernel. Appears just after a reset or power-up.

    · Preboot Active, Preboot Done, Loading, Kernel Init - Shows the intermediate stages that occur while loading the kernel.

    · Ready - The kernel has been loaded and is running.

    · Down - The board was disabled by the driver resulting from internal errors.

    · Unknown ??? - The driver cannot determine the state of the board.

    Least Free Buffers

    The least amount of available buffers detected in the buffer pool.

    Packets Sent

    The total number of packets sent to the TX board.

    Bytes Sent

    The total number of bytes sent to the TX board.

    Sends Rejected

    Total number of packets that timed-out on send.

    Packets Received

    The total number of packets received from the TX board.

    Bytes Received

    The total number of bytes received from the TX board.

    No Receiver Packets

    The total number of packets received on a channel for which no task is registered.

    No Buffers Available Packets

    The total amount of packets sent for which no buffers were available.

    Truncated Receive Packets

    Not used.

4.3.2 UnixWare

The cputil utility, found in the /opt/nmstx/bin/ directory, can be used to access a TX 2000/TX 3000 board's statistics. This can be useful in troubleshooting problems with a TX board.

  1. As root, type the following at the command prompt:

cputil -b 1 -R

This command will reset board number 1.

  • Type:

    
    
    cputil -b 1 -C

    This command clears the statistics counters for board 1.

  • Type:

    
    
    cputil -b 1 -S

    This is an example of the output:

    TXN000 board(1) statistics:
    Total Interrupts              [0]
    Transmits Started             [0]
    Receives                      [0]
    OS READY interrupts           [0]
    MSG interrupts                [0]
    MSGACK interrupts             [0]
    RXACK interrupts              [0]
    OS LOAD packet interrupts     [0]
    Stray interrupts              [0]
    Out of State errors           [0]
    Out of Memory errors          [0]
    Messages for Unbound Channel  [0]
    Unknown errors                [0]
    Successful OS runs            [0]
    Unexpected ACK received       [0]
    Unexpected ACK during load    [0]
    
    
    
    1. Next, download the kernel to the board as follows:

      cplot -c 1 -f /opt/nmstx/lib/txn/cpk2000.lo -k -a
      
      
    or

    cplot -c 1 -f /opt/nmstx/lib/txn/cpk3000.lo -k -a
    
    
    depending on whether your TX board is a TX 2000 or a TX 3000. This command produces the following output:
    Loading: 5.5 Txn000 Kernel (c) 1996-1997 Natural
    MicroSystems, Inc. 7/15/98
    Note: If the output hangs after printing the first line or displays an error message, either the driver configuration does not match the IRQ setting on the board, or there may still be a memory conflict with another device. Recheck board settings and driver configuration.
    1. After the kernel download is complete, print the current counter values for the board as follows:

      cputil -b 1 -S
      
      
    The following statistics reflect a successful kernel download and communication with the host processor (actual numbers may vary slightly):

    Total Interrupts              [239]
    Transmits Started             [0]
    Receives                      [0]
    OS READY interrupts           [1]
    MSG interrupts                [1]
    MSGACK interrupts             [0]
    RXACK interrupts              [0]
    OS LOAD packet interrupts     [237]
    Stray interrupts              [0]
    Out of State errors           [0]
    Out of Memory errors          [0]
    Messages for Unbound Channel  [1]
    Unknown errors                [0]
    Successful OS runs            [1]
    Unexpected ACK received       [0]
    Unexpected ACK during load    [0]
    
    
    
    The important items to note are the Successful OS runs, which should be 1 after the first kernel download, and OS LOAD packet interrupts, with 237 being a typical value.
  • 4.3.3 Solaris

    The cputil utility found in /opt/nmstx/bin/ can be used to access a TX 2000/TX 3000 board's statistics. This can be useful in troubleshooting problems with a TX board.

    1. As root, at the command prompt type:

      cputil -b 1 -R
      
      
      This command will reset board number 1.
    2. Type:

      cputil -b 1 -C
      
      
      This command clears the statistics counters for board 1.
    3. Type:

      cputil -b 1 -S
      
      
      This is an example of the output:
      TXN000 board(1) statistics:
      Total Interrupts             [0]
      Transmits Started            [0]
      Receives                     [0]
      OS READY interrupts          [0]
      MSG interrupts               [0]
      MSGACK interrupts            [0]
      RXACK interrupts             [0]
      OS LOAD packet interrupts    [0]
      Stray interrupts             [0]
      Out of State errors          [0]
      Out of Memory errors         [0]
      Messages for Unbound Channel [0]
      Unknown errors               [0]
      Successful OS runs           [0]
      Unexpected ACK received      [0]
      Unexpected ACK during load   [0]
      
      
    4. Next, download the kernel to the board as follows:

      cplot -c 1 -f /opt/nmstx/lib/txn/cpk2000.lo -k -a
      
      
    or

    cplot -c 1 -f /opt/nmstx/lib/txn/cpk3000.lo -k -a
    
    
    depending on whether your TX board is a TX 2000 or a TX 3000. This command produces the following output:
    Loading: 5.5 Txn000 Kernel (c) 1996-1997 Natural MicroSystems, Inc. 7/15/98
    
    
    Note: If the output hangs after printing the first line or displays an error message, either the driver configuration does not match the IRQ setting on the board, or there may still be a memory conflict with another device. Recheck board settings and driver configuration.
    1. After the kernel download is complete, print the current counter values for the board:

      cputil -b 1 -S
      
      
      The following statistics reflect a successful kernel download and communication with the host processor (Actual numbers may vary slightly):
      Total Interrupts             [239]
      Transmits Started            [0]
      Receives                     [0]
      OS READY interrupts          [1]
      MSG interrupts               [1]
      MSGACK interrupts            [0]
      RXACK interrupts             [0]
      OS LOAD packet interrupts    [237]
      Stray interrupts             [0]
      Out of State errors          [0]
      Out of Memory errors         [0]
      Messages for Unbound Channel [1]
      Unknown errors               [0]
      Successful OS runs           [1]
      Unexpected ACK received      [0]
      Unexpected ACK during load   [0]
      
      
      The important items to note are the Successful OS runs, which should be 1 after the first kernel download, and OS LOAD packet interrupts, with 237 being a typical value.

    4.4 The tx2diag and tx3diag Utilities

    The tx2diag and tx3diag programs are diagnostic utilities for the TX 2000 and TX 3000 boards, respectively. When run, the tx2diag and tx3diag programs perform a very thorough test of the TX hardware selected. These programs are located in \nms\tx\bin\ under Windows NT (/opt/nmstx/bin/ under UNIX) and must be run from this directory.

    To run the tx2diag or tx3diag utility, perform the following steps:

    1. From a DOS (or UNIX) prompt, type:

    tx2diag (if you are using a TX 2000 board)

    or

    tx3diag (if you are using a TX 3000 board).

    The following options are available:

    CP # <ENTER> Only the CP indicated in the CP # parameter will be diagnosed.

    <ENTER> All available CPs will be diagnosed.

    other key <ENTER> Typing any other key and pressing enter will abort the test and shut down the utility.

    1. tx2diag/tx3diag will run a series of tests to check the status of the EEPROM, the memory on the board, the 68360 processors, and the NMI (Non-maskable Interrupt).

      
      tx2diag/tx3diag will either report a success or failure after each test. When the last test has finished, you can check the results of each test by scrolling up.
    2. Press <ENTER> to close the utility.

    4.5 The cpcon Utility

    Name

    cpcon

    Purpose

    Displays configuration and statistics information maintained by the operating system.

    Usage

    cpcon option option


    command

    Valid options include:
    Option

    Function

    -b boardnumb

    TX board number (1-8). (default = 1)

    -c channelnumb

    Dual port RAM channel number (default = 6)

    Valid commands include:
    Command

    Description

    Information Displayed

    help

    Shows the full command set or details for a specified command name.

    Names of valid commands.

    date

    Show the current date
    (as viewed by the communication
    processor).

    Current date.

    dpr

    Show information about the dual port RAM interface.

    · DPR Context: Memory address of dual port RAM control structure.

    · CP Number : Communications processor number assigned to this board.

    · VS,VR,NS,NR : Sequence numbers used to maintain synchronization with the host processor.

    · Errors: A set of error counters indicating communication problems.

    · Current DPD: Address of Dual Port Descriptor currently involved in transfer.

    · TX Semaphore: State of semaphore used to ensure only 1 transmit in progress.

    · Two Part: Status of transmit that was broken into 2 parts.

    · Trans Queue: Number of transmits waiting to go to host (and peak number queued.

    dump memory address

    Display a hex/ASCII dump of the memory
    address specified (256 bytes display).

    Address information.

    eth Ethernet interface number

    Show detailed information on specified Ethernet interface.

    This command is specific to PCI-based boards, even though it appears on the help menu for ISA boards.

    if

    Show all interfaces currently defined

    · Res#: Resource number that interface is associated with.

    · HW: Hardware type for given interface:

    Interface Description

    DPR Dual port RAM interface.

    SCC Serial com controller.

    ETH Ethernet controller.

    QCH QUICC32 channel.

    · Type: Type of usage:

    Type Description

    SER Serial.

    ETH Ethernet.

    TDM Time division multiplexed.

    · Port: Physical port number associated with interface.

    · Max Tx: Maximum number of pending transmit requests over interface.

    kernel

    Show information from the main KERNEL control
    structure.

    · Context: Memory address of KERNEL context block.

    · Unused RGDs: Number of region descriptors currently available.

    · current: Shows information about the current task.

    · Memory: Shows the address range and total amount of memory on the system.

    · msg: Shows message handing key and errors related to messages.

    · tcb: Shows Task Control Block key and TCB deallocation errors.

    · tmr: Shows timer control key and timer queuing errors.

    · levels: Shows how deep exceptions and critical code areas have nested.

    · semaphore: Shows any saved SR (due to critical code) & state of DMA semaphore.

    · sys info: Memory address of the SYSTEM INFORMATION block.

    · idle peak: counter used for determining CPU utilization.

    · Timer Granularity: Indicates the tick interval used to advance timers.

    lfd

    Show list of all open files (Logical File Descriptors).

    · Name: Unique name identifying file.

    · State: Either \pending\ (open has not completed) or \live\.

    · Task: Name of the task that owns the file (i.e. issued the open).

    · IAddr: Internal address associated with open.

    · Server: Name of the task that serviced the open.

    · IO Outst: Count of IO requests issued by owner and not yet responded to.

    · CLOSING: Indicates whether a close has been issued.

    · CLOSED: Indicated whether the server has responded to a close request.

    Log

    Show the KERNEL error log.

    KERNEL error log.

    mem

    Show total amount of memory in use and available.

    Memory in use and available.

    memreg

    Show assignments for all memory regions.

    · Owner: Name of task owning the memory region (*KERNEL if no task).

    · Name: Name of memory region (or address if not named).

    · Start: Starting memory address of region.

    · End: Address of last byte in memory region.

    · Size: Total number of bytes in region.

    · Access: Memory access flags.

    mvip

    Show all current MVIP stream/timeslot assignments.

    · Status/Map: Status of FMIC (\reset\, \enabled\,\disabled\) and frame B value.

    · Clocking: Clock source for Master, Sec8K, and T1/E1.

    · Current FMIC Map : Output destination where connection is directed (MVIP or LOCAL stream/timeslot).

    · Source where connection originates (MVIP or LOCAL stream/timeslot).

    · Stream: MVIP stream number (Output and Source).

    · TS: MVIP timeslot number (Output and Source).

    · Pat: Pattern being generated when in pattern mode.

    · Mode: FMIC mode for connection (NORMAL, PATTERN, or REVERSE).

    Conn: Connection indication of one of following types:

    Type Description

    <--> Full duplex: connects point
    to each other.

    <--- Connect points to entry with
    NULL connection.

    ---- Connect of NULL when
    Mode = PATTERN.

    !!!! Connect of NULL when
    Mode != PATTERN.

    ???? Connect points to entry (with
    out connect back)

    names

    Show all Named Objects defined in the system.

    · Type: Type of Named Object. Can be one of:

    Type Description

    Resource HW or SW resource

    Virtual Port Virtual port

    Memory Segment Named mem. area

    · Name: Registered name for the Object.

    · Pointer: Pointer to the Named Object.

    pmem

    Show the percentage of memory assigned to each task.

    List of tasks with allocated memory percentages.

    q32

    Show information about each 360 operating in QUICC32
    mode.

    · 360 #: Number identifying the 360 that is in QUICC32 mode (0 = MAIN).

    · context: Memory address of context block controlling QUICC32.

    · IMPBASE: Base address of QUICC32 360 chip.

    · Level 1: Level 1 driver context block assigned to each QUICC32 channel.

    · ctrlbase: Control base address for SCC3 and SCC4 (channels split between).

    · prbase: Parameter ram base address (SCC3 and SCC4).

    · stats: Statistics indicating total number of interrupts and error counts.

    qprio
    task name

    Show all priority message queues for the specified task.

    Head: Head message element on the queue.

    Tail: Tail message element on the queue.

    Count: Count of messages currently on the queue.

    Peak: Peak number of messages that have resided on the queue.

    Max: Maximum number of messages allowed on the queue.

    OFlow: Number of messages that were discarded due to queue overflow.

    Ques

    Show the list of priority queues (tasks waiting to
    execute).

    Priority queue list.

    res

    Show all resources currently defined.

    List of defined resources.

    resdet resource number

    Show detailed resources information.

    · Res#: Resource number.

    · HW: Interface hardware type. Can be one of:

    Interface Description

    DPR Dual Port Ram interface

    SCC Serial Com. Controller

    ETH Ethernet interface

    PCI PCI interface

    QCH QUICC32 Channel

    SFT Software resource

    · Type: Level 1 interface type. Must be one of:

    Interface Description

    VRes Virtual Resource

    HBUS Host Bus interface

    SER Serial interface

    ETH Ethernet interface

    TDM TDM interface

    EROM EEPROM interface

    MBOX Mailbox interface

    · Port: Hardware port number

    · Lvl1 Key: Level 1 driver context key

    · Protocol: Type of protocol in use:

    Protocol Description

    NONDEF Type Not Defined

    ETH Ethernet packet protocol

    ASY Async protocol

    HDLC HDLC protocol

    SS7 SS7 protocol

    NSNR Dual port ram protocol

    P2P Peer-to-Peer protocol (PCI)

    ETH IP Ethernet IP packet protocol

    IP IP protocol

    UDP UDP protocol

    TCP TCP protocol

    MAILBOX Mailbox protocol

    · Vports: Count of Virtual Ports attached to the resource.

    · TxQued: Number of transmits currently queued.

    · TxPost: Total number of transmits posted via the resource.

    · Users: Current number of users of the resource.

    · Rx Drops: Number of received packets dropped at the resource layer.

    · EnaCnt: Number of times resource has been enabled.

    · Max Tx: Max number of transmits allowed.

    · Rx Fails: Total number of receive failures.

    · LastErr: Last error encountered by the resource.

    · Connection: Type of connection used by the resource:

    Type Description

    HBUS Host Bus

    SERIAL Serial com. controller

    ETH Ethernet interface

    TDM MVIP/T1/E1 controller

    EEPROM EEPROM controller

    SOFTWARE Software connection

    scc

    Show information for each serial communications
    controller.

    · Type: Type of serial communications controller (SCC) usage:

    Type Description

    SCC Physical SCC port
    (i.e. POD port).

    ETH Physical ethernet port.

    MVIP MVIP bus connection.

    · Chl #: Channel number associated with serial communications controller.

    · SCC # : Physical serial communications controller number of processor indicated by IMPBase.

    · IMPBase: Memory address of base of serial communications controller processor.

    · CTLBase: Control base address for serial communications controller.

    · PRamBase: Parameter RAM base address for serial communications controller.

    · Tx/Rx: Average (last 10 secs) transmit and receive packet counts.

    t1cfg

    Show the T1/E1 configuration.

    · Framing: Type of framing (T1 or E1) in use:

    Frame Description
    D4 D4 (193S) Framing (T1).

    ESF Extended Superframe
    Format(T1).

    CCS Common Channel
    Signaling (E1).

    CAS Channel Associated
    Signaling (E1).

    CCS/CRC CCS with CRC4 (E1).

    CAS/CRC CAS with CRC4 (E1).

    · Encoding: Type of encoding (T1 or E1) in use:

    Encoding Description

    NONE No encoding.

    AMI AMI encoding with no
    zero suppression.

    B7ZS Bit 7 Stuffing (T1).

    B8ZS Bipolar Eight Zero
    Substitution (T1).

    HDB3 High Density Bipolar
    Order 3 (E1).

    · Build Out: Measure of build out (T1 in feet / E1 ohm desc)

    · Robbed Bit: (T1 only) either blank (not active) or \Robbed Bit\.

    · Loop Master: Either blank (not master) or \Loop Master\.

    t1stat

    Show T1/E1 statistics information.

    T1/E1 statistics.

    tasks

    Show all tasks that have been created on the TX board.

    · Name: Name of the given task (leading \$\ indicates KERNEL task.

    · Prior: Priority of task (1 = highest priority; 31 = lowest).

    · Read: Indicates whether task is ready to be executed.

    · State: Shows the current state of task. Valid states include:

    State Description

    Created Task has been created but
    never executed.

    Stalled KERNEL detected
    invalid instruction.

    Waiting Task is asleep, waiting
    for work.

    Blocked Higher priority task
    currently blocking.

    Running Task is executing.

    Holding Invalid KERNEL service
    was requested.

    time

    Show the current time (as viewed by the communication
    processor).

    Current time.

    timers

    Show all timers that exist on the system.

    · Owner: Name of task that created the timer.

    · Address: Address of timer control block.

    · Period: Number of milliseconds between timer ticks.

    · Init: Initial number of milliseconds waited.

    · Value: Number of milliseconds remaining before timer fires.

    · User Key: Key provided by the application.

    · User Pkt: Timer control packet provided by user.

    · Status: Current status of timer (running or stopped).

    · Timer Granularity: Indicates the tick interval used to advance timers.

    tmem

    Show all memory regions assigned to the specified task.

    · Owner: Name of task ($kernel if no task specified).

    · Name: Name of memory region (or address if not named).

    · Start: Starting memory address of region.

    · End: Address of last byte in memory region.

    · Size: Total number of bytes in region.

    · Access: Memory access flag.

    util

    Show the current and average system utilization.

    Current/average system utilization.

    vol

    Show all volumes - mounted tasks (I/O accessible).

    · Name: Name of the mounted volume.

    · Devtype: Device type used on the mount (indicates alarm number range).

    · Task: Name of the task that has been mounted as \Name\.

    Note: Mount Pending indicates that the mount has not been completed.

    vport vp#

    Show detailed information for the virtual port #
    specified

    · Vport: Virtual port number.

    · Owner: Task that has attached to virtual port.

    · AtchKey: Task-supplied key associated with attach.

    · Addr1..4: Receive addresses assoc\'d with port (up to 4, all F's = ALL).

    · Rx Frm: Maximum receive frame size.

    · State: Current state of the virtual port:

    State Description

    FREE No task has been attached
    to virtual port.

    DISABLED Task attached, but virtual
    port not enabled.

    IDLE Virtual ports enabled, but
    not transmitting.

    FULL Transmitting all allowed
    for transmit window.

    DISABLING Bringing down an
    enabled virtual port.

    · Free/Pend: Number of transmit requests available (free) and in progress (pend).

    · Tx/Rx Stats: Counts of frames/bytes transmitted and received.

    · Fail Stats: Counts of Tx and Rx failures with last error code reported.

    · HW Port: Hardware type and physical port number.

    · Lvl1 Key: Level 1 driver key (and protocol indication).

    · Type-Specif: HW type-specific additional description of virtual port.

    vports

    Show all virtual ports currently defined.

    List of defined virtual ports.

    Procedure

    To run cpcon:

    1. Open a command line window.

      
      
    2. Navigate to the \nms\tx\bin directory on Windows NT (or /opt/nmstx/bin/ on UNIX).

      
      
    3. Enter the following at the prompt:

      
      cpcon [-b boardnumb -c channelnumb]
    4. At the prompt, enter one of the cpcon commands.

      
      cpcon displays the requested information.



    (Page 1 of 1 in this chapter) Version


    tech_support@nmss.com
    Copyright © 2001, Natural MicroSystems, Inc. All rights reserved.