New Parameter within the Integrated-SS7 Software's AccessRd.cfg File [Cisco VCO/4K Open Programmable Switches]

Document ID: 15274

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      Perform an Integrated-SS7 Software Upgrade to One of Two Software Versions
      Configure the AccessRd.cfg File
Verify
      Error Messages if AccessRd.cfg Not Properly Configured
      Other Error Conditions if AccessRd.cfg is Not Properly Configured
Troubleshoot
Related Information

Introduction

This configuration document pertains to the Integrated-SS7 software's AccessRd.cfg file, located in the $EBSHOME/access/config/ directory.

Note: If your system is a non-redundant system, then regardless of the Integrated-SS7 software's version level, the Integrated-SS7 software knows to ignore the AccessRd.cfg file. As a result, it does not matter how the AccessRd.cfg file is configured in non-redundant systems. This document does not apply to non-redundant systems.

This document assumes that within the Integrated-SS7 software $HOME/ directory, you have specified this information within the .cshrc file:

PLTFRMTYP REDUNDANT
#PLTFRMTYP STANDALONE

In these two configuration lines, the presence of the comment symbol # on "STANDALONE", together with the lack of the comment symbol on "REDUNDANT", configures the Integrated-SS7 software as a redundant system.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document pertains to these combinations of hardware and software:

Redundant systems running International Telecommunication Union (ITU) Integrated-SS7 software V5.1.2 or later, or
Redundant systems running American National Standards Institute (ANSI) Integrated-SS7 software V5.1.0 or later.

Note: If your system is running ITU Integrated-SS7 software earlier than V5.1.2, or if your system is running ANSI Integrated-SS7 software earlier than V5.1.0, then the AccessRd.cfg file does not support the new parameters described in this document.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Configure

In this section, you are presented with the information to configure the features described in this document.

Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) .

Perform an Integrated-SS7 Software Upgrade to One of Two Software Versions

Configure the AccessRd.cfg file, which is located in $EBSHOME/access/config/ directory, while you perform a software upgrade to ITU Integrated-SS7 software version 5.1.2 or later, or to ANSI Integrated-SS7 software version 5.1.0 or later, before you execute the start-ss7.sh command in this manner:

At the bottom of the AccessRd.cfg file, you are asked to specify HOST-A and HOST-B; these are the new parameters. The HOST-A value must be the same as the hostname assigned to the A-Side SS7 SPARC5 CPU. The HOST-B value must be the same as the hostname assigned to the B-Side SS7 SPARC5 CPU.

You can log into the A-Side or B-Side SS7 as cktint and issue the hostname command in order to find these hostnames.

Configure the AccessRd.cfg File

Perform these steps to properly configure the AccessRd.cfg file:

Log on as cktint to the Integrated SS7 system side A, <hostname>a.
Issue the chmod 644 $EBSHOME/access/config/AccessRd.cfg command.
Use the vi editor to open the $EBSHOME/access/config/AccessRd.cfg file, and then check for this information:
1. Check that these lines are present:
```
MONITOR_OPTION OFF
CTS_CONFIGURATION INVERTED
HOST-A <Integrated SS7 system side A hostname>
```
  An example for the last line is HOST-A tsup6ss7a.
2. If the lines do not match the intended configuration, modify them accordingly.
3. Save the changes, and close the file.
Log on as cktint to the Integrated SS7 system side B, <hostname>b, and repeat Steps 1 through 3.

Ideally, this time the lines in Step 3 read:
```
MONITOR_OPTION OFF
CTS_CONFIGURATION INVERTED
HOST-B <Integrated SS7 system side B hostname>
```
An example for the last line is HOST-B tsup6ss7b.

Verify

The configuration of the AccessRd.cfg can be verified by checking for these errors.

Error Messages if AccessRd.cfg Not Properly Configured

If you do not properly configure the AccessRd.cfg file, this error message appears in the start-ss7.sh screen output when you issue the start-ss7.sh command (the error message is indicated in bold):

%start-ss7.sh
This script will assist you in bringing up your Integrated
SS7 system in a controlled fashion.
Would you like to start the EBS stack [y/n]?y
Starting Signaling Point 0
Starting ebs_start...
Signalling Point Manager - Version 3.5
Copyright (c) ADC NewNet, Inc.
All Rights Reserved
Loading /dev/ecp0   - device does not exist
Loading /dev/ecp1   - device does not exist
Loading /dev/ecp2   - device does not exist
Loading /dev/ecp3   - device does not exist
Loading /dev/ecp4   - device does not exist
Loading /dev/ecp5   - device does not exist
Loading /dev/ecp6   - device does not exist
Loading /dev/ecp7   - device does not exist
Loading /dev/ecpt0  - device does not exist
Loading /dev/ecpt1
Loading /dev/ecpt2  - device does not exist
Loading /dev/ecpt3  - device does not exist
Loading /dev/ecpt4  - device does not exist
Loading /dev/ecpt5  - device does not exist
Loading /dev/ecpt6  - device does not exist
Loading /dev/ecpt7  - device does not exist
AccessMANAGER Ready
*****************************************
******* AccessALARM is in service *******
*****   Console Output is DISABLED  *****
*****************************************
Starting upmd...
User Part Manager - Version 3.5
Copyright (c) ADC NewNet, Inc.
All Rights Reserved
UPMD #0  Waiting <snmd> to start
Starting snmd...
Signalling Network Manager - Version 3.5
Copyright (c) ADC NewNet, Inc.
All Rights Reserved
UPMD #0  <snmd>  started, loading prestored data
UPMD #0  MTP Started
UPMD #0  EBSRUN is set to /export/home/EBS/access/RUN0
UPMD #0  Protocol type is CCITT
Starting AccessRd...
filename /export/home/EBS/access/config/AccessRd.cfg
HOST-A and HOST-B must be defined
Error reading configuration parameters
Starting AccessISUP...
Starting tli...
EBS SS7 is now started.
Would you like to start the Circuit Interworking (CktInt) software?
(Note You should not start CktInt without the EBS stack running!) [y/n]
<snip>

If you see this error message, type n in response to the question Would you like to start the Circuit Interworking (CktInt) software?. Issue the stop-ss7.sh command in order to stop the EBS stack, re-edit the AccessRd.cfg file properly, and try again.

Other Error Conditions if AccessRd.cfg is Not Properly Configured

Iif you run your redundant system (that is, if you fully execute the start-ss7.sh command, starting both the EBS and cktint stacks) with an AccessRd.cfg file that does not properly specify HOST-A and HOST-B, when you issue the system switchover command the Intregrated-SS7 software fails to respond and system redundancy is lost.

For more details on how to recover from such a loss-of-redundancy problem, refer to VCO: SS7 Software Switchover Failures if SS7 AccessRd.cfg File not Properly Configured.