Table Of Contents

Solution-Level Upgrade Procedures

Solutions Overview

Before Starting the Upgrade

General Tips

Gathering Required Software and Hardware

Gathering Required Information

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

Gathering Provisioning Data

Minimum SC Hardware Requirements

SC Software Requirements

Solution-Specific Requirements

Upgrade Procedures

Upgrading from the Cisco SS7 DAS Release 2.0 to the Cisco SS7 Interconnect for Access Servers Solution Release 2.x

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

Upgrading within the Cisco SS7 Interconnect for Voice Gateways Solution, from Release 1.0 or 1.1 to Release 1.3

Solution-Level Upgrade Procedures

---

Solutions 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 (also referred to as the Cisco SC2200 product) 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 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 the Cisco SS7 Dial Access Solution 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 Cisco SLT can be located remotely from the Cisco SC host using a dedicated link. Refer to the Cisco SLT documentation for details.

---

The Cisco SS7 Interconnect for Voice Gateways Solution is a distributed system that provides SS7 connectivity for Voice over IP (VoIP) access gateways by using the Cisco SC2200 and the access gateways as a bridge from the H.323 IP network to the PSTN network. This solution interacts over the IP network with other Cisco H.323 VoIP access gateways. In addition, the Cisco SS7 Interconnect for Voice Gateways Solution can interoperate with H.323 endpoints, using non-SS7 signaling such as ISDN PRI and channelized T1.

The Cisco SS7 Interconnect for Voice Gateways Solution also uses the Cisco SLTs to terminate the first and second MTP layers of SS7 signaling. Bearer traffic remains on the voice gateways.

The upgrade process for the Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions is described in the following sections:

• Before Starting the Upgrade

• Upgrade Procedures

Before Starting the Upgrade

The information you need to be aware of before upgrading is found in the following sections:

• General Tips

• Gathering Required Software and Hardware

• Gathering Provisioning Data

• Minimum SC Hardware Requirements

• SC Software Requirements

• Solution-Specific Requirements

General Tips

Before you upgrade the SC host software, check the following:

•Begin the upgrade process during a maintenance window or low traffic period to minimize call attempt losses, and plan for system downtime accordingly. In a simplex configuration, the host stops processing calls at the beginning of the upgrade. In a continuous service configuration, the standby SC host is upgraded. Calls would only be lost if a failure occurred on the active SC host during the upgrade process.

---

Caution If you upgrading from the Cisco SS7 DAS Release 2.0 to the Cisco SS7 Interconnect for Access Servers Solution, all calls will be lost during the upgrade, because 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.

---

•Have your company's internal support information and Cisco Systems support contact information available to help you with the installation or upgrade if needed. (See the "Obtaining Technical Assistance" section on page xviii for Cisco support contact information.) Depending on your level of UNIX expertise, you might need to have your UNIX system administrator available for assistance during the upgrade.

•Review the software terms and conditions.

•Review the software and tool requirements and procedural overview.

•Review the hardware and software requirements found in the Release Notes for the Cisco SS7 Interconnect for Access Servers Solution or Release Notes for the Cisco SS7 Interconnect for Voice Gateways Solution.

•Ensure that all systems are working properly and that there are no alarms.

---

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 SC Hardware Requirements" section and "SC Software Requirements" section. At a minimum, you must obtain the following CD-ROM disks:

•Sun SolarisTM Operating Environment Installation CD, September 1999, p/n: 704-6914-10

•Sun SolarisTM 2.6 Software, p/n: 704-6220-10

•Sun SolarisTM 2.5.1 Software, to be used if you need to back out of the Sun SolarisTM 2.6 upgrade and reinstall Sun SolarisTM.

•Cisco Telephony Controller Software Release 7.3(x) CD or Cisco Media Gateway Controller Release 7.4(x) CD

•Cisco MGC Installation CD—Includes software for Sun SolarisTM Y2K patches, Volume Manager software, and the log and spool software.

---

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.

---

•Sun Netra t 112x CD, if installing alarm card software.

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:

•SC host server name and IP address

•Root password

•Subnet netmask

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

If you are upgrading a Cisco SS7 DAS Release 2.0 system, you must review your components.dat and properties.dat files to determine whether 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 Software Release 7 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 and Voice Gateways Solutions Provisioning Guide or the Cisco SS7 Interconnect for Voice Gateways Solution Release 1.3 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 the command line interface, MML, or a Cisco-provided GUI provisioning tool. The following GUI provisioning tools are available for your SC software:

•Telephony Controller Manager (TCM)—Available only with software release 7.3(x)

•Cisco Media Gateway Controller Manager (CMM)—Available with software release 7.4(x) and later versions of software release 7.3

•Voice Services Provisioning Tool (VSPT)—Available with later versions of software release 7.4(x)

---

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 or Cisco SS7 Interconnect for Voice Gateways 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:

•Provisioning Tool Component Name: PointCode

•MML Component Name: PTCODE

•GUI Provisioning Tool Component Name: APC

•MML Component Name: APC

Table 1-1 Point Code Parameter Descriptions

MML Parameter Name	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: LinkSet

•MML Component Name: LNKSET

---

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	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: SS7SubSys

•MML Component Name: SS7SUBSYS

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	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: SS7Route

•MML Component Name: SS7ROUTE

Table 1-8 SS7 Route Configuration Parameter Descriptions 

MML Parameter Name	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: SigSS7

•MML Component Name: SS7PATH

Table 1-10 SS7 Signaling Service Configuration Parameter Descriptions 

MML Parameter Name	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: Adapter

•MML Component Name: CARD

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.

Table 1-12 Card Configuration Parameter Descriptions for Cisco SLT Communications 

MML Parameter Name	Provisioning Tool 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. This should be EN for Ethernet cards. The ITK and V35 types are no longer supported for use with the Cisco SC software
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:

•GUI Provisioning Tool Component Name: EnetIF

•MML Component Name: ENETIF

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	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: C7IPLink

•MML Component Name: C7IPLNK

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	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: ExtNode

•MML Component Name: EXTNODE

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	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: SigNAS

•MML Component Name: NASPATH

Table 1-20 Media Gateway Signaling Service Configuration Parameter Descriptions 

MML Parameter Name	Provisioning Tool 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:

•GUI Provisioning Tool Component Name: IPLink

•MML Component Name: IPLNK

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	Provisioning Tool 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

Minimum SC 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 Your SC Host Data," and Chapter 5, "Upgrading SC Host 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 and Voice Gateways Solutions. 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 the Cisco SS7 Interconnect for Access Servers Solution or Release Notes for the Cisco SS7 Interconnect for Voice Gateways Solution (available from Cisco.com) to determine whether any new or additional hardware or software is required.

---

SC Host Minimum Server Requirements

Table 1-24 shows the SC host minimum hardware requirements.

---

Note The Sun E450 server is no longer supported for use with the Cisco SC software.

---

Table 1-24 Host Minimum Hardware Requirements 

Component	Sun Netra t 100/105	Sun Netra t 1120/1125	Sun Netra t1400/t1405
Processor	one 440 MHz	two 440 MHz	four 440 MHz
Disk drive	two 18-gigabyte	two 18-gigabyte	two 18-gigabyte
CD-ROM/DVD drive	1CD-ROM drive	1DVD drive	1DVD drive
DAT 3-Drive	N/A	1	1
RAM	1 gigabyte	2 gigabyte	4 gigabyte

Interface Options

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

---

Note The ITK E1/T1 and the PTI V.35 interface cards are no longer supported for use with the Cisco SC software.

---

Table 1-25 Interface Options 

Interface Options	Sun Netra t 100/105	Sun Netra t 1120/1125	Sun Netra t1400/t1405
Sun Ethernet 1-port card	N/A (comes equipped with two Ethernet ports)	Required	Required
Cisco SLT	Supported	Supported	Supported

Ancillary Hardware

The following pieces of ancillary hardware are no longer supported for use with the Cisco SC software:

•Dataprobe ARU

•Dataprobe A/B Switch

•Asynch Extension

SC Software Requirements

The SC host requires the software listed below for the Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions. Gather the required software before beginning the upgrade.

•Sun Solaris 2.6

•Veritas Volume Manager 2.6 (for mirrored drives only)

•Cisco Telephony Controller Software Release 7.3(x) or Cisco Media Gateway Controller Software Release 7.4(x)

•Cisco MGC Installation CD

---

Note A minimum of 2 gigabytes of swap space is required for the Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions

---

Solution-Specific Requirements

To determine the latest hardware and software requirements for your solution, see the following online documents:

• Release Notes for Cisco SS7 Interconnect for Access Servers Release 2.2(B)

• Release Notes for Cisco SS7 Interconnect for Voice Gateways Release 1.3

Upgrade Procedures

This section provides the upgrade procedures for the Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions, as described in the following sections:

• Upgrading from the Cisco SS7 DAS Release 2.0 to the Cisco SS7 Interconnect for Access Servers Solution Release 2.x

• Upgrading within the Cisco SS7 Interconnect for Access Servers Solution, from Release 2.1 to Release 2.2

• Upgrading within the Cisco SS7 Interconnect for Voice Gateways Solution, from Release 1.0 or 1.1 to Release 1.3

Upgrading from the Cisco SS7 DAS Release 2.0 to the Cisco SS7 Interconnect for Access Servers Solution Release 2.x

Upgrading from the Cisco DAS Release 2.0 to the Cisco SS7 Interconnect for Access Servers Solution is described in the following sections:

• Upgrading a Simplex Configuration

• Upgrading a High-Availability Configuration

Upgrading a Simplex Configuration

To upgrade a simplex configuration, perform the steps in Table 1-26:

Table 1-26 Upgrading a Cisco DAS Release 2.0 System with an SC host in a Simplex Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note Call processing must be stopped at this time. The SC host will be out of service until the upgrade is completed.	Backing Up Your SC Host Data
Step 3	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 4	Install and configure Cisco SLTs.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 5	If necessary, perform SC host hardware upgrades.	Upgrading SC Host Hardware, page 5-1
Step 6	If necessary, 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 Operating System on the SC Hosts, page 6-1
Step 7	Uninstall the old SC software.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software.	Installing SC Software Release 7.3(x), page 7-5 or Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	Restore your backed up SC software data.	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 12	Configure SNMP resources.	Configuring SNMP Support Resources, page 7-13
Step 13	Configure the execution environment parameters.	Configuring the Execution Environment, page 7-19
Step 14	Configure SCP queries.	Configuring SCP Queries, page 7-38
Step 15	Terminate signaling links to Cisco SLTs.	Terminating Signaling Links, page 7-56
Step 16	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 17	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 18	Provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

Upgrading a High-Availability Configuration

To upgrade a high-availability configuration, perform the steps in Table 1-26:

Table 1-27 Upgrading a Cisco DAS Release 2.0 System with SC hosts in a High Availability Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note The standby SC host is upgraded, leaving the active SC host to process calls. Unless the active SC host goes down, call processing will not be affected.	Backing Up Your SC Host Data
Step 3	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 4	Install and configure the Cisco SLTs. Note Do not connect the signaling links to the Cisco SLT during this step, or call processing will stop.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 5	If necessary, perform SC host hardware upgrades.	Upgrading SC Host Hardware, page 5-1
Step 6	Upgrade the operating system and associated software on the standby SC host, including: •Sun Solaris 2.6 •Alarm card software •Ethernet interfaces •Second disk drives (for mirrored disks)	Installing the Operating System on the SC Hosts, page 6-1
Step 7	Uninstall the old SC software on the standby SC host.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software on the standby SC host.	Installing SC Software Release 7.3(x), page 7-5 or Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	Restore your backed up SC host data files on the standby SC host.	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 12	Configure SNMP resources on the standby SC host.	Configuring SNMP Support Resources, page 7-13
Step 13	Configure the execution environment parameters on the standby SC host. Note When you upgrade the first SC host, ensure that the value of *.desiredPlatformState is Master and pom.dataSync is false. When you upgrade the second SC host, ensure that the value of *.desiredPlatformState is Slave and pom.dataSync is true.	Configuring the Execution Environment, page 7-19
Step 14	Configure SCP queries on the standby SC host.	Configuring SCP Queries, page 7-38
Step 15	Terminate signaling links to the Cisco SLTs.	Terminating Signaling Links, page 7-56
Step 16	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 17	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 18	Upgrade and verify the other SC host.	Repeat steps 7 through 17 on the other SC host.
Step 19	Reset the value of pom.dataSync to true in the first SC host.	Resetting the Configuration, page 7-68
Step 20	Provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

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

Upgrading within the Cisco SS7 Interconnect for Access Servers Solution, from Release 2.1 to Release 2.2 is described in the following sections:

• Upgrading a Simplex Configuration

• Upgrading a Continuous Service Configuration

Upgrading a Simplex Configuration

To upgrade a simplex configuration, perform the steps in Table 1-28:

Table 1-28 Upgrading a Cisco SS7 Interconnect for Access Servers Release 2.1 System with an SC host in a Simplex Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note Call processing must be stopped at this time. The SC host will be out of service until the upgrade is completed.	Backing Up Your SC Host Data
Step 3	If you are using the Cisco Media Gateway Controller Node Manager (CMNM) software to manage the Cisco SC2200, ensure that you have the latest CMNM patches installed.	Proceed to the CMNM patch web page at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mgc-nm The installation instructions for each patch are found in the associated README files.
Step 4	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 5	Upgrade the software on the Cisco SLTs.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 6	Identify the name of the active configuration.	Identifying the Active Configuration, page 7-2
Step 7	Uninstall the old SC software.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software.	Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	Configure SNMP resources.	Configuring SNMP Support Resources, page 7-13
Step 12	Configure the execution environment parameters.	Configuring the Execution Environment, page 7-19
Step 13	Configure SCP queries.	Configuring SCP Queries, page 7-38
Step 14	If you are upgrading from ITK/PTI cards to Cisco SLTs, terminate signaling links to the Cisco SLTs.	Terminating Signaling Links, page 7-56
Step 15	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 16	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 17	If necessary, provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

Upgrading a Continuous Service Configuration

To upgrade a continuous service configuration, perform the steps in Table 1-29:

Table 1-29 Upgrading a Cisco SS7 Interconnect for Access Servers Solution Release 2.1 System with SC hosts in a Continuous Service Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note The standby SC host is upgraded, leaving the active SC host to process calls. Unless the active SC host goes down, call processing is not affected.	Backing Up Your SC Host Data
Step 3	If you are using the Cisco Media Gateway Controller Node Manager (CMNM) software to manage the Cisco SC2200, ensure that you have the latest CMNM patches installed.	Proceed to the CMNM patch web page at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mgc-nm The installation instructions for each patch are found in the associated README files.
Step 4	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 5	Upgrade the software on the Cisco SLTs.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 6	Identify the name of the active configuration.	Identifying the Active Configuration, page 7-2
Step 7	Uninstall the old SC software on the standby SC host.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software on the standby SC host.	Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	Check the value of pom.dataSync. When you upgrade the first SC host, ensure that the value of pom.dataSync is false. When you upgrade the second SC host, ensure that the value of pom.dataSync is true.	Opening the XECfgParm.dat File, page 7-20, Initializing the Provisioning Object Manager (POM), page 7-37, and Saving the XECfgParm.dat File, page 7-37
Step 12	If you are upgrading from ITK/PTI cards to Cisco SLTs, terminate signaling links to the Cisco SLTs.	Terminating Signaling Links, page 7-56
Step 13	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 14	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 15	Upgrade and verify the other SC host.	Perform steps 6 through 14 on the other SC host.
Step 16	Reset the value of pom.dataSync to true in the first SC host.	Resetting the Configuration, page 7-68
Step 17	If necessary, provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

Upgrading within the Cisco SS7 Interconnect for Voice Gateways Solution, from Release 1.0 or 1.1 to Release 1.3

Upgrading within the Cisco SS7 Interconnect for Voice Gateways Solution, from Release 1.0 or 1.1 to Release 1.3 is described in the following sections:

• Upgrading a Simplex Configuration

• Upgrading a Continuous Service Configuration

Upgrading a Simplex Configuration

To upgrade a simplex configuration, perform the steps in Table 1-30:

Table 1-30 Upgrading a Cisco SS7 Interconnect for Voice Gateways Release 1.0 or 1.1 System with an SC host in a Simplex Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note Call processing must be stopped at this time. The SC host will be out of service until the upgrade is completed.	Backing Up Your SC Host Data
Step 3	If you are using the Cisco Media Gateway Controller Node Manager (CMNM) software to manage the Cisco SC2200, ensure that you have the latest CMNM patches installed.	Proceed to the CMNM patch web page at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mgc-nm The installation instructions for each patch are found in the associated README files.
Step 4	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 5	Upgrade the software on the Cisco SLTs.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 6	Identify the name of the active configuration.	Identifying the Active Configuration, page 7-2
Step 7	Uninstall the old SC software.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software.	Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 12	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 13	If necessary, provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

Upgrading a Continuous Service Configuration

To upgrade a continuous service configuration, perform the steps in Table 1-31:

Table 1-31 Upgrading a Cisco SS7 Interconnect for Voice Gateways Solution Release 1.0 or 1.1 System with SC hosts in a Continuous Service Configuration  

	Step	Chapter/Section
Step 1	Prepare by gathering the required hardware, software, and information you need to perform the upgrade.	Before Starting the Upgrade
Step 2	Back up your SC host data. Note The standby SC host is upgraded, leaving the active SC host to process calls. Unless the active SC host goes down, call processing will not be affected.	Backing Up Your SC Host Data
Step 3	If you are using the Cisco Media Gateway Controller Node Manager (CMNM) software to manage the Cisco SC2200, ensure that you have the latest CMNM patches installed.	Proceed to the CMNM patch web page at the following URL: http://www.cisco.com/cgi-bin/tablebuild.pl/mgc-nm The installation instructions for each patch are found in the associated README files.
Step 4	Upgrade the software on your media gateways. Note All calls on the media gateways are dropped during the software upgrade.	Cisco Media Gateway Upgrade Procedures, page 3-1
Step 5	Upgrade the software on the Cisco SLTs.	Cisco Signaling Link Terminal Upgrade Procedures, page 4-1
Step 6	Identify the name of the active configuration.	Identifying the Active Configuration, page 7-2
Step 7	Uninstall the old SC software on the standby SC host.	Removing a Previous Version of the Cisco Telephony Controller Software (Release 4 and Release 7.3(x)), page 7-3 or Removing a Previous Version of the Cisco MGC Software (Release 7.4(x)), page 7-4
Step 8	Install the new SC software on the standby SC host.	Installing SC Software Release 7.4(x), page 7-7
Step 9	Install patches to the new SC software version	Installing Patches for the SC Software, page 7-10
Step 10	If necessary, install your GUI provisioning tool on a separate server	Installing a GUI Provisioning Tool on a Separate Server, page 7-10
Step 11	Check the value of pom.dataSync. When you upgrade the first SC host, ensure that the value of pom.dataSync is false. When you upgrade the second SC host, ensure that the value of pom.dataSync is true.	Opening the XECfgParm.dat File, page 7-20, Initializing the Provisioning Object Manager (POM), page 7-37, and Saving the XECfgParm.dat File, page 7-37
Step 12	Start the software on the newly upgraded SC host.	Restarting the SC Software, page 7-56
Step 13	Verify that the newly installed software is working properly.	Verifying SC Software is Running Properly, page 7-59
Step 14	Upgrade and verify the other SC host.	Perform steps 6 through 13 on the other SC host.
Step 15	Reset the value of pom.dataSync to true in the first SC host.	Resetting the Configuration, page 7-68
Step 16	If necessary, provision your Cisco SC2200, including Cisco SLTs.	Provisioning the Configuration, page 7-68

Posted: Wed Oct 20 13:27:48 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.