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

Table of Contents

Checklists

Checklists

This appendix contains checklists to capture the information for a Cisco TAC to most efficiently address your problem.

VCO Subsystem

Data Checklist - General Questions for the VCO Subsystem

Before you start gathering information, consider the following high-level general questions:

SS7 Subsystem

Data Checklist

This section deals with ckint software failure (with and without ckint core file). It guides you through a data collection process that requires you to enter commands at several points and to then paste the resulting information into a .txt file. Then send the .txt file to TAC for analysis.

This procedure is needed if the cktint software malfunctions, and is needed whether or not the core file was created.

Data Collection


Step 1   Is the VCO/SS7 platform a redundant or nonredundant platform?

Step 2   Create a file stating the software version numbers of the following platform. Name this file versions.txt and list the versions in the following order and with the following labels:

Step 3   Are you running China-TUP?

CC_CONFIG = tup (to set environment as China)

cd $XNV

version ckint (version is displayed)

Step 4   Are you running TCAP (yes or no)?

    1. If yes, then what version? Type:

sept (log in)

abc123 (password)

cd $XNV

version sept (tcap version is displayed)

Step 5   Were new circuits brought into service within the last 60 days?

What is the VCO RLSS designation for this span?

What is the hex address of the first port of this span?

(Obtain this information from the VCO Diagnostic / Display Card Data screen)

Preparing the Information for Transmission

To prepare the data you have gathered, do the following:


Step 1   Encode (uuencode, optional) the cktint core file, if any.

Step 2   Compress the VCO core file, if any (Winzip).

Step 3   Compress any cktint log file that is over 0.5 MB.

Step 4   Compress any VCO log file that is over 0.5 MB.

Step 5   When cktint died, was a cktint core file created?

Step 6   When cktint died, was a VCO core file created?

Step 7   Log in to cktint and type ps -ef on the side that died.

Step 8   When cktint died, did SS7/cktint properly switch over (yes or no)?

Step 9   When cktint died, did VCO/generic properly switch over (yes or no)?

Step 10   When cktint died and if a proper switchover occurred, then what event did the host application see, from its perspective, that caused it to decide to issue a switchover command (the host application switchover command, if issued, would be recorded in the VCO active-side log)?

Step 11   Analyze your host application logs and summarize what the host application was doing at the time of the switchover command.

Step 12   At the time that cktint died, was a system administrator logged in to cktint?

Step 13   At the time that cktint died, was a system administrator logged in to the VCO system?

Step 14   Log in to the SS7/cktint a-side and provide the following ls -l outputs:

%pwd

/export/home/cktint/sys/CktintAnEnv/log

%ls -l

(Put the output into a text file. Name the file alogls-l.txt.)

%pwd

/export/home/cktint/sys/CktintAnEnv

%ls -l

(Put the output into a text file. Name the file aXNVls-l.txt.)

Step 15   Log in to the SS7/cktint b-side and provide the following ls -l outputs:

%pwd

/export/home/cktint/sys/CktintAnEnv/log

%ls -l

(Put the output into a text file. Name the file blogls-l.txt.)

%pwd

/export/home/cktint/sys/CktintAnEnv

%ls -l

(Put the output into a text file. Name the file bXNVls-l.txt.)


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