cc/td/doc/product/tel_pswt/vco_prod
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Host Communications Troubleshooting

Host Communications Troubleshooting

This chapter describes general corrective procedures for host communications links. Refer to the Cisco VCO/4K System Administrator's Guide for additional details on configuring Ethernet host communication links. The Cisco VCO/4K Standard Programming Reference and the Cisco VCO/4K Extended Programming Reference describe the command and reports passed between a VCO/4K and a host. Refer to the Cisco VCO/4K Ethernet Guide for information on TCP/IP sockets and additional maintenance practices.

Reference is made to other OEM manuals supplied with the host computer I/O package and modems employed for a remote access (optional), and to documentation related to the communication and application packages to be run on the host computer.

Overview

In a VCO/4K, the CPU card in the system controller controls initializing and deinitializing the host link(s) and data transfer to and from the host. All control sequences are initiated by the CPU card; the Storage/Control I/O Module is merely a connector panel which provides physical connectivity between EIA cables and the CPU card.

Before a host communication channel can be initialized, you must first define it with the Host Configuration utility (refer to the Cisco VCO/4K System Administrator's Guide). This utility is used to configure host interfaces and software overlays (TeleRouter) and indicate the status of alarm conditions for host interfaces. The following constraints are placed on this configuration:

The host communication parameters are defined in Table 6-1.


Table 6-1: Host Communication Parameters
Interface Parameters

Ethernet

Host Name

Connect Password (for local port)—optional

Loc. Port (logical port number of local port)

Rem.Inet.Addr (Remote Internet Address)

Rem. Port (logical port number of remote port A)

Trace

Protocol (fixed at TCP)

Reset Time

A reset deinitializes the link (if it was already in service) and then initializes it and applies the configuration parameters stored in the database. Three events can cause a link reset:

Problem Isolation Techniques

VCO/4K administrative software continuously monitors host communications links. Since the VCO/4K acts as a subordinate node in a network configuration, it expects the host (master) to poll the communications channels at regular intervals for message exchanges.

Error and status messages reflect the status of the data links between the VCO/4K and the host computer. If a communication channel fails, the appropriate message is sent to the VCO/4K error log (stored to disk and/or printed on the local printer, depending on the File System Configuration selections). Messages with the HST prefix indicate errors or status changes in host communication. Refer to the Cisco VCO/4K System Messages whenever a host error or status message appears on the local system printer.

The following subsections offer general troubleshooting guidelines for remedying the cause of a host communications link failure.

Host Communications Failure on Power-On

If the system experiences a general failure of host communications at initial system power-on, check for the following:

Cabling

Cabling refers to the general wiring practices used to complete the physical connection between a host communications port and a DB-15 Ethernet port. The Cisco VCO/4K Hardware Installation Guide describes the possible host communication configurations supported by the VCO/4K. Cabling between the host and the VCO/4K is determined by the desired system implementation.

Use the following recommendations to detect and correct cabling problems:

Modems

Modem setup parameters are dictated by the type of interface, communication protocol, cabling requirements, and answering mode required for the intended application.

To determine the actual modem setup requirement, review the following documents:

If the modems are connected over the switched public network or leased data lines, you must also contend with problems of noise, line losses and other problems common to data communications over analog networks.

Host Computer

Host computer I/O consists of hardware and software components which control data communications to and from the VCO/4K. The complexity of the data communications requirement is directly proportional to the number of channels between a host computer and the VCO/4K, the telecommunications traffic throughput expected for the intended application, the number of messages per call scenario, and the communications type/protocol selected for the links.

Traffic throughput requirements affect the CPU overhead required in the host computer. CPU overhead must also be provided for I/O processing of the communications links. The host computer communications software includes drivers for the I/O ports and I/O performance is controlled by the relative sophistication of the communications package running on the host.

If excess CPU overhead is expended on trying to run the call processing application, the I/O rate of the data links may be insufficient to prevent timeouts and resets at the interface ports of the VCO/4K. The host may be unable to receive, process, and return a command to the VCO/4K to prevent such autonomous timeouts and resets.

Host communications links must be operated and serviced in real time. All VCO/4K events and transitions are initiated over these links. Any delays in response affect the timely execution of the application.

If the call processing application requires sending/receiving a relatively large number of commands and reports over the communications links, the host I/O hardware and software should be selected to accommodate this requirement.

Use the following guidelines to reduce problems resulting from the handling of data communications between the host computer and the VCO/4K:

Corrective Procedures

The steps to be taken to correct host communications problems vary according to the suspected cause. Table 6-2 cross-references causes to corrective procedures.


Table 6-2:
Lost Data and Lost Communications Causes
Possible Cause Corrective Procedure
Erratic or Lost Data Communications at Initial Power-on Erratic or Lost Data Communications After Successful Power-on

Host I/O Failure

1. Reboot the host computer and load application and communications software.

2. Reboot the VCO/4K.

3. If unsuccessful, verify host computer I/O performance via the protocol analyzer or other in-circuit device.

1. Verify the operational performance of host computer and its I/O ports.

2. Enable message trace facility to determine whether messages are being passed over the communication links.

3. If unsuccessful, insert a data communications analyzer in the link. Look to see whether messages are being sent by the host and/or the VCO/4K. Failure to send a command or report isolates the cause to either the host or the VCO/4K.

4. Review the host I/O driver and application package to assure that VCO/4K commands and reports are being properly handled, without excessive delay.

Cabling

1. Inspect all connections between the host and the VCO/4K.

2. Verify that the pinouts meet signaling requirements of host and the Storage/Control I/O Module.

CPU Card

1. Verify that the CPU card is operating at normal parameters.

2. Use the Host Configuration Screen to verify link parameters.

3. Reboot the system.

4. If unsuccessful, refer to the Cisco VCO/4K Card Technical Descriptions and replace CPU card and/or the Storage/Control I/O Module.

Nonredundant
controller failure

1. Reboot the system.

2. If unsuccessful, service the controller and reboot.

Redundant
controller failure

1. Switch Active to Standby.

2. If successful, service the Standby controller.

Modem SetUp

Refer to OEM modem manual and verify setup parameters against desired communication protocols and signaling parameters. Verify the integrity of the analog data link.


Figure 6-1: Troubleshooting Host Communications Links


hometocprevnextglossaryfeedbacksearchhelp
Posted: Sat Sep 28 18:03:49 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.