cc/td/doc/product/access/sc/rel7/soln/das
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Introduction and Overview

Introduction and Overview

Solution Overview

The Cisco SS7 Interconnect for Access Servers Solution is a distributed system used for interconnecting Cisco network access servers (NASs) to a circuit-switched time division multiplexing (TDM) network using Signaling System #7 (SS7) protocols for signaling. The interconnections are achieved using a protocol conversion platform called the Cisco Signaling Controller combined with the Cisco Signaling Link Terminal (Cisco SLT). The Cisco SC2200 comprises the hardware and software package that provides the signaling controller function in the Cisco SS7 Interconnect for Access Servers Solution. It provides high availability, high performance, and key scaling.

The Cisco SS7 Dial Access Solution Release 2.0 provided the Cisco signaling controller using T1/E1 or V.35 signaling cards to terminate SS7 signaling from the public switched telephone network (PSTN) and control bearer traffic on the NASs. The new Cisco SS7 Interconnect for Access Servers Solution uses the Cisco SLTs instead of cards in the SC host to terminate the first and second MTP layers of SS7 signaling. Bearer traffic remains on the NASs. The use of Cisco SLTs provides redundancy and ensures no disruption of service; this feature was not available with the signaling cards in the SC host in Release 2.0.

Use of T1/E1 or V.35 signaling cards is supported for existing installations, but Cisco strongly recommends upgrading to Cisco SLTs to terminate signaling.

Note   The SLT can be located remotely from the Cisco SC host using a dedicated link. Refer to the Cisco SLT documentation for details.

This chapter contains the following sections:

Before Starting the Upgrade

This section contains the following information you should read before upgrading:

General Tips

Before you upgrade the SC software, check the following:

Caution All calls are lost during the upgrade. You cannot switchover from SC Software
Release 4 to SC Software Release 7. You can, however, minimize downtime by preparing the new components of your solution, such as setting up hardware and installing software, before you begin. You should also coordinate with your SS7 link service provider to let them know that your links will go out of service. Your provider should have onsite support staff available to assist you should there be problems reestablishing the links.
Note   Monitor system output frequently for error messages during the upgrade process. Correct any error messages before continuing with the upgrade.

Gathering Required Software and Hardware

Gather all required software and hardware. Refer to "Minimum Hardware Requirements" section and "Software Requirements" section. At a minimum, you must obtain the following CD-ROM disks:

Note   Obtain the Volume Manager License key from Sun Microsystems using the software license key request form that is ordered with the target machine. Follow the instructions on the form to obtain a Volume Manager License Key.

The target machine must have a terminal connected by using a serial cable inserted into the console port.

Gathering Required Information

You need the following information for the upgrade:

Reviewing Your Components.dat and Properties.dat Files for Potential Problems

Review your components.dat and properties.dat files to determine if long file names or special characters such as periods, symbols, or spaces are used. The migration between Software Release 4 and Software Release 7.3(x) requires that MML names of components be 10 alphanumeric characters or less, begin with a character, and cannot contain special characters. MML names can contain dashes. (In Software Release 7.4(x), MML names must be 20 characters or less and meet the same standards.)

To review these files:

Step 1   Change to the /opt/TransPath/etc directory.

Step 2   View the components.dat and properties.dat files. For example, the following components.dat file has long file names that will cause the migration to fail:

# cd /opt/TransPath/etc
# more components.dat
00010001  00000000  "LPC-01"                "TransPath: SC07  SC-Pod7-TP"
00020001  00010001  "CFGG-01"               "Config Mgr Subsystem"
00020002  00010001  "ALGG-01"               "Alarm Mgr Subsystem"
00020003  00010001  "MSGG-01"               "Measurement Mgr Subsystem"
00020004  00010001  "ENGG-01"               "Engine Subsystem"
00020005  00010001  "IOSG-01"               "IO Subsystem"
00020006  00010001  "LOGM-01"               "Log Manager Subsystem"
00020007  00010001  "XEG-01"                "Execution Environment Daemons"
00020008  00010001  "PFMG-01"               "Platform Monitoring"
00030001  00020007  "CFM-01"                "Config Manager"
00030002  00020007  "ALM-01"                "Alarm Manager"
00030003  00020007  "MM-01"                 "Measurement Manager"
00030004  00020007  "DMPR-01"               "Data Dumper"
00030005  00020008  "DSKM-01"               "Disk Space Monitor"
00030006  00020004  "ENG-01"                "Engine"
00030007  00020005  "IOCM-01"               "IOS Channel Manager"
00030008  00020005  "IOCC-ASP"              "IOS Channel Controller - ASP"
0003000A  00020007  "SNMP-AGT"              "SNMP Agent Subsystem"
0003000B  00020005  "IOCC-02"               "IOS Channel Controller - ANSI-SS7"
0003000C  00020005  "IOCC-01"               "IOS Channel Controller - ISDNPRI-IP"
00040001  00010001  "CPU-01"                "CPU 1"
00040003  00010001  "DISK-01"               "Hard Disk #1"
00040004  00010001  "DISK-02"               "Hard Disk #2"
00050001  00010001  "SS7-Link-STP-A"        "SS7-Link-STP-A: STP-A-SS7-linkset"
00050002  00010001  "ss7-Link-STP-B"        "ss7-Link-STP-B: tester1"
00050003  00010001  "EN-1"                  "EN-1: Ethernet 1"
00050004  00010001  "EN-2"                  "EN-2: Ethernet 2"
00060001  00050001  "L-ss7-Link-STP-B-0"    "L-ss7-Link-STP-B-0: 5-E"

In this example, the SS7-Link-STP-A , SS7-Link-STP-B, and L-SS7-Link-STP-B-0 components are invalid.

Step 3   Use a text editor such as vi to edit the file and rename the invalid components.

Caution If you do not edit MML names to conform to the new restrictions, your installation migration will fail. You will have to edit the names and reinstall package CSCOgc001.

Gathering Provisioning Data

Gather provisioning information in order to quickly provision your system after upgrading. You should read the Cisco Media Gateway Controller Provisioning Guide and use the worksheets below to list the components in your network that you need to provision. Also refer to the Cisco SS7 Interconnect for Access Servers Solution Provisioning Guide for further instructions. Advance preparation will greatly lessen the time required to complete the provisioning during the upgrade.

To provision, you can use either the Telephony Controller Manager (TCM), available with software release 7.3(x), the Cisco Media Gateway Controller Manager (CMM), available with software release 7.4(x), or MML, the command-line interface available with both software versions.

TimeSaver To save time, you can use an MML batch file to provision your system. This requires that you enter all MML commands to provision your system into an ASCII text file and import the file. See the Cisco SS7 Interconnect for Access Servers Solution Provisioning Guide for more information and a sample batch file.

Completing the following worksheets will help you in provisioning your system.

Point Codes

To define SS7 network addresses, you must configure the following component types:


Table 1-1: Point Code Parameter Descriptions
MML Parameter Name CMM Parameter Name Description

NAME

MML Name

Unique name for this point code. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

NETADDR

Network Address

SS7 network address in dotted notation.

NETIND

Network Indicator

The network indicator assigned by the network administrator.

DESC

Description

Text description of this point code. Enter as many as 128 characters and enclose in straight quotes.


Table 1-2: Point Code Configuration Parameters
NAME NETADDR NETIND DESC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 1-3: Adjacent Point Code Configuration Parameters
NAME NETADDR NETIND DESC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Linksets

To define linksets, you must configure the following component types:

Note   When configuring linksets for STP connections, you will usually configure two linksets for each pair of STPs.


Table 1-4: Linkset Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Description

NAME

MML Name

Unique name for this linkset. Enter as many as 10 characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

APC

Adjacent Point Code/Point Code

Adjacent point code or destination point code. For linksets that connect directly to an SSP, enter the MML name of a previously defined destination point code. For linksets that connect to a Cisco SLT, enter the MML name of a previously defined adjacent point code.

TYPE

Transport Type

Enter TDM for linksets that connect directly to an SSP, or enter IP for linksets that connect to Cisco SLTs. The default is TDM.

PROTO

Protocol Family

Enter one of the following:

SS7-ANSI

SS7-ITU

SS7-China

SS7-UK

DESC

Description

Text description of this linkset. Enter as many as 128 characters and enclose in straight quotes.


Table 1-5: Linkset Configuration Parameters
Name APC or DPC Type Proto Desc

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SS7 Subsystem

To define an SS7 subsystem, you must configure the following component types:

For mated STPs, the subsystem defined for each STP defines the other STP as the mate using the MATEDAPC parameter.


Table 1-6: SS7 Subsystem Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Description

NAME

MML Name

Unique name for this subsystem. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

SVC

Adjacent Point Code

Adjacent point code for an STP. The MML name or index of the APC if TRANSPROTO is SCCP. Or the MML name or index of TCAPOverIP service for IN trigger services if TRANSPROTO is TCPIP. Enter the MML name of a previously defined APC.

MATEDAPC

Mated Adjacent Point Code

Adjacent point code for an STP mate. Enter the MML name of previously defined APC. Only used when mating STPs, not when creating AIN subsystems.

PRI

Priority

Priority. Enter an integer that is greater than 0 and less than 4. One (1) is the highest priority level. When two subsystems share the same priority level, traffic is shared by both subsystems. Not used when mating STPs.

Default = 1.

PROTO

Protocol Family

Protocol family. When mating STPs, only the SS7 variant is allowed.

  • SS7-ANSI - when creating an AIN subsystem.

  • SS7-ITU - when creating an AIN subsystem.

  • SS7-China - when mating an STP pair.

  • SS7-UK - when mating an STP pair.

If the SVC is an APC, SCCP should not be used (SCCP is not used when mating STP pairs. If the SVC is a TCAPoverIP service, then TCPIP should be used

SSN

Sub System Number

Subsystem number. Enter an integer from 0 to 255. When mating STPs, SSN = 0. When using IN services, SSN can be set to a value greater than 0.
Default = 0.

STPSCPIND

STP-SCP Index

STP/SCP index. Enter an integer greater than 0. When mating STPs = 0. Default = 0. Not used when mating STPs.

TRANSPROTO

Transport Protocol

Transport protocol. Enter the transport protocol of this subsystem. When mating STPs = SCCP. Values: SCCP or TCPIP. Not used when mating STPs.


Table 1-7: SS7 Subsystem Configuration Parameters
Name APC Mated APC Pri Proto SSN Desc

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SS7 Route

To define an SS7 route, you must configure the following component types:


Table 1-8: SS7 Route Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Description

NAME

MML Name

Unique name for this route. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

OPC

Originating Point Code

Origination point code. Enter the MML name of a previously defined origination point code for this SC node.

DPC

Destination Point Code

Destination point code. Enter the MML name of a previously defined destination point code for a remote switch.

LNKSET

Link Set

Linkset that leads to the destination device. Enter the MML name of a previously defined linkset.

PRI

Priority

SS7 route priority. Enter an integer that is greater than 0. One (1) is the highest priority level. When two SS7 routes share the same priority level, traffic is shared by both routes.

Default = 1.

DESC

Description

Text description of this route. Enter as many as 128 characters and enclose in straight quotes.


Table 1-9: SS7 Route Configuration Parameters
NAME OPC DPC LINKSET PRI DESC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SS7 Signaling Service

To define an SS7 signaling service, you must configure the following component types:


Table 1-10: SS7 Signaling Service Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Value Description

NAME

MML Name

 

Unique name for this signaling service. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

DESC

Description

 

Text description of this signaling service. Enter as many as 128 characters and enclose in straight quotes.

DPC

Point Code

 

Destination point code. Enter the MML name of a previously defined destination point code.

MDO

MDO File Name

 

Message definition object file name. Choose the MDO filename that was used in your previous configuration.

SIDE

Side

network

Q.931 call model side. Enter user for user side or network for network side.
Default = network.

CUSTGRPID

Customer Group ID

0000

Customer Group ID. Virtual network identification characters (formerly called the Closed User Group). Values accepted for this field depend on the use of the D channel. Used to retrieve information about this signaling service and which dial plan to use. Enter the four-digit ID. Default = 0000.

CUSTGRP
TBL

Customer Group Table

NA

Reserved for future use.


Table 1-11: SS7 Signaling Service Configuration Parameters
NAME DPC MDO Side CUSTGRPID

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ethernet Cards

To provision network cards, you must configure the following component types:

Table 1-12 describes configuration parameters you can use to configure cards, and Table 1-13 serves as a form on which you can plan card configurations.

If you are not using Cisco SLTs for signaling, refer to Cisco Media Gateway Controller Provisioning Guide for signaling card parameters and values.


Table 1-12: Card Configuration Parameter Descriptions for Cisco SLT Communications
MML Parameter Name CMM Parameter Name Default Value Description

NAME

MML Name

None

Unique name for this component. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

SLOT

Slot

None

Location of card or adapter within the host machine. Acceptable values depend on the host machine. The first slot is usually 0. Enter a value from 0 through 15.

TYPE

Type

None

The interface card type. Acceptable values are:

  • EN

  • ITK

  • V35

DESC

Description

None

Text description of this component point code. Enter as many as 128 characters and enclose in straight quotes.


Table 1-13: Card Configuration Parameters
NAME SLOT TYPE DESC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Ethernet Interfaces

To provision Ethernet interfaces, you must configure the following component types:

Table 1-14 describes the configuration parameters that define an Ethernet interface. Table 1-15 serves as a form for you to plan the Ethernet interfaces.


Table 1-14: Ethernet Interface Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Description

NAME

MML Name

Unique name for this interface. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

CARD

Ethernet Adapter

Identifies the card that supports this interface. Set this to the MML name of a card that has already been defined.

DESC

Description

Text description of this interface. Enter as many as 128 characters and enclose in straight quotes.


Table 1-15: Ethernet Interface Configuration Parameters
NAME CARD DESC

 

 

 

 

 

 

 

 

 

 

 

 

C7 IP Links

To provision the Cisco SLT links, you must configure the following component types:

Table 1-16 lists and describes the C7 IP link configuration parameters that define each link. Table 1-17 serves as a form for planning a single C7 IP link.


Table 1-16: C7 IP Link Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Default Value Description

NAME

MML Name

None

Unique name for this link. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

DESC

Description

None

Text description of this link. Enter as many as 128 characters and enclose in straight quotes.

IF

Enet Line Interface

None

Ethernet interface to which this link connects. Enter the MML name of a previously defined Ethernet interface, or enter the SNMP index number for the interface.

IPADDR

IP Address

None

Cisco SC host IP address for interface. Enter the IP address variable defined in the XECfgParm.dat file during the installation of the Cisco SC software. Valid entries are IP_Addr1, IP_Addr2, IP_Addr3, and IP_Addr4.

LNKSET

Link Set

None

Linkset to which this link belongs. Enter the MML name of a previously defined linkset.

PORT

Port

None

Cisco SC host port number to which this link connects. Enter any valid IP port number. Value range: any valid IP port number from 1025 through 32766.

PEERADDR

Peer Address

None

Remote IP address (in dotted notation) of the Cisco SLT interface to which this link connects. (May also be specified as a host name or a DNS name.)

PRI

Priority

1

Priority. Enter an integer greater than 0. Value range: 1 through 16.

SLC

Link Code

1

SS7 Signaling link code. Value range: 0 through 15.

TIMESLOT

Time Slot

0

Time slot field for the C7 IP link. Identifies the physical WAN interface card (WIC) slot, or the SS7 serial port, of the Cisco SLT.
Value range: 0 through 3.


Table 1-17: C7 IP Link Configuration Parameters
MML Parameter Name Configuration Setting

DESC

 

IF

 

IPADDR

 

LNKSET

 

NAME

 

PORT

 

PEERADDR

 

PRI

 

SLC

 

TIMESLOT

 

NAS External Nodes

To provision media gateway external nodes, you must configure the following component types:

Table 1-18 describes the external node configuration parameters, and Table 1-19 serves as a form for you to plan a unique name for each media gateway.


Table 1-18: External Node Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Default Value Description

NAME

MML Name

None

Unique name for an external device. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

DESC

Description

None

Text description of an external device. Enter as many as 128 characters and enclose in straight quotes.


Table 1-19: Media Gateway External Node Configuration Parameters
NAME DESC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

NAS Signaling Service

To provision a NAS signaling service, you must configure the following component types:

Note   Used if you have more than one SC host.


Table 1-20: Media Gateway Signaling Service Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Default Value Description

NAME

MML Name

None

Unique name for this signaling service. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

MDO

MDO File Name

None

Enter a valid message definition object (MDO) file protocol name by using the PROV-RTRV:VARIANTS MML command.

EXTNODE

External Node

None

Enter the external node name assigned to the media gateway you are configuring.

SIDE

Side

Network

Q.931 call model side. Enter user for user side or network for network side.
Default = network. (Used only for IP FAS transport service.)

CUSTGRPID

Customer Group ID

0000

Customer Group ID. Virtual network identification characters (formerly called the VNET ID). Values accepted for this field depend on the use of the D channel. Enter the four-digit ID. (Used only for IP FAS transport service.)

CUSTGRP
TBL

Customer Group Table

NA

Reserved for future use.

ABFLAG

A/B flag

N

A/B flag. Specifies digital private network signaling system (DPNSS) a or b side. Enter A for a side, B for b side, or N for not applicable. (Used only for IP FAS transport service.)

CRLEN

Call Reference Length

2

Call reference length. Enter 0 for DPNSS, 1 for one-byte call reference, or 2 for two-byte call reference. Default = 2. (Used only for IP FAS transport service.)

DESC

Description

None

Text description of this signaling service. Enter as many as 128 characters and enclose in straight quotes.


Table 1-21: Media Gateway Signaling Service Configuration Parameters
MML Parameter Name Configuration Setting

NAME

 

MDO

 

EXTNODE

 

DESC

 

IP Links

To provision a media gateway IP link, you must configure the following component types:

Table 1-22 lists and describes the configuration parameters that define each link. Table 1-23 serves as a form for planning a single IP link.


Table 1-22: IP-Link Configuration Parameter Descriptions
MML Parameter Name CMM Parameter Name Default Value Description

NAME

MML Name

None

Unique name for this link. Enter as many as 10 alphanumeric characters (or 20 alphanumeric characters for Release 7.4) and enclose in straight quotes. Dashes (-) can be used.

IF

Enet Line Interface

None

Ethernet interface to which this link connects. Enter the MML name of a previously defined Ethernet interface.

DESC

Description

None

Text description of this link. Enter as many as 128 characters and enclose in straight quotes.

IPADDR

IP Address

None

Cisco SC host IP address for interface. Enter the IP address variable defined in the XECfgParm.dat file during the installation of the Cisco SC software. Valid entries ar: IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.

PEERADDR

Peer Address

None

Remote IP address of link interface on media gateway.

PEERPORT

Peer Port

None

Port number of link interface on remote device.
Enter any valid IP port number greater than 1024. For MGCP and SGCP, 2427 is recommended.

PORT

Port

None

Local port number of link interface on the Cisco SC host. Enter any valid IP port number greater than 1024.

PRI

Priority

1

Priority. Enter an integer that is greater than 0.

SIGPORT

Signal Port

0

Physical port on the gateway on the slot.Value range: 0 through 168. (Used only to support IPFAS.)

SIGSLOT

Signal Slot

0

Physical slot on the gateway where the T1/E1 is plugged into.
Value range: 0 through 63. (Used only to support IPFAS.)

SVC

IP Signaling Services

None

Signaling service this IP supports. Enter the MML name of a previously defined signal service.

SIGPORTSKIP

 

0

Signal port skip. The number of SIGPORT values to be skipped before using the next value. (Used only for NFAS signaling type.)


Table 1-23: IP-Link Configuration Parameters
MML Parameter Name Value

NAME

 

IF

 

DESC

 

IPADDR

 

PEERADDR

 

PEERPORT

 

PORT

 

PRI

 

SIGPORT

 

SIGSLOT

 

SVC

 

Upgrading from Cisco SS7 Interconnect for Access Servers Solution Release 2.1 to Release 2.2

To upgrade from the Cisco SS7 Interconnect for Access Servers Solution Release 2.1 to Release 2.2, you must upgrade the Cisco Telephony Controller Software Release 7.3(x) to Cisco Media Gateway Controller Software Release 7.4(x). Refer to Chapter 2, Installing the Cisco Media Gateway Controller Software, in the Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for instructions.

Minimum Hardware Requirements

Your system must meet the minimum requirements shown in the following tables. If your system does not meet these requirements, you must upgrade components. See "Backing Up and Restoring Your Data," and "Upgrading Hardware."

Caution The amount and speed of hardware such as processors and memory strongly impacts the call processing power and speed of the Cisco SS7 Interconnect for Access Servers Solution. Before using the minimum hardware configuration, consult with your Cisco representative to determine the hardware that will give you the best results based on your network configuration, proposed traffic, and desired processing power. In particular, B-number analysis or screening, long call hold times, and SCP queries may require additional hardware resources.
Note   Always consult the latest version of the Release Notes for Cisco Telephony Controller Software Release 7.3(x) or Release Notes for Cisco Media Gateway Controller Software Release 7.4(x) (available from your Cisco representative) to determine if any new or additional hardware or software is required.

Host Minimum Server Requirements

Table 1-24 shows the host minimum hardware requirements.


Table 1-24: Host Minimum Hardware Requirements
Component Sun Netra t 1120/1125 Sun Netra t1400/t1405 Sun E4501

Processor

2 300 MHz

2 440 MHz2

2 300 MHz

Disk drive

1 9-gigabyte3

1 9-gigabyte4

1 9-gigabyte5

CD-ROM drive

1

1

1

DAT 3-Drive

optional

optional

optional

RAM

1 gigabyte

1 gigabyte

1 gigabyte

1Supported for existing installations only; no longer orderable.
2300 MHz processors are not available in the Sun Netra t1400/t1405. The minimum processor speed available is 440 MHz.
3Two disks are required for disk mirroring. Cisco highly recommends disk mirroring.
4Two disks are required for disk mirroring. Cisco highly recommends disk mirroring.
5Two disks are required for disk mirroring. Cisco highly recommends disk mirroring.

Interface Options

Table 1-25 shows the signaling and Ethernet interface options.


Table 1-25: Interface Options
Interface Options Sun Netra t 1120/1125 Sun Netra t1400/t1405 Sun E4501

ITK E1/T1 card

Supported

Not supported

Supported

PTI V.35 card

Supported

Not supported

Supported

Sun Ethernet 1-port card

Required

Required

Required

Cisco SLT

Supported

Supported

Supported

1Supported for existing installations only; no longer orderable.

Note   Cisco recommends that you upgrade to the Cisco SLT to terminate signaling. ITK T1/E1 and PTI V.35 cards are no longer orderable.

Ancillary Hardware Requirements

Table 1-26 shows the ancillary hardware requirements.


Table 1-26: Ancillary Hardware
Component Sun Netra t 1120/1125 Sun Netra t1400/t1405 Sun E450

Dataprobe ARU

Supported

Note   Not recommended; you should use the built-in alarm card and software.

Not supported

Supported; not required if alarm functions not necessary

Dataprobe A/B Switch

Required with use of ITK T1/E1 or PTI V.35 cards1

Not supported

Required with use of ITK T1/E1 or PTI V.35 cards2

Asynch Extension

Optional for simplex configurations; required with use of Dataprobe A/B switch

Not supported

Optional for simplex configurations; required with use of Dataprobe A/B switch

1Call preservation upon switchover or failover is not supported with the A/B switch.
2Call preservation upon switchover or failover is not supported with the A/B switch.

NAS Hardware Requirements

For Cisco IOS memory requirements, see the Cisco IOS release notes listed in Table 1-27:


Table 1-27: NAS Release Notes
NAS Release Notes

Cisco AS52001

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5200/ios52/index.htm

Cisco AS5300

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosrn/index.htm

Cisco AS5800

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/58_iosrn/index.htm

Note   AS5800 modem boards require at least 64 MB of memory per board. The part number for the correct modem board is MEM=200/NPE-64MB=.

1Supported for existing installations only; no longer orderable.

Software Requirements

Table 1-28 shows the software requirements for the components in the Cisco SS7 Interconnect for Access Servers Solution. Gather the required software before beginning the upgrade.

Note   Always consult the latest version of the Release Notes for Cisco Telephony Controller Software Release 7.3(x) or Release Notes for Cisco Media Gateway Controller Software Release 7.4(x) (available from your Cisco representative) to determine if any new or additional hardware or software is required.
Note   A minimum of 2 gigabytes of swap space is required for the Cisco SS7 Interconnect for Access Servers Solution Release 2.1 or Release 2.2

Table 1-28: Software Requirements 
Component

Required Software Release

Required Firmware (If applicable)

 SC host


  • Sun Solaris 2.6
    

  • Veritas Volume Manager 2.6 (for mirrored drives only)
    

  • Cisco Telephony Controller Software Release 7.3(x)
    

  • Cisco MGC Installation CD
    



 None


 CiscoSLT


 Refer to the release notes for CiscoTelephony Controller Software Release 7.3(x) or CiscoMedia Gateway Controller Release 7.4(x).


 None


 CiscoAS52001


 Refer to the release notes for CiscoTelephony Controller Software Release 7.3(x) or CiscoMedia Gateway Controller Release 7.4(x).


 Refer to the Cisco AS5X00 MICA 6-Port and 12-Port Modem Module Portware/Cisco IOS Software Compatibility Matrixes


 CiscoAS5300


 Refer to the release notes for CiscoTelephony Controller Software Release 7.3(x) or CiscoMedia Gateway Controller Release 7.4(x).


 Refer to the Cisco AS5X00 MICA 6-Port and 12-Port Modem Module Portware/Cisco IOS Software Compatibility Matrixes


 CiscoAS5800


 Refer to the release notes for CiscoTelephony Controller Software Release 7.3(x) or CiscoMedia Gateway Controller Release 7.4(x).


 Refer to the Cisco AS5X00 MICA 6-Port and 12-Port Modem Module Portware/Cisco IOS Software Compatibility Matrixes
1The Cisco AS5200 is supported for existing installations only.

Upgrade Procedures Overview

This section provides an overview of upgrade procedures for the Cisco SS7 Interconnect for Access Servers Solution. Install and upgrade the hardware and software in the order outlined in the following tables.

Upgrading a Simplex Configuration

To upgrade a simplex configuration: 


Step

Chapter/Section


Step1 


 Prepare by gathering the required hardware, software, and information you need to perform the upgrade.


 "Before Starting the Upgrade" section



Step2 


 Back up your data.







Note   Call processing must be stopped at this time. The host will be out of service until the upgrade is completed.




 


 "Backing Up and Restoring Your Data"



Step3 


 Perform hardware upgrades if necessary.


 "Upgrading Hardware"



Step4 


 Install and configure the CiscoSLT, unless ITK cards are used.


 "Installing and Configuring the Cisco SLT"



Step5 


 Upgrade the operating system and associated software, including:


  • Sun Solaris 2.6
    

  • Alarm card software
    

  • Ethernet interfaces
    

  • Second disk drives (for mirrored disks)
    



 "Installing the Sun Solaris 2.6 Operating System"



Step6 


 Restore your backed up SC software data.


 "Restoring Your SC Host Data" section



Step7 


 Install the SC software.


 "Installing SC Software Release 7.3(x)" section or "Installing SC Software Release 7.4(x)" section



Step8 


 Configure SNMP resources.


 "Configuring SNMP Support Resources" section



Step9 


 Configure the execution environment parameters.


 "Configuring the Execution Environment" section



Step10 


 Configure SCP queries.


 "Configuring SCP Queries" section



Step11 


 Terminate signaling links into the CiscoSLTs, unless ITK cards are used.


 "Terminating Signaling Links" section



Step12 


 Provision your system, including CiscoSLTs (if used).


 "Provisioning the Configuration" section



Step13 


 Upgrade Cisco IOS software on the NASs.1


 "Restarting and Verifying the Newly Upgraded Host" section



Step14 


 Start the software on the newly upgraded host and verify that it is working.


 "Restarting and Verifying the Newly Upgraded Host" section
1NASs = network access servers.

Upgrading a High-Availability Configuration

To upgrade a high-availability configuration: 


Step

Chapter/Section


Step1 


 Prepare by gathering the required hardware, software, and information you need to perform the upgrade.


 "Before Starting the Upgrade" section


 



Step2 


 Back up your data on the standby machine.







Note   The standby host is upgraded, leaving the active host to process calls. Unless the active host goes down, call processing will not be affected.




 


 "Backing Up and Restoring Your Data"



Step3 


 Perform hardware upgrades if necessary.


 "Upgrading Hardware"



Step4 


 Install and configure the CiscoSLT, unless ITK cards are used.







Note   Do not connect the signaling links to the Cisco SLT during this step, or call processing will stop.




 


 "Installing and Configuring the Cisco SLT"



Step5 


 Upgrade the operating system and associated software on the standby host, including:


  • Sun Solaris 2.6
    

  • Alarm card software
    

  • Ethernet interfaces
    

  • Second disk drives (for mirrored disks)
    



 "Installing the Sun Solaris 2.6 Operating System"


 



Step6 


 Restore your backed up SC data files.


 "Restoring Your SC Host Data" section



Step7 


 Install the SC software on the standby host.


 "Installing and Configuring the SC Software"



Step8 


 Configure SNMP resources.


 "Configuring SNMP Support Resources" section



Step9 


 Configure the execution environment parameters.







Note   Be sure to change the *.desiredPlatformState of the machine you are upgrading to Master, and change the pom.dataSync parameter to false.




 


 "Configuring the Execution Environment" section



Step10 


 Configure SCP queries on the standby host.


 "Configuring SCP Queries" section



Step11 


 Terminate signaling links from the newly upgraded host into the CiscoSLTs, unless ITK cards are used.


 "Terminating Signaling Links" section



Step12 


 Provision your system, including CiscoSLTs (if used).


 "Provisioning the Configuration" section



Step13 


 Upgrade Cisco IOS software on the NASs.1







Note   All calls on the NASs will be dropped during the software upgrade.




 


 "Restarting and Verifying the Newly Upgraded Host" section



Step14 


 Start the software on the newly upgraded host and verify that it is working.


 "Restarting and Verifying the Newly Upgraded Host" section



Step15 


 Upgrade and verify the second server.


 "Upgrading and Verifying the Second Server" section



Step16 


 Complete the upgrade by removing and installing required software on the newly standby host.







Note   Be sure to change the *.desiredPlatformState of the machine you are upgrading to slave, and change the pom.dataSync parameter to true. On the active host (the first host you upgraded), change the pom.dataSync parameter to true and perform switchover.




 


 "Upgrading and Verifying the Second Server" section
1NASs = network access servers.

Where to Go Next

Proceed to "Backing Up and Restoring Your Data."


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 8 05:26:16 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.