Cisco Media Gateway Controller Software
Installation and Configuration Guide
(Releases 9.1 through 9.6)
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-1150-15
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of
Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step,
Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study,
LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way
to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0710R)
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
Copyright © 2001-2007, Cisco Systems, Inc.
All rights reserved.
CONTENTS
Preface
xiii
Document Objectives
Audience
i-xiii
i-xiii
Document Conventions
i-xiii
Documentation Map i-xvi
Related Documentation
i-xvii
Obtaining Documentation, Obtaining Support, and Security Guidelines
Document Change History
CHAPTER
1
i-xvii
i-xvii
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
1-1
Supported Platforms and Cisco Products 1-1
Software Release 9.2(x) or Higher 1-1
Software Release 9.1(5) 1-2
Solaris 8, Cisco MGC 9.2(x) and Higher Software Release Pre-Installation Checklists
Required Software Media 1-2
Minimum System Requirements 1-3
Required Site-specific Information 1-3
Required Machine-specific Information 1-4
Required Tasks 1-4
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Required Software Media 1-4
Required Site-specific Information 1-5
Required Machine-specific Information 1-6
Required Tasks 1-6
Optional Components for Solaris 2.6 Installation 1-6
CHAPTER
2
Sun Solaris 8 Operating System Installation
Overview
1-2
1-4
2-1
2-1
Supported Platforms
Supported Disk Drives
2-2
2-2
Before You Start 2-3
Cautions, Notes, and Tips
2-3
Loading the Solaris 8 Operating System
2-4
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
iii
Contents
Devices on Supported Platforms 2-4
Booting from a Local CD-ROM 2-4
Installing the Solaris 8 Operating System 2-15
Verifying Network Time Protocol (NTP) Packages
2-31
Configuring a Second Disk Drive 2-32
Installing the Solstice DiskSuite (CSCOh016) 2-32
Rebooting from the Mirrored (Secondary) Disk 2-34
Removing the Solstice DiskSuite 2-36
Installing the Log and Spool File Systems (CSCOh005) 2-37
Uninstalling the Log and Spool File System 2-43
Configuring Additional Ethernet Interfaces
2-45
Installing the Alarm Software 2-46
Installing Lights Out Management Software 2-47
Alarm Card Software Installation for Netra t 1120/1125
Installing the Solaris 8 Patch Cluster (CSCOh015)
2-51
Installing the BAMS Disk Array on a Netra t 140x Host
Installing the RAID Manager Software 2-55
Configuring the RAID Module 2-55
Verifying/Upgrading Firmware 2-56
Configuring LUNs 2-56
Verifying the RAID Module 2-56
Troubleshooting 2-57
Netra t 10x 2-57
Swap File Size Input
CHAPTER
3
2-50
2-54
2-57
Cisco MGC Software Release 9 Installation
Before You Start 3-1
Cautions, Notes, and Tips
3-1
3-2
Cisco MGC Software Installation/Uninstallation Sequence
3-3
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Installing on a Simplex System 3-3
Installing on a Fault Tolerant System 3-15
3-3
Installing the Cisco Security Package (CSCOh013) 3-16
Removing the Cisco Security Package (CSCOh013) 3-20
Verification Test Suite (VTS) Package (CSCOh014) Overview
Installing the VTS Package 3-23
Using the SunVTS Test Package 3-26
Normal Unit Test 3-26
3-22
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
iv
OL-1150-15
Contents
Running a Test in Brief Mode 3-30
Running a Test in Full Mode 3-30
vts_script Execution Times 3-31
Removing SunVTS 3-31
Removing the VTS Package (CSCOh014) 3-32
CHAPTER
4
Cisco PGW 2200 Security Enhancements
Supported Platforms
4-1
4-2
Feature Overview 4-2
Client/Server and Secure Connectivity Relationships 4-3
Secure Connectivity Among Cisco PGW 2200 Applications 4-3
Secure Connectivity Between Cisco MGC Application Platforms 4-5
Secure Connectivity Between BAMS Application Platforms 4-5
Secure Connectivity Between BAMS and Cisco MGC Application Platforms
4-5
Installation Overview 4-6
Conditions for Installation 4-6
CSCOk9000 and CSCOh013 Security Packages 4-7
Installation Sequence 4-8
Server and Client Platforms Application Example 4-9
Export Control Splash Screens 4-9
CSCOk9000 Security Package Functions 4-10
Connecting to the Cisco PGW 2200, BAMS, and HSI 4-10
Telnet and FTP Toggle Options 4-10
Installing the CSCOk9000 Security Package 4-10
Installing CSCOk9000 on the Cisco PGW 2200 Host
Installing the CSCOk9000 on BAMS 4-15
Installing CSCOk9000 on HSI 4-18
Securing the Networks 4-18
Securing the Cisco PGW 2200 4-19
Securing BAMS 4-20
Uninstalling the CSCOk9000 Security Package
Fallback Procedures 4-29
Procedures for Cisco PGW 2200
Procedures for BAMS 4-30
Alarms and Messages
CHAPTER
5
4-11
4-27
4-29
4-32
Configuring the Cisco MGC Software
5-1
Quick Guide to Configuring the Cisco MGC Software
5-1
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
v
Contents
Before You Start 5-3
Software Directory Structure
5-3
Initial Cisco MGC Software Configuration 5-4
Parameters Required for Initial Setup 5-7
Using the Cisco MGC Environment Configuration Tool
5-8
Configuring Groups and Users 5-10
Verifying the mgcgrp Group 5-10
Adding a User with Full MML Privileges 5-11
Adding a User with Minimal MML Privileges 5-11
Configuring SNMP Support Resources 5-12
Migrating the SNMP Configuration to a More Secure Environment (for MGC 9.3(2) or Later)
Basic Tasks 5-13
Before You Run the config-snmp Utility 5-13
Running the config-snmp Utility 5-14
Adding an SNMP Community Entry 5-15
Deleting an SNMP COMMUNITY 5-18
Adding a Trap Destination 5-19
Deleting a Trap Destination 5-20
Activating the New Settings 5-21
Verifying the SNMP Configuration Migration 5-22
Setting up the SNMP Community for Software Releases Before Cisco MGC 9.3(2) 5-24
Adding a New Community 5-24
Setting the Destination for Traps 5-24
Configuring SNMP Entries 5-25
Configuring the Execution Environment 5-27
Changing XECfgParm.dat File Parameters 5-27
Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System
Configuring Basic System Information 5-29
Specifying IP Addresses 5-31
Configuring Engine Parameters 5-32
Enabling Call Screening 5-35
Configuring Call Detail Record File Output 5-36
Configuring the Clearing Location and Default Location Parameters 5-38
Configuring Switchover 5-41
Initializing the Provisioning Object Manager 5-43
Configuring SCP Queries 5-45
Before You Start 5-45
Configuring the trigger.dat File Attributes 5-45
Configuring the Global Title Translation Attribute
5-13
5-28
5-46
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
vi
OL-1150-15
Contents
Configuring the Service Key Value Attribute 5-46
Configuring the Translation Type Attribute 5-47
Sample trigger.dat File 5-49
Initializing the Call Screening Database 5-57
.odbc.ini File Information 5-58
Setting Up Replication 5-58
Network Requirements 5-58
Initializing Database Replication 5-60
Verifying Database Replication 5-61
Troubleshooting the Main Memory Database Replication 5-61
Displaying the Main Memory Database Replication Status 5-62
Verifying Database Synchronization 5-62
Synchronizing Databases 5-62
Checking for Installation Errors 5-63
Reinstalling CSCOga002 5-63
Configuring Cisco SLTs
5-63
Configuring Disk Monitor During Initial Software Configuration
Configuring the Data Dumper
5-65
Configuring the Data Dumper to Support BAMS
CHAPTER
6
Upgrading the Cisco MGC Software
Requirements for Upgrading
5-64
5-66
6-1
6-1
Quick Guide to Upgrading Your Cisco MGC Software
6-2
Before You Begin 6-3
If You are Upgrading from Cisco MGC 7.4(x) 6-3
If You are Upgrading from a Cisco MGC 9.x Release to Another 9.x Release
Back Up Your Software 6-4
Check for Mated STP Pairs 6-5
Add an SS7 Route for Each Mated STP (from Release 7.4(x) only) 6-6
Check for ^M Characters in XECfgParm.dat 6-7
Running the dos2unix Utility 6-7
Editing the XECfgParm.dat File 6-7
6-4
Upgrading the Cisco MGC Software Release 6-8
Backing Up the Main Memory Database 6-9
Backing Up the Configuration Data 6-10
Restoring Data Files 6-11
Downgrading the Cisco MGC Software Release 6-15
Scenario 1: Standby Host is Running Cisco MGC 7.4(x) or 9.x
6-15
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
vii
Contents
Scenario 2: Active and Standby Hosts are Running Cisco MGC 9.x or Later Software Release
If Migration Fails
CHAPTER
7
6-16
6-17
Cisco MGC Software Release 9.1(5) Installation
7-1
Before You Start 7-2
Cautions, Notes, and Tips 7-2
Installation Overview 7-2
Cisco MGC Software Installation/Uninstallation Sequence
Installing the Cisco MGC Software Release 9.1(5)
Installing on a Simplex System 7-4
Installing on a Fault Tolerant System 7-6
7-3
7-3
Installing the Cisco Security Package 7-7
Removing the Cisco Security Package 7-11
CHAPTER
8
Sun Solaris 2.6 Operating System Installation
8-1
Installing the Sun Solaris 2.6 and 2.5(1) Operating System 8-1
Booting from a Local CD-ROM on Netra t 1120/1125, t 1400/1405 and t 100/105 8-2
Installing the Solaris 2.6 or 2.5.1 Operating System on Netra t 1120/1125, t 1400/1405 and
t 100/105 8-6
Installing the Solaris Patch Cluster 8-16
Installing the Solaris 2.6 Patch Cluster on Netra t 1120/1125, t 1400/1405 and t 100/105
Installing the Solaris 2.5.1 Patch Cluster on Netra t 1120/1125 and t 1400/1405 8-18
Installing the Alarm Software 8-20
Installing Lights Out Management Software 8-21
Installing the Alarm Card Software for Netra t 1120/1125
PCI Card Configuration
8-16
8-23
8-25
Configuring a Second Ethernet Interface
8-26
Configuring a Second Disk Drive 8-27
Installing the Sun StorEdge Volume Manager 2.6 8-27
Removing the Sun StorEdge Volume Manager 2.6 8-35
Installing Veritas Volume Manager 3.1 8-38
Removing Veritas Volume Manager 3.1 8-46
Installing Log and Spool File Systems 8-48
If the Cisco MGC Software is Already Installed on the Platform 8-48
If the Cisco MGC Software is Not Installed on the Platform 8-56
Replacing Hard Disks for Existing Solaris 2.6 Platforms
Backup Procedure 8-64
Replacing Hard Disks 8-65
8-63
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
viii
OL-1150-15
Contents
Loading the Solaris 2.6 operating system 8-65
Installing the Cisco MGC Software 8-65
Restoring System Files 8-65
Troubleshooting 8-66
Symptom: Netra t 100/105 will not boot from CD-ROM 8-66
Symptom: Installation program will not accept swap file size input 8-66
Symptom: CD-ROM on Netra t 100/105 is not accessible after OS installation
CHAPTER
9
Upgrading the Cisco MGC to Software Release 9.1(5)
Before You Start 9-1
Required Software
8-66
9-1
9-2
Quick Upgrade Guide 9-2
Backing Up System Data 9-2
Removing a Previous Version of the Cisco MGC Software
9-3
Upgrading to Software Release 9.1(5) 9-5
Upgrading a Simplex System 9-5
Upgrading a Fault Tolerant System 9-6
Fallback Procedures
CHAPTER
10
9-8
Configuring the Local Area Network Switch
LAN Switch Overview
10-1
Catalyst 2900 XL Series
10-2
Catalyst 5500 and 5000 Series
APPENDIX
11
10-1
10-2
Migrating to Cisco MGC Software Release 9.3(1)
Before you Begin
11-1
11-1
Conditions for Migration
11-1
Quick Guide to Migration
11-2
Migrating Host B (Standby Box) 11-2
Verify the Existing Network Status 11-2
Back Up the PGW Configuration on Host A 11-3
Back Up the PGW Configuration on Host B 11-3
Remove Cisco MGC 9.2(2) from Host B 11-4
Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host B
Stop Cisco MGC 9.2(2) on Host A 11-5
Start Cisco MGC 9.3(1) on Host B 11-5
Migration Verification on Host B 11-5
Migrating Host A (Active Box)
11-5
11-6
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
ix
Contents
Remove Cisco MGC 9.2(2) from Host A 11-6
Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host A
Start Cisco MGC 9.3(1) on Host A 11-7
Migration Verification on Host A 11-7
Failover Testing
11-7
11-8
Backout Procedures 11-8
Backout After Migration on Host B 11-8
Stop Cisco MGC 9.3(1) on Host B 11-8
Start Cisco MGC 9.2(2) on Host A 11-8
Backout Verification 11-8
Remove Cisco MGC 9.3(1) from Host B 11-9
Install Cisco MGC 9.2(2) and Cisco MGC Patches on Host B 11-9
Start Cisco MGC 9.2(2) on Host B 11-10
Backout Verification on Host B 11-10
Backout After Migration on Host B and Host A 11-10
Stop Cisco MGC 9.3(1) on Host A 11-10
Remove Cisco MGC 9.3(1) from Host A 11-11
Install Cisco MGC 9.2(2) and 9.2(2) Patches on Host A 11-11
Stop Cisco MGC 9.3(1) on Host B 11-12
Start Cisco MGC 9.2(2) on Host A 11-12
Post Backout Verification on Host A 11-12
Remove Cisco 9.3(1) from Host B 11-12
Install Cisco MGC 9.2(2) and 9.2(2) Patches on Host B 11-13
Start Cisco MGC 9.2(2) on Host B 11-13
Post Backout Verification on Host B 11-13
Failover Testing 11-14
APPENDIX
12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Conditions for Migration
Cautions and Notes
Required Software
12-1
12-2
12-3
Backing Up System Data
12-3
Backing Up the Main Memory Database
12-4
Backing Up the Cisco MGC Configuration Files
Installing Solaris 8
12-1
12-5
12-6
Restoring Data Files 12-7
Restoring Data Files from Remote Server or Local Tape Drive 12-7
Restoring Data Files from the Log Partition of the Second Disk 12-8
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
x
OL-1150-15
Contents
Installing the Cisco MGC Software and Patches
12-9
Configuring a Second Disk 12-9
Solstice DiskSuite Installation 12-10
Log and Spool Software Installation 12-10
Installing the Alarm Software
12-11
Installing the Solaris 8 Patch Cluster (CSCOh015)
12-11
Restoring the SNMP Configuration on PGW for Cisco MNM and BAMS
12-11
Falling Back to Solaris 2.6 12-12
Falling Back to Solaris 2.6 If Hard Drives Were Replaced During the Upgrade
Falling Back to Solaris 2.6 on the Second Disk Drive 12-12
Restoring the Original Cisco MGC Software 12-17
Replacing Hard Disks on an Existing Solaris 8 Platform
Backup Procedure 12-17
Hard Disk Replacement Procedure 12-18
Loading the Solaris 8 operating system 12-18
Installing the Cisco MGC Software 12-19
Restoring the System 12-19
APPENDIX
A
XECfgParm.dat File Parameters
12-17
A-1
Understanding the XECfgParm.dat File Format A-1
Cisco MGC XECfgParm.dat Files A-1
Facility Names A-1
Special Parameters A-2
Cisco MGC 9.x XECfgParm.dat File Parameter Definitions
APPENDIX
B
HP OpenView Sample SNMP Configuration
APPENDIX
C
D
Formatting Trap Messages
B-3
Sample LAN Configurations
C-1
A-2
B-1
Configuring the Cisco MGC to Send Alarms to HP OpenView
APPENDIX
B-1
Sample Configuration for Cisco Catalyst 5500 A C-1
Sample Configuration for Cisco Catalyst 5500 A RSM
C-7
Sample Configuration for Cisco Catalyst 5500 B C-8
Sample Configuration for Cisco Catalyst 5500 B RSM
C-15
Sample Installation Scripts
12-12
D-1
Sample Output from install.sh
D-1
Updated Configuration File Sample
D-10
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xi
Contents
Sample Configured snmpd.cnf File
APPENDIX
E
D-11
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
D-14
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
D-21
Sample Uninstall Scripts
E-1
Removing a Previous Software Version: Sample Output for uninstall.sh
E-1
INDEX
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xii
OL-1150-15
Preface
This preface describes the objectives and organization of this document and explains how to find
additional information on related products and services. It contains the following sections:
•
Document Objectives, page xiii
•
Document Conventions, page xiii
•
Document Conventions, page xiii
•
Documentation Map, page xvi
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page xvii
•
Document Change History, page xvii
Document Objectives
This guide describes the steps necessary to install and configure the Cisco Media Gateway Controller
(Cisco MGC) Software Release 9.1 to 9.6, the Sun Solaris operating system on the Cisco MGC host, and
the Solstice DiskSuite on the Netra t and Sun Fire platforms.
Note
This guide does not cover media gateway (MGW) or hardware installation. For instructions on installing
these components, see the Cisco Media Gateway Controller Hardware Installation Guide.
Audience
The audience of this document is network operators and administrators. This audience is assumed to
have experience in telecommunications networks, protocols, and equipment, and a familiarity with data
communications networks, protocols, and equipment.
This guide attempts to show all the commands needed to perform the installation and configuration of
the software. The installer is assumed to be familiar with UNIX, vi, or other text editors, and the
command line interface for Cisco switches and routers.
Document Conventions
This guide uses the conventions listed in Table 1 to represent text and table information.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xiii
Preface
Document Conventions
Table 1
Document Conventions
Convention
Meaning
Example and Comments
Boldface
Commands and
keywords you enter
literally as shown
offset-list
Italics
Variables for which you command type interface
supply values
You replace the variable with
the type of interface.
In contexts that do not allow
italics, such as online help,
arguments are enclosed in
angle brackets (< >).
Square brackets ([ ])
Optional elements
command [abc]
abc is optional (not required),
but you can choose it.
Vertical bars ( | )
Braces ({ })
Separated alternative
elements
command [ abc | def ]
Required choices
command { abc | def }
You can choose either abc or
def, or neither, but not both.
You must use either abc or
def, but not both.
Braces and vertical bars
within square brackets
([ { | } ])
A required choice
within an optional
element
command [ abc { def | ghi } ]
You have three options:
•
nothing
•
abc def
•
abc ghi
Caret character (^)
Control key
The key combinations ^D and
Ctrl-D are equivalent: Both
mean hold down the Control
key while you press the D key.
Keys are indicated in capital
letters, but are not case
sensitive.
A string
A nonquoted set of
characters
For example, when setting an
SNMP community string to
public, do not use quotation
marks around the string;
otherwise, the string will
include the quotation marks.
System prompts
Denotes interactive
sessions and indicates
that the user enters
commands at the
prompt
The system prompt indicates
the current command mode.
For example, the prompt
Router (config) # indicates
global configuration mode.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xiv
OL-1150-15
Preface
Document Conventions
Table 1
Document Conventions (continued)
Convention
Screen
font
Angle brackets (< >)
Exclamation point (!) at the
beginning of a line
Note
Timesaver
Tip
Caution
Meaning
Terminal sessions and
information the system
displays
Example and Comments
For example:
Save
Nonprinting characters
such as passwords
For example:
A comment line
Comments are sometimes
displayed by the Cisco IOS
software.
<password>
Means reader take note. Notes contain helpful suggestions or references to material not contained in this
manual.
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Means the following information might help you solve a problem. The Tips information might not be for
troubleshooting or even an action, but it could be useful information, similar to a Timesaver.
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xv
Preface
Documentation Map
Documentation Map
Start
Solution Overview
Is
MGC host
set up?
Yes
No
Is
gateway
set up?
Yes
No
Regulatory Compliance and Safety
Information for Cisco MGC
Regulatory Compliance and Safety
Information for Cisco Media Gateway
Cisco MGC Hardware
Installation Guide
Solution Gateway Hardware
Installation Guide
Release Notes for
Cisco MGC Software Release 9
Solution Gateway Software
Installation and Configuration Guide
Cisco MGC Software Release 9
Installation and Configuration Guide
Solution Gateway
Provisioning Guide
Cisco MGC Software Release 9
Provisioning Guide
End
Cisco MGC Software Release 9
Billing Interface Guide *
Cisco Voice Services Provisioning
Tool Version 2.x
Cisco MGC Software Release 9 Operations,
Maintenance, and Troubleshooting Guide
Cisco MGC Software Release 9 MML
Command Reference Guide *
Cisco MGC Software Release 9
Messages Reference Guide *
Cisco MGC Software Release 9
Management Information Base Guide *
* This guide provides useful information
that is not required during installation.
57047
Cisco MGC Software Release 9
Dial Plan Guide
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xvi
OL-1150-15
Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
Related Documentation
Other useful reference publications include:
Note
•
Overviews of the related telephony solutions—Describe the Cisco Integrated Network Solutions
with which the Cisco MGC node is associated.
•
Provisioning guides for the related telephony solutions—Describe the provisioning steps for the
Cisco Integrated Network Solutions with which the Cisco MGC node is associated
•
Solution gateway installation and configuration guides—Describe how to install and configure the
media gateway (MGW) for a particular Cisco Integrated Network Solution.
•
Release Notes for the Cisco Media Gateway Controller Software Release 9—Describes the features
and caveats in the latest version of the Cisco MGC software release.
•
Cisco Signaling Link Terminal—Describes the Cisco Signaling Link Terminal (Cisco SLT) and
provides configuration information.
Documentation for the Cisco Integrated Network Solutions are located at
http://www.cisco.com/univercd/cc/td/doc/solution/index.htm.
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's
New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Document Change History
Subject
Document #, Change Date
Change Summary
Appendix C: XECfgParm.dat
Parameters
OL-1150-15, March 17, 2006
•
Added descriptions for the
*.AllISDNLinksFailCausesFailover and
*.AllLinksFailCausesFailover parameters.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-15, March 17, 2006
•
Add a note about having to copy the
snmpd.cnf.tmpl to the snmp.cnf file before
running the config-snmp utility for new
installations of Release 9.6(1)
Chapter 1: Preparing for Sun
Solaris 8 Operating System and
Cisco MGC Software Installation
OL-1150-14, February 17, 2006
•
Added changes related to the introduction of the
Sun Sun Fire V210 as platforms for the Cisco
MGC software.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xvii
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Chapter 2: Sun Solaris 8 Operating OL-1150-14, February 17, 2006
System Installation
•
Added changes related to the introduction of the
Sun Sun Fire V210 as platforms for the Cisco
MGC software.
Chapter 3: Cisco MGC Software
Release 9 Installation
•
Added changes related to the introduction of the
Sun Sun Fire V210 and as platforms for the Cisco
MGC software.
Chapter 2: Sun Solaris 8 Operating OL-1150-14, December 29, 2005
System Installation
•
Corrected response information for Step 2 of the
Rebooting from Mirrored (Secondary) Disk
procedure.
Chapter 6: Upgrading the Cisco
MGC Software
•
Added Caution against adding provisioning data
to your system during the upgrade process.
•
Added information on stopping and restarting
database replication when upgrading to Release
9.6(x).
•
Added Caution about using config-lib tool to
copy old XECfgParm.dat data to make new
production version of the file.
•
Modified instructions to make a copy of the
snmpd.cnf file to indicate that this step is only
necessary for upgrades from Release 7.4(x)
OL-1150-14, February 17, 2005
OL-1150-14, December 29, 2005
Appendix C: XECfgParm.dat File
Parameters
OL-1150-14, December 29, 2005
•
Corrected information for the
engine.ShortDurationCallPeriod parameter.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-14, August 4, 2005
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
•
Added information to expand on the information
on database replication.
•
Corrected links for the Check for Mated STP
Pairs section.
•
Updated upgrade procedures for the new version
of the TimesTen database used in Release 9.6(x).
•
Added text to verify whether there is a 32-bit
kernel running on the existing host prior to
upgrade.
Chapter 6: Upgrading the Cisco
MGC Software
OL-1150-14, August 4, 2005
Appendix B: Migrating to Solaris 8 OL-1150-14, August 4, 2005
and Cisco MGC 9.2(2)
Appendix C: XECfgParm.dat File
Parameters
OL-1150-14, August 4, 2005
Added definitions for these parameters new for
Release 9.6(1):
•
*.maxLocationLabels
•
engine.CallLimitingControl.
Added definitions for several parameters added in
previously releases that were missing.
Chapter 3: Cisco MGC Software
Release 9 Installation
OL-1150-13, May 16, 2005
Modified the procedure to install the CSCOh013
package.
Added a step to modify the XECfgParm.dat
parameter diskmonitor.CoreRmDays.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xviii
OL-1150-15
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Chapter 4: Cisco PGW 2200
Security Enhancements
OL-1150-13, May 16, 2005
Modified the procedure to install the CSCOx9000
package.
Appendix C: XECfgParm.dat File
Parameters
OL-1150-13, May 16, 2005
Corrected the definitions for the XECfgParm.dat
parameters DefaultLocation and ClearingLocation.
Corrected the definitions for the XECfgParm.dat
parameters diskmonitor.CdrRmFinished and
diskmonitor.OptFileSys.
Added a definition for the XECfgParm.dat parameter
diskmonitor.CoreRmDays.
Chapter 2: Sun Solaris 8 Operating OL-1150-13, March 25, 2005
System Installation
Chapter 3: Cisco MGC Software
Release 9 Installation
OL-1150-13, March 25, 2005
•
Corrected values in a partition table.
•
Clarified information on command parameters
for adding a second Ethernet interface.
•
Added a caution statement about the
configuration of the Solaris environment and the
use of the Cisco VSPT and the Cisco MGC
softwareon the same server.
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
•
Corrected errors in the procedure to install
CSCOh013.
•
Corrected errors in the procedure to install
CSCOh014.
Chapter 4: Cisco PGW 2200
Security Enhancements
OL-1150-13, March 25, 2005
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-13, March 25, 2005
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
Appendix B: Migrating to Solaris 8 OL-1150-13, March 25, 2005
and Cisco MGC 9.2(2)
•
Added notes detailing the messages related to
Solaris Disk Suite startup that would occur when
a system is rebooted.
Chapter 2: Sun Solaris 8 Operating OL-1150-13, January 31, 2005
System Installation
•
Corrected values in a partition table.
Chapter 4: Cisco PGW 2200
Security Enhancements
OL-1150-13, January 31, 2005
•
Modified the Fallback procedure for the
Cisco MGC software.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-13, January 31, 2005
•
Added information on the new engine parameter,
engine.SendHardwareBlock.
Chapter 6: Upgrading the Cisco
MGC Software
OL-1150-13, January 31, 2005
•
Added notes on changes to the snmpd.cnf file
triggered by the upgrade process.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xix
Preface
Document Change History
Subject
Document #, Change Date
Appendix C:XECfgParm.dat
Parameters
OL-1150-13, January 31, 2005
Change Summary
•
Added information on the new engine parameter,
engine.SendHardwareBlock.
Chapter 2: Sun Solaris 8 Operating OL-1150-13, November 22,
System Installation
2004
•
Indicated that the procedures for installing a
BAMS disk array are used when the BAMS host
is a Netra t 1400/1405.
Chapter 5: Configuring the Cisco
MGC Software
•
Corrected value in Table 5-9 for the
*.sm_meas_baseaddr parameter.
•
Updated various parameter values related to the
changes in engine.SysVirtualSwitch for Release
9.4(1) and up.
•
Updated procedures for installing/uninstalling
log and spool functions.
•
Corrected information regarding installation of
BAMS disk array hardware and software.
•
Corrected value for the *.sm_meas_baseaddr
parameter.
•
Corrected value in for the
procM.minCheckHealthTimeout parameter.
•
Updated various parameter values related to the
changes in engine.SysVirtualSwitch for Release
9.4(1) and up.
OL-1150-13, September 27,
2004
•
Updated information in Table 5-9 pertaining to
the addition of call detail block (CDB) 1071 to
engine.CDRmessageTypes.
Appendix A, “XECfgParm.dat File OL-1150-13, September 27,
Parameters”
2004
•
Updated information in Table C-9 pertaining to
the addition of call detail block (CDB) 1071 to
engine.CDRmessageTypes.
Preface
OL-1150-13, September 23,
2004
•
Updated information in this section.
Chapter 2, “Sun Solaris 8
Operating System Installation”
OL-1150-13, September 17,
2004
•
Updated information in Table 2-2 pertaining to
the Ethernet and disk drive devices for each
platform type.
Chapter 2, “Sun Solaris 8
Operating System Installation”
OL-1150-13, September 17,
2004
•
Updated the section Configuring a Second Disk
Drive to include cautionary note and procedure
to ensure compatibility between the CSCOh016
and CSCOh015 software packages if CSCOh015
was previously installed.
Chapter 2, “Sun Solaris 8
Operating System Installation”
OL-1150-13, September 17,
2004
•
Updated the section Installing the Alarm
Software to include information that the alarm
software is installed automatically on a Netra
240 or Netra 440 platform—the ALOM
(Advance Lights Out Management) software for
Netra 240 or Netra 440 is integrated within the
Solaris 8 OS, Revision 2/04.
OL-1150-13, November 22,
2004
Chapter 8: Sun Solaris 8 Operating OL-1150-13, November 22,
Software Installation
2004
Appendix A, “XECfgParm.dat File OL-1150-13, November 22,
Parameters”
2004
Chapter 5: Configuring the Cisco
MGC Software
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xx
OL-1150-15
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Chapter 1, “Preparing for Sun
OL-1150-13, August 27, 2004
Solaris Operating System and
Cisco MGC Software Installation”
•
Updated this section to include information for
Sun Netra 240 and 440 and support for Solaris 8
OS, Revision 2/04.
Chapter 2, “Sun Solaris 8
Operating System Installation”
•
Updated partition tables for 73 GB Disks in
Chapter 2 to reflect support for BAMS and HSI.
•
Updated Table 2-2, Device Names on Supported
Platforms, to include information on the Sun
Quad GigaSwift Ethernet interface PCI adaptor
card.
OL-1150-13, August 27, 2004
Sun Solaris 8 Operating System
Installation
OL-1150-13, August 27, 2004
•
Updated this section to include information for
Sun Netra 240 and 440.
Cisco MGC Software Release 9
Installation
OL-1150-13, August 27, 2004
•
Updated this section to include information for
Sun Netra 240 and 440.
Upgrading the Cisco MGC
Software
OL-1150-13, June 14, 2004
•
Revised the chapter to make the upgrade
procedures applicable to all versions of Cisco
MGC 7.4(x) and 9.x.
•
Information added to “Before You Begin”
section regarding upgrading from Cisco MGC
7.4(x) if screening is being used.
•
Note added regarding TimesTen Database not
allowing the installation of a new schema.
Cisco MGC Software Release 9
Installation
OL-1150-13, June 14, 2004
•
Removed obsolete protocols from the document.
Chapter 2, “Sun Solaris 8
Operating System Installation”
OL-1150-13, June 14, 2004
•
Added an optional step 2 to the section on
“Booting from a Local CD-ROM.”
•
Updated DiskSuite section with a note on the
order of installing CSCOh016.
•
Added description of new parameter:
SipToIsupInterworkingInd.
•
Added new parameter to turn Lawful Intercept
on and off.
Appendix A, “XECfgParm.dat File OL-1150-13, June 14, 2004
Parameters”
Chapter 2, “Sun Solaris 8
Operating System Installation”
OL-1150-13, Jan. 18, 2004
•
Updated “Loading the Solaris 8 Operating
System” section on page 4 to clarify support of
QFE cards for BAMS platforms only and support
of CE NIC cards (GigE) in Cisco MGC software
9.3(2) and later releases.
Chapter 4, “Cisco PGW 2200
Security Enhancements”
OL-1150-13, Jan, 5, 2004
•
Updated “Fallback Procedures” section on
page 29.
Appendix C: XECfgParm.dat File
Parameters
OL-1150-13, Oct. 2, 2003
•
Updated the descriptions of the following
parameters:
– engine.CDRmessageTypes
– engine.CDRtimeStamp
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xxi
Preface
Document Change History
Subject
Document #, Change Date
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-13, Oct. 2, 2003
Change Summary
•
Configuring Call Detail Record File Output
section: Updated the descriptions of the
following parameters:
– engine.CDRmessageTypes
– engine.CDRtimeStamp
Chapter 2: Sun Solaris 8 Operating OL-1150-13, Oct. 2, 2003
System Installation
•
Verifying Network Time Protocol (NTP)
Packages section: Added a step to enable slewing
to synchronize the local clock with the NTP
server reference time.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-13, Sept. 9, 2003
•
Configuring SNMP Support Resources section:
Added procedures for migrating the SNMP
configuration to a more secure environment by
running the config-snmp utility.
Chapter 5: Configuring the Cisco
MGC Software
OL-1150-13, Sept. 9, 2003
•
Using the Cisco MGC Environment
Configuration Tool: Updated the MGC
Environment Configuration Tool screen.
Chapter 6: Upgrading the Cisco
MGC Software
OL-1150-13, Sept. 9, 2003
•
Backing Up the Configuration Data section:
Added steps for removing a ^M character (in
files edited in DOS mode) before starting the
upgrade from Cisco MGC 7.4(x).
•
Added information on BAMS: If the
configuration being upgraded to Cisco MGC
9.4(1) includes BAMS, the changes noted in the
section “Configuring the Cisco MGC for Using
BAMS” of the BAMS User’s Guide must first be
re-applied.first re-apply
•
Added new chapter describing the installation of
the CSCOk9000 security package.
Chapter 2: Sun Solaris 8 Operating OL-1150-13, April 30, 2003
System Installation
•
Updated the section Rebooting from the
Mirrored (Secondary) Disk with new procedures.
Chapter 2: Sun Solaris 8 Operating OL-1150-13, April 17, 2003
System Installation
•
Updated the Disk Partitioning Tables with HSI
disk partitioning information.
Chapter 6: Upgrading the Cisco
MGC Software
OL-1150-13, April 17, 2003
•
Added information on how to upgrade
successfully from Cisco MGC 9.2(2) to 9.3(2) if
sipURL containing more than 30 characters or
Carrier Table is configured in the system.
Appendix D: HP OpenView
Sample SNMP Configuration
OL-1150-13, April 17, 2003
•
In Formatting Trap Messages, Step 2,the user is
instructed to select TransPath under Enterprise
Name.
•
Updated the Disk Partitioning Tables with HSI
disk partitioning information.
•
Note added: Sun Netra 20 requires Solaris 8 Rev.
2/02.
Chapter 4: Cisco PGW2200
Security Enhancements
OL-1150-13, Sept. 9, 2003
Chapter 2: Sun Solaris 8 Operating OL-1150-13, Feb. 28, 2003
System Installation
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xxii
OL-1150-15
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Chapter 3: Cisco MGC Software
Releases 9.2(x) and 9.3(x)
Installation
OL-1150-13, Feb. 28, 2003
Clarified instructions for installing CSCOh013
security package on a fault tolerant (duplex) system.
Chapter 4: Configuring the Cisco
MGC Software
OL-1150-13, Feb. 28, 2003
•
Updated: Table 4-5 (*.stPort entry) to match
description in Appendix C, XECfgParm.dat File
Parameters.
•
Updated: Added information that database
replication can only be stopped by mgcusr and
not root.
Chapter 5: Upgrading to Cisco
MGC Software Release 9.3(2)
OL-1150-13, Feb. 28, 2003
Added information: Before migrating from Cisco
MGC 9.2(2) to 9.3(2), the directory /opt/SW/ must be
backed up. The .pkg files must be removed from the
/opt/SW/ directory before migrating to 9.3(2).
Chapter 4: Configuring the Cisco
MGC Software
OL-1150-13, Jan. 21, 2003
Updated the section Initializing Database
Replication: added step 3, to log back in to the
standby host as mgcusr.
Chapter 4: Configuring the Cisco
MGC Software
OL-1150-13, Jan. 21, 2003
Added information to the section Initializing the Call
Screening Database cautioning against using
TimesTen commands directly.
Appendix C: XECfgParm.dat File
Parameters
OL-1150-13, Jan. 21, 2003
Removed the note stating that the value for the
*.disableMeas parameter should not be changed.
Chapter 5: Migrating to Cisco
MGC software release 9.3(2)
OL-1150-13, Jan. 14, 2003
Procedures were updated.
Chapter 5: Migrating to Cisco
MGC software release 9.3(2)
OL-1150-12, Dec. 9, 2002
New chapter added detailing procedures for
upgrading major Cisco MGC software releases
without service interruption, such as 7.4(x), 9.1(5),
9.2(2), and 9.3(1)T, to software release 9.3(2).
Chapter 5: Migrating to Cisco
MGC software release 9.3(2)
OL-1150-12, Dec. 9, 2002
Procedures added for migrating the dial plan from
Cisco MGC software release 7.4(x) to 9.3(2).
Appendix A: Migrating to Cisco
MGC 9.3(2)
OL-1150-12, Dec. 9, 2002
Moved chapter on Migrating to Cisco MGC 9.3(1)
from Chapter 5 to Appendix A.
Appendix C: XECfgParm.dat
OL-1150-12, Dec. 9, 2002
Added new information and updates for the following
XECfgParm.dat parameters:
•
engine.StartUpAuditEnabled
•
set-log
Chapter 2: Sun Solaris 8 Operating OL-1150-12, Dec. 9, 2002
System Installation
Added description for DiskSuite installation using a
script.
Sun Netra 20 (AC & DC) platform OL-1150-11, Nov. 6, 2002
information
New information added regarding Sun Netra 20, Sun
Netra 1400 (DC) and 1405 (AC). Product information
in Table 1-1 (Cisco MGC Host Configurations) was
updated.
Reduced Configuration Sun Netra
1400 (DC) and 1405 (AC)
Chapter 5: Migrating to Cisco
MGC 9.3(1)
OL-1150-10, Sept. 23, 2002
Added new chapter detailing procedures for
migrating to Cisco MGC software release 9.3(1).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xxiii
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Appendix B: XECfgParm.dat
OL-1150-10, Sept. 23, 2002
In Table 4-1: Provided descriptions/values for the
following parameters:
•
engine.RelINAPCallsAfterSwOver
•
engine.CircuitReservation
•
*.GWClearChannelAlgorithm
Appendix B: XECfgParm.dat
OL-1150-09, Aug. 30, 2002
In Table B-1: Replaced *.OverdecadicDigitsEnabled
with *.OverdecadicDigitsSupported.
Appendix B: XECfgParm.dat
OL-1150-08, July 15, 2002
In Table B-1: Added description for
*.maxNumRLMPorts.
Chapter 2: BAMS Disk
Partitioning
OL-1150-07, June 21, 2002
Corrected Table 2-1 (column for BAMS without Disk
Array) to indicate that the /usr partition is 1000 MB.
Chapter 5: Updates to migration
OL-1150-06, June 17, 2002
procedures; note regarding the Sun
Quad Fast Ethernet card (qfe)
Updated Chapter 5, added note regarding the support
of QFE card for BAMS.
Solaris 8 and 2.6 operating system OL-1150-05, June 2002
36GB disk drive support, NTP
configuration, return codes during
Solaris 8 patch installation
Added information for 36GB disk drive, NTP
configuration, explanation of return codes during
Solaris 8 patch installation.
Migration procedures
OL-1150-04, April 2002
Procedures were updated.
Document reorganization
OL-1150-03, March 2002
Document reorganized to contain separate chapters
for Solaris 8, Solaris 6, Cisco MGC Release 9.2(2)
and 9.1(5).
Solaris 8 operating system
installation
OL-1150-03, March 2002
Information updated.
Verification Test Suite Package
(CSCOh014)
OL-1150-03, March 2002
Information added.
Solaris 8 operating system
installation
OL-1150-03, February 2002
Information added.
Cisco MGC software and Solaris 8 OL-1150-03, February 2002
Migration/Upgrade Procedures
Information added.
Cisco Security Package
CSCOh013)
OL-1150-03, February 2002
Information added.
MGC software
installation/uninstallation
sequence
OL-1150-03, February, 2002
Installation and uninstallation sequence information
added.
XECfgParm.dat parameter:
CDBOutputSel
OL-1150-03, Dec. 31, 2001
Appendix B: Deleted description of the
CDBOutputSel parameter (no longer used).
XECfgParm.dat parameter:
SyscreeningCheck
OL-1150-03, Oct. 5, 2001
Note added stating that setting this parameter to true
will impact system performance because it will
reduce MAX CPS and the maximum number of
sustained calls.
Rel. 7.3 XECfgParm.dat
parameters
OL-1150-03, Oct. 5, 2001
Deleted all references to Rel. 7.3 XECfgParm.dat
parameters.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xxiv
OL-1150-15
Preface
Document Change History
Subject
Document #, Change Date
Change Summary
Upgrading the Cisco MGC to
Release 7.4
OL-1150-03, Sept. 24, 2001
Upgrading within Rel. 7.4: procedures corrected.
Chapter 2: Installing Release 7.3
OL-1150-03, Sept. 24, 2001
Deleted Release 7.3 information.
Configuring SNMP resources
OL-1150-03, August 3, 2001
Additional procedures added to verify that the
services file lists the default SNMP ports (Chapter 4).
Installing the Cisco Security
Package
OL-1150-03, August 3, 2001
Installation procedures added to Chapter 1.
NewXeCfgParm.dat parameter
OL-1150-03, August 3, 2001
Added *.RedirectingATree parameter information to
Appendix B.
Fallback Procedures
OL-1150-03, July 11, 2001
Added fallback procedures (Chapter 4).
Duplex mismatch between the
switch and the SC NIC.
OL-1150-03, July 11, 2001
Added cautionary note to ensure that users correctly
configure the duplex on the catalyst port (Chapter 5).
Time mismatch on VSC pair.
OL-1150-03, July 11, 2001
Added note to ensure that the correct NTP packages
are installed. NTP synchronizes call detail record
(CDR) timestamps on SC2200s and BAMS.
XECfgParm.dat file parameters
OL-1150-02, June 19, 2001
Added XECfgParms.dat parameters to Appendix B.
XECfgParm.dat file: configured
file example
OL-1150-02, June 19, 2001
XECfgParm.dat file: example of updated configured
file added to replace old file.
XECfgParm.dat file parameters
OL-1150-02, June 19, 2001
Added parameter descriptions to Chapter 4.
Automatic Congestion Control
(ACC)
OL-1150-02, June 19, 2001
Added ACC configuration information (Chapter 4).
Call Detail Record File (CDR)
OL-1150-02, June 19, 2001
Added CDR file output configuration information
(Chapter 4).
*.GWClearChannelAlgorithm
parameter
OL-1150-02, June 19, 2001
Added *.GWClearChannelAlgorithm parameter
information (Chapter 4).
Configuring SCP queries;
trigger.dat file
OL-1150-02, June 19, 2001
Added information on Cisco MGC trigger.dat file
attributes to perform Transaction Capabilities
Application Part (TCAP) queries.
Sample installation scripts
OL-1150-02, June 19, 2001
Reorganized this document and moved sample
installation scripts to Appendix C.
Sample Cisco Media Gateway
Controller configuration files
OL-1150-02, June 19, 2001
Reorganized this document and moved sample Cisco
MGC configuration scripts to Appendix D.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
xxv
Preface
Document Change History
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
xxvi
OL-1150-15
CH A P T E R
1
Preparing for Sun Solaris Operating System and
Cisco MGC Software Installation
This chapter provides checklists describing the required and optional components, software media,
tasks, and information you must have on hand before installing the Cisco MGC software and the Sun
Solaris operating system:
•
Cisco MGC Software Release 9.2(x) or higher, which requires the Sun Solaris Operating System 8
Or:
•
Cisco MGC Software Release 9.1(5), which requires the Sun Solaris Operating System 2.6
Note
The Cisco PGW 2200 PSTN Gateway (hereafter referred to as Cisco PGW 2200) is the new name for
the Cisco VSC 3000 and the Cisco SC 2200. Some parts of this document may use these older names.
Note
The entire installation procedure takes approximately 2 hours to complete.
Supported Platforms and Cisco Products
Software Release 9.2(x) or Higher
The following platforms are supported in the Cisco MGC 9.2(x) or higher software releases:
•
Netra 240
•
Netra 440
•
Sun Fire V120
•
Sun Fire V210
•
Netra 120
•
Netra 20
•
Netra t 1120/1125
•
Netra t 1400/1405
•
Netra t 100/105
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
1-1
Chapter 1 Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 8, Cisco MGC 9.2(x) and Higher Software Release Pre-Installation Checklists
The following Cisco products are supported in this release:
•
Cisco PGW 2200 (PSTN Gateway)
•
Cisco Billing and Measurements Server (BAMS)
•
Cisco H.323 Signaling Interface (HSI)
Software Release 9.1(5)
The following platforms are supported in the Cisco MGC software release 9.1(5):
•
Netra t 100/105
•
Netra t 1120/1125
•
Netra t 1400/1405
Solaris 8, Cisco MGC 9.2(x) and Higher Software Release
Pre-Installation Checklists
The following tables list the required and optional tasks, information, software media for installing the
Solaris 8 operating system and the Cisco MGC software.
Before installing the Sun Solaris operating system, Solaris patches and alarm card software, make sure
the information and tasks listed in the following tables are collected and completed. These tables list the
requirements for installing the Solaris 8 operating system and the Cisco MGC software.
Note
The target machine must have a terminal connected to the console port by means of a serial cable.
Required Software Media
Gather all the appropriate software media listed in Table 1-1. For more information, refer to the
appropriate Sun documentation that shipped with your system.
Table 1-1
Solaris 8 Required Media Checklist
Media
Version
The following CD-ROM disks are ordered from Sun:
•
Note
Solaris 8 Software CD, Disk 1 of 2
Release 2/04 (or Release 2/02
or 10/01)
The Netra 20 requires Solaris 8 Software Release 2/02 or
later.
The Sun Fire V210 and the Netra 240 and 440 require Solaris
8 Software Release 2/04 or later.
•
Solaris 8 Software CD, Disk 2 of 2,
Release 2/04 (or Release 2/02
or 10/01)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
1-2
OL-1150-15
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 8, Cisco MGC 9.2(x) and Higher Software Release Pre-Installation Checklists
Table 1-1
Solaris 8 Required Media Checklist (continued)
Media
•
Version
Software Supplement for Solaris 8 Operating Environment CD
Release 2/04 (or Release 2/02
or 10/01)
The Solaris 8 Environment Patches for Cisco PGW, which is included in your installation packet
(Media & Install Doc Kit), contains the following:
•
CSCOh016 (DiskSuite installation scripts)
•
CSCOh015 (Solaris 8 patch cluster package)
•
CSCOh013 (Security patch)
•
CSCOh005 (Log/Spool package)
•
CSCOh014 (Verification Test Suite package)
Minimum System Requirements
For minimum system requirements, refer to the Cisco Media Gateway Controller Hardware Installation
Guide for the host minimum hardware requirements. Before using the minimum hardware configuration,
consult your Cisco representative to determine the hardware that will provide you the best performance
results based on your network configuration, proposed traffic, and desired processing power.
Required Site-specific Information
Your system site administrator can provide the required site-specific information listed in Table 1-2. Use
the Notes column in this table to record the information. Several steps in the installation procedure in
Chapter 2, “Sun Solaris 8 Operating System Installation”, will require you to provide this information,
and references to your notes this table will be made.
Table 1-2
Site-specific Information
Required Information
Notes
Netmask
(Example: 123.123.123.0)
Default Router
(Example: 111.11.xxx.1)
NTP server IP address
Time Zone
(Example: United States (Eastern))
Root Password
(Assigned by your system site
administrator)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
1-3
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Required Machine-specific Information
Your system site administrator can provide the following information specific to your target Sun Netra
machine listed in Table 1-3. Use the Notes column in this table to record the information. Several steps
in the installation procedure in Chapter 2, “Sun Solaris 8 Operating System Installation”, will require
you to provide this information, and references to your notes in this table will be made.
Table 1-3
Required Information Checklist
Information
Notes
Host name of target machine
IP address of target machine
Default router IP address
Additional Ethernet IP address
Subnet address of each additional Ethernet IP address
Netmask address of each additional Ethernet IP address
Required Tasks
Before you begin installing the Solaris 8 Operating system, perform the tasks listed in Table 1-4.
Table 1-4
Required Tasks Checklist
Tasks
Make sure that the target machine is connected to a terminal by a serial cable inserted into the
console port.
Have your company's internal support and Cisco support contact information readily available
so you can get help with the installation if needed. If you have questions or need assistance,
see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on
page xvii.
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
The following tables list the required and optional tasks, information, software media for installing the
Solaris 2.6 operating system and the Cisco MGC Software Release 9.1(5).
Before installing the Sun Solaris 2.6 operating system, Solaris patches, alarm software, and Veritas
Volume Manager software, make sure the information and tasks listed in the following tables are
collected and completed. These tables list the requirements for installing the Solaris 2.6 operating
system and the Cisco MGC Software Release 9.1(5).
Required Software Media
Gather all the appropriate software media listed in Table 1-1. For more information, refer to the
appropriate Sun documentation that shipped with your system.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
1-4
OL-1150-15
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Table 1-5
Solaris 2.6 Required Media Checklist
Media
Version
Part Number
Operating Environment Installation CD
September 1999
704-6914-10
Cisco MGC Installation CD
One of the following Solaris Software CDs:
704-6220-10
•
Solaris 2.6 software
704-6220-10
•
Solaris 2.5.1 software
704-5949-10
•
Sun StorEdge Volume Manager
2.6
704-6316-10
Netra t alarm card software (for Netra t 112x)
—
704-6330-10
Cisco PGW Solaris 2.6 Patch containing the following:
—
80-5965-01
•
CSCOh007.pkg (Solaris 2.6 patch software)
•
CSCOh013 (Security patch)
•
CSCOh005.pkg (Log/Spool package)
•
CSCOh006 (Veritas Installation)
•
CSCOh012 (Hardware test package)
Required Site-specific Information
Your system site administrator can provide the required site-specific information listed in Table 1-2. Use
the Notes column in this table to record the information. Several steps in the installation procedure will
require you to provide this information, at which time references to this table will be made.
Table 1-6
Site-specific Information
Required Information
Notes
Netmask
(Example: 123.123.123.0)
Default Router
(Example: 111.xx.xxx.x)
Time Zone
(Example: United States (Eastern))
Root Password
(Assigned by the lab administrator)
Sun StorEdge Volume Manager
Installation Software Key
(Obtained from Sun Microsystems
using the request form that is ordered
with the target machine. A temporary
key can be provided by the Sun service
representative.)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
1-5
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Required Machine-specific Information
Your system site administrator can provide the following information specific to your target Sun Netra
machine listed in Table 1-3. Use the Notes column in this table to record the information. Several steps
in the installation procedure in Chapter 8, “Sun Solaris 2.6 Operating System Installation”, will require
you to provide this information, at which time references to this table will be made.
Table 1-7
Required Information Checklist
Information
Notes
Host name of target machine
IP address of target machine
Default router IP address
Second Ethernet IP address
Required Tasks
Before you begin installing the Sun Operating system, you must perform the tasks listed in Table 1-8.
Table 1-8
Required Tasks Checklist
Tasks
Make sure that the target machine is connected to a terminal by a serial cable inserted into the
console port.
If you do not have the Veritas Volume Manager license key, contact your Cisco or Sun
Microsystems service representative to get a temporary 45-day key. Follow the instructions
on the software license key request form to obtain a Volume Manager license key.
Make sure that you have the latest Solaris software packages—check CCO
(http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml) to ensure that you have the latest
required patch version released by Cisco on your system, CD, or file system (if downloaded
previously from CCO).
Have your company's internal support and Cisco support contact information readily available
so you can get help with the installation if needed. If you have questions or need assistance,
see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on
page xvii.
Optional Components for Solaris 2.6 Installation
Obtain the optional components listed in Table 1-9, depending upon the system options you are
installing.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
1-6
OL-1150-15
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Table 1-9
Optional Media Checklist
Media
Version
Sun StorEdge Volume Manager (referred to as
Veritas Volume Manager in this guide)
3.1
Sun StorEdge Volume Manager
2.6
Part Number
704-6316-10
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
1-7
Chapter 1
Preparing for Sun Solaris Operating System and Cisco MGC Software Installation
Solaris 2.6 and Cisco MGC 9.1(5) Pre-Installation Checklists
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
1-8
OL-1150-15
CH A P T E R
2
Sun Solaris 8 Operating System Installation
This chapter provides instructions for installing the Sun Solaris 8 operating system and Solstice
DiskSuite on the Netra and Sun Fire platforms.
Overview
The following sections in this chapter describe the installation of software on the hardware platform for
your solution.
There are points in the procedures when your responses to prompts will depend on the disk drive size or
other particulars of your system. These are pointed out as you follow the procedures.
Table 2-1
Guide to this Chapter
Section
Page
Supported Platforms
2
Supported Disk Drives
2
Before You Start
3
– Cautions, Notes, and Tips
3
Loading the Solaris 8 Operating System
4
– Devices on Supported Platforms
4
– Booting from a Local CD-ROM
4
– Installing the Solaris 8 Operating System
15
– Verifying Network Time Protocol (NTP) Packages
31
Configuring a Second Disk Drive
32
– Installing the Solstice DiskSuite (CSCOh016)
32
– Rebooting from the Mirrored (Secondary) Disk
34
– Removing the Solstice DiskSuite
36
Installing the Log and Spool File Systems (CSCOh005)
– Uninstalling the Log and Spool File System
37
43
Configuring Additional Ethernet Interfaces
45
Installing the Alarm Software
46
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-1
Chapter 2
Sun Solaris 8 Operating System Installation
Supported Platforms
Table 2-1
Guide to this Chapter
Section
– Installing Lights Out Management Software
47
– Alarm Card Software Installation for Netra t 1120/1125
50
Installing the Solaris 8 Patch Cluster (CSCOh015)
51
Installing the BAMS Disk Array on a Netra t 140x Host
54
– Installing the RAID Manager Software
55
– Configuring the RAID Module
55
Troubleshooting
Note
Page
57
– Netra t 10x
57
– Swap File Size Input
57
For procedures on migrating to Solaris 8 and Cisco MGC 9.2(2) software, refer to Appendix 12,
“Migrating to Solaris 8 and Cisco MGC 9.2 and Up.”
Supported Platforms
This document describes the specific steps necessary to install the Solaris 8 Operating System software
and Solstice DiskSuite on the Netra t and Sun Fire platforms. The following platforms are supported:
•
Netra 240
•
Netra 440
•
Sun Fire V120
•
Sun Fire V210
•
Netra 120
•
Netra t1 100/105
•
Netra t 1120/1125
•
Netra t 1400/1405
•
Netra 20
Supported Disk Drives
The following disk drives are supported:
•
18 GB
•
36 GB
•
73 GB
•
146 GB
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-2
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Before You Start
Before You Start
Be sure to read the following cautions, notes, and tips before installing the Solaris 8 operating system.
Cautions, Notes, and Tips
Caution
During the installation of the software package on the Netra t 112X machines, leave the
front panel open to prevent damage to the CD or machine because the CD-ROM drive will
automatically eject the CD.
Note
The Cisco PGW 2200 PSTN Gateway (hereafter referred to as Cisco PGW 2200) is the new name for
the Cisco VSC 3000 and Cisco SC 2200. Some parts of this document may use these older names.
Note
The procedures in this chapter require a working knowledge of the system administration procedures for
the Sun Solaris (UNIX) operating system.
Note
Be sure to have the required information listed in Chapter 1, “Preparing for Sun Solaris Operating
System and Cisco MGC Software Installation,” before you begin the installation process.
Note
The Sun Netra 20 requires Solaris 8 Software Release 2/02 or later.
The Sun Netra 220 and 440 require Solaris 8 Software Release 2/04 or later.
Note
Allow at least two hours down time for the installation of the Sun Solaris 8 operating
system.
Note
The text in the screens displayed throughout this document may differ slightly from the text displayed
on your console. The screen displays are for reference only and should be treated as examples.
Note
Most of the steps in the installation process ask you to press F2 to continue. However, F2 does not apply
to all console types. In this case, you should press Esc+2 instead.
Tip
During the installation process, monitor system output frequently for error messages and
correct any error conditions before continuing with the installation.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-3
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Note
In order to use Cisco Voice Services Provisioning Tool (Cisco VSPT) to provision MGC, you need to
install SUNWtftp package for Solaris 8 after you install the Solaris 8 operating system. You can
download that package from the Sun website.
Loading the Solaris 8 Operating System
This section provides instructions for loading the Solaris 8 operating system.
Devices on Supported Platforms
The following table shows the Ethernet and disk drive device names for each platform type. This table
is referenced throughout this chapter.
Table 2-2
Device Names on Supported Cisco MGC Software Platforms
Ethernet Interfaces
Platform Type
First
Second
Disk Drives
Third
Fourth
First
Second
Third
Fourth
Netra t 100/105
hme0
hme1 or
qfe01
n/a
n/a
c0t0d0
c0t0d1
n/a
n/a
Netra t
1120/1125
hme0
hme1
n/a
n/a
c0t0d0
c0t0d1
n/a
n/a
Netra t
1400/1405
hme0
hme1 or ce02 n/a
n/a
c0t0d0
c0t0d1
n/a
n/a
Sun Fire V120 /
Netra 120
eri0
eri1 or qfe01 qfe11 or ce11
or ce01
qfe21 or ce21 c1t0d0
c1t1d0
n/a
n/a
Sun Fire V210 /
bge03
bge13
bge21
bge31
c1t0d0
c1t1d0
n/a
n/a
n/a
n/a
c1t0d0
c1t1d0
n/a
n/a
bge24
bge34
c1t0d0
c1t1d0
n/a
Netra 20
eri0
hme0 or ce0
Netra 240
bge03
bge13
Netra 440
ce0
3
ce1
3
2
n/a
n/a
c1t0d0
c1t1d0
c1t2d0
n/a
4
c1t3d04
1. These interfaces are supported only on platforms hosting the BAMS application. Support for the "bge" and “ce” interfaces requires Solaris Environment
Patches 2.0(11) or later, and BAMS 3.13 Patch 13 or later.
2. Support for these “ce” interfaces requires Solaris Environment Patches 2.0(8) or later, and MGC 9.4(1) with the latest patches.
3. Support for these “bge” and “ce” interfaces require Solaris Environment Patches 2.0(11) or later, and Cisco MGC 9.4(1) patch CSCOgs028 or later.
4. This device is not used currently.
Booting from a Local CD-ROM
The instructions and sample screen shots in this section were written to correspond with the Solaris
10/01 installation disk(s). Other Solaris installations are similar, with slight variations. These
instructions will note the differences between the sets of installation instructions.
Step 1
Connect to the target system through a console.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-4
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 2
This step is optional—if you decide to skip this, go to Step 3.
a.
Place the system in single-user mode by shutting down the standby machine.
b.
When the machine prompts for password, type either ^ -d to proceed with normal startup, or the root
password for system maintenance.
Step 3
Load the CD-ROM labeled Solaris 8 Software CD (disk 1 of 2) into the CD-ROM drive.
Step 4
If the system is currently running, log in as root and bring the system to the ok prompt by entering the
following command:
# init 0
Note
If you are prompted to select a language before booting from the CD, go to the ok prompt by
sending a break on the console port. On the Sun Fire V210, Netra 20, 240, and 440 platforms,
the key sequence <cr>#. will get you to the system controller prompt.
From the system controller prompt, use the break -y command to break out of the operating
system and console -f command to return to the console display. You should see the ok prompt.
Step 5
From the following list, select the procedure that corresponds to the machine you are installing.
a.
Netra t 100/105: Type the following command and press Enter:
ok set-defaults
Step 6
b.
Netra t 1400/1405: Go to Step 6.
c.
Netra t 1120/1125: Go to Step 6.
d.
Sun Fire V120/Netra 120: Go to Step 6.
e.
Sun Fire V210: Go to Step 6.
f.
Netra 20: Go to Step 6.
g.
Netra 240: Go to Step 6.
h.
Netra 440: Go to Step 6.
Boot the system from the CD-ROM drive by entering the following command at the ok prompt:
ok boot cdrom
The system reboots and a screen similar to the following is displayed:
Select a Language
0. English
1. French
2. German
3. Italian
4. Japanese
5. Korean
6. Simplified Chinese
7. Spanish
8. Swedish
9. Traditional Chinese
Please make a choice (0 - 9), or press h or ? for help: 0
Step 7
Type the number 0 for the English language. Press Enter to continue.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-5
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Other language choices are not supported.
Note
A screen similar to the following is displayed:
Select a Locale
0.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
English (C - 7-bit ASCII)
Albania (ISO8859-2)
Australia (ISO8859-1)
Belgium-Flemish (ISO8859-1)
Belgium-Flemish (ISO8859-15 - Euro)
Bosnia (ISO8859-2)
Brazil (ISO8859-1)
Brazil (UTF-8)
Bulgaria (ISO8859-5)
Canada-English (ISO8859-1)
Catalan, Spain (ISO8859-1)
Catalan, Spain (ISO8859-15 - Euro)
Croatia (ISO8859-2)
Czech Republic (ISO8859-2)
Denmark (ISO8859-1)
Denmark (ISO8859-15 - Euro)
Egypt (ISO8859-6)
Egypt (UTF-8)
Egypt (UTF-8)
Press Return to show more choices.
Please make a choice (0 - 55), or press h or ? for help:
Step 8
See the following selections:
a.
If you are using the 10/01 installation CDs: If your system is located in the USA, type 53
(en_US.ISO8859-1) and press Enter to continue.
If your location is not in the USA, type the number 0 for English and press Enter to continue.
a.
If you are using the 2/02 installation CDs: If your system is located in the USA, type 48—the
number that corresponds to USA (en_US.ISO8859-1)—and press Enter to continue.
b.
If you are using the 2/04 installation CDs: If your system is located in the USA, type 49—the
number that corresponds to USA (en_US.ISO8859-1)—and press Enter to continue.
If your location is not in the USA, type the number 0 for English and press Enter to continue.
Note
Only the USA and English locales are supported.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-6
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
What
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
13)
Type
Step 9
type of terminal are you using?
ANSI Standard CRT
DEC VT52
DEC VT100
Heathkit 19
Lear Siegler ADM31
PC Console
Sun Command Tool
Sun Workstation
Televideo 910
Televideo 925
Wyse Model 50
X Terminal Emulator (xterms)
Other
the number of your choice and press Return:
Enter the number that corresponds to the terminal you are using and press Enter. For example, if you
are using an X terminal emulator, type 12 and press Enter.
A screen similar to the following is displayed:
- The Solaris Installation Program -------------------------------------------The Solaris installation program is divided into a series of short sections
where you'll be prompted to provide information for the installation. At
the end of each section, you'll be able to change the selections you've
made before continuing.
About navigation...
- The mouse cannot be used.
- If your keyboard does not have function keys, or they do not
respond, press ESC; the legend at the bottom of the screen
will change to show the ESC keys to use for navigation.
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 10
Press F2 to continue.
A screen similar to the following is displayed:
- Identify This System -------------------------------------------------------On the next screens, you must identify this system as networked or
non-networked, and set the default time zone and date/time.
If this system is networked, the software will try to find the information
it needs to identify your system; you will be prompted to supply any
information it cannot find.
> To begin identifying this system, press F2.
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 11
Press F2 to continue.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-7
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
- Network Connectivity -------------------------------------------------------Specify Yes if the system is connected to the network by one of the Solaris
or vendor network/communication Ethernet cards that are supported on the
Solaris CD. See your hardware documentation for the current list of
supported cards.
Specify No if the system is connected to a network/communication card that
is not supported on the Solaris CD, and follow the instructions listed under
Help.
Networked
--------[X] Yes
[ ] No
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 12
Use the arrow keys to navigate and press the space bar to make your selection. Verify that Yes is selected
and press F2 to continue.
A screen similar to the following is displayed:
- DHCP -----------------------------------------------------------------------On this screen you must specify whether or not this system should use DHCP
for network interface configuration. Choose Yes if DHCP is to be used, or
No if the interfaces are to be configured manually.
WARNING: Because this machine booted from the network, DHCP support will not
be enabled, if selected, until after the system reboots.
Use DHCP
-------[ ] Yes
[X] No
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 13
Verify that No is selected and press F2 to continue.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-8
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
- Primary Network Interface --------------------------------------------------On this screen you must specify which of the following network adapters is
the system's primary network interface. Usually the correct choice is the
lowest number. However, do not guess; ask your system administrator if
you're not sure.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Primary network interface
------------------------[X] hme0
[ ] hme1
------------------------------------------------------------------------------F2_Continue
F6_Help
Note
Step 14
This screen may show a different interface, depending on the platform and PCI card that are
installed. For details, refer to Table 2-2 on page 2-4 (Device Names on Supported Cisco MGC
Software Platforms).
Select the proper port and press F2 to continue.
A screen similar to the following is displayed:
- Host Name ------------------------------------------------------------------On this screen you must enter your host name, which identifies this system
on the network. The name must be unique within your domain; creating a
duplicate host name will cause problems on the network after you install
Solaris.
A host name must be at least two characters; it can contain letters, digits,
and minus signs (-).
Host name:
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 15
Type the host name of the target Netra machine, then press F2 to continue.
Note
For machine-specific information such as host name, refer to your notes in Table 1-2 on
page 1-4, “Required Machine-specific Information”, if you used the checklist to note down the
host name.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-9
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
- IP Address -----------------------------------------------------------------On this screen you must enter the Internet Protocol (IP) address for this
system. It must be unique and follow your site's address conventions, or a
system/network failure could result.
IP addresses contain four sets of numbers separated by periods (for example
129.200.9.1).
IP address:
------------------------------------------------------------------------------F2_Continue
Step 16
F6_Help
Enter the IP address of this machine in dotted decimal format and press F2 to continue.
Note
Refer to “Required Information Checklist”, Table 1-3 on page 1-4, if you used the checklist to
note down the IP address.
A screen similar to the following is displayed:
- Subnets --------------------------------------------------------------------On this screen you must specify whether this system is part of a subnet. If
you specify incorrectly, the system will have problems communicating on the
network after you reboot.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
System part of a subnet
----------------------[X] Yes
[ ] No
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 17
Verify that Yes is selected (use the arrow keys to move the cursor to Yes and press the spacebar to select
it). Press F2 to continue.
A screen similar to the following is displayed:
- Netmask -----------------------------------------------------------------------On this screen you must specify the netmask of your subnet. A default
netmask is shown; do not accept the default unless you are sure it is
correct for your subnet. A netmask must contain four sets of numbers
separated by periods (for example 255.255.255.0).
Netmask:
---------------------------------------------------------------------------------F2_Continue
F6_Help
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-10
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 18
Enter the site-specific IP netmask for the subnet (see “Site-specific Information”, Table 1-2 on
page 1-3, if you noted down the information provided by your site administrator in this table). Press F2
to continue.
A screen similar to the following is displayed:
- IPv6 -----------------------------------------------------------------------On this screen you should specify whether or not IPv6, the next generation
Internet Protocol, will be enabled on this machine. Enabling IPv6 will have
no effect if this machine is not on a network that provides IPv6 service.
IPv4 service will not be affected if IPv6 is enabled.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Enable IPv6
----------[ ] Yes
[X] No
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 19
Verify that No is selected and press F2 to continue.
A screen similar to the following is displayed:
- Confirm Information --------------------------------------------------------> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Networked:
Use DHCP:
Primary network interface:
Host name:
IP address:
System part of Subnet:
Netmask:
Enable IPv6:
Yes
No
hme0
<host-name>
<IP address>
Yes
<IP netmask>
No
------------------------------------------------------------------------------F2_Continue
F4_Change
F6_Help
Step 20
Confirm the information displayed. Press F2 to accept the information and continue, or press F4 to go
back and make changes.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-11
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
- Configure Security Policy: -------------------------------------------------Specify Yes if the system will use the Kerberos security mechanism.
Specify No if this system will use standard UNIX security.
Configure Kerberos Security
--------------------------[ ] Yes
[X] No
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 21
Verify that No is selected and press F2 to continue.
A screen similar to the following is displayed:
- Confirm Information > Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Configure Kerberos Security: No
------------------------------------------------------------------------------F2_Continue
F4_Change
F6_Help
Step 22
Confirm your previous answer of No and press F2 to continue.
A screen similar to the following is displayed:
- Name Service ---------------------------------------------------------------On this screen you must provide name service information. Select the name
service that will be used by this system, or None if your system will either
not use a name service at all, or if it will use a name service not listed
here.
> To make a selection, use the arrow keys to highlight the option
and press Return to mark it [X].
Name service
-----------[ ] NIS+
[ ] NIS
[ ] DNS
[X] None
------------------------------------------------------------------------------F2_Continue
F6_Help
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-12
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 23
Use the arrow keys to move the cursor to None and press the spacebar to select it. Press F2 to continue.
A screen similar to the following is displayed:
- Confirm Information --------------------------------------------------------> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Name service: None
------------------------------------------------------------------------------F2_Continue
F4_Change
F6_Help
Step 24
Confirm your previous answer of None and press F2 to continue.
A screen similar to the following is displayed:
- Time Zone ------------------------------------------------------------------On this screen you must specify your default time zone. You can specify a
time zone in three ways: select one of the geographic regions from the
list, select other - offset from GMT, or other - specify time zone file.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Regions
---------------------------------[ ] Asia, Western
[ ] Australia / New Zealand
[ ] Canada
[ ] Europe
[ ] Mexico
[ ] South America
[X] United States
[ ] other - offset from GMT
[ ] other - specify time zone file
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 25
Select the local time zone where the system is located.
Note
a.
The following two steps are examples of how to set the time zone, in this case, to United States
Eastern time.
Use the arrow keys to move the cursor to United States and press the spacebar to select it, then press
F2 to continue.
A screen similar to the following is displayed:
- Time Zone ------------------------------------------------------------------> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Time zones
---------------[X] Eastern
[ ] Central
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-13
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
[
[
[
[
[
[
[
[
[
]
]
]
]
]
]
]
]
]
Mountain
Pacific
East-Indiana
Arizona
Michigan
Samoa
Alaska
Aleutian
Hawaii
------------------------------------------------------------------------------F2_Continue
F5_Cancel
F6_Help
b.
Use the arrow keys to move the cursor to your time zone (in this example, “Eastern” is selected) and
press the space bar to select it. Press F2 to continue.
A screen similar to the following is displayed:
- Date and Time --------------------------------------------------------------> Accept the default date and time or enter
new values.
Date and time: 2001-01-04 10:59
Year
Month
Day
Hour
Minute
(4 digits)
(1-12)
(1-31)
(0-23)
(0-59)
:
:
:
:
:
2002
03
20
10
59
------------------------------------------------------------------------------F2_Continue
F6_Help
Step 26
Enter the correct date and time and press F2 to continue.
A screen showing the time zone, date, and time is displayed.
Step 27
Confirm that the information displayed is correct. Press either F2 to accept the information and continue,
or F4 to go back and make changes.
A screen similar to the following may be displayed:
Please wait...
System identification is completed.
Starting Solaris installation program...
Executing JumpStart preinstall phase...
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
System identification is now complete. Proceed to the next section, “Installing the Solaris 8 Operating
System”.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-14
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Installing the Solaris 8 Operating System
This section provides the procedures for installing the Solaris 8 operating system.
Note
These procedures cover the 18 GB, 36 GB, and 73 GB disk drives (see Step 11, below).
Upon acceptance of Step 27 in the previous section, “Booting from a Local CD-ROM”, a screen similar
to the following may be displayed if there is a previous file system on the disk:
- Solaris Interactive Installation -------------------------------------------This system is upgradable, so there are two ways to install the Solaris
software.
The Upgrade option updates the Solaris software to the new release, saving
as many modifications to the previous version of Solaris software as
possible. Back up the system before using the Upgrade option.
The Initial option overwrites the system disks with the new version of
Solaris software. This option allows you to preserve any existing file
systems. Back up any modifications made to the previous version of Solaris
software before starting the Initial option.
After you select an option and complete the tasks that follow, a summary of
your actions will be displayed.
------------------------------------------------------------------------------F2_Upgrade
F4_Initial
F5_Exit
F6_Help
Step 1
Press F4 for Initial Installation and continue. The following screen is displayed:
- Solaris Interactive Installation -------------------------------------------You'll be using the initial option for installing Solaris software on the
system. The initial option overwrites the system disks when the new Solaris
software is installed.
On the following screens, you can accept the defaults or you can customize
how Solaris software will be installed by:
- Selecting the type of Solaris software to install
- Selecting disks to hold software you've selected
- Specifying how file systems are laid out on the disks
After completing these tasks, a summary of your selections (called a
profile) will be displayed.
There are two ways to install the software - standard and flash
------------------------------------------------------------------------------F2_Standard
F3_Go Back
F4_Flash F5_Exit
F6_Help
Step 2
Press F2 for Standard installation.
The following screen is displayed:
- Select Geographic Regions --------------------------------------------------Select the geographic regions for which support should be installed.
> [ ] Asia
> [ ] Eastern Europe
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
>
>
>
>
>
>
>
>
>
>
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[/]
[ ]
[ ]
[ ]
Middle East
Central America
South America
Northern Europe
Southern Europe
Central Europe
North America
Australasia
Western Europe
Northern Africa
Move left, right, up, down using the arrow keys
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F5_Exit
F6_Help
Step 3
Use the arrow keys to move the cursor to the geographic region of the target machine and press the
spacebar to make your selection. Press F2 to continue.
Note
The following two screens are not displayed when installing on newer platforms such as Sun Fire
V120, Sun Fire V210, Netra 20, Netra 120, Netra 240, or Netra 440. Continue to Step 4.
A screen similar to the following may be displayed:
- Select 64 Bit --------------------------------------------------------------Select 64-bit if you want to install the Solaris 64-bit packages on this
system.
[X]
Select To Include Solaris 64-bit Support
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F5_Exit
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-16
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 4
If the preceding screen is displayed, verify the that Select To Include Solaris 64-bit Support is selected
and press F2 to continue.
A screen similar to the following is displayed:
- Select Software ------------------------------------------------------------Select the Solaris software to install on the system.
NOTE: After selecting a software group, you can add or remove software by
customizing it. However, this requires understanding of software
dependencies and how Solaris software is packaged
[ ]
[ ]
[ ]
Entire Distribution plus OEM support ....... 1224.00 MB
Entire Distribution with 64 bit ............ 1197.00 MB
Developer System Support with 64 bit support. 1148.00 MB (F4 to Customize)
[X]
[ ]
End User System Support..................... 856.00 MB
Core System Support ........................ 279.00 MB
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Customize
F5_Exit
F6_Help
Step 5
Use the arrow keys to move the cursor to Developer System Support with 64 bit support for the 10/01
and 2/02 releases, or Entire Distribution with 64 bit for the 2/04 release, and press the space bar to
select. Then press F2 to continue.
A screen similar to the following is displayed:
- Select Disks ---------------------------------------------------------------On this screen you must select the disks for installing Solaris software.
Start by looking at the Suggested Minimum field; this value is the
approximate space needed to install the software you've selected. Keep
selecting disks until the Total Selected value exceeds the Suggested Minimum
value.
Disk Device (Size)
Available Space
=============================================
[X] c0t0d0
(17269 MB) boot disk
17269 MB
[ ] c0t1d0
(17269 MB)
17269 MB
Total Selected:
Suggested Minimum:
(F4 to edit)
17269 MB
845 MB
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Edit
F5_Exit
F6_Help
Note
For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names on
Supported Cisco MGC Software Platforms).
If the machine has a larger disk drive than the 18 GB disks shown here, the Size and Available
Space fields will be different.
Netra 440 will display with four disks, but only two will be used.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-17
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 6
Select the procedure that applies to your system:
a.
PGW Host: When installing Solaris for a PGW Host, make sure that only the first disk device is
selected. For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names
on Supported Cisco MGC Software Platforms).
Press F2 to continue.
Note
Caution
For the PGW Host, the second disk device may be configured as a mirror of the first or as
storage space for logs, measurements, alarm, and CDR files. This is done in the
“Configuring a Second Disk Drive” section on page 2-32.
If your PGW Host has the Cisco MGC software and the Cisco Voice Services Provisioning Tool (VSPT)
installed, you must perform the procedures that follow to configure the Solaris environment for the PGW.
The Cisco MGC software requires a particular configuration of the Solaris environment to function
properly.
b.
HSI: When installing Solaris for HSI with two disks, verify that both the first and second disk
devices are selected.
When installing Solaris for HSI on a platform with a single disk, verify that only the first disk device
is selected.
For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names on
Supported Cisco MGC Software Platforms).
Press F2 to continue.
Note
c.
For the HSI, the second disk device may be configured as a mirror of the first. This is done
in the “Configuring a Second Disk Drive” section on page 2-32.
BAMS with Disk Array: When installing Solaris for a BAMS on a Netra 1400/1405 with an
st A1000 Disk Array, verify that only the first disk device is selected. For the device names for each
platform type, refer to Table 2-2 on page 2-4 (Device Names on Supported Cisco MGC Software
Platforms).
Press F2 to continue.
d.
BAMS without Disk Array only: When installing Solaris for a BAMS without a Disk Array, verify
that both the first and second disk devices are selected. For the device names for each platform type,
refer to Table 2-2 on page 2-4 (Device Names on Supported Cisco MGC Software Platforms).
Press F2 to continue.
A screen similar to the following is displayed:
- Preserve Data? -------------------------------------------------------------Do you want to preserve existing data? At least one of the disks you've
selected for installing Solaris software has file systems or unnamed slices
that you may want to save.
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Preserve
F5_Exit
F6_Help
Step 7
If above screen is displayed, press F2 to continue.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-18
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
A screen similar to the following is displayed:
- Automatically Layout File Systems? -----------------------------------------Do you want to use auto-layout to automatically layout file systems?
Manually laying out file systems requires advanced system administration
skills.
------------------------------------------------------------------------------F2_Auto Layout
F3_Go Back
F4_Manual Layout
F5_Exit
F6_Help
Step 8
Press F2 to automatically lay out the file systems and continue.
A screen similar to the following is displayed:
- Automatically Layout File Systems ------------------------------------------On this screen you must select all the file systems you want auto-layout to
create, or accept the default file systems shown.
NOTE: For small disks, it may be necessary for auto-layout to break up some
of the file systems you request into smaller file systems to fit the
available disk space. So, after auto-layout completes, you may find file
systems in the layout that you did not select from the list below.
File Systems for Auto-layout
========================================
[X] /
[ ] /opt
[ ] /usr
[ ] /usr/openwin
[ ] /var
[X] swap
------------------------------------------------------------------------------F2_Continue
F5_Cancel
F6_Help
Step 9
Press F2 to continue.
A screen similar to the following is displayed:
- File System and Disk Layout ------------------------------------------------The summary below is your current file system and disk layout, based on the
information you've supplied.
NOTE: If you choose to customize, you should understand file systems, their
intended purpose on the disk, and how changing them may affect the operation
of the system.
File system/Mount point
Disk/Slice
Size
=============================================================
/
c0t0d0s0
1270 MB
swap
c0t0d0s1
296 MB
overlap
c0t0d0s2
17269 MB
/export/home
c0t0d0s7
15702 MB
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Customize
F5_Exit
F6_Help
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-19
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 10
Press F4 (Customize) to manually change the disk partitions.
If more than one disk was selected in Step 6, a screen similar to the following is displayed:
- Select Disk to Customize
Boot Device: c0t0d0s0
----------------------------------------------------
Disk
(Size)
Configured File Systems
==================================================================
[
[
] c0t0d0
] c0t1d0
(34730 MB)
(34730 MB)
/, swap, /export/home
/export/home
------------------------------------------------------------------------------F2_OK
F4_Customize
F6_Help
Step 11
Select each disk using the up and down arrows and press F4 to customize.
Note
The following screen may not be displayed for Solaris 2/04. The disk was already selected in
Step 6.
For Solaris 2/02, a screen similar to the following is displayed:
- Customize Disk: c0t0d0 -----------------------------------------------------Boot Device: c0t0d0s0
Entry: /
Recommended: 960 MB
Minimum: 815 MB
================================================================================
Slice Mount Point
Size (MB)
0
/
1270
1
swap
296
2
overlap
17269
3
0
4
0
5
0
6
0
7
/export/home
15702
================================================================================
Capacity:
17269 MB
Allocated:
17268 MB
Rounding Error:
1 MB
Free:
0 MB
------------------------------------------------------------------------------F2_OK
F4_Options
F5_Cancel
F6_Help
Note
Step 12
For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names on
Supported Cisco MGC Software Platforms). If the machine has a larger disk drive than the 18
GB shown here, Size and Available Space fields will be different.
Use the Tab key to navigate from field to field on this display. Enter the partition name and size to match
the corresponding drive in Table 2-3 through Table 2-6.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-20
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Caution
Make sure that you select the correct tables based on the disk drive being configured (Disk 0
or Disk 1), as well as the correct disk size. Select the column in the table that matches the
software that will be installed on the platform later.
For BAMS, select the correct column based on whether the platform will have an external disk
array attached.
Caution
In the partition tables that follow, slice 2 is the overlap slice. It is configured by default to be
the whole disk. This slice entry is only used for test and maintenance purposes—it is not
mounted by the operating system. This slice entry should not be changed.
You must remove slice 7 before configuring the rest of the drive.
Due to rounding, the size of the slice shown after entry may be slightly larger than what was
entered (for example, an entry of 1024 may be rounded up to 1025 or 1026).
Disks 2 and 3 are not currently used.
Caution
For HSI: If you are upgrading from HSI 2.2 to HSI 4.1, make sure that your disks are
correctly partitioned to support disk mirroring—partitioning requires the new disk layout.
If your disks are not correctly partitioned, you must re-partition your disks.
Note
There may be an unnamed partition in some of the following tables that is created without a
mount point (slice 7) for the PGW Host and HSI. The DiskSuite disk mirroring software uses
this partition. If DiskSuite is not used, then the space is unused.
Note
The third and fourth disks are not used.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-21
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Table 2-3
PGW Host
Slice
No.
Slice
Name
18-Gigabyte Disk 0 Partition Table
BAMS with Disk
Array
BAMS without Disk Array
Slice Size
(MB)
Slice Name
Slice Size
(MB)
Slice Name Slice Size
(MB)
HSI
Slice Name
Slice Size
(MB)
0.
/
512
/
1000
/
1024
/
512
1
swap
4096
swap
2040
swap
4096
swap
4096
2
overlap
17269
overlap
17269
overlap
17269
overlap
17269
0
/opt
6144
3
0
0
4
/opt
10590
/opt
1729
/opt
11110
/var
1024
5
/var
1024
/usr
1024
/usr
1024
/usr
1024
6
/usr
1024
/opt/CiscoBAMS/CDR/archive
11000
0
/export
4081
0
15
7
15
Table 2-4
PGW Host
(See Configuring a
Second Disk Drive,
page 2-32)
Slice
No.
Slice
Name
0.
0
1
0
2
overlap
17269
18-Gigabyte Disk 1 Partition Table
BAMS without Disk Array
Slice
Size (MB)
Slice Name
/opt/CiscoBAMS/data
overlap
15
Slice Size
(MB)
BAMS with Disk
Array
Slice Name
Slice Size
(MB)
HSI
(See Configuring a Second
Disk Drive, page 2-32)
Slice Name
Slice Size
(MB)
17269
0
0
0
0
0
17269
overlap
17269
overlap
17269
3
0
0
0
0
4
0
0
0
0
5
0
0
0
0
6
0
0
0
0
7
0
0
0
0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-22
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Table 2-5
36-Gigabyte Disk 0 Partition Table
PGW Host
Slice
Name
Slice
No.
BAMS with Disk
Array
BAMS without Disk Array
Slice
Size
(MB)
Slice Name
Slice
Size
(MB)
Slice Name
HSI
Slice
Size
(MB)
Slice Name
Slice Size
(MB)
0.
/
1024
/
2048
/
2048
/
1024
1
swap
4096
swap
4096
swap
4096
swap
4096
2
overlap
34730
overlap
34730
overlap
34730
overlap
34730
0
/opt
25600
3
0
0
4
/opt
27545
/opt
3458
/opt
26537
/var
1024
5
/var
1024
/usr
2048
/usr
2048
/usr
2048
6
/usr
1024
/opt/CiscoBAMS/CDR/archive
23078
0
/export
920
0
0
7
15
Table 2-6
36-Gigabyte Disk 1 Partition Table
PGW
(See Configuring a
Second Disk Drive,
page 2-32)
Slice
No.
Slice
Name
0
1
0
2
overlap
BAMS with Disk
Array
BAMS without Disk Array
Slice Size
(MB)
0.
15
Slice Name
/opt/CiscoBAMS/data
34730 overlap
Slice Size
(MB)
Slice Name
Slice Size
(MB)
HSI
(See Configuring a
Second Disk Drive,
page 2-32)
Slice Name
Slice Size
(MB)
34730
0
0
0
0
0
34730
overlap
34730
overlap
34730
3
0
0
0
0
4
0
0
0
0
5
0
0
0
0
6
0
0
0
0
7
0
0
0
0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-23
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Table 2-7
73-Gigabyte Disk 0 Partition Table
PGW Host
Slice Slice Name
No.
BAMS without Disk Array
Slice Size
(MB)
Slice Name
BAMS with Disk Array
Slice Size Slice Name
(MB)
HSI
Slice Size
(MB)
Slice
Name
Slice Size
(MB)
0.
/
4099 /
4099 /
4099
/
1028
1
swap
4099 swap
4099 swap
4099
swap
4099
2
overlap
69994 overlap
69994 overlap
69994
overlap
69994
/opt
59341
3
0
0
4
/opt
53553 /opt
8193 /opt
57697
/var
1028
5
/var
4099 /usr
4099 /usr
4099
/usr
2052
6
/usr
4099 /opt/CiscoBAMS/CDR/archive
/export
2399
7
49503
44
44
Table 2-8
73-Gigabyte Disk 1 Partition Table
PGW Host
(See Configuring a Second
Disk Drive, page 2-32)
Slice
No.
Slice Name
Slice Size
(MB)
0.
BAMS without Disk Array
Slice Name
/opt/CiscoBAMS/data
BAMS with Disk Array
Slice Size
(MB)
Slice Name
Slice Size
(MB)
HSI
(See Configuring a
Second Disk Drive,
page 2-32)
Slice
Name
Slice Size
(MB)
69994 overlap
69994
69994
1
2
overlap
69994 overlap
69994 overlap
3
0
0
0
0
4
0
0
0
0
5
0
0
0
0
6
0
0
0
0
7
0
0
0
0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-24
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Table 2-9
73-Gigabyte Disk 2 Partition Table
PGW Host
(Not Supported)
Slice
No.
Slice Name
BAMS without Disk Array
(Not Supported)
Slice Size
(MB)
Slice Name
BAMS with Disk Array
(Not Supported)
Slice Size
(MB)
Slice Name
HSI
(Not Supported)
Slice Size
(MB)
Slice
Name
Slice Size
(MB)
69994 overlap
69994
0.
1
2
overlap
69994 overlap
69994 overlap
3
0
4
0
5
0
6
0
7
0
Table 2-10
73-Gigabyte Disk 3 Partition Table
PGW Host
(Not Supported)
Slice
No.
Slice Name
BAMS without Disk Array
(Not Supported)
Slice Size
(MB)
Slice Name
BAMS with Disk Array
(Not Supported)
Slice Size
(MB)
Slice Name
HSI
(Not Supported)
Slice Size
(MB)
Slice
Name
Slice Size
(MB)
69994 overlap
69994
0.
1
2
overlap
69994 overlap
69994 overlap
3
0
0
0
4
0
0
0
5
0
0
0
6
0
0
0
7
0
0
0
PGW Host
Slice Slice Name Slice Size
No.
(MB)
Table 2-11
146-Gigabyte Disk 0 Partition Table
Table 2-12
146-Gigabyte Disk 1 Partition Table
BAMS without Disk Array
Slice Name
BAMS with Disk Array
Slice Size Slice Name
(MB)
HSI
Slice Size
(MB)
Slice
Name
Slice Size
(MB)
0.
/
4104 /
4099 /
4099
/
1028
1
swap
4104 swap
4099 swap
4099
swap
4099
2
overlap
139989 overlap
139989 overlap
139989
overlap
69994
/opt
59341
/var
1028
3
4
0
/opt
123523 /opt
0
8193 /opt
115395
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-25
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
5
/var
4104 /usr
6
/usr
4104 /opt/CiscoBAMS/CDR/archive
7
4099 /usr
4099
99007 0
/usr
2052
/export
2399
49
44
PGW Host
(Not Supported)
Slice
No.
Slice Name
0.
BAMS without Disk Array
(Not Supported)
Slice Size
(MB)
Slice Name
/opt/CiscoBAMS/
data
Slice Size
(MB)
BAMS with Disk Array
(Not Supported)
Slice Name
Slice Size
(MB)
HSI
(Not Supported)
Slice
Name
Slice Size
(MB)
139989 overlap
139989
139989
1
2
overlap
139989 overlap
139989 overlap
3
0
4
0
5
0
6
0
7
0
Step 13
When the configuration is complete, press F2 to accept and continue. If you are configuring two disks
and both disks have been customized correctly, press F2 a second time.
The following screen reflects the 18 GB disk drive configuration for the Cisco MGC software
application. It will differ for the BAMS and HSI installation and for all installations on 36 GB or 73 GB
disks.
- File System and Disk Layout ------------------------------------------------The summary below is your current file system and disk layout, based on the
information you've supplied.
NOTE: If you choose to customize, you should understand file systems, their
intended purpose on the disk, and how changing them may affect the operation
of the system.
File system/Mount point
Disk/Slice
Size
=============================================================
/
c0t0d0s0
513 MB
swap
c0t0d0s1
4097 MB
overlap
c0t0d0s2
17269 MB
/opt
c0t0d0s4
10590 MB
/var
c0t0d0s5
1026 MB
/usr
c0t0d0s6
1026 MB
c0t0d0s7
15 MB
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Customize
F5_Exit
F6_Help
Step 14
If the display does not coincide with the entered data (see the Note in Step 6), press F3 to go back and
make changes. If the information displayed is acceptable, press F2 to continue.
A screen similar to the following is displayed:
- Mount Remote File Systems? --------------------------------------------------
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-26
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Do you want to mount software from a remote file server? This may be
necessary if you had to remove software because of disk space problems.
------------------------------------------------------------------------------F2_Continue
F3_Go Back
F4_Remote Mounts
F5_Exit
F6_Help
Step 15
Press F2 to continue.
A screen similar to the following is displayed:
- Profile ---------------------------------------------------------------------
The information shown below is your profile for installing Solaris software.
It reflects the choices you've made on previous screens.
============================================================================
Installation Option: Initial
|
Boot Device: c0t0d0
|
Client Services: None
|
|
Locales: U.S.A. (en_US.ISO8859-1)
|
|
Software: Solaris 8, Developer System Support 64-bit
|
|
File System and Disk Layout:
v
------------------------------------------------------------------------------F2_Continue
F4_Change
F5_Exit
F6_Help
Step 16
If the display does not coincide with the data that is entered, press F4 to make changes. Otherwise, press
F2 to accept the information displayed and continue.
A screen similar to the following is displayed:
- Warning --------------------------------------------------------------------The following disk configuration condition(s) have been
detected. Errors must be fixed to ensure a successful
installation. Warnings can be ignored without causing the
installation to fail.
WARNING: Unused disk space (c0t0d0)
------------------------------------------------------------------------------F2_OK
F5_Cancel
Step 17
A small amount of disk space (required for DiskSuite installation) is left unused, causing the displayed
warning. This will not effect the installation. Press F2 to continue.
A screen similar to the following is displayed:
- Reboot After Installation? -------------------------------------------------After Solaris software is installed, the system must be rebooted. You can
choose to have the system automatically reboot, or you can choose to
manually reboot the system if you want to run scripts or do other
customizations before the reboot. You can manually reboot a system by using
the reboot(1M) command.
[X] Auto Reboot
[ ] Manual Reboot
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-27
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
------------------------------------------------------------------------------F2_Begin Installation
F5_Cancel
Step 18
Press F2 to automatically reboot after the Solaris 8 operating system is installed and to continue. This
begins the actual operating system installation.
A screen similar to the following is displayed:
Preparing system for Solaris install.
As the installation program sets up the disk drive for the OS installation, lines similar to the following
are appended to the display:
Configuring disk (c0t0d0)
- Creating Solaris disk label (VTOC)
Creating and checking UFS file systems
- Creating / (c0t0d0s0)
- Creating /opt (c0t0d0s4)
- Creating /var (c0t0d0s5)
- Creating /usr (c0t0d0s6)
Beginning Software Installation
Solaris Initial Install
MBytes Installed:
MBytes Remaining:
xxx.xx
xxx.xx
Installing: Solaris package currently being installed
|
0
|
20
|
40
|
60
|
80
|
100
When the installation of the Solaris 8 operating system on Disk 1 of 2 is complete, information similar
to the following scrolls through the display and the machine reboots:
Solaris 8 software installation succeeded
Customizing system files
- Mount points table (/etc/vfstab)
- Unselected disk mount points (/var/sadm/system/data/vfstab.unselected)
- Network host addresses (/etc/hosts)
Customizing system devices
- Physical devices (/devices)
- Logical devices (/dev)
Installing boot information
- Installing boot blocks (c0t0d0s0)
Installation log location
- /a/var/sadm/system/logs/install_log (before reboot)
- /var/sadm/system/logs/install_log (after reboot)
Installation complete
Executing SolStart postinstall phase...
Executing finish script "patch_finish"...
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-28
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Finish script patch_finish execution completed.
Executing JumpStart postinstall phase...
The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.
The finish script log 'finish.log'
is located in /var/sadm/system/logs after reboot.
syncing file systems... done
rebooting...
Resetting ...
When the reboot is complete, a screen similar to the following is displayed:
On this screen you can create a root password.
A root password can contain any number of characters, but only the first eight
characters in the password are significant. (For example, if you create
`a1b2c3d4e5f6' as your root password, you can use `a1b2c3d4' to gain root
access.)
You will be prompted to type the root password twice; for security, the password
will not be displayed on the screen as you type it.
> If you do not want a root password, press RETURN twice.
Root password:
Press Return to continue.
Step 19
Refer to Table 1-2 for the root password for this system and type it. Press Enter to continue. The
following line is appended to the display and you will be prompted to confirm the root password.
Re-enter your root password.
Press Return to continue.
Step 20
Re-type the root password for this system, then press Enter.
A screen similar to the following is displayed:
System identification is completed.
Note
The next two screens are not displayed when installing on newer systems such as Sun Fire V120,
Sun Fire V210, Netra 120, Netra 20, Netra 240, or Netra 440 platforms.
================================================================
This system is configured to conserve energy.
================================================================
After 30 minutes of idle time on this system, your system state will
automatically be saved to disk, and the system will power-off. Later, when you
want to use the system again, and you turn the power back on, your system will
be restored to its previous state, including all the programs that you were
running. Do you want this automatic power-saving shutdown? (If this system is
used as a server, answer n) [y,n,?]
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-29
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 21
Type n and press Enter to disable the power saving feature and continue. The following lines are
appended to the display:
Autoshutdown has been disabled.
Do you want the system to ask about this again, when you next reboot? (This
gives you the chance to try it before deciding whether to keep it.) [y,n,?]
Step 22
Type n and press Enter to permanently disable the power saving feature and continue. The installation
continues and text similar to the following are displayed:
Starting Web Start Launcher in Command Line Mode.
Please specify the media from which you will be installing Solaris 8 (SPARC)
Software 2.
Alternatively, choose the selection for "Skip" to skip this CD and go on to the
next one.
Media:
1. CD
2. Network File System
3. Skip
Media [1]: 1
Step 23
Type 1 Press Enter to continue. The following lines are appended to the display:
Please insert the CD for Solaris 8 (SPARC) Software 2.
Once the CD has been inserted, please press Enter.
Enter S to skip this CD and go on to the next one.
To select a different media, enter B to go Back.
[]
Note
Step 24
For the Sun Fire V210 and Netra 240 and 440: The screen output is CD/DVD.
Remove the Solaris 8 Software CD, Disk 1 of 2, load Solaris 8 Software CD, Disk 2 of 2, and press Enter to
continue.
Lines similar to the following are appended to the display:
Reading Solaris 8 (SPARC) Software 2.... \
Launching installer for Solaris 8 (SPARC) Software 2. Please Wait...
Installing Solaris 8 Software 2
|-1%--------------25%-----------------50%-----------------75%--------------100%|
Installation details:
1.
Product
Solaris 8 Software 2
2.
Done
Result
Installed
More Info
Available
Enter the number corresponding to the desired selection for more
information, or enter 2 to continue [2]:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-30
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Loading the Solaris 8 Operating System
Step 25
Type 2 and press Enter to continue.
The following lines are appended to the display:
End of Solaris 8 Software 2 installation.
<Press ENTER to continue>
Step 26
Press Enter to continue.
The following line is appended to the display:
<Press Return to reboot the system>
Step 27
Press Enter to reboot.
Step 28
When the machine reboots, log in as root.
Step 29
Define the default router address and make it permanent by performing the following:
a.
Create a file called /etc/defaultrouter.
b.
Put the default gateway IP address on the first and only line of the file by entering the following
command:
# echo default_router_IP_address > /etc/defaultrouter
This completes the installation of the Solaris 8 operating system. Proceed to the following section to
verify Network Time Protocol (NTP) Packages.
Verifying Network Time Protocol (NTP) Packages
NTP synchronizes call detail record (CDR) timestamps on Cisco PGW 2200s and BAMS. Make sure that
the correct NTP packages are installed by performing the following procedure:
Step 1
Enter the following command:
pkginfo | grep ntp
Text similar to the following is displayed:
system SUNWntpr NTP, (Root)
system SUNWntpu NTP, (Usr)
Step 2
Echo the NTP server IP Address into the file /etc/inet/ntp.conf by entering the following command
(the NTP server address is provided by your system administrator):
# echo "server NTP_server_IP_address" > /etc/inet/ntp.conf
Step 3
Cisco PGW 2200 requires the NTP daemon to always use slewing mechanism to synchronize the local
clock with the NTP server reference time. To enable slewing, enter the following commands to add the
lines in the /etc/inet/ntp.conf file (Note the use of the double arrows ">>"):
# echo "slewalways yes" >> /etc/inet/ntp.conf
# echo "disable pll" >> /etc/inet/ntp.conf
Step 4
Reboot the machine with the following command to activate the default route:
# reboot -- -r
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-31
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring a Second Disk Drive
Step 5
Log in as root.
Step 6
Verify that the deamon xntpd is running by entering the following command:
ps -ef | grep ntp
Text similar to the following is displayed:
root 224 1 0 13:59:25 ? 0:00 /usr/lib/inet/xntpd
siggen 424 415 0 14:15:28 pts/1 0:00 grep ntp
This completes the procedure for verifying that the correct Network Time Protocol (NTP) packages are
installed.
To continue the Solaris 8 operating system installation, go to the following sections in this chapter:
•
For PGW Host: Proceed to the “Configuring a Second Disk Drive” section on page 2-32 for
procedures on configuring a second disk drive, then proceed to the “Configuring Additional Ethernet
Interfaces” section on page 2-45 if you are configuring additional Ethernet interfaces.
•
For BAMS: Proceed to the “Installing the BAMS Disk Array on a Netra t 140x Host” section on
page 2-54, then proceed to the “Configuring Additional Ethernet Interfaces” section on page 2-45 if
you are configuring additional Ethernet interfaces.
•
For HSI: Proceed to the “Configuring a Second Disk Drive” section on page 2-32 for procedures
on configuring a second disk drive, then proceed to the “Configuring Additional Ethernet Interfaces”
section on page 2-45 if you are configuring additional Ethernet interfaces.
Configuring a Second Disk Drive
Note
This section applies to the PGW Host running either the Cisco MGC or HSI software.
The following options are available at this stage of the installation process:
1.
Use the second disk drive as a mirror of the first to increase the availability of the system. Refer to
the “Installing the Solstice DiskSuite (CSCOh016)” section on page 2-32 to install DiskSuite.
2.
Only for systems running the Cisco MGC software: Use the second disk drive for log and spool
systems to increase the capacity for log, alarm, measurement and CDR files. This increases the
performance of the machine. Refer to the “Installing the Log and Spool File Systems (CSCOh005)”
section on page 2-37.
If CSCOh005 is not installed, you will continue to have log and spool file system on the first disk
drive.
Installing the Solstice DiskSuite (CSCOh016)
You can install the DiskSuite program by running the scripts described below. The machine will reboot
several times during the installation process. The scripts are designed to minimize the possibility of
running the scripts in the wrong order. However, you should ensure that the program is properly installed
and take reasonable precautions to run the scripts correctly.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-32
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring a Second Disk Drive
Caution
The order in which packages are installed on the system is important. In particular, DiskSuite
(located in the CSCOh016 package) must be installed before installing the Cisco PGW application
(CiscoMGC software) and the Cisco Security package (CSCOh013).
If your system already has the CSCOh015 software package installed and you install CSCOh016, you
must run the CSCOh015 installation script again to ensure compatibility between the two software
packages (see Step 10, below).
When removing DiskSuite, you must remove CSCOh013 and the Cisco PGW application before
removing DiskSuite. If the CSCOh013 package or the Cisco PGW application are already installed, the
DiskSuite scripts will fail to run.
Note
You must log in as root to run the following DiskSuite installation script.
Note
If you have installed the Solaris 8 operating system on the platform with only one hard disk, shut down
the server and insert a second disk. Turn on the server and log in as root. Run the UNIX command,
/usr/sbin/shutdown -g0 -y -i0, to enter the OK mode. Then run the command, boot -rv, in OK mode to
detect the newly inserted hard disk.
Step 1
Load the Cisco Solaris 8 Patches CD into the CD-ROM drive. Enter the following command to install
the DiskSuite installation scripts:
pkgadd -d /cdrom/cdrom0/CSCOh016.pkg
This command copies the DiskSuite installation scripts into the directory /opt/sun_install/DiskSuite.
Step 2
Enter the following command to open the door of the CD-ROM drive:
eject
Remove the Cisco Solaris 8 Patches CD and re-install the Solaris CD (#2 of 2) in the CD-ROM drive.
Step 3
Change directories. Enter the following command:
cd
Step 4
/opt/sun_install/DiskSuite
Run the first script. Enter the following command:
sh ./install_disksuite_1.sh
This script installs the DiskSuite packages from the Sun Solaris CD (disk #2). The machine reboots after
installing the packages.
Step 5
Log in as root and enter the following command to open the door of the CD-ROM drive:
eject
Remove the Solaris CD (#2 of 2) from the CD-ROM drive.
Step 6
Change directories to /opt/sun_install/DiskSuite. Enter the following command:
cd /opt/sun_install/DiskSuite
Step 7
Run the second script. Enter the following command:
sh ./install_disksuite_2.sh
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-33
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring a Second Disk Drive
This script formats the second disk drive with a partition table that is identical to the first drive on the
system (where Solaris was installed). It creates the required DiskSuite disk partitions and databases. The
machine reboots after creating the disk partitions and databases.
Step 8
Log in as root and go to the /opt/sun_install/DiskSuite directory. Enter the following command:
cd /opt/sun_install/DiskSuite
Step 9
Run the third script. Enter the following command:
sh ./install_disksuite_3.sh
This script attaches the meta-disks and starts the disk mirroring.
Caution
Step 10
DO NOT REBOOT until the disk is completely and correctly mirrored.
Skip this step if the CSCOh015 software package is not installed in your system. However, if the
CSCh015 software package is already installed, ensure that both CSCOh015 and CSCOh016 are
compatible by entering the following commands:
# cd /opt/sun_install
# ./installPatches8
The DiskSuite installation is now complete.
Rebooting from the Mirrored (Secondary) Disk
Caution
Rebooting from the mirrored (secondary) disk is normally done only after a catastrophic failure of the
primary disk.
Perform the following procedure to add an alias in the boot ROM so you can boot off of the secondary
disk, if necessary.
Step 1
Get the information from the system on the second disk that you will boot from. Type the following
command and press Enter:
# prtconf -vp | grep pci | grep disk1
Text similar to the following is displayed:
disk1: ‘/pci@1f,0/pc1@1/scsi@8/disk1,0’
Note
Disk1 is a system-maintained standard for the system's second hard disk.
a.
If the prtconf command returns the above information, you can use it to boot the second disk
without any additional changes. Proceed to Step 3.
b.
If you do not wish to use the above default information, create an alias name other than disk1 for
the second boot disk in the NVRAM by using the information from the prtconf command (above).
For example, to create an alias of "backup_root", enter the following command:.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-34
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring a Second Disk Drive
# eeprom nvramrc='devalias backup_root /pci@1f,0/pci@1/scsi@8/disk@1,0'
Step 2
Check the alias you created by typing the following commands and pressing Enter:
eeprom |grep nvramrc
Text similar to the following is displayed:
use-nvramrc?=true
nvramrc=devalias backup_root /pci@1f,0/pci@1/scsi@8/disk@1,0
Note
In the steps that follow, wherever you see "disk1" would be replaced with the alias you configured above.
Step 3
Before shutting down the system, check the progress of the mirroring to make sure that replication
is complete. Type the following the command to check the progress of the mirroring. An Okay response
means that disk mirroring is complete.
/usr/sbin/metastat
Warning
Step 4
DO NOT REBOOT until the replication is complete and the mirrors are in the Okay state.
When the replication is complete, bring the machine down to the boot prompt. Type the following
command and press Enter:
# /usr/sbin/shutdown -g0 -y -i0
Text similar to the following is displayed:
The system is coming down. Please wait.
System services are now being stopped.
.
.
.
The system is down.
.
.
.
Program terminated
ok
ok boot disk1
Res
LOM event: +0h5m53s host resetting
.
.
.
Executing last command: boot disk1
Boot device: /pci@1f,0/pci@1/scsi@8/disk@1,0 File and args:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
The machine should reboot from the second disk.
Step 5
Verify that the following text is displayed in the boot output (see the output in Step 4, above). This
ensures that the machine was working from the second drive:
Executing last command: boot disk1
Boot device: /pci@1f,0/pci@1/scsi@8/disk@1,0 File and args:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-35
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring a Second Disk Drive
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
This completes the procedures for rebooting from the mirrored (secondary) disk.
Removing the Solstice DiskSuite
Note
This section applies to the PGW Host running either the Cisco MGC or HSI software. The
following procedure only works from platforms that have been mirrored using the procedure provided
in the “Installing the Solstice DiskSuite (CSCOh016)” section on page 2-32.
This procedure un-mirrors the disk partitions and removes the DiskSuite application from the platform.
Use this procedure if a system has DiskSuite installed and you no longer wish to use CSCOh005 to
configure the second disk for the log and spool directories.
If the platform is configured with customer-specific information, be sure to back up this information
before the partitions are un-mirrored and DiskSuite is removed. Consult the appropriate document,
depending on the software installed.
Step 1
Log in as root. Use the metastat command to verify that the state of all the mirrors is Okay.
Step 2
Type the following commands to run the script and press Enter:
cd /opt/sun_install/DiskSuite
sh rm_disksuite_1.sh
The sh rm_disksuite_1.sh command detaches the mirrored disks and restores the original disk partition
file in /etc/vfstab. The machine reboots after detaching the mirrored disks and restoring the original disk
partition file.
Step 3
Log in as root and change directory to /opt/sun_install/DiskSuite. Enter the following command:
cd /opt/sun_install/DiskSuite
Step 4
Run the script sh ./rm_disksuite_2.sh:
sh ./rm_disksuite_2.sh
This script clears the disk mirrors and removes the DiskSuite software packages from the system.
This completes the DiskSuite removal.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-36
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
Installing the Log and Spool File Systems (CSCOh005)
Note
This section applies to the PGW Host running the Cisco MGC software.
Note
If the DiskSuite software is installed and configured, you must first follow the procedure in the
“Removing the Solstice DiskSuite” section on page 2-36 to remove the DiskSuite software before
configuring the second disk to be used for the Log and Spool File Systems.
To determine whether DiskSuite is installed and configured, run the /usr/sbin/metastat command. If the
command is found and it displays the status of mirrors, it indicates that DiskSuite is installed and
configured.
Note
For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names on Supported
Cisco MGC Software Platforms).
The following procedure configures the second disk of a PGW Host for use by the Cisco MGC software
as storage for log, alarm, measurement, and CDR files. The second disk is defined into two partitions,
as follows:
•
The first partition is the log partition and uses 40% of the disk.
•
The second partition is the spool partition that uses 60% of the disk.
Table 2-13 shows a sample partition table for the second disk of a Netra t 1400 with 36 GB disk drives.
Table 2-13
36 GB Disk 1 Partition Table (PGW with Log and Spool Package)
PGW Host
Slice No.
Note
Slice Name
Slice Size (GB)
0.
0.00
1
0.00
2
overlap
33.92
3
/opt/CiscoMGC/var/log
13.57
4
/opt/CiscoMGC/var/spool
20.35
5
0.00
6
0.00
7
0.00
If you have installed the Solaris 8 operating system on the platform with only one hard disk, shut down
the server and insert a second disk. Turn on the server and log in as root. Run the UNIX command,
/usr/sbin/shutdown -g0 -y -i0, to enter the OK mode. Then run the command, boot -rv, in OK mode to
detect the newly inserted hard disk.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-37
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
Step 1
Load the Cisco PGW Solaris 8 Patch CD into the CD-ROM drive. From the /var/tmp directory of the
target Netra machine, install the Log And Spool Software by entering the following command:
# cd /var/tmp
# pkgadd -d /cdrom/cdrom0/CSCOh005.pkg
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh005
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Type package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]
Step 2
Press Enter to accept the default answer all.
A screen similar to the following is displayed:
Processing package instance <CSCOh005 from </var/tmp/CSCOh005.pkg
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Cisco System, Inc.
Using </opt/sun_install as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh005> [y,n,?]
Step 3
Type y and press Enter to continue.
A screen similar to the following is displayed:
Installing Media Gateway Controller VSC log and spool package as <CSCOh005>
## Executing preinstall script.
Platform is SUNW,Ultra-80
This is a known platform
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/format_log_spool_start.cmd
/opt/sun_install/install_log_spool
/opt/sun_install/query_2nd_disk.cmd
[ verifying class <none> ]
## Executing postinstall script.
!!
!!
!!
!!
Step 4
You must now change directories to /opt/sun_install/Log_Spool and
run the ./install_log_spool script as root.
Change directory to /opt/sun_install/Log_Spool and run the install_log_spool script.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-38
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
Note
You must first shut down the Cisco MGC before running the install_log_spool script.
# cd /opt/sun_install/Log_Spool
# ./install_log_spool
A screen similar to the following is displayed:
Platform is SUNW,Ultra-80
Searching for disks...done
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
volname
!<cmd>
quit
format> disk
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
set 8-character volume name
execute <cmd>, then return
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@0,0
1. c0t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
Specify disk (enter its number): 1
selecting c0t1d0
[disk formatted]
format> current
Current Disk = c0t1d0
<SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
format> q
2nd Disk device is:
Disk type is:
Number of Cylinders :
c0t1d0
SUN36G
24620
Enter absolute path of the desired mount point for the
log directory or press enter to accept
the default [/opt/CiscoMGC/var/log]:
Step 5
If the PGW displays the following error message, you need to unmount the /opt/CiscoMGC/var/log and
/opt/CiscoMGC/var/spool directories.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If DiskSuite or StorEdge VM is running, it must be disabled
The second disk must not be mounted to run this script
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-39
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
Note
If the PGW does not display this error message, continue to the next step.
Enter the following commands to unmount the directories, and run the install_log_spool script again.
# umount /opt/CiscoMGC/var/log
# umount /opt/CiscoMGC/var/spool
Step 6
Press Enter to accept the default mount point for the log directory or change it if you plan on installing
the Cisco MGC software in a different location.
A screen similar to the following is displayed:
Log directory mount point is /opt/CiscoMGC/var/log
Enter absolute path of the desired mount point for the
spool directory or press enter to accept
the default [/opt/CiscoMGC/var/spool]:
Step 7
Press Enter to accept the default mount point for the spool directory or change it if you plan on installing
the Cisco MGC software in a different location.
A screen similar to the following is displayed:
Spool directory mount point is /opt/CiscoMGC/var/spool
Number of cylinders for log partition: 9848
Start: 0
Start: 9847
Number of cylinders for spool partition: 14772
Start: 9848
Start: 24619
Build partition table for c0t1d0 ...
Searching for disks...done
selecting c0t1d0
[disk formatted]
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> p
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
PARTITION MENU:
0
- change `0' partition
1
- change `1' partition
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-40
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
2
3
4
5
6
7
select
modify
name
print
label
!<cmd>
quit
partition> 0
Part
Tag
0
root
-
change `2' partition
change `3' partition
change `4' partition
change `5' partition
change `6' partition
change `7' partition
select a predefined table
modify a predefined partition table
name the current table
display the current table
write partition map and label to the disk
execute <cmd>, then return
Flag
wm
Cylinders
0 725
Size
1.00GB
Blocks
(726/0/0)
2097414
Enter partition id tag[root]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 1
Part
Tag
Flag
Cylinders
Size
Blocks
1
swap
wu
726 - 3629
4.00GB
(2904/0/0)
8389656
Enter partition id tag[swap]: unassigned
Enter partition permission flags[wu]: wm
Enter new starting cyl[726]: 0
Enter partition size[8389656b, 2904c, 4096.51mb, 4.00gb]: 0c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 0c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
3630 - 23156
26.90GB
0
Blocks
(19527/0/0) 56413503
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[3630]: 0
Enter partition size[56413503b, 19527c, 27545.66mb, 26.90gb]: 0c
partition> 5
Part
Tag
Flag
Cylinders
Size
Blocks
5
var
wm
23157 - 23882
1.00GB
(726/0/0)
2097414
Enter partition id tag[var]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23157]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 6
Part
Tag
Flag
Cylinders
Size
Blocks
6
usr
wm
23883 - 24608
1.00GB
(726/0/0)
2097414
Enter partition id tag[usr]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23883]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 7
Part
Tag
Flag
Cylinders
Size
Blocks
7 unassigned
wm
24609 - 24619
15.52MB
(11/0/0)
31779
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-41
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[24609]: 0
Enter partition size[31779b, 11c, 15.52mb, 0.02gb]: 0c
partition> 2
Part
Tag
Flag
Cylinders
Size
Blocks
2
backup
wm
0 - 24619
33.92GB
(24620/0/0) 71127180
Enter partition id tag[backup]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[71127180b, 24620c, 34730.07mb, 33.92gb]: 24620c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
0
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 9848c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
0
0
0
Blocks
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 9848
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 14772c
partition> p
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part
Tag
0 unassigned
1 unassigned
2 unassigned
3 unassigned
4 unassigned
5 unassigned
6 unassigned
7 unassigned
Flag
wm
wm
wm
wm
wm
wm
wm
wm
Cylinders
0
0
0 - 24619
0 - 9847
9848 - 24619
0
0
0
Size
0
0
33.92GB
13.57GB
20.35GB
0
0
0
Blocks
(0/0/0)
0
(0/0/0)
0
(24620/0/0) 71127180
(9848/0/0) 28450872
(14772/0/0) 42676308
(0/0/0)
0
(0/0/0)
0
(0/0/0)
0
partition> l
partition> q
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-42
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
quit
format> q
unknown disk type, assuming the speed is 10000 rpm
Build log filesystem at /dev/rdsk/c0t1d0s3 ...
mkfs -F ufs /dev/rdsk/c0t1d0s3 28450872 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s3:
28450872 sectors in 9848 cylinders of 27 tracks, 107 sectors
13892.0MB in 308 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
.
.
.
Build spool filesystem at /dev/rdsk/c0t1d0s4 ...
mkfs -F ufs /dev/rdsk/c0t1d0s4 42676308 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s4:
42676308 sectors in 14772 cylinders of 27 tracks, 107 sectors
20838.0MB in 462 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
.
.
.
Remove any existing entry in /etc/vfstab for c0t1d0s3 or c0t1d0s4
Adding entries to /etc/vfstab
Mounting /opt/CiscoMGC/var/log
Mounting /opt/CiscoMGC/var/spool
Success!!!
Note
After the Log and Spool File system is successfully installed, you must install the Cisco Security
Patch (CSCOh013) if it was removed before DiskSuite was removed. For installation
procedures, see “Installing the Cisco Security Package (CSCOh013)” section on page 3-16.
This completes the installation of the Log and Spool File system.
Uninstalling the Log and Spool File System
Do the following procedure if you need to remove the Log and Spool File system from the second disk.
Contact Cisco TAC if you need assistance (see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii).
Note
Step 1
You must be logged in as root to uninstall CSCOh005.
Type the following command at the # prompt and press Enter:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-43
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Log and Spool File Systems (CSCOh005)
cd /opt/sun_install/Log_Spool/
./uninstall_log_spool
Text similar to the following is displayed:
You are running as root - Good...
*** WARNING! LOG FILES WILL NOT BE SAVED ***
Uninstalling this package typically means that the log &
spool directories will be on the same disk as the rest of
the software so there is less space available for those
files. We will not save any existing log or spool files.
*** WARNING! LOG FILES WILL NOT BE SAVED ***
However, they are not being deleted - the log files will
still exist on the second (unmounted) disk drive
It is possible to manually mount that disk and recover
log files if necessary.
If you want to save log files before running this
script, then exit and do so now
Do you want to continue? (y/n) [N] y
Step 2
Type y and press Enter to remove CSCOh005. Text similar to the following is displayed:
Unmount /opt/CiscoMGC/var/log
Unmount /opt/CiscoMGC/var/spool
Update /etc/vfstab
Remove old files...
The Log/Spool software has been removed from the system
Now you can remove the package with the command:
pkgrm CSCOh005
Done!
Step 3
Type the following command and press Enter to continue the removal of CSCOh005.
pkgrm CSCOh005
Step 4
Reboot your machine with the -r option. Type the following command and press Enter:
# reboot -- –r
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
This completes the removal of the Log and Spool File system from the second disk.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-44
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Configuring Additional Ethernet Interfaces
Configuring Additional Ethernet Interfaces
The primary Ethernet interface is configured during the operating system installation. All additional
Ethernet interfaces must be configured separately.
Note
For Ethernet interface information for each platform type, refer to Table 2-2 on page 2-4 (Device Names
on Supported Cisco MGC Software Platforms).
To configure additional Ethernet interfaces:
Step 1
Add the IP address and hostname of the additional Ethernet interfaces to the /etc/hosts file by typing the
following command for each Ethernet port:
# echo IP_address hostname.deviceX >> /etc/hosts
Where:
•
IP_address—IP address of an additional Ethernet interface, expressed in dotted decimal notation.
•
hostname—Name of the host for the additional Ethernet interface.
•
deviceX—A combination of the Ethernet device type and the interface instance, such as hme1.
For example, to add an IP address, 172.24.237.52, for an Ethernet port, hme1, on a host called Madison
to the /etc/hosts file, you would enter the following command:
# echo 172.24.237.52 madison.hme1 >> /etc/hosts
Step 2
Create a new file to store the IP address or hostname for each additional Ethernet port by entering the
command listed below. Refer to Table 1-2 on page 1-3 (Site-specific Information) if you made notes
while preparing for the installation.
# echo IP_address > /etc/hostname.deviceX
Where:
•
IP_address—IP address of an additional Ethernet interface, expressed in dotted decimal notation,
or a hostname.
•
deviceX—Must match the value used in Step 1.
For example, to enter an IP address of 172.24.237.52 for a second Ethernet interface of hme1, you would
enter the following command:
# echo 172.24.237.52 > /etc/hostname.hme1
Step 3
Add a line to the /etc/netmasks file for each unique subnet of the interfaces being added by entering the
command listed below. Multiple subnets of the same network address should have individual lines in the
/etc/netmasks file.
# echo subnet_address subnet_mask >> /etc/netmasks
Where:
•
subnet_address—IP address of a subnet, expressed in dotted decimal notation.
•
subnet_mask—Subnet mask value, expressed in dotted decimal notation.
For example, to enter a subnet address of 172.24.237.0 with a subnet mask of 255.255.255.0, you would
enter the following command:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-45
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Alarm Software
# echo 172.24.237.0 255.255.255.0 >> /etc/netmasks
Step 4
The machine must now be rebooted with a -r option to complete the configuration. Enter the following
command:
# reboot -- -r
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 5
When the machine finishes rebooting, log in as root and type the command ifconfig -a. Verify that the
new Ethernet interfaces appear in the output.
# ifconfig -a
A screen similar to the following is displayed. IP addresses are for demonstration purposes only. Actual
addresses will differ in each application.
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 172.24.235.53 netmask ffffff00 broadcast 172.24.235.255
ether 8:0:20:9a:76:6c
hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 172.24.237.53 netmask ffffff00 broadcast 172.24.237.255
ether 8:0:20:9a:76:6c
The configuration of additional Ethernet interfaces is now complete. Proceed to “Installing the Alarm
Software” section on page 2-46.
Installing the Alarm Software
The driver for the alarm device is not part of the standard Solaris installation. It must be installed
separately.
If you are installing Solaris 8 on a Netra t 1120/1125, use the procedure in the “Alarm Card Software
Installation for Netra t 1120/1125” section on page 2-50 for alarm card software installation. For all
other platforms, use the procedure in the following section, “Installing Lights Out Management
Software”.
If you are installing Solaris 8 2/04 on a Sun Fire V210, Netra 240 or Netra 440 platform, there are no
separate alarm software packages to install because the alarm software is installed automatically. The
ALOM (Advance Lights Out Management) software for the Sun Fire V210, Netra 240, and Netra 440 is
integrated within the Solaris 8 Operating System. Therefore, previous SUN lights-out alarm packages
like "SUNWlomm" (on Sun Fire V120) and "SUNWtsalm" (on Netra 112X) do not exist on the Sun Fire
V210, Netra 240 and Netra 440 platforms. For additional information regarding lights-out alarms on the
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-46
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Alarm Software
Sun Fire V210, Netra 240 and Netra 440, refer to the SUN ALOM Guide at
http://www.sun.com/servers/alom.html. Proceed to the “Installing the Solaris 8 Patch Cluster
(CSCOh015)” section on page 2-51.
Note
If your system is using Sun Fire V210 platforms as PGW hosts, be aware that a log message indicating
that the LOM package has not been installed is generated every time you start the Cisco MGC software.
You can ignore this message. The message is similar to the following:
Tue Jan 31 12:10:44:936 2006 EST | AlarmManager (PID 4176) <Error>
MGMT_ERR_LOM_NOT_INSTALLED: The LOM package for NETRA not installed
For all other platforms, use the procedure in the following section, “Installing Lights Out Management
Software”.
Installing Lights Out Management Software
To install Lights Out Management software on the following platforms:
Step 1
•
Netra t 1400/1405
•
Netra t 100/105
•
Sun Fire V120
•
Netra 120
•
Netra 20
Load the Software Supplement for the Solaris 8 Operating Environment 10/01 CD-ROM into the
CD-ROM drive. Install the Lights out Management software by entering the following commands at the
# prompt.
# cd /cdrom/cdrom0/Netra_Lights_Out_Management_2.0/Product
# pkgadd -d .
A screen similar to the following is displayed along with copyright and trademark information:
The following packages are available:
1 SUNWlomm
LOMlite manual pages
(sparc) 2.0,REV=2000.08.22.14.14
2 SUNWlomr
LOMlite driver (root)
(sparc) 2.0,REV=2000.08.22.14.14
3 SUNWlomu
LOMlite Utilities (usr)
(sparc) 2.0,REV=2000.08.22.14.14
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to accept the default answer of all and install all the packages. A screen similar to the
following is displayed:
Processing package instance <SUNWlomm> from
</cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product>
LOMlite manual pages
(sparc) 2.0,REV=2000.08.22.14.14
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
Using </> as the package base directory.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-47
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Alarm Software
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
Installing LOMlite manual pages as <SUNWlomm>
## Installing part 1 of 1.
43 blocks
Installation of <SUNWlomm> was successful.
Processing package instance <SUNWlomr> from
</cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product>
LOMlite driver (root)
(sparc) 2.0,REV=2000.08.22.14.14
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWlomr> [y,n,?] y
Step 3
Type y and press Enter to continue the Netra t Lights Out Management installation. A screen similar to
the following is displayed:
Installing LOMlite driver (root) as <SUNWlomr>
## Installing part 1 of 1.
10 blocks
i.drivers: INFO: Starting ...
i.drivers: Adding
/cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platf
orm/sun4u/kernel/drv/lom
i.drivers: Adding
/cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platf
orm/sun4u/kernel/drv/lomp
i.drivers: Adding
/cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platf
orm/sun4u/kernel/drv/sparcv9/lom
i.drivers: Adding
/cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product/SUNWlomr/reloc/platf
orm/sun4u/kernel/drv/sparcv9/lomp
Identified drivers: lom lomp lom lomp
i.drivers: Installing drivers ...
Driver: lom ... devlinks ... add_drv(1M) ...
Driver: lomp ... devlinks ... add_drv(1M) ...
Driver: lom ... devlinks ... add_drv(1M) ...OK ...
Driver: lomp ... devlinks ... add_drv(1M) ...OK ...
i.drivers: Finished
[ verifying class <drivers> ]
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-48
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Alarm Software
Installation of <SUNWlomr> was successful.
Processing package instance <SUNWlomu> from
</cdrom/solaris8_1000_suppcd/Netra_t_Lights_Out_Management_2.0/Product>
LOMlite Utilities (usr)
(sparc) 2.0,REV=2000.08.22.14.14
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
Installing LOMlite Utilities (usr) as <SUNWlomu>
## Installing part 1 of 1.
337 blocks
Installation of <SUNWlomu> was successful.
The following packages are available:
1 SUNWlomm
LOMlite manual pages
(sparc) 2.0,REV=2000.08.22.14.14
2 SUNWlomr
LOMlite driver (root)
(sparc) 2.0,REV=2000.08.22.14.14
3 SUNWlomu
LOMlite Utilities (usr)
(sparc) 2.0,REV=2000.08.22.14.14
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: q
Step 4
Type q and press Enter when the Netra t Lights Out Management installation has completed.
Step 5
Eject the CD from the CD-ROM drive by entering the following commands:
# cd /
# eject
Step 6
The machine must now be rebooted. Enter the following command:
# reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 7
When the machine finishes rebooting, log in as root.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-49
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Alarm Software
The Lights Out Management installation is now complete. Proceed to “Installing the Solaris 8 Patch
Cluster (CSCOh015)” section on page 2-51
Alarm Card Software Installation for Netra t 1120/1125
To install the alarm card software:
Step 1
Load the Software Supplement for the Solaris 8 Operating Environment 10/01 CD into the CD-ROM
drive and enter the following commands:
# cd /cdrom/cdrom0/Netra_t11xx_Alarms_2.0/Product
# pkgadd -d .
A screen similar to the following is displayed:
The following packages are available:
1 SUNWtsalm
TS91 Alarm and Monitor manual pages
(sparc.sun4u) 1.1.0,REV=1999.07.26.14.37
2 SUNWtsalr
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.1.0,REV=1999.07.26.14.37
3 SUNWtsalu
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.1.0,REV=1999.07.26.14.37
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to install all the packages.
A screen similar to the following is displayed:
Processing package instance <SUNWtsalm from </cdrom/netrat_11xx_1_0
TS91 Alarm and Monitor Manpages
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Copyright 1997 Sun Microsystems Inc. Tous droits reserves.
Fabrique aux Etats-Unis, 2550 Garcia Avenue, Mountain View, California
94043-1100 USA
...
Installing TS91 Alarm and Monitor Manpages as <SUNWtsalm
...
Installation of <SUNWtsalm was successful.
Processing package instance <SUNWtsalr from </cdrom/netrat_11xx_1_0
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Do you want to continue with the installation of <SUNWtsalr [y,n,?]
Step 3
Type y and press Enter to continue the installation. A screen similar to the following is displayed:
Installing TS91 Alarm and Monitor driver as <SUNWtsalr
...
Installation of <SUNWtsalr was successful.
Processing package instance <SUNWtsalu from </cdrom/netrat_11xx_1_0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-50
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Solaris 8 Patch Cluster (CSCOh015)
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
...
Installation of <SUNWtsalu was successful.
The following packages are available:
1
SUNWtsalm
2
SUNWtsalr
3
SUNWtsalu
TS91 Alarm and Monitor Manpages
(sparc.sun4u) 1.0,REV=1.1
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.0,REV=1.1
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.0,REV=1.1
Type package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 4
Enter q to quit the installation when it has completed.
Step 5
Eject the CD from the CD-ROM drive.
# cd /
# eject
Step 6
The machine must now be rebooted. Enter the following command:
# reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 7
When the machine finishes rebooting, log in as root.
This completes the Alarm Card software installation. Proceed to “Installing the Solaris 8 Patch Cluster
(CSCOh015)” section on page 2-51.
Installing the Solaris 8 Patch Cluster (CSCOh015)
Caution
You must back up your system prior to installing the Solaris 8 Patch Cluster (CSCOh015). If you do not
back up and your disk is too full when you install this software, the script may fail and corrupt your disk.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-51
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Solaris 8 Patch Cluster (CSCOh015)
Caution
Make sure that no earlier version of the Solaris 8 Patch Cluster (CSCOh015) is installed on the system,
otherwise the installation of the latest version of CSCOh015 may fail.
Note
Removing the Solaris 8 Patch Cluster (CSCOh015) does not remove the Solaris patches that were
installed when the /opt/sun_install/installPatches8 was executed during a previous patch installation.
However, if you install the package CSCOh015 and it contains a newer version of previously-installed
Solaris patches, the new version will supersede the older version. The older patches will remain on the
system, but stay inactive unless the newer patches are removed.
To determine the Solaris patch version in your system, use the command showrev -p. This command
will show both the old and new patch versions.
Note
Install the Solaris 8 Patch Cluster (CSCOh015) after Solaris DiskSuite and LOM software are installed
because some patches in CSCOh015 apply to DiskSuite and LOM.
To install the Solaris 8 Operating System Patch Cluster (CSCOh015):
Step 1
If you are installing using the CD-ROM, load the Cisco Solaris 8 Patches CD into the CD-ROM drive.
Enter the following command:
# pkgadd -d /cdrom/cdrom0/CSCOh015.pkg
Step 2
Press Enter to accept the default response of all and continue. A screen similar to the following is
displayed:
Processing package instance <CSCOh0015> from </var/tmp/CSCOh0015.pkg>
Media Gateway Controller Solaris 8 Patch Cluster
(sparc) 1.0(3)
Cisco System, Inc.
The selected base directory </opt/sun_install> must exist before
installation is attempted.
Do you want this directory created now [y,n,?,q] y
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
* /opt/sun_install <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q] y
Step 3
Type y and press Enter to continue. A screen similar to the following is displayed:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-52
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the Solaris 8 Patch Cluster (CSCOh015)
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh015> [y,n,?] y
Step 4
Type y and press Enter to continue. A screen similar to the following is displayed:
Installing Media Gateway Controller Solaris 8 Patch Cluster as <CSCOh0015>
The system lists the patches that it will install. This list will vary over time. A screen similar to the
following is displayed:
….
## Executing postinstall script.
****************************************************
*
You must now change directories
*
*
to /opt/sun_install and run
*
*
./installPatches8
*
****************************************************
Installation of <CSCOh0015> was successful.
Step 5
Change directory to /opt/sun_install and run the installPatches8 script by entering the following
commands:
# cd /opt/sun_install
# ./installPatches8
Note
During the installation of the Solaris 8 patch cluster, some patches will fail with return codes 2,
8, and 35. This is normal and does not indicate a problem with the installation. The following is
an explanation of these error codes:
2 - Attempting to apply a patch that is already applied.
8 - Attempting to patch a package that is not installed.
35 - A later version of the patch has already been installed.
A screen similar to the following is displayed:
*** InstallPatches8 begins Wed Jan 10 13:50:50 EST 2001 ***
Platform is SUNW,Ultra-80
Changed to /var/tmp directory
… Patches will be installed and logged.
*** InstallPatches8 ends Wed Jan 10 13:58:12 EST 2001 ***
*************************************************
*
It is necessary to reboot this machine
*
*
for these patches to be incorporated into *
*
the operating system. Enter the following
*
*
command and press Enter: reboot -- -r
*
*************************************************
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-53
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the BAMS Disk Array on a Netra t 140x Host
Step 6
The Solaris 8 patch cluster installation is complete. Reboot the target machine.
Note
If you used the CD-ROM drive to load the Solaris 8 patch cluster, eject the CD prior to rebooting.
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
This completes the Solaris 8 Patch cluster installation procedure.
For PGW Hosts: The Cisco MGC software can now be loaded.
For HSI: The HSI software can now be loaded.
For BAMS: If your BAMS host is a Netra t 1400/1405 and you are using a Disk Array, proceed to the
“Installing the BAMS Disk Array on a Netra t 140x Host” section on page 2-54. Otherwise, the BAMS
software can now be loaded.
Caution
Do not install the Solaris patch CSCOh005 on the BAMS server.
Installing the BAMS Disk Array on a Netra t 140x Host
This section only applies to a BAMS Disk Array Installation for a Netra t 1400/1405.
Raid hardware should be installed according to Sun manuals – PCI UltraSCSI Host Adapter Installation
Guide, Part #805-1271-10 and Netra st A1000 and Netra st D1000, Installation and Maintenance
Manual, Part # 805-7147-12.
Note
Solaris 8 should be installed on the primary disk with the partition information described in Table 2-3
on page 2-22, Table 2-5 on page 2-23, or Table 2-7 on page 2-24.
Make sure the Solaris 8 recommended patches are installed (Cisco package CSCOh015.pkg).
Reboot the system.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-54
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the BAMS Disk Array on a Netra t 140x Host
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Installing the RAID Manager Software
Solaris 8 requires the Sun Raid Manager Software 6.22.1. If this is not the version shipped to you, then
download rm6221-fsc-sparc-bin.zip from SunSolve at sun.sunsolve1.com. Newer units may have the
proper version shipped with the RAID module.
Note
Currently, all patches required for Raid Manager 6.22.1 are included in the Solaris 8 07/01 and later
releases, as well as the Cisco Patch package CSCOh015.
After the Raid Manager is installed, you must reboot the system.
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Configuring the RAID Module
Updating firmware, configuring LUNs and monitoring the RAID module are done using the Raid
Manager GUI software, Sun StorEdge RAID Manager 6.22.1, and Sun StorEdge 6.22 Installation and
Support Guide for Solaris (Part # 805-756-10). The GUI for Raid Manager is started with the following
command:
/usr/lib/osa/bin/rm6
Note
There is no CLI available to configure the RAID module. To configure the RAID module remotely over
the network, you must access the Sun box through a graphic adapter and a monitor.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-55
Chapter 2
Sun Solaris 8 Operating System Installation
Installing the BAMS Disk Array on a Netra t 140x Host
Verifying/Upgrading Firmware
Check and update the RAID Module firmware as required. If the firmware is not at least version 3.0, it
will need to be updated. Refer to the Installation and Support Manual, page 44, for installation
instructions, and page 122 for the correct version information. Perform a RAID Module health check
after the firmware is upgraded. Refer to the Installation and Support Manual, page 48, for health check
procedures.
Configuring LUNs
The array should be configured with 2 LUNs. LUN0 should consist of three 36 GB drives and be
configured with RAID 0 format. It will be used for /opt/CiscoBAMS/CDR/archive. LUN1 should be
configured with five 36 GB drives and be configured with RAID 0. It will be used for
/opt/CiscoBAMS/data.
You should first delete existing LUNs (refer to page 44 of the User Guide). Create new LUNs (refer to
page 69 of the User Guide). The configuration should be set up as listed above.
Note
Do not exit the configuration without creating at least LUN 0. If you exit without creating LUN 0, you
will not be able to access the RAID module!
After LUNs have been created, perform a health check using the GUI Recovery Guru/Health Check
Menu. This function should pass without any errors. For information, see page 48 of the Installation and
Support Manual.
Verifying the RAID Module
When the RAID module is configured, verify that there are 2 LUNs and check the disk sizes.
Note
Step 1
For the device names for each platform type, refer to Table 2-2 on page 2-4 (Device Names on Supported
Cisco MGC Software Platforms).
Use the following command and verify that you have 2 LUNs and check the approximate disk sizes
(shown in the text display):
/usr/lib/osa/bin/raidutil -c c1t5d0 -I
Text similar to the following is displayed:
LUNs found on c1t5d0
LUN 0
RAID 0
104077 MB
LUN 1
RAID 0
173463 MB
Vendor ID
Symbios
ProductID
StorEDGE A1000
Product Revision 0205
Boot Level
03.01.04.00
Boot Level Date
04/05/01
Firmware Level
03.01.04.68
Firmware Date
06/22/01
Raidutil succeeded!
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-56
OL-1150-15
Chapter 2
Sun Solaris 8 Operating System Installation
Troubleshooting
Step 2
Make file systems on LUNs. Check the file systems and make mount points for disk volumes. Modify
the /etc/vfstab file and mount new disk volumes.
Step 3
Make the file system for /opt/CiscoBAMS/CDR/archive. Enter the following command:
newfs /dev/rdsk/c1t5d0s6
Step 4
Make the file systems for /opt/CiscoBAMS/data. Enter the following command:
newfs /dev/rdsk/c1t5d1s6
Step 5
Check the file systems. Enter the following commands:
fsck -y /dev/rdsk/c1t5d0s6
fsck -y /dev/rdsk/c1t5d1s6
Step 6
Make the mount points for the RAID volumes. Enter the following commands:
mkdir /opt/CiscoBAMS/data
mkdir /opt/CiscoBAMS/CDR/archive
Step 7
Add entries to /etc/vfstab for new RAID volumes. Enter the following commands:
echo “/dev/dsk/c1t5d0s6 /dev/rdsk/c1t5d0s6 /opt/CiscoBAMS/CDR/archive
/etc/vfstab
echo “/dev/dsk/c1t5d1s6 /dev/rdsk/c1t5d1s6 /opt/CiscoBAMS/data
-“ >> /etc/vfstab
Step 8
ufs 2
yes - “ >>
ufs
2
yes
Mount the RAID volumes. Enter the following command:
mount -a
This completes the RAID module configuration.
Troubleshooting
Netra t 10x
Symptom:
Netra t 10x will not boot from the CD-ROM.
Solution:
At the ok prompt, type set-defaults to reset the OpenBoot PROM. Be sure to enter the environment
variable settings shown in Installing the Solaris 8 Operating System, page 2-15, Step 28, at the end of
the installation procedure.
Swap File Size Input
Symptom:
Installation program does not accept swap file size input.
Solution:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
2-57
Chapter 2
Sun Solaris 8 Operating System Installation
Troubleshooting
If the target machine does boot to the hard disk drive, use the format command to delete the existing
partitions.
If the target machine does not boot to the hard disk drive, boot from the CD-ROM by typing
boot cdrom -s at the ok prompt. Follow the instructions to reformat the disk. This procedure takes
approximately 1.5 hours.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
2-58
OL-1150-15
CH A P T E R
3
Cisco MGC Software Release 9 Installation
This chapter describes how to install Releases 9.2(x) and later releases of the Cisco Media Gateway
Controller (MGC) software.
Note
In Release 7.4 and later, the Cisco MGC software files and processes are located in the /opt/CiscoMGC
directory.
This chapter contains the following sections:
Note
•
Before You Start, page 3-1
•
Cisco MGC Software Installation/Uninstallation Sequence, page 3-3
•
Installing the Cisco MGC Software 9.2(x) and Higher Releases, page 3-3
•
Installing the Cisco Security Package (CSCOh013), page 3-16
•
Verification Test Suite (VTS) Package (CSCOh014) Overview, page 3-22
For information on configuring the Cisco MGC software, see the following publication:
Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Before You Start
Before you start, perform the following steps:
1.
Review the hardware and software requirements found in the document Release Notes for the
Cisco Media Gateway Controller Software Release 9.
2.
Have your company's internal support and Cisco support contact information readily available so
you can get help with the installation if needed. (If you have questions or need assistance, see the
“Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii of the
Cisco support contact information.)
3.
Ensure that you have access to the console port on your Cisco MGC host.
4.
Before you begin installing the Cisco MGC software, make sure the Sun Operating System is
properly installed. The following table provides the location of the installation procedure you may
require.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-1
Chapter 3
Cisco MGC Software Release 9 Installation
Before You Start
Table 3-1
Installation Overview and Reference Sections
Installation Procedure
Refer to...
If the Sun Solaris 8 operating system is not yet
installed, you must first install it...
Start with Chapter 2, “Sun Solaris 8 Operating
System Installation.”
If the Sun Solaris 8 operating system is already
installed and you are installing the Cisco MGC
software for the first time...
Follow the procedures found in the “Installing the
Cisco MGC Software 9.2(x) and Higher
Releases” section on page 3-3.
Cautions, Notes, and Tips
Caution
To prevent the system from running out of disk space during installation and to avoid removal of data
files and databases to compensate, you must first verify that there is enough hard disk space to support
your intended installation. To get free space, you can delete the following files:
- Unnecessary log files (platform*.log)
- User-generated trace files (*.btr)
- Call detail record (CDR) files (.bin or .csv)
- Old *.tar files
- User-generated toolkit files (in the /var/cust_specific/toolkit directory)
Caution
Make sure to follow the Cisco MGC software installation and uninstallation sequence listed in “Cisco
MGC Software Installation/Uninstallation Sequence” section on page 3-3.
Note
For the software to work properly, you must reboot the system every time you modify any file in the /etc
directory.
Note
Monitor system output frequently for error messages during the installation process and correct any error
conditions before continuing with the installation.
Tip
Allow for at least 2 hours to install the Sun Solaris 8 operating system and approximately 1 hour to install
the Cisco MGC software.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-2
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Cisco MGC Software Installation/Uninstallation Sequence
Cisco MGC Software Installation/Uninstallation Sequence
Note
At this point, the Solaris Operating System 8 and Solaris Operating System 8 patch cluster package
(CSCOh015) should be already installed on your system.
For the system to work properly, it is important that Cisco MGC software installation be performed in
the following order:
1.
Cisco MGC software
2.
Solaris System Security Patch (CSCOh013)
Caution
Software must be uninstalled in the reverse order in which it is installed. For example, you must first
uninstall software package CSCOh013 before you uninstall the Cisco MGC software.
Note
You do not have to uninstall the Cisco MGC if only software package CSCOh013 requires updating but
the Cisco MGC does not.
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Note
For a sample output listing from the install.sh script, see Appendix D, “Sample Output from install.sh”
section on page D-1.
Note
Remove /usr/ucb from the path environment variable before the initial installation of the Cisco MGC
software. However, if /usr/ucb is needed, make sure that it is located in the path variable in the user
profile after /usr/sbin.
Note
To enable the SIP Improved Failover Support feature, both PGW 2200 systems must be in same VLANs.
A trunk line between the two switches must be connected and configured for the SIP Improved Failover
Support feature to work. However, if SIP Improved Failover Support is not required on your system,
then the trunk line is not mandatory.
Installing on a Simplex System
To install the Cisco MGC software, complete the following steps:
Step 1
Log in as root.
Step 2
Load the Cisco MGC software CD into the CD-ROM drive.
Step 3
To install the Cisco MGC software, enter the following commands:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-3
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
# cd /cdrom/cdrom0
# ./install.sh
The following prompt is displayed:
Use supplied admin file for unattended install? [n] [y,n,?,q]
Step 4
Answer y to perform an unattended installation. If you answer n, you must answer prompts and press
Enter for each package that is installed.
The following prompt is displayed:
Base directory for Toolkit (default /opt/Toolkit) [?,q]
##########################################################################################
#
# The CSCOgu000 utilities package must be installed prior to other components
#
# but has not been detected on your system. This package contains all required system
#
# parameters necessary for installing the rest of your software. If you do not install
#
# this package, the installation script will exit.
#
##########################################################################################
Would you like to install it now? [y] [y,n,?,q] y
Step 5
Answer y if you want to install the Toolkit application on this host.
Step 6
The following prompt is displayed:
Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q]
Enter CiscoMGC user name [mgcusr]
Enter CiscoMGC UID [20000]
Enter CiscoMGC group name [mgcgrp]
[mgcgrp] group already exists - continuing
[mgcusr] user added
Modifying /etc/init.d/inetinit name is non-existent for this module for a list of valid
names, use name'?'
We recommend that you accept the default values (by pressing Enter). You can, however, specify a
different user ID and a group ID. If the ID you specify already exists on the system, the corresponding
ID will be determined and reused, or you will be prompted to enter another ID.
Caution
No validation is performed on the IDs you enter. If you enter an invalid ID, the utilities
package does not add any accounts.
The system returns the following message, stating that the CSCOgu000 utilities package was
successfully installed:
Installation of <CSCOgu000> was successful.
(c)1998 Cisco Systems, Inc. All Right Reserved. Unpublished -- rights reserved under the
copyright laws of the United States. RESTRICTED RIGHTS LEGEND. Use, duplication, or
disclosure by the Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS
252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software -Restricted Rights at 48 CFR 52.227-19, as applicable. Cisco Systems, Inc. 3615 Dulles
Technology Drive Herndon, VA 20171
Step 7
Depending on your system configuration, rebooting after a successful utilities package installation might
not be necessary.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-4
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Note
Rebooting may take approximately 5 minutes.
If a reboot is not required, the installation continues uninterrupted.
If a reboot is required, perform the following steps when prompted:
a.
Type the following command displayed on the screen and press Enter.
# shutdown -y -g0 -i6
Note
If the command shown on the screen does not work, you can enter the /usr/sbin/reboot
command to reboot the system.
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
b.
After the reboot finishes, restart install.sh to install the remaining packages. To restart install.sh,
type the following commands at the # prompt and press Enter:
# cd /cdrom/cdrom0
# ./install.sh
The following prompts are displayed:
Use supplied admin file for unattended install? [n] [y,n,?,q]
c.
Note
Type y and press Enter.
This procedure can take approximately an hour to complete.
Text similar to the following is displayed, showing the packages that were installed:
Installation of <CSCOga000> was successful.
Uncompressing EISUP
Uncompressing ISDNIP
Uncompressing ISDNL3
Uncompressing LogServerd
Uncompressing MGCP
Uncompressing SIP
Uncompressing SS7
Uncompressing TALI
Uncompressing TCAP
Uncompressing almM
Uncompressing amDmpr
Uncompressing cdrDmpr
Uncompressing cfgM
Installing chk_inv
Uncompressing cms
Uncompressing converter
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-5
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Uncompressing engine.no_smartalloc
Uncompressing engine.smartalloc
Uncompressing foverd
Uncompressing ioChanMgr
Uncompressing measMgr
Uncompressing mmBldCfg
Uncompressing mmdbd
Uncompressing mml
Uncompressing pom
Uncompressing procM
Uncompressing replicator
Installing libACE.so
Uncompressing lib_cmg.so
Uncompressing lib_cxn.so
Uncompressing lib_eng.so
Uncompressing lib_rmg.so
Installing libcms.so
Uncompressing libconvutil.so
Uncompressing libda.so
Uncompressing libmmdb.so
Uncompressing libpolbase.so
Uncompressing libpolcomp.so
Uncompressing libpolfiles.so
Uncompressing libpolnuman.so
Uncompressing libpolroute.so
Uncompressing libpom.so
Uncompressing libpxe.so
Uncompressing libpxelog.so
Uncompressing librudp.so
Uncompressing libsa.so
Installing libsunmath.so.1
Installing libtten.so
Uncompressing libxe.so
Updating parameters for CiscoMGC
Updating parameters for SW_Layout.cfg
Updating parameters for getConfig
Updating parameters for log_rotate.sh
Updating parameters for startAudit.sh
Updating parameters for diagdata
Updating parameters for .cshrc
Updating parameters for .dump-prov
Updating parameters for .master.cks
Updating parameters for actDPlan
Updating parameters for backup.sh
Updating parameters for cdbscript.sh
Updating parameters for config-lib
Updating parameters for diskmonitor.sh
Updating parameters for failover_nfs.sh
Updating parameters for getDPlan
Updating parameters for init.tcl
Updating parameters for listDPlan
Updating parameters for mgcbackup
Updating parameters for mgcrestore
Updating parameters for migrateDPlan.sh
Updating parameters for pmctrl
Updating parameters for reconfig-all.mml
Updating parameters for restore.sh
Updating parameters for rmsem.sh
Updating parameters for startAudit.mml
Updating parameters for startLogServer
Updating parameters for stop-all
Installing /opt/CiscoMGC/man/mml.help.tar.gz
Installation of <CSCOga001> was successful.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-6
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Modifying /etc/syslog.conf
Updating parameters for .odbc.ini
Updating parameters for backupDb.sh
Updating parameters for restoreDb.sh
Preparing to install TimesTen4.1 in /opt on va-jupiter
Executing TimesTen installation script...
Installing 32-bit version...
Of the three components:
[1] TimesTen Client/Server and Data Manager
[2] TimesTen Data Manager Only
[3] TimesTen Client Only
Begin installing in /opt/TimesTen4.1 ...
Creating /opt/TimesTen4.1 ...
Uncompressing...
The TimesTen Demo applications can take up to 64 Mbytes of
disk space. Depending on
how your system is configured, you may not want to create the
DemoDataStore directory in the default location :
/var/TimesTen/TT4.1/32/DemoDataStore
Creating /var/TimesTen/TT4.1/32/DemoDataStore ...
System logging appears to be configured correctly.
(TimesTen syslog messages seem to be recorded in the file
'/var/adm/messages')
Starting the daemon ...
Installing TimesTen Server...
Installing TimesTen Server startup/shutdown scripts...
The TimesTen Server has started successfully.
Creating new /var/TimesTen/sys.ttconnect.ini
Creating /opt/TimesTen4.1/doc ...
Extracting /opt/ttdb-install/doc/doc.tar ...
End of TimesTen installation.
TimesTen installation script returned status 0
Program complete
Restoring backup schema.
Sun Microsystems Inc.SunOS 5.8GenericFebruary 2000
Restoring database contents for DSN=howdydb from
/opt/CiscoMGC/etc/export.ttdb
Restoring file /opt/TimesTen4.1/datastore/howdydb.ds0 from backup
Restoring file /opt/TimesTen4.1/datastore/howdydb.log0 from backup
The restore process is being initiated
Restore complete
Installation of <CSCOga002> was successful.
smpd.cnf up to date, no configuration upgrade required
Uncompressing mmSAgt
Uncompressing sagt
Uncompressing libsa.so
Updating parameters for CiscoMGC
Updating parameters for snmpd
Updating inittab
Installation of <CSCOga003> was successful.
Installing /opt/Toolkit/Packages/Packages.tar.gz
Installing /opt/Toolkit/bytecode/XECfg/XECfg.tar.gz
Installing /opt/Toolkit/bytecode/am/am.tar.gz
Installing /opt/Toolkit/bytecode/cdr/cdr.tar.gz
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-7
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Installing /opt/Toolkit/bytecode/log/Viewer.tar.gz
Installing /opt/Toolkit/bytecode/toolbar/toolbar.tar.gz
Installing /opt/Toolkit/bytecode/tv/tv.tar.gz
Installing /opt/Toolkit/gif/gif.tar.gz
Installing /opt/Toolkit/mibs/common/common.tar.gz
Installing /opt/Toolkit/tcl/tcl.tar.gz
Updating parameters for MGC_Setup
Updating parameters for MGC_Toolkit
Updating parameters for init.tcl
Updating parameters for toolbar.sh
Setting VERSION=9.2(2) in version.dat
Installation of <CSCOga004> was successful.
Installing ca
Installing callver
Installing get_trc.sh
Installing sim
Installing simWriter
Installing siptool
Installing sp
Installation of <CSCOgt001> was successful.
Updating parameters for XECfgParm.dat
Updating parameters for trigger.template
Updating parameters for migrate
Updating parameters for migrateTKGFile
Installing /opt/CiscoMGC/etc/CONFIG_LIB/migrate_mod.tar.gz
Installing /opt/CiscoMGC/etc/migrate/migrate_scr.tar.gz
Migrating .dat files in /opt/CiscoMGC/etc
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.dialPlan
Backing up dialPlans
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.bin
Backing up binary dialplans
Backing up .dat file
Backing up database
Sun Microsystems Inc.SunOS 5.8GenericFebruary 2000
migrate_XECfgParm: setting *.transpathId = 01
migrate_XECfgParm: setting *.ownTranspathId = 01
migrate_XECfgParm: setting *.peerTranspathId = 02
migrate_XECfgParm: setting *.MGC_CDR_NODE_ID = MGC-CDR-NODE-STRING
migrate_XECfgParm: setting foverd.conn1Type = socket
migrate_XECfgParm: setting foverd.conn2Type = socket
migrate_XECfgParm: setting *.IP_Addr1 = 10.1.0.16
migrate_XECfgParm: setting *.IP_Addr2 = 10.129.0.16
migrate_XECfgParm: setting *.IP_Addr3 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr4 = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrLocalA = 10.1.0.16
migrate_XECfgParm: setting *.ipAddrLocalB = 10.129.0.16
migrate_XECfgParm: setting *.ipAddrPeerA = 10.1.0.17
migrate_XECfgParm: setting *.ipAddrPeerB = 10.129.0.17
migrate_XECfgParm: setting *.SysConnectDataAccess = true
migrate_XECfgParm: setting *.SysConnectDataAccess = true
migrate_XECfgParm: setting foverd.abswitchPort = /dev/null
migrate_XECfgParm: setting foverd.ipLocalPortA = 1050
migrate_XECfgParm: setting foverd.ipLocalPortB = 1052
migrate_XECfgParm: setting foverd.ipPeerPortA = 1051
migrate_XECfgParm: setting foverd.ipPeerPortB = 1053
migrate_XECfgParm: setting replicator.portDataChannelSend = 2968
migrate_XECfgParm: setting replicator.portDataChannelRecv = 2970
migrate_XECfgParm: setting replicator.portCommChannelSend = 2972
migrate_XECfgParm: setting replicator.portCommChannelRecv = 2974
migrate_XECfgParm: setting *.SyscheckpointEnabled = true
migrate_XECfgParm: setting *.desiredPlatformState = master
migrate_XECfgParm: setting *.stPort = 7000
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-8
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
migrate_XECfgParm:
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
setting
pom.dataSync = true
*.chkPtPort = 2001
engine.SysPropagateChanAvail = false
engine.SysGeneratedCode = true
engine.SysGRSTimerInterval = 0
engine.SysGRSBlockSize = 0
engine.AuditTimerInterval = 1000
engine.MaxAuditCics = 32
engine.StartUpAuditEnabled = false
engine.SysVirtualSwitch = 1
engine.SysMdlMemoryReduction = 1
engine.CALL_MEM_BLOCK_SIZE = 0
engine.CALL_MEM_CHUNK_SIZE = 0
*.ClearingLocation = 0
engine.MDLANumberScreening = 0
*.DefaultLocation = 0
*.detailedCallEventCapture = 1
*.DataBaseAccessError = 0
*.SelectTermCustGrpId = 0
diskmonitor.Limit = 7
diskmonitor.Threshold = 80
diskmonitor.SoftLimit = false
diskmonitor.CdrRmFinished = 0
diskmonitor.CoreRmDays = 1
diskmonitor.CfgRmDirs = 64
*.logPrio = Error
*.logDirectory = ../var/log
*.logFileNamePrefix = platform
engine.CDRencodingFormat = AnsiCDB
engine.CDRtimeStamp = S
engine.CDRmessageTypes =
"1010,1020,1030,1040,1050,1060,1070"
migrate_XECfgParm: setting *.numberOfThreads = 2
migrate_XECfgParm: setting *.dataSourceName = howdydb
migrate_XECfgParm: setting *.maxNumLinks = 32
migrate_XECfgParm: setting *.maxLinksPerSessionSet = 4
migrate_XECfgParm: setting *.maxNumDChansPerIOCC = 504
migrate_XECfgParm: setting *.maxNumMGCPLinks = 1000
migrate_XECfgParm: setting *.GWClearChannelAlgorithm = null
migrate_XECfgParm: setting *.CallCutoffTimer = 0
migrate_XECfgParm: setting *.CPUTimerInterval = 3000
migrate_XECfgParm: setting *.dataCommitTime = 10
migrate_XECfgParm: setting ioChanMgr.sessionPauseTimer = 8
migrate_XECfgParm: setting ioChanMgr.resumeAckTimer = 1
migrate_XECfgParm: setting MML.timeout = 10000
migrate_XECfgParm: setting *.OverdecadicDigitsSupported = false
migrating XECfgParm.dat ...
starting migration ...
source and destination versions are the same, no need to migrate
copying files from source to destination
No data file changes required to support CMS
trigger.dat exists: not overwriting with trigger.template
Installation of <CSCOgc001> was successful.
The following prompt is displayed:
Would you like to add a protocol set to your system? [y]
[y,n,?,q] y
Step 8
Select y to add a protocol set.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-9
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Note
The protocols that you select are specific to your system requirements. These should be decided prior to
installation.
The following prompt is displayed:
Please insert a two digit package identifier and type <enter>
If you choose to add all protocols to your system, type "all": <package identifier>
Step 9
You can do either of the following:
a.
Type all and press Enter to add all the protocols to your system. If you do, more disk space will be
used and the installation process will take some time.
b.
For Cisco MGC Software Release 9.3(x) and later releases: Select the specific protocol(s) you need
from the following table (instead of selecting all) and enter the protocol identifier(s).
###################################
##
01
##
02
##
###################################
## BTNUP_BTNR167 ## IETF_SIP ##
## BTNUP_IUP
##
##
##
##
##
##
##
##
##
##
##
##
##
##
###################################
SS7 Protocol Family PRI Protocol Family
######################## ####################
##
10
## ## 20
##
######################## ####################
## ANSISS7_92
## ## ATT_41459
##
## ANSISS7_C2
## ## ATT_41459_C2
##
## ANSISS7_C3
## ## BELL_1268
##
## ANSISS7_STANDARD
## ## BELL_1268_C2
##
## GR317
## ## ETS_300_102
##
## GR317_C2
## ## ETS_300_102_C2 ##
## GR317_C3
## ## ETS_300_172
##
######################## ####################
Q761 Version 1 Protocol Family
##########################################################################################
##
30
##
31
##
32
##
33
##
##########################################################################################
## ETS_300_121
## Q761_BASE
## Q761_GERMAN
## Q761_SINGAPORE
##
## ETS_300_356
## Q761_BELG
## Q761_INDIA
## Q761_SINGAPORE_C2
##
## HONGKONG
## Q761_BELG_C2 ## Q761_KOREAN
## Q761_TAIWAN
##
## ISUPV1_POLI
## Q761_BELG_C3 ## Q761_NEWZEALAND
## Q761_THAILAND
##
## Q761_ARGENTINA
## Q761_CHILE
## Q761_97VER_BASE
## Q761_MALAYSIAN
##
## Q761_ARGENTINA_C2## Q761_CHINA
## Q761_PERU
##
##
## Q761_AUSTRL
## Q761_CHINA_C2 ## Q761_PORTUGAL
##
##
## Q761_AUSTRL_C2
## Q761_DANISH
##
##
##
##########################################################################################
Q761 Version 2 Protocol Family
###############################################
##
40
##
41
##
###############################################
## ISUPV2_AUSTRIAN
## ISUPV2_NORWEGIAN
##
## ISUPV2_CZECH
## ISUPV2_NTT
##
Q761 Version 3 Protocol Family
#################################
##
50
##
#################################
## ISUPV3
##
## ISUPV3_FRENCH
##
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-10
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
## ISUPV2_FINNISH96 ## ISUPV2_SPANISH
##
## ISUPV2_FRENCH
## ISUPV2_SWISS
##
## ISUPV2_GERMAN
## ISUPV2_SWISS_C2
##
## ISUPV2_JAPAN
## ISUPV2_TELEFONICA ##
## ISUPV2_KPNPB
## ISUPV2_TOKYO
##
##
## ISUPV2_VIETNAM
##
###############################################
Q721 Protocol Family
#######################
##
60
##
#######################
## Q721_BASE
##
## Q721_BRAZILIAN
##
## Q721_CHINA
##
## Q721_FRENCH
##
## Q721_PHILLIPINE ##
##
##
##
##
##
##
#######################
## ISUPV3_UK
##
## ISUPV3_UK_AXE10
##
## ISUPV3_UK_AXE10_BTNETCHAT ##
## ISUPV3_UK_BTNETCHAT
##
##
##
##
##
#################################
Q767 Protocol Family
#################################################
##
70
##
71
##
#################################################
## Q767_BASE
## Q767_RUSS
##
## Q767_BRAZIL
## Q767_SINGAPORE ##
## Q767_COLOMBIA
## Q767_SPAN
##
## Q767_GUATEMALA
## Q767_SWED
##
## Q767_INDONESIA
## Q767_TELSTRA
##
## Q767_ITAL
## Q767_TURKISH
##
## Q767_ITAL_INTERCONNECT ##
##
## Q767_MEXICAN
##
##
#################################################
Q931 Protocol Family
######################
##
80
##
######################
## Q931
##
## Q931_AUSTRALIA ##
## Q931_SINGAPORE ##
##
##
##
##
##
##
##
##
##
##
######################
The following prompt is displayed:
Would you like to add another protocol set to your system?
[y] [y,n,?,q] n
c.
For Cisco MGC Software Release 9.2(x): Select the specific protocol(s) you need from the
following table (instead of selecting all) and enter the protocol identifier(s).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-11
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Miscellaneous Protocols
###################################
##
01
##
02
##
###################################
## BTNUP_BTNR167 ## IETF_SIP ##
## BTNUP_IUP
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
##
###################################
SS7 Protocol Family
#########################
##
10
##
#########################
## ANSISS7_92
##
## ANSISS7_CLEAR
##
## ANSISS7_MCI
##
## ANSISS7_STANDARD
##
## GR317
##
## GR317_C1
##
## GR317_NOTPTX
##
##
##
#########################
PRI Protocol Family
########################################
##
20
##
21
##
########################################
## ATT_41459
## ETS_300_102
##
## ATT_41459_C2 ## ETS_300_102_C1 ##
## BELL_1268
## ETS_300_121
##
## BELL_1268_C3 ## ETS_300_172
##
##
## ETS_300_356
##
##
##
##
##
##
##
########################################
Q761 Version 1 Protocol Family
#########################################################################################
##
30
##
31
##
32
##
33
##
#########################################################################################
## Q761_ARGENTINA
## Q761_CHILE
## Q761_97VER_BASE
## HKTA_2202
##
## Q761_ARGENTINA_C2
## Q761_CHINA
## Q761_PERU
## ISUPV1_POLI ##
## Q761_AUSTRL
## Q761_CHINA_MOB
## Q761_PORTUGAL
##
##
## Q761_AUSTRL_C2
## Q761_DANISH
## Q761_SIEMENS_MOBI
##
##
## Q761_BASE
## Q761_INDIA
## Q761_SINGAPORE
##
##
## Q761_BELG_BCOM
## Q761_KOREAN
## Q761_SINGAPORE_C2
##
##
## Q761_BELG_ISUP_CUJO ## Q761_NEWZEALAND ## Q761_TAIWAN
##
##
## Q761_BELG_MOBI
##
## Q761_THAILAND
##
##
#########################################################################################
Q761 Version 2 Protocol Family
###############################################
##
40
##
41
##
###############################################
## ISUPV2_AUSTRIAN
## ISUPV2_NORWEGIAN
##
## ISUPV2_CZECH
## ISUPV2_NTT
##
## ISUPV2_FINNISH96
## ISUPV2_SPANISH
##
## ISUPV2_FRENCH
## ISUPV2_SWISS
##
## ISUPV2_GERMAN
## ISUPV2_SWISS_C2
##
## ISUPV2_JAPAN
## ISUPV2_TELEFONICA ##
## ISUPV2_KPNPB
## ISUPV2_TOKYO
##
##
## ISUPV2_VIETNAM
##
###############################################
Q761 Version 3 Protocol Family
#################################
##
50
##
#################################
## ISUPV3
##
## ISUPV3_FRENCH
##
## ISUPV3_UK
##
## ISUPV3_UK_AXE10
##
## ISUPV3_UK_AXE10_BTNETCHAT ##
## ISUPV3_UK_BTNETCHAT
##
##
##
##
##
#################################
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-12
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Q721 Protocol Family
#######################
##
60
##
#######################
## Q721_BASE
##
## Q721_BRAZILIAN
##
## Q721_CHINA
##
## Q721_FRENCH
##
## Q721_PHILLIPINE ##
##
##
##
##
##
##
#######################
Q767 Protocol Family
#################################################
##
70
##
71
##
#################################################
## Q767_BASE
## Q767_RUSS
##
## Q767_BRAZIL
## Q767_SINGAPORE ##
## Q767_COLOMBIA
## Q767_SPAN
##
## Q767_GUATEMALA
## Q767_SWED
##
## Q767_INDONESIA
## Q767_TELSTRA
##
## Q767_ITAL
## Q767_TURKISH
##
## Q767_ITAL_INTERCONNECT ##
##
## Q767_MEXICAN
##
##
#################################################
Q931 Protocol Family
######################
##
80
##
######################
## Q931
##
## Q931_AUSTRALIA ##
## Q931_SINGAPORE ##
##
##
##
##
##
##
##
##
##
##
######################
The following prompt is displayed:
Would you like to add another protocol set to your system?
[y] [y,n,?,q] n
Step 10
Select one of the following options:
a.
If you select y, you are prompted by the system to enter another protocol identifier (see Step 9).
a.
If you select n, the installation of a stand-alone Cisco MGC is done and text similar to the following
is displayed:
OK, no more protocols will be installed on your system
Uncompressing ASP_NotRealProtocol.mdo
Uncompressing ASP_NotRealProtocol.so
Uncompressing CALLVER.mdo
Uncompressing CALLVER.so
Uncompressing CALLVER_GENERIC_ANALYSIS.mdo
Uncompressing CALLVER_GENERIC_ANALYSIS.so
Uncompressing CALLVER_LCM.mdo
Uncompressing CDR_MAN.mdo
Uncompressing CDR_MAN.so
Uncompressing CONNECTION_PLANE_MANAGER.mdo
Uncompressing CONNECTION_PLANE_MANAGER.so
Uncompressing EISUP.mdo
Uncompressing EISUP.so
Uncompressing GENERIC_ANALYSIS.mdo
Uncompressing GENERIC_ANALYSIS.so
Uncompressing IN_TRIGGER.mdo
Uncompressing IN_TRIGGER.so
Uncompressing LEG_CONTROLLER.mdo
Uncompressing LEG_CONTROLLER.so
Uncompressing cc.mdo
Uncompressing cc.so
Uncompressing dummy.mdo
Uncompressing dummy.so
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-13
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
Uncompressing lcm.mdo
Uncompressing lcm.so
Installation of <CSCO00000> was successful.
Uncompressing Q761_ARGENTINA.mdo
Uncompressing Q761_ARGENTINA.so
Uncompressing Q761_ARGENTINA_C2.mdo
Uncompressing Q761_ARGENTINA_C2.so
Uncompressing Q761_AUSTRL.mdo
Uncompressing Q761_AUSTRL.so
Uncompressing Q761_AUSTRL_C2.mdo
Uncompressing Q761_AUSTRL_C2.so
Uncompressing Q761_BASE.mdo
Uncompressing Q761_BASE.so
Uncompressing Q761_BELG_BCOM.mdo
Uncompressing Q761_BELG_BCOM.so
Uncompressing Q761_BELG_ISUP_CUJO.mdo
Uncompressing Q761_BELG_ISUP_CUJO.so
Uncompressing Q761_BELG_MOBI.mdo
Uncompressing Q761_BELG_MOBI.so
Installation of <CSCO30000> was successful.
Beginning Check of System Performance Requirements
Number of CPUs in system 4
Memory size: 4096 Megabytes
The sparcv9 processor operates at 440 MHz,
Swap is total: 36912k bytes allocated + 24272k reserved =
61184k used, 5446792k available
Please Verify that you have over 4000000K Available swap
install.sh: setting *.numberOfThreads = 2
Shutting down TimesTen Server: done.
Installation completed Fri Feb 22 10:56:24 EST 2002
Installation log can be found in /var/adm/MGC_install.log
Step 11
Use the following command to set a new password for mgcusr:
# passwd mgcusr
Step 12
Type eject and press Enter to open the door to the CD-ROM drive. Remove the Cisco MGC software
CD.
Step 13
Proceed to the “Installing the Cisco Security Package (CSCOh013)” section on page 3-16 and follow the
CSCOh013 installation procedures.
Note
Install the CSCOh013 security package for both simplex and fault tolerant (duplex) systems.
Step 14
Type eject and press Enter to open the door to the CD-ROM drive. Remove the Cisco MGC software
CD.
Note
During installation of the Cisco MGC software, the system is automatically installed, using a standard
performance profile satisfactory for both nailed and switched solutions.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-14
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco MGC Software 9.2(x) and Higher Releases
This completes the installation of the Cisco MGC software for a simplex configuration. You can now
begin configuring your Cisco MGC software in the “Configuring Groups and Users” section on
page 5-10.
For a sample install.sh log file, see Appendix D, “Sample Output from install.sh” section on page D-1.
See the Cisco Media Gateway Controller Provisioning Guide for information on provisioning the Cisco
MGC software on a simplex system.
If you have a redundant configuration, continue to the section “Installing on a Fault Tolerant System”
section on page 3-15.
If you have questions or need assistance, see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii.
Installing on a Fault Tolerant System
Caution
To ensure the successful installation of a fault tolerant configuration, you must first provision the
software for the active Cisco MGC host after Step 7 of the “Installing on a Simplex System” section on
page 3-3 before proceeding to Step 1, below. Refer to the Cisco Media Gateway Controller Provisioning
Guide for information about the following:
- Provisioning the active Cisco MGC host
- Procedures for converting the active Cisco MGC host to standby host
Note that only one active provisioning session is permitted and provisioning is only permitted on the
active Cisco MGC host.
Exit the provisioning session on the active host and continue to Step 1, below. If software is not
provisioned after it is installed on the active Cisco MGC host, the standby host will not be synchronized
with the active host. As a result, a forced switchover may cause the switchover to fail.
To install the Cisco MGC software on a fault tolerant system (with two Cisco MGC hosts and Cisco
SLTs), complete the following steps:
Note
The MGC_install.log and the MGC_pkgerrors.log are stored in the /var/adm directory.
Step 1
Continuing from Step 13 of the “Installing on a Simplex System” section on page 3-3, exit server 1.
Step 2
Log on to server 2 as root and go to the # prompt.
Step 3
Load the Cisco MGC software CD into the server 2 CD-ROM drive.
Step 4
Follow the instructions in “Installing on a Simplex System” section on page 3-3 starting from Step 3.
Step 5
Configure the execution environment parameters and database replication for fault tolerant systems,
using the following sections:
•
Configuring Switchover, page 5-41
•
Initializing the Provisioning Object Manager, page 5-43
•
Initializing the Call Screening Database, page 5-57
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
This completes the installation of the Cisco MGC software. Continue to the “Configuring Groups and
Users” section on page 5-10 to configure groups and users. If you have questions or need assistance, see
the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Note
Always check CCO (http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml) to ensure that you have
the latest required patch version released by Cisco on your system, CD, or file system (if downloaded
previously from CCO).
Installing the Cisco Security Package (CSCOh013)
The system security patches install the Cisco Security Package. This package reduces the number of
known system security vulnerabilities.
Note
The Sun Solaris 8 operating system and Cisco MGC software must already be installed in your system
before you can install the Cisco Security Package.
You must have system administrator privileges to install this package.
Caution
If you are planning to use DiskSuite, you must first install it before installing the Cisco Security Package.
For DiskSuite installation procedures, see the “Installing the Solstice DiskSuite (CSCOh016)” section
on page 2-32.
Caution
If you are planning to run mgcrestore, make sure you are installing the same version of the Cisco
Security Package that was installed on your system when mgcbackup was run. Or, if the Cisco Security
Package was not installed on your system when mgcbackup was run, you must first run mgcrestore
before installing the Cisco Security Package.
Note
During an HSI upgrade, the CSCOh013 security package must be installed after upgrading the HSI
application and prior to uninstalling the previous HSI version. Otherwise, the installation of the
CSCOh013 package will fail. This does not apply to new HSI installations.
Do the following procedures to install the Cisco Security Package:
Step 1
Before installing the Cisco Security Package, you must first determine the Solaris release version of the
package installed on your system. Type the following command and press Enter:
pkginfo -l <package name>
The following is similar to the text that is displayed when the pkginfo command is used:
hostname% pkginfo -l CSCOh013
PKGINST: CSCOh013
NAME: Media Gateway Controller Security package compatible with Solaris 2.6 and
Solaris 8
CATEGORY: utilities
ARCH: sparc
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-16
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
VERSION:
BASEDIR:
VENDOR:
PSTAMP:
INSTDATE:
EMAIL:
STATUS:
FILES:
Note
Step 2
2.0(1)
/opt/sun_install
Cisco System, Inc.
2002/02/25 20:56 GMT (liberty)
Mar 06 2002 16:19
[email protected]
completely installed
4 installed pathnames
2 shared pathnames
2 directories
2 executables
57 blocks used (approx)
If you have an older version of the Cisco Security patch, you must remove it before installing
the new patch. For package removal procedures, see Removing the Cisco Security Package
(CSCOh013), page 3-20.
Install latest version of the Cisco Security Package either by downloading the software from CCO or
from a CD-ROM.
a.
If you are downloading the software from CCO, store the Cisco Security Package on your UNIX
platform. To determine the Solaris release version of the package you downloaded, use the
following command:
pkg -l -d <package instance>.pkginfo
The following is similar to the text that is displayed when using the -d option with the pkginfo
command:
hostname% pkginfo -l CSCOh013
PKGINST: CSCOh013
NAME: Media Gateway Controller Security package compatible with Solaris 2.6 and
Solaris 8
CATEGORY: utilities
ARCH: sparc
VERSION: 2.0(1)
BASEDIR: /opt/sun_install
VENDOR: Cisco System, Inc.
PSTAMP: 2002/02/25 20:56 GMT (liberty)
INSTDATE: Mar 06 2002 16:19
EMAIL: [email protected]
STATUS: completely installed
FILES:
4 installed pathnames
2 shared pathnames
2 directories
2 executables
57 blocks used (approx)
b.
Step 3
If you are installing the software from a CD-ROM, insert the Solaris 8 Environment Patches for
Cisco PGW CD into the CD-ROM drive.
Enter one of the following commands at the # prompt:
a.
If you are using the file downloaded from CCO, enter the following command:
# pkgadd -d ./CSCOh013.pkg
b.
If you are installing from a CD-ROM, enter the following command:
# pkgadd -d /cdrom/cdrom0/CSCOh013.pkg
The following text is displayed:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-17
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
The following packages are available:
1 CSCOh013
Media Gateway Controller Security package compatible with Solaris 2.6
and Solaris 8
(sparc) 2.0(1)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 4
Select all by pressing Enter. The following is an example of the text display:
Processing package instance <CSCOh013> from </auto/mgc-sqa/PATCHES/SUN/2.0.1/CSCOh013.pkg>
Media Gateway Controller Security package compatible with Solaris 2.6 and Solaris 8
(sparc) 2.0(1)
Cisco System, Inc.
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh013> [y,n,?] y
Step 5
Type y and press Enter to install the package. The following is an example of the text that is displayed:
Installing Media Gateway Controller Security package compatible with Solaris 2.5.1, 2.6,
and 8 as <CSCOh013>
## Executing preinstall script.
Cisco MGC software or an adjunct was found.
## Installing part 1 of 1.
/opt/sun_install/CiscoSec.sh
/opt/sun_install/restore_lp.sh
[ verifying class <none> ]
## Executing postinstall script.
You must now run the install security script
Step 6
Type eject and press Enter to open the door to the CD-ROM drive. Remove the Solaris 8 Operating
Environment Patches CD.
Step 7
Log in as root and enter the following commands to run the install security script.
# cd /opt/sun_install
# ./CiscoSec.sh install /tmp/security.log
Text similar t o the following is displayed:
Output will be logged in
/tmp/security.log
You are running as root - Good...
Operating System: SunOS 5.8
Backup directory does not exist - creating it now...
Original files will be saved. Run this script
with the parameter 'uninstall' to restore
system to its original state
The following files will be removed from /etc/rc2.d:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-18
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
File /etc/rc2.d/K60nfs.server not found
File /etc/rc2.d/K77dmi not found
Remove /etc/rc2.d/S47asppp
Remove /etc/rc2.d/S70uucp
Remove /etc/rc2.d/S71rpc
Remove /etc/rc2.d/S73cachefs.daemon
Remove /etc/rc2.d/S73nfs.client
Remove /etc/rc2.d/S74autofs
Remove /etc/rc2.d/S76nscd
Remove /etc/rc2.d/S80lp
Remove /etc/rc2.d/S80spc
Remove /etc/rc2.d/S85power
Remove /etc/rc2.d/S88sendmail
Remove /etc/rc2.d/S89bdconfig
File /etc/rc2.d/S91leoconfig not found
File /etc/rc2.d/S92rtvc-config not found
Remove /etc/rc2.d/S92volmgt
Remove /etc/rc2.d/S93cacheos.finish
Remove /etc/rc2.d/S99dtlogin
The following files will be removed from /etc/rc3.d:
Remove /etc/rc3.d/S15nfs.server
Now remove users from the password file
Remove lp from password file
Remove nuucp from password file
Remove uucp from password file
Remove smtp from password file
Remove listen from password file
Remove lp crontab entry
Remove uucp crontab entry
Create new inetd.conf file with only ftp,
telnet and echo services enabled
Adjust kernel parameters in the /etc/system file
Force TCP/IP to use random initial seeds
Enable recording of failed login attempts
Create a new (minimal) inetsvc startup file
Restrict FTP Usage
Don't allow telnet users to log in as root
Disable keyboard abort sequence
Save existing /etc/shells file
Create /etc/shells file
Create /etc/init.d/nddconfig file
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-19
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
Note
Step 8
If you are planning to install CSCOk9000, do not reboot after installing the CSCOh013
security package. You will be prompted to reboot after the installation of CSCOk9000.
Reboot your machine with the -r option. Type the following command and press Enter:
# reboot -- -r
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
The installation of the Cisco security package (CSCOh013) is now complete. Return to the procedure
for installing the Cisco MGC software.
Removing the Cisco Security Package (CSCOh013)
Do the following procedure if you need to remove the Cisco Security Package. Contact Cisco TAC if you
need assistance (see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii).
Caution
Removing the Cisco Security Package (CSCOh013) is the first step in removing the Cisco MGC
software. Remove the Cisco Security Package only if you intend to perform tasks such as upgrading the
Cisco MGC or upgrading to a new version of CSCOh013. Otherwise, the /etc/system files might be
corrupted if removed out of order and security might be compromised if CSCOh013 is removed without
removing the Cisco MGC.
If CSCOk9000 is installed, it must be removed first, before CSCOh013 is removed.
Note
Step 1
Make sure the Sun Solaris 8 operating system and the Cisco MGC software are still installed in your
system before you remove the Cisco Security Package.
Prior to uninstalling the CSCOh013 package, you must first uninstall the CiscoSec.sh script. Enter the
following commands:
cd /opt/sun_install
./CiscoSec.sh uninstall /tmp<logfile>.log
Text similar to the following is displayed:
Output will be logged in
/tmp/<logfile>.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-20
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Installing the Cisco Security Package (CSCOh013)
You are running as root - Good...
Operating System: SunOS 5.8
Restoring system to original configuration...
File K60nfs.server not found
File K77dmi not found
Restore /etc/rc2.d/S47asppp
Restore /etc/rc2.d/S70uucp
Restore /etc/rc2.d/S71rpc
Restore /etc/rc2.d/S73cachefs.daemon
Restore /etc/rc2.d/S73nfs.client
Restore /etc/rc2.d/S74autofs
Restore /etc/rc2.d/S76nscd
Restore /etc/rc2.d/S80lp
Restore /etc/rc2.d/S80spc
Restore /etc/rc2.d/S85power
Restore /etc/rc2.d/S88sendmail
Restore /etc/rc2.d/S89bdconfig
File S91leoconfig not found
File S92rtvc-config not found
Restore /etc/rc2.d/S92volmgt
Restore /etc/rc2.d/S93cacheos.finish
Restore /etc/rc2.d/S99dtlogin
Restore /etc/rc3.d/S15nfs.server
Replace the following userids in the password file
lp nuucp uucp smtp listen
Restore
Restore
Restore
Restore
Restore
lp to the password file
nuucp to the password file
uucp to the password file
smtp to the password file
listen to the password file
Restore lp crontab entry
Restore uucp crontab entry
Restore /etc/inetd.conf file
Restore /etc/system file
Restore /etc/default/inetinit file
Disable recording of failed login attempts
Restore /etc/init.d/inetsvc file
Restore /etc/ftpusers file
Restore /etc/default/login file
Restore /etc/default/kbd file
Restore /etc/shells file
/etc/init.d/nddconfig did not exist originally
Delete existing file
/etc/rc2.d/S70nddconfig did not exist - delete existing file
Backup directory is being removed
**************************************************
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-21
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Done!
Step 2
Type the following command and press Enter:
pkgrm CSCOh013
Text similar to the following is displayed:
The following package is currently installed:
CSCOh013
Media Gateway Controller Security package compatible with Solaris
2.5.1, 2.6, and 8
(sparc) 2.0(11)
Do you want to remove this package?
Step 3
Type y and press Enter to remove the package.
Text similar to the following is displayed:
## Removing installed package instance <CSCOh013>
This package contains scripts which will be executed with super-user
permission during the process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q] y
Step 4
Type y and press Enter to continue the removal of the package.
Text similar to the following is displayed:
## Verifying package dependencies.
## Processing package information.
## Executing preremove script.
*** Removal of system security update package started...Fri Jul 30 17:21:56 EDT 2004 ***
## Removing pathnames in class <none>
/var/tmp <shared pathname not removed>
/opt/sun_install/restore_lp.sh
/opt/sun_install/CiscoSec.sh
/opt/sun_install <shared pathname not removed>
## Updating system information.
Removal of <CSCOh013> was successful.
This completes the removal of the Cisco Security Package.
Verification Test Suite (VTS) Package (CSCOh014) Overview
The Verification Test Suite (VTS) provides an optional script designed to test configured Sun Solaris 8
platforms used for Cisco MGC and BAMS products. These platforms include the following:
•
Sun Fire V120
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-22
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
•
Netra 120
•
Netra t1 100/105
•
Netra 20
•
Sun Fire V210
•
Netra 240
•
Netra 440
•
Netra t 1120/1125
•
Netra t 1400/1405
VTS test instructions support the following interface cards:
•
Sun GigaSwift Ethernet PCI card (order # X1150A)
•
Sun 10/100BT Ethernet PCI card (order # X1033)
•
Sun Quad Fast Ethernet PCI card (order # X1034A)
Perform all testing with a console log file enabled to capture everything entered at the console input and
displayed on the console output. One way to accomplish this is through a terminal server connected to
the console port of the Netra box. You can use the xterm program with the -l –lf <logfile> command line
option to create the console log file.
You should archive the console log file along with the VTS log file created with other records for each
target system during the test below.
Installing the VTS Package
Note
The VTS package must be installed before running any tests.
To install the VTS package:
Step 1
Place the PGW Solaris Patches CD in the CD-ROM drive of the target system.
Step 2
Type the following commands to install the VTS package and press Enter:
# /usr/sbin/vold &
Note
Entering this command may result in an error indicating the vold daemon is already running. If
this happens, the error can be ignored.
# cd /cdrom/cdrom0
# pkgadd –d CSCOh014.pkg
The following text is displayed:
The following packages are available:
1 CSCOh014
Media Gateway Controller Solaris 8 test
(sparc) 2.x(x)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: 1
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-23
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Processing package instance <CSCOh014> from </auto/monument04/tbova/CSCOh014.pkg>
Media Gateway Controller Solaris 8 test
(sparc) 2.x(x)TJB
Cisco System, Inc.
##
##
##
##
Processing package information.
Processing system information.
Verifying disk space requirements.
Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh014> [y,n,?] y
Step 3
Answer y and press Enter to continue with the installation.
Text similar to the following is displayed:
Installing Media Gateway Controller Solaris 8 test as <CSCOh014>
## Executing preinstall script.
Platform is SUNW,Ultra-80
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/VTSadmin.file
/opt/sun_install/installVTS.sh
/opt/sun_install/uninstallVTS.sh
/opt/sun_install/vts_script
[ verifying class <none> ]
## Executing postinstall script.
Installation of <CSCOh014> was successful.
#
Step 4
Type the following command to eject the CD and press Enter:
# cd /
# eject
Step 5
Change directories at the end of the CSCOh014 installation, when text similar to the following is
displayed:
You must now change directories to /opt/sun_install and run the ./installVTS.sh as root.
Step 6
Change directories and install the SunVTS package. Press Enter when prompted.
# cd /opt/sun_install
# ./installVTS.sh
The following text is displayed:
Changing directories to /cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product
Current directory /cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product
Processing package instance <SUNWvts> from
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>
SunVTS
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-24
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
SunVTS supports Kerberos V5 network authentication protocol, included in SEAM (Sun
Enterprise Authentication Mechanism). This protocol is designed to provide strong
authentication for client/server applications by using secret-key cryptography.
_In order to use this feature, a SEAM-based Security enabled network must be present.
Step 7
Enter n when asked if you want the Kerberos V5-based security installed.
Do you want to enable the Kerberos V5 based security? n
The following text is displayed:
## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
Installing SunVTS as <SUNWvts>
## Installing part 1 of 1.
94394 blocks
/opt/SUNWvts/.etc_inetdconf <symbolic link>
Executing i.inetdconf class script...
Completed editing /etc/inetd.conf
Sending signal to inetd to read the modified conf file...
[ verifying class <inetdconf> ]
[ verifying class <gsscfg> ]
## Executing postinstall script.
Installation of <SUNWvts> was successful.
Processing package instance <SUNWvtsx> from
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>
64-bit SunVTS
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
Installing 64-bit SunVTS as <SUNWvtsx>
## Installing part 1 of 1.
20946 blocks
Installation of <SUNWvtsx> was successful.
Processing package instance <SUNWvtsmn> from
</cdrom/solaris8_1001_suppcd/SunVTS_4.5/Product>
SunVTS Man Pages
(sparc) 4.5,REV=08.01.08.15,OE=5.8
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-25
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
## Verifying package dependencies.
## Verifying disk space requirements.
Installing SunVTS Man Pages as <SUNWvtsmn>
## Installing part 1 of 1.
53 blocks
Installation of <SUNWvtsmn> was successful.
#
This completes the VTS installation. If you have questions or need assistance, see the “Obtaining
Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Using the SunVTS Test Package
Note
Version 4.5 of the SunVTS should be used. This version is available with the 10/01 release of Solaris 8.
Use the SunVTS program to test the following:
•
CPUs
•
Memory
•
Ethernet cards
Note
To fully test the Ethernet ports, all Ethernet ports must be configured with valid IP addresses
and connected to an Ethernet network with at least one other machine on the network.
•
Hard disks
•
CD-ROM drive
Note
•
To test the CD-ROM drive, a CD-ROM must be in the drive.
LOM hardware
Normal Unit Test
The normal unit test must be successfully run on each target system before it is shipped to the customer.
A normal unit test checks 20 percent of each disk surface. To run a normal unit test:
Caution
Step 1
Do not run this test while the application is running because it could adversely affect the application
performance.
Change directories to the following directory:
# cd /var/tmp
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-26
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Step 2
Enter the following command to start the test:
# ./vts_script
Text similar to the following is displayed:
Platform is SUNW,Ultra-80
OS version is 5.8
OS is 64-bits
checking for VTS packages
system
SUNWvts
SunVTS
system
SUNWvtsx
64-bit SunVTS
VTS version: 4.5,REV=08.01.08.15,OE=5.8
VTS probe output:
Processor(s)
cpu-unit0(fputest)
Type:SPARC V9 based FPU
clock-frequency:440 MHz.
cpu-unit0(cputest)
Type:SPARC V9 CPU
clock-frequency: 440 MHz.
cpu-unit1(fputest)
Type:SPARC V9 based FPU
clock-frequency:440 MHz.
cpu-unit1(cputest)
Type:SPARC V9 CPU
clock-frequency: 440 MHz.
cpu-unit2(fputest)
Type:SPARC V9 based FPU
clock-frequency:440 MHz.
cpu-unit2(cputest)
Type:SPARC V9 CPU
clock-frequency: 440 MHz.
cpu-unit3(fputest)
Type:SPARC V9 based FPU
clock-frequency:440 MHz.
cpu-unit3(cputest)
Type:SPARC V9 CPU
clock-frequency: 440 MHz.
l1dcache(l1dcachetest)
Level 1 Cache Test
l2dcache(l2dcachetest)
Level 2 Cache Test
mp(mptest)
Number of processors:4
mp(mpconstest)
Number of processors:4
system(systest)
System Configuration= Sun Microsystems
Memory size= 4096 Megabytes
System clock-frequency= 110 MHz
Memory
kmem(vmemtest)
Total Swap: 5404MB
mem(pmemtest)
System memory size:4096MB
Network
hme0(nettest)
Host_Name: va-panthers
Host Address: 10.82.80.64
Host ID: 80c4d518
Domain Name:
hme1(nettest)
sun4u
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-27
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Host_Name: va-panthers-a
Host Address: 10.82.81.64
Host ID: 80c4d518
Domain Name:
Comm.Ports
se0(sptest)
port a = se0 = /dev/term/a = /devices/...se...:a
port b = se1 = /dev/term/b = /devices/...se...:b
Monitor&Alarms
lomlite(lomlitetest)
Device information: NONE
OtherDevices
ecpp0(ecpptest)
IEEE 1284 parallel port (ECP/nibble/centronics modes)
ssc100@16(dpmtest)
DPM controller at ssc100@16
SCSI-Devices(glm0)
c0t0d0(disktest)
Capacity: 16.86GB
Controller: glm0
Vendor: SEAGATE
SUN Id: ST318203LSUN18G
Firmware Rev: 034A
Serial Number: 9946717334
c0t1d0(disktest)
Capacity: 16.86GB
Controller: glm0
Vendor: SEAGATE
SUN Id: ST318203LSUN18G
Firmware Rev: 034A
Serial Number: 9946723866
c0t6d0(cdtest)
Controller: glm0
Number of hard disks:
disks:
c0t0d0
c0t1d0
2
Number of network interfaces:
Network interfaces:
hme0
hme1
2
normal test
Platform: Netra T140x (LW3)
Floating Point Unit Test ...
Central Processor Unit Test cpu-unit0
Central Processor Unit Test cpu-unit2
Central Processor Unit Test cpu-unit1
Level 1 Data Cache Test ...
Central Processor Unit Test cpu-unit3
Level 2 Data Cache Test ...
System Test ...
Level 1 Data Cache Test done
System Test done
Floating Point Unit Test done
Level 2 Data Cache Test done
Central Processor Unit Test cpu-unit2
Central Processor Unit Test cpu-unit0
Central Processor Unit Test cpu-unit3
Central Processor Unit Test cpu-unit1
...
...
...
...
done
done
done
done
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-28
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Virtual Memory Test 64MB ...
Physical Memory Test ...
Virtual Memory Test done
Physical Memory Test done
Network Test hme0 ...
CD-ROM Test c0t6d0 ...
Network Test hme1 ...
Lights Out Management Test lomlite ...
Hard Disk Test c0t0d0 20% ...
Hard Disk Test c0t1d0 20% ...
Network Test hme1 done
Network Test hme0 done
Feb 27 10:03:29 va-panthers lom: LOMlite Alarm 1 OFF Feb 27 10:03:34 va-panthers lom:
LOMlite Alarm 1 ON Feb 27 10:03:39 va-panthers lom: LOMlite Alarm 2 OFF Feb 27 10:03:44
va-panthers lom: LOMlite Alarm 2 ON Feb 27 10:03:49 va-panthers lom: LOMlite Alarm 3 OFF
Feb 27 10:03:53 va-panthers lom: LOMlite Alarm 3 ON
CD-ROM Test c0t6d0 done
Feb 27 10:04:09 va-panthers lom: LOMlite Fault LED ON Feb 27 10:04:13 va-panthers lom:
LOMlite Fault LED OFF
Lights Out Management Test lomlite done
Hard Disk Test c0t1d0 done
Hard Disk Test c0t0d0 done
**************************************
************* RESULTS ****************
**************************************
normal test
Number of hard disks:
disks:
c0t0d0
c0t1d0
2
Number of network interfaces:
Network interfaces:
hme0
hme1
PPPPPP
AA
SSSSSS
PP PP A A SS
PPPPPP AAAAAA SSSSSS
PP
AA AA
SS
PP
AA AA SSSSSS
#
2
SSSSSS
SS
SSSSSS
SS
SSSSSS
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-29
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Note
Refer to Table 3-2 for the approximate amount of time the test will take on the different
platforms supported.
Step 3
Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the
test passed and the proper number of hard disks and Ethernet interfaces were detected.
Step 4
Reboot your host from root by entering the following command:
# reboot -- -r
Running a Test in Brief Mode
When run in brief mode, the vts_script tests 1 percent of each disk surface. To run the test in brief mode:
Step 1
Change directories to the /var/tmp directory. Enter the following command:
# cd /var/tmp
Step 2
Enter the following command to start the test:
# /opt/sun_install/vts_script brief
Step 3
Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the
test passed and the proper number of hard disks and Ethernet interfaces were detected.
Step 4
Reboot your host from root by entering the following command:
# reboot -- -r
Running a Test in Full Mode
When run in full mode, the vts_script tests 100 percent of each disk surface. To run the test in full mode:
Step 1
Change directories to the /var/tmp directory. Enter the following command:
# cd /var/tmp
Step 2
Enter the following command to start the test:
# /opt/sun_install/vts_script full
Step 3
Once the test completes, examine the console output and the file /var/tmp/vts_script.log. Verify that the
test passed and the proper number of hard disks and Ethernet interfaces were detected.
Step 4
Reboot your host from root by entering the following command:
# reboot -- -r
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-30
OL-1150-15
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
vts_script Execution Times
Table 3-2 lists estimated execution times for the VTS script on a sampling of Cisco MGC software host
platforms.
Note
Table 3-2
Actual VTS script execution time on your host platforms differs based on the configuration of your
hardware. The size of the disks used in your host platforms has the largest single impact on execution
time.
Sample Estimates of VTS Script Execution Times
Platform Type, Number of CPUs, CPU speed,
VTS
Amount of RAM, Number of Disks,
Version Size of Disks
Brief Mode
Execution Time
(hours:minutes:
seconds)
Normal Mode
Execution Time
(hours:minutes:
seconds)
Full Mode
Execution Time
(hours:minutes:
seconds)
4.3
Netra t1 10x, 1, 360MHz, 64M, 2, 9GB
0:5:02
0:8:19
0:36:26
4.3
Netra t 112x, 1, 296MHz, 2GB, 1, 9GB
0:5:42
0:10:23
0:40:31
4.3
Netra t 112x, 2, 440MHz, 2GB, 2, 18GB
0:3.55
0:11:05
0:51:44
4.3
Netra t 140x, 4, 440MHz, 4GB, 2, 18GB
0:4:21
0:11:16
0:52:06
4.3
Netra t 140x, 4, 440MHz, 4GB, 4, 18GB
0:5:23
0:15:03
0:65:40
5.1
Netra 120, 1 440MHz, 2GB, 2, 36GB
0:06:09
1:16:35
estimate unavailable
5.1
Netra 20, 4, 900MHz, 4GB, 2, 73GB
0:09:36
2:31:00
estimate unavailable
5.1
Sun Fire V210, 1, 1340MHz, 2GB, 2, 73GB
0:08:56
2:30:57
estimate unavailable
5.1
Netra 240, 2, 1280MHz, 4GB, 2, 73GB
0:11:30
2:31:00
estimate unavailable
5.1
Netra 440, 4, 1281MHz, 8GB, 4, 73GB
0:09:31
2:22:00
estimate unavailable
Netra 240, 2, 1280MHz, 4GB, 2, 146GB
Removing SunVTS
The following procedure will remove SunVTS software and patch from the target system. The SunVTS
software occupies about 60 Mb of disk space under the /opt/SUNWvts directory. The SunVTS software
does not have to be removed; however, the if it is left on the target system, it will consume disk space
that could otherwise be used for application data.
Step 1
Enter the following commands to remove the SUNVTS package:
# cd /opt/sun_install
# ./uninstallVTS.sh
This completes the procedures for installing and running the VTS package. If you have questions or need
assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on
page xvii.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
3-31
Chapter 3
Cisco MGC Software Release 9 Installation
Verification Test Suite (VTS) Package (CSCOh014) Overview
Removing the VTS Package (CSCOh014)
Use the following procedure to remove the VTS test software from the target system after all tests are
complete, all the log files are archived, and the SunVTS software is uninstalled.
Note
Do not remove the CSCOh014 package without first removing the SunVTS package.
Type the following command and press Enter to remove the VTS package:
# pkgrm CSCOh014
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
3-32
OL-1150-15
CH A P T E R
4
Cisco PGW 2200 Security Enhancements
This document describes the Cisco PGW 2200 Security Enhancements feature. It provides procedures
for installing secure communication interfaces on the Cisco MGC, BAMS and HSI application platforms
in a network.
Table 4-1
Guide to Document Contents
Section and Page
Supported Platforms, page 4-2
Feature Overview, page 4-2
•
Client/Server and Secure Connectivity Relationships, page 4-3
– Secure Connectivity Among Cisco PGW 2200 Applications, page 4-3
– Secure Connectivity Between Cisco MGC Application Platforms, page 4-5
– Secure Connectivity Between BAMS Application Platforms, page 4-5
– Secure Connectivity Between BAMS and Cisco MGC Application Platforms, page 4-5
Installation Overview, page 4-6
•
Conditions for Installation, page 4-6
•
Installation Sequence, page 4-8
•
Export Control Splash Screens, page 4-9
•
CSCOk9000 Security Package Functions, page 4-10
– Connecting to the Cisco PGW 2200, BAMS, and HSI, page 4-10
– Telnet and FTP Toggle Options, page 4-10
Installing the CSCOk9000 Security Package, page 4-10
•
Installing CSCOk9000 on the Cisco PGW 2200 Host, page 4-11
•
Installing the CSCOk9000 on BAMS, page 4-15
•
Installing CSCOk9000 on HSI, page 4-18
•
Securing the Networks, page 4-18
– Securing the Cisco PGW 2200, page 4-19
– Securing the Cisco PGW 2200, page 4-19
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-1
Chapter 4
Cisco PGW 2200 Security Enhancements
Supported Platforms
Table 4-1
Guide to Document Contents (continued)
Section and Page
Fallback Procedures, page 4-29
•
Procedures for Cisco PGW 2200, page 4-29
•
Procedures for BAMS, page 4-30
Alarms and Messages, page 4-32
Supported Platforms
The hardware platforms supported for the Cisco MGC, BAMS, and HSI software are described in the
Cisco MGC Software Release 9 Installation and Configuration Guide.
Note
Cisco PGW 2200 consists of platforms that run the Cisco Media Gateway Controller (MGC) software,
Billing and Measurements Server (BAMS), and H.323 Signaling Interface (HSI).
Feature Overview
The Cisco PGW 2200 Security Enhancements feature is used to install secure communication interfaces
on the Cisco MGC, BAMS and HSI application platforms in a network. The secure interfaces consists
of multiple programs found in the openSSH software. These programs include the following:
•
ssh—secure shell, which replaces Telnet (for secure Telnet sessions, such as running MML)
•
sftp—secure FTP, which replaces FTP (for secure file transfers)
•
scp—secure copy, which replaces rcp
•
various other programs
Documentation for the various programs can be found at the openSSH web site
(http://www.openssh.org).
Note
The use of "SSH" (all upper case) refers to the collection of programs mentioned above, while the use
of "ssh" (all lower case) refers specifically to the secure shell program.
A confirmation is required when you attempt to run ssh for the first time on each new machine. For
scripts to run without human intervention, you will be required to manually run ssh at least once prior
to invoking automatic scripts.
Note
The SSH password is your regular login password.
A script is provided to restore the non-secure Telnet daemon if it has been disabled (toggle_telnet.sh).
A similar script (toggle_ftp.sh) is provided to restore the non-secure version of FTP.
Note
If you prefer not to use the SSH secure interfaces, you have the option to not disable Telnet and FTP.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-2
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Feature Overview
The SSH daemon supports two versions of the SSH protocol. By default, the sshd program is configured
to recognize clients using either connection protocol, and to respond appropriately.
Note
Cisco recommends that client programs use SSH protocol Version 2 (shipped with the CSCOk9000
security package).
Client/Server and Secure Connectivity Relationships
The following figures show the client/server and secure connectivity relationships used among the
different applications of the Cisco MGC, BAMS, and HSI.
In a network containing Cisco MGC platforms and BAMS platforms, the Cisco MGC platform is
considered to be a server system to BAMS. The BAMS platform is a client of the Cisco MGC platform.
This means that in the current, non-secure interface environment, to transfer files from the Cisco MGC
to BAMS, the BAMS system invokes the FTP program which talks to an FTP daemon process on the
Cisco MGC platform.
The following table explains the letters and acronyms used in these figures:
Table 2
Acronym/
Abbreviation
Description
C
Client
S
Server
SCP
Secure Copy
SFTP
Secure File Transfer
SSH
Secure Shell
Secure Connectivity Among Cisco PGW 2200 Applications
The following figure illustrates the client/server relationship and the secure connectivity used among the
different application types of the Cisco PGW 2200 and its network management elements. Note that
Cisco MNM-PT has SSH and SFTP interfaces to HSI.
Note
For simplicity, redundant platforms are not shown in this figure. The secure connectivity among the
different application types and the redundant platforms is the same.
Note
Install SSH on the Cisco MGC Node Manager 2.4(1) and Cisco MNM-PT 2.4(1) to enable the use of
secure communications for managing and provisioning the Cisco PGW 2200 and supported network
elements. With SSH installed on the Cisco MGC Node Manager, it can monitor the Cisco PGW node
during SSH installation. Refer to the document Implementing Security Enhancements for Cisco
MNM-PT and Cisco MGC Node Manager.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-3
Chapter 4
Cisco PGW 2200 Security Enhancements
Feature Overview
C
Cisco MNM-PT
C
C
SSH & SFTP
SSH & SFTP
SSH & SFTP
S
Cisco MGC
S
S
SFTP
HSI
S
S
C
S
BAMS
Cisco MNM
C
C
SSH & SFTP
S
SSH & SFTP
SSH
101110
C
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-4
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Feature Overview
Secure Connectivity Between Cisco MGC Application Platforms
The following figure illustrates the client/server relationship and the secure connectivity used between
two Cisco MGC application platforms operating as a redundant pair.
Cisco MGC
S
SCP
SCP
S
Cisco MGC
C
101111
C
Secure Connectivity Between BAMS Application Platforms
The following figure illustrates the client/server relationship and the secure connectivity used between
two BAMS application platforms operating as a redundant pair.
BAMS
S
SFTP
SFTP
S
BAMS
C
101153
C
Secure Connectivity Between BAMS and Cisco MGC Application Platforms
The following figure illustrates the client/server relationship and the secure connectivity used when one
redundant BAMS pair controls multiple Cisco MGC application platforms.
Note
For simplicity, the redundant Cisco MGC application platforms are not shown. The secure connectivity
between the redundant BAMS pair and the redundant Cisco MGC application platforms is the same.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-5
Chapter 4
Cisco PGW 2200 Security Enhancements
Installation Overview
Cisco MGC
Cisco MGC
Cisco MGC
S
S
S
S
SFTP
S
SFTP
SFTP
S
SFTP
SFTP
SFTP
C
C
SFTP
C
BAMS
SFTP
S
C
C
C
S
BAMS
C
101154
C
Installation Overview
The following sections describe details and the conditions necessary for installing the CSCOk9000
security package.
Conditions for Installation
You must have permission from the US government to download this software from CCO. Contact your
Cisco marketing representative to apply for eligibility.
Note
For remote access, you must have SSH client software (ssh and sftp) installed.
The following table lists the prerequisites for installing the CSCOk9000 security package:
Table 4-3
Requirements for Installing the CSCOk9000 Security Package
Requirement
Description
Sun Solaris 8 operating system
Versions of the Cisco PGW 2200 prior to Solaris 8 Operating
System will not install the SSH programs.
SSH installed on Cisco Node Manager and other element SSH must first be installed on Cisco Node Manager before
managers.
installing the CSCOk9000 security package on PGW, HSI, or
BAMS.
Refer to the section “Getting Started with SSH-Enabled Cisco
Node Manager” in the document Implementing Security
Enhancements for Cisco MNM-PT and Cisco MGC Node
Manager.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-6
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installation Overview
Table 4-3
Requirements for Installing the CSCOk9000 Security Package
Requirement
Description
One of the following software versions must be installed: The CSCOk9000 security package is not supported on the
following:
– Cisco MGC software release 9.4(1) or higher
• Cisco MGC software releases prior to release 9.4(1)
– BAMS release 3.13 or higher
• BAMS software releases prior to release 3.13
– HSI release 4.1 or higher.
• HSI software releases prior to release 4.1.
CSCOk9000 script must be installed after the Cisco
MGC software, BAMS or HSI are installed.
This allows the CSCOk9000 script to verify the version of the
application that was installed.
Install the CSCOh013 security package first before
installing CSCOk9000.
Make sure to follow this sequence of installation for the security
packages to work properly.
Caution
CSCOh013 cannot be installed after
CSCOk9000 is installed.
CSCOk9000 and CSCOh013 Security Packages
The secure interfaces can be logically considered as an extension to the 'box hardening' procedures
already implemented in the Cisco Security Package CSCOh013. 'Box hardening' refers to the practice of
removing unused or unnecessary users, services, and access points from the system to increase security
and reduce the possibility of unauthorized access to a machine.
The CSCOh013 security package is distributed as part of the Solaris Environment Patches (refer to CCO
for the latest version of these patches).
In most cases, Cisco recommends that both CSCOh013 and CSCOk9000 security packages be installed
to get the most secure environment Cisco can provide. However, it is possible to install only CSCOh013.
In this case, although the resulting system will have some, but not all security features installed, the
Cisco PGW 2200 node will operate correctly.
The SSH secure interface software is bundled in a separate package (CSCOk9000) because of U.S.
government restrictions on the export of encryption technology. The Cisco Secure Interface package
CSCOk9000 is distributed as part of the Cisco PGW 2200 Restricted Software (refer to CCO for the
latest version). The Cisco PGW 2200 Restricted Software can only be obtained through controlled
means—you are required to apply for permission to download this software and install it after your Cisco
MGC, BAMS, or HSI applications are installed.
Note
There are U.S. Government restrictions on exporting cryptographic technology. The Secure Shell (SSH)
program falls under the umbrella of those restrictions. The security package (CSCOk9000) is registered
and located in a restricted area from which only authorized customers can download.
If you have Cisco PGW 2200s that span various geographic locations, you must apply and be approved
for each site.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-7
Chapter 4
Cisco PGW 2200 Security Enhancements
Installation Overview
Installation Sequence
Because of the way the various Cisco PGW 2200 application programs (such as Cisco MGC, BAMS,
and HSI) operate, Cisco specifies the order in which systems must be upgraded to minimize down time
or time when systems are unable to communicate with one another.
Note
Secure versions of Cisco MNM-PT and Cisco MGC Node Manager are required in this secure
environment. SSH must first be installed on Cisco Node Manager before installing the CSCOk9000
security package on PGW, HSI, or BAMS.
Cisco MNM and MNM-PT can be installed to support SSH. Installation procedures for Cisco MNM is
located at the following url:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/products_installation_guide_chapter0918
6a008019f524.html#1226353
Installation procedures for Cisco MNM-PT is located at the following url:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/products_installation_guide_chapter0918
6a008019f526.html#35443
If you are using Cisco MNM-PT to perform system backups, refer also to documentation located at the
following url:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/products_installation_guide_chapter0918
6a008019f526.html#95252.
In the secure interface environment, the FTP daemon on the Cisco MGC is replaced by the ssh daemon
process (the ssh daemon controls sftp). The FTP client on BAMS is replaced by sftp. A special script
which invokes the use of sftp instead of FTP must be run on the BAMS platform. This means that the
order in which systems are upgraded is important.
A platform operating as a secure interface server must have SSH (the secure interface software) installed
and ready before the associated platform operating as the secure interface client can start to use the
secure interface. To clarify the suggested order of installation, refer to the table below to determine
which Cisco PGW 2200 application acts as a server to another.
Table 4
Server (Location of SSH and SFTP)
Client Programs Invoking SSH or SFTP
Cisco MGC
Cisco Billing and Measurements Server (BAMS)
Cisco MGC
Cisco Voice Services Provisioning Tool (Cisco
MNM-PT)
BAMS
Cisco MNM-PT
BAMS
BAMS (Both BAMS act as client and server to each other)
HSI
Cisco MGC Node Manager
Cisco MGC
Cisco MGC Node Manager
BAMS
Cisco MGC Node Manager
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-8
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installation Overview
Note
Any customer application that uses FTP, Telnet, and RCP to access any of the Cisco PGW 2200
applications must first install the SSH client.
Note
If you are accessing the Cisco PGW 2200, BAMS, or HSI from a remote machine, you must first install
SSH client on your machine before disabling the non-secure interfaces on the Cisco PGW 2200, BAMS,
or HSI. This client is not provided by the CSCOk9000 security package.
Server and Client Platforms Application Example
The following example uses the Cisco MGC and BAMS as the server and client platforms (respectively).
However, a case may occur where a customer-specific application is used to transfer billing files from
the Cisco MGC platform, or another customer application is used to transfer measurement data from the
BAMS platform. When these cases occur, it is important to know which platform is acting as server and
which is acting as the client.
Note
1.
Install the secure interface software package on Cisco MGC platforms controlled by a particular
BAMS. At this point both the secure and non-secure interface software exist and are enabled on the
Cisco MGC platform. This allows the BAMS machines to continue to communicate with the Cisco
MGC platforms using the non-secure interfaces.
2.
Once the Cisco MGC platforms controlled by the BAMS platform have the secure interface software
installed, install the secure interface package on the BAMS platform. As the BAMS machine is
re-configured (with the secure interface setup script) and rebooted, it will begin to communicate
with the Cisco MGC platforms using the secure interfaces.
3.
After the BAMS platform is updated and is using the secure interfaces, the non-secure interfaces on
the Cisco MGC and BAMS platforms can be disabled. This is done on the Cisco MGC and BAMS
platforms, using the scripts provided (toggle_ftp.sh and toggle_ftp.sh).
From the server/client table, note that the HSI platform does not act as a secure interface client, and
serves as the secure interface server only to the Cisco MGC Node Manager application. When installing
the secure interface software, the sequence of installation on the HSI is independent of the installation
on Cisco MGC or BAMS platforms.
Export Control Splash Screens
A warning message screen announcing that the product contains export controlled encryption code with
U.S. government export restrictions is displayed at the following times:
Note
•
During the installation of the encryption software (CSCOk9000).
•
As part of the startup script for the Cisco MGC, BAMS and HSI.
This warning is displayed if the SSH software is installed on the machine, regardless of whether the
Cisco PGW 2200, BAMS, and HSI are actually using the secure interfaces. You have the option to
enable Telnet and FTP and use the nonsecure interfaces, even if SSH is available.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-9
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
CSCOk9000 Security Package Functions
A system can have different components such as the Cisco PGW 2200, BAMS, and HSI, that need the
CSCOk9000 package,
When the CSCOk9000 security package is installed, it will do its work without user intervention until
the end of the installation process.
When the CSCOk9000 security package is installed, it loads the SSH daemon onto the disk and
configures it to start up the next time the system is rebooted.
Note
The SSH code is installed in a directory under /opt/SSH.
Connecting to the Cisco PGW 2200, BAMS, and HSI
For secure Telnet sessions, you can connect to the Cisco PGW 2200, BAMS, and HSI by using SSH (for
example, to run MML).
For file transfers or using scp, you can connect to the Cisco PGW 2200, BAMS, and HSI by using sftp
(for example, to run MGC_setup).
Telnet and FTP Toggle Options
After the CSCOk9000 package is installed, you have the option to toggle the operation of the Telnet and
FTP programs using two scripts—toggle_telnet.sh and toggle_ftp.sh. These scripts are located in the
/opt/sun_install directory.
To turn the FTP service on, run the toggle_ftp.sh script by typing the following command and pressing
Enter:
/opt/sun_install/toggle_ftp.sh enable <filename>
To turn the FTP service off, run the toggle_ftp.sh script by typing the following command and pressing
Enter:
/opt/sun_install/toggle_ftp.sh disable <filename>
Installing the CSCOk9000 Security Package
Following are detailed procedures for installing the CSCOk9000 security package. It is important to
install the CSCOk9000 security package according to the following sequence:
1.
Installing CSCOk9000 on the Cisco PGW 2200 Host, page 4-11
2.
Installing the CSCOk9000 on BAMS, page 4-15
3.
Installing CSCOk9000 on HSI, page 4-18
4.
Securing the Networks, page 4-18
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-10
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Installing CSCOk9000 on the Cisco PGW 2200 Host
Note
Always begin the installation on the standby host (Host B).
To install the CSCOk9000 security package on the Cisco PGW 2200 host:
Step 1
On Host B, log in as root.
Step 2
Shut down the Cisco MGC. Enter the following command:
/etc/init.d/CiscoMGC stop
Step 3
If CSCOh013 is already installed on your Cisco PGW 2200 host, skip this step and go to Step 4.
If the CSCOh013 is not yet installed on your Cisco PGW 2200 host, you must first install it before
installing the CSCOk9000 security package. Follow the CSCOh013 installation procedures in the
“Installing the Cisco Security Package (CSCOh013)” section on page 3-16 in Chapter 3, “Cisco MGC
Software Release 9 Installation.”
When the CSCOh013 security package installation is complete, text similar to the following is
displayed:
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Note
Step 4
If you are planning to install CSCOk9000, do not reboot after installing the CSCOh013
security package. You will be prompted to reboot after the installation of CSCOk9000.
Install the CSCOk9000 security package on the standby Cisco PGW 2200 first (Host B). Enter the
following command:
pkgadd -d CSCOk9000.pkg
Text similar to the following is displayed:
The following packages are available:
1 CSCOk9000
Security package (ssh, sftp) for Solaris 8
(sparc) 1.0(0.4)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 5
Type all and press Enter to process all packages.
Step 6
Enter the following command to change the current directory:
cd /opt/sun_install
Step 7
Type the following command to run the SSH script on Host B:
./CiscoSSH.sh install /tmp/SSH.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-11
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Text similar to the following is displayed:
*** NOTE ***
Your ftp and telnet (ie. non-secure) interfaces
have NOT been disabled! When you are ready to fully
secure your system, you should disable these interfaces
with the commands 'toggle_ftp.sh disable' and
'toggle_telnet.sh disable'
*** END NOTE ***
End of SSH installation...
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Note
Step 8
If you do not get the above message about rebooting, the installation might have failed — call
Cisco TAC for assistance.
Reboot the standby host (Host B). Enter the following command:
reboot
Rebooting may take about five minutes.
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 9
Disable FTP access to your system. Enter the following command:
/opt/sun_install/toggle_ftp.sh disable /tmp/toggle_ftp.log
Step 10
Disable Telnet access to your system. Enter the following command:
/opt/sun_install/toggle_telnet.sh disable /tmp/toggle_telnet.log
Note
Step 11
If you run the above command, the access to the Solaris box is disabled.
Start Cisco MGC on Host B. Enter the following command:
/etc/init.d/CiscoMGC start
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-12
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Note
Step 12
After rebooting Host B, you may find that the Cisco MGC application may be already running.
This is because the Cisco MGC start script is located in one of the /etc/rcX.d directories. This
causes the application to start and stop automatically when Unix is started or stopped.
Fail over to the standby host (Host B). Log in as mgcusr on Host A (Active now), enter mml to get in
MML mode, and enter the following MML command:
sw-over::confirm
Step 13
Install the CSCOh013 security package first if it is not yet installed on Host A. If CSCOh013 is already
installed, go to Step 14.
Follow the CSCOh013 installation procedures in the section “Installing the Cisco Security Package
(CSCOh013)” section on page 3-16 in Chapter 3, “Cisco MGC Software Release 9 Installation,” of the
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.
When the CSCOh013 security package installation is complete, text similar to the following is
displayed:
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Note
Step 14
If you will be installing CSCOk9000, do not reboot after installing the CSCOh013 security
package. You will be prompted to reboot after the installation of CSCOk9000.
Install the CSCOk9000 security package on Host A. Log in Host A again as root. Enter the following
command:
pkgadd -d CSCOk9000.pkg
Text similar to the following is displayed:
The following packages are available:
1 CSCOk9000
Security package (ssh, sftp) for Solaris 8
(sparc) 1.0(0.4)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 15
Type all and press Enter to process all packages.
Text similar to the following is displayed:
cd ../sun_install/
pwd
/opt/sun_install
./CiscoSSH.sh install /tmp/SSH.log
Output will be logged in /tmp/SSH.log
You are running as root - Good...
Step 16
Enter the following command to change the current directory:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-13
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
cd /opt/sun_install
Step 17
Type the following command to run the SSH script on Host A:
./CiscoSSH.sh install /tmp/SSH.log
Text similar to the following is displayed:
*** NOTE ***
Your ftp and telnet (ie. non-secure) interfaces
have NOT been disabled! When you are ready to fully
secure your system, you should disable these interfaces
with the commands 'toggle_ftp.sh disable' and
'toggle_telnet.sh disable'
*** END NOTE ***
End of SSH installation...
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Step 18
Reboot Host A. Log in as root and enter the following command:
reboot
Rebooting may take about five minutes.
Step 19
Disable FTP access to your system. Enter the following command:
/opt/sun_install/toggle_ftp.sh disable /tmp/toggle_ftp.log
Step 20
Disable Telnet access to your system. Enter the following cmmand:
/opt/sun_install/toggle_telnet.sh disable /tmp/toggle_telnet.log
Note
Step 21
If you run the above command, the access to the Solaris box is disabled.
Fail-over again to the standby host (Host A). Log in as mgcusr on Host B and enter the following MML
command:
sw-over::confirm
The CSCOk9000 security package installation on Cisco PGW 2200 is now complete.
To install SSH on BAMS, continue to the “Installing the CSCOk9000 on BAMS” section on page 4-15.
To install SSH on HSI, continue to the “Installing CSCOk9000 on HSI” section on page 4-18.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-14
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Installing the CSCOk9000 on BAMS
After the CSCOk9000 security package is installed on the Cisco PGW 2200 platform, it can be installed
on BAMS. BAMS will use SFTP to transfer files after the ./setupSSH.sh script is done installing the
software. Install the CSCOk9000 security package on BAMS to install the secure shell on the system.
Caution
For BAMS to properly create CDR records and measurements, all components in the network must have
both CSCOk900 and CSCOh013 either installed or not installed.
The BAMS startup script includes a splash screen warning that the system is running with export
controlled encryption software installed.
Note
Run the /opt/install/enableFTPClient.sh script each time SSH is re-installed on Cisco PGW 2200 or
BAMS. If only SSH on the Cisco PGW 2200 host is changed, then you only need to enter the Cisco PGW
2200 host names when running this script. If the SSH on BAMS is changed, you must enter all Cisco
PGW 2200 and BAMS host names.
To install the CSCOk9000 package on BAMS:
Step 1
Log in as bams on BAMS 1.
Step 2
Shut down BAMS 1. Enter the following command:
stop_system
Text similar to the following is displayed:
Terminating BAMS
waiting for MGR to shut down...
$
Step 3
Log in as root.
Step 4
Install the CSCOh013 security package on BAMS 1 and run the CiscoSec.sh install /tmp/security.log
script.
Follow the CSCOh013 installation procedures in the section “Installing the Cisco Security Package
(CSCOh013)” in Chapter 3, “Cisco MGC Software Releases 9.2(x) and 9.3(x)”, of the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
When the CSCOh013 security package installation is complete, text similar to the following is
displayed:
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Note
If you will be installing CSCOk9000, do not reboot after installing the CSCOh013 security
package. You will prompted to reboot after the installation of CSCOk9000.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Step 5
Install the CSCOk9000 security package on BAMS 1. Enter the following command:
pkgadd -d CSCOk9000.pkg
Text similar to the following is displayed:
The following packages are available:
1 CSCOk9000
Security package (ssh, sftp) for Solaris 8
(sparc) 1.0(0.4)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 6
Type all and press Enter to process all packages.
Step 7
Enter the following command
cd /opt/sun_install
Step 8
Enter the following command to run the SSH script:
./CiscoSSH.sh install /tmp/ssh.log
Text similar to the following is displayed:
Output will be logged in
/tmp/SSH.log
You are running as root - Good...
*** NOTE ***
Your ftp and telnet (ie. non-secure) interfaces
have NOT been disabled! When you are ready to fully
secure your system, you should disable these interfaces
with the commands 'toggle_ftp.sh disable' and
'toggle_telnet.sh disable'
*** END NOTE ***
End of SSH installation...
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Step 9
Reboot BAMS 1. Enter the following command:
reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-16
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Step 10
To configure SSH on BAMS 2, log in as bams on BAMS 2.
Step 11
Shut down BAMS 2. Enter the following command:
stop_system
Text similar to the following is displayed:
Terminating BAMS
waiting for MGR to shut down...
$
Step 12
Log in as root.
Step 13
Install the CSCOh013 security package on BAMS 2 and run the CiscoSec.sh install /tmp/security.log
script.
Follow the CSCOh013 installation procedures in the section “Installing the Cisco Security Package
(CSCOh013)” in Chapter 3, “Cisco MGC Software Releases 9.2(x) and 9.3(x)”, of the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
When the CSCOh013 security package installation is complete, text similar to the following is
displayed:
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Note
Step 14
If you will be installing CSCOk9000, do not reboot after installing the CSCOh013 security
package. You will prompted to reboot after the installation of CSCOk9000.
Install the CSCOk9000 security package on BAMS 2. Enter the following command:
pkgadd -d CSCOk9000.pkg
Text similar to the following is displayed:
The following packages are available:
1 CSCOk9000
Security package (ssh, sftp) for Solaris 8
(sparc) 1.0(0.4)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 15
Type all and press Enter to process all packages.
Step 16
Enter the following command
cd /opt/sun_install
Step 17
Enter the following command to run the SSH script:
./CiscoSSH.sh install /tmp/ssh.log
Text similar to the following is displayed:
Output will be logged in
/tmp/SSH.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-17
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
You are running as root - Good...
*** NOTE ***
Your ftp and telnet (ie. non-secure) interfaces
have NOT been disabled! When you are ready to fully
secure your system, you should disable these interfaces
with the commands 'toggle_ftp.sh disable' and
'toggle_telnet.sh disable'
*** END NOTE ***
End of SSH installation...
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Step 18
Reboot BAMS 2. Enter the following command:
reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
The installation of the CSCOk9000 security package on BAMS is now complete. To install the
CSCOk9000 security package on HSI, continue to the “Installing CSCOk9000 on HSI” section.
Continue to the “Securing the Networks” section on page 4-18 to secure your networks.
Installing CSCOk9000 on HSI
You can install the CSCOhk9000 security package on any HSI machine on the system. The procedure
for installing SSH on HSI is the same as the procedure for installing the CSCOk9000 security package
on the Cisco PGW 2200 (see the “Installing CSCOk9000 on the Cisco PGW 2200 Host” section on
page 4-11).
Securing the Networks
You must have completed the installation of the CSCOhk9000 security package on your network (which
can consist of Cisco PGW 2200, BAMS, and HSI) before securing your network.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-18
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Securing the Cisco PGW 2200
To secure the Cisco PGW 2200:
Step 1
Before you begin, verify that the last CDR has been pulled into BAMS.
You must be logged in as root. To verify that the last CDR has been pulled into BAMS, type the
following command and press Enter to go to the directory:
/opt/CiscoMGC/var/spool
Step 2
Type the following command and press Enter to verify the CDR:
ls -l cdr_<yyyymmdd>
Where <yyyymmdd> represents the current date, entered in the following format:
yyyy = year
mm = month
dd = day
A list of files is displayed when you enter this command.
Step 3
Check the list of files that is displayed for the last finished filename preceded by a period (.) and write
down the file name—you will need this information later.
Step 4
On the Cisco PGW 2200 Host B (the standby host), as root, type the following command and press
Enter to change directory:
cd /opt/sun_install
Step 5
Type the following command and press Enter to toggle FTP off:
toggle_ftp.sh disable <filename>
Note
<filename> is a name that you selected.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Step 6
Type the following command and press Enter to toggle Telnet off:
toggle_telnet.sh disable <filename>
Note
<filename> is a name that you select.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Step 7
On Host A (the active host), while logged in as root, type the following command and press Enter to
change directory:
cd /opt/sun_install
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-19
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Step 8
Type the following command and press Enter to toggle FTP off:
toggle_ftp.sh disable <filename>
Note
<filename> is a name that you selected.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Step 9
Type the following command and press Enter to toggle Telnet off:
toggle_telnet.sh disable <filename>
Note
<filename> is a name that you selected.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Step 10
Verify that Telnet and FTP are off. Telnet or FTP to you Cisco PGW 2200 platform. If Telnet and FTP
are turned off, you will get the following error message:
Connection refused.
This completes the procedures for securing your Cisco PGW 2200. If you have BAMS on your network,
continue to the “Securing the Cisco PGW 2200” section on page 4-19.
Securing BAMS
To secure BAMS on your network:
Step 1
Log in to the standby BAMS by typing the following and pressing Enter:
bams
Step 2
The following steps require you to use MML commands. To use MML commands, type the following
and press Enter:
mml
Step 3
Enter the node of the Cisco PGW 2200 that is being changed. At the MML command line type the
following and press Enter:
set-mode:<x>:
Where <x> is a number between 1 through 8.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-20
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Note
Step 4
In this example, the node number is 2.
Check for alarms. Type the following command and press Enter:
rtrv-alms
Text similar to the following is displayed:
Billing and Measurements Server - BAMS-00 2003-02-12 15:12:05
B RTRV
02/12/03 14:58:14 *C POL402: Cannot connect to unit va-hoover
02/12/03 15:00:15 *C POL401: Max FTP failures for one file reached
02/12/03 15:00:25 *C POL402: Cannot connect to unit va-hoover_b
02/12/03 15:02:36 *C POL402: Cannot connect to unit va-fish
02/12/03 15:04:46 *C POL402: Cannot connect to unit va-fish_b
;
B COMPLD
;
Note
Look for the line containing POL402. POL402 indicates the presence of an alarm. Proceed to
Step 5.
In this text display, “va-hoover” and “va-fish” are Cisco PGW 2200 and BAMS host name
examples.
Step 5
Log in as root.
Step 6
Type the following command and press Enter to change directory:
cd /opt/sun_install
Step 7
Type the following command to toggle FTP off:
toggle_ftp.sh disable <filename>
Note
<filename> is a name that you selected.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Done!
Step 8
Type the following command and press Enter to toggle Telnet off:
toggle_telnet.sh disable <filename>
Note
<filename> is a name that you selected.
Text similar to the following is displayed:
You are running as root - Good...
Operating System: SunOS 5.8
Disable ftp in inetd.conf file
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-21
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Done!
Step 9
On the active host (BAMS 1), log in as bams.
Step 10
Repeat Step 2 through Step 8.
Step 11
On the standby BAMS, while logged in as root, type the following command and press Enter to change
the directory:
cd /opt/install
Step 12
As root, enter the following command to set up the SSH process:
setupSSH.sh
Text similar to the following is displayed:
BAMS is installed, proceeding with SSH configuration
Warning:
Before running this script, SSH must be installed on all PGW and BAMS hosts
This script will disable the standard FTP client on BAMS and set up
SSH connections from BAMS to PGW and from BAMS to BAMS.
If you want to use the standard FTP client, it is still available
in the file /usr/bin/ftp.orig
Do you want to continue [y/n]:
Step 13
Type y (yes) to continue and press Enter.
Text similar to the following is displayed:
Sun Microsystems Inc.
SunOS 5.6
Generic August 1997
Warning:
Before running this script, SSH must be installed on all PGW and BAMS hosts.
This script will reset the existing known hostkeys
and user keys for bams user for each host entered during this session.
You need to run this script every time the PGW or BAMS is re-installed.
You also need to run this script if SSH is re-installed on PGW or BAMS.
Do you want to continue [y/n]:
Step 14
Type y (yes) to continue and press Enter.
Text similar to the following is displayed:
Generating security keys, this will take a couple of minutes...
Generating public/private rsa key pair.
Your identification has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa.
Your public key has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa.pub.
The key fingerprint is:
32:8e:10:10:98:2a:35:8a:18:bb:e6:3e:a1:54:d9:27 bams@va-pine
Generating public/private dsa key pair.
Your identification has been saved in /opt/CiscoBAMS/local/.ssh/id_dsa.
Your public key has been saved in /opt/CiscoBAMS/local/.ssh/id_dsa.pub.
The key fingerprint is:
32:dd:2d:51:e3:b4:9b:41:29:49:1a:f2:49:6f:e4:29 bams@va-pine
You will be prompted for the user name and password for each PGW
or BAMS host.
Please remember to enter both PGW host names for a failover pair.
You also need to enter the other BAMS host if this is a redundant setup.
Please enter a PGW or BAMS host name, or q to quit
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-22
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Enter a host name now:
Step 15
Type host name PGW1 and press Enter.
Text similar to the following is displayed:
Please enter a PGW or BAMS host name, or q to quit
Enter a host name now:
Step 16
Type the host name mgcusr (the login name of PGW1) and press Enter.
Text similar to the following is displayed:
Are you sure you want to continue connecting (yes/no)? yes
Step 17
Type y (yes) and press Enter.
Text similar to the following is displayed:
mgcusr@<hostname>'s password:
id_dsa.pub
100% |*****************************|
Step 18
602
00:00
Type the password and press Enter.
Text similar to the following is displayed:
mgcusr@<BAMS 1>'s password:
Step 19
Type y (yes) again and press Enter.
Text similar to the following is displayed:
mgcusr on <BAMS> successfully configured
Do you want to configure second interface for <BAMS>? n
Step 20
Step 21
You can answer either y (yes) or n (no):
a.
Yes (configuring a second interface) is optional. If you answer y, repeat Step 1 through Step 19.
b.
If you answer no, proceed to Step 21.
Repeat Step 15 through Step 19 for additional Cisco PGW 2200 nodes.
Text similar to the following is displayed:
mgcusr on <BAMS1> successfully configured
Do you want to configure second interface for <BAMS1>? n
Step 22
Type n (no) and press Enter.
Text similar to the following is displayed:
Please enter a PGW or BAMS host name, or q to quit
Enter a host name now:
Step 23
While still on the standby BAMS, type the active BAMS unit information (BAMS name, BAMS login
password).
Step 24
When all the BAMS interfaces have been configured, type q to quit and press Enter.
Text similar to the following is displayed:
Done
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-23
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Note
Look out for the following error message. If some hosts were not configured, follow the
recommendation in this message.
Failed to configure some hosts. Please check for SSH installation on these hosts and/or the user
name and password for these hosts.
Step 25
Log in to the active BAMS as root.
Step 26
Change the directory. Type the following command and press Enter:
cd /opt/install
Step 27
Type the following command and press Enter:
setupSSH.sh
Text similar to the following is displayed:
BAMS is installed, proceeding with SSH configuration
Warning:
Before running this script, SSH must be installed on all PGW and BAMS hosts
This script will disable the standard FTP client on BAMS and set up
SSH connections from BAMS to PGW and from BAMS to BAMS.
If you want to use the standard FTP client, it is still available
in the file /usr/bin/ftp.orig
Do you want to continue [y/n]:
Step 28
Type y to continue and press Enter.
Text similar to the following is displayed:
Sun Microsystems Inc.
SunOS 5.6
Generic August 1997
Warning:
Before running this script, SSH must be installed on all PGW and BAMS hosts.
This script will reset the existing known hostkeys
and user keys for bams user for each host entered during this session.
You need to run this script every time the PGW or BAMS is re-installed.
You also need to run this script if SSH is re-installed on PGW or BAMS.
Do you want to continue [y/n]:
Step 29
Type y (yes) to continue and press Enter.
Text similar to the following is displayed:
Generating security keys, this will take a couple of minutes...
Generating public/private rsa key pair.
Your identification has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa.
Your public key has been saved in /opt/CiscoBAMS/local/.ssh/id_rsa.pub.
The key fingerprint is:
32:8e:10:10:98:2a:35:8a:18:bb:e6:3e:a1:54:d9:27 bams@va-pine
Generating public/private dsa key pair.
Your identification has been saved in /opt/CiscoBAMS/local/.ssh/id_dsa.
Your public key has been saved in /opt/CiscoBAMS/local/.ssh/id_dsa.pub.
The key fingerprint is:
32:dd:2d:51:e3:b4:9b:41:29:49:1a:f2:49:6f:e4:29 bams@va-pine
You will be prompted for the user name and password for each PGW
or BAMS host.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-24
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Please remember to enter both PGW host names for a failover pair.
You also need to enter the other BAMS host if this is a redundant setup.
Please enter a PGW or BAMS host name, or q to quit
Enter a host name now:
Step 30
Type host name PGW1 and press Enter.
Text similar to the following is displayed:
Please enter a PGW or BAMS host name, or q to quit
Enter a host name now:
Step 31
Type the host name mgcusr (the login name of PGW1) and press Enter.
Text similar to the following is displayed:
Are you sure you want to continue connecting (yes/no)? yes
Step 32
Type y (yes) and press Enter.
Text similar to the following is displayed:
mgcusr@<hostname>’s password:
id_dsa.pub
100% |*****************************|
602
00:00
Type the password and press Enter.
Text similar to the following is displayed:
mgcusr@<BAMS 1>'s password:
Step 33
Type y (yes) again and press Enter.
Text similar to the following is displayed:
mgcusr on <BAMS> successfully configured
Do you want to configure second interface for <BAMS>? n
Step 34
Step 35
You can answer either y (yes) or n (no):
a.
Yes (configuring a second interface) is optional. If you answer y, repeat Step 1 through Step 19.
b.
If you answer no, proceed to Step 21.
Repeat Step 15 through Step 19 for additional Cisco PGW 2200 nodes.
Text similar to the following is displayed:
mgcusr on <BAMS1> successfully configured
Do you want to configure second interface for <BAMS1>? n
Step 36
Type n (no) and press Enter.
Text similar to the following is displayed:
Please enter a PGW or BAMS host name, or q to quit
Enter a host name now:
Step 37
While still on the active BAMS, type the standby BAMS unit information (BAMS name, BAMS login
password).
Step 38
When all the BAMS interfaces have been configured, type q to quit and press Enter.
Text similar to the following is displayed:
Done
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-25
Chapter 4
Cisco PGW 2200 Security Enhancements
Installing the CSCOk9000 Security Package
Step 39
Go to the active Cisco PGW 2200 (Host A) in the “Securing the Cisco PGW 2200” section on page 4-19
and repeat Step 1 and Step 2.
Text similar to the following is displayed:
-rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcusr
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
mgcgrp
182
182
182
182
182
182
182
182
182
182
182
182
182
182
182
182
182
182
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
Feb
12
12
12
12
12
12
12
12
12
12
12
12
12
12
12
12
12
12
14:29
14:34
14:39
14:44
14:49
14:54
14:59
15:04
15:09
15:14
15:19
15:24
15:30
15:35
15:40
15:45
15:50
15:55
cdr_20030212142403_037281.finished
cdr_20030212142903_037282.finished
cdr_20030212143403_037283.finished
cdr_20030212143903_037284.finished
cdr_20030212144403_037285.finished
cdr_20030212144903_037286.finished
cdr_20030212145403_037287.finished
cdr_20030212145903_037288.finished
cdr_20030212150403_037289.finished
cdr_20030212150903_037290.finished
cdr_20030212151403_037291.bin
cdr_20030212151904_037292.bin
cdr_20030212152434_037293.bin
cdr_20030212153004_037294.bin
cdr_20030212153504_037295.bin
cdr_20030212154004_037296.bin
cdr_20030212154504_037297.bin
cdr_20030212155004_037298.bin
Step 40
Make sure that the CDR file number you noted down in Step 3 has changed from .bin to .finished.
Step 41
Check for alarms on BAMS. Type the following command and press Enter:
<bams hostname> rtrv-alms
Text similar to the following is displayed:
Billing and Measurements Server - BAMS-00 2003-02-12 16:02:08
B RTRV
02/12/03 15:02:36 *C POL402: Cannot connect to unit <bams1 hostname>
02/12/03 15:04:46 *C POL402: Cannot connect to unit <bams2 hostname>
;
B COMPLD
Note
Step 42
The CDR file POL402 (which indicates the presence of an alarm, shown in Step 4) for the active
Cisco PGW 2200 and standby BAMS should be gone.
Verify that both BAMS 1 and BAMS 2 are communicating with each other.
CDR file POL329 indicates that the active BAMS (BAMS 1) is sending information to the standby
BAMS (BAMS 2).
Note
Step 43
Since BAMS polls the Cisco PGW 2200 at regular intervals, you may still see an alarm for a
while. When you do, wait a few minutes and check the logs (see Step 43).
To check the logs for alarms (the log name within this directory is syslog), change directory to the
following:
cd /opt/CiscoBAMS/files/s0x
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-26
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Uninstalling the CSCOk9000 Security Package
Note
x in s0x is the node you are in.
The process for securing your network is now complete.
Uninstalling the CSCOk9000 Security Package
If you want to uninstall the CSCOk9000 security package on the PGW, follow the following detailed
procedures.
Step 1
Remove the CSCOk9000 security package. Enter the following command and press Enter.
pkgrm CSCOk9000
Text similar to the following is displayed:
The following package is currently installed:
CSCOk9000 Security package (ssh, sftp) for Solaris 8
(sparc) 1.0(2)PGWR
Do you want to remove this package?
Step 2
Enter y and press Enter to confirm the removal.
Text similar to the following is displayed:
Removing installed package instance <CSCOk9000>
This package contains scripts which will be executed with super-user permission during the
process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q]
Step 3
Enter y and press Enter to continue with the removal of this package.
Text similar to the following is displayed:
Verifying package dependencies.
Processing package information.
Executing preremove script.
Logfile is /var/adm/CSCOh090.uninstall.log
*** Removal of SSH update package started...Fri Oct 12 03:02:00 EDT 2007 *** You are not
allowed to remove this package until you run the uninstall security script To do this:
cd /opt/sun_install
./CiscoSSH.sh uninstall /tmp/uninstall_SSH.log
Once that script completes correctly, you may remove this package from the machine
Removal of <CSCOk9000> was terminated due to user request.
Step 4
Enter the following command to change the current directory and press Enter.
cd /opt/sun_install
Step 5
Enter the following command to run the uninstall security script and press Enter.
./CiscoSSH.sh uninstall /tmp/uninstall_SSH.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-27
Chapter 4
Cisco PGW 2200 Security Enhancements
Uninstalling the CSCOk9000 Security Package
Text similar to the following is displayed:
Output will be logged in
/tmp/uninstall_SSH.log
You are running as root - Good...
Operating System: SunOS 5.8
**************************************************************
**************************************************************
**************************************************************
***
***
***
WARNING
WARNING
WARNING
WARNING
***
***
***
*** This product contains cryptographic features and is
***
*** subject to United States and local country laws
***
*** governing import, export, transfer and use
***
*** Delivery of Cisco cryptographic products does not
***
*** imply third-party authority to import, export,
***
*** distribute or use encryption.
***
*** Importers, exporters, distributors and users are
***
*** responsible for compliance with U.S. and local
***
*** country laws.
***
***
***
*** By using this product you agree to comply with
***
*** applicable laws and regulations. If you are unable
***
*** to comply with U.S. and local laws, return this
***
*** product immediately.
***
***
***
*** A summary of U.S. laws governing Cisco cryptographic
***
*** products may be found at:
***
***
***
*** http://www.cisco.com/wwl/export/crypto/tool/stqrg.html ***
***
***
*** If you require further assistance please contact us
***
*** us by sending email to [email protected]
***
***
***
***
WARNING
WARNING
WARNING
WARNING
***
***
***
**************************************************************
**************************************************************
**************************************************************
Do you want to continue? [n]:
Step 6
Enter y to continue and press Enter.
Text similar to the following is displayed:
Restoring system to original configuration...
The following package is currently installed:
ANDIrand
random-0.7
(sparc) 0.7
Do you want to remove this package?
Step 7
Enter y to confirm the removal and press Enter.
Text similar to the following is displayed:
Removing installed package instance <ANDIrand>
This package contains scripts which will be executed with super-user permission during the
process of removing this package.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-28
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Fallback Procedures
Do you want to continue with the removal of this package [y,n,?,q]
Step 8
Enter y to continue the removal of the package and press Enter.
Verifying package dependencies.
Processing package information.
Executing preremove script.
Removing pathnames in class <km64>
/usr/kernel/drv/sparcv9/random
/usr/kernel/drv/sparcv9 <shared pathname not removed>
Removing pathnames in class <sed>
Modifying /etc/devlink.tab
Removing pathnames in class <none> /usr/kernel/drv/random.conf /usr/kernel/drv/random
/usr/kernel/drv <shared pathname not removed> /usr/kernel <shared pathname not removed>
/usr <shared pathname not removed> /etc/rc2.d/S60random /etc/rc2.d <shared pathname not
removed> /etc/rc0.d/K50random /etc/rc0.d <shared pathname not removed> /etc/init.d/random
/etc/init.d <shared pathname not removed> /etc <shared pathname not removed>
Executing postremove script.
Updating system information.
Removal of <ANDIrand> was successful.
Backup directory is being removed
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Done!
Step 9
Reboot the system. Enter the following command and press Enter.
reboot
The uninstallation of CSCOk9000 security package is now complete.
Fallback Procedures
Perform fallback procedures if you have problems with the installation of the CSCOk9000 security
package on the Cisco PGW 2200 or BAMS.
If you have BAMS installed in your system, make sure you perform the fallback procedures on the Cisco
PGW 2200 first, then do the procedures on BAMS.
Procedures for Cisco PGW 2200
Do the following procedures if you encounter problems with CSCOk9000 security package installation
on Cisco PGW 2200:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-29
Chapter 4
Cisco PGW 2200 Security Enhancements
Fallback Procedures
Step 1
Log in to the standby Cisco MGC as root and stop the system by entering the following command:
/etc/init.d/CiscoMGC stop
Step 2
From the /opt/sun/install directory, enable FTP and Telnet by entering the following commands:
toggle_ftp.sh enable /tmp/enable.log
toggle_telnet.sh enable /tmp/enable.log
Step 3
Run the uninstall security script:
cd /opt/sun_install
./CiscoSSH.sh uninstall /tmp/uninstall_SSH.log
Step 4
Uninstall CSCOk9000. Enter the following command:
pkgrm CSCOk9000
Step 5
In /opt/sun_install directory, enter the following command:
CiscoSec.sh uninstall /tmp/security.log
Step 6
Uninstall CSCOh013. Enter the following command:
pkgrm CSCOh013
Step 7
Reboot the standby Cisco MGC. Enter the following command:
reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 8
Repeat Step 1 through Step 9 on the active Cisco MGC.
The fallback procedures for Cisco PGW 2200 is now complete. Proceed to the “Procedures for BAMS”
section if you have BAMS.
Procedures for BAMS
Do the following procedures if you encounter problems with the installation of the CSCOk9000 security
package on BAMS:
Step 1
Log in to the standby BAMS unit as bams and stop the system by entering the following command:
stop_system
Text similar to the following is displayed:
Terminating BAMS
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-30
OL-1150-15
Chapter 4
Cisco PGW 2200 Security Enhancements
Fallback Procedures
waiting for MGR to shut down...
$
Step 2
On the standby BAMS, log in as root.
Step 3
From the /opt/sun/install directory, enable FTP and Telnet by entering the following commands:
toggle_ftp.sh enable /tmp/enable.log
toggle_telnet.sh enable /tmp/enable.log
Step 4
Run the following script:
/opt/install/enableFTPClient.sh
Text similar to the following is displayed:
# /opt/install/enableFTPClient.sh
FTP Client restored
Step 5
Run the uninstall security script:
cd /opt/sun_install
./CiscoSSH.sh uninstall /tmp/uninstall_SSH.log
Step 6
Uninstall CSCOk9000. Enter the following command:
pkgrm CSCOk9000
Note
Step 7
If you wish to uninstall CSCOh013, then proceed to Step 7 through Step 8. If not, then skip to
Step 9 to reboot the BAMS unit.
In /opt/sun_install directory, enter the following command:
CiscoSec.sh uninstall /tmp/security.log
Step 8
Uninstall CSCOh013. Enter the following command:
pkgrm CSCOh013
Step 9
Reboot the BAMS unit. Enter the following command:
reboot
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Step 10
Repeat Step 1 through Step 9 on the active BAMS unit.
The fallback procedures for BAMS is now complete.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
4-31
Chapter 4
Cisco PGW 2200 Security Enhancements
Alarms and Messages
Alarms and Messages
When you attempt to run SSH, the program requires a confirmation to continue. If you fail to log in
successfully (for example, you typed the wrong password), this information will be logged. The CIAgent
raises an SNMP alarm based on the failed login attempt.
Note
These traps apply to the Cisco MGC platform as well as to BAMS and HSI.
When a login failure is detected, an SNMP trap is generated. For example:
snmpTrapOID.0 = siLogMatchTrap
siLogName.1 = /var/log/authlog
siLogTrapTextLine.1 = Oct 9 13:42:51 va-baltimore sshd[5698]: [ID 800047
auth.info] Failed password for mgcusr from 161.44.86.29 port 40781 ssh2
Where:
•
siLogName object identifies the log file where the login failures are logged.
•
siLogTrapTextLine object is the exact line from the log file that reports the login failure.
A UNIX syslog file, /var/log/authlog, is used to log all access to the system by SSH. Both successful
and failed login attempts are logged in this file. An SNMP trap will be generated for failed login
attempts.
Note
New log files are started on Sundays.
There are five files related to the authlog file in the /var/log directory:
•
authlog - the most recent logs since last Sunday.
•
authlog.0 - logs from two Sundays ago to last Sunday.
•
authlog.1 - logs from three Sundays ago to two Sundays ago.
•
authlog.2 - logs from four Sundays ago to three Sundays ago.
•
authlog.3 - logs from five Sundays ago to four Sundays ago.
Log files which generated more than five Sundays ago are automatically deleted.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
4-32
OL-1150-15
CH A P T E R
5
Configuring the Cisco MGC Software
This chapter describes how to configure Release 9 of the Cisco Media Gateway Controller (MGC)
software.
Quick Guide to Configuring the Cisco MGC Software
Note
The Cisco MGC software files and processes are located in the /opt/CiscoMGC directory.
The following table provides an overview of the configuration procedure. Go to the page indicated in
the right most column for more detailed information.
Table 5-1
Quick Guide to Configuring the Cisco MGC Software
Task
Detailed Procedures
Before You Start
on page 5-3
Initial Cisco MGC Software Configuration
on page 5-4
– Using the Cisco MGC Environment Configuration Tool
Configuring Groups and Users
on page 5-8
on page 5-10
– Verifying the mgcgrp Group
on page 5-10
– Adding a User with Full MML Privileges
on page 5-11
– Adding a User with Minimal MML Privileges
on page 5-11
Configuring SNMP Support Resources
– Migrating the SNMP Configuration to a More Secure
on page 5-12
on page 5-13
Environment (for MGC 9.3(2) or Later)
– Setting up the SNMP Community for Software Releases
on page 5-24
Before Cisco MGC 9.3(2)
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-1
Chapter 5
Configuring the Cisco MGC Software
Quick Guide to Configuring the Cisco MGC Software
Table 5-1
Quick Guide to Configuring the Cisco MGC Software (continued)
Task
Detailed Procedures
Configuring the Execution Environment
on page 5-27
– Changing XECfgParm.dat File Parameters
on page 5-27
– Changing XECfgParm.dat File Parameters in a Running
on page 5-28
Fault Tolerant System
– Configuring Basic System Information
on page 5-29
– Specifying IP Addresses
on page 5-31
– Configuring Engine Parameters
on page 5-32
– Enabling Call Screening
on page 5-35
– Configuring Call Detail Record File Output
on page 5-36
– Configuring the Clearing Location and Default
on page 5-38
Location Parameters
on page 5-38
– Configuring the Clearing Location and Default
Location Parameters
– Configuring Switchover
on page 5-41
on page 5-43
– Initializing the Provisioning Object Manager
Configuring SCP Queries
on page 5-45
– Before You Start
on page 5-45
– Configuring the trigger.dat File Attributes
on page 5-45
Initializing the Call Screening Database
on page 5-57
– .odbc.ini File Information
on page 5-58
– Setting Up Replication
on page 5-58
– Verifying Database Replication
on page 5-61
– Troubleshooting the Main Memory Database
on page 5-61
Replication
Note
Configuring Cisco SLTs
on page 5-63
Configuring Disk Monitor During Initial Software Configuration
on page 5-64
Configuring the Data Dumper
on page 5-65
Configuring the Data Dumper to Support BAMS
on page 5-66
For further information on configuring the Cisco MGC software, see the Cisco Media Gateway Controller
Software Release 9 Provisioning Guide.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-2
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Before You Start
Before You Start
Before you start, verify the following:
Caution
•
Have your company's internal support and Cisco support contact information readily available so
you can get help with the installation if needed. (If you have questions or need assistance, see the
“Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii of the
Cisco support contact information.)
•
Ensure that you have access to the console port on your Cisco MGC host.
The Cisco MGC software is case-sensitive. Ensure that you enter parameter names correctly, or the
maximum number of configurations will not be modified.
Software Directory Structure
Table 5-2 shows the Cisco MGC software directory structure.
Caution
Do not edit any .dat files (except for the XECfgParm.dat and trigger.dat files). Use MML or the GUI
provisioning tool to make changes to your configuration. In addition, only make changes to the call
screening database by using MML or the GUI provisioning tool.
Table 5-2
Software Directory Structure
Directory
Contents
/etc/init.d
Control scripts, including scripts used to stop and start the
software.
/opt/CiscoMGC
Root location of base software installation.
/opt/CiscoMGC/local
User accounts home directory.
/opt/CiscoMGC/etc
Contains active configuration data files and the
configuration library.
/opt/CiscoMGC/etc/CONFIG_LIB
Library of all configuration data files.
/opt/CiscoMGC/etc/CONFIG_LIB/new
The initial startup configuration supplied with a new
installation of the software.
/opt/CiscoMGC/etc/active_link
The active running configuration that has been committed
or deployed.
/opt/CiscoMGC/etc/prov_link
The latest provisioned configuration that has not yet been
committed or deployed.
/opt/CiscoMGC/etc/cust_specific
Location of configurations that have been exported using
the prov-exp MML command.
/opt/CiscoMGC/man
MML help files.
/opt/CiscoMGC/lib
System software libraries of *.so object files (including
protocol and system libraries).
/opt/CiscoMGC/snmp
SNMP support directory. MIBs are named *.my and are in
ASN.1 syntax.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-3
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Table 5-2
Software Directory Structure (continued)
Directory
Contents
/opt/CiscoMGC/var
Contains the log, spool, and trace file directories.
/opt/CiscoMGC/var/log
Default platform informational and error logs.
/opt/CiscoMGC/var/spool
Spool files for CDRs and measurements.
/opt/CiscoMGC/var/trace
Location of trace files created by using the sta-trc MML
command.
/opt/TimesTen
Call screening database files. Do not edit the database.
/opt/Toolkit
The Toolkit application files.
/opt/sun_install
Contains the scripts used to install Solaris patches (part of
the CSCh007.pkg).
Initial Cisco MGC Software Configuration
When configuring the Cisco MGC software for the first time, use the MGC Environment Configuration
Tool XECfg program to modify the XECfgParm.dat file. The MGC Environment Configuration Tool is
a utility that is based on the Tool Command Language/Toolkit (Tcl/Tk). This utility uses an initialization
wizard to facilitate the initial configuration of the XECfgParm.dat file.
The following required configuration parameters in the XECfgParm.dat file (see Table 5-3) are critical
to bringing up the system. For more information on XECfgParm.dat files, refer to the “Cisco MGC 9.x
XECfgParm.dat File Parameter Definitions” section on page A-2.
Note
The XECfgParm.dat file must be provisioned with the installation of every system. The file consists of
set of parameters that are necessary to bring up the system. This set of required parameters is configured
via the MGC Environment Configuration Tool.
When you exit the MGC Environment Configuration Tool, the slave file is sent via FTP to the
appropriate system.
Caution
During Initial Cisco MGC Configuration: We recommend that you put an initial configuration on the
active host, otherwise both the active and standby hosts will remain in the stopped state. Do not
start the standby host if the active host is not yet provisioned.
When the initial configuration on the active host is deployed, you must change the pom.dataSync
parameter to true in the XECfgParm.dat file in the standby host. After setting this parameter to
true, you can start the Cisco MGC on the standby host. As the Cisco MGC comes up, the data on
the standby host is synchronized with the data on the active host. Initiate switchover to bring the
active host to the standby state.
To accommodate failover conditions where the current active host can become the standby host,
you must also set the pom.dataSync parameter to true on the current active host.
When Upgrading the Cisco MGC software: You must set the pom.dataSync parameter to false on
the current active host to preserve configuration files.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-4
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Table 5-3
Configuration Parameters
Parameter
Description
*.CPUTimerInterval
Samples the frequency of CPU utilization.
Prior to Release 9.4(1), this parameter must be set to 0
during the initial configuration of any platform with a
single CPU (including Sun Netra t 100/105, Sun
Netra V 120, and Sun Netra 120).
For Release 9.4(1) and up, this parameter is set
automatically when you specify a Cisco MGC type in
the engine.SysVirtualSwitch parameter. Any attempt
to modify this parameter is overwritten.
*.desiredPlatformState
Specifies the operating mode of the Cisco MGC.
*.ipAddr1 through ipAddr4
Specify the IP addresses being used by the system.
Note that *.ipAddrLocalA, and *.ipAddrLocal2 are the
same as *.ipAddr1, and *.ipAddr2, respectively.
*.ownClli
Specifies ANSI CLLI code.
pom.dataSync
Indicates that the Provisioning Object Manager (POM)
should synchronize the provisioning data at startup.
*.SyscheckpointEnabled
Specify true if the master/slave operating mode is being
used.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-5
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Table 5-3
Configuration Parameters (continued)
Parameter
Description
*.SysConnectDataAccess
Controls whether data access is enabled or disabled (if
the engine attempts to connect to the MMDB or to call
screening database at startup).
Values:
•
true = connect to MMDB or call screening
database
•
false = do not connect to MMDB or call screening
database
Default: false
engine.SysVirtualSwitch
Note
This parameter must be set to true in calling
scenarios where Euro-LNP, A Number
Screening, or other features requiring real time
database access are required. Otherwise, it can
remain false for an increase in the available
system memory usable for call processing.
Note
This parameter replaces the
engine.sysScreeningCheck parameter in Cisco
MGC 7.4.
Specifies the Cisco MGC type. Indicates whether the
Cisco MGC host functions as a signaling controller or a
virtual switch controller.
Values:
•
0 = signaling controller (nailed trunks, no auditing
is initiated)
•
1 = virtual switch controller (switched trunks)
Default: 0
Note
For Release 9.4(1) and up, the values of the
parameters listed below are automatically set
based on the Cisco MGC type you select, to
maximize performance for that configuration.
Any attempt to change the values of these
parameters is overwritten.
engine.SysMdlMemoryReduction
engine.CALL_MEM_BLOCK_SIZE
engine.CALL_MEM_CHUNK_SIZE
*.CPUTimerInterval
*.numberOfThreads
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-6
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Parameters Required for Initial Setup
The following table lists the parameter values that must be defined during the initial installation.
Note
These parameters are located at the top of the XECfgParm.dat file, thus making it easier to find the
parameters required for initial setup.
Table 5-4
Item
Parameters Required for Initial Setup
Parameter Name
Default Value
Changed Values
1
PlatformId
1
1, if slave
2
TranspathId
01
02, if slave
3
DesiredPlatformState
Standalone
Master,slave,standalone
4
SyscheckpointEnabled
False
True, if redundant system
5
IpAddrLocalA
0.0.0.0
Ifconfig(hme0)
6
IpAddrLocalB
0.0.0.0
Ifconfig(hme1)
7
IpAddrPeerA
0.0.0.0
Slave(ifconfig(hme0))
8
IpAddrPeerB
0.0.0.0
Slave(ifconfig(hme1))
9
IPAddr1
0.0.0.0
Ifconfig(hme0)
10
IPAddr2
0.0.0.0
Ifconfig(hme1)
11
IPAddr3
0.0.0.0
Ifconfig(hme2)
12
IPAddr4
0.0.0.0
Ifconfig(hme3)
13
StPort
0
7000, if Master or 7001 if Slave
14
Engine.SysVirtualSwitch
0
1 for Switched solution
15
Foverd.ipLocalPortA (con 1)
0
1051, if Master or 1052 if Slave
16
Foverd.ipPeerPortA (con 1)
0
1052, if Master or 1051 if Slave
17
Foverd.ipLocalPortA (con 2)
0
1053, if Master or 1054 if Slave
18
Foverd.ipPeerPortA (con 2)
0
1054, if Master or 1053 if Slave
19
Pom.dataSync
False
True if Master or Slave, both sides
20
Diskmonitor.OptFileSys
<blank>
../var/log
21
NumberOfThreads
0
Prior to 9.4(1): 0,1,2 depends of CPUs
in system
9.4(1) and up: Depends on the setting
for engine.SysVirtualSwitch.
Note
22
OwnClli
12233344445
ANSI(CLLI of Switch)
23
*.SysConnectDataAccess
False
call screening using the database
For an example of an updated configuration file, see the “Updated Configuration File Sample” section
on page D-10.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-7
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Using the Cisco MGC Environment Configuration Tool
You must configure the basic parameters required to bring the system to an operational mode. To use
the MGC Environment Configuration Tool XECfg program:
Step 1
Run the MGC Environment Configuration Tool. Log in as mgcusr, type the following at the command
prompt, and press Enter:
MGC_Setup
A dialog box is displayed, warning that the MGC Environment Configuration Tool is for initial system
set up only and asks if you wish to continue running the XECfg program.
Step 2
Select Yes.
A screen similar to the following is displayed:
Figure 5-1
MGC Environment Configuration Tool
Optionally, you can run the MGC Environment Configuration Tool in detail mode by selecting the detail
parameter at the command line.
a.
Type the following command and press Enter:
MGC_Setup -detail
A dialog box is displayed, warning that the MGC Environment Configuration Tool is for initial
system set up only, and asks if you wish to continue running XECfg.
b.
Select Yes.
The MGC Environment Configuration Tool screen expands to provide detailed information from the
XECfgParm.dat file (see Figure 5-2).
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-8
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initial Cisco MGC Software Configuration
Figure 5-2
Step 3
MGC Environment Configuration Tool—Detail Mode
You can configure your system to operate either as a standalone system or as a fault-tolerant system.
If you configure your system to be in fault-tolerant mode, you must do the following:
Step 4
a.
Supply a set of IP addresses for the back-up/standby machine. By default, these backup IP addresses
are set to 0.0.0.0.
b.
Type the backup IP addresses in the Slave IP field in the Master-Slave IP Map section of the MGC
Environment Tool screen.
Click the Commit button to implement changes after you have completed configuring the parameters.
Note
The required parameters are the Cisco MGC type and its operating mode. There are no default
parameters defined when you bring up the XECfg program.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-9
Chapter 5
Configuring the Cisco MGC Software
Configuring Groups and Users
After committing the changes, the XECfg program backs up the current XECfgParm.dat file into
XECfgParm.dat.xyz, where xyz can be between 0 and 19. The earliest version of the XECfgParm.dat file
is version 0 and the latest is version 19.
If the operating mode is stand-alone, the XECfgParm.dat file is updated with new parameters. If the
operating mode is fault-tolerant, the XECfgParm.dat file is updated and the XECfgParm.data.slave file
is generated, based on the XECfgParm.dat file. There is no backup for the XECfgParm.dat.slave file.
Old parameters are commented out and new parameters are inserted. Use the comment line to keep file
history. A history line is inserted every time a change is made against parameters. All required
parameters are moved up to the top of the file for ease of use. However, the configuration tool does not
depend on the location of the parameters.
Step 5
When you exit the application, the XECfg program prompts you to determine whether you wish to
transfer the XECfgParm.dat.slave file to the remote machine (this is done through the FTP operation).
If you choose to transfer the file to the remote machine, you must enter a password before the FTP is
performed successfully. Alternately, you can exit the application without performing the FTP operation.
Configuring Groups and Users
You must set up groups and users for the Cisco MGC software on each host server. A user must be a
member of the “mgcgrp” group to use certain Cisco MGC software functions, such as Man-Machine
Language (MML). (MML is an interface that enables you to communicate with the Cisco MGC. Users
with full MML privileges have monitor and control access; users with minimal MML privileges have
only monitor access. For more information on MML, see the Cisco Media Gateway Controller Software
Release 9 Provisioning Guide and the Cisco Media Gateway Controller Software Release 9 MML
Command Reference.)
Verifying the mgcgrp Group
To verify the mgcgrp group, complete the following steps:
Step 1
Log in to the Cisco MGC host as root.
Step 2
Change to the /etc directory.
Step 3
Edit the group file to verify the entry for the mgcgrp group. The file should contain the following line:
mgcgrp::20000:
Step 4
Save and close the group file.
Step 5
Edit the passwd file to verify the entry for the mgcusr user. The file should contain the following line:
mgcusr:x:20000:20000::/opt/CiscoMGC/local:/bin/csh
If the file does not contain the line, add it.
Step 6
Save and close the password file.
This completes the procedures for verifying the mgcgrp group.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-10
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring Groups and Users
Adding a User with Full MML Privileges
To add a user with full MML privileges, complete the following steps.
Caution
If your user’s home directory differs from /opt/CiscoMGC/local, you must perform Step 6 through
Step 9 before using MML.
Step 1
Log in to the Cisco MGC host as root.
Step 2
Enter the following command:
# useradd -u UID -g mgcgrp -d /opt/CiscoMGC/local -s /bin/csh -m username
UID is a user ID that is an integer from 0 through 2147483647 (excluding the numbers 0, 1, 2, 3, 4, 5,
9, 37, 71, 60001, 60002, and 65534, because they are used by the operating system).
Step 3
Add the new username to the mgcgrp group in the group file:
# mgcgrp::20000:username
Note
Step 4
The group file is a comma-separated list of user names. If you add more than one user, use
commas (with no spaces) to separate one name in the list from another.
Enter the following command and press Enter:
passwd username
Step 5
Type the user’s password and press Enter twice when prompted.
Step 6
If your user’s home directory differs from /opt/CiscoMGC/local: Log in to the Cisco MGC.
Step 7
Enter the following command and press Enter:
cd /opt/CiscoMGC/local
Step 8
Enter the following command and press Enter:
source .cshrc
Step 9
Enter the following command and press Enter:
mml
This completes the procedures for adding a user with full MML privileges.
Adding a User with Minimal MML Privileges
To add a user with minimal MML privileges, follow the steps in the “Adding a User with Full MML
Privileges” section on page 5-11, but do not add the user to the mgcgrp group.
This completes the group and user configuration. Continue to the “Configuring SNMP Support
Resources” section on page 5-12. If you have questions or need assistance, see the “Obtaining
Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-11
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Configuring SNMP Support Resources
The Cisco MGC software includes a Simple Network Management Protocol (SNMP) agent subsystem
that provides an alarm management interface on the Cisco MGC. It uses SNMP to report events, or traps
(such as alarms), to your SNMP Manager and to provide access to the Cisco MGC Management
Information Base (MIB).
Note
SNMP MIB measurements are only valid on the active node. They are not replicated on the standby
node.
The SNMP agent subsystem reports the following event categories to your SNMP Manager:
1.
Communications
2.
Quality of Service
3.
Processing
4.
Equipment
5.
Environment
In a fault tolerant configuration, the SNMP agent subsystem runs on both the active and standby
machines.
Note
If your system is running Cisco MGC software 9.3(2) or later, go to the “Migrating the SNMP
Configuration to a More Secure Environment (for MGC 9.3(2) or Later)” section on page 5-13 for SNMP
configuration procedures.
If your system is running an earlier version of Cisco MGC software 9.3(2), such as version 7.4(x), go to
the “Setting up the SNMP Community for Software Releases Before Cisco MGC 9.3(2)” section on
page 5-24 for SNMP configuration procedures.
Note
For a sample snmpd.cnf file, see the “Sample Configured snmpd.cnf File” section on page D-11.
Note
Use any of the following to configure SNMP community names and trap destinations:
– config-snmp utility (for Cisco MGC software 9.3(2) or later)
– vi editor (for Cisco MGC software 9.2(2) or earlier)
Note
SNMP managers such as the Cisco Media Gateway Controller Node Manager (MNM) or HP OpenView
can be used to receive traps.
Note
The config-snmp utility is case-sensitive. It will accept “name1” and “NAME1” as two different entries.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-12
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Migrating the SNMP Configuration to a More Secure Environment (for MGC
9.3(2) or Later)
If your system is running Cisco MGC software version 9.3(2) or later, Cisco recommends that your
SNMP configuration be migrated to a more secure environment by running the config-snmp utility. Use
the config-snmp utility to perform the following:
•
Modify the snmpd.cnf file to automatically migrate old configuration files to a secure environment.
•
Facilitate the addition or deletion of the community string and trap destination.
Note
There is no limit to the number of community strings that can be added to the configuration.
Note
The config-snmp script only allows you to add or delete an entry to your snmpd.cnf file.
Basic Tasks
The following is an overview of the major tasks you must perform to get the SNMP security provided
by the config-snmp utility:
1.
Run config-snmp utility. See the “Running the config-snmp Utility” section on page 5-14.
2.
Add a new snmpCommunityEntry. See the “Adding an SNMP Community Entry” section on
page 5-15
3.
Make sure that the new snmpCommunityEntry string is recognized and can communicate with your
Cisco MGC hosts. See the “Activating the New Settings” section on page 5-21.
4.
Delete the old entry that you were using. See the “Deleting an SNMP COMMUNITY” section on
page 5-18.
Before You Run the config-snmp Utility
Note
If you have completed a first-time installation of the Cisco MGC softare with Release 9.6(1) and its
associated patches, you must copy the snmpd.cnf.tmpl to snmpd.cnf before your run the config-snmp
utility. Users who have upgraded to Release 9.6(1) from a previous release do not have to perform this
procedure. To copy the snmpd.cnf.tmpl to the snmp.cnf, perform the following steps:
1. Log in as root and enter the following UNIX commands:
cd /opt/CiscoMGC/snmp
cp snmpd.cnf.tmpl snmpd.cnf
2. Enter the following UNIX commands to restart the snmp daemon:
ps -ef |grep snmpdm
The system will display the process ID for the snmp daemon. Restart the daemon using the
following command:
kill -9 snmpdm_pid
Where snmpdm_pid is the process ID for the snmp daemon.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-13
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Note that the first instance of ReadAndNotifyToAll in the snmpCommunityEntry will be the only
CommunityName used in the Trap.
For example, if your snmpd.cnf file has the following snmpCommunityEntry, you will find only the
CommunityName of Iron1 in the Trap.
#Entry type: snmpCommunityEntry
#Format: snmpCommunityIndex (text)
#
snmpCommunityName (text)
#
snmpCommunitySecurityName (text)
#
snmpCommunityContextEngineID (octetString)
#
snmpCommunityContextName (text)
#
snmpCommunityTransportTag (text)
#
snmpCommunityStorageType (nonVolatile, permanent, readOnly)
snmpCommunityEntry Iron1 ron1 ReadAndNotifyToAll localSnmpID - - nonVolatile
snmpCommunityEntry Iron2 ron2 ReadWriteAll localSnmpID - - nonVolatile
snmpCommunityEntry Iron3 ron3 ReadAndNotifyToAll localSnmpID - - nonVolatile
snmpCommunityEntry admin WBnAGZ54 PGWInternalSignal localSnmpID - localAccess \
nonVolatile
snmpCommunityEntry readonly public ReadAndNotifyToAll localSnmpID - - \
nonVolatile
Running the config-snmp Utility
Perform the following steps to run the config-snmp utility:
Step 1
Make sure your system has the latest Cisco MGC patches on both Host A and Host B. Refer to the
Release Notes for Cisco Media Gateway Controller Software Release 9 for the patches’ installation
procedures.
Step 2
On Host A, log in as root user.
Step 3
Check whether the snmpdm or critagt process is running.
Note
If snmpdm or critagt are not running, call Cisco TAC or contact your Field Engineer for
assistance.
Type one of the following commands and press Enter:
a.
To check snmpdm:
ps -ef |grep snmpdm
If the snmpdm process is running, text similar to the following is displayed:
root 12098 27888 0
Jun 16 ?
0:00 /opt/CiscoMGC/snmp/snmpdm -tcplocal -d
b.
To check critagt:
ps -ef |grep critagt
If the critagt process is running, text similar to the following is displayed:
root 27888
1 0
May 19 ?
0:15 /opt/CiscoMGC/snmp/critagt -d
Step 4
To start the config-snmp utility, type the following command and press Enter:
config-snmp
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-14
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
The following screen is displayed:
Migrating snmpd.cnf into a more secure setting...
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
Step 5
To view the configuration entries, type 1 and press Enter.
The Entries Menu is displayed and you are prompted to make a selection:
===================
Entries Menu
===================
1. sysDescr
2. sysObjectID
3. sysLocation
4. sysContact
5. sysName
6. snmpEnableAuthenTraps
7. MAX_THREADS
8. MAX_PDU_TIME
9. MAX_OUTPUT_WAITING
10. MAX_SUBAGENTS
11. subagent
12. snmpCommunityEntry
13. communityEntry
14. snmpEngineBoots
15. usmUserEntry
16. vacmAccessEntry
17. vacmSecurityToGroupEntry
18. vacmViewTreeFamilyEntry
19. snmpNotifyEntry
20. snmpTargetAddrEntry
21. snmpTargetParamsEntry
22. snmpNotifyFilterProfileEntry
23. snmpNotifyFilterEntry
24. httpUserNameEntry
Enter a selection (1 through 24) or 'q' to quit to Main Menu:
Step 6
Enter your selection number (1 through 24) to view your configuration entries.
Adding an SNMP Community Entry
Continuing from Step 6, above (of the section Running the config-snmp Utility):
Step 1
Enter 12 to select snmpCommunityEntry and view the entries:
Text similar to the following and the SNMPD Configuration Main Menu are displayed.
#Entry type: snmpCommunityEntry
#Format: snmpCommunityIndex (text)
#
snmpCommunityName (text)
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
#
snmpCommunitySecurityName (text)
#
snmpCommunityContextEngineID (octetString)
#
snmpCommunityContextName (text)
#
snmpCommunityTransportTag (text)
#
snmpCommunityStorageType (nonVolatile, permanent, readOnly)
snmpCommunityEntry IT555 T555 ReadWriteAll localSnmpID - - nonVolatile
snmpCommunityEntry Ijammmy jammmy ReadAndNotifyToAll localSnmpID - nonVolatile
snmpCommunityEntry admin za8RQzBg PGWInternalSignal localSnmpID - localAccess
nonVolatile
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
Step 2
You are prompted to make a selection. Enter 2 to add an SNMP Community.
The Add CommunityString Menu is displayed and you are asked if you would like to proceed with
adding a community string:
===================
Add CommunityString Menu ===================
SnmpCommunityName
CommunitySecurityName
T555
jammmy
ReadWriteAll
ReadAndNotifyToAll
-- Where:
CommunitySecurityName
SecurityModel
Read
Write
Notification
ReadWriteAll
ReadWriteAll
ReadAndNotifyToAll
ReadAndNotifyToAll
snmpv1
snmpv2c
snmpv1
snmpv2c
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
-
AllMibObjects
AllMibObjects
Would you like to proceed with the Add
Step 3
[n]/[y]?
Enter y to proceed (if you enter n to cancel the addition, you return to the SNMPD Configuration Main
Menu).
The following text is displayed, prompting you to enter an snmpCommunityName.
Enter snmpCommunityName:
Note
Step 4
The snmpCommunityName should be at least three characters in length. The
snmpCommunityName can contain numeric characters, but should begin with an alpha
character.
Enter an snmpCommunityName (the following name is an example):
comname1
Text similar to the following is displayed:
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-16
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Enter CommunitySecurityName (ReadAndNotifyToAll or ReadWriteAll):
Step 5
Enter a community security name (the following security name entry is an example):
ReadAndNotifyToAll
Note
The CommunitySecurityName (ReadAndNotifyToAll or ReadWriteAll) is case sensitive.
Text similar to the following text is displayed:
snmpCommunityName: comname1 is about to be added.
snmpCommunity Name [y]/[n]?
Step 6
Are you sure that you want to add this
Enter y to add the snmpCommunityName (if you enter n to cancel the addition, you return to the
SNMPD Configuration Main Menu):
Text similar to the following is displayed:
Adding snmpCommunity:
snmpCommunityEntry Icomname1 comname1 ReadAndNotifyToAll localSnmpID - - nonVolatile
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
Step 7
Enter a selection number, 1 through 6. For steps on how to execute the selections from the SNMPD
Configuration Main Menu, refer the following sections:
•
Adding an SNMP Community Entry, page 5-15
•
Deleting an SNMP COMMUNITY, page 5-18
•
Adding a Trap Destination, page 5-19
•
Deleting a Trap Destination, page 5-20
•
Activating the New Settings, page 5-21
•
Verifying the SNMP Configuration Migration, page 5-22
Note
To complete the migration of the SNMP configuration to a more secure environment, see the
“Activating the New Settings” section on page 5-21.
The procedure for adding an SNMP Community Entry is now complete.
From the SNMPD Configuration Main Menu, choose option 6 (Activate the New Settings) to commit
the changes, or select other options (1 through 5) to add or delete a community name or trap.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-17
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Deleting an SNMP COMMUNITY
From the SNMPD Configuration Main Menu:
Step 1
If you select 3 (Delete an SNMP Community) from the SNMPD Configuration Main Menu, the delete
CommunityString Menu is displayed:
Note
The SNMP Community Names listed in the following display are examples.
===================
Delete CommunityString Menu ===================
SnmpCommunityName
CommunitySecurityName
comname1
T555
jammmy
ReadAndNotifyToAll
ReadWriteAll
ReadAndNotifyToAll
-- Where:
CommunitySecurityName
SecurityModel
Read
Write
Notification
ReadWriteAll
ReadWriteAll
ReadAndNotifyToAll
ReadAndNotifyToAll
snmpv1
snmpv2c
snmpv1
snmpv2c
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
AllMibObjects
-
AllMibObjects
AllMibObjects
Would you like to proceed with the Delete
Step 2
[n]/[y]?
Enter y to delete SNMP Community (if you enter n to cancel the deletion, you return to the SNMPD
Configuration Main Menu):
Text similar to the following is displayed:
Enter snmpCommunityName:
Step 3
Enter an SnmpCommunityName. Select an SnmpCommunityName from the list that is displayed in
Step 1. The SnmpCommunityName T555, is an example:
T555
Text similar to the following is displayed:
snmpCommunityName: T555 is about to be deleted.
snmpCommunity Name [y]/[n]?
Step 4
Are you sure that you want to delete this
Enter y to confirm the deletion (if you enter n to cancel the deletion, you return to the SNMPD
Configuration Main Menu).
Text similar to the following is displayed and you are returned to the SNMPD Configuration Main Menu:
Deleting snmpCommunity= T555
===================
1.
2.
3.
4.
5.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-18
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
6. Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
Step 5
Enter your selection. For detailed procedures for your selection, refer to the following list:
•
Adding an SNMP Community Entry, page 5-15
•
Deleting an SNMP COMMUNITY, page 5-18
•
Adding a Trap Destination, page 5-19
•
Deleting a Trap Destination, page 5-20
•
Activating the New Settings, page 5-21
•
Verifying the SNMP Configuration Migration, page 5-22
The procedure for deleting an SNMP Community Entry is now complete. Proceed to the selection you
entered in the SNMPD Configuration Main Menu.
Adding a Trap Destination
From the SNMPD Configuration Main Menu:
Step 1
Select option 4 (Add a Trap Destination) from the SNMPD Configuration Main Menu and press Enter
to add a Trap Destination.
The Add Trap Menu is displayed:
Note
The IP Address (Target Address) listed below is an example of existing Trap entries.
=================== Add Trap Menu
===================
1. TargetAddress: 6.6.6.6:0 , TargetAddrParams: v1ExampleParams , IP Mask:
255.255.255.255:0
Would you like to proceed with the Add
Step 2
[n]/[y]?
Enter y to add a Trap Destination (if you enter n to cancel the addition, you return to the SNMPD
Configuration Main Menu).
Text similar to the following is displayed:
Enter IP Address (x.x.x.x):
Step 3
Enter the IP address listed in Step 1:
7.7.7.7
Text similar to the following is displayed:
Enter Trap Type (v1 or v2c):
Step 4
Enter the Trap Type based on your SNMP manager. The following entry is an example:
v1
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-19
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Text similar to the following is displayed:
'snmpTargetAddrEntry 483 snmpUDPDomain 6.6.6.6:0 100 3 TrapSink v1ExampleParams
nonVolatile 255.255.255.255:0 2048
' is about to be added. Are you sure that you want to add this Trap Entry [n]/[y]?
Step 5
Enter y to add a Trap Destination (if you enter n to cancel the addition, you return to the SNMPD
Configuration Main Menu).
Text confirming the addition of the Trap Destination is displayed, followed by the SNMPD
Configuration Main Menu:
Adding Trap: snmpTargetAddrEntry 483 snmpUDPDomain 7.7.7.7:0 100 3 TrapSink
v1ExampleParams nonVolatile 255.255.255.255:0 2048
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
ENTER YOUR SELECTION.
Step 6
Enter your selection. For detailed procedures for your selection, go to the section listed below:
•
Adding an SNMP Community Entry, page 5-15
•
Deleting an SNMP COMMUNITY, page 5-18
•
Adding a Trap Destination, page 5-19
•
Deleting a Trap Destination, page 5-20
•
Activating the New Settings, page 5-21
•
Verifying the SNMP Configuration Migration, page 5-22
The procedure for adding a Trap Destination is now complete. Proceed to the selection you entered in
the SNMPD Configuration Main Menu.
Deleting a Trap Destination
From the SNMPD Configuration Main Menu:
Step 1
To delete a Trap Destination, enter 5 (Delete a Trap Destination):
Text similar to the following is displayed:
=================== Delete Trap Menu
1.
IP
2.
IP
===================
TargetAddress: 7.7.7.7:0 , TargetAddrParams: v1ExampleParams ,
Mask: 255.255.255.255:0
TargetAddress: 6.6.6.6:0 , TargetAddrParams: v1ExampleParams ,
Mask: 255.255.255.255:0
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-20
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Would you like to proceed with the Delete
Step 2
[n]/[y]?
Enter y to delete a Trap Destination (if you enter n to cancel the deletion, you return to the SNMPD
Configuration Main Menu):
Text similar to the following is displayed:
Enter a selection (1 through 2):
Note
Step 3
The Target Addresses (1 through 2) shown above are examples only.
Enter 1 to select the TargetAddress to be deleted:
Text similar to the following is displayed:
Trap is about to be deleted.
[n]/[y]?
Step 4
Are you sure that you want to delete this Trap Entry
Enter y to confirm the deletion (if you enter n to cancel the deletion, you return to the SNMPD
Configuration Main Menu).
Text confirming the deleted Trap Entry is displayed and you are returned to the SNMPD Configuration
Main Menu. Note that 483 (below) is an internal Trap snmpTargetAddrName.
Deleting Trap snmpTargetAddrName = 483
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Enter a selection (1 through 6) or 'q' to quit:
Step 5
Enter your selection. For detailed procedures for your selection, refer to the following list:
•
Adding an SNMP Community Entry, page 5-15
•
Deleting an SNMP COMMUNITY, page 5-18
•
Adding a Trap Destination, page 5-19
•
Deleting a Trap Destination, page 5-20
•
Activating the New Settings, page 5-21
•
Verifying the SNMP Configuration Migration, page 5-22
The procedures for deleting a Trap Destination is now complete. Proceed to the selection you entered in
the SNMPD Configuration Main Menu.
Activating the New Settings
From the SNMPD Configuration Main Menu:
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-21
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Step 1
Enter 6 to activate the new settings:
6
Text similar to the following is displayed:
Backing up the current snmpd.cnf to snmpd.cnf.backup.
snmpd.cnf.backup already exists. Do you want to overwrite the file
Note
Step 2
[y]/[n]?
If you choose n, your backup file will not be updated.
Enter y to activate the new settings.
y
Are you sure you would like to Activate the New Settings
Note
[y]/[n]?
If you choose y, your SNMPD.dat file will be updated and you will be exited from the utility.
If you choose n, your SNMPD.dat file will not be updated and you will be exited from the utility.
Step 3
Enter y to activate the new settings (if you enter n to cancel the activation, you return to the SNMPD
Configuration Main Menu).
Text similar to the following is displayed:
snmpd.cnf file has been updated.
The procedure for activating the new settings is now complete and you are exited from the config-snmp
utility. Proceed to the following section, “Verifying the SNMP Configuration Migration”.
Verifying the SNMP Configuration Migration
Perform the following steps to verify that your changes were applied by running the config-snmp utility:
Step 1
To start the config-snmp utility, type the following command and press Enter:
config-snmp
Text similar to the following is displayed:
Migrating snmpd.cnf into a more secure setting...
When the SNMPD Configuration Main Menu is displayed, you are prompted to make a selection:
===================
1.
2.
3.
4.
5.
6.
SNMPD Configuration Main Menu
===================
View Configuration Entries
Add an SNMP Community
Delete an SNMP Community
Add a Trap Destination
Delete a Trap Destination
Activate the New Settings
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-22
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Enter a selection (1 through 6) or 'q' to quit: 1
Step 2
Enter 1 to view the configuration entries.
The Entries Menu is displayed and you are prompted to make a selection:
===================
Entries Menu
===================
1. sysDescr
2. sysObjectID
3. sysLocation
4. sysContact
5. sysName
6. snmpEnableAuthenTraps
7. MAX_THREADS
8. MAX_PDU_TIME
9. MAX_OUTPUT_WAITING
10. MAX_SUBAGENTS
11. subagent
12. snmpCommunityEntry
13. communityEntry
14. snmpEngineBoots
15. usmUserEntry
16. vacmAccessEntry
17. vacmSecurityToGroupEntry
18. vacmViewTreeFamilyEntry
19. snmpNotifyEntry
20. snmpTargetAddrEntry
21. snmpTargetParamsEntry
22. snmpNotifyFilterProfileEntry
23. snmpNotifyFilterEntry
24. httpUserNameEntry
Enter a selection (1 through 24) or 'q' to quit to Main Menu:
a.
If you select 12 from the SNMPD Configuration Main Menu, the snmpCommunityEntry is
displayed, showing the changes you made:
Note
The following entries are examples only.
#Entry type: snmpCommunityEntry
#Format: snmpCommunityIndex (text)
#
snmpCommunityName (text)
#
snmpCommunitySecurityName (text)
#
snmpCommunityContextEngineID (octetString)
#
snmpCommunityContextName (text)
#
snmpCommunityTransportTag (text)
#
snmpCommunityStorageType (nonVolatile, permanent, readOnly)
snmpCommunityEntry Icomname1 comname1 ReadWriteAll localSnmpID - - nonVolatile
snmpCommunityEntry Ijammmy jammmy ReadAndNotifyToAll localSnmpID - nonVolatile
snmpCommunityEntry admin VD6FZbov PGWInternalSignal localSnmpID - localAccess
nonVolatile
b.
If you select 20 from the SNMPD Configuration Main Menu, the Trap Destination information is
displayed, showing the changes you made:
Note
The following entries are examples only.
#Entry type: snmpTargetAddrEntry
#Format: snmpTargetAddrName (text)
#
snmpTargetAddrTDomain (snmpUDPDomain, snmpIPXDomain, etc.)
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-23
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
#
snmpTargetAddrTAddress (transport address,i.e. 192.147.142.254:0)
#
snmpTargetAddrTimeout (integer)
#
snmpTargetAddrRetryCount (integer)
#
snmpTargetAddrTagList (text)
#
snmpTargetAddrParams (text)
#
snmpTargetAddrStorageType (nonVolatile, permanent, readOnly)
#
snmpTargetAddrTMask (transport mask, i.e. 255.255.255.255:0)
#
snmpTargetAddrMMS (integer)
snmpTargetAddrEntry 531 snmpUDPDomain 6.6.6.6:0 100 3 TrapSink
v1ExampleParams
nonVolatile 255.255.255.255:0 2048
snmpTargetAddrEntry local snmpUDPDomain 127.0.0.1:0 100 3 localAccess nonVolatile 255.255.255.255:0 2048
The SNMP support resource configuration is now complete. Continue to the “Configuring the Execution
Environment” section on page 5-27 to configure the execution environment. If you have questions or
need assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii.
Setting up the SNMP Community for Software Releases Before Cisco MGC
9.3(2)
If your software release is earlier than Cisco MGC software release 9.3(2), you must edit your files using
the vi editor. You can either use the existing SNMP community (public) or create your own.
To create a new SNMP community, log in to the Cisco MGC as root and use the vi editor to modify the
/opt/CiscoMGC/snmp/snmpd.cnf file. This file has three default access security levels:
•
Guest (read-only)
•
User (read-write for most of the MIBS)
•
SuperUser (read-write).
Adding a New Community
To add a new community called myCommunity (for example, a community with an access level of
User), do the following procedures:
Step 1
Add a line in the snmpCommunityEntry as follows:
snmpCommunityEntry myUser myCommunity private localSnmpID - - nonvolatile
Step 2
Change the access level. To change the access level to Guest, replace “private” by “public”. To change
the access level to SuperUser, replace “private” by “mgcusr”.
Setting the Destination for Traps
Do the following procedures to add a trap destination, which is a machine named manager-host with the
IP address of 10.10.10.5. Traps will be sent to this destination by the MGC SNMP agent.
Step 1
In the snmpNotifyEntry section, add the following line:
snmpNotifyEntry
50 myTrap trap nonvolatile
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-24
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Note
Step 2
You can replace the number 50 with any unique number. You can also use any unique name in
place of myTrap. To send inform instead of traps, replace trap by inform.
In the snmpTargetAddrEntry section, add the following two lines:
snmpTargetAddrEntry 51 snmpUDPDomain 10.10.10.5:0 100 3 myTrap \
v2cExampleParams nonVolatile 255.255.255.255:0 2048
There must be nothing (not even a space or any other invisible characters) after the \ on the first line.
You can change the following entries in the above line:
•
51 is a unique index of the snmpTargetAddEntry. Use a different number if 51 is already in use;
make sure you are using a unique number.
•
10.10.10.5 is the IP address of the snmp manager.
•
100 specifies the round trip timeout of 1 second (100 of 100th second) for an inform. This number
is not used for traps.
•
3 is the number of retries the agent will attempt to retransmit an inform when a response is not
received. This number is not used for traps.
•
myTrap is the name defined in the snmpNotifyEntry.
•
v2cExampleParams specifies that SNMP v2c traps will be sent. To send v1 traps, use
v1cExampleParams.
Configuring SNMP Entries
To configure the SNMP resources, perform the following steps:
Step 1
Log in to the Cisco MGC and change to the /etc directory.
Step 2
Using FTP, transfer the following MIBs (located in /opt/CiscoMGC/snmp) from the Cisco MGC to the
machine on which the SNMP Manager runs:
Step 3
•
CISCO-SMI.my
•
v3-tgt.my
•
tp.my
•
measurement.my
Load the MIBs into the SNMP Manager.
For example, you can use the xnmnloadmib -load command from HP OpenView.
Tip
For more detailed information about configuring HP OpenView, see Appendix B, “HP OpenView
Sample SNMP Configuration.”
Note
See your SNMP Manager documentation for more information. We do not recommend an SNMP
Manager; however, this chapter gives examples using the Hewlett-Packard (HP) OpenView
Network Node Manager.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-25
Chapter 5
Configuring the Cisco MGC Software
Configuring SNMP Support Resources
Example 5-1
HP OpenView Example
If you are using HP OpenView Network Node Manager as your SNMP manager, follow
these procedures to load your MIB:
(a) Select Options from the File Menu and choose Load/Unload MIBs:SNMP.
(b) From the Load/Unload MIBs: SNMP window (on the lower left of your screen).
(c) Click the Load... button.
(c) From the “Load/Unload MIBs:SNMP /Load MIB from File” window, select the MIB to
load (for example, tp.my).
(d) Click OK.
Step 4
Connect the SNMP events to an event category to display the event. As Cisco MGC events are
connected, you can alter the format of the event messages for easier viewing.
Note
On many SNMP Managers, event categories can be added so that customer-specific events can
be mapped to corresponding categories.
Example 5-2
HP OpenView Event Configuration Example
If you are using HP OpenView Network Node Manager, follow these procedures to
configure an event:
(a) Select Options from the File Menu and choose Event Configuration.
(b) From the Event Configuration window, in the Enterprise Identification list,
select transpath.
(c) In the Event Identification list, double click on each of the event types, one
at a time.
(d) If desired, change the event information display. To change the format of an
event, from the Event Configurator / Modify Event window, enter a format in the
Event Log Message Box to change the format and labels for received events of this
type.
The following example shows how an event can be reformatted using the HP OpenView
Network Node Manager.
ID# $13
Name $12
Set $10
MMLname $4
CatDesc
$11 \nCompDesc $3
Severity $8
CompID $6
CompType $5
CatID $14\nAlarmNotify $9
AlarmTime$1
ParentID $2
AlarmReported $7\n$o
Tip
Step 5
For more detailed information about configuring HP OpenView, see Appendix B, “HP OpenView
Sample SNMP Configuration.”
Configure where to set Cisco MGC traps using any of the following:
– Cisco MNM
– HP OpenView
– vi editor
Step 6
Verify that your SNMP Manager shows the traps from the Cisco MGC. If you do not see the events in
your SNMP Manager, you might have a port mismatch or an incorrect IP address in your configuration.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-26
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
This completes the SNMP support resource configuration. Continue to the following section,
“Configuring the Execution Environment”, to configure the execution environment. If you have
questions or need assistance, see the “Obtaining Documentation, Obtaining Support, and Security
Guidelines” section on page xvii.
Configuring the Execution Environment
This section provides instructions for configuring the Cisco MGC execution environment and contains
the following topics:
•
Configuring Basic System Information, page 5-29
•
Specifying IP Addresses, page 5-31
•
Configuring Engine Parameters, page 5-32
•
Enabling Call Screening, page 5-35
•
Configuring Call Detail Record File Output, page 5-36
•
Configuring the Clearing Location and Default Location Parameters, page 5-38
•
Configuring Switchover, page 5-41
•
Initializing the Provisioning Object Manager, page 5-43
The configuration data file, or XECfgParm.dat file (located in /opt/CiscoMGC/etc/XECfgParm.dat),
lists all the components in the Cisco MGC and defines how it operates. You must edit the execution
environment parameters in the XECfgParm.dat file to initialize and configure the Cisco MGC software
application. For more detailed information on XECfgParm.dat parameters, refer to Appendix A,
“XECfgParm.dat File Parameters” and the Cisco Media Gateway Controller Software Release 9
Operations, Maintenance, and Troubleshooting Guide.
For samples of configured XECfgParm.dat files, see the “Sample Configured Cisco MGC 9.2(2)
XECfgParm.dat Files” section on page D-14.
Caution
To ensure that your system works as intended, edit only the XECfgParm.dat file parameters which
are listed below, and remember that all parameters are case-sensitive.
Do not modify the processes.dat file. This XECfgParm.dat file should remain unmodified, as delivered
with the MGC software. If this file is modified, procM may core dump when you start the MGC software.
Changing XECfgParm.dat File Parameters
For a complete list of the parameters found in the XECfgParm.dat file and how they are used by the
Cisco MGC, see Appendix A, “XECfgParm.dat File Parameters.”
If you have a fault tolerant system with two Cisco MGC hosts, the XECfgParm.dat files are different for
each host. For examples of these XECfgParm.dat files, see the “Sample Configured Cisco MGC 9.2(2)
XECfgParm.dat Files” section on page D-14 and the “Sample Configured Cisco MGC 9.1(5)
XECfgParm.dat Files” section on page D-21.
To change the XECfgParm.dat file parameters, perform the following steps:
Step 1
Log in as root and go to the # prompt.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-27
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Step 2
If the Cisco MGC software is running, enter the following command:
/etc/init.d/CiscoMGC stop
Wait until the system returns the following response:
Signalling procM to shut down
...shutdown complete
Step 3
Change to the /opt/CiscoMGC/etc directory, which contains the XECfgParm.dat file used by your
system.
Step 4
Open the XECfgParm.dat file with any text editor, such as vi.
Step 5
Save your changes and close the editor.
Step 6
Restart the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC start
Note
Do not restart the software yet if you need to configure SCP queries or initialize the call
screening database. Complete the instructions in the appropriate sections of this chapter before
restarting the software.
Continue to “Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System” to change
parameters without call interruption. Continue to the “Configuring SCP Queries” section on page 5-45
to configure Service Control Point (SCP) queries using transaction capabilities application part (TCAP).
If you have questions or need assistance, see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii.
Changing XECfgParm.dat File Parameters in a Running Fault Tolerant System
To change parameters in a running fault tolerant system without call interruption, perform the following
steps:
Step 1
Log in to the active host (Host X) and make your changes. See “Changing XECfgParm.dat File
Parameters” section on page 5-27 for more specific instructions.
Step 2
Log in to the standby host (Host Y) and stop the Cisco MGC software by entering the following
command:
/etc/init.d/CiscoMGC stop
Step 3
Restart the Cisco MGC software on the standby box (Host Y) by entering the following command:
/etc/init.d/CiscoMGC start
Step 4
Perform switchover on the active host (Host X). Log in to the active host (Host X) and stop the Cisco
MGC software by entering the following command:
/etc/init.d/CiscoMGC stop
Stopping the software on Host X causes switchover to the standby, Host Y. Host Y becomes active and
takes over call processing.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-28
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Tip
If Host Y does not take over call processing after switchover, restart the software on Host X to take over
the calls. Check the parameters you changed on Host Y and make sure you have the correct values.
Step 5
Restart the Cisco MGC software on the now standby host, Host X, by entering the following command:
/etc/init.d/CiscoMGC start
Step 6
On Host Y, the currently active host, enter the following MML command to switch call processing from
Host Y to the newly changed Host X. Host X becomes active:
SW-OVER::CONFIRM
Tip
If Host X does not take over call processing after switchover, restart the software on Host Y to take over
the calls. Check the parameters you changed on Host X and make sure you have the correct values.
Configuring Basic System Information
Note
For descriptions of the parameters found in the XECfgParm.dat file and how they are used by the Cisco
MGC, see Appendix A, “XECfgParm.dat File Parameters.”
To configure basic system information required for your system to function, modify the following
parameters in the first section of the XECfgParm.dat file:
Parameter
Modification
*.transpathId
To identify the local Cisco MGC host in a fault tolerant system,
enter any one- or two-digit integer.
Note
*.ownTranspathId
To identify the local Cisco MGC host in a fault tolerant system,
enter the same value that you used for *.transpathID.
Note
*.peerTranspathId
If you have two Cisco MGC hosts in a fault tolerant system,
this number must be different in the XECfgParm.dat file for
each host.
If you have two Cisco MGC hosts in a fault tolerant system,
enter this value in the *.peerTranspathID field in the
XECfgParm.dat file on the second host server. If you have
a simplex system, leave this value blank.
To identify the peer Cisco MGC host in a fault tolerant system, enter
any one- or two-digit integer. The IDs must be unique in an active
and standby pair.
Note
If you have two Cisco MGC hosts in a fault tolerant system,
enter the same value that you used for *.transpathID in the
XECfgParm.dat file of the second host server in this field.
If you have a simplex system, leave it blank.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-29
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
*.desiredPlatformState
To determine the desired platform state at initialization, enter one
of the following values:
•
master—If you have two (active and standby) Cisco MGC
hosts, and you are editing the file on the active host
•
slave—If you have two (active and standby) Cisco MGC hosts,
and you are editing the file on the standby host
•
standalone—If you have a simplex system
Note
*.SyscheckpointEnabled
To enable or disable checkpointing, enter one of the following
values:
•
false—Disables checkpointing. Calls are not preserved during
a switchover, and status messages are not sent to the replicator
(default).
•
true—Enables checkpointing. Calls that are in the talking state
are preserved and survive a control switchover. All status
checkpointing information is sent to the replicator on the active
side.
Note
*.numberOfThreads
If you have two Cisco MGC hosts in a fault tolerant system,
make sure that the active Cisco MGC is set to master and the
standby host is set to slave.
If you have two Cisco MGC hosts in a switchover
configuration, enter true. If you have a standalone
configuration, enter false.
Prior to Release 9.4(1), the number of threads generated by
multithreaded processes such as the engine and the log master, is
specified by entering one of the following values:
•
0—Single CPU (default)
•
1—Two CPUs
•
2—Four CPUs
Note
If you have a multi-CPU system, the
engine.SysGeneratedCode parameter must be left as
true (the default).
For Release 9.4(1) and up, this parameter is set automatically when
you specify a Cisco MGC type in the engine.SysVirtualSwitch
parameter. Any attempt to modify this parameter is overwritten.
*.OverdecadicDigitsSupported
This parameter controls the method of loading dial plan tables and
instructs the system whether to expect overdecadic (base 16) or
regular decadic (base 10) digits in dial plans, routing, and other digit
streams.
Correct setting of this parameter depends on local network
interconnect agreements and the expected data format.
Enter true to use overdecadic digits (0-F).
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-30
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
*.stPort
Port number used between peer components or processes.
Enter any unused port number (for example, 7000). If your
configuration uses a Cisco SLT, enter the port number on the Cisco
SLT.
*.OwnClli
Note
If you have two Cisco MGC hosts in a failover
configuration, enter a different number for this value in the
XECfgParm.dat file on the secondary host (for example,
7001).
Note
On a new configuration, we recommend that this parameter
be set to 0. This value allows the SLT port to be defined
using the PEERPORT parameter of the SESSIONSET.
Note
SESSIONSET reads the port value that is defined.
However, if an *.stPort value other than 0 is defined in
XECfgParm.dat (for example, *.stPort=7001), the
SESSIONSET value gets overridden by the value in
XECfgParm.dat.
Common language location identifier. To initiate circuit query
validation if circuit queries are supported, enter an alphanumeric
string of as many as 24 characters.
Default: TTT-SS-BB-XXX
Example: 1-22-33-444
Specifying IP Addresses
To specify IP addresses, modify the following parameters in the first section of the XECfgParm.dat file:
Note
If there are two Ethernet interfaces defined on the Cisco MGC, it is mandatory to have these on distinct
subnets.
For example, consider the following configuration:
*.ipAddrLocalA = 172.22.119.108
*.ipAddrLocalB = 172.22.119.54
This is not a valid combination because they are on the same subnet. The following example illustrates
a valid combination:
*.ipAddrLocalA = 172.22.119.108
*.ipAddrLocalB = 172.22.120.54
In this example, the subnet mask is 255.255.255.0 (or 255.255.255.128).
If the two Ethernet interfaces are on the same subnet, then one of them must be physically disconnected
from the existing subnet and then connected to a different subnet. The new IP address must be
appropriately configured on the system. Refer to the manual pages for the UNIX command ifconfig for
more information.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-31
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
*.ipAddrLocalA
Enter the first local IP address; used for checkpointing and
switchover heartbeats.
*.ipAddrPeerA
Caution
This address is the same value as *.IP_Addr1, and
is the hme0 interface.
Caution
No other machine on the network should have
*.ipAddrLocalA set to 0.0.0.0.
Enter the first corresponding peer IP address; used for
checkpointing and switchover heartbeats.
Note
*.ipAddrLocalB
Enter the second local IP address; used for checkpointing and
switchover heartbeats. This is the address of the hme1
interface.
Note
*.ipAddrPeerB
If you have two Cisco MGC hosts in a fault tolerant
configuration, this value is set to the IP address of the
second host.
If your configuration does not use a secondary
Ethernet adapter, leave this address set to the default
value, 0.0.0.0.
Enter the second corresponding peer IP address; used for
checkpointing and switchover heartbeats. This is the address
of the hme1 interface on the second host.
Note
If your configuration does not use a secondary
Ethernet adapter, leave this address set to the default
value, 0.0.0.0.
*.IP_Addr1
Enter the IP address of the hme0 interface.
*.IP_Addr2
Enter the IP address of the hme1 interface (if configured).
*.IP_Addr3
Enter the IP address of the hme2 interface (if configured).
*.IP_Addr4
Enter the IP address of the hme3 interface (if configured).
Configuring Engine Parameters
For the engine to run correctly, you must modify the following parameters in the Engine section of the
XECfgParm.dat file:
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-32
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
engine.CALL_MEM_BLOCK_SIZE
Block of memory allocated per call.
Used by MDL.
Default:
Prior to Release 9.4(1): 0
•
For memory-critical configurations, use the default
value.
•
For performance-critical configurations, set this value to
110000.
Release 9.4(1) and up: set automatically based on the type
of Cisco MGC selected in engine.SysVirtualSwitch. Any
attempt to modify this value is overwritten.
engine.CALL_MEM_CHUNK_SIZE Memory chunks allocated from the block of memory
designated with engine.CALL_MEM_BLOCK_SIZE.
Default:
Prior to Release 9.4(1): 0
•
For memory-critical configurations, use the default
value.
•
For performance-critical configurations, set this value to
110000.
Release 9.4(1) and up: set automatically based on the type
of Cisco MGC selected in engine.SysVirtualSwitch. Any
attempt to modify this value is overwritten.
engine.SendHardwareBlock
To enable the Cisco MGC to send hardware-oriented blocking
messages for any blocks that originate from the media
gateways:
•
true—Sends hardware-oriented blocking messages for
any blocks that originate from the media gateways.
•
false—Sends only maintenance-oriented blocking
messages for all blocking cases (default).
Note
The functionality for this parameter is added in a
patch for Release 9.3(2) and up. If your system is
running Release 9.3(2) or Release 9.4(1) you must
enter this parameter in the XECfgParm.dat file
manually after installing the patch. If your system is
running Release 9.5(2), the parameter is
automatically added to the XECfgParm.dat file during
the patch installation.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-33
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
engine.SysCdrCollection
To designate the format of call detail records (CDRs), enter
one of the following values:
•
true—Generates old-style non-tagged CDRs
•
false—Generates new tag, length, and value (TLV)
format CDRs (default)
Note
engine.SysVirtualSwitch
Typically, this value should be false.
To indicate whether the Cisco MGC host functions as a
signaling controller or a virtual switch controller, enter one of
the following values:
•
0—Signaling controller (nailed trunks, no auditing is
initiated)
•
1—Virtual switch controller (switched trunks)
Note
For Release 9.4(1) and up, the values of the
parameters listed below are automatically set based
on the Cisco MGC type you select, to maximize
performance for that configuration. Any attempt to
change the values of these parameters is overwritten.
engine.SysMdlMemoryReduction
engine.CALL_MEM_BLOCK_SIZE
engine.CALL_MEM_CHUNK_SIZE
*.CPUTimerInterval
*.numberOfThreads
engine.SysGRSTimerInterval
To specify the interval between blocks of Circuit Group Reset
(GRS) messages when the engine.SysGRSBlockSize
parameter is used, set to the value required (in milliseconds).
engine.SysGRSBlockSize
Many Circuit Group Reset (GRS) messages can become due
for sending at the same time. This situation occurs if you have
set the *.GRSEnabled parameter to true during provisioning.
The *.GRSEnabled parameter is a property that is set on an
SS7 signaling service (in the CMM) or an SS7 path (in
MML).
GRS messages can be staggered by sending in blocks. Set the
engine.SysGRSBlockSize parameter to the number of
messages to be sent in each block. Use the
engine.SysGRSTimerInterval parameter to set the time from
the start of one block to the start of the next.
Default: 0
Note
This parameter operates independently for each SS7
route (each OPC/DPC pair).
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-34
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
engine.SysGeneratedCode
To determine whether compiled or interpreted code is used,
enter one of the following values:
•
true—System uses compiled code (default).
•
false—System uses interpreted code (used only for
engineering and debugging).
Compiled code runs faster than interpreted code.
Typically, this value should be true. If your
configuration uses multiple CPUs, this value must be
true.
Note
*.SysConnectDataAccess
This parameter controls if data access is enabled or disabled
and if the engine attempts to connect to the MMDB at startup.
Set this parameter to true for calling scenarios where
European LNP, A-number screening, or other features
requiring real-time database access are used.
If you do not need real-time database access, set this
parameter to false to increase the available system memory
that can be used for call processing.
Enabling Call Screening
To initialize the database that stores call screening information, modify the following parameter in the
Engine section of the XECfgParm.dat file:
Parameter
Modification
*.SysConnectDataAccess
Controls whether data access is enabled or disabled (whether
the engine attempts to connect to the MMDB at startup.
Values:
•
true = connect to MMDB
•
false = do not connect to MMDB
Default: false
Note
In calling scenarios where Euro-LNP, A Number
Screening, or other features requiring real time
database access are required, this parameter must be
set to true. Otherwise, it can remain false for an
increase in the available system memory usable for
call processing.
Note
This parameter replaces the SysScreeningCheck
parameter.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-35
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Configuring Call Detail Record File Output
To configure call detail record (CDR) file output, modify the following parameters in the Data Dumper
and Engine sections of the XECfgParm.dat file:
Parameter
Modification
engine.CDRencodingFormat
To specify the call detail record (CDR) file encoding format,
enter one of the following values:
engine.CDRmessageTypes
•
AnsiCDB—North American (default)
•
ItuCDB—European
To specify the Call Detail Blocks (CDBs are the accounting
records written at various points in a call) that are generated
during a call, enter one of the following sets of values (each
number represents a point in a call):
•
1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080—These
are considered the “event-based” set of values. Use this
event-based list when you want to receive all CDR
records at predefined points in the call. Although each of
these CDBs can be specified independently, Cisco
suggests that you use the event-based set as a "package"
of CDBs for full accounting purposes.
Note
The event-based setting is required when
operating the Cisco MGC in conjunction with the
BAMS adjunct.
•
1060, 1110—Use this value if you want end-of-call
summary-type records only.
•
1071—Use this set of values for BAMS measurements.
Refer to the chapter “Detailed CDB Description” in the Cisco
Media Gateway Controller Software Release 9 Billing
Interface Guide for details on each CDB.
engine.CDRtimeStamp
Specifies the time stamp unit in seconds or milliseconds.
To specify the CDR file time-stamp unit, enter one of the
following values:
•
S—Seconds (default).
•
M—Milliseconds. Use this parameter if your
configuration uses TCAP or if you want the millisecond
granularity in all of your CDR records.
Note
The M setting is mandatory when operating the
Cisco MGC in conjunction with the BAMS
adjunct.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-36
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
cdrDmpr.callDetail
Specifies that call detail record (CDR) files may be
automatically converted from binary format to ASCII,
comma-delimited format.
Default: /opt/CiscoMGC/local/cdbscript.sh
Optional: /opt/CiscoMGC/bin/converter (if binary CDR
files need to be converted to ASCII)
The default CDR file format has changed from an
ASCII format in Release 4 to a binary format in
Release 7. The ASCII file has a .csv extension.
Note
For more information on generating and viewing
CDR files, see the Cisco Media Gateway Controller
Software Release 9 Operations, Maintenance, and
Troubleshooting Guide.
dmpr.openCDR
Specifies whether the standard data dumper should write out
CDR files.
Values:
•
true = Standard data dumper opens a CDR file and log
the call data blocks (CDB).
•
false = Standard data dumper does not open a CDR file
and does not log CDBs.
Default: true
Note
The default format for CDR files has been changed
since release 4 from an ASCII format to a binary
format. Use the dmpr.callDetail parameter to convert
the files to an ASCII format, if necessary.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-37
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Configuring the Clearing Location and Default Location Parameters
This property overrides the Clearing Location and Default Location fields in Call Context. Change
the clearing location value if you need a value other than the default to be sent to the switch.
Change the default location value if you need to define a customer-specific default location for your
system that can differ from the default location set in the type definition of the protocol.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-38
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
ClearingLocation
This property overrides the Clearing Location field in
Call Context. Change this value if you need a value other
than the default to be sent to the switch. Valid values are:
•
0—The Cisco MGC software uses the default Clearing
Location in Call Context.
•
1—The Cisco MGC software overrides the Clearing
Location in Call Context with LOCATION_USER
•
2—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
PRIVATE_LOCAL
•
3—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_ PUBLIC_LOCAL
•
4—The Cisco MGC software overrides the Clearing
Location in Call Context with
LOCATION_TRANSIT
•
5—The Cisco MGC software overrides the Clearing
Location in Call Context with LOCATION_
PUBLIC_REMOTE
•
6—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
PRIVATE_REMOTE
•
7—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
INTERNATIONAL
•
8—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
INTERWORKING
•
9—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
LOCAL_INTERFACE
•
10—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_ LOCAL_LOCAL
•
11—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
LOCAL_REMOTE
•
12—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_
PACKET_MANAGER
•
13—The Cisco MGC overrides the Clearing Location
in Call Context with LOCATION_ UNKNOWN
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-39
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
DefaultLocation
This property overrides the Default Location field in Call
Context. Change this value if you need to define a
customer-specific default location for your system that can
differ from the default location set in the type definition of the
protocol. Valid values are:
•
0—The Cisco MGC software uses the Default
Location in Call Context
•
1—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_USER
•
2—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
PRIVATE_LOCAL
•
3—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
PUBLIC_LOCAL
•
4—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_TRANSIT
•
5—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
PUBLIC_REMOTE
•
6—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
PRIVATE_REMOTE
•
7—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
INTERNATIONAL
•
8—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
INTERWORKING
•
9—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
LOCAL_INTERFACE
•
10—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
LOCAL_LOCAL
•
11—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
LOCAL_REMOTE
•
12—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
PACKET_MANAGER
•
13—The Cisco MGC software overrides the Default
Location in Call Context with LOCATION_
UNKNOWN
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-40
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Configuring Switchover
To configure switchover, modify the following parameters in the foverd section of the XECfgParm.dat
file.
:
Parameter
Modification
foverd.conn1Type
To set the connection type for connection number 1, enter serial or
socket.
Typically, set this value to socket.
Note
foverd.ipLocalPortA
To define the local port number used for IP communication, enter
a unique number, keeping the following in mind:
•
Typically, if Type is socket, set this value to 1051.
•
If you have two Cisco MGC hosts in a fault tolerant
configuration, enter the foverd.ipLocalPortA value in the
foverd.ipPeerPortA field in the XECfgParm.dat file on the
secondary host.
Caution
foverd.ipPeerPortA
To define the peer port number used for IP communication, enter a
unique number, keeping the following in mind:
•
Typically, if Type is socket, set this value to 1052.
•
If you have two Cisco MGC hosts in a switchover
configuration, enter the foverd.ipPeerPortA value in the
foverd.ipLocalPortA field in the XECfgParm.dat file on the
secondary host.
Caution
foverd.conn2Type
The value of foverd.ipLocalPortA must be unique for
every host on the network. Otherwise, active and
standby hosts cannot communicate properly. In the
instance discussed here, no other machine on the
network can have foverd.ipLocalPortA set to 1051. If
that happens, the active and standby hosts cannot
perform proper switchover.
The value of foverd.ipPeerPortA must be unique for
every host on the network. Otherwise, active and
standby hosts cannot communicate properly. In the
instance discussed here, no other machine on the
network can have foverd.ipPeerPortA set to 1052. If
that happens, the active and standby hosts cannot
perform proper switchover.
To set the connection type for connection number 2, enter serial or
socket.
Note
Typically, set this value to socket.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-41
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
foverd.ipLocalPortB
To define the secondary local port number used for IP
communication, enter a unique number, keeping the following in
mind:
•
Typically, if Type is socket, set this value to 1053.
•
If you have two Cisco MGC hosts in a switchover
configuration, enter this value in the foverd.ipPeerPortB field
in the XECfgParm.dat file on the secondary host.
Caution
foverd.ipPeerPortB
To define the secondary local port number used for IP
communication, enter a unique number, keeping the following in
mind:
•
Typically, if Type is socket, set this value to 1054.
•
If you have two Cisco MGC hosts in a switchover
configuration, enter this value in the foverd.ipLocalPortB field
in the XECfgParm.dat file on the secondary host.
Caution
foverd.conn3Type
The value of foverd.ipPeerPortB must be unique for
every host on the network. Otherwise, master and
slave hosts cannot communicate properly. In the
instance discussed here, no other machine on the
network can have foverd.ipPeerPortB set to 1054. If
that happens, the master and slave hosts cannot
perform proper switchover.
To set the connection type for connection number 3, enter serial or
socket.
Note
foverd.conn3Addr
The value of foverd.ipLocalPortB must be unique for
every host on the network. Otherwise, active and
standby hosts cannot communicate properly. In the
instance discussed here, no other machine on the
network can have foverd.ipLocalPortB set to 1053. If
that happens, the active and standby hosts cannot
perform proper switchover.
Typically, set this value to serial.
To specify the address of the peer system, enter a location; for
example, /dev/term/a.
If your configuration does not use connection number 3, enter
/dev/null (default).
Note
If your configuration uses an 8-port connector as a serial
connection for switchover, you must modify the read-write
permissions for the connection.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-42
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
foverd.abswitchPort
To specify the port used for communication with the A/B switch,
enter a location; for example, /dev/term/a.
Note
foverd.heartbeatInterval
If your configuration does not use an A/B switch, use the
default value (/dev/null).
Specifies the maximum time in milliseconds between heartbeat
messages from the peer switchover daemon. This interval defines
the frequency with which the switchover daemon exchanges
heartbeat messages with its peer.
Default: 1000 milliseconds (1 second).
Note
For more information on switchover, see Cisco Media Gateway Controller Software Release 9
Operations, Maintenance, and Troubleshooting Guide.
Initializing the Provisioning Object Manager
To configure the Provisioning Object Manager (POM), modify the following parameters in the POM
section of the XECfgParm.dat file:
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-43
Chapter 5
Configuring the Cisco MGC Software
Configuring the Execution Environment
Parameter
Modification
pom.dataSync
Used in a fault tolerant system to indicate that the POM should
synchronize the provisioning data at startup.
•
If you have a standalone system, set this value to false.
•
If you have a fault tolerant system, set this value to true.
Caution
Note
If pom.dataSync is set to true for a fault tolerant
system, you must ensure that you are running the
same version of the Cisco MGC software on both
active and standby machines. Otherwise, the wrong
version of your data files may be copied to the other
machine.
When the initial Cisco MGC configuration on the active
host is deployed, you must change the pom.dataSync
parameter to true in the XECfgParm.dat file in the
standby host. After setting this parameter to true, you
can start the Cisco MGC on the standby host. As the
Cisco MGC comes up, the data on the standby host is
synchronized with the data on the active host and the
active host goes into the standby state.
To accommodate failover conditions where the current
active host can become the standby host, you must also
set the pom.dataSync parameter to true on the current
active host.
pom.port
Used in a fault tolerant configuration to indicate the port number
that the POM uses to communicate with its peer. Enter any integer
from 4001 through 4050, or default.
Note
This is a platform-specific value and depends on your
system installation. You should modify this value only if the
default port (4001) is being used by another process or
application.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-44
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
Configuring SCP Queries
The SCP translates routing information for the Advanced Intelligent Network (AIN) database queries
over TCAP. This section provides instructions for selecting the type of translation you use to enable SCP
database queries. If your site or network requires changes, you can enable SCP queries by manually
editing the parameters in the trigger.dat file. The trigger.dat file (located in /opt/CiscoMGC/etc) contains
the message-sending table that contains translation values.
This section contains the following topics:
Warning
Note
•
Before You Start, page 5-45
•
Configuring the trigger.dat File Attributes, page 5-45
•
Sample trigger.dat File, page 5-49
Do not edit trigger.dat file parameters that are not listed below, and remember that all parameters are
case-sensitive. Otherwise, your system might not work as intended.
The following Bellcore Standards are supported for US 800 toll-free services:
IN/1 Toll Free Service support : GR-1428
AIN 0.1 Toll Free Service support : GR-2902
Before You Start
If you are changing an ANSI query and you need a different Translation Type, you need to know the
Translationtype value from the Global Title Translation tables on the Signal Transfer Point (STP). Get
this value from the administrator of your STP.
Configuring the trigger.dat File Attributes
Note
The trigger.dat file is not overwritten during software installation. All changes to the trigger.dat file are
contained in a file called trigger.template that is installed with the new software. If you modify the
trigger.dat file after installing a new software release, you need to view the trigger.template file and copy
any changes in that file to your trigger.dat file.
Caution
Improper editing of the trigger.dat file can cause service interruption and prevent the Cisco MGC from
correctly performing SCP database queries.
You can configure the following Cisco MGC trigger.dat file attributes to perform a Transaction
Capabilities Application Part (TCAP) query:
•
Global Title Translation
•
Service Key Value
•
Translation Type
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-45
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
Configuring the Global Title Translation Attribute
Perform the following steps to configure the Global Title Translation attribute:
Step 1
Back up the trigger.dat file.
Step 2
Determine the Trigger Number that you need to edit. You can get this information from your network
administrator.
Step 3
Navigate to directory /opt/CiscoMGC/etc.
Step 4
Open the trigger definition file in an ASCII text editor and search for the string $TriggerTable.
Step 5
Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from
the number 1.
Note
Do not count any row that is blank or that begins with a pound sign (#).
Step 6
When you find your row, note down the second number in that row. This number is the index to the
$MessageSending table.
Step 7
Edit the file as follows:
a.
In the $MessageSending table, select column 9, gtSsn (see Table 5-5).
b.
In the table for your translation type, change the Global Title Translation value (column F9) to either
0 or 1. You can get this information from your network administrator. If the number is 0, use GTT.
If the number is 1, use PC/SSN.
c.
If you change the gtSsn value to 0, you must go to gtFormat in column 16 and reset the value to 0.
If you set the value to 1, you must also set column 16 to a non-zero value.
Note
See Table 5-5 for table values.
Step 8
Save your changes and close the editor.
Step 9
For your changes to take effect you must reboot the Cisco MGC by entering the following command:
# /etc/init.d/CiscoMGC start
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
Configuring the Service Key Value Attribute
Perform the following steps to configure the Service Key Value (tcv_sk) attribute:
Step 1
Back up the trigger.dat file.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-46
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
Step 2
Determine the Trigger Number that you need to edit. You can get this information from your network
administrator.
Step 3
Navigate to directory /opt/CiscoMGC/etc.
Step 4
Open the trigger.dat file in an ASCII text editor and search for the string $TriggerTable.
Step 5
Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from
the number 1.
Do not count any row that is blank or that begins with a pound sign (#).
Note
Step 6
When you find your row, note down the second number in that row. This number is the index to the
$MessageSending table.
Caution
Step 7
Do not change TCVs. You must verify that column 2 is equal to 1 before changing tcv_sk. If
column 2 is not equal to 1, this is not an ETSI trigger and column 6 is a TCV, not an SK.
Edit the trigger.dat file as follows:
a.
In the $MessageSending table, select tcv_sk, in column 6 (see Table 5-5).
b.
In the table, change the value for tcv_sk to a value from 0 through 255. You can get this information
from your network administrator.
Step 8
Save your changes and close the editor.
Step 9
Restart the Cisco MGC software by entering the following command:
# /etc/init.d/CiscoMGC start
Configuring the Translation Type Attribute
Perform the following steps to configure the Translation Type (translationType) attribute:
Step 1
Back up the trigger.dat file.
Step 2
Determine the Trigger Number that you need to edit. You can get this information from your network
administrator.
Step 3
Navigate to directory /opt/CiscoMGC/etc.
Step 4
Open the trigger definition file in an ASCII text editor and search for the string $TriggerTable.
Step 5
Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from
the number 1.
Note
Step 6
Do not count any row that is blank or that begins with a pound sign (#).
When you find your row, note down the second number in that row. This number is the index to the
$MessageSending table.
Caution
You must verify that column 2 is equal to 2 or 3 before changing Translation Type. If column
2 is not equal to 2 or 3, this is not an ANSI trigger and Translation Type is not used.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-47
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
Edit the file as follows:
Step 7
a.
In the $MessageSending table, select translationType, in column 7 (see Table 5-5).
b.
In the table for your translation type, change the value for translationType to a value from 0 through
255. You can get this information from your network administrator.
Step 8
Save your changes and close the editor.
Step 9
For your changes to take effect you must reboot the Cisco MGC by entering the following command:
# /etc/init.d/CiscoMGC start
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
Note
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
F19
F20
F21
OS5
F18
OS4
F17
OS3
F16
OS2
F15
OS1
F14
gtFormat
F13
ssn
F12
dpcMember
F11
dpcCluster
F10
dpcNetwork
F9
ssnPres
F8
dpcPres
F7
gtSsn
F6
tcapBodyType
msg
tcapType
F5
translationType
F4
tcv_sk
F3
stpScpGroupIndex
F2
Transport
F1
$MessageSending Table Values
asn1Encoding
Table 5-5
# MS 1: xxxxxx LNP
1
2
0
6
0
0
255
1
0
0
1
0
0
0
0
2
1
0
0
0
0
6
0
37
255
1
0
0
1
0
0
0
0
2
2
0
0
0
0
1
0
0
0
1
0
0
1
0
0
0
0
2
3
0
0
0
0
0
4
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
5
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
# MS 2: Generic LNP
1
2
0
# MS 3: xxxxxxx 800
2
1
1
# MS 4: ANSI AIN 800 NPA
1
2
0
6
# MS 5: ANSI AIN 800 NPA-NXX
1
2
0
6
0
# MS 6: ANSI AIN 800 NPA-NXX-XXX
1
2
0
6
0
8
# MS 7: ANSI AIN 800 Termination information
1
2
0
5
0
0
255
1
0
0
1
0
0
0
0
2
5
0
0
0
0
0
0
254
2
0
0
1
0
0
0
0
2
6
0
0
0
0
0
0
1
0
0
0
0
2
7
0
0
0
0
# MS 8: ANSI PRE AIN 800
1
3
0
6
# MS 9: ANSI PRE AIN 800 Termination information
1
3
0
5
0
0
254
2
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-48
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
Sample trigger.dat File
#--//******************************************************************************
#--//* Table_9.trigger
*
#--//*
*
#--//* TRIGGER TABLES
*
#--//*
*
#--//* (c) 1999-2000 CISCO SYSTEMS, INC. ALL RIGHTS RESERVED.
*
#--//* THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF
*
#--//* CISCO SYSTEMS, INC. USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED
*
#--//* WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF THE CISCO SYSTEMS, INC.
*
#--//*
*
#--//******************************************************************************
# "$Id: Table_9.trigger,v 1.11.2.3 1999/09/20 18:20:51 xxxxxxxx Exp $";
# "(c) 1999-2000 Cisco Systems, Inc. All Rights Reserved."
#############
$TriggerTable
#############
# All fields are pointers to records of other types
# F1
F2
F3
F4
F5
F6
F7
# MA
MS
RR1 RR2 RR3 RR4 RR5
#---------------------------------# TT 1: xxxxxx LNP
#---------------------------------1
1
1
2
0
0
0
#---------------------------------# TT 2: Generic LNP
#---------------------------------2
2
1
3
0
0
0
#---------------------------------# TT 3: xxxxxxx 800
#---------------------------------3
3
10
4
5
0
0
#---------------------------------# TT 4: ANSI AIN 800 NPA
#---------------------------------4
4
10
6
7
0
0
#---------------------------------# TT 5: ANSI AIN 800 NPA-NXX
#---------------------------------4
5
10
6
7
0
0
#---------------------------------# TT 6: ANSI AIN 800 NPA-NXX-XXXX
#---------------------------------4
6
10
6
7
0
0
#---------------------------------# TT 7: ANSI AIN 800 Termination Information
#---------------------------------5
7
10
0
0
0
0
#---------------------------------# TT 8: ANSI PRE AIN AIN 800
#---------------------------------4
8
10
8
9
0
0
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-49
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#---------------------------------# TT 9: ANSI PRE AIN 800 Termination Information
#---------------------------------5
9
10
0
0
0
0
##############
$MessageAction
##############
#
# F1
F2
F3
F4
# ACT1 REQ ACT2 REQ
F5
F6
ACT3 REQ
F7
F8
ACT4 REQ
F9
F10
ACT5 REQ
#------------------------------------------------# MA 1: xxxxxx LNP
#------------------------------------------------1
1
3
0
0
0
0
0
0
0
#------------------------------------------------# MA 2: Generic LNP
#------------------------------------------------1
1
2
1
3
0
0
0
0
0
#------------------------------------------------# MA 3: xxxxxxx 800
#------------------------------------------------1
1
3
0
0
0
0
0
0
0
#------------------------------------------------# MA 4: ANSI AIN 800 / ANSI PRE AIN 800
#------------------------------------------------1
1
3
0
0
0
0
0
0
0
#------------------------------------------------# MA 5: ANSI AIN 800 Termination Information / PRE AIN 800 Termination Information
#------------------------------------------------4
1
0
0
0
0
0
0
0
0
###############
$MessageSending
###############
#
# gtFormat Values
# GTFORMAT_DO_NOT_USE_GLOBAL_TITLE
:= 0
# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE_NUMBERING_SCHEME_ENCODING_SCHEME := 1
# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE
:= 2
# GTFORMAT_USE_GLOBAL_TITLE_ONLY
:= 3
# GTFORMAT_UNKNOWN
:= 4
#
Note
To see proper formatting for the table below, see Table 5-5.
# F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 F16 F17 F18 F19 F20 F21
# transport tcapType stpScpGroupIndex msg asn1Encoding tcv_sk translationType tcapBodyType
gtSsn dpcPres ssnPres dpcNetwork dpcCluster dpcMember ssn gtFormat OS1 OS2 OS3 OS4 OS5
#---------------------------------------------------------------------------------------# MS 1: xxxxxx LNP
#---------------------------------------------------------------------------------------1 2 0 6 0 0 255 1 0 0 1 0 0 0 0 2 1 0 0 0 0
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-50
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#---------------------------------------------------------------------------------------# MS 2: Generic LNP
#---------------------------------------------------------------------------------------1 2 6 37 255 0 1 0 0 2 0 0 0 0
#---------------------------------------------------------------------------------------# MS 3: xxxxxxx 800
#---------------------------------------------------------------------------------------2 1 1 0 1 0 0 0 2 0 0
#---------------------------------------------------------------------------------------# MS 4: ANSI AIN 800 NPA
#---------------------------------------------------------------------------------------1 2 0 6 0 4 255 1 0 0 1 0 0 0 0 2 4 0 0 0 0
#---------------------------------------------------------------------------------------# MS 5: ANSI AIN 800 NPA-NXX
#---------------------------------------------------------------------------------------1 2 0 0 255 0 1 0 0 4 0 0
#---------------------------------------------------------------------------------------# MS 6: ANSI AIN 800 NPA-NXX-XXX
#---------------------------------------------------------------------------------------1 2 0 6 0 8 255 1 0 0 1 0 0 0 0 2 4 0 0 0 0
#---------------------------------------------------------------------------------------# MS 7: ANSI AIN 800 Termination information
#---------------------------------------------------------------------------------------1 2 0 5 0 0 255 1 0 0 1 0 0 0 0 2 5 0 0 0 0
#---------------------------------------------------------------------------------------# MS 8: ANSI PRE AIN 800
#---------------------------------------------------------------------------------------1 3 0 6 0 0 254 2 0 0 1 0 0 0 0 2 6 0 0 0 0
#---------------------------------------------------------------------------------------# MS 9: ANSI PRE AIN 800 Termination information
#---------------------------------------------------------------------------------------1 3 0 5 0 0 254 2 0 0 1 0 0 0 0 2 7 0 0 0 0
################
$OperationSending
#################
#
# F1
F2
# componentType opClass
# F6
F7
# correlationRequired PS
F3
opCodeFamily
F4
F5
opCodeSpecifier opCodeFlag
#---------------------------------------------------------------------------------------# OS 1: xxxxxx LNP
#---------------------------------------------------------------------------------------6 1 3 0
#---------------------------------------------------------------------------------------# OS 2: Generic LNP
#---------------------------------------------------------------------------------------6 100 4 2
#---------------------------------------------------------------------------------------# OS 3: xxxxxxx 800
#---------------------------------------------------------------------------------------1 0 4 3
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-51
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#---------------------------------------------------------------------------------------# OS 4: ANSI AIN 800
#---------------------------------------------------------------------------------------6 100 4 0 4
#---------------------------------------------------------------------------------------# OS 5: ANSI AIN 800 Termination Information Should have correlationRequired = 1
#---------------------------------------------------------------------------------------6 1 103 4 4 0 5
#---------------------------------------------------------------------------------------# OS 6: ANSI PRE AIN 800
#---------------------------------------------------------------------------------------6 1 3 1 3 0 6
#---------------------------------------------------------------------------------------# OS 7: ANSI PRE AIN 800 Termination Information
#---------------------------------------------------------------------------------------2 1 0 0 0 0 7
################
$ParameterSending
#################
#
# F1
F2
F3
F4
# PA1 REQ PA2 REQ
# F19 F20
# PA10 REQ
F5
PA3
F6
REQ
F7
PA4
F8
REQ
F9
PA5
F10
REQ
F11
PA6
F12
REQ
F13
PA7
F14
REQ
F15
PA8
F16
REQ
F17 F18
PA9 REQ
#---------------------------------------------------------------------------------------# PS 1: xxxxxx LNP
#---------------------------------------------------------------------------------------100 1 101 1 102 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#---------------------------------------------------------------------------------------# PS 2: Generic LNP
#---------------------------------------------------------------------------------------100 1 101 1 102 1 103 1 0 0 0 0 0 0 0 0 0 0 0 0
#---------------------------------------------------------------------------------------# PS 3: xxxxxxx 800
#---------------------------------------------------------------------------------------200 1 201 1 202 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#---------------------------------------------------------------------------------------# PS 4: ANSI AIN 800 (All types)
#---------------------------------------------------------------------------------------100 1 101 1 102 1 103 1 104 1 109 0 110 0 111 0 112 0 113 0
#---------------------------------------------------------------------------------------# PS 5: ANSI AIN 800 Termination Information
#---------------------------------------------------------------------------------------105 1 106 1 107 0 108 0 0 0 0 0 0 0 0 0 0 0 0 0
#---------------------------------------------------------------------------------------# PS 6: ANSI PRE AIN 800
#---------------------------------------------------------------------------------------17 1 2 1 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#---------------------------------------------------------------------------------------# PS 7: ANSI PRE AIN 800 Termination Information
#----------------------------------------------------------------------------------------
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-52
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
21 1 20 1 22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#################
$ReceivedResponse
#################
#
# F1
F2
# MR
RA
#---------------------------------------------------------------------------------------# RR 1: xxxxxx LNP / Generic LNP Default
#---------------------------------------------------------------------------------------0
1
#---------------------------------------------------------------------------------------# RR 2: xxxxxx LNP 1st expected
#---------------------------------------------------------------------------------------1
2
#---------------------------------------------------------------------------------------# RR 3: Generic LNP 1st expected
#---------------------------------------------------------------------------------------1
3
#---------------------------------------------------------------------------------------# RR 4: xxxxxxx 800 1st expected (Result)
#---------------------------------------------------------------------------------------2
1
#---------------------------------------------------------------------------------------# RR 5: xxxxxxx 800 2st expected (Error)
#---------------------------------------------------------------------------------------3
4
#---------------------------------------------------------------------------------------# RR 6: ANSI AIN 800 With termination status notification
#---------------------------------------------------------------------------------------4
5
#---------------------------------------------------------------------------------------# RR 7: ANSI AIN 800
#---------------------------------------------------------------------------------------5
6
#---------------------------------------------------------------------------------------# RR 8: ANSI PRE AIN 800 With termination status notification
#---------------------------------------------------------------------------------------6
7
#---------------------------------------------------------------------------------------# RR 9: ANSI PRE AIN 800
#---------------------------------------------------------------------------------------7
8
#---------------------------------------------------------------------------------------# RR 10: ANSI AIN 800 / PRE AIN 800 Default
#---------------------------------------------------------------------------------------0
9
#################
$MessageReceiving
#################
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-53
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#
# F1
# MSG
F2
OR1
F3
REQ
F4
OR2
F5
REQ
F6
OR3
F7
REQ
F8
OR4
F9
REQ
F10
OR5
F11
REQ
#-----------------------------------------------------# MR 1: xxxxxx LNP / Generic LNP
#-----------------------------------------------------8
1
1
0
0
0
0
0
0
0
0
#-----------------------------------------------------# MR 2: xxxxxxx 800 (Result)
#-----------------------------------------------------3
2
1
0
0
0
0
0
0
0
0
#-----------------------------------------------------# MR 3: xxxxxxx 800 (Error)
#-----------------------------------------------------3
3
1
0
0
0
0
0
0
0
0
#-----------------------------------------------------# MR 4: ANSI AIN 800 with termination status notification
#-----------------------------------------------------8
4
1
5
1
0
0
0
0
0
0
#-----------------------------------------------------# MR 5: ANSI AIN 800
#-----------------------------------------------------8
4
1
0
0
0
0
0
0
0
0
#-----------------------------------------------------# MR 6: ANSI PRE AIN 800 with termination status notification
#-----------------------------------------------------8
6
1
7
1
0
0
0
0
0
0
#-----------------------------------------------------# MR 7: ANSI PRE AIN 800
#-----------------------------------------------------8
6
1
0
0
0
0
0
0
0
0
###################
$OperationReceiving
###################
#
# F1
F2
# componentType opClass
F3
F4
F5
F6
opCodeFamily opCodeSpecifier opCodeFlag PR
#---------------------------------------------------------------------# OR 1: xxxxxx LNP / Generic LNP
#---------------------------------------------------------------------6
1
101
1
4
1
#---------------------------------------------------------------------# OR 2: xxxxxxx 800 (Result)
#---------------------------------------------------------------------1
1
0
20
4
2
#---------------------------------------------------------------------# OR 3: xxxxxxx 800 (Error)
#---------------------------------------------------------------------3
1
0
0
4
3
#---------------------------------------------------------------------# OR 4: ANSI AIN 800
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-54
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#---------------------------------------------------------------------6
1
101
1
4
4
#---------------------------------------------------------------------# OR 5: ANSI AIN 800 Request for status notification
#---------------------------------------------------------------------6
1
103
5
4
5
#---------------------------------------------------------------------# OR 6: ANSI PRE AIN 800
#---------------------------------------------------------------------6
1
4
1
3
6
#---------------------------------------------------------------------# OR 7: ANSI PRE AIN 800 Request for status notification
#---------------------------------------------------------------------6
1
6
1
4
7
###################
$ParameterReceiving
###################
# F1
# PA1
REQ
ACT
F2
REQ
F17
PA7
F3
ACT
F18
REQ
F4
PA2
F19
ACT
F5
REQ
F20
PA8
F6
ACT
F21
REQ
F7
PA3
F22
ACT
F8
REQ
F23
PA9
F9
ACT
F24
REQ
F10
PA4
F25
ACT
F11
REQ
F26
PA10
F12
ACT
F27
REQ
F13
PA5
F28
ACT
F14
REQ
F29
F15
ACT
F30
F16
PA6
#---------------------------------------------------------------------------------------# PR 1: xxxxxx LNP / Generic LNP
#---------------------------------------------------------------------------------------102 1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#---------------------------------------------------------------------------------------# PR 2: xxxxxxx 800 (Result)
#---------------------------------------------------------------------------------------205 1
1
206 1
1
204 1
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#---------------------------------------------------------------------------------------# PR 3: xxxxxxx 800 (Error)
#---------------------------------------------------------------------------------------205 1
1
206 1
1
204 1
3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#---------------------------------------------------------------------------------------# PR 4: ANSI AIN 800 Result
#---------------------------------------------------------------------------------------102 1
1
110 0
2
113 0
2
114 1
2
115 1
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#---------------------------------------------------------------------------------------# PR 5: ANSI AIN 800 Status request
#---------------------------------------------------------------------------------------105 1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#---------------------------------------------------------------------------------------# PR 6: ANSI PRE AIN 800 Result
#---------------------------------------------------------------------------------------8
0
2
4
1
1
18
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-55
Chapter 5
Configuring the Cisco MGC Software
Configuring SCP Queries
#---------------------------------------------------------------------------------------# PR 7: ANSI PRE AIN 800 Status request
#---------------------------------------------------------------------------------------20
1
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
###############
$ResponseAction
###############
#
# F1
F2
F3
# ACT1 REQ DAT
F4
F5
ACT2 REQ
F6
DAT
F7
F8
ACT3 REQ
F9
DAT
F10 F11
ACT4 REQ
F12
DAT
F13 F14
ACT5 REQ
F15
DAT
#-------------------------------------------------------------------------# RA 1: xxxxxx LNP Default & Generic LNP Default
#-------------------------------------------------------------------------4
1
2
0
0
0
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 2: xxxxxx LNP 1st Expected
#-------------------------------------------------------------------------4
1
2
0
0
0
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 3: Generic LNP 1st Expected
#-------------------------------------------------------------------------1
1
0
4
1
2
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 4: xxxxxxx (Error)
#-------------------------------------------------------------------------0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 5: ANSI AIN 800 with termination status notification
#-------------------------------------------------------------------------2
0
1
4
1
3
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 6: ANSI AIN AIN 800
#-------------------------------------------------------------------------4
1
3
0
0
0
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 7: ANSI PRE AIN 800 with termination status notification
#-------------------------------------------------------------------------2
0
4
4
1
3
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 8: ANSI PRE AIN 800
#-------------------------------------------------------------------------4
1
3
0
0
0
0
0
0
0
0
0
0
0
0
#-------------------------------------------------------------------------# RA 9: 800 Default
#-------------------------------------------------------------------------4
1
3
0
0
0
0
0
0
0
0
0
0
0
0
###########
$ActionData
###########
#
# F1
F2
F3
F4
F5
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-56
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
#----------------------# AD 1: ANSI AIN 800 Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination
information)
# Trg Pic
Null Null Null
#-------------------------7
13
0
0
0
# AD 2: ANSI LNP Data for RESULT_ACTION_SEND_ACTION_TO_LCM
# Act Null Null Null NULL
#-------------------------1
0
0
0
0
# AD 3: ANSI AIN / PRE AIN 800 Data for RESULT_ACTION_SEND_ACTION_TO_LCM
# Act Null Null Null NULL
#-------------------------2
0
0
0
0
# AD 4: ANSI PRE AIN 800 Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination
information)
# Trg Pic
Null Null Null
#-------------------------9
13
0
0
0
This completes the SCP configuration. Continue to the next section to initialize the call-screening
database. If you have questions or need assistance, see the “Obtaining Documentation, Obtaining
Support, and Security Guidelines” section on page xvii.
Initializing the Call Screening Database
This section contains the following topics:
Caution
•
.odbc.ini File Information, page 5-58
•
Setting Up Replication, page 5-58
•
Troubleshooting the Main Memory Database Replication, page 5-61
Cisco does not support the direct use of TimesTen commands (files found in /opt/TimesTen/32/bin).
Incorrect use of these commands can cause database corruption.
During installation, the installation script (install.sh) installs and initializes the Main Memory Database
(MMDB) that the Cisco MGC can use for the following:
•
Store call-screening information for calling- and called-number analysis
•
Ported Numbers
•
Number Termination
•
Multiple Dial Plan
•
Advice of Charge II
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-57
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
You might want to perform white and black list screening to include or exclude calls from certain
numbers. You can provision white lists that specify allowed A-numbers (calling numbers) or B-numbers
(called numbers). Black lists block specified A-numbers (calling numbers) or B-numbers (called
numbers). For more details, see the Cisco MGC Software Release 9 Dial Plan Guide.
The call screening database is stored in the /opt/TimesTen/datastore directory. The database name is
howdydb. The maximum database size, 256 MB, is specified in the .odbc.ini file shown in the .odbc.ini
File Information section, below.
Caution
Do not change the database name.
.odbc.ini File Information
The .odbc.ini file specifies the location of the database storage. Unless you installed the software to other
than the default directory, the .odbc.ini file is located in the /opt/CiscoMGC/local directory. The
following is an example of an .odbc.ini file:
[ODBC Data Sources]
howdydb=TimesTen 4.1 Driver
[howdydb]
Driver=/opt/TimesTen4.1/32/lib/libtten.so
DataStore= /opt/TimesTen4.1/datastore/howdydb
DurableCommits=0
ExclAccess=0
ThreadSafe=1
WaitForConnect=0
Size=256
[ODBC]
Trace=0
TraceFile=
Installdir=/opt/TimesTen4.1/32
Setting Up Replication
If you have two Cisco MGC hosts in a fault tolerant system, you must set up database replication
between the two hosts. During replication, any updates applied to the database on one host are replicated
on the other. Data is transferred real time and does not require committing or deploying a configuration.
Replication copies data changes to either database after the initial setup. If you have data in one database
and want to retain it, go to the host that has the data that you want to retain (usually this is the active
host), then follow the procedures below, “Initializing Database Replication” section on page 5-60.
Note
Before you can initialize the databases, you must install the Cisco MGC software on both machines.
Network Requirements
In most replication schemes, you need to identify the name of the host machine on which your data store
resides. The operating system translates this host name to an IP address. This section describes how to
configure your host names to ensure they use the correct IP addresses.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-58
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
Identifying data store hosts (UNIX and VxWorks)
If your Unix or VxWorks host has a single IP address and hostname, you can use the host name returned
by the hostname command on UNIX or the hostname() call on VxWorks. If a host contains multiple
network interfaces (with different IP addresses), TimesTen replication tries to connect to the IP address
in the same order as returned by the gethostbyname() call on UNIX or the hostGetByName() call on
VxWorks. It will try to connect using the first address; if a connection cannot be established, it tries the
remaining addresses in order until a connection is established. TimesTen replication uses this same
sequence each time it establishes a new connection to a host. If a connection to a host fails on one IP
address, TimesTen replication attempts to re-connect (or fall back) to another IP address for the host in
the same manner described above.
There are two basic ways you can configure a host to use multiple IP addresses on UNIX platforms: DNS
or /etc/hosts files. On VxWorks platforms you use the hostAdd() call. For example, the following entry
in the /etc/hosts file on a UNIX platform describes a server named Machine1 with two Ethernet IP
addresses:
10.10.98.102 Machine1
192.168.1.102 Machine1
To specify the same configuration for DNS, your entry in the domain zone file would look like:
Machine1 IN A 10.10.98.102
IN A 192.168.1.102
In either case, you only need to specify Machine1 as the hostname in your replication scheme and
replication will use the first available IP address when establishing a connection. In an environment in
which multiple IP addresses are used, you can also assign multiple host names to a single IP address in
order to restrict a replication connection to a specific IP address. For example, you might have an entry
in your /etc/hosts file that looks like:
10.10.98.102 Machine1
192.168.1.102 Machine1 RepMachine1
Or a DNS zone file that looks like:
Machine1 IN A 10.10.98.102
IN A 192.168.1.102
RepMachine1 IN A 192.168.1.102
Should you want to restrict replication connections to IP address 192.169.1.102 for this host, you can
specify RepMachine1 as the hostname in your replication scheme. (Another option is to simply specify
the IP address as the hostname in the CREATE REPLICATION statement used to configure your
replication scheme.)
The following are example hosts files from an active PGW host and an associated peer PGW host:
Active PGW Host /etc/hosts
27.0.0.1 localhost
192.168.11.1 UK-A-Netra1125-1 loghost
192.168.12.1 UK-A-Netra1125-1.hme1
192.168.11.2 UK-A-Netra1125-2
192.168.12.2 UK-A-Netra1125-2.hme1 UK-A-Netra1125-2 <----- Peer PGW hostname
Peer PGW Host /etc/hosts
127.0.0.1 localhost
192.168.11.2 UK-A-Netra1125-2 loghost
192.168.12.2 UK-A-Netra1125-2.hme1
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-59
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
192.168.11.1 UK-A-Netra1125-1 1
92.168.12.1 UK-A-Netra1125-1.hme1 UK-A-Netra1125-1 <----- Peer PGW hostname
Initializing Database Replication
To set up the initial replication, perform the following steps:
Step 1
Log in to the active host as mgcusr and enter the following command:
setup_replication.sh standbyhost active
Where standbyhost is the name (not IP address) of your standby host. In the example below, the active
host is hostx and the standby host is hosty.
Caution
Do not use IP addresses when setting up database replication. If you do, replication will fail.
Example 5-3
Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty active
Setting up replication to node
Adding cisco.whitelist_a
Adding cisco.blacklist_a
Adding cisco.whitelist_b
Adding cisco.blacklist_b
Adding cisco.portednumbers
Adding cisco.numberterm
RAM Residence Policy
:
RAM Residence Grace (Secs)
:
Manually Loaded In Ram
:
Purge Logs for Data Store
:
Logging Enabled
:
Replication Manually Started
:
Step 2
hosty for DSN howdydb
inUse
0
False
True
True
True
Log in to the standby host as the root user and stop the MGC software by entering the following UNIX
command:
/etc/init.d/CiscoMGC stop
Step 3
Log back in to the standby host as mgcusr.
Step 4
At the standby host, enter the following command:
setup_replication.sh activehost standby
where activehost is the name (not IP address) of your active host. In the example below, the active host
is hostx and the standby host is hosty.
Caution
Do not use IP addresses when setting up database replication. If you do, replication will fail.
Example 5-4
Initializing Database Replication on the Standby Host
Configuring replication for DSN=howdydb
Restoring file /opt/TimesTen4.1/datastore/howdydb.ds0 from backup
Restoring file /opt/TimesTen4.1/datastore/howdydb.log0 from backup
RAM Residence Policy
:inUse
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-60
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
Manually Loaded In Ram
Replication Agent Policy
Replication Manually Started
Oracle Agent Policy
Oracle Agent Manually Started
Replication setup completed.
Step 5
:False
:manual
:True
:manual
:False
Start the Cisco MGC by entering the following command:
/etc/init.d/CiscoMGC start
Proceed to “Verifying Database Replication”.
Verifying Database Replication
To verify that replication is working, perform the following steps:
Step 1
Log in to the active host and start an MML session by entering mml.
Step 2
Add an entry into the B white list database using the numan-add MML command. For example:
hostx mml> numan-add:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
VSC-01 - Media Gateway Controller 2000-08-30 11:31:25
M COMPLD
"bwhite"
;
Step 3
Log in to the standby host and start an MML session by entering mml.
Step 4
Enter the numan-rtrv MML command to verify that the entry you added in Step 3 was replicated to the
database on the standby host. For example:
hosty mml> numan-rtrv:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
VSC-01 - Media Gateway Controller 2000-08-30 11:33:52
M RTRV
"session=test:bwhite"
/* The cli :9998: exists.
*/
;
Troubleshooting the Main Memory Database Replication
If you have problems during replication, try stopping and restarting the replication as follows:
Step 1
Stop the replication by entering:
# /etc/init.d/ttreplic stop
Step 2
Restart the replication by entering:
# /etc/init.d/ttreplic start
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-61
Chapter 5
Configuring the Cisco MGC Software
Initializing the Call Screening Database
Displaying the Main Memory Database Replication Status
The script replication_status.sh displays the status of the MMDB replication, if it is configured.
Run the script by typing the following command:
replication_status.sh
The output shows the following replication status:
Peer name
---------------HOWDYDB
Last Msg Sent
-------------
Note
Host name
Port
------------------------ -----VA-DEALE
Auto
Last Msg Recv
-------------
Latency
-------1.00
TPS
-------1
State Proto
------- ----Start
5
RecordsPS
---------1
Logs
---1
If the value for Last Msg Recv is more than a few seconds, or Logs is more than 1, then this indicates
that replication is not occurring.
Verifying Database Synchronization
The script db_count.sh provides the number of records configured in each of the database tables. This
is useful for checking whether two machines have the same database data configured in them.
Run the script by typing the following command:
db_count.sh
The output shows the rows counted in each database table:
CISCO.A_CHARGE_ORIGIN
< 0 >
CISCO.A_NUMBERDIALPLANSELECTION < 0 >
CISCO.BLACKLIST_A
< 0 >
CISCO.BLACKLIST_B
< 0 >
CISCO.NUMBERTERM
< 0 >
CISCO.PORTEDNUMBERS
< 0 >
CISCO.WHITELIST_A
< 0 >
CISCO.WHITELIST_B
< 3 >
Synchronizing Databases
If you have data in the databases in the active and standby hosts, but both databases are out of synch or
do not match, re-synchronize both databases by following the steps listed below. Otherwise, contact
Cisco TAC for assistance in merging the databases.
Assuming the active host is the "better" database, do the following on the standby host:
Step 1
Log in as mgcusr.
Step 2
Stop the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC stop
Step 3
Stop MMDB replication by entering the following command:
/etc/init.d/ttreplic stop
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-62
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring Cisco SLTs
Step 4
Copy the active host database to the standby host database by entering the following command:
setup_replication <active host> standby
Step 5
Start the Cisco MGC by entering the following command:
/etc/init.d/CiscoMGC start
Checking for Installation Errors
If you still have problems, retry the commands listed in the “Verifying Database Replication” section on
page 5-61. If your output differs from the example in that section, or if you suspect problems or errors
in the database installation, try the following:
Step 1
Ensure that the database is installed in the /opt/TimesTen directory.
Step 2
Check the log file for installation errors. (The log file is in the directory /var/adm/MGC.install.log.)
Reinstalling CSCOga002
If necessary, remove and reinstall the CSCOga002 package, as follows:
Step 1
Remove the CSCOga002 package using the pkgrm command. To remove the package file, enter the
following command:
# pkgrm CSCOga002
Step 2
Reinstall the package using the pkgadd command by entering the following command:
# pkgadd -d CSCOga002.pkg
This completes the Cisco MGC software installation. If you have questions or need assistance, see the
“Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii. If you do
not need to install or remove patches, proceed to configure your Cisco SLTs.
Configuring Cisco SLTs
Note
For configuration information, refer to the document Cisco Signaling Link Terminal and the Release
Notes for the Cisco Media Gateway Controller Software Release 9.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-63
Chapter 5
Configuring the Cisco MGC Software
Configuring Disk Monitor During Initial Software Configuration
Configuring Disk Monitor During Initial Software Configuration
The setting of the disk monitor parameters in the XECfgParm.dat file typically occurs while you are
performing the initial configuration procedures for your Cisco MGC software. To configure the disk
monitor settings in the XECfgParm.dat file during initial software configuration, perform the following
steps:
Step 1
While configuring your settings in the XECfgParm.dat file, find the disk monitor parameters in the file
(they are near the end of the file).
Step 2
To change the number of days to preserve logged data before trimming is initiated, modify the value of
the diskmonitor.Limit parameter. The default value is 7.
Step 3
To change the list of optional file systems that are checked by the disk monitor script, modify the value
of the diskmonitor.OptFileSys parameter.
Note
Files in optional directories are not trimmed by disk monitor.
Step 4
To change the percentage of disk usage at which alarming and disk trimming is initiated, modify the
value of the diskmonitor.Threshold parameter. The default value is 80.
Step 5
To change the number of days that finished CDR files are kept in the log directory, modify the value of
the diskmonitor.CdrRmFinished parameter. The default value is 0, which means that finished CDRs are
immediately sent to the spool directory.
Step 6
If you want to change what action is taken once the number of days threshold set in the
diskmonitor.Limit parameter is reached, change the value of the diskmonitor.SoftLimit parameter. If this
parameter is set to true, disk monitor decrements the value in the diskmonitor.Limit parameter one day
at a time (that is, from 7 down to 6 then down to 5 and so on), until the utilization level drops below the
threshold. If this parameter is set to false, disk monitor exits and the system generates a DISK alarm.
The default value is true.
Step 7
To change the number of days that core dump files are kept in the log directory, modify the value of the
diskmonitor.CoreRmDays parameter. The default value is 1, which means that core dump files are kept
for one day before disk monitor removes them automatically.
Step 8
You can control the maximum number of configurations that can be stored in the configuration library
using the diskmonitor.CfgRmDirs parameter. The valid values are the range of integers from 3 through
64. The default value is 64. This parameter is not present in the XECfgParm.dat file initially. If you want
to modify the value, you must enter the parameter manually into the file.
Step 9
Note
If you want to ensure the proper functioning of the prov-sync MML command, set this
parameter to a value between 50 and 60.
Note
Entering a value outside of the range of valid values (3 through 64) disables monitoring of the
number of entries stored in the configuration library.
Save your changes.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-64
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Data Dumper
This completes the procedures for configuring disk space monitoring. If you have questions or need
assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on
page xvii.
Configuring the Data Dumper
The data dumper is a Cisco MGC software function that controls the destinations for active and archived
log files for CDRs, measurements, and alarms, and controls when the active files are archived. The data
dumper runs automatically and works correctly with a default configuration. However, you can
customize the dumper settings by editing the dmprSink.dat file.
The following is an example of the contents of the dmprSink.dat file:
“callDetail” bin “cdr” “../var/log” “../var/spool” 1000 0 15
“measReport” csv “meas” “../var/log” “../var/spool” 500 0 15
“almState” csv “alm” “../var/log” “../var/spool” 500 0 15
Table 5-6 lists the fields that can be modified depending on your needs.
Table 5-6
Dumper Sink Log File Parameters
Field Name
Default Value
Description
maxRecs
1000
The maximum number of records a file can contain before it is flushed
or moved to the spool area. If this value is set to 0, the number of
records is unlimited. You can improve system performance by
increasing the value of this record to a larger value, such as 50000.
This results in fewer log record files being generated during periods
of high call volume.
maxSize
0
The maximum size of the file in bytes before it is moved to the spool
area. If this value is set to 0, the size of the file is limited only by the
disk space available.
maxTime
15
The maximum time, in minutes, the file is allowed to remain open,
before it is flushed or moved to the spool area. If there is no data in
the file, it will not be flushed when the time limit expires. If this value
is set to 0, there is no time limit.
Note
Caution
One or more of the above fields must be set to a value other
than zero (0) for each record in the dmprSink.dat file.
Do not modify or change any of the following log file configuration values.
recordFormat csv
The translation of the records being placed in the capture file. Valid
values are csv (comma-separated values) or bin (binary).
logDirectory
/var/log
The directory where the current dumper logs reside.
logSpoolDir
/var/spool
The directory to which historic logs are copied after being closed.
To configure the dmprSink.dat file fields, use the following procedure:
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-65
Chapter 5
Configuring the Cisco MGC Software
Configuring the Data Dumper to Support BAMS
Step 1
If you are not already logged in, log into a Cisco MGC as root.
Step 2
Change to the /opt/CiscoMGC/etc directory by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 3
Use a text editor, such as vi, to open and edit the dmprSink.dat file fields you want to change.
Note
If you are going to use the BAMS to collect CDRs, proceed to the “Configuring the Data Dumper
to Support BAMS” section on page 5-66, for information on how to configure the data dumper
to support BAMS.
Step 4
Save your changes and exit the text editor.
Step 5
Change to the /opt/CiscoMGC/etc/CONFIG_LIB/new directory by entering the following UNIX
command:
cd /opt/CiscoMGC/etc/CONFIG_LIB/new
Step 6
Stop and start the standby host.
Step 7
Perform sw-over on the active host.
Step 8
Stop and start the newly-standby host (formerly active host).
Step 9
Repeat Step 3 and Step 4 for the version of dmprSink.dat stored in this directory.
Step 10
Change to the /opt/CiscoMGC/etc/active_link directory by entering the following UNIX command:
cd /opt/CiscoMGC/etc/active_link/
Step 11
Repeat Step 3 and Step 4 for the version of dmprSink.dat stored in this directory.
Step 12
If your system is equipped with a second Cisco MGC, repeat Step 1 through Step 10 on this second Cisco
MGC.
This completes the procedures for configuring the data dumper. If your system uses BAMS, continue to
the “Configuring the Data Dumper to Support BAMS” section on page 5-66. If you have questions or
need assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii.
Configuring the Data Dumper to Support BAMS
If your system will use BAMS to retrieve CDRs from the Cisco MGC, perform the following procedure
to configure the data dumper to support BAMS:
Step 1
If you are not already logged in, log into a Cisco MGC as root.
Step 2
Change to the /opt/CiscoMGC/etc directory by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 3
Use a text editor, such as vi, to open and edit the dmprSink.dat file fields you want to change.
Step 4
Save your changes and exit the text editor.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-66
OL-1150-15
Chapter 5
Configuring the Cisco MGC Software
Configuring the Data Dumper to Support BAMS
Step 5
Change to the /opt/CiscoMGC/etc/CONFIG_LIB/new directory by entering the following UNIX
command:
cd /opt/CiscoMGC/etc/CONFIG_LIB/new
Step 6
Stop and start the standby host.
Step 7
Perform sw-over on the active host.
Step 8
Stop and start the newly-standby host (formerly active host).
Step 9
Repeat Step 3 and Step 4 for the version of dmprSink.dat stored in this directory.
Step 10
Change to the /opt/CiscoMGC/etc/active_link directory by entering the following UNIX command:
cd /opt/CiscoMGC/etc/active_link/
Step 11
Repeat Step 3 and Step 4 for the version of dmprSink.dat stored in this directory.
Step 12
If your system is equipped with a second Cisco MGC, repeat Step 1 through Step 10 on this second Cisco
MGC.
This completes the procedures for configuring the data dumper to support BAMS. If you have questions
or need assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii.
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
OL-1150-15
5-67
Chapter 5
Configuring the Cisco MGC Software
Configuring the Data Dumper to Support BAMS
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
5-68
OL-1150-15
CH A P T E R
6
Upgrading the Cisco MGC Software
This chapter describes procedures for upgrading from a major Cisco MGC software release such as
7.4(x) or 9.x(x) to the latest Cisco MGC software release without service interruption.
The following sections in this chapter describe the procedures for upgrading to the latest Cisco MGC
software release:
•
Requirements for Upgrading, page 6-1
•
Quick Guide to Upgrading Your Cisco MGC Software, page 6-2
•
Before You Begin, page 6-3
•
Upgrading the Cisco MGC Software Release, page 6-8
•
Downgrading the Cisco MGC Software Release, page 6-15
•
If Migration Fails, page 6-17
Requirements for Upgrading
Your hardware and software environment must meet the following requirements before you can upgrade
to the latest Cisco MGC software release:
Table 6-1
Requirements for Upgrading
Requirement
Description
Disk requirements
Minimum of 2 disks
Disk size
Minimum of 18 GB
Operating system
Solaris 8 operating system
Note
Patch levels
If you are running Cisco MGC software release 7.4(x) or
9.1(5), you must first upgrade your operating system to
Solaris 8 and the latest patches.
Install the latest patch versions on both the Active and Standby
hosts. Refer to Cisco.com to determine the latest patch versions
available.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-1
Chapter 6
Upgrading the Cisco MGC Software
Quick Guide to Upgrading Your Cisco MGC Software
Table 6-1
Requirements for Upgrading
Requirement
Description
pom.dataSync parameter
setting
Located in the XECfgParm.dat file. Set the pom.dataSync parameter
to false when upgrading from a patch level that does not support
Seamless Upgrade to a patch level that supports it. Otherwise, the
standby system will not transition to the standby state and will remain
out-of-service (OOS).
Installer requirements
Note
•
Experienced Solaris system administrator.
•
Familiarity with system administration tasks such as mounting
file systems and running tar to save and restore files.
Before starting the upgrade, obtain a remote server IP address from your system administrator.
A remote file server is required when backing up configuration data (see Step 4 in the “Backing
Up the Configuration Data” section on page 6-10.
Quick Guide to Upgrading Your Cisco MGC Software
Caution
Always start migration from the standby box (Host B).
The following table provides a guide to upgrading to the latest Cisco MGC software release. For details,
refer to the page numbers located on the right-hand column of the table.
Procedure
Details on Page...
Before You Begin
6-3
– Back Up Your Software
6-4
– Check for Mated STP Pairs
6-5
– Add an SS7 Route for Each Mated STP (from Release 7.4(x) only)
6-6
– Check for ^M Characters in XECfgParm.dat
6-7
Upgrading the Cisco MGC Software Release
6-8
– Backing Up the Main Memory Database
6-9
– Backing Up the Configuration Data
6-10
– Restoring Data Files
6-11
Downgrading the Cisco MGC Software Release
6-15
– Scenario 1: Standby Host is Running Cisco MGC 7.4(x) or 9.x
6-15
– Scenario 2: Active and Standby Hosts are Running Cisco MGC 9.x or
6-16
Later Software Release
If Migration Fails
6-17
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-2
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Before You Begin
Before You Begin
You can do limited provisioning while upgrading from Cisco MGC software releases 9.x. Limited
provisioning means you can provision the following during the upgrade or downgrade period:
– Screening configuration
– Ported numbers
– Number termination
– Advice of Charge (AOC)
– A number dial plan selection
Caution
Do not make any provisioning changes while upgrading from Cisco MGC software releases 7.4(x) or 9.x
to the latest software release.
Note
Contact Cisco TAC if you need assistance (see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii).
If You are Upgrading from Cisco MGC 7.4(x)
Step 1
If you are not using any screening data (AWHITE, ABLACK, BWHITE, BBLACK), proceed to Step 2
prior to uninstalling Cisco MGC 7.4(x).
If you are using screening, perform the procedure in Step 3 following after restoring the configuration
data, as described in Chapter 2, “Sun Solaris 8 Operating System Installation,” and prior to installing
Cisco MGC release 9.x.
Step 2
Remove the .ttdb files from the /opt/CiscoMGC/etc directory. Enter the following command to cause a
complete installation of the TimesTen database instead of an upgrade.
rm /opt/CiscoMGC/etc/*.ttdb
The procedure is complete.
Step 3
Enter the following commands prior to uninstalling 7.4(x) for each customer group ID that you have data
for—this will create export files of your data that can later be re-imported:
prov-add:files:name="awhitefile",
prov-add:files:name="bwhitefile",
prov-add:files:name="ablackfile",
prov-add:files:name="bblackfile",
file="XXXX.awhite",
file="XXXX.bwhite",
file="XXXX.ablack",
file="XXXX.bblack",
action="export
action="export
action="export
action="export
Where XXXX is a customer group ID (dialplan name).
Step 4
After the installation of the Cisco PGW is complete you can provision the data again (if necessary) by
doing the following for each of the export files created prior to the uninstallation of Cisco MGC release
7.4:
prov-add:files:name="awhitefile",
prov-add:files:name="bwhitefile",
prov-add:files:name="ablackfile",
prov-add:files:name="bblackfile",
file="XXXX.awhite",
file="XXXX.bwhite",
file="XXXX.ablack",
file="XXXX.bblack",
action="import
action="import
action="import
action="import
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-3
Chapter 6
Upgrading the Cisco MGC Software
Before You Begin
The procedure is complete.
If You are Upgrading from a Cisco MGC 9.x Release to Another 9.x Release
You must run the current Cisco MGC 9.x uninstall script before upgrading to or downgrading from
another Cisco MGC 9.x version.
Note
You must run the uninstall script of the current Cisco MGC 9.x version to avoid upgrade problems.
Back Up Your Software
Step 1
Verify that there are no existing major alarms. Log in to both Host A (active box) and Host B (standby
box) and enter the following MML command:
rtrv-alms
If major alarms are found, resolve the problems first before proceeding with the upgrade.
Step 2
Step 3
Before migrating from Cisco MGC software release 9.x prior to 9.4(1), you must first back up the
/opt/SW directory.
a.
To ensure that you do not lose the contents of the /opt/SW directory, create a sub-directory under
/opt/SW/9.x directory name and save the contents there. This will provide you a copy of the
originally-installed 9.x patches, in case you need to fall back to it.
b.
Remove the .pkg files from the /opt/SW directory before proceeding with the upgrade.
Save the configuration data in both Host A and Host B. To create an mgc-backup folder under /tmp,
log in as mgcusr and enter the following commands:
mkdir /tmp/mgc-relnum-backup
mgcbackup -d /tmp/mgc-relnum-backup
Where relnum is the current software release number.
For example, to save the configuration data for a system running Release 9.4(1), you would enter the
following commands:
mkdir /tmp/mgc-941-backup
mgcbackup -d /tmp/mgc-941-backup
Step 4
Copy the XECfgParm.dat file. Enter the following command:
cp /opt/CiscoMGC/etc/XECfgParm.dat
/tmp/mgc-relnum-backup/XECfgParm.dat.relnum
Where relnum is the current software release number.
For example, to copy the XECfgParm.dat file for a system running Release 9.4(1), you would enter the
following command:
cp /opt/CiscoMGC/etc/XECfgParm.dat
Step 5
/tmp/mgc-941-backup/XECfgParm.dat.941
Copy the files in the mgc-relnum-backup folder to a remote file server using the FTP file transfer utility.
Type the following command to FTP the files to a remote server and press Enter:
ftp remote_server_IP_address
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-4
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Before You Begin
Note
The remote server IP address is provided by your system administrator.
Make sure that you are in binary mode before you FTP your files.
Step 6
If you are using MMDB, do the following steps:
a.
Verify that both the Active and Standby hosts have the latest Cisco MGC 9.x system patch.
b.
Log in as mgcusr and type the following command in both the Active and Standby Hosts, then press
Enter:
./mod_replication_port.sh
c.
If you are upgrading to Release 9.6(x) from Release 9.3(x), 9.4(x), or 9.5(x), type the following
command in both the Active and Standby Hosts, then press Enter:
./delete_replication.sh
Check for Mated STP Pairs
Before upgrading the standby host (Host B) to Cisco MGC 9.3(2), check if Mated Signal Transfer Point
(STP) pairs are currently configured on the system.
On the active host (Host A), type the following MML command and press Enter to retrieve the
provisioning information for all the SS7SUBSYS:
prov-rtrv:ss7subsys:”all”
Following is an example of the text that is displayed. Look for STP entries in the MATEDAPC column
in the text display.
va-seattle mml> prov-rtrv:ss7subsys:"all"
MGC-01 - Media Gateway Controller 2003-06-16 23:15:18.093 EST
M RTRV
"session=932-Japan-9:ss7subsys"
/*
NAME
SVC
PRI
MATEDAPC
SSN
PROTO
STPSCPIND
-------------—--------------mate1
stp1
1
stp2
0
SS7-ITU
0
mate2
stp2
1
stp1
0
SS7-ITU
0
*/
;
RANSPROTO
--------SCCP
SCCP
a.
If Mated STP pairs are configured on the SS7SUBSYS, they are displayed in the MatedAPC
column: You must create routes for the mated pairs before proceeding with the upgrade. Follow the
procedures in the “Add an SS7 Route for Each Mated STP (from Release 7.4(x) only)” section on
page 6-6.
b.
If Mated STP pairs are not configured on the SS7SUBSYS, the MatedAPC column is blank:
Continue to the “Check for ^M Characters in XECfgParm.dat” section on page 6-7, below.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-5
Chapter 6
Upgrading the Cisco MGC Software
Before You Begin
Add an SS7 Route for Each Mated STP (from Release 7.4(x) only)
To ensure a seamless upgrade from Cisco MGC 7.4(x), one SS7 route is required for each STP if the STP
is mated.
On the active host (Host A), do the following procedures to add a route for each mated STP:
Step 1
Find the OPC, DPC and linkset names that are associated with STPs. Type the following MML command
and press Enter:
prov-rtrv:ss7route:"all"
Text similar to the following is displayed:
MGC-01 - Media Gateway Controller 2003-06-16 23:22:42.542 EST
RTRV
"session=932-Japan-9:ss7route"
/*
NAME
OPC
DPC
LNKSET
PRI
--------------route1
opc-sc2200
dpc1
ls1
1
route2
opc-sc2200
dpc2
ls2
1
route3
opc-sc2200
dpc2
ls1
1
route4
opc-sc2200
dpc1
ls2
1
route-stp1
opc-sc2200
stp1
ls1
1
route-stp2
opc-sc2200
stp2
ls2
1
*/
;
M
Step 2
Start a provisioning session. Type the following command and press Enter:
prov-sta::srcver=”active” dstver=”newconfig”
Step 3
Create priority 2 SS7Routes to the "SVC"s (SERVICE) through the corresponding MATEDAPCs, as
shown in the following example.
In this example, the following provisioning command is entered to create an SS7 route to SVC (stp1)
via MATEDAPC (mateStp):
prov-add:ss7route:name="rte-to-stp1",desc="Route to stp1 via mated STP",opc="opc1",
dpc="stp1",lnkset="ls-to-mateStp",pri=2
Where:
ls-to-mateStp = the MML name of the previously provisioned linkset to "mateStp"
opc1 = the MML name of the OPC associated with linkset to "mateStp"
Example:
The following example is based on the output above. One route for each STP is needed.
prov-add:ss7route:name="route-stp1",desc="Route to stp1 via mated STP",opc="opc-pgw2200 ",
dpc="stp1",lnkset="ls2",pri=2
prov-add:ss7route:name="route-stp2",desc="Route to stp2 via mated STP",opc="opc-pgw2200 ",
dpc="stp2",lnkset="ls1",pri=2
Step 4
Deploy the configuration changes done in Step 3 (above), to the STANDBY platform by typing the
following command:
prov-dply
Step 5
Type the following command to execute a MML command on ACTIVE platform:
sw-over::confirm
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-6
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Before You Begin
Step 6
Wait about 10 minutes then make sure the platforms have switched to ACTIVE/STANDBY.
Step 7
Perform a manual switchover using the sw-over::confirm MML command on the ACTIVE platform.
Step 8
Follow normal upgrade process to upgrade the STANDBY platform to the latest software release.
Step 9
To complete the upgrade process, go to Step 2 on page 6-8.
Check for ^M Characters in XECfgParm.dat
Before you perform backup procedures on your configuration data, make sure to remove ^M characters
(Ctrl-m or carriage return) at the end of each line in the file. The ^M characters may be present if the
XECfgParm.dat file was modified by a Microsoft Windows (DOS)-based editor like Notepad.
If you do not remove the ^M characters, you might get an error similar to the following when you install
the new software version:
ttRestore: SQL Error: Failed to connect to data store
There are two ways to remove ^M characters and avoid this error. Before backing up your configuration
data, perform one of the following procedures:
•
Run the dos2unix utility. For instructions, see Running the dos2unix Utility, page 6-7.
•
Edit the XECfgParm.dat file with the vi editor. For instructions, see Editing the XECfgParm.dat
File, page 6-7.
Running the dos2unix Utility
To run the dos2unix utility to remove ^M characters, perform the following steps before backing up your
configuration data:
Step 1
Set your directory to the location of the XECfgParm.dat file by entering the following command:
cd /opt/CiscoMGC/etc
Step 2
Move the XECfgParm.dat file by entering the following command:
mv XECfgParm.dat XECfgParm.dat.old
Step 3
Run the dos2unix utility by entering the following command:
dos2unix XECfgParm.dat.old XECfgParm.dat
Step 4
Using the vi editor, verify that all the ^M characters have been removed from the XECfgParm.dat file.
Editing the XECfgParm.dat File
Check for the presence of a ^M character before starting the upgrade. If found, perform the following
steps before backing up your configuration data.
Step 1
Set your directory to the location of the XECfgParm.dat file by typing the following command:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-7
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
cd /opt/CiscoMGC/etc
Step 2
Edit the XECfgParm.dat file with the vi editor by typing the following command:
vi XECfgParm.dat
Step 3
Execute the following command in the vi editor to remove the ^M character from the end of each line.
1,$s/^v^m$//
Where:
^v is Ctrl-v
^m is Ctrl-m
There is no space between //.
Step 4
Save the changes and exit vi.
Continue to the following section, “Upgrading the Cisco MGC Software Release”.
Upgrading the Cisco MGC Software Release
Note
Both the active host (Host A) and standby host (Host B) must be running either Cisco MGC software
release 7.4(x) or 9.x.
Note
If you are upgrading from Cisco MGC release 7.4(x) and using screening data (such as AWHITE,
ABLACK, BWHITE, BBLACK), you must first see the “If You are Upgrading from Cisco MGC 7.4(x)”
section on page 6-3.
To upgrade to a later Cisco MGC software release:
Step 1
On both Host A and Host B, make sure that pom.dataSync is set to False. Use an editor such as vi to
edit the /opt/CiscoMGC/etc/XECfgParm.dat file and set this value.
Step 2
On Host B, log in as root. Enter the following command to stop the Cisco MGC and shut down Host B:
/etc/init.d/CiscoMGC stop
Step 3
On Host B, install the latest available system and protocol patches for the system you are running. Refer
to the Release Notes for the Cisco Media Gateway Controller Software Release x (release version of the
software you are running) for the patch location and installation procedure.
Step 4
Start Host B. Type the following command and press Enter:
/etc/init.d/CiscoMGC start
Step 5
Make sure that the replication of call states is occurring between Host A and Host B are now running the
latest patches.
To verify whether replication of call states is occurring between Host A and Host B, enter the following
MML command:
rtrv-cic:<ss7sigpath>:cic=<cicno>
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-8
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Step 6
Perform a manual switchover on Host A. Let Host B (the standby host running Cisco MGC 7.4(x) or 9.x
and the latest patch) take over and become active. Enter the following command:
sw-over::confirm
Step 7
Check to make sure that Host B is processing calls.
Step 8
Wait until Host A becomes standby. Shut down Host A.
Step 9
On Host A, log in as root. Enter the following command to stop the Cisco MGC:
/etc/init.d/CiscoMGC stop
Step 10
On Host A, install the latest available system and protocol patches for the system you are running.
Refer to the Release Notes for the Cisco Media Gateway Controller Software Release 7 for the patch
location and installation procedure.
Step 11
Start Host A. Type the following command and press Enter:
/etc/init.d/CiscoMGC start
Step 12
Back up the Main Memory Database (MMDB) on Host A, as shown in the following procedure,
“Backing Up the Main Memory Database”.
Continue to the following section, “Backing Up the Main Memory Database”.
Backing Up the Main Memory Database
To back up the Main Memory Database (MMDB):
Step 1
Log in as mgcusr. As root, set user to mgcusr by typing the following command and pressing Enter:
su -l mgcusr
Step 2
Back up the database, using the following command:
/opt/CiscoMGC/local/backupDb.sh /opt/CiscoMGC/etc/export.ttdb
Step 3
Enter one of the following commands to create the file migrate.ttdb.
a.
If your host is running Cisco MGC 7.4(x):
/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb
b.
If your host is running Cisco MGC 9.x:
/opt/TimesTen4.1/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb
Note
If you are upgrading to Release 9.6(1), enter the command as follows:
/opt/TimesTen5.0/32/bin/ttVersion presenter
Step 4
Create a version file of the MMDB (export.ttdb). Enter the following commands for systems running
Cisco MGC software release 7.4(x) or 9.x(x):
rm -f /opt/CiscoMGC/etc/version.ttdb
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-9
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Step 5
Determine the database version of the version.ttdb file.
a.
For Cisco MGC 7.4(x), enter the following command:
/opt/TimesTen32/32/bin/ttVersion presenter
Text similar to the following example is displayed:
[ output = “TimesTen Release x.y.z build time ... ]
b.
For Cisco MGC 9.x, enter the following command:
/opt/TimesTen4.1/32/bin/ttVersion presenter
Note
If you are upgrading to Release 9.6(1), enter the command as follows:
/opt/TimesTen5.0/32/bin/ttVersion presenter
Text similar to the following example is displayed:
[ output = “TimesTen Release x.y.z build time ... ]
Step 6
Replace the “TimesTen Release x.y.z” with the version output. Type the following command and press
Enter:
echo xyz >/opt/CiscoMGC/etc/version.ttdb
Step 7
Verify that the backup is successful. Type the following commands and press Enter to make sure that
the version.ttdb, migrate.ttdb, and export.ttdb files are present:
cd /opt/CiscoMGC/etc
ls *.ttdb
Continue to the following section, “Backing Up the Configuration Data”.
Backing Up the Configuration Data
To back up the configuration data:
Step 1
Log in as root.
Step 2
If you are upgrading from Release 7.4(x), save the snmpd.cnf file located in /opt/CiscoMGC/snmp in
another directory. Enter the following command:
cp /opt/CiscoMGC/snmp/snmpd.cnf
Step 3
/opt/CiscoMGC/dialPlan
Enter the following commands to back up the etc and dialPlan folders:
cd /opt/CiscoMGC
mkdir upgrade-backup
tar cvf /opt/CiscoMGC/upgrade-backup/MGC.tar ./etc ./dialPlan
Note
The mkdir upgrade-backup command is used to create a new folder in /opt/CiscoMGC.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-10
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Step 4
Type the following command to FTP the files to a remote server and press Enter:
ftp <remote server IP address>
Note
The remote server IP address is provided by your system administrator.
Text similar to the following is displayed:
Name (ip address: root):
Step 5
Press Enter to continue.
Text similar to the following is displayed:
Password:
Step 6
Type the following and press Enter:
bin
Step 7
Type the following command and press Enter:
lcd /opt/CiscoMGC/upgrade-backup
Step 8
Type the following command and press Enter:
put MGC.tar
Step 9
Shut down the standby Host A by entering the following MML command:
/etc/init.d/CiscoMGC stop
Step 10
Install the Solaris 8 operating system on Host A if you are upgrading from Release 7.4(x). If not,
skip this step. For the Solaris 8 operating system and Solaris patches installation procedures, refer to
Chapter 2, “Sun Solaris 8 Operating System Installation”.
Continue to the following section, “Restoring Data Files”.
Restoring Data Files
Do the following to restore data files:
Step 1
Log in as root.
Step 2
Enter the following command to move the configuration files to the tmp folder:
cd /tmp
mkdir saved
cd /tmp/saved
Step 3
Enter the following commands to restore the data files:
a.
From the local tape drive:
tar xvf /dev/rmt/0
b.
From a remote file server:
Using FTP, copy the file MGC.tar from a remote file server to the /tmp/saved folder.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-11
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Note
Step 4
You must use the binary mode of FTP and verify that the files are successfully transferred
to the /tmp/saved folder before continuing to restore data files.
You may need to create the CiscoMGC directory. To do this, enter the following commands:
cd /opt
mkdir CiscoMGC
cd /opt/CiscoMGC
cp /tmp/saved/MGC.tar MGC.tar
tar xvf MGC.tar
Step 5
Type the following command and press Enter to verify that both the etc and dialPlan folders are
present:
ls
Step 6
Log in as root.
Step 7
Download the latest installation script (patch) to the /opt/SW directory. Install the Cisco MGC software
release and the latest patches on Host A.
For Cisco MGC software installation procedures, refer to the Chapter 3, “Cisco MGC Software
Release 9 Installation.” For patch installation procedures, refer to the Release Notes for the Cisco Media
Gateway Controller Software Release 9.x.
Caution
Do not add to your provisioning data until both of your PGW hosts have been upgraded to the current
Cisco MGC software release.
Step 8
If you are upgrading from Release 7.4(x), enter the following command to move the saved snmp.cnf file
back to the correct directory:
mv /opt/CiscoMGC/dialPlan/snmpd.cnf /opt/CiscoMGC/snmp/snmpd.cnf
Note
When you install the latest release of the Cisco MGC software, the existing snmpd.cnf file is renamed
and a new empty snmpd.cnf file is created. The command above assumes that you backed up the old
snmpd.cnf file as described in Step 2 of the “Backing Up the Configuration Data” section on page 6-10.
If you did not back up the old snmpd.cnf file, you can delete the new empty file and rename the
snmpd.cnf.custorig file to snmpd.cnf to restore your old SNMP configuration.
Caution
When you upgrade your Cisco MGC software with patches or the newest release, there may be changes
to the SNMP configuration file. After an upgrade, ensure that the snmpd.cnf file is still properly
configured for your system. If you find that it is not, contact the Cisco TAC. You can find information
on contacting the Cisco TAC in the “Obtaining Documentation, Obtaining Support, and Security
Guidelines” section on page xvii.
Step 9
Verify that the Cisco MGC software release installation on Host A is successful by using an editor (such
as vi) to check that there are no errors in the /var/adm/MGC_install.log file.
a.
If the upgrade is successful: Continue to b.Step 10.
b.
If the upgrade is not successful: Continue to the “If Migration Fails” section on page 6-17 then
return to Step 10 on page 6-13 to continue the upgrade process from Cisco MGC 7.4(x) to 9.x.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-12
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Caution
If you are upgrading from Release 7.4(x) to Release 9.5(2), and you are going to use the config-lib tool
to copy your Release 7.4(x) configuration to your Release 9.5(2) production, you must manually convert
your XECfgParm.dat file to support Release 9.5(2) by performing the steps below once you have
finished using config-lib and before you restart the Cisco MGC software.
1.Copy your Release 9.5(2) XECfgParm.dat file to a new filename. For example:
cp /opt/CiscoMGC/etc/XECfgParm.dat /opt/CiscoMGC/etc/9.5_XECfgParm.dat
2.Copy your Release 7.4(x) XECfgParm.dat file from the Configuration Library to the production
directory. For example:
cp /opt/CiscoMGC/etc/CONFIG_LIB/new/XECfgParm.dat /opt/CiscoMGC/etc/XECfgParm.dat
3.Compare the content of the original Release 9.5(2) XECfgParm.dat file to your new production
XECfgParm.dat file. Make note of parameters that are supported in Release 9.5(2) that are not in
your production file.
4.Edit your production XECfgParm.dat file (using a tool such as vi), adding the parameters to the file
that are supported in Release 9.5(2).
Step 10
Start the Cisco MGC software on Host A. Type the following command and press Enter:
/etc/init.d/CiscoMGC start
Step 11
Verify that the configuration is migrated to the desired Cisco MGC 9.x software release on Host A and
ensure that all states are operational by entering the following MML commands:
rtrv-ne
rtrv-tc:all
rtrv-dest:all
rtrv-c7lnk:all
rtrv-iplnk:all
Step 12
Make sure that replication of call states is occurring between Host B (the active host running Cisco MGC
7.4(x) or 9.1(5) and the latest patch) and Host A (the standby host running the Cisco MGC 9.3(2) or later
software release). Enter the following command on the standby host (Host A):
rtrv-tc:all
Step 13
Perform a manual switchover on Host B (the active host). Type the following command and press Enter:
sw-over::confirm
Step 14
Let Host A take over and become active.
Step 15
Verify that Host A (running Cisco MGC 9.3(2) or later software release) is processing calls. Type the
following command and press Enter:
rtrv-tc:all
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-13
Chapter 6
Upgrading the Cisco MGC Software
Upgrading the Cisco MGC Software Release
Note
If the call replication fails, or if Host A is not processing calls, refer to the “Cisco Media
Gateway Controller Operations, Maintenance, and Troubleshooting Guide” for procedures on
how to resolve the problem. Call Cisco TAC if you require further assistance.
To downgrade to a previous software release, see the section “Downgrading the Cisco MGC
Software Release” section on page 6-15.
Step 16
Back up the MMDB. Refer to the “Backing Up the Main Memory Database” section on page 6-9 for
backup procedures.
Step 17
Back up the configuration data. For backup procedures, refer to the “Backing Up the Configuration
Data” section on page 6-10 and follow Step 1 through Step 8.
Step 18
Shut down Host B (the standby host running Cisco MGC 7.4(x) or 9.1(5) and the latest patch) by entering
the following MML command:
/etc/init.d/CiscoMGC stop
Step 19
Install the Solaris 8 operating system and the necessary patches on Host B if you are upgrading from
Cisco MGC 7.4(x). Install the necessary patches if you are upgrading from Cisco MGC 9.x. For
installation procedures, refer to Chapter 2, “Sun Solaris 8 Operating System Installation.”
Step 20
Restore the data files. Refer to the “Restoring Data Files” section on page 6-11 and follow Step 1
through Step 5 to restore the data files.
Step 21
Install Cisco MGC 9.x software and the latest patch on Host B. For installation procedures, refer to the
“Installing the Cisco MGC Software 9.2(x) and Higher Releases” section on page 3-3.
Step 22
Set the value of pom.dataSync=true. Use an editor such as vi to edit the file
/opt/CiscoMGC/etc/XECfgParm.dat to set this value.
Step 23
Bring up Host B as standby.
Note
Step 24
Before starting the Cisco MGC software: If your configuration includes BAMS and you are
upgrading to Cisco MGC 9.4(x), you must first re-apply the changes noted in Steps 4 and 5 in
the section “Configuring the Cisco MGC for Using BAMS” of the BAMS User’s Guide.
Start the MGC software on Host B (which now has the Cisco 9.x software). Enter the following
command:
/etc/init.d/CiscoMGC start
Step 25
Wait for Host B to come up fully as standby host.
Step 26
If you are upgrading to Release 9.6(x) from Release 9.3(x), 9.4(x), or 9.5(x) and your Cisco PGW 2200
uses the MMDB, you must restart database replication between the active and standby hosts. Type the
following command and press Enter:
./setup_replication.sh
The upgrade from the Cisco MGC 7.4(x) and 9.x is now complete.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-14
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
Downgrading the Cisco MGC Software Release
Downgrading the Cisco MGC Software Release
Two scenarios for downgrading to Release 7.4(x) or 9.x software release are detailed in this section:
Note
•
Scenario 1: Standby Host is Running Cisco MGC 7.4(x) or 9.x
•
Scenario 2: Active and Standby Hosts are Running Cisco MGC 9.x or Later Software Release
Features in later software releases may not be supported if you are downgrading to an older release.
Scenario 1: Standby Host is Running Cisco MGC 7.4(x) or 9.x
When these two conditions apply, do the following procedures to downgrade from Cisco MGC 9.x:
•
Host A (active Host) is running the latest version of Cisco MGC 9.x
•
Host B (standby host) is running Cisco MGC 7.4(x) or 9.x and the latest patch
Step 1
Set the value of pom.dataSync=false. Use an editor such as vi to edit the
/opt/CiscoMGC/etc/XECfgParm.dat file to set this value.
Step 2
Trigger switchover on Host A, the active Host, running Cisco MGC 9.x. Host B becomes active.
Step 3
Shut down Host A. Type the following command and press Enter:
/opt/init.d/CiscoMGC stop
Step 4
On Host A, install the following:
a.
Solaris 2.6 operating system and the necessary patches, if you are downgrading to Releases 7.4(x)
or 9.1(5). Otherwise, proceed to Step 4b. For installation procedures, see Chapter 8, “Sun Solaris
2.6 Operating System Installation.”
b.
Software release originally installed on your system prior to the upgrade (either Cisco MGC 7.4(x)
or 9.x.
For Cisco MGC installation procedures, see the following:
– For Cisco MGC 9.1(5), see Chapter 7, “Cisco MGC Software Release 9.1(5) Installation.”
– For later Cisco MGC releases, see Chapter 3, “Cisco MGC Software Release 9 Installation.”
– For Cisco MGC 7.(x), see the “Cisco Media Gateway Controller Software Release 7 Installation
and Configuration Guide.”
c.
Latest patches (the same patch installed on Host B).
Step 5
Set the value of pom.dataSync=true. Use an editor such as vi to edit the file
/opt/CiscoMGC/etc/XECfgParm.dat to set this value.
Step 6
On Host A, start the Cisco MGC software with the latest patches as standby host.
Step 7
Make sure the configuration is backed up.
Step 8
Make sure that replication of call states is occurring between Host B (the active host running Cisco MGC
7.4(x) or 9.x and the latest patch) and Host A (the standby host running Cisco MGC 7.4(x) or 9.x and
the latest patches).
Type the following command and press Enter:
rtrv-tc:all
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-15
Chapter 6
Upgrading the Cisco MGC Software
Downgrading the Cisco MGC Software Release
This completes the downgrade procedure for Scenario 1: Standby Host is Running Cisco MGC 7.4(x) or
9.x. For assistance, call Cisco TAC.
Scenario 2: Active and Standby Hosts are Running Cisco MGC 9.x or Later
Software Release
Caution
All provisioning that is done after the upgrade will be lost because the system is using backup data.
To downgrade to Cisco MGC 7.4(x) or 9.1(5) when both the active and standby hosts are running Cisco
MGC 9.3(2) or later software release:
Step 1
Shut down Host B (standby host).
Step 2
To restore data files, refer to the “Upgrading the Cisco MGC Software Release” section on page 6-8.
Step 3
If you are downgrading to Release 7.4(x) or 9.1(5), you must reinstall the Solaris 2.6 operating system
and all of the patches that apply to it. Otherwise, proceed to Step 4. For installation procedures, refer to
Chapter 8, “Sun Solaris 2.6 Operating System Installation.”
Step 4
Create a CiscoMGC folder. Enter the following commands to create the CiscoMGC folder and extract
data files:
cd /opt
mkdir CiscoMGC
cd /opt/CiscoMGC
cp /tmp/saved/MGC.tar MGC.tar
tar xvf MGC.tar
Step 5
On Host B, install Cisco MGC 7.4(x) or 9.x and the latest patch.
Step 6
On Host B, start the software release that was originally installed on your system prior to the upgrade
(either Cisco MGC 7.4(x) or 9.x software) and the latest patch.
Step 7
Set the value of pom.dataSync=false. Use an editor such as vi to edit the file
/opt/CiscoMGC/etc/XECfgParm.dat to set this value.
Step 8
Bring up Host B as standby.
Step 9
Make sure that the configuration is backed up.
Step 10
Make sure that replication of call states are occurring between Host A (the active host running the latest
version of the Cisco MGC software) and Host B (the standby host running Cisco MGC 7.4(x) or 9.x and
the latest patch).
On the standby Host B, type the following command and press Enter:
rtrv-tc:all
Step 11
Trigger switchover on Host A. Enter the following command:
sw-over::confirm
Host B should become active.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-16
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
If Migration Fails
Step 12
Shut down Host A (now the standby host) and install the following:
a.
Solaris 2.6 Operating system: If downgrading to Cisco MGC 7.4(x) or 9.1(5), see Chapter 8, “Sun
Solaris 2.6 Operating System Installation.”
b.
Cisco MGC software release that was originally installed on your system prior to the
upgrade—either Cisco MGC 9.x or 7.4(x).
For Cisco MGC installation procedures, see the following:
– For Cisco MGC 9.1(5), see Chapter 7, “Cisco MGC Software Release 9.1(5) Installation.”
– For later Cisco MGC releases, see Chapter 3, “Cisco MGC Software Release 9 Installation.”
– For Cisco MGC 7.(x), see the “Cisco Media Gateway Controller Software Release 7 Installation
and Configuration Guide.”
Step 13
Set the value of pom.dataSync=true. Use an editor such as vi to edit the file
/opt/CiscoMGC/etc/XECfgParm.dat to set this value.
Step 14
Bring up Host A and ensure that call replication is taking place between Host A and Host B. Type the
following command and press Enter:
rtrv-tc:all
This completes the downgrade procedures for Scenario 2.
If Migration Fails
When upgrading the Cisco MGC software, you may encounter unique instances which result in
migration failures. An unsuccessful migration is indicated by the following message in the log:
Error migrating
If this occurs, you must install the latest patches then run config-lib, as shown in the following
procedures.
Note
If you are migrating to Cisco MGC 9.4(1) and the migration fails: The subroutine that adds the
addition of the software packages exits and the last package is skipped after a migration failure. If this
occurs, perform the following command on the file located in the APPLICATIONS directory:
cd APPLICATIONS
pkgadd -d CSC0gd004.pkg
Step 1
Download the latest Cisco MGC system and protocol patches.
Step 2
Run the config-lib script (this script resides in opt/CiscoMGC/local). Type the following command and
press Enter:
config-lib
Text similar to the following is displayed:
Configuration File Library Main Menu
1. List Configuration Versions in Library
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-17
Chapter 6
Upgrading the Cisco MGC Software
If Migration Fails
2. Save Production to a new Library Version
3. Copy Library Version to Production
4. Remove Configuration Library Version
Enter Selection or 'q' to quit> 2
Step 3
Type 2 to select the option Save Production to a new Library Version and press Enter.
This operation will copy the current version of configuration files from the PRODUCTION area to a new
LIBRARY version.
Text similar to the following is displayed:
Is this what you want (y/n)?
Step 4
Type y to confirm your selection and press Enter.
Text similar to the following is displayed:
Please Enter a Tag for this Version:
Step 5
Assign a configuration file name (referred to as "Tag" in the text display above) and press Enter. For
example, backup_config_01.
You are returned to the main menu and text similar to the following is displayed:
Copying to the backup_config_01 version...
Completed the save
The Configuration File Library Main Menu
1. List Configuration Versions in Library
2. Save Production to a new Library Version
3. Copy Library Version to Production
4. Remove Configuration Library Version
Enter Selection or 'q' to quit>
Step 6
Type 3 to select the option Copy Library Version to Production and press Enter.
A screen showing the saved configuration version is displayed:
Configuration Versions
1. backup_config_01
***Current Production Version = backup_config_01
Enter Selection to Copy or 'q' to go back>
Step 7
Type the number that matches the previously provided file name (for example, in this case, type 1 for
backup_config_01) and press Enter.
A screen similar to the following displays the saved configuration version:
***Start checking if migration is needed...
starting migration ...
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
from version 9.2003 to version 9.3 ...
version.dat
variant.dat
alarmCats.dat
compTypes.dat
tables.dat
buckets.dat
alarmTable.dat
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-18
OL-1150-15
Chapter 6
Upgrading the Cisco MGC Software
If Migration Fails
migrating thresholds.dat
migrating measProfs.dat
migrating measCats.dat
migrating mdlProcess.dat
migrating extProcess.dat
migrating extNodeTypes.dat
migrating profileTypes.dat
migrating mmlCommands.dat
migrating properties.dat
migrating sigPath.dat
migrating dial plan and route analysis files
Migrating routing files...
Migrating dial plans...
Migrating IP links...
Migrating C7IP links...
migrating TimesTen database
Migrating database from 9.2003 to 9.3
Database successfully migrated to 9.3
migrating from version 9.3 to version 9.3001 ...
migrating dynamic files completed
migrating version.dat
migrating propSet.xml.dat
migrating propVal.xsd.dat
migrating variant.dat
migrating alarmCats.dat
migrating compTypes.dat
migrating tables.dat
migrating buckets.dat
migrating alarmTable.dat
migrating thresholds.dat
migrating measProfs.dat
migrating measCats.dat
migrating mdlProcess.dat
migrating extProcess.dat
migrating extNodeTypes.dat
migrating profileTypes.dat
migrating mmlCommands.dat
migrating properties.dat
migrating sigPath.dat
migrating dial plan and route analysis files
Migrating routing files...
Migrating dial plans...
Migrating IP links...
Migrating C7IP links...
migrating TimesTen database
Migrating database from 9.2003 to 9.3
Database successfully migrated to 9.3
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
migrating
from version 9.3 to version 9.3001 ...
dynamic files completed
version.dat
propSet.xml.dat
propVal.xsd.dat
variant.dat
alarmCats.dat
compTypes.dat
tables.dat
buckets.dat
alarmTable.dat
thresholds.dat
measProfs.dat
measCats.dat
mdlProcess.dat
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
6-19
Chapter 6
Upgrading the Cisco MGC Software
If Migration Fails
migrating extProcess.dat
migrating extNodeTypes.dat
migrating mmlCommands.dat
migrating profileTypes.dat
migrating codec.dat
migrating static files completed
migrating profiles.dat
migrating properties.dat
migrating dial plan and route analysis files
Migrating routing files...
Migration routing file:routeAnalysis.dat:
Migrating dial plans...
Migration dialplan file:MGX7.dialPlan:
Migrating IP links...
Migrating C7IP links...
migrating TimesTen database
Migrating database from 9.3 to 9.3001
Database successfully migrated to 9.3001
migration completed successfully
***finish checking migration...
This operation will copy the selected version of each configuration file
from the LIBRARY to the PRODUCTION area.
Do you want to overwrite the production files (y/n)?
Step 8
Type y and press Enter.
Text similar to the following is displayed:
Removing data files in Production Area....
/opt/CiscoMGC/etc/*.routeAnalysis: No such file or directory
Copying data files of selected version to the data Production Area....
Completed copy
The Configuration File Library Main Menu
1. List Configuration Versions in Library
2. Save Production to a new Library Version
3. Copy Library Version to Production
4. Remove Configuration Library Version
Enter Selection or 'q' to quit>
Step 9
Type q to quit and press Enter.
q
Step 10
Ensure that the config-lib migration works and that all states are operational by entering the following
MML commands:
rtrv-ne
rtrv-tc:all
rtrv-dest:all
rtrv-c7lnk:all
Contact Cisco TAC if you need assistance (see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii).
The procedure for running config-lib is now complete.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
6-20
OL-1150-15
CH A P T E R
7
Cisco MGC Software Release 9.1(5) Installation
This chapter describes how to install Release 9.1(5) of the Cisco Media Gateway Controller (MGC)
software.
Note
For Release 7.4 and later, the Cisco telephony controller software is called the Cisco Media Gateway
Controller software. The Cisco MGC software files and processes are located the /opt/CiscoMGC
directory.
This chapter contains the following sections:
Note
•
Before You Start, page 7-2
•
Installing the Cisco MGC Software Release 9.1(5), page 7-3
•
Installing the Cisco Security Package, page 7-7
For information on configuring the Cisco MGC software, see the following publication:
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-1
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Before You Start
Before You Start
Before you start, perform the following steps:
•
Review the hardware and software requirements found in the document Release Notes for the
Cisco Media Gateway Controller Software Release 9.
•
Have your company's internal support and Cisco support contact information readily available so
you can get help with the installation if needed. (If you have questions or need assistance, see the
“Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii of the
Cisco support contact information.)
•
Ensure that you have access to the console port on your Cisco MGC host.
Cautions, Notes, and Tips
Caution
To prevent the system from running out of disk space during installation and to avoid removal of data
files and databases to compensate, you must first verify that there is enough hard disk space to support
your intended installation. You can delete unnecessary log files (platform*.log), user-generated trace
files (*.btr), call detail record (CDR) files (.bin or .csv), old *.tar files, or user-generated toolkit files (in
the /var/cust_specific/toolkit directory) to free space. You also need at least 4 GB of disk space for the
/opt file system.
Caution
Make sure to follow the Cisco MGC software installation and uninstallation sequence listed in Cisco
MGC Software Installation/Uninstallation Sequence, page 7-3.
Note
For the software to work properly, you must reboot the system every time you modify any file in the /etc
directory.
Note
Monitor system output frequently for error messages during the installation process and correct any error
conditions before continuing with the installation.
Tip
Allow for at least 2 hours to install the Sun Solaris 2.6 operating system and approximately 1 hour to
install the Cisco MGC software.
Installation Overview
Before you begin installing the Cisco MGC software, make sure the Sun Operating System is properly
installed. The following table provides the location of the installation procedure you may require.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-2
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Cisco MGC Software Installation/Uninstallation Sequence
Table 7-1
Installation Overview and Reference Sections
Installation Procedure
Refer to...
If the Sun Solaris 2.6 operating system is not yet
installed, you must first install it.
Start with Chapter 8, “Sun Solaris 2.6 Operating
System Installation.”
With the Sun Solaris 2.6 operating system
installed, go to the correct section in this chapter:
•
If you are upgrading from a previous release,
follow the procedures found in the
“Upgrading to Software Release 9.1(5)”
section on page 9-5.
•
If you are installing the software for the first
time, follow the procedures found in the
“Installing the Cisco MGC Software Release
9.1(5)” section on page 7-3.
Cisco MGC Software Installation/Uninstallation Sequence
For the system to work properly, it is important that Cisco MGC software installation be performed in
the following order:
Note
At this point, the Solaris Operating System 2.6 and Solaris Operating System 2.6 patch cluster
(CSCOh007) should be already installed in your system.
1.
Cisco MGC software
2.
Solaris System Security Patch (CSCOh013)
Caution
Software must be uninstalled in the reverse order in which it is installed. For example, you must first
uninstall software package CSCOh013 before you uninstall the Cisco MGC software.
Note
You do not have to uninstall the Cisco MGC if only software package CSCOh013 requires updating but
the Cisco MGC does not.
Installing the Cisco MGC Software Release 9.1(5)
Note
For a sample output listing from the install.sh script, see Appendix D, “Sample Output from install.sh”
section on page D-1.
Note
Remove /usr/ucb from the path environment variable before the initial installation of the Cisco MGC
software. However, if /usr/ucb is needed, make sure that it is located in the path variable in the user
profile after /usr/sbin.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-3
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco MGC Software Release 9.1(5)
Installing on a Simplex System
To install the Cisco MGC software, complete the following steps:
Step 1
Log in as root.
Step 2
Enter the following command:
cd /etc
Step 3
Open the passwd file with your editor (such as vi).
Step 4
Save any changes to the passwd file.
Step 5
Close the passwd file.
Step 6
Insert the Cisco MGC Software Release 9 CD into the CD-ROM drive.
Caution
If you are upgrading to a new software release, you must first copy the new software from the
CD-ROM to an appropriate directory in your system (for example, create a directory as root
user under /opt), then perform the installation from that directory. This step prevents possible
CD-ROM ejection problems.
When the upgrade has successfully completed, it is strongly recommended that you delete the
software you copied from the CD-ROM to your directory, to avoid running out of disk space.
Step 7
To install the Release 9 Cisco MGC software, enter the following commands:
# ./install.sh
Step 8
The following prompt is displayed:
Use supplied admin file for unattended install? [n] [y,n,?,q]
Answer y to perform an unattended installation. If you answer n, you must answer prompts and press
Enter for each package that is installed.
Step 9
The following prompt is displayed:
Base directory for Toolkit (default /opt/Toolkit) [?,q]
Press Enter to accept /opt/Toolkit, the default directory.
Step 10
The following prompt is displayed:
The CSCOgu000 utilities package must be installed prior to other components but has not
been detected on your system.
Would you like to install it now? [y] [y,n,?,q]
Answer y to install the utilities package. This package must be installed before installing the rest of the
software.
Step 11
The following prompts are displayed:
Base directory
Enter CiscoMGC
Enter CiscoMGC
Enter CiscoMGC
Enter CiscoMGC
for CiscoMGC (default /opt/CiscoMGC) [?,q]
user name [mgcusr]
UID [20000]
group name [mgcgrp]
GID [20000]
We recommend that you accept the default values (by pressing Enter).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-4
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco MGC Software Release 9.1(5)
You can, however, specify a different user ID and a group ID. If the ID you specify already exists on the
system, the corresponding ID will be determined and reused, or you will be prompted to enter another
ID.
Caution
No validation is performed on the IDs you enter. If you enter an invalid ID, the utilities
package does not add any accounts.
The system returns a message stating that the CSCOgu000 utilities package was successfully installed.
Step 12
Rebooting after a successful utilities package installation might not be necessary, depending on your
system configuration.
Note
Rebooting may take approximately 5 minutes.
If a reboot is not required, the installation continues uninterrupted.
If a reboot is required, perform the following steps when prompted:
a.
Note
b.
Type the command displayed on the screen and press Enter.
If the command shown on the screen does not work, you can enter the /usr/sbin/reboot
command to reboot the system.
After the reboot finishes, restart install.sh to install the remaining packages. To restart install.sh,
type the following command at the # prompt and press Enter:
# ./install.sh
Note
c.
This procedure can take approximately an hour to complete.
The following prompts display:
Use supplied admin file for unattended install? [n] [y,n,?,q]
d.
Note
Step 13
Type y and press Enter.
The installation of the application software may take some time.
The system checks the memory and CPUs in the host. If you do not have enough memory or CPUs, a
caution appears. After the check is complete and the software packages are installed, the performance
profile script is automatically invoked. The following prompt appears:
Configure System for (1) Standard Performance Profile (2) Maximum
(3) Maximum Call Throughput
Enter 1, 2, or 3
Sustained Calls
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-5
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco MGC Software Release 9.1(5)
Note
Options 1, 2, and 3 are performance tuning options that allow optimizing certain parameters and
settings on the system for better performance, based on your system requirements. This choice
should have been resolved when Cisco analyzed your system requirements. We recommend
selecting Option 1.
When you select a performance profile, the performance profile script sets the parameters in
XECfgParm.dat that are appropriate for your selected profile.
Selected performance profiles do not take effect until the Cisco MGC is started.
Enter 1, 2 or 3 to choose the performance profile you want and press Enter.
Caution
The performance profile can only be selected during the MGC software installation. If a
wrong selection is made and the host is rebooted, you must uninstall and re-install the Cisco
MGC software.
Step 14
If you have a simplex configuration, proceed to the “Installing the Cisco Security Package” section on
page 7-7.
Step 15
After installing the Cisco Security Package, continue to the “Configuring Groups and Users” section on
page 5-10.
This completes the installation of the Cisco MGC software for a simplex configuration. For a sample
install.sh log file, see Appendix D, “Sample Output from install.sh” section on page D-1.
See the Cisco Media Gateway Controller Provisioning Guide for information on provisioning the Cisco
MGC software on a simplex system.
If you have a redundant configuration, continue to the section “Installing on a Fault Tolerant System”
section on page 7-6.
If you have questions or need assistance, see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii.
Installing on a Fault Tolerant System
Caution
To ensure the successful installation of a fault tolerant configuration, after Step 12 of the “Installing on
a Simplex System” section on page 7-4, make sure that you provision the software for the active Cisco
MGC host first, before proceeding to Step 1, below. Refer to the Cisco Media Gateway Controller
Provisioning Guide for information about the following:
- Provisioning the active Cisco MGC host
- Procedures for converting the active Cisco MGC host to standby host
Note that only one active provisioning session is permitted and provisioning is only permitted on the
active Cisco MGC host.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-6
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
Exit the provisioning session on the active host and continue to Step 1, below. If software is not
provisioned after it is installed on the active Cisco MGC host, the standby host will not be synchronized
with the active host. As a result, a forced switchover may cause the switchover to fail.
To install the Cisco MGC software on a fault tolerant system (with two Cisco MGC hosts and Cisco
SLTs), complete the following steps:
Note
The MGC-install.log and the MGC_pkgerrors.log are stored in the /var/adm directory.
Step 1
Continuing from Step 15 of the “Installing on a Simplex System” section on page 7-4, exit server 1.
Step 2
Log in to server 2 as root and go to the # prompt.
Step 3
Insert the Cisco MGC Software Release 9 CD into the server 2 CD-ROM drive.
Step 4
Follow the instructions in Step 7 through Step 15 of the “Installing on a Simplex System” section on
page 7-4.
Step 5
Configure the execution environment parameters and database replication for fault tolerant systems,
using the following sections:
•
Configuring Switchover, page 5-41
•
Initializing the Provisioning Object Manager, page 5-43
•
Initializing the Call Screening Database, page 5-57
This completes the installation of the Cisco MGC software. Continue to the “Configuring Groups and
Users” section on page 5-10 to configure groups and users. If you have questions or need assistance, see
the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Note
Always check CCO (http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml) to ensure that you have
the latest required patch version released by Cisco on your system, CD, or file system (if downloaded
previously from CCO).
Installing the Cisco Security Package
The system security patches install the Cisco Security Package. This package reduces the number of
known system security vulnerabilities.
Do the following procedures to install the Cisco Security Package.
Note
The Sun Solaris 2.6 operating system and Cisco MGC software must already be installed in your system
before you can install the Cisco Security Package.
You must have system administrator privileges to install this package.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-7
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
Caution
If you are planning to run mgcrestore, make sure you are installing the same version of the Cisco
Security Package that was installed on your system when mgcbackup was run. Or, if the Cisco Security
Package was not installed on your system when mgcbackup was run, you must first run mgcrestore
before installing the Cisco Security Package.
Use the command pkginfo -l CSCOh013 to determine the Cisco Security Package version.
Step 1
Before installing the Cisco Security Package, you must first determine the Solaris release version of the
package installed on your system. Type the following command and press Enter:
pkginfo -l <package instance>
The following is similar to the text that is displayed when the pkginfo command is used:
hostname% pkginfo -l CSCOh007
PKGINST:CSCOh007
NAME:Media Gateway Controller Solaris 2.6 patch cluster
CATEGORY:utilities
ARCH:sparc
VERSION:1.0(7)
BASEDIR:/opt/sun_install
VENDOR:Cisco System, Inc.
PSTAMP:2002/01/07 22:10 GMT (embassy)
INSTDATE:Jan 07 2002 17:12
EMAIL:[email protected]
STATUS:completely installed
FILES: 154 installed pathnames
2 shared pathnames
2 directories
4 executables
561747 blocks used (approx)
Note
Step 2
If you have an older version of the Cisco Security patch, you must remove it before installing the new
patch. For package removal procedures, see Removing the Cisco Security Package, page 7-11.
Install latest version of the Cisco Security Package either by downloading the software from CCO or
from a CD-ROM.
a.
If you are downloading the software from CCO, store the Cisco Security Package on your UNIX
platform. To determine the Solaris release version of the package you downloaded, use the
following command:
pkg -l -d <package instance>.pkginfo
The following is is similar to the text that is displayed when using the -d option with the pkginfo
command:
hostname% pkginfo -l -d CSCOh013.pkg
PKGINST:CSCOh013
NAME:Media Gateway Controller Security 2.6 package installation and patches
CATEGORY:utilities
ARCH:sparc
VERSION:1.0(5)
BASEDIR:/opt/sun_install
VENDOR:Cisco System, Inc.
PSTAMP:2001/07/20 17:48 GMT (embassy)
EMAIL:[email protected]
STATUS:spooled
FILES:
8 spooled pathnames
2 directories
1 executables
5 package information files
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-8
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
4 blocks used (approx)
b.
Step 3
If you are installing the software from a CD-ROM, insert the Cisco Media Gateway Controller
Software CD into the CD-ROM drive.
Type the following command at the # prompt and press Enter.
a.
If you are using the file downloaded from CCO, enter the following command:
# pkgadd -d ./CSCOh013.pkg
b.
If you are installing from a CD-ROM, enter the following command:
# pkgadd -d /cdrom/cdrom0/solaris_patches/CSCOh013.pkg
The following text is displayed:
The following packages are available:
1 CSCOh013
Media Gateway Controller Security package compatible with Solaris 2.6 and
Solaris 8
(sparc) 1.0(x)
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 4
Select all by pressing Enter. The following is an example of the text display:
Processing package instance <CSCOh013> from </auto/mgc-build/BUILD/SUN/1.xx/CSCOh013.pkg>
Media Gateway Controller Security 2.6 and Solaris 8
(sparc) 1.0(x)
Cisco System, Inc.
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh013> [y,n,?] y
Step 5
Type y and press Enter to install the package. The following is an example of the text display:
Installing Media Gateway Controller Security 2.6 package compatible with Solaris 2.6 and
Solaris 8 as <CSCOh013>
## Executing preinstall script.
Platform is SUNW,Ultra-5_10
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/var/sadm/pkg/CSCOh013/save/CiscoSec.sh
[ verifying class <none> ]
## Executing postinstall script.
Logfile is /var/adm/CSCOh013.install.log
*** Installation of system security update package started...Wed Dec 12 10:36:37 EST 2001
***
Output will be logged in
/var/adm/CSCOh013.install.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-9
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
You are running as root - Good...
Operating System: SunOS 5.6
Backup directory does not exist - creating it now...
Original files will be saved. Run this script
with the parameter 'uninstall' to restore
system to its original state
The following files will be removed from /etc/rc2.d:
Remove /etc/rc2.d/K60nfs.server
File /etc/rc2.d/K77dmi not found
Remove /etc/rc2.d/S47asppp
Remove /etc/rc2.d/S71rpc
Remove /etc/rc2.d/S73cachefs.daemon
Remove /etc/rc2.d/S73nfs.client
Remove /etc/rc2.d/S74autofs
Remove /etc/rc2.d/S76nscd
Remove /etc/rc2.d/S80lp
Remove /etc/rc2.d/S80spc
Remove /etc/rc2.d/S85power
Remove /etc/rc2.d/S88sendmail
Remove /etc/rc2.d/S89bdconfig
Remove /etc/rc2.d/S91leoconfig
Remove /etc/rc2.d/S92rtvc-config
Remove /etc/rc2.d/S92volmgt
Remove /etc/rc2.d/S93cacheos.finish
File /etc/rc2.d/S99dtlogin not found
Remove
Remove
Remove
Remove
Remove
Remove
the following users from the password file
lp from password file
uucp from password file
nuucp from password file
smtp from password file
listen from password file
Remove lp crontab entry
Create new inetd.conf file with only ftp,
telnet and echo services enabled
Adjust kernel parameters in the /etc/system file
Force TCP/IP to use random initial seeds
Enable recording of failed login attempts
Create a new (minimal) inetsvc startup file
Restrict FTP Usage
Don't allow telnet users to log in as root
Disable keyboard abort sequence
Add /bin/true to the /etc/shells file
Create /etc/init.d/nddconfig file
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-10
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
**
**
**************************************************
**************************************************
Step 6
Reboot your machine with the -r option. To do so, type the following command and press Enter:
# /usr/sbin/shutdown -y -go -i6
Step 7
When the machine finishes rebooting, the text similar to the following is displayed:
Done!
Installation of <CSCOh013> was successful.
This completes the installation of the Cisco Security Package. If you have questions or need assistance,
see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Removing the Cisco Security Package
Do the following procedure if you need to remove the Cisco Security Package. Contact Cisco TAC if
you need assistance (see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii).
Caution
Removing the Cisco Security Package (CSCOh013) is the first step in removing the Cisco MGC
software. Remove the Cisco Security Package only if you intend to perform tasks such as upgrading the
Cisco MGC or upgrading to a newversion of CSCOh013. Otherwise, the /etc/system files might be
corrupted if removed out of order and security might be compromised if CSCOh013 is removed without
removing the Cisco MGC.
Note
Make sure the Sun Solaris 2.6 operating system and the Cisco MGC software are still installed in your
system before you remove the Cisco Security Package.
Step 1
Type the following command at the # prompt and press Enter:
# pkgrm CSCOh013
Text similar to the following is displayed:
The following package is currently installed:
CSCOh013
Media Gateway Controller Security package compatible with Solaris 2.6
and Solaris 8
(sparc) 1.0(6)
Do you want to remove this package? y
Step 2
Type y and press Enter to remove the package. Text similar to the following is displayed:
## Removing installed package instance <CSCOh013>
This package contains scripts which will be executed with super-user
permission during the process of removing this package.
Do you want to continue with the removal of this package [y,n,?,q] y
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-11
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
Step 3
Type y and press Enter to continue the removal of the package. Text similar to the following is
displayed:
## Verifying package dependencies.
## Processing package information.
## Executing preremove script.
Logfile is /var/adm/CSCOh013.uninstall.log
*** Removal of system security update package started...Wed Dec 12 10:38:13 EST 2001 ***
Output will be logged in /var/adm/CSCOh013.uninstall.log
You are running as root - Good...
Operating System: SunOS 5.6File K77dmi not found
Restore /etc/rc2.d/S47asppp
Restore /etc/rc2.d/S71rpc
Restore /etc/rc2.d/S73cachefs.daemon
Restore /etc/rc2.d/S73nfs.client
Restore /etc/rc2.d/S74autofs
Restore /etc/rc2.d/S76nscd
Restore /etc/rc2.d/S80lp
Restore /etc/rc2.d/S80spc
Restore /etc/rc2.d/S85power
Restore /etc/rc2.d/S88sendmail
Restore /etc/rc2.d/S89bdconfig
Restore /etc/rc2.d/S91leoconfig
Restore /etc/rc2.d/S92rtvc-config
Restore /etc/rc2.d/S92volmgt
Restore /etc/rc2.d/S93cacheos.finish
File S99dtlogin not found
Replace the following userids in the password file
lp uucp nuucp smtp listen
Restore lp crontab entry
Restore /etc/inetd.conf file
Restore /etc/system file
Restore /etc/default/inetinit file
Disable recording of failed login attempts
Restore /etc/init.d/inetsvc file
/etc/ftpusers did not exist - delete existing file
Restore /etc/default/login file
Restore /etc/default/kbd file
Restore /etc/shells file
Restoring system to original configuration...
Restore /etc/rc2.d/K60nfs.server
/etc/init.d/nddconfig did not exist originally
Delete existing file
/etc/rc2.d/S70nddconfig did not exist - delete existing file
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-12
OL-1150-15
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
Backup directory is being removed
**************************************************
**************************************************
**
**
** NOTE!! The machine must be REBOOTED in order **
**
for these changes to take effect
**
**
**
**************************************************
**************************************************
Step 4
Reboot your machine with the -r option. To do so, type the following command and press Enter:
# reboot -- –r
Text similar to the following is displayed:
Done!
## Removing pathnames in class <none>
/var/tmp <shared pathname not removed>
/var/sadm/pkg/CSCOh013/save/CiscoSec.sh
/opt/sun_install <shared pathname not removed>
## Updating system information.
Removal of <CSCOh013> was successful.
This completes the removal of the Cisco Security Package. If you have questions or need assistance, see
the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
To configure the Cisco MGC software, go to Chapter 5, “Configuring the Cisco MGC Software.”
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
7-13
Chapter 7
Cisco MGC Software Release 9.1(5) Installation
Installing the Cisco Security Package
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
7-14
OL-1150-15
CH A P T E R
8
Sun Solaris 2.6 Operating System Installation
The following sections in this chapter provide instructions on how to load the Solaris 2.5.1 or Solaris
2.6 operating system on the Netra t 100/105, t 1120/1125 and t 1400/1405 machines.
•
Installing the Sun Solaris 2.6 and 2.5(1) Operating System, page 8-1
•
Installing the Solaris Patch Cluster, page 8-16
•
Installing the Alarm Software, page 8-20
•
PCI Card Configuration, page 8-25
•
Configuring a Second Ethernet Interface, page 8-26
•
Configuring a Second Disk Drive, page 8-27
•
Replacing Hard Disks for Existing Solaris 2.6 Platforms, page 8-63
•
Troubleshooting, page 8-66
There are points in this procedure when your entries will depend on the target machine model, disk drive
size or the operating system type. You will be alerted and informed where to look for the required
information.
If the Sun Solaris operating system is already installed on your hardware platform, you can skip this
chapter and go to Chapter 7, “Cisco MGC Software Release 9.1(5) Installation.”
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
The procedures in this chapter require a working knowledge of the system administration procedures for
the Sun Solaris (UNIX) 2.6 operating system.
Note
Allow at least two hours for the installation of the Sun Solaris 2.6 or 2.5 (1) operating system.
Note
During the installation of either software package on the Netra t 1120/1125 machines, leave the front
panel open. The CD-ROM drive will automatically eject the CD.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-1
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Note
Due to a known Sun bug, when installing Solaris on a Netra t 100/105, the CD-ROM will become
disabled prior to the installation the Cisco patch packages. You must have a copy of patch
107665-01.tar.Z locally or have the ability to install the patch by some means other than the CD-ROM.
This patch will re-enable the CD-ROM. The recommended form of installation is through a network.
The required patch is also included in the Solaris 2.6 patch cluster.
Booting from a Local CD-ROM on Netra t 1120/1125, t 1400/1405 and t 100/105
To boot the system from a local CD-ROM drive:
Step 1
Load the disk labeled Operating Environment Installation CD (p/n: 704-6914-10) into the CD-ROM
drive.
Step 2
If the system is currently running, login in as root and bring the system to the ok prompt by entering the
following command:
# init 0
Step 3
From the ok prompt, enter the following command to boot the system from the CD-ROM drive:
Note
If the target machine is a Netra t 100/105, you must set the OpenBoot PROM environment
parameters to the default settings prior to booting the system from the CD-ROM.
Enter the following command if the target machine is a Netra t 100/105: ok set-defaults
ok boot cdrom
If the target machine has never had an operating system installed, a screen similar to the following is
displayed when the CD-ROM boot has completed:
Note
The SunOs Release 5.7 Version that is displayed in the following screen refers to the release
version of the Operating Environment CD.
Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args:
SunOS Release 5.7 Version Generic_106541-06 [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1999, Sun Microsystems, Inc.
Solaris Web Start 3.0 installer
No frame buffer found.
Command line install is available in English only.
English has been selected as the language in which to perform the install.
Starting the Web Start 3.0 Solaris installer
Solaris installer is searching the system's hard disks for a
location to place the Solaris installer software.
The default root disk is /dev/dsk/c0t0d0.
The Solaris installer needs to format
/dev/dsk/c0t0d0 to install Solaris.
WARNING: ALL INFORMATION ON THE DISK WILL BE ERASED!
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-2
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Do you want to format /dev/dsk/c0t0d0?
[y,n,?,q]
If an operating system has been previously installed on the machine, a screen similar to the following is
displayed with two warnings:
Command line install is available in English only.
English has been selected as the language in which to perform the install.
Starting the Web Start 3.0 Solaris installer.
Solaris installer is searching the system's hard disks for a
location to place the Solaris installer software.
This system appears to contain a version of Solaris.
The Solaris installer does not allow upgrading. If you
choose to use this installer an initial install will be
required. Any information on your system's disks could be erased.
Would you like to use this installer?
Step 4
[y,n,?]
In either case, select y and press Enter to continue until the following text is displayed:
Enter a swap partition size between 320Mb and 17269Mb, default = 512Mb [?]
Type 320 (4 GB disk drives) or 2040 (9 GB, 18 GB, and 36 GB disk drives) for swap partition size and
press Enter. It is not necessary to enter “MB” after the number; the system assumes that the entry is in
megabytes.
A screen similar to the following is displayed:
You have selected /dev/dsk/c0t0d0 with a swap size of 2040/320 to be used by the Solaris
installer.
WARNING: ALL INFORMATION ON THE DISK WILL BE ERASED!
Is this OK [y,n,?,q]
Step 5
Select y and press Enter to begin the installation.
A screen similar to the following is displayed:
The system will copy the necessary files for the CD-ROM and reboot.
This process takes approximately 10 minutes to run and does not require user intervention. A screen
similar to the following is displayed:
Welcome to the Web Start Solaris Command Line installation!
The following questions will gather information about this system.
This information will be used to configure:
Network
Name Service
Date and Time
Root Password
Power Management
<Press Return to continue>
Step 6
Press Enter to continue.
A screen similar to the following is displayed:
Please enter a host name, which identifies this system on the network. The name must be
unique within the domain in which it resides; creating a duplicate host name will cause
problems on the network after you install Solaris.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-3
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
A host name must be at least two characters; it can contain letters, digits, and minus
signs (-).
Enter host name: <host-name>
Step 7
Type the hostname of the target Netra machine, then press Enter.
A screen similar to the following is displayed:
Please specify whether your system will be networked. Specify Yes if the
system is connected to the network by one of the Solaris or vendor
network/communication Ethernet cards that are supported on the Solaris CD. See
your hardware documentation for the current list of supported cards.
Specify No if the system is connected to a network/communication card that is not
supported or not connected to a network.
Is this machine networked (y/n) [n]?
Step 8
Select y and press Enter to specify that this machine is networked.
A screen similar to the following is displayed:
Please enter the Internet Protocol (IP) Address for this system. It must be unique and
follow your site's address conventions, or a system/network failure could result.
IP Addresses contain four sets of numbers separated by periods (for example 129.200.9.1).
Enter this machine's IP Address:
Step 9
Enter the IP address assigned to this system in dotted decimal format, then press Enter.
A screen similar to the following is displayed:
Please specify the netmask of your subnet. A default netmask is shown; do not accept the
default unless you are sure it is correct for your subnet. A netmask must contain four
sets of numbers separated by periods (for example 255.255.255.0).
Enter the subnet netmask [255.255.255.0]:
Step 10
Refer to Table 1-6 on page 1-5 for the specific IP netmask for the subnet and type it here, then press
Enter.
Warning
Do not accept the default netmask unless you are sure it is correct for your subnet.
A screen similar to the following is displayed:
Please provide name service information. Select the name service that will be used by
this system, or None if your system will either, not use a name service at all, or if it
will use a name service not listed here
Available name services:
1.
2.
3.
4.
NIS+
NIS
DNS
None
Please enter the number corresponding to the type of name service you
would like [ ]:
Step 11
Select 4 for None and press Enter to specify your default time zone. You can specify a default time zone
in one of three ways described in the screen displayed above.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-4
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
A screen similar to the following is displayed:
Please select how to specify your default time zone.
Specify Time Zone by:
1. Geographic region
2. Offset from GMT
3. Time zone file
Please enter the number corresponding to how you would like to specify
the time zone [1]:
Step 12
Select the means of defining your default time zone then press Enter. The screens that follow will
prompt you for appropriate input until the following screen is displayed:
The default date and time is (current date and time of defined time zone). Do you want to
use this date and time (y/n) [y]?
Step 13
You can accept the date and time information as shown by pressing Enter, or you can select n and press
Enter to be prompted to enter different values. If the information is correct, press Enter.
The next screen allows you enter a root password for the system. You will be prompted to enter it a
second time for verification.
Type in an alphanumeric string to be used as the root password for the computer you are
setting up.
Enter the root password []:
Step 14
Refer to Table 1-6 on page 1-5 for the root password for this system and enter it here. Press Enter to
continue. You will now be prompted to confirm the root password.
A screen similar to the following is displayed:
Retype the above password for confirmation.
Enter the root password again []:
Step 15
Re-type the root password for this system, then press Enter.
A screen similar to the following is displayed:
Do you want Power Management turned on (y/n) [n]?
Step 16
Select n to disable Power Management, then press Enter.
A screen similar to the following is displayed:
You can choose to be asked the preceding question every time you reboot the system.
Alternatively, you can choose never to be asked about Power Management again.
Ask about Power Management at each reboot (y/n) [n]?
Step 17
Select n, then press Enter.
A screen similar to the following is displayed:
You have entered the following values:
Host Name:
IP Address:
System part of a subnet:
Netmask:
Name Service:
Time Zone:
Power Management:
host-name
IP_address
Yes
IP_netmask
NONE
time_zone
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-5
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Turn Power Management Off
Do not ask about Power Management at reboot.
Enter 'y' to apply these values and proceed to the next stage of the
installation, or 'n' to return to the beginning and make changes (y/n):
Step 18
Select n if these values are not correct, then press Enter to return to Step 6. If these values are correct,
select y, then press Enter. Continue on to “Installing the Solaris 2.6 or 2.5.1 Operating System on Netra
t 1120/1125, t 1400/1405 and t 100/105” section on page 8-6.
Installing the Solaris 2.6 or 2.5.1 Operating System on Netra t 1120/1125,
t 1400/1405 and t 100/105
This section provides the procedure for installing the Solaris 2.6 or 2.5.1 operating system.
Note
This procedure covers 9 GB, 18 GB, and 36 GB disk drives (see Step 11) for Solaris 2.6. The 36 GB disk
drive is not supported in Solaris 2.5.1.
The following screen is displayed upon the acceptance of Step 18 above.
keyserv: failed to generate host's netname when establishing root's key.
Solaris Web Start will now gather information to install software for Solaris.
Please wait while initial values are loaded...
Available operating environments:
1.
2.
Solaris 2.5.1 Hardware: 11/97
Solaris 2.6 5/98
Select the number corresponding to the operating environment you would
like to install [1]:
To install the Solaris operating system:
Step 1
Select the number or the desired installation software, then press Enter.
A screen similar to the following is displayed:
You have selected:
Solaris OS:
Solaris 2…
Enter 'y' if this is correct, or 'n' if it is incorrect:
Step 2
If the display represents the software that you have chosen, select y and press Enter to accept. If the
display is not correct, select n and select the correct Solaris installation software.
A screen similar to the following is displayed:
Please insert the Solaris 2… CD.
<Press Return after the CD has been inserted>
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-6
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Step 3
The Operating Environment Installation CD will be ejected automatically from the machine at this time.
Remove it from the CD-ROM drive and load the appropriate Solaris operating system software CD, then
press Enter.
A screen similar to the following is displayed:
Reading CD for Solaris 2…
Please wait while the system is initializing...
To install basic Solaris products into their default directory locations, select Default
Install.
Custom install provides a choice of which Solaris products to install.
it also provides an option to further customize the products install.
For each product,
Types of install available:
1. Default Install
2. Custom Install
Select the number corresponding to the type of install you would like [1]:
Step 4
Select 2 for Custom Install and press Enter to continue.
Note
If you are installing Solaris 2.5.1, skip to Step 9.
A screen similar to the following is displayed:
Select the software localizations you want to install. The English version of Solaris will
be installed by default.
Enable locale German ( de ) (y/n) [n]?
Step 5
Select n and press Enter.
A screen similar to the following is displayed:
Enable locale Spanish ( es ) (y/n) [n]?
Step 6
Select n and press Enter.
A screen similar to the following is displayed:
Enable locale French ( fr ) (y/n) [n]?
Step 7
Select n and press Enter.
A screen similar to the following is displayed:
Enable locale Italian ( it ) (y/n) [n]?
Step 8
Select n and press Enter.
A screen similar to the following is displayed:
Enable locale Swedish ( sv ) (y/n) [n]?
Step 9
Select n and press Enter to continue.
A screen similar to the following is displayed:
Available locales:
1. English (Australia) ( en_AU )
2. English (Canada) ( en_CA )
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-7
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
3.
4.
5.
6.
7.
English
English
English
English
English
(Ireland) ( en_IE )
(New Zealand) ( en_NZ )
(UK) ( en_UK )
(United States) ( en_US )
(POSIX C) ( C )
Select the number corresponding to the desired system locale [6]:
Step 10
Select the number corresponding to the appropriate locale and press Enter.
A screen similar to the following is displayed:
Available software groups:
1.
2.
3.
4.
5.
Entire Solaris Software Group Plus OEM
Entire Solaris Software Group
Developer Solaris Software Group
End User Solaris Software Group
Core Solaris Software Group
Select the number corresponding to the desired Solaris software group [2]:
Step 11
Select 1 for “Entire Solaris Software Group Plus OEM” and press Enter.
One of the following screens will be displayed. You should take note of the disk drive size on the target
machine. The columns in the following steps are labeled for 4, 9, and 36 GB disk drives. There are two
separate columns for 18 Gigabyte disk drives. One column is for the Solaris installation for VSC
applications and one is for the Solaris installation for BAMS applications. Refer to the columns in
Step 20 when asked to define the disk partitions.
A screen similar to the following is displayed:
Please wait while the system is initializing...
Select which disks you want to lay out the file systems on.
Required disk space: 2,705 MB
4 GB disk
Available
Disk
c0t1d0
drive
Disks:
Size
4092 MB
9 GB disk
Available
Disk
c0t0d0
c0t1d0
drive
Disks:
Size
8633 MB
8633 MB
18 GB disk drive
Available Disks:
Disk
Size
c0t0d0
17269 MB
c0t1d0
17269 MB
36 GB disk drive
Available Disks:
Disk
Size
c0t0d0
34730 MB
c0t1d0
34730 MB
Enter ‘y’ to lay out file systems on the specified disk. This will erase all existing
data on the disk. Enter 'n' to leave the disk unmodified.
Layout file systems on disk c0t0d0 (bootdisk) (y/n) [y]?
Step 12
Select y and press Enter to continue.
A screen similar to the following is displayed on systems using two or more disk drives:
Layout file systems on disk c0t1d0 (y/n) [n]?
Step 13
If the target machine is a t 100/105 for BAMS applications, select y and press Enter, otherwise select n
and press Enter to continue.
A screen similar to the following is displayed:
File System operations:
1. Print the current partition table
2. Modify a disk's partition table
3. Done
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-8
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Select the number corresponding to a file system operation, or 'Done' to
proceed with the install [3]:
Step 14
Select 2 and press Enter to set up the disk partitions.
A screen similar to the following is displayed:
4 GB HDD
Available disks:
9 GB HDD
Available disks:
18 GB HDD
Available disks:
1.
1. c0t0d0
/
667 MB
swap
2040 MB
/export/home 5296 MB
1. c0t0d0
/
668 MB
swap
2040 MB
/export/home 14561 MB
2. c0t1d0
3. Done
2. c0t1d0
3. Done
c0t1d0
/
599 MB
swap
320 MB
/export/home 3173 MB
2. Done
Not Selected
Not Selected
18 GB HDD for BAMS
Available disks:
1.
c0t0d0
/
668 MB
swap
2040 MB
/export/home 14561 MB
2.
c0t1d0
3. Done
36 GB HDD
Available disks:
1.
c0t0d0
/
665 MB
swap
2040 MB
/export/home 32023 MB
2.
c0t1d0
Not Selected
3. Done
Select a disk to modify, or Done to return to the previous menu [3]:
Step 15
Select 1 to modify the partitions on disk c0t0d0 and press Enter.
A screen similar to the following is displayed:
4 GB Disk Drive
Disk Name
TotalSpace
Used Space
Free Space
Round Error
#
0.
1.
3.
4.
Slice Name
/
swap
Unused
Unused
c0t1d0
4092
4092
0
0
Slice Size
599 MB
320 MB
Minimum Size
597 MB
320 MB
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-9
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
5.
6.
7.
Unused
Unused
/export/home
8.
Done
3173 MB
0 MB
18 GB Disk Drive
Disk Name
Total Space
Used Space
Free Space
Round Error
c0t0d0
17269
17269
0
0
#
0.
1.
3.
4.
5.
6.
7.
Slice Name
/
swap
Unused
Unused
Unused
Unused
/export/home
8.
Done
Slice Size
668 MB
2040 MB
Minimum Size
665 MB
2040 MB
14561 MB
0 MB
9 GB disk drive
Disk Name
TotalSpace
Used Space
Free Space
Round Error
c0t0d0
8633
8633
0
0
#
0.
1.
3.
4.
5.
6.
7.
Slice Name
/
swap
Unused
Unused
Unused
Unused
/export/home
8.
Done
Slice Size
667 MB
2040 MB
Minimum Size
665 MB
2040 MB
5926 MB
0 MB
36 GB Disk Drive
Disk Name
TotalSpace
Used Space
Free Space
Round Error
c0t0d0
34730
34728
2
0
#
0.
1.
3.
4.
5.
6.
7.
Slice Name
/
swap
Unused
Unused
Unused
Unused
/export/home
8.
Done
Slice Size
665 MB
2040 MB
Minimum Size
665 MB
2040 MB
32023 MB
0 MB
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-10
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Select a slice to modify, or Done to return to the previous menu [8]:
Note
Partition 1 (swap) was already defined in Step 5 of “Booting from a Local CD-ROM on Netra t
1120/1125, t 1400/1405 and t 100/105” section on page 8-2.
When defining the partition size, it is not necessary to enter "MB" after the number. The system
assumes that the entry is in megabytes.
Solaris 2.6: To remove partition 7 in Solaris 2.6, proceed to Step 16 and Step 17.
Solaris 2.5.1: Do not remove partition 7 when installing Solaris 2.5.1. Instead, proceed to
Step 18.
On the 4 GB disk drives, it will be necessary to redefine the root (/) partition after all other
partitions have been defined. At this point, the system will allow the minimum partition size for
the root to be smaller than originally defined.
Step 16
Select 7 and press Enter to remove partition 7.
A screen similar to the following is displayed:
Enter new slice name:
Step 17
Press Enter to remove the name associated with partition 7.
The display shows that partition 7 is "Unused."
Repeat Step 18, Step 19, and Step 20 to define partitions 4, 5 and 6. Use the appropriate column in
Step 20 for partition names and sizes.
Step 18
Select the number of the partition to be defined and press Enter.
A screen similar to the following is displayed:
Enter new slice name:
Step 19
Type the partition name and press Enter.
A screen similar to the following is displayed:
Enter new slice size (in MB) [default]:
Step 20
Type the partition size and press Enter. Each time a partition is defined the changes are displayed on
the screen. The tables below show the end result of defining the drive partitions for each drive size.
Repeat Step 18, Step 19, and Step 20 as necessary to define the remaining partitions.
Table 8-1
4 GB Disk Drive
9 GB Disk Drive
Slice No.
Slice Name Slice Size
(MB)
Slice No.
Slice Name
Slice Size
(MB)
0.
/
151
0.
/
665
1
swap
320
1
swap
2040
3
/var
251
3
unused
0
4
unused
4
/opt
2560
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-11
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Table 8-1
4 GB Disk Drive
9 GB Disk Drive
5
/opt
1170
5
/var
1025
6
/usr
600
6
/usr
2287
7
/home
1600
7
unused
0
Table 8-2
18 GB Disk Drive
18 GB Disk Drive for BAMS
Disk 0
Slice No.
Slice Name Slice Size
(MB)
Slice No.
Slice Name
Slice Size
(MB)
0.
/
668
0.
/
665
1
swap
2040
1
swap
2040
2
overlap
17269
3
unused
0
3
unused
0
4
/opt
17269
4
/opt
11040
5
/var
1000
5
/var
1024
6
/opt/CiscoBAMS
11000
6
/usr
2435
7
unused
0
/CDRS/archive
7
/export/home
500
/opt/CiscoBAMS
17269
Disk 1
0
/data
Table 8-3
36 GB Disk Drive
Slice No.
Slice Name
Slice Size (MB)
0.
/
665
1
swap
2040
2
overlap
34730
3
unused
0
4
/opt
29950
5
/var
1024
6
/usr
1024
7
unused
0
Select a slice to modify, or Done to return to the previous menu:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-12
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
Step 21
Select the number corresponding to Done and press Enter to end partitioning. One of the following
screens will be displayed:
4 GB Disk Drive
Available disks:
1. c0t1d0
/
swap
/var
/opt
/usr
/home
151
320
251
1170
600
1600
MB
MB
MB
MB
MB
MB
668
2040
11040
1024
2435
MB
MB
MB
MB
MB
2. Done
18 GB disk drive
Available disks:
1. c0t0d0
/
swap
/opt
/var
/usr
2.
c0t1d0
Not Selected
3. Done
9 GB Disk Drive
Available disks:
1.
2.
c0t0d0
/
swap
/opt
/var
/usr
c0t1d0
665
2040
2616
1024
2287
MB
MB
MB
MB
MB
Not Selected
3. Done
18 GB Disk Drive For BAMS Software
Available disks:
1.
c0t0d0
/
swap
/opt
/usr
/opt/CiscoBAMS/CDR/archive
/export/home
2. c0t1d0
/opt/CiscoBAMS/data
1000
2040
1729
1000
11000
500
MB
MB
MB
MB
MB
MB
17269 MB
3. Done
36 GB Disk Drive
Available disks:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-13
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
1.
2.
c0t0d0
/
swap
/opt
/var
/usr
c0t1d0
665
2040
29950
1024
1024
MB
MB
MB
MB
MB
Not Selected
3. Done
Select a disk to modify, or Done to return to the previous menu [3]:
Step 22
If the target machine is a t 100/105 for BAMS application, select 2 to modify the partitions on c0t1d0
and press Enter. Go back to Step 18 and follow the steps to define partition 0 of disk c0t1d0, as shown
in Step 21, above. When you have completed defining the partition, select 3 (Done) and press Enter to
continue.
A screen similar to the following is displayed:
File System operations:
1. Print the current partition table
2. Modify a disk's partition table
3. Done
Select the number corresponding to a file system operation, or 'Done' to
proceed with the install [3]:
Step 23
Select 3 and press Enter to continue.
A screen similar to the following is displayed:
The following items will be installed:
Solaris OS:
Software Locales:
System Locale:
Solaris Software Group:
Solaris 2…
none
English (United States) ( en_US )
Entire Solaris Software Group Plus OEM
Enter 'y' to accept these values and start the installation, or 'n' to
return to the beginning and make changes (y/n):
Step 24
If these values are not correct, select n then press Enter to return to Step 1. If these values are correct
select y, then press Enter to continue.
This process will take approximately 30 minutes to run and does not require user intervention. The
following screen will be displayed:
Installing...
Installing Solaris software group
|-1%------------25%----------------50%----------------75%-------------100%|
Installing Additional Software
|-1%------------25%----------------50%----------------75%-------------100%|
Installation details:
1.
2.
Product
Solaris 2… 5/98
Additional Software
Result
Installed
Installed
More Info
Available
Available
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-14
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Sun Solaris 2.6 and 2.5(1) Operating System
3.
Done
Enter the number corresponding to the desired selection for more
information, or Done to continue [3]:
Step 25
Select 3 and press Enter to continue.
A screen similar to the following is displayed:
The system needs to reboot to complete installation.
<Press Return to reboot>
Step 26
Press Enter to reboot the system. The Solaris Software CD is automatically ejected from the CD-ROM
drive. Remove it now.
Step 27
If you wish to define the default gateway, after the system has rebooted, log in as root and enter the
following command:
# route add default default router IP address 2
Refer to Table 1-6 on page 1-5 for the default router IP address
Step 28
To make this permanent, create a file called /etc/defaultrouter and put the default gateway IP address on
the first and only line of the file by entering the following command:
# echo default router IP address > /etc/defaultrouter
Note
Step 29
There is a known bug with the Netra t 100/105 machine. After the installation of the operating system,
the CD-ROM becomes inaccessible. If you are loading the patches over the network by mounting a
remote directory, then you need only enter the commands stated in Step 30 before proceeding to the next
section. If you are loading the patches via CD, it will be necessary to connect to a network, download
the patch and install it, as shown in Step 29, before continuing. The patch is included in package
CSCOh007.pkg and is also available on www.sunsolve.sun.com.
Download the 107665-01.tar.Z patch file to the /var/tmp directory and install the patch by using the
following commands:
#
#
#
#
#
#
Step 30
cd /var/tmp
zcat 107665-01.tar.Z | xf cd 107665-01
./installpatch .
cd ..
rm -rf 107665-01
The Netra t 100/105 is shipped with OBP environment parameters which are different from the defaults.
Enter the following commands to set the environment variables:
# init 0
ok setenv pcib-probe-list 1,2,3
ok setenv output-device ttya
ok setenv input-device ttya
Step 31
Reboot the machine with the following command:
ok boot -r
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Solaris Patch Cluster
This completes the installation of the Solaris operating system. Proceed to “Installing the Solaris Patch
Cluster” to install the Solaris patches.
Installing the Solaris Patch Cluster
In the following sections, procedures are provided for installing the patch cluster on the target machine.
Proceed to “Installing the Solaris 2.6 Patch Cluster on Netra t 1120/1125, t 1400/1405 and t 100/105”
section on page 8-16for Solaris 2.6 Patch installation.
For Solaris 2.5.1 patch installation, proceed to “Installing the Solaris 2.5.1 Patch Cluster on Netra
t 1120/1125 and t 1400/1405” section on page 8-18.
Installing the Solaris 2.6 Patch Cluster on Netra t 1120/1125, t 1400/1405 and
t 100/105
To install the Solaris 2.6 patch cluster:
Step 1
CD-ROM installation: Load the Cisco MGC Solaris Patches CD into the CD-ROM drive. Enter the
following command to install the Solaris 2.6 operating system patches:
# pkgadd -d /cdrom/cdrom0/CSCOh007.pkg
Note
Make sure that the CSCOh007 package version number is 1.0.7 or later.
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh007
Virtual Switch Controller Solaris 2.6 patch cluster
(sparc) 1.0(0)E
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to accept the default response of all and continue.
A screen similar to the following is displayed:
Processing package instance <CSCOh007> from </cdrom/ciscomgc_install/CSCOh007.pkg>
Virtual Switch Controller Solaris 2.6 patch cluster
(sparc) 1.0(0)F
Cisco System, Inc.
The selected base directory </opt/sun_install> must exist before
installation is attempted.
Do you want this directory created now [y,n,?,q]
Step 3
Select y and press Enter to continue.
A screen similar to the following is displayed:
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-16
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Solaris Patch Cluster
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
* /opt/sun_install <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q]
Step 4
Select y and press Enter to continue.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh007> [y,n,?]
Step 5
Select y and press Enter to continue.
A screen similar to the following is displayed:
Installing Virtual Switch Controller Solaris 2.6 patch cluster as <CSCOh007>
## Executing preinstall script.
Platform is SUNW,Ultra-60
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/checkPackages2.6
/opt/sun_install/checkPatches2.6
/opt/sun_install/installPatches2.6
/opt/sun_install/packages2.6
/opt/sun_install/patch_optional2.6
/opt/sun_install/patch_order2.6
/opt/sun_install/patch_required2.6
/var/tmp/105181-19.tar.Z
/var/tmp/105210-27.tar.Z
.
.
.
/var/tmp/108199-01.tar.Z
/var/tmp/108201-01.tar.Z
[ verifying class <none> ]
## Executing postinstall script.
!!
!!
!!
!!
You must now change directories to /opt/sun_install and
run the installPatches2.6 script as root.
Installation of <CSCOh007> was successful.
Step 6
Complete the installation of the Solaris 2.6 software patch by entering the following commands:
# cd /opt/sun_install
# ./installPatches2.6 .
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-17
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Solaris Patch Cluster
A screen similar to the following is displayed:
*** InstallPatches2.6 begins Thu Mar 16 10:49:01 GMT 2000 ***
Platform is SUNW,Ultra-60
Changed to /var/tmp directory
Uncompressing 106125-08 ...
Extracting 106125-08 ...
Extraction of patch 106125-08 successful
Installing 106125-08 ...
.
.
.
Uncompressing 105591-07 ...
Extracting 105591-07 ...
Extraction of patch 105591-07 successful
Installing 105591-07 ...
*** InstallPatches2.6 ends Thu Mar 16 11:07:38 GMT 2000 ***
Step 7
Eject the CD by entering the following commands:
# cd /
# eject
Step 8
Edit the /etc/default/kbd file to change the break sequence of the target machine. The line in the file to
be changed is as follows:
# KEYBOARD_ABORT=enable
Change the previous line by removing the # comment and changing the word enable to alternate, as
follows:
# KEYBOARD_ABORT=alternate
Step 9
Reboot the machine by entering the following command:
# init 6
This completes the Solaris operating system and patch installation. Proceed to the “Installing the Alarm
Software” section on page 8-20.
Installing the Solaris 2.5.1 Patch Cluster on Netra t 1120/1125 and t 1400/1405
To install the the Solaris 2.5.1 patch cluster on the target machine:
Step 1
Load the Cisco MGC Solaris Patches CD into the CD-ROM drive. Enter the following command to
install the Solaris 2.5.1 operating system patches:
# pkgadd -d /cdrom/cdrom0/CSCOh0008.pkg
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh008
Virtual Switch Controller Solaris 2.5.1 patch cluster
(sparc) 1.0(0)A
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-18
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Solaris Patch Cluster
Step 2
Press Enter to accept the default response of all and continue.
A screen similar to the following is displayed:
Processing package instance <CSCOh008> from </var/tmp/CSCOh008.pkg>
Virtual Switch Controller Solaris 2.5.1 patch cluster
(sparc) 1.0(0)A
Cisco System, Inc.
The selected base directory </opt/sun_install> must exist before
installation is attempted.
Do you want this directory created now [y,n,?,q]
Step 3
Select y and press Enter to continue.
A screen similar to the following is displayed:
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being used by another
package:
* /opt/sun_install <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q]
Step 4
Select y and press Enter to continue.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh008> [y,n,?]
Step 5
Select y and press Enter to continue.
A screen similar to the following is displayed:
Installing Virtual Switch Controller Solaris 2.5.1 patch cluster as <CSCOh008>
## Executing preinstall script.
Platform is SUNW,Ultra-60
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/installPatches2.5.1
/opt/sun_install/patch_order2.5.1
/var/tmp/103461-33.tar.Z
/var/tmp/103558-15.tar.Z
.
.
.
/var/tmp/107986-01.tar.Z
/var/tmp/108658-01.tar.Z
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-19
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Alarm Software
[ verifying class <none> ]
## Executing postinstall script.
!!
!!
!!
!!
You must now change directories to /opt/sun_install and
run the installPatches2.5.1 script as root.
Installation of <CSCOh008> was successful.
Step 6
Enter the following commands to complete the installation of the Solaris 2.5.1 software patches:
# cd /opt/sun_install
# ./installPatches2.5.1 .
A screen similar to the following is displayed:
Platform is SUNW,Ultra-60
Changed to /var/tmp directory
Uncompressing 103630-15 ...
Extracting 103630-15 ...
Extraction of patch 103630-15 successful
Installing 103630-15 ...
.
.
.
Uncompressing 107524-01 ...
Extracting 107524-01 ...
Extraction of patch 107524-01 successful
Installing 107524-01 ...
*** InstallPatches2.5.1 ends Thu Mar 16 19:58:02 GMT 2000 ***
Step 7
Eject the CD by entering the following commands:
# cd /
# eject
Step 8
Reboot the machine by entering the following command:
# init 6
This completes the Solaris operating system and patch installation. Proceed to “Installing the Alarm
Software” section on page 8-20.
Installing the Alarm Software
The driver for the alarm software is not part of the standard Solaris installation. It must be installed
separately, according to the following procedure. If you are installing Solaris on a Netra t 1400/1405 or
t 100/105 platform, proceed to “Installing Lights Out Management Software” section on page 8-21 for
Lights Out Management software installation. If you are installing Solaris on a Netra t 1120/1125
platform, proceed to “Installing the Alarm Card Software for Netra t 1120/1125” section on page 8-23
for alarm card software installation.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-20
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Alarm Software
Installing Lights Out Management Software
To install Lights Out Management software:
Step 1
Load the Cisco MGC Solaris Patches CD into the CD-ROM drive. Install the Lights out Management
software by entering the following commands at the # prompt:
# cd /var/tmp
# tar xvf /cdrom/cdrom0/lomsw.tar
# pkgadd -d . SUNWlomm SUNWlomr SUNWlomu
A screen similar to the following is displayed, along with copyright and trademark information:
Processing package instance <SUNWlomm> from </cdrom/netra_t_server_lom/Product>
LOMlite manual pages
(sparc.sun4u) 1.1.0,REV=1999.10.20.13.34
Copyright 1999 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Copyright 1999 Sun Microsystems Inc. Tous droits reserves.
Fabrique aux Etats-Unis, 2550 Garcia Avenue, Mountain View, Californie
94043-1100 USA
The Lights Out Management Manual Pages will be installed at this time, followed by the LOMlite driver.
A screen similar to the following is displayed:
Using </> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
/etc <attribute change only>
Do you want to install these conflicting files [y,n,?,q]
Step 2
Select y and press Enter to install all the packages.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWlomr> [y,n,?]
Step 3
Select y and press Enter to continue.
A screen similar to the following is displayed:
Installing LOMlite driver as <SUNWlomr>
## Installing part 1 of 1.
/etc/init.d/lomlited
/etc/init.d/tsaldog
/kernel/drv/lom.conf
/kernel/drv/sparcv9/lom
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-21
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Alarm Software
[ verifying class <none> ]
/etc/rc0.d/K80tsaldog <linked pathname>
/etc/rc2.d/S25tsaldog <linked pathname>
/etc/rc2.d/S75lomlited <linked pathname>
i.drivers: INFO: Starting ...
i.drivers: Adding /cdrom/netra_t_server_lom/Product/SUNWlomr/reloc/kernel/drv/lom
Identified drivers: lom
i.drivers: Installing drivers ...
Driver: lom ... devlinks ... add_drv(1M) ...
i.drivers: Finished
[ verifying class <drivers> ]
…
The LOMlite Utilities will then install followed by its copyright and trademark
information.
LOMlite Utilities
(sparc.sun4u) 1.1.0,REV=1999.10.20.13.34
Copyright 1999 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Copyright 1999 Sun Microsystems Inc. Tous droits reserves.
Fabrique aux Etats-Unis, 2550 Garcia Avenue, Mountain View, Californie
94043-1100 USA
…
Using </> as the package base directory.
## Processing package information.
## Processing system information.
16 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
Installing LOMlite Utilities as <SUNWlomu>
## Installing part 1 of 1.
/etc/lomlited.conf
/usr/include/lom_io.h
/usr/include/tsalarm_io.h
/usr/lib/locale/de/LC_MESSAGES/lom.cat
/usr/lib/locale/de/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/es/LC_MESSAGES/lom.cat
/usr/lib/locale/es/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/fr/LC_MESSAGES/lom.cat
/usr/lib/locale/fr/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/it/LC_MESSAGES/lom.cat
/usr/lib/locale/it/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/ko/LC_MESSAGES/lom.cat
/usr/lib/locale/ko/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/sv/LC_MESSAGES/lom.cat
/usr/lib/locale/sv/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/zh/LC_MESSAGES/lom.cat
/usr/lib/locale/zh/LC_MESSAGES/tsalarm.cat
/usr/lib/locale/zh_TW/LC_MESSAGES/lom.cat
/usr/lib/locale/zh_TW/LC_MESSAGES/tsalarm.cat
/usr/sbin/258-7691-15.hex
/usr/sbin/lomctl
/usr/sbin/lominfo
/usr/sbin/lomlited
/usr/sbin/lomprog
/usr/sbin/tsctl
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-22
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Alarm Software
/usr/sbin/tsdog
/usr/sbin/tsmonitor
/usr/sbin/tsstate
/usr/sbin/tsunlock
[ verifying class <none> ]
Installation of <SUNWlomu> was successful.
Step 4
Eject the CD by entering the following commands:
# cd /
# eject
This completes the installation of the Lights Out Management sofware. Proceed to the following:
•
If your target machine will be using a Serial Asynchronous Interface Port (SAIP) Card, proceed to
the “PCI Card Configuration” section on page 8-25.
•
If your target machine is using a second Ethernet interface, proceed to the “Configuring a Second
Ethernet Interface” section on page 8-26.
•
If your target machine is not using either of the above options, proceed to the “Configuring a Second
Disk Drive” section on page 8-27.
Installing the Alarm Card Software for Netra t 1120/1125
To install the Alarm Card software:
Step 1
Load the Netra t 11xx CD into the CD-ROM drive, log in as root and enter the following commands:
# cd /cdrom/cdrom0
# pkgadd -d .
A screen similar to the following is displayed:
The following packages are available:
1 SUNWtsalm
TS91 Alarm and Monitor Manpages
(sparc.sun4u) 1.0,REV=1.1
2 SUNWtsalr
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.0,REV=1.1
3 SUNWtsalu
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.0,REV=1.1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to install all the packages.
A screen similar to the following is displayed:
Processing package instance <SUNWtsalm from </cdrom/netrat_11xx_1_0
TS91 Alarm and Monitor Manpages
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Copyright 1997 Sun Microsystems Inc. Tous droits reserves.
Fabrique aux Etats-Unis, 2550 Garcia Avenue, Mountain View, Californie 94043-1100 USA
...
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-23
Chapter 8
Sun Solaris 2.6 Operating System Installation
Installing the Alarm Software
Installing TS91 Alarm and Monitor Manpages as <SUNWtsalm
...
Installation of <SUNWtsalm was successful.
Processing package instance <SUNWtsalr from </cdrom/netrat_11xx_1_0
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
Do you want to continue with the installation of <SUNWtsalr [y,n,?]
Step 3
Enter y to continue the installation.
A screen similar to the following is displayed:
Installing TS91 Alarm and Monitor driver as <SUNWtsalr
...
Installation of <SUNWtsalr was successful.
Processing package instance <SUNWtsalu from </cdrom/netrat_11xx_1_0
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.0,REV=1.1
Copyright 1997 Sun Microsystems, Inc. All Rights Reserved.
Manufactured in the United States of America.
2550 Garcia Avenue, Mountain View, California, 94043-1100 U.S.A.
...
Installation of <SUNWtsalu was successful.
The following packages are available:
1 SUNWtsalm
TS91 Alarm and Monitor Manpages
(sparc.sun4u) 1.0,REV=1.1
2 SUNWtsalr
TS91 Alarm and Monitor driver
(sparc.sun4u) 1.0,REV=1.1
3 SUNWtsalu
TS91 Alarm and Monitor Utilities
(sparc.sun4u) 1.0,REV=1.1
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 4
Enter q to quit the installation when it is finished.
Step 5
Eject the CD from the CD-ROM drive.
# cd /
# eject
This completes the installation of the Alarm Card sofware. Proceed to the following:
•
If your target machine will be using a Serial Asynchronous Interface Port (SAIP) Card, proceed to
the “PCI Card Configuration” section on page 8-25.
•
If your target machine is using a second Ethernet interface, proceed to the “Configuring a Second
Ethernet Interface” section on page 8-26.
•
If your target machine is not using either of the above options, proceed to the “Configuring a Second
Disk Drive” section on page 8-27.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-24
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
PCI Card Configuration
PCI Card Configuration
If the target machine will be using a Serial Asynchronous Interface Port (SAIP) Card, do the following
procedure to install the SAIP drivers:
Step 1
Load the SAI/P CD into the CD-ROM drive. Enter the following commands at the # prompt to install
the SAI/P software:
# cd /cdrom/cdrom0/saip_2.0_u1/Solaris_2.6/Packages
# pkgadd -d .
A screen similar to the following is displayed, along with copyright and trademark information:
The following packages are available:
1 SUNWsaip
Serial Asynchronous Interface Driver (PCI)
(sparc) 2.0,REV=1998.10.19
2 SUNWsaipu
Serial Asynchronous Interface Utilities (PCI)
(sparc) 2.0,REV=1998.10.19
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to install all the packages.
A screen similar to the following is displayed:
Processing package instance <SUNWsaip> from
</cdrom/sun_saip/saip_2.0_u1/Solaris_7/Packages>
Serial Asynchronous Interface Driver (PCI)
(sparc) 2.0,REV=1998.10.19
Copyright 1998 Sun Microsystems, Inc. All rights reserved.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWsaip> [y,n,?] y
Step 3
Select y and press Enter to continue.
A screen similar to the following is displayed:
Installing Serial Asynchronous Interface Driver (PCI) as <SUNWsaip>
## Installing part 1 of 1.
/etc/init.d/saip
/etc/opt/SUNWconn/bin/saipconfig <symbolic link>
/etc/opt/SUNWconn/bin/saipd <symbolic link>
/etc/opt/SUNWconn/saip/bin/saipconfig
.
.
.
Installation of <SUNWsaipu> was successful.
The following packages are available:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-25
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Ethernet Interface
1
SUNWsaip
2
SUNWsaipu
Serial Asynchronous Interface Driver (PCI)
(sparc) 2.0,REV=1998.10.19
Serial Asynchronous Interface Utilities (PCI)
(sparc) 2.0,REV=1998.10.19
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: q
Step 4 Select q and press Enter to quit the installation when it has finished.
Step 4
Enter the following commands to eject the CD from the CD-ROM drive:
# cd /
# eject
Step 5
Reboot the system by using the -r function.
# reboot -- -r
PCI card configuation is now complete. If you have a second Ethernet interface, proceed to the
“Configuring a Second Ethernet Interface” section on page 8-26. Otherwise, go to the “Configuring a
Second Disk Drive” section on page 8-27
Configuring a Second Ethernet Interface
A second Ethernet interface is optional to the base configuration and must be configured separately. To
configure a second Ethernet interface:
Step 1
Enter the following command to add the IP address and hostname of the second Ethernet interface to the
/etc/hosts file:
# echo IP address of hme1
Step 2
hostname of hme1 >> /etc/hosts
Enter the following command to create a new file named /etc/hostname.hme1. Place the hostname for
the second Ethernet interface on the first and only line.
# echo hme1 hostname > /etc/hostname.hme1
Step 3
If the IP address of the second Ethernet interface is on a network that is different from the first Ethernet
interface and this network has a subnet mask, edit the file /etc/netmasks to add the netmask for the new
network. Follow the example in the header of the file.
Step 4
To complete the configuration, you must now reboot the machine by using the -r option. Enter the
following comand:
# reboot -- -r
Step 5
When the machine finishes rebooting, log in as root and enter the command ifconfig -a. Verify that the
new interface, hme1, appears in the output.
# ifconfig -a
Text similar to the following is displayed.
Note
The IP addresses are for demonstration purposes only. Actual addresses will differ in each
application.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-26
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 172.24.235.53 netmask ffffff00 broadcast 172.24.235.255
ether 8:0:20:9a:76:6c
hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 172.24.237.53 netmask ffffff00 broadcast 172.24.237.255
ether 8:0:20:9a:76:6c
This completes the configuration of a second Ethernet interface. Proceed to “Configuring a Second Disk
Drive” section on page 8-27.
Configuring a Second Disk Drive
There are three options at this stage of the installation process:
•
If there is no second disk drive, the installation is complete; you should stop here and move on to
installing the Cisco MGC software.
•
If there is a second disk drive, it can be used as a mirror of the first to increase the availability of
the system. Go to the section “Installing the Sun StorEdge Volume Manager 2.6”, below, for
installation procedures.
•
Or a second disk drive can be used as log and spool disk to off-load tasks from the first disk. This
will increase the performance of the machine. Go to “Installing Log and Spool File Systems” section
on page 8-48 for installation procedures.
Installing the Sun StorEdge Volume Manager 2.6
Follow the procedures for installing the Volume Manager only if you wish to mirror the boot disk onto
a second disk drive, instead of using it for the log and spool file systems. Use the procedures in this
section to install the Sun StorEdge 2.6 Volume Manager software, encapsulate, and mirror the hard
drives.
Caution
Step 1
If you are planning to run mgcrestore, make sure you are installing the same version of Volume
Manager that was installed on your system when mgcbackup was run. Or, if Volume Manager was not
installed on your system when mgcbackup was run, you must first run mgcrestore before installing
Volume Manager.
Load the Cisco MGC Solaris Patches CD into the CD-ROM drive. Enter the following command to
install the Solaris 2.6 operating system patches:
# pkgadd -d /cdrom/cdrom0/CSCOh006.pkg
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh006
Virtual Switch Controller Volume Manager 2.6 package installation and
patches
(sparc) TJB_ELAN_2000_01_04_23_16_GMT
Select package(s) you wish to process (or 'all' to process
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-27
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to accept the default response of all.
A screen similar to the following is displayed:
Processing package instance <CSCOh006> from </var/tmp/CSCOh006.pkg>
Virtual Switch Controller Volume Manager 2.6 package installation and patches
(sparc) TJB_ELAN_2000_01_04_23_16_GMT
Cisco System, Inc.
The selected base directory </opt/sun_install> must exist before installation is
attempted.
Do you want this directory created now [y,n,?,q]
Step 3
Select y and press Enter to create this directory.
A screen similar to the following is displayed:
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
* /opt/sun_install <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q]
Step 4
Select y and press Enter to continue installation.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh006> [y,n,?]
Step 5
Select y and press Enter to continue installation.
A screen similar to the following is displayed:
Installing Virtual Switch Controller Volume Manager 2.6 package installation and patches
as <CSCOh006>
## Executing preinstall script.
Platform is SUNW,Ultra-80
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/installVM
/opt/sun_install/install_rootdg
/opt/sun_install/install_vscdg
/opt/sun_install/removeVM
/opt/sun_install/remove_rootdg
/opt/sun_install/remove_vscdg
/var/tmp/106606-04.tar.Z
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-28
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
[ verifying class <none> ]
## Executing postinstall script.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!
!! You must now change directories to /opt/sun_install and
!!
!! run the installVM script as root.
!!
!!
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installation of <CSCOh006> was successful.
Step 6
Change directories to /opt/sun_install, eject the CD and run the VM script by entering the following
commands at the # prompt. If the installation was performed using an nfs mount then disregard the eject
command below.
# cd /opt/sun_install
# eject
# ./installVM
A screen similar to the following is displayed:
Install the "Sun StorEdge Volume Manager 2.6 Software" CD into the CD-ROM drive
Press Enter when ready
Step 7
Press Enter to continue the installation.
A screen similar to the following is displayed:
Sun StorEdge Volume Manager
(sparc) 2.6,REV=2.5.3
Copyright 1998 Sun Microsystems, Inc. All rights reserved.
Copyright (c) 1990-1997 VERITAS Software Corporation.
ALL RIGHTS RESERVED.
THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE,
AND/OR ITS SUPPLIERS.
## Processing package information.
## Processing system information.
10 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
/etc <attribute change only>
Do you want to install these conflicting files [y,n,?,q]
Step 8
Select y and press Enter to continue the installation.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
The following files are being installed with setuid and/or setgid
permissions:
/usr/sbin/vxprint <setuid root>
Do you want to install these as setuid/setgid files [y,n,?,q]
Step 9
Select y and press Enter to continue the installation.
A screen similar to the following is displayed:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-29
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWvxvm> [y,n,?]
Step 10
Select y and press Enter to continue the installation.
A screen similar to the following is displayed:
Copyright (c) 1990-1997 VERITAS Software Corporation.
ALL RIGHTS RESERVED.
THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE,
AND/OR ITS SUPPLIERS.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWvxva> [y,n,?]
Step 11
Select y and press Enter to continue installation.
A screen similar to the following is displayed:
Installation of <SUNWvmman> was successful.
Ejecting CDROM
Changed to /var/tmp directory
Uncompressing 106606-04 ...
Extracting 106606-04 ...
Extraction of patch 106606-04 successful
Installing 106606-04 ...
Create vxassist file
Create vxaltstale file
Edit S95vxvm-recover script
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! The system must be rebooted before running 'vxinstall' !!
!! as root to continue the Volume Manager installation.
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Do you want to reboot now (y/n)?
Step 12
Select y and press Enter to reboot.
A screen similar to the following is displayed:
REBOOTING
#
INIT: New run level: 6
The system is coming down. Please wait.
System services are now being stopped.
Print services stopped.
Stopping the syslog service.
syslogd: going down on signal 15
Jan 6 12:56:21 snmpdx: received signal 15
The system is down.
Step 13
When the reboot is complete, log in as root and boot to the # prompt.
Step 14
Enter the following command at the # prompt:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-30
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
# vxinstall
A screen similar to the following is displayed:
VxVM uses license keys to control access. If you have a SPARCstorage
Array (SSA) controller or a Sun Enterprise Network Array (SENA) controller
attached to your system, then VxVM will grant you a limited use license
automatically. The SSA and/or SENA license grants you unrestricted use
of disks attached to an SSA or SENA controller, but disallows striping
and RAID-5 on non-SSA and non-SENA disks. If you are not running a
SPARCstorage Array controller, or a Sun Enterprise Network Array controller, then you must
obtain a license key to operate.
Licensing information:
System host ID: ##?#?###
Host type: SUNW,Ultra-80
SPARCstorage Array or Sun Enterprise Network Array: No arrays found (license is required)
Some licenses are already installed. Do you wish to review them
[y,n,q,?] (default: y) n
Step 15
Type n and press Enter.
A screen similar to the following is displayed:
Do you wish to enter another license key [y,n,q,?] (default: n) y
Step 16
Type y and press Enter to enter the license key.
A screen similar to the following is displayed:
Please enter your key:
Step 17
Type the key number, with spaces, and press Enter.
A screen similar to the following is displayed:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
Feature name: CURRSET [95]
Number of licenses: 1 (non-floating)
Expiration date: Sun Jun 04 04:00:00 2006 (2340.6 days from now)
Release Level: 20
Machine Class: All
Key successfully installed in /etc/vx/elm/95.
Do you wish to enter another license key [y,n,q,?] (default: n)
Note
Step 18
When you receive the Sun StorEdgeVolume Manager key you will also get a RAID5 key. This
key is included in the package from Sun but is not required for the installation.
Press Enter to accept the default answer no.
A screen similar to the following is displayed:
Volume Manager Installation
Menu: VolumeManager/Install
The Volume Manager names disks on your system using the controller
and disk number of the disk, substituting them into the following
pattern:
c<controller>t<disk>d<disk>
If the Multipathing driver is installed on the system then for the
disk devices with multiple access paths, the controller number
represents a multipath pseudo controller number. For example, if a
disk has 2 paths from controllers c0 and c1, then the Volume Manager
displays only one of them such as c0 to represent both the
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-31
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
controllers.
Some examples would be:
c0t0d0
c1t0d0
c1t1d0
- first controller, first target, first disk
- second controller, first target, first disk
- second controller, second target, first disk
The Volume Manager has detected the following controllers on your system:
c0:
Hit RETURN to continue.
Step 19
Press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Installation
Menu: VolumeManager/Install
You will now be asked if you wish to use Quick Installation or
Custom Installation. Custom Installation allows you to select how
the Volume Manager will handle the installation of each disk
attached to your system.
Quick Installation examines each disk attached to your system and
attempts to create volumes to cover all disk partitions that might
be used for file systems or for other similar purposes.
If you do not wish to use some disks with the Volume Manager, or if
you wish to reinitialize some disks, use the Custom Installation
option Otherwise, we suggest that you use the Quick Installation
option.
Hit RETURN to continue.
Step 20
Press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Installation Options
Menu: VolumeManager/Install
1
2
Quick Installation
Custom Installation
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform:
Step 21
Select 2 and press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The c0t0d0 disk is your Boot Disk. You can not add it as a new
disk. If you encapsulate it, you will make your root filesystem
and other system areas on the Boot Disk into volumes. This is
required if you wish to mirror your root filesystem or system
swap area.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-32
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Encapsulate Boot Disk [y,n,q,?] (default: n)
Step 22
Select y and press Enter to continue.
A screen similar to the following is displayed:
Enter disk name for c0t0d0 [<name>,q,?] (default: rootdisk)
Step 23
Type rootdiska and press Enter to continue.
A screen similar to the following is displayed:
The c0t0d0 disk has been configured for encapsulation.
Hit RETURN to continue.
Step 24
Press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom/c0
Generating list of attached disks on c0....
<excluding root disk c0t0d0
The Volume Manager has detected the following disks on controller c0:
c0t1d0
Hit RETURN to continue.
Step 25
Press Enter to continue.
A screen similar to the following is displayed:
Installation options for controller c0
Menu: VolumeManager/Install/Custom/c0
1
2
3
4
Install all
Install all
Install one
Leave these
disks as pre-existing disks. (encapsulate)
disks as new disks. (discards data on disks!)
disk at a time.
disks alone.
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform:
Step 26
Select 4 to leave the disks alone and press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The following is a summary of your choices.
c0t0d0
Encapsulate
Is this correct [y,n,q,?] (default: y)
Step 27
Press Enter to accept the default answer, yes and continue. The system now must be shut down and
rebooted in order to continue the reconfiguration.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-33
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
A screen similar to the following is displayed:
Shutdown and reboot now [y,n,q,?] (default: n)
Step 28
Select y and press Enter to shut down and reboot the system. Wait for the computer to shut down and
reboot twice, then proceed to the next section.
Step 29
Once the system has rebooted twice, at the # prompt, log in as root and run the install_rootdg script as
shown below:
Note
This process takes approximately 28 minutes to run and does not require user intervention.
# cd /opt/sun_install
# ./install_rootdg
The following is displayed.
Determine the device names for the disks
Platform is SUNW,Ultra-60
A-DSK0: c0t0d0
B-DSK0: c0t1d0
Initialize device c0t1d0
Succeeded
Add rootdiskb to rootdg, device is c0t1d0
Succeeded
Mirror all the volumes of A-DSK0 to B-DKS0 and make root
bootable
Mirroring root to rootdiskb
Success
Mirroring var to rootdiskb
Success
Mirroring opt to rootdiskb
Success
Mirroring swap to rootdiskb
Success
Mirroring usr to rootdiskb
Success
Step 30
Edit the /etc/init.d/sysetup file to enable a core dump. These lines are located at the end of the file.
Remove the comment symbol (#) from the beginning of the lines. The completed edit should be the same
as shown below.
# Default is to not do a savecore
#
if [ ! -d /var/crash/`uname -n` ]
then mkdir -m 0700 -p /var/crash/`uname -n`
fi
echo 'checking for crash dump...\c '
savecore /var/crash/`uname -n`
echo ''
Step 31
Re-install the CSCOh007 package to install Volume Manager 2.6 patch 106606-04. See “Installing the
Solaris 2.6 Patch Cluster on Netra t 1120/1125, t 1400/1405 and t 100/105” section on page 8-16.
Step 32
At the # prompt, type init 6 and press Enter to reboot the system.
# init 6
This completes the Operation System installation process.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-34
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Note
After the installation of the Sun Storedge Volume Manager Software, you will receive the following
error messages during the boot process:
WARNING: forceload of drv/scsi failed
WARNING: forceload of drv/ssd failed
WARNING: forceload of drv/sf failed
WARNING: forceload of drv/pln failed
WARNING: forceload of drv/soc failed
WARNING: forceload of drv/socal failed
These error messages are acceptable and will not affect the operation of the MGC application.
Removing the Sun StorEdge Volume Manager 2.6
To remove Volume Manager:
Step 1
Load the CD containing the CISCO patch packages into the CD-ROM drive. Install the CSCOh000.pkg
package by entering the following commands:
# pkgadd -d /cdrom/cdrom0/CSCOh000.pkg
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh000
Media Gateway Controller Volume Manager 3.1 package installation and
patches
(sparc) 1.0(3)A
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to accept the default response of all.
A screen similar to the following is displayed:
Processing package instance <CSCOh000> from </tftpboot/CiscoMGC_Install/CSCOh000.pkg>
Media Gateway Controller Volume Manager 3.1 package installation and patches
(sparc) 1.0(3)A
Cisco System, Inc.
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
* /opt/sun_install/pkg_admin
* /opt/sun_install/rm_Veritas2.6
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q] y
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-35
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Step 3
Select y and press Enter to create this directory.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh000> [y,n,?] y
Step 4
Select y and press Enter to continue the installation.
A screen similar to the following is displayed:
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh006> [y,n,?]
Step 5
Select y and press Enter to continue the installation.
A screen similar to the following is displayed:
Installing Media Gateway Controller Volume Manager 3.1 package installation and patches as
<CSCOh000>
## Executing preinstall script.
Platform is SUNW,Ultra-60
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/installVM3.1
/opt/sun_install/pkg_admin
/opt/sun_install/rm_Veritas2.6
[ verifying class <none> ]
## Executing postinstall script.
Installation of <CSCOh000> was successful.
Step 6
Change directories to /opt/sun_install, eject the CD and run the script to remove Volume Manager 2.6
by entering the following commands at the # prompt. If the installation was performed using an nfs
mount, disregard the eject command below.
# cd /opt/sun_install
# eject
# ./rm_Veritas2.6
A screen similar to the following is displayed:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!
!!
This script will completely remove
!!
!!
Sun StorEdge Volume Manager 2.6 (Veritas 2.6)
!!
!!
from this system
!!
!!
!!
!!
It requires that the machine
!!
!!
be rebooted several times during the procedure.
!!
!!
!!
!! Do you wish to continue? (y/n):
!!
!!
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-36
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Step 7
Select y and press Enter to continue removing Volume Manager 2.6.
A screen similar to the following is displayed:
Removing Sun StorEdge Volume Manager 2.6
This operation will convert the following file systems from
volumes to regular partitions: root swap usr var opt
Replace volume rootvol with c0t0d0s0.
This operation will require a system reboot. If you choose to
continue with this operation, system configuration will be updated
to discontinue use of the volume manager for your root and swap
devices.
Do you wish to do this now [y,n,q,?] (default: y)
Step 8
Select y and press Enter to continue.
A screen similar to the following is displayed:
Restoring kernel configuration...
A shutdown is now required to install the new kernel.
You can choose to shutdown now, or you can shutdown later, at your
convenience.
Do you wish to shutdown now [y,n,q,?] (default: n) y
Step 9
Select y and press Enter to shut down and reboot the system.
A screen similar to the following is displayed:
shutdown -g0 -y -i6
Shutdown started.
Tue Mar
6 17:22:23 EST 2001
During the reboot sequence the following warning will be displayed:
VxVM general startup...
Volume Manager: Removing c0t0d0 from Volume Manager control.
vxvm:vxdg: ERROR: disassociating disk-media rootdiska:
Cannot remove last disk in disk group
The removal of rootdiska from rootdg failed. It will be marked as
reserved so no space from it is accidentally allocated
This message can be ignored. After this process has been completed it will not be
displayed again.
Step 10
When the system has completed rebooting, log in as root and remove the Sun StorEdge Volume
Manager Packages by entering the following commands:
# cd /opt/sun_install
# pkgrm -a pkg_admin -n SUNWvmman SUNWvxva SUNWvxvm
A screen similar to the following is displayed:
Removal of <SUNWvmman> was successful.
Removal of <SUNWvxva> was successful.
Checking for system volumes:
swap
...
Stopping vxconfigd...
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-37
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Unloading vxspec driver...
Removing //kernel/drv/vxspec
Unloading vxio driver...
Removing //kernel/drv/vxio
Unloading vxdmp driver...
Removing //kernel/drv/vxdmp
Removing changes to //etc/devlink.tab...
Removing changes to //etc/system...
Removing files under /var/vxvm...
Removing vxconfigd...
Removing files under //etc/vx...
Removal of <SUNWvxvm> was successful.
This completes the Solaris Operating System installation process.
Note
After the removal of the Sun Storedge Volume Manager Software, you will receive the following error
messages during the boot process:
WARNING: forceload of drv/scsi failed
WARNING: forceload of drv/ssd failed
WARNING: forceload of drv/sf failed
WARNING: forceload of drv/pln failed
WARNING: forceload of drv/soc failed
WARNING: forceload of drv/socal failed
This error message is acceptable and will not affect the operation of the MGC application. These error
messages can be removed by editing the /etc/system file and removing the lines at the end of the file that
begin with "forceload: drv/…"
Installing Veritas Volume Manager 3.1
Perform the procedures in this section only if you wish to mirror the boot disk onto the second disk drive
instead of using it for the Log and Spool file systems. Use the procedures in this section to install the
Sun StorEdge 2.6 Volume Manager software, encapsulate, and mirror the hard drives.
Caution
Note
Step 1
If you are planning to run mgcrestore, make sure you are installing the same version of Volume
Manager that was installed on your system when mgcbackup was run. Or, if Volume Manager was not
installed on your system when mgcbackup was run, you must first run mgcrestore before installing
Volume Manager.
If you have not already loaded package CSCOh000.pkg from the previous section, then do so by
following Step 1. Otherwise, start this procedure with Step 4.
Load the Cisco MGC Solaris Patches CD into the CD-ROM drive. Install the Solaris 2.6 operating
system patches by entering the following commands:
# pkgadd -d /cdrom/cdrom0/CSCOh000.pkg
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-38
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
A screen similar to the following is displayed:
The following packages are available:
1 CSCOh000
Media Gateway Controller Volume Manager 3.1 package installation and
patches
(sparc) 1.0(3)A
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Step 2
Press Enter to accept the default response of all.
A screen similar to the following is displayed:
Processing package instance <CSCOh000> from </tftpboot/CiscoMGC_Install/CSCOh000.pkg>
Media Gateway Controller Volume Manager 3.1 package installation and patches
(sparc) 1.0(3)A
Cisco System, Inc.
Using </opt/sun_install> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh000> [y,n,?] y
Step 3
Select y and press Enter to have this directory created.
A screen similar to the following is displayed:
Installing Media Gateway Controller Volume Manager 3.1 package installation and patches as
<CSCOh000>
## Executing preinstall script.
Platform is SUNW,Ultra-60
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/installVM3.1
/opt/sun_install/pkg_admin
/opt/sun_install/rm_Veritas2.6
[ verifying class <none> ]
## Executing postinstall script.
Installation of <CSCOh000> was successful.
Step 4
Change directories to /opt/sun_install, eject the CD and run the installVM3.1 script by entering the
following commands at the # prompt. If the installation was performed using an nfs mount, disregard
the eject command below.
# cd /opt/sun_install
# eject
# ./installVM3.1
The following screen is displayed:
Install the "Foundation Products 2000-08 for Solaris" CD into the CD-ROM driver
Press Enter when ready
Step 5
Press Enter to continue the installation.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-39
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
A screen similar to the following is displayed:
Changing directories to /cdrom/cdrom0/Solaris_2_6/pkgs
Current directory /cdrom/foundation_products_2000_08_sun/Solaris_2_6/pkgs
Installing Volume Manager Packages
Processing package instance <VRTSvxvm> from
</cdrom/foundation_products_2000_08_sun/Solaris_2_6/pkgs>
VERITAS Volume Manager, Binaries
(sparc) 3.1,REV=07.21.2000.07.59
Copyright (c) 1990-2000 VERITAS Software Corporation.
ALL RIGHTS RESERVED.
THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE,
AND/OR ITS SUPPLIERS.
This package, VxVM 3.1, is supported on Solaris 2.6, 7,
and 8. You appear to be running Solaris 2.6. Press
ENTER to install VxVM 3.1 for Solaris 2.6, or enter
another Solaris version number if you are certain that you
want to install the drivers for a different release of
Solaris.
Install for which version of Solaris?
[8, 7, 2.6] (default: 2.6):
Step 6
Press Enter to accept the default answer, Solaris 2.6, and continue the installation.
A screen similar to the following is displayed:
Installing VxVM for Solaris 2.6
The following Sun patch(s) are required for Solaris 2.6.
Sun patch(s):
105223
105357
Continue installation? [y,n,q,?] (default: n): y
Step 7
These patches are already installed on the system. Select y and press Enter to continue installation. After
a long list of files are installed for the VRTSvxvm package, the following screen is displayed:
## Executing postinstall script.
Installation of <VRTSvxvm> was successful.
Processing package instance <VRTSvmsa> from
</cdrom/foundation_products_2000_08_sun/Solaris_2_6/pkgs>
VERITAS Volume Manager Storage Administrator
(sparc) 3.1,REV=07.26.2000.17.55
Copyright (c) 2000 VERITAS Software Corporation.
ALL RIGHTS RESERVED.
THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE,
AND/OR ITS SUPPLIERS.
Where should this package be installed? (default: /opt]) [?,q]
Step 8
Press Enter to accept the default answer, /opt, and continue the installation. The following lines are
appended to the display:
Should the Volume Manager Storage Administrator Server be installed on this
system?
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-40
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
(The Volume Manager Storage Administrator Client will be installed regardless)
(default: y) [y,n,?,q]
Step 9
Select y and press Enter to continue the installation. After another list of files are installed for the
VRTSvmsa package, the following screen is displayed:
## Executing postinstall script.
Installation of <VRTSvmsa> was successful.
Processing package instance <VRTSvmman> from
</cdrom/foundation_products_2000_08_sun/Solaris_2_6/pkgs>
VERITAS Volume Manager, Manual Pages
(sparc) 3.1,REV=07.21.2000.07.59
Copyright (c) 1990-2000 VERITAS Software Corporation.
ALL RIGHTS RESERVED.
THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE,
AND/OR ITS SUPPLIERS.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing VERITAS Volume Manager, Manual Pages as <VRTSvmman>
## Installing part 1 of 1.
/opt/VRTSvxvm/man/man1m/libvxvmsc.3x
/opt/VRTSvxvm/man/man1m/vxapslice.1m
/opt/VRTSvxvm/man/man1m/vxassist.1m
.
.
.
Installation of <VRTSvmman> was successful.
Create vxassist file
Create vxaltstale file
Edit S95vxvm-recover script
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!
!! The system must be rebooted before running vxinstall
!!
!! as root to continue the Volume Manager installation.
!!
!!
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Do you want to reboot now (y/n)?y
Step 10
Select y and press Enter to reboot. After another list of files are installed for the VRTSvmsa package,
the following screen is displayed:
REBOOTING
Remember to remove your Volume Manager CD from the CD-ROM drive
INIT: New run level: 6
The system is coming down.
Please wait.
You can now remove the Veritas CD from the CD-ROM.
Step 11
When the reboot is complete, log in as root and boot the system at the # prompt.
Enter the following command at the # prompt:
# vxinstall
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-41
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
VxVM uses license keys to control access. If you have a SPARCstorage
Array (SSA) controller or a Sun Enterprise Network Array (SENA) controller
attached to your system, then VxVM will grant you a limited use license
automatically. The SSA and/or SENA license grants you unrestricted use
of disks attached to an SSA or SENA controller, but disallows striping,
RAID-5, and DMP on non-SSA and non-SENA disks. If you are not running an
SSA or SENA controller, then you must obtain a license key to operate.
Licensing information:
System host ID: 80b7fc9b
Host type: SUNW,Ultra-60
SPARCstorage Array or Sun Enterprise Network Array: No arrays found
No valid licenses found.
Are you prepared to enter a license key [y,n,q,?] (default: y) y
Note: If you are upgrading from Veritas 2.6 the system will recognize your existing key
and ask if you wish to review them. If you are not upgrading you must enter your license
here.
Step 12
Press Enter to accept the default answer yes. The following screen is displayed:
Please enter your key:
Step 13
Type the key number, with spaces, and press Enter.
A screen similar to the following is displayed:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
vrts:vxlicense:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
Feature name: VxVM [95]
Number of licenses: 1 (non-floating)
Expiration date: Sun Jun 04 04:00:00 2006 (1914.7 days from now)
Release Level: 20
Machine Class: All
Key successfully installed in /etc/vx/elm/95.
Do you wish to enter another license key [y,n,q,?] (default: n)
Note
Step 14
When you receive the Sun StorEdgeVolume Manager key you will also get a RAID5 key. This
key is included in the package from Sun but is not required for the installation.
Press Enter to accept the default answer no.
A screen similar to the following is displayed:
Generating list of attached controllers....
Volume Manager Installation
Menu: VolumeManager/Install
The Volume Manager names disks on your system using the controller
and disk number of the disk, substituting them into the following
pattern:
c<controller>t<disk>d<disk>
If the Multipathing driver is installed on the system then for the
disk devices with multiple access paths, the controller number
represents a multipath pseudo controller number. For example, if a
disk has 2 paths from controllers c0 and c1, then the Volume Manager
displays only one of them such as c0 to represent both the
controllers.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-42
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Some examples would be:
c0t0d0
c1t0d0
c1t1d0
- first controller, first target, first disk
- second controller, first target, first disk
- second controller, second target, first disk
The Volume Manager has detected the following controllers on your system:
c0:
Hit RETURN to continue.
Step 15
Press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Installation
Menu: VolumeManager/Install
You will now be asked if you wish to use Quick Installation or
Custom Installation. Custom Installation allows you to select how
the Volume Manager will handle the installation of each disk
attached to your system.
Quick Installation examines each disk attached to your system and
attempts to create volumes to cover all disk partitions that might
be used for file systems or for other similar purposes.
If you do not wish to use some disks with the Volume Manager, or if
you wish to reinitialize some disks, use the Custom Installation
option Otherwise, we suggest that you use the Quick Installation
option.
Hit RETURN to continue.
Step 16
Press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Installation Options
Menu: VolumeManager/Install
1
2
Quick Installation
Custom Installation
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform: 2
Step 17
Select 2 and press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The c0t0d0 disk is your Boot Disk. You can not add it as a new
disk. If you encapsulate it, you will make your root file system
and other system areas on the Boot Disk into volumes. This is
required if you wish to mirror your root file system or system
swap area.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-43
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Encapsulate Boot Disk [y,n,q,?] (default: n) y
Step 18
Select y and press Enter to continue.
A screen similar to the following is displayed:
Enter disk name for
Step 19
[<name>,q,?] (default: rootdisk) rootdiska
Type rootdiska and press Enter to continue.
A screen similar to the following is displayed:
The c0t0d0 disk has been configured for encapsulation.
Hit RETURN to continue.
Step 22 Press Enter to continue. The following screen will be displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom/c0
Generating list of attached disks on c0....
<excluding root disk c0t0d0>
The Volume Manager has detected the following disks on controller c0:
c0t1d0
Hit RETURN to continue.
Press Enter to continue. The following screen is displayed:
Installation options for controller c0
Menu: VolumeManager/Install/Custom/c0
1
2
3
4
Install all
Install all
Install one
Leave these
disks as pre-existing disks. (encapsulate)
disks as new disks. (discards data on disks!)
disk at a time.
disks alone.
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform: 4
Step 20
Select 4 to leave the disks alone and press Enter to continue.
A screen similar to the following is displayed:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The following is a summary of your choices.
c0t0d0
Encapsulate
Is this correct [y,n,q,?] (default: y)
Step 21
Press Enter to accept the default answerm yes and continue.
The system must be shut down now and rebooted in order to continue the reconfiguration.
A screen similar to the following is displayed:
Shut down and reboot now [y,n,q,?] (default: n) y
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-44
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Step 22
Select y and press Enter to shut down and reboot the system. Wait for the computer to shut down and
reboot twice, then proceed to the next step.
Step 23
Log in as root at the # prompt and run the install_rootdg script as shown below:
Note
This process takes approximately 28 minutes to run and does not require user intervention.
# cd /opt/sun_install
# ./install_rootdg
A screen similar to the following is displayed:
Determine the device names for the disks
Platform is SUNW,Ultra-60
A-DSK0: c0t0d0
B-DSK0: c0t1d0
Initialize device c0t1d0
Succeeded
Add rootdiskb to rootdg, device is c0t1d0
Succeeded
Mirror all the volumes of A-DSK0 to B-DKS0 and make root
bootable
Mirroring root to rootdiskb
Success
Mirroring var to rootdiskb
Success
Mirroring opt to rootdiskb
Success
Mirroring swap to rootdiskb
Success
Mirroring usr to rootdiskb
Success
Step 24
Edit the /etc/init.d/sysetup file to enable a core dump. These lines are located at the end of the file.
Remove the comment symbol (#) from the beginning of the lines The completed edit should be the same
as shown below.
# Default is to not do a savecore
#
if [ ! -d /var/crash/`uname -n` ]
then mkdir -m 0700 -p /var/crash/`uname -n`
fi
echo 'checking for crash dump...\c '
savecore /var/crash/`uname -n`
echo ''
Step 25
At the # prompt, type init 6 and press Enter to reboot the system.
# init 6
This completes the Sun Storedge Volume Manager Software installation.
Note
After the installation of the Sun Storedge Volume Manager Software you will receive the following error
messages during the boot process:
WARNING: forceload of drv/scsi failed
WARNING: forceload of drv/ssd failed
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-45
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
WARNING: forceload of drv/sf failed
WARNING: forceload of drv/pln failed
WARNING: forceload of drv/soc failedWARNING: forceload of drv/socal failed
These error messages are acceptable and will not affect the operation of the MGC application.
Removing Veritas Volume Manager 3.1
To remove Veritas Volume Manager 3.1:
Step 1
Change directories to /opt/sun_install, eject the CD and run the script to remove Volume Manager 3.1
by entering the following commands at the # prompt.
# cd /opt/sun_install
# eject
# ./rm_Veritas3.1
The following screen is displayed:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!
!!
This script will completely remove
!!
!!
Veritas Volume Manager 3.1 from this system
!!
!!
!!
!!
It requires that the machine
!!
!!
be rebooted several times during the procedure.
!!
!!
!!
!! Do you wish to continue? (y/n):
!!
!!
!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Step 2
Select y and press Enter to continue removing Volume Manager 3.1.
A screen similar to the following is displayed:
Removing Sun StorEdge Volume Manager 3.1
This operation will convert the following file systems from
volumes to regular partitions: root swap usr var opt
Replace volume rootvol with c0t0d0s0.
This operation will require a system reboot. If you choose to
continue with this operation, system configuration will be updated
to discontinue use of the volume manager for your root and swap
devices.
Do you wish to do this now [y,n,q,?] (default: y)
Step 3
Select y and press Enter to continue.
A screen similar to the following is displayed:
Restoring kernel configuration...
A shutdown is now required to install the new kernel.
You can choose to shutdown now, or you can shutdown later, at your
convenience.
Do you wish to shut down now [y,n,q,?] (default: n) y
Step 4
Select y and press Enter to shut down and reboot the system.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-46
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
A screen similar to the following is displayed:
shutdown -g0 -y -i6
Shutdown started.
Tue Mar
6 17:22:23 EST 2001
During the reboot sequence the following warning will be displayed:
VxVM general startup...
Volume Manager: Removing rootdiska from Volume Manager control.
vxvm:vxdg: ERROR: disassociating disk-media rootdiska:
Cannot remove last disk in disk group
The removal of rootdiska from rootdg failed. It will be marked as
reserved so no space from it is accidentally allocated
Note
Step 5
This message can be ignored. After this process is completed, it will not be displayed again.
When the system completes rebooting, log in as root and remove the Sun StorEdge Volume Manager
Packages by entering the following commands:
# cd /opt/sun_install
# pkgrm -a pkg_admin -n VRTSvmman VRTSvmsa VRTSvxvm
A screen similar to the following is displayed:
Removal of <VRTSvmman> was successful.
Attempting to stop vmsa_server
Removing files under /var/opt/vmsa...
Removal of <VRTSvmsa> was successful.
Checking for system volumes:
swap
...
Stopping vxconfigd...
Stopping the host information RPC daemon
Unloading vxspec driver...
Removing //kernel/drv/vxspec
Unloading vxio driver...
Removing //kernel/drv/vxio
Unloading vxdmp driver...
Removing //kernel/drv/vxdmp
Removing changes to //etc/devlink.tab...
Removing changes to //etc/system...
Removing files under /var/vxvm...
Removing vxconfigd...
Removing files under //etc/vx...
Removal of <VRTSvxvm> was successful.
This completes the operating system installation process.
Note
After the removal of the Sun Storedge Volume Manager Software you will still receive the following
error messages during the boot process:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-47
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
WARNING: forceload of drv/scsi failed
WARNING: forceload of drv/ssd failed
WARNING: forceload of drv/sf failed
WARNING: forceload of drv/pln failed
WARNING: forceload of drv/soc failed
WARNING: forceload of drv/socal failed
These error messagse are acceptable and will not affect the operation of the MGC application. They can
be removed by editing the /etc/system file and removing the lines at the end of the file that begin with
"forceload: drv/…"
Installing Log and Spool File Systems
Note
This section applies to the PGW Host only.
Note
If the Cisco MGC software is installed, follow the procedure in the “If the Cisco MGC Software is
Already Installed on the Platform” section on page 8-48 to install the Log and Spool File Systems and
make sure that the Log and Spool data in the directory is backed up. Otherwise, all the data in log and
spool will be lost and no data can be written to the log and spool directory.
The following procedure configures the second disk of a PGW Host for use by the Cisco MGC Software
as storage for log, alarm, measurement, and CDR files. The second disk is divided into two partitions.
The first partition is the log partition and uses 40% of the disk. The second partition is the spool partition
which uses 60% of the disk. Table 8-4 shows a sample partition table for the second disk of a Netra
t 1400 with 36 GB disk drives.
Table 8-4
36 GB Disk 1 Partition Table (PGW with Log and Spool Package)
PGW Host
Slice No.
Slice Name
Slice Size (GB)
0.
0.00
1
0.00
2
overlap
33.92
3
/opt/CiscoMGC/var/log
13.57
4
/opt/CiscoMGC/var/spool
20.35
5
0.00
6
0.00
7
0.00
If the Cisco MGC Software is Already Installed on the Platform
If the Cisco MGC software is already installed on your platform, start Log and Spool software
installation by following the procedures listed below.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-48
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Note
If the Cisco MGC was installed in a base directory other than the default /opt/CiscoMGC, adjust the
following procedures to use the correct base directory.
Note
If the Cisco MGC software is not installed on your platform, you should skip this procedure and begin
Log and Spool installation from the “If the Cisco MGC Software is Not Installed on the Platform”
section on page 8-56.
Step 1
Save the existing log and spool directories. Log in to the platform as root and enter the following
command to stop the Cisco MGC software:
# /etc/init.d/CiscoMGC stop
Step 2
Enter the following commands to rename the existing log and spool directories:
#
#
#
#
Step 3
cd
mv
mv
mv
/opt/CiscoMGC/var
log log.save
log/.*.seq log.save
spool spool.save
Load the Cisco PGW Solaris 2.6 Patch CD into the CD-ROM drive. From the /var/tmp directory of the
target Netra machine, install the Log and Spool Software by entering the following command:
# cd /var/tmp
# pkgadd -d /cdrom/cdrom0/CSCOh005.pkg
The following screen is displayed:
The following packages are available:
1 CSCOh005
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Type package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]
Step 4
Press Enter to accept the default answer all.
The following screen is displayed:
Processing package instance <CSCOh005 from </var/tmp/CSCOh005.pkg
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Cisco System, Inc.
Using </opt/sun_install as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh005> [y,n,?]
Step 5
Type y and press Enter to continue.
The following screen is displayed:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-49
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Installing Media Gateway Controller VSC log and spool package as <CSCOh005>
## Executing preinstall script.
Platform is SUNW,Ultra-80
This is a known platform
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/format_log_spool_start.cmd
/opt/sun_install/install_log_spool
/opt/sun_install/query_2nd_disk.cmd
[ verifying class <none> ]
## Executing postinstall script.
!!
!!
!!
!!
Step 6
You must now change directories to /opt/sun_install and
run the ./install_log_spool script as root.
Change directories to /opt/sun_install and run the install_log_spool script.
# cd /opt/sun_install
# ./install_log_spool
Platform is SUNW,Ultra-80
Searching for disks...done
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
volname
!<cmd>
quit
format> disk
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
set 8-character volume name
execute <cmd>, then return
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@0,0
1. c0t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
Specify disk (enter its number): 1
selecting c0t1d0
[disk formatted]
format> current
Current Disk = c0t1d0
<SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
format> q
2nd Disk device is:
Disk type is:
c0t1d0
SUN36G
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-50
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Number of Cylinders :
24620
Enter absolute path of the desired mount point for the
log directory or press enter to accept
the default [/opt/CiscoMGC/var/log]:
Step 7
Press Enter to accept the default mount point for the log directory, or change it if the Cisco MGC
software was installed in a different location.
The following screen is displayed:
Log directory mount point is /opt/CiscoMGC/var/log
Enter absolute path of the desired mount point for the
spool directory or press enter to accept
the default [/opt/CiscoMGC/var/spool]:
Step 8
Press Enter to accept the default mount point for the spool directory, or change it if the Cisco MGC
software was installed in a different location.
The following screen is displayed:
Spool directory mount point is /opt/CiscoMGC/var/spool
Number of cylinders for log partition: 9848
Start: 0
Start: 9847
Number of cylinders for spool partition: 14772
Start: 9848
Start: 24619
Build partition table for c0t1d0 ...
Searching for disks...done
selecting c0t1d0
[disk formatted]
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> p
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
PARTITION MENU:
0
- change `0' partition
1
- change `1' partition
2
- change `2' partition
3
- change `3' partition
4
- change `4' partition
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-51
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
5
6
7
select
modify
name
print
label
!<cmd>
quit
partition> 0
Part
Tag
0
root
-
change `5' partition
change `6' partition
change `7' partition
select a predefined table
modify a predefined partition table
name the current table
display the current table
write partition map and label to the disk
execute <cmd>, then return
Flag
wm
Cylinders
0 725
Size
1.00GB
Blocks
(726/0/0)
2097414
Enter partition id tag[root]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 1
Part
Tag
Flag
Cylinders
Size
Blocks
1
swap
wu
726 - 3629
4.00GB
(2904/0/0)
8389656
Enter partition id tag[swap]: unassigned
Enter partition permission flags[wu]: wm
Enter new starting cyl[726]: 0
Enter partition size[8389656b, 2904c, 4096.51mb, 4.00gb]: 0c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 0c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
3630 - 23156
26.90GB
0
Blocks
(19527/0/0) 56413503
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[3630]: 0
Enter partition size[56413503b, 19527c, 27545.66mb, 26.90gb]: 0c
partition> 5
Part
Tag
Flag
Cylinders
Size
Blocks
5
var
wm
23157 - 23882
1.00GB
(726/0/0)
2097414
Enter partition id tag[var]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23157]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 6
Part
Tag
Flag
Cylinders
Size
Blocks
6
usr
wm
23883 - 24608
1.00GB
(726/0/0)
2097414
Enter partition id tag[usr]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23883]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 7
Part
Tag
Flag
Cylinders
Size
Blocks
7 unassigned
wm
24609 - 24619
15.52MB
(11/0/0)
31779
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-52
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Enter new starting cyl[24609]: 0
Enter partition size[31779b, 11c, 15.52mb, 0.02gb]: 0c
partition> 2
Part
Tag
Flag
Cylinders
Size
Blocks
2
backup
wm
0 - 24619
33.92GB
(24620/0/0) 71127180
Enter partition id tag[backup]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[71127180b, 24620c, 34730.07mb, 33.92gb]: 24620c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
0
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 9848c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
0
0
0
Blocks
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 9848
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 14772c
partition> p
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part
Tag
0 unassigned
1 unassigned
2 unassigned
3 unassigned
4 unassigned
5 unassigned
6 unassigned
7 unassigned
Flag
wm
wm
wm
wm
wm
wm
wm
wm
Cylinders
0
0
0 - 24619
0 - 9847
9848 - 24619
0
0
0
Size
0
0
33.92GB
13.57GB
20.35GB
0
0
0
Blocks
(0/0/0)
0
(0/0/0)
0
(24620/0/0) 71127180
(9848/0/0) 28450872
(14772/0/0) 42676308
(0/0/0)
0
(0/0/0)
0
(0/0/0)
0
partition> l
partition> q
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> q
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-53
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
unknown disk type, assuming the speed is 10000 rpm
Build log filesystem at /dev/rdsk/c0t1d0s3 ...
mkfs -F ufs /dev/rdsk/c0t1d0s3 28450872 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s3:
28450872 sectors in 9848 cylinders of 27 tracks, 107 sectors
13892.0MB in 308 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552,
1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032,
2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928,
3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408,
3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888,
4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368,
5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264,
6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744,
6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224,
7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704,
8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600,
9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080,
9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560,
10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480,
11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400,
11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736,
12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656,
13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576,
13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496,
14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832,
15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752,
15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672,
16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592,
17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512,
17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848,
18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768,
18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688,
19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608,
20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944,
20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864,
21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784,
22189344, 22281904, 22374464, 22467024, 22559584, 22652144, 22744704,
22837264, 22929824, 23022384, 23114944, 23207504, 23300064, 23392624,
23485184, 23577744, 23666720, 23759280, 23851840, 23944400, 24036960,
24129520, 24222080, 24314640, 24407200, 24499760, 24592320, 24684880,
24777440, 24870000, 24962560, 25055120, 25147680, 25240240, 25332800,
25425360, 25517920, 25610480, 25703040, 25795600, 25888160, 25980720,
26073280, 26165840, 26258400, 26350960, 26443520, 26536080, 26625056,
26717616, 26810176, 26902736, 26995296, 27087856, 27180416, 27272976,
27365536, 27458096, 27550656, 27643216, 27735776, 27828336, 27920896,
28013456, 28106016, 28198576, 28291136, 28383696,
Build spool filesystem at /dev/rdsk/c0t1d0s4 ...
mkfs -F ufs /dev/rdsk/c0t1d0s4 42676308 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s4:
42676308 sectors in 14772 cylinders of 27 tracks, 107 sectors
20838.0MB in 462 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552,
1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032,
2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928,
3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408,
3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888,
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-54
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368,
5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264,
6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744,
6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224,
7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704,
8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600,
9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080,
9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560,
10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480,
11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400,
11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736,
12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656,
13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576,
13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496,
14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832,
15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752,
15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672,
16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592,
17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512,
17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848,
18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768,
18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688,
19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608,
20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944,
20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864,
21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784,
22189344, 22281904, 22374464, 22467024, 22559584, 22652144, 22744704,
22837264, 22929824, 23022384, 23114944, 23207504, 23300064, 23392624,
23485184, 23577744, 23666720, 23759280, 23851840, 23944400, 24036960,
24129520, 24222080, 24314640, 24407200, 24499760, 24592320, 24684880,
24777440, 24870000, 24962560, 25055120, 25147680, 25240240, 25332800,
25425360, 25517920, 25610480, 25703040, 25795600, 25888160, 25980720,
26073280, 26165840, 26258400, 26350960, 26443520, 26536080, 26625056,
26717616, 26810176, 26902736, 26995296, 27087856, 27180416, 27272976,
27365536, 27458096, 27550656, 27643216, 27735776, 27828336, 27920896,
28013456, 28106016, 28198576, 28291136, 28383696, 28476256, 28568816,
28661376, 28753936, 28846496, 28939056, 29031616, 29124176, 29216736,
29309296, 29401856, 29494416, 29583392, 29675952, 29768512, 29861072,
29953632, 30046192, 30138752, 30231312, 30323872, 30416432, 30508992,
30601552, 30694112, 30786672, 30879232, 30971792, 31064352, 31156912,
31249472, 31342032, 31434592, 31527152, 31619712, 31712272, 31804832,
31897392, 31989952, 32082512, 32175072, 32267632, 32360192, 32452752,
32541728, 32634288, 32726848, 32819408, 32911968, 33004528, 33097088,
33189648, 33282208, 33374768, 33467328, 33559888, 33652448, 33745008,
33837568, 33930128, 34022688, 34115248, 34207808, 34300368, 34392928,
34485488, 34578048, 34670608, 34763168, 34855728, 34948288, 35040848,
35133408, 35225968, 35318528, 35411088, 35500064, 35592624, 35685184,
35777744, 35870304, 35962864, 36055424, 36147984, 36240544, 36333104,
36425664, 36518224, 36610784, 36703344, 36795904, 36888464, 36981024,
37073584, 37166144, 37258704, 37351264, 37443824, 37536384, 37628944,
37721504, 37814064, 37906624, 37999184, 38091744, 38184304, 38276864,
38369424, 38458400, 38550960, 38643520, 38736080, 38828640, 38921200,
39013760, 39106320, 39198880, 39291440, 39384000, 39476560, 39569120,
39661680, 39754240, 39846800, 39939360, 40031920, 40124480, 40217040,
40309600, 40402160, 40494720, 40587280, 40679840, 40772400, 40864960,
40957520, 41050080, 41142640, 41235200, 41327760, 41416736, 41509296,
41601856, 41694416, 41786976, 41879536, 41972096, 42064656, 42157216,
42249776, 42342336, 42434896, 42527456, 42620016,
Remove any existing entry in /etc/vfstab for c0t1d0s3 or c0t1d0s4
Adding entries to /etc/vfstab
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-55
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Mounting /opt/CiscoMGC/var/log
Mounting /opt/CiscoMGC/var/spool
Success!!!
Copying old contents of log and spool to new partitions.
Step 9
Move the data from the saved directories to the new partitions on disk 1. Enter the following commands:
# cd /opt/CiscoMGC/var
# mv log.save/* log
# mv log.save/.*.seq log
*mv spool.save/* spool
Step 10
Remove the save directories. Enter the following commands:
# cd /opt/CiscoMGC/var
# rmdir log.save spool.save
Step 11
Change the owner, group, and file permissions of the var and spool directories to match the
/opt/CiscoMGC/var directory. Enter the following commands:
# cd /opt/CiscoMGC/var
# ls -ld . log spool
drwxrwxr-x 5 mgcusr mgcgrp 1024 May 8 23:43 .
drwxr-xr-x 3 root root 512 May 8 23:42 log
drwxr-xr-x 3 root root 3584 May 8 22:54 spool
# chown mgcusr:mgcgrp log spool
# chmod 775 log spool
# ls -ld . log spool
drwxrwxr-x 5 mgcusr mgcgrp 1024 May 8 23:43 .
drwxrwxr-x 3 mgcusr mgcgrp 512 May 8 23:42 log
drwxrwxr-x 3 mgcusr mgcgrp 3584 May 8 22:54 spool
Step 12
Start the Cisco MGC software. Enter the following command:
# /etc/init.d/CiscoMGC start
This completes the installation of the Log and Spool File system on a platform that already has the Cisco
MGC software installed.
If the Cisco MGC Software is Not Installed on the Platform
If the Cisco MGC software is not yet installed on your platform, start Log and Spool software installation
by following these procedures:
Step 1
Load the Cisco PGW Solaris 2.6 Patch CD into the CD-ROM drive. From the /var/tmp directory of the
target Netra machine, install the Log And Spool Software by entering the following command:
# cd /var/tmp
# pkgadd -d /cdrom/cdrom0/CSCOh005.pkg
The following screen is displayed:
The following packages are available:
1 CSCOh005
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Type package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-56
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Step 2
Press Enter to accept the default answer all.
The following screen is displayed:
Processing package instance <CSCOh005 from </var/tmp/CSCOh005.pkg
Virtual Switch Controller VSC log and spool package
(sparc) 2.0(3)
Cisco System, Inc.
Using </opt/sun_install as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <CSCOh005> [y,n,?]
Step 3
Type y and press Enter to continue.
The following screen is displayed:
Installing Media Gateway Controller VSC log and spool package as <CSCOh005>
## Executing preinstall script.
Platform is SUNW,Ultra-80
This is a known platform
NOTICE: Architecture checks passed
## Installing part 1 of 1.
/opt/sun_install/format_log_spool_start.cmd
/opt/sun_install/install_log_spool
/opt/sun_install/query_2nd_disk.cmd
[ verifying class <none> ]
## Executing postinstall script.
!!
!!
!!
!!
Step 4
You must now change directories to /opt/sun_install and
run the ./install_log_spool script as root.
Change directories to /opt/sun_install and run the install_log_spool script.
# cd /opt/sun_install
# ./install_log_spool
Platform is SUNW,Ultra-80
Searching for disks...done
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-57
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
defect
backup
verify
save
volname
!<cmd>
quit
format> disk
-
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
set 8-character volume name
execute <cmd>, then return
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@0,0
1. c0t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
Specify disk (enter its number): 1
selecting c0t1d0
[disk formatted]
format> current
Current Disk = c0t1d0
<SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1f,4000/scsi@3/sd@1,0
format> q
2nd Disk device is:
Disk type is:
Number of Cylinders :
c0t1d0
SUN36G
24620
Enter absolute path of the desired mount point for the
log directory or press enter to accept
the default [/opt/CiscoMGC/var/log]:
Step 5
Press Enter to accept the default mount point for the log directory or change it if you plan on installing
the Cisco MGC software in a different location.
The following screen is displayed:
Log directory mount point is /opt/CiscoMGC/var/log
Enter absolute path of the desired mount point for the
spool directory or press enter to accept
the default [/opt/CiscoMGC/var/spool]:
Step 6
Press Enter to accept the default mount point for the spool directory or change it if you plan on installing
the Cisco MGC software in a different location.
The following screen is displayed:
Spool directory mount point is /opt/CiscoMGC/var/spool
Number of cylinders for log partition: 9848
Start: 0
Start: 9847
Number of cylinders for spool partition: 14772
Start: 9848
Start: 24619
Build partition table for c0t1d0 ...
Searching for disks...done
selecting c0t1d0
[disk formatted]
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-58
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> p
PARTITION MENU:
0
1
2
3
4
5
6
7
select modify name
print label !<cmd> quit
partition> 0
Part
Tag
0
root
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
change `0' partition
change `1' partition
change `2' partition
change `3' partition
change `4' partition
change `5' partition
change `6' partition
change `7' partition
select a predefined table
modify a predefined partition table
name the current table
display the current table
write partition map and label to the disk
execute <cmd>, then return
Flag
wm
Cylinders
0 725
Size
1.00GB
Blocks
(726/0/0)
2097414
Enter partition id tag[root]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 1
Part
Tag
Flag
Cylinders
Size
Blocks
1
swap
wu
726 - 3629
4.00GB
(2904/0/0)
8389656
Enter partition id tag[swap]: unassigned
Enter partition permission flags[wu]: wm
Enter new starting cyl[726]: 0
Enter partition size[8389656b, 2904c, 4096.51mb, 4.00gb]: 0c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 0c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
3630 - 23156
26.90GB
0
Blocks
(19527/0/0) 56413503
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-59
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[3630]: 0
Enter partition size[56413503b, 19527c, 27545.66mb, 26.90gb]: 0c
partition> 5
Part
Tag
Flag
Cylinders
Size
Blocks
5
var
wm
23157 - 23882
1.00GB
(726/0/0)
2097414
Enter partition id tag[var]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23157]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 6
Part
Tag
Flag
Cylinders
Size
Blocks
6
usr
wm
23883 - 24608
1.00GB
(726/0/0)
2097414
Enter partition id tag[usr]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[23883]: 0
Enter partition size[2097414b, 726c, 1024.13mb, 1.00gb]: 0c
partition> 7
Part
Tag
Flag
Cylinders
Size
Blocks
7 unassigned
wm
24609 - 24619
15.52MB
(11/0/0)
31779
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[24609]: 0
Enter partition size[31779b, 11c, 15.52mb, 0.02gb]: 0c
partition> 2
Part
Tag
Flag
Cylinders
Size
Blocks
2
backup
wm
0 - 24619
33.92GB
(24620/0/0) 71127180
Enter partition id tag[backup]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[71127180b, 24620c, 34730.07mb, 33.92gb]: 24620c
partition> 3
Part
Tag
Flag
Cylinders
Size
Blocks
3 unassigned
wm
0
0
(0/0/0)
0
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 0
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 9848c
partition> 4
Part
Tag
Flag
Cylinders
Size
4 unassigned
wm
0
0
0
Blocks
(0/0/0)
Enter partition id tag[unassigned]: unassigned
Enter partition permission flags[wm]: wm
Enter new starting cyl[0]: 9848
Enter partition size[0b, 0c, 0.00mb, 0.00gb]: 14772c
partition> p
Current partition table (unnamed):
Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part
Tag
0 unassigned
1 unassigned
2 unassigned
3 unassigned
4 unassigned
5 unassigned
6 unassigned
Flag
wm
wm
wm
wm
wm
wm
wm
Cylinders
0
0
0 - 24619
0 - 9847
9848 - 24619
0
0
Size
0
0
33.92GB
13.57GB
20.35GB
0
0
Blocks
(0/0/0)
0
(0/0/0)
0
(24620/0/0) 71127180
(9848/0/0) 28450872
(14772/0/0) 42676308
(0/0/0)
0
(0/0/0)
0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-60
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
7 unassigned
wm
0
0
(0/0/0)
0
partition> l
partition> q
FORMAT MENU:
disk
type
partition
current
format
repair
label
analyze
defect
backup
verify
save
inquiry
volname
!<cmd>
quit
format> q
-
select a disk
select (define) a disk type
select (define) a partition table
describe the current disk
format and analyze the disk
repair a defective sector
write label to the disk
surface analysis
defect list management
search for backup labels
read and display labels
save new disk/partition definitions
show vendor, product and revision
set 8-character volume name
execute <cmd>, then return
unknown disk type, assuming the speed is 10000 rpm
Build log filesystem at /dev/rdsk/c0t1d0s3 ...
mkfs -F ufs /dev/rdsk/c0t1d0s3 28450872 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s3:
28450872 sectors in 9848 cylinders of 27 tracks, 107 sectors
13892.0MB in 308 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552,
1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032,
2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928,
3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408,
3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888,
4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368,
5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264,
6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744,
6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224,
7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704,
8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600,
9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080,
9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560,
10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480,
11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400,
11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736,
12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656,
13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576,
13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496,
14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832,
15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752,
15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672,
16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592,
17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512,
17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848,
18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768,
18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688,
19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608,
20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944,
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-61
Chapter 8
Sun Solaris 2.6 Operating System Installation
Configuring a Second Disk Drive
20893504,
21541424,
22189344,
22837264,
23485184,
24129520,
24777440,
25425360,
26073280,
26717616,
27365536,
28013456,
20986064,
21633984,
22281904,
22929824,
23577744,
24222080,
24870000,
25517920,
26165840,
26810176,
27458096,
28106016,
21078624,
21726544,
22374464,
23022384,
23666720,
24314640,
24962560,
25610480,
26258400,
26902736,
27550656,
28198576,
21171184,
21819104,
22467024,
23114944,
23759280,
24407200,
25055120,
25703040,
26350960,
26995296,
27643216,
28291136,
21263744,
21911664,
22559584,
23207504,
23851840,
24499760,
25147680,
25795600,
26443520,
27087856,
27735776,
28383696,
21356304,
22004224,
22652144,
23300064,
23944400,
24592320,
25240240,
25888160,
26536080,
27180416,
27828336,
21448864,
22096784,
22744704,
23392624,
24036960,
24684880,
25332800,
25980720,
26625056,
27272976,
27920896,
Build spool filesystem at /dev/rdsk/c0t1d0s4 ...
mkfs -F ufs /dev/rdsk/c0t1d0s4 42676308 107 27 8192 1024 251 1 166 8192 t 0 -1 8 107
Cylinder groups must have a multiple of 16 cylinders with the given parameters
Rounded cgsize up to 256
/dev/rdsk/c0t1d0s4:
42676308 sectors in 14772 cylinders of 27 tracks, 107 sectors
20838.0MB in 462 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552,
1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032,
2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928,
3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408,
3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888,
4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368,
5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264,
6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744,
6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224,
7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704,
8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600,
9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080,
9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560,
10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480,
11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400,
11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736,
12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656,
13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576,
13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496,
14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832,
15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752,
15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672,
16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592,
17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512,
17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848,
18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768,
18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688,
19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608,
20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944,
20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864,
21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784,
22189344, 22281904, 22374464, 22467024, 22559584, 22652144, 22744704,
22837264, 22929824, 23022384, 23114944, 23207504, 23300064, 23392624,
23485184, 23577744, 23666720, 23759280, 23851840, 23944400, 24036960,
24129520, 24222080, 24314640, 24407200, 24499760, 24592320, 24684880,
24777440, 24870000, 24962560, 25055120, 25147680, 25240240, 25332800,
25425360, 25517920, 25610480, 25703040, 25795600, 25888160, 25980720,
26073280, 26165840, 26258400, 26350960, 26443520, 26536080, 26625056,
26717616, 26810176, 26902736, 26995296, 27087856, 27180416, 27272976,
27365536, 27458096, 27550656, 27643216, 27735776, 27828336, 27920896,
28013456, 28106016, 28198576, 28291136, 28383696, 28476256, 28568816,
28661376, 28753936, 28846496, 28939056, 29031616, 29124176, 29216736,
29309296, 29401856, 29494416, 29583392, 29675952, 29768512, 29861072,
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-62
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Replacing Hard Disks for Existing Solaris 2.6 Platforms
29953632,
30601552,
31249472,
31897392,
32541728,
33189648,
33837568,
34485488,
35133408,
35777744,
36425664,
37073584,
37721504,
38369424,
39013760,
39661680,
40309600,
40957520,
41601856,
42249776,
30046192,
30694112,
31342032,
31989952,
32634288,
33282208,
33930128,
34578048,
35225968,
35870304,
36518224,
37166144,
37814064,
38458400,
39106320,
39754240,
40402160,
41050080,
41694416,
42342336,
30138752,
30786672,
31434592,
32082512,
32726848,
33374768,
34022688,
34670608,
35318528,
35962864,
36610784,
37258704,
37906624,
38550960,
39198880,
39846800,
40494720,
41142640,
41786976,
42434896,
30231312,
30879232,
31527152,
32175072,
32819408,
33467328,
34115248,
34763168,
35411088,
36055424,
36703344,
37351264,
37999184,
38643520,
39291440,
39939360,
40587280,
41235200,
41879536,
42527456,
30323872,
30971792,
31619712,
32267632,
32911968,
33559888,
34207808,
34855728,
35500064,
36147984,
36795904,
37443824,
38091744,
38736080,
39384000,
40031920,
40679840,
41327760,
41972096,
42620016,
30416432,
31064352,
31712272,
32360192,
33004528,
33652448,
34300368,
34948288,
35592624,
36240544,
36888464,
37536384,
38184304,
38828640,
39476560,
40124480,
40772400,
41416736,
42064656,
30508992,
31156912,
31804832,
32452752,
33097088,
33745008,
34392928,
35040848,
35685184,
36333104,
36981024,
37628944,
38276864,
38921200,
39569120,
40217040,
40864960,
41509296,
42157216,
Remove any existing entry in /etc/vfstab for c0t1d0s3 or c0t1d0s4
Adding entries to /etc/vfstab
Mounting /opt/CiscoMGC/var/log
Mounting /opt/CiscoMGC/var/spool
Success!!!
This completes the installation of the Log and Spool File system on a platform that does not yet have the
Cisco MGC software installed.
Replacing Hard Disks for Existing Solaris 2.6 Platforms
This chapter describes the scenario for replacing the hard disks of an existing platform running Solaris
2.6 and Cisco MGC 9.1(x) and 7.4(x) software.
Note
If you are running Cisco MGC Software release 7.4(11), then you must install patch CSCgp067 or a
patch that supercedes it before using this procedure.
Note
If you are running Cisco MGC Software release 7.4(12), then you must install patch CSCOgs011 or a
patch that supercedes it before using this procedure.
Note
If you are running Cisco MGC software release 9.1(5), then you must install patch CSCOgs004 or a
patch that supercedes it before using this procedure.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-63
Chapter 8
Sun Solaris 2.6 Operating System Installation
Replacing Hard Disks for Existing Solaris 2.6 Platforms
Backup Procedure
Caution
Step 1
When restoring the mgcbackup file, you must first install the same Cisco MGC software release version
and patch level that was originally installed on the platform. The same release version of the Volume
Manager and the Cisco Security Package (CSCOh013.pkg) must also be installed first if they were
originally installed on the platform.
Log in as root and stop the Cisco MGC application.
# /etc/init.d/CiscoMGC stop
a.
Local tape backup: Using the mgcbackup utility, back up the system to the local tape drive.
# /opt/CiscoMGC/local/mgcbackup -d /dev/rmt/0
b.
Remote file server backup: Using the mgcbackup utility, back up the system toa local directory.
Use the mgcbackup utility to list the filename of the last backup and then use ftp to transfer the file
to a remote file system.
# /opt/CiscoMGC/local/mgcbackup -d /opt/CiscoMGC/var/log
The backup file is stored in the specified directory path in the following
format:mgc_hostname_yyyymmdd_hhmmss_backup.tar
Note
Where:
- hostname is the name of the Cisco MGC host, such as MGC-01.
- yyyymmdd is the date the backup file was created, in a year-month-day format, such as
20011130.
- hhmmss is the time the backup file was created, in an hour-minute-second format, such as
115923.
# /opt/CiscoMGC/local/mgcbackup -l
Caution
Step 2
The backup file must now be moved to a remote filer server using the ftp program so it can
be recovered after Solaris 8 is installed on the new disk. You are responsible for providing the
mechanism and storage location.
Halt the operating system and power down the platform.
# /usr/sbin/shutdown -g0 -i5
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-64
OL-1150-15
Chapter 8
Sun Solaris 2.6 Operating System Installation
Replacing Hard Disks for Existing Solaris 2.6 Platforms
Replacing Hard Disks
To replace hard disks:
Step 1
Label the hard disks with their current locations and remove them from the system. Refer to the Sun
System Manual for your platform for the proper procedure. Be sure to follow proper antistatic
procedures.
Step 2
Install the new hard disks in the same slots as the existing hard disks. Refer to the Sun System Manual
for your platform for the proper procedure. Be sure to following proper antistatic procedures.
Loading the Solaris 2.6 operating system
Power on the platform and follow the procedures starting from the “Booting from a Local CD-ROM on
Netra t 1120/1125, t 1400/1405 and t 100/105” section on page 8-2 through “Configuring a Second Disk
Drive” section on page 8-27 to install the Solaris 2.6 operating system.
Installing the Cisco MGC Software
Install the same release and patch level of Cisco MGC Software that was originally on the box using the
“Installing the Cisco MGC Software Release 9.1(5)” section on page 7-3.
Restoring System Files
Caution
Step 1
Before restoring system files, install the same version of Volume Manager and the Cisco Security
Package (CSCOh013.pkg) if they were originally installed on the platform. See the “Installing Veritas
Volume Manager 3.1” section on page 8-38 and the
To restore system files:
a.
Local tape backup: Using the mgcrestore utility, restore the system files from the local tape drive.
# /opt/CiscoMGC/local/mgcrestore -d /dev/rmt/0
b.
Remote file server backup: Using the ftp program, retrieve the files and place them in the
/opt/CiscoMGC/var/log directory. Using the mgcrestore utility, restore the system files:
# /opt/CiscoMGC/local/mgcrestore -d /opt/CiscoMGC/var/spool -f filename
Where filename is the filename created in the “Backup Procedure” section on page 8-64.
Step 2
Enter the following command to start the Cisco MGC Software:
# /etc/init.d/CiscoMGC start
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
8-65
Chapter 8
Sun Solaris 2.6 Operating System Installation
Troubleshooting
This completes the Solaris 2.6 operating system installation. Continue to Chapter 7, “Cisco MGC
Software Release 9.1(5) Installation.” If you have questions or need assistance, see the “Obtaining
Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Troubleshooting
Symptom: Netra t 100/105 will not boot from CD-ROM
Solution:
At the ok prompt,type set-defaults to reset the OpenBoot PROM. Be sure to enter the environment
variable settings shown in Section 3.2 Step 30 at the end of the installation procedure.
Symptom: Installation program will not accept swap file size input
Solution:
If target machine will boot to the hard disk drive, use the format command to delete the existing
partitions.
If the target machine will not boot to the hard disk drive, boot from the CD-ROM by typing boot cdrom
-s at the ok prompt. Follow the instructions to reformat the disk. This procedure takes approximately 1.5
hours.
Symptom: CD-ROM on Netra t 100/105 is not accessible after OS installation
Solution:
Install the latest revision of the patch and reboot the target machine. This patch can be downloaded from
Sunsolve.sun.com. It is also included in Cisco patch package CSCOh007.pkg.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
8-66
OL-1150-15
CH A P T E R
9
Upgrading the Cisco MGC to Software
Release 9.1(5)
This chapter contains procedures for upgrading Software Release 7 of the Cisco Media Gateway
Controller (MGC) to Software Release 9.1(5) and upgrading within Software Release 9.1(5).
Note
Upgrading to Software Release 9.1(5) may take approximately two hours.
Note
In Cisco MGC software releases prior to Release 7.4, the Cisco Media Gateway Controller (MGC) was
referred to as the Cisco telephony controller software. If you are uninstalling a software release prior to
Release 7.4, you can find the Cisco MGC software files and processes in the /opt/TransPath directory
of your host server.
In Release 7.4 and later releases, the Cisco MGC software files and processes are located in the
/opt/CiscoMGC directory.
This chapter contains the following sections:
•
Before You Start, page 9-1
•
Quick Upgrade Guide, page 9-2
•
Upgrading to Software Release 9.1(5), page 9-5
•
Fallback Procedures, page 9-8
Before You Start
Caution
To prevent the system from running out of disk space during installation and to avoid removal of data
files and databases to compensate, you must first verify that there is enough hard disk space to support
your intended upgrade. You can delete unnecessary log files (platform*.log), user-generated trace files
(*.btr), call detail record (CDR) files (.bin or .csv), old *.tar files, or user-generated toolkit files (in the
/var/cust_specific/toolkit directory) to free space. You also need at least 4 GB of disk space for the /opt
file system.
Before you start upgrading to the current MGC software release, perform the following steps:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
9-1
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Quick Upgrade Guide
•
Review the hardware and software requirements found in the document Release Notes for the
Cisco Media Gateway Controller Software Release 9.
•
Ensure that you have access to the console port on your Cisco MGC host.
Required Software
You must have the Cisco MGC Installation CD, which includes the current release of the Cisco MGC
software.
Quick Upgrade Guide
The following table provides an overview of the upgrade procedure. If you need more detailed
information, go to the page indicated in the rightmost column.
Caution
It is important to follow the sequence of software installation procedures provided in “Cisco MGC
Software Installation/Uninstallation Sequence” section on page 7-3.
Task
For Detailed Procedures, Go to...
Back up system data
“Backing Up System Data” section
on page 9-2
Remove previous version of the MGC software.
“Removing a Previous Version of the
Cisco MGC Software” section on
page 9-3.
Install Cisco MGC Software Release 9.
Depending on your software upgrade
requirements, see the following:
“Upgrading a Simplex System”
section on page 9-5
OR
“Upgrading a Fault Tolerant System”
section on page 9-6
Backing Up System Data
Before you upgrade, make copies of the following directories to back up system data:
Tip
•
/opt/CiscoMGC/etc
•
/opt/CiscoMGC/dialPlan
•
/opt/CiscoMGC/CONFIG_LIB
You also may want to back up your CDR files to a separate server.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
9-2
OL-1150-15
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Quick Upgrade Guide
Step 1
Back up the database by entering the following command:
/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb/opt/ciscoMGC/etc/migrate.ttdb
If you do not run the migrate command when you back up your system data, you will get the following
message (when this occurs, run the migrate command and repeat the installation process):
Error Message A backup file was found for the database, but no migration file.
A migration file is required in order to upgrade to the latest release of the Main Memory Database
(MMDB). If you get the above message, you must do one of the following procedures:
Option 1:
1.
Run the following command on the other MGC if running in a failover pair:
/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb migrate.ttdb
2.
Move the file to the /opt/CiscoMGC/etc directory.
3.
Reinstall the package.
Option 2:
1.
Reinstall the previous release of the MGC and run the following command:
/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb
2.
Uninstall the previous release.
3.
Reinstall the package.
Option 3:
If you do not want to save your data from the previous release, remove the file
/opt/CiscoMGC/etc/export.ttdb
4.
Reinstall the package.
For details on backing up your system data, see “Cisco MGC Backup and Restore Procedures” section
in Chapter 3 of the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide.
Removing a Previous Version of the Cisco MGC Software
Before upgrading an existing release of the Cisco MGC software, you must first uninstall the previous
software version.
Caution
Note
We require that software be uninstalled in the reverse order in which it is installed. For example, you
must first uninstall package CSCOh013 before you uninstall the Cisco MGC software.
For a sample uninstall.sh output, see the “Removing a Previous Software Version: Sample Output for
uninstall.sh” section on page E-1.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
9-3
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Quick Upgrade Guide
To remove the Cisco MGC software, complete the following steps:
Step 1
Log in at the console as the root user.
Step 2
Uninstall package CSCOh013. Refer to Removing the Cisco Security Package, page 7-11 for the
uninstallation procedures.
Step 3
Stop the Cisco MGC software by entering the following command:
Caution
Stopping the Cisco MGC software on the active host takes all processes and links out of
service.
# /etc/init.d/CiscoMGC stop
Wait until the system returns the following response:
Signalling procM to shut down
...shutdown complete
Step 4
Uninstall the Cisco MGC.
Step 5
Install the new version of the Cisco MGC. Insert the Cisco MGC Software Version 9 CD-ROM into the
CD-ROM drive and enter the following commands:
# cd /cdrom/cdrom0
# ./uninstall.sh
Step 6
Answer y to the following prompt if you are upgrading from a previous version of software Release 9.
If this is an initial installation, answer n:
If you answer no to the following question you will lose all new provisioning work.
Is the uninstall being done in order to upgrade to a new version of the software? [y]
[y,n,?,q]
Step 7
Timesaver
Step 8
The system asks if you want to use the supplied administrative file to perform an unattended package
removal. This process removes all the packages automatically.
If you do not accept the unattended removal, the system prompts you before removing each package
individually.
Type y (yes) and press Enter to accept unattended package removal. The system displays a list of
packages as it removes them.
When package removal is finished, the following message appears:
Uninstallation log can be found in /var/adm/MGC_uninstall.log.
Step 9
Install package CSCOh013. Refer to Installing the Cisco Security Package, page 7-7 for detailed
procedures.
Step 10
Start the Cisco MGC.
Step 11
Change to the /etc directory and open the group file with your editor.
Make sure that the mgcgrp group is removed so that the default software installation will be accepted
later.
Step 12
Save any changes to the group file and close it.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
9-4
OL-1150-15
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Upgrading to Software Release 9.1(5)
This completes the removal of the previous version of the Cisco MGC software. If you have questions
or need assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii.
Upgrading to Software Release 9.1(5)
Caution
Perform software upgrade only during the maintenance window, when call traffic is minimal.
Caution
When upgrading to Software Release 9.1(5), make sure that you limit the MML names that you are using
for the PRI backhaul IP links to a maximum of 16 characters. If the MML names exceed 16 characters,
the upgrade will fail.
Note
For the software to work properly, you must reboot the system every time you modify any file in the /etc
directory.
Monitor system output frequently for error messages during the software upgrade process and correct
any error conditions before continuing with the upgrade.
Note
During migration from Software Release 7.4.11 to 9.1.5, the PTCODE TID for one of the destinations
is converted to an OPC from DPC, resulting in the system having two OPCs with same type
"TRUEOPC".
You must delete the extra OPC by using the MML command prov-dlt:OPC and adding the real DPC
back by entering the MML command prov-add:DPC after 9.1.5 is installed.
Upgrading a Simplex System
To upgrade a simplex system, perform the following steps:
Step 1
Back up your system data. See “Backing Up System Data” section on page 9-2.
Step 2
Remove the Cisco MGC software. See “Removing a Previous Version of the Cisco MGC Software”
section on page 9-3.
Step 3
Install the new software. See the “Installing the Cisco MGC Software Release 9.1(5)” section on
page 7-3.
Note
Make sure you run the migrate command when backing up your system data (see “Backing Up System
Data” section on page 9-2).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
9-5
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Upgrading to Software Release 9.1(5)
Upgrading a Fault Tolerant System
Note
There will be a brief service interruption when you upgrade from one major software release to another.
Before upgrading a fault tolerant system, make sure that you complete the following prerequisites:
Caution
•
Verify that both platforms (dual system) are operational and processing calls.
•
Ensure that both servers are able to run as master immediately prior to the upgrade.
If your fault tolerant system has Software Release 7.3, you cannot upgrade to Software Release 9 without
call interruption.
You must install the software on the standby server and bring it up before you can take the active server
down.
To upgrade a fault tolerant system:
Step 1
Back up your system data. See “Backing Up System Data” section on page 9-2.
Step 2
On Host X, make sure that both MGCs share the same configuration by entering the prov-sync
command.
Step 3
On Host Y, log in to the standby host (Host Y) as mgcusr.
Step 4
Run the MML command prov-exp to export your data files to an MML script. (This command is
available only in Software Release 7.4 and later.)
Note
After exporting your data files, you must edit them because the format of some files has been
changed in Software Release 9. You must edit the trunk group and routing files so that they can
be read by the newer software.
For more information on MML, see the Cisco Media Gateway Controller Software Release 9
Provisioning Guide and the Cisco Media Gateway Controller Software Release 9 MML Command
Reference.)
Step 5
On Host Y, stop the Cisco MGC software by entering the /etc/init.d/CiscoMGC stop command.
Note
Before you take the active server down, we recommend first installing and bringing up the
software on the standby server.
Step 6
Remove the Cisco MGC software. See “Removing a Previous Version of the Cisco MGC Software”
section on page 9-3.
Step 7
Install the new software. See the “Installing the Cisco MGC Software Release 9.1(5)” section on
page 7-3.
Note
Make sure you run the migrate command when backing up your system data (see “Backing Up System
Data” section on page 9-2).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
9-6
OL-1150-15
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Upgrading to Software Release 9.1(5)
Step 8
Turn off the synchronization interfaces by editing (on Host Y) the XECfgParm.dat file in the
/opt/CiscoMGC directory to set the pom.dataSync parameter to false.
Step 9
Save changes to the XECfgParm.dat file.
Step 10
To prevent impact on existing calls, enter the following command (on Host X) and wait for existing calls
to release:
set-admin-state:mgc02:lock
Step 11
Log in to the active host (Host X) as the root user. Stop the MGC software by entering the
/etc/init.d/CiscoMGC stop command. Wait for Host X to stop before starting Host Y.
Step 12
To unblock the CICs when the new system comes up, edit the properties.dat file on Host Y to set
*.GRSEnabled=true before starting the MGC software.
Caution
Before setting *.GRSEnabled=true, make sure the protocol supports group reset.
Step 13
On Host Y, restart the MGC software by entering the /etc/init.d/CiscoMGC start command.
Step 14
Verify that Host Y is in the active state by entering the following MML command:
rtrv-ne
If Host Y is not in the active state, contact Cisco TAC.
Step 15
On Host X, remove the MGC software. See “Removing a Previous Version of the Cisco MGC Software”
section on page 9-3.
Step 16
On Host X, install the new software. See the “Installing the Cisco MGC Software Release 9.1(5)” section
on page 7-3.
Step 17
Start the MGC software on Host X by entering the /etc/init.d/CiscoMGC start command.
Step 18
Verify that the Host X MGC software is running in standby mode by entering the following MML
command:
rtrv-ne
Step 19
Turn on the synchronization interfaces. On Host Y, enter the MML command sw-over::confirm to
switch call processing to Host X. Verify that Host X is processing calls.
Step 20
On Host Y (now the standby host), stop the MGC software by entering the /etc/init.d/CiscoMGC stop
command.
Step 21
Edit the XECfgParm.dat file in the /opt/CiscoMGC directory to set the pom.dataSync parameter to true.
Step 22
Save changes to the XECfgParm.dat file and restart the MGC software by entering the
/etc/init.d/CiscoMGC start command.
Step 23
On Host X, make sure the pom.dataSync parameter is set to true.
Step 24
On Host Y, stop the daemon on the standby host by entering the ttreplic command.
Step 25
On Host Y, re-run the replication script by entering the following command:
setup_replication.sh activehost standby
This completes the procedures for upgrading to Cisco MGC Software Release 9. If you have questions
or need assistance, see the “Obtaining Documentation, Obtaining Support, and Security Guidelines”
section on page xvii.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
9-7
Chapter 9
Upgrading the Cisco MGC to Software Release 9.1(5)
Fallback Procedures
Fallback Procedures
Note
Before upgrading your Cisco MGC software, make sure that you back up all .dat files. Use the config-lib
command located in /opt/CiscoMGC/local to back up these files.
If the upgrade fails for some reason, uninstall the new software release, fall back to the last software
release installed on your system, note down the details of the upgrade failure, and open a TAC case with
Cisco.
Do the following procedures to fall back to the last software release:
Step 1
Log in as root.
Step 2
At the prompt, enter the following command to uninstall the new software release you were attempting
to install:
uninstall.sh
The following message displays:
If you answer no to the following question you will lose all new provisioning work.
Is the uninstall being done in order to upgrade to a new version of the
software? [y] [y,n,?,q]
Step 3
Type n to fallback to the original software release. The following message displays:
Backup setup complete.
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Step 4
Type y to start unattended removal of the new software.
Step 5
Install the old Cisco MGC configuration by using the following command:
install.sh
Step 6
Call TAC for assistance after the old software is restored.
This completes the fallback procedures for Software Release 9. If you have questions or need assistance,
see the “Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page xvii.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
9-8
OL-1150-15
CH A P T E R
10
Configuring the Local Area Network Switch
This chapter provides a brief overview of the local area network (LAN) switches (Cisco Catalyst Switch
family) in your solution. The LAN switch connects the Cisco MGC hosts to the media gateways
(MGWs) or to the Cisco Signaling Link Terminals (SLTs). A LAN switch is not provided with the Cisco
MGC.
LAN Switch Overview
The LAN switch is used in the Cisco MGC node to extend virtual LANs (VLANs) across platforms
through backbone Ethernet connections, when necessary.
Figure 10-1 illustrates an example of a fault-tolerant control signaling network using dual Cisco Catalyst
LAN switches.
Note
Make sure that the duplex on the Cisco catalyst port is correctly configured and that there is no duplex
mismatch between the switch and the shelf controller (SC) network interface card (NIC). Otherwise,
some SS7 messages, although received at the SC NIC, might be ignored by the SC call processing
engine.
Figure 10-1
Sample Configuration of a Duplex LAN Switch
MGC hosts
Cisco SLTs
5500
30707
5500
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
10-1
Chapter 10
Configuring the Local Area Network Switch
Catalyst 2900 XL Series
Catalyst 2900 XL Series
See the following web sites for hardware and software documentation for the Catalyst 2900 XL series:
http://www.cisco.com/warp/public/cc/pd/si/casi/ca2900xl/prodlit/index.shtml
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/index.htm
Catalyst 5500 and 5000 Series
See the following web sites for hardware and software documentation for the Catalyst 5500 series (5500,
5509, and 5505) and Catalyst 5000 series (5000 and 5002) switches:
http://www.cisco.com/warp/public/cc/pd/si/casi/ca5000/prodlit/lanem_ds.htm
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/index.htm
Note
For information about the correct Cisco IOS software version, see Release Notes for the Cisco Media
Gateway Controller Software Release 9.
For information on the image that your switch supports, see the documentation that came with your
switch.
If you have questions or need assistance, see the “Obtaining Documentation, Obtaining Support, and
Security Guidelines” section on page xvii of the Preface.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
10-2
OL-1150-15
CH A P T E R
11
Migrating to Cisco MGC Software Release 9.3(1)
This chapter describes procedures for migrating to the Cisco MGC 9.3(1) software from Cisco MGC
software release 9.2(2).
Before you Begin
Caution
Before starting the upgrade, verify the existing system status and make sure there are no major alarms.
To ensure a smooth migration, we recommend the following steps:
1.
Start the procedure on the standby box (Host B).
2.
After Host B is migrated to Release 9.3(1), shut down the active box (Host A) before starting Cisco
MGC 9.3(1) on Host B. A brief service interruption will occur while both systems are out of service.
3.
After starting Cisco MGC 9.3(1) on Host B, perform acceptance testing to verify that the migration
is successful.
Note
Do not make any provisioning changes during the migration and verification period.
If any part of the testing fails, try to resolve the problems within a reasonable period of time. If
the problem cannot be resolved, perform backout procedures.
4.
When migration of both Host A and Host B to Release 9.3(1) is complete, perform failover testing
to verify redundancy.
Conditions for Migration
Your hardware and software environment must meet the following conditions before you can use the
procedures provided below to migrate your software to the Cisco MGC software release 9.3(1):
1.
Your system must have at least 2 disks.
2.
The disks in the system must be at least 18 GB in size.
3.
You (or the person doing the upgrade) must be an experienced Solaris system administrator. You
must be familiar with system administration tasks such as mounting file systems and running tar to
save and restore files.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-1
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Quick Guide to Migration
Quick Guide to Migration
Caution
Always start migration from the standby box (Host B).
The following table provides a quick guide to migrating to Cisco MGC software release 9.31). For
details, refer to the page numbers located on the right-hande column of the table.
Procedure
Details on Page...
Migrating Host B (Standby Box)
2
– Verify the Existing Network Status
2
– Back Up the PGW Configuration on Host A
3
– Back Up the PGW Configuration on Host B
3
– Remove Cisco MGC 9.2(2) from Host B
4
– Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host B
5
– Stop Cisco MGC 9.2(2) on Host A
5
– Start Cisco MGC 9.3(1) on Host B
5
– Migration Verification on Host B
5
Migrating Host A (Active Box)
6
– Remove Cisco MGC 9.2(2) from Host A
6
– Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host A
7
– Start Cisco MGC 9.3(1) on Host A
7
– Migration Verification on Host A
7
Failover Testing
8
Backout Procedures
8
– Backout After Migration on Host B
8
– Backout After Migration on Host B and Host A
10
Migrating Host B (Standby Box)
Verify the Existing Network Status
From Host B (standby box):
Step 1
Verify that there are no existing alarms. Log in to both Host A (active box) and Host B (standby box)
and enter the following command:
mml>rtv-alms
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-2
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Migrating Host B (Standby Box)
Step 2
If alarms are found, resolve all before proceeding with migration.
Proceed to the following procedure, “Back Up the PGW Configuration on Host A”.
Back Up the PGW Configuration on Host A
To back up the PGW configuration on Host A:
Step 1
Log in as mgcusr.
Step 2
Enter the following command:
mml>prov-exp:all:dirname=”922-backup”
Step 3
Go to /opt/CiscoMGC/etc. Enter the following command:
% cd /opt/CiscoMGC/etc
Step 4
Record the active link. Enter the following command:
% ls -l
Step 5
Create an mgc-922-backup directory under /tmp. Enter the following command:
% mkdir /tmp/mgc-922-backup
Step 6
Go to /opt/CiscoMGC/local. Enter the following command:
% cd /opt/CiscoMGC/local
Step 7
Back up the PGW configuration on Host A. Enter the following commands:
% mgcbackup -d /tmp/mgc-922-backup
% cd /tmp/mgc-922-backup
Step 8
Using FTP, transfer the backup configuration files to a remote server and a remote storage location such
as a laptop computer.
Caution
These files must now be moved to a remote server and remote storage location so they can be
recovered if necessary. You are responsible for providing the mechanism and storage
location.
Proceed to back up Host B.
Back Up the PGW Configuration on Host B
To back up Host B’s PGW configuration:
Step 1
Log in as mgcusr.
Step 2
Create an mgc-922-backup directory under /tmp. Enter the following command:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-3
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Migrating Host B (Standby Box)
% mkdir /tmp/mgc-922-backup
Step 3
Enter the following command:
% mgcbackup -d /tmp/mgc-922-backup
Step 4
Go to /opt/CiscoMGC/etc. Enter the following command:
% cd /opt/CiscoMGC/etc
Step 5
Copy the XECfgParm.dat file. Enter the following command:
% cp XECfgParm.dat/tmp/922-backup/XECfgParm.dat.922
Step 6
Verify whether both the backup and XECfgParm.dat.922 files are present, indicating that the backup is
successful. Enter the following command:
% cd /tmp/922-backup
Step 7
Using FTP, transfer the backup and XECfgParm.dat.922 files to a remote server and a remote storage
location such as a laptop computer.
Caution
These files must now be moved to a remote server and remote storage location so they can be
recovered if necessary. You are responsible for providing the mechanism and storage
location.
Proceed to the following section, “Remove Cisco MGC 9.2(2) from Host B”.
Remove Cisco MGC 9.2(2) from Host B
To remove Cisco MGC 9.2(2) from Host B:
Step 1
Log out and log back in as root.
Step 2
Stop the Cisco MGC. Enter the following command:
# /etc/init.d/CiscoMGC stop
Step 3
Load the CD-ROM containing Cisco MGC 9.3(1) into the CD-ROM drive. Enter the following
command:
# cd /cdrom/cdrom0
Step 4
Enter the following command:
# ./uninstall.sh
Text similar to the following is displayed:
Is the uninstall being done in order to upgrade to a
new version of the software? [y] [y,n,?,q] y
Step 5
Type y and press Enter to accept unattended package removal. The system displays a list of the packages
as it removes them.
Step 6
Check the uninstall log for any errors.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-4
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Migrating Host B (Standby Box)
Step 7
If the uninstallation procedure is successful, continue with the migration. If errors are present in the log,
try to resolve the problem or contact your Cisco Support Engineer.
Proceed to the next section, “Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host B”.
Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host B
To install Cisco MGC 9.3(1) and the latest Cisco MGC patches on Host B, refer to the “Installing the
Cisco MGC Software 9.2(x) and Higher Releases” section on page 3-3.
For the most recent released Cisco MGC patches, refer to the Release Notes for the Cisco Media
Gateway Controller Software Release 9.3(1) located at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn931.htm
Stop Cisco MGC 9.2(2) on Host A
Caution
Make sure to stop the older software version in the active box before starting the newly-installed Cisco
MGC 9.3(1) software. Use the command /etc/init.d/CiscoMGC stop to stop the older software version
in the active box.
Step 1
At the active box, Host A, log in as root.
Step 2
Stop the Cisco MGC 9.2(2). Enter the following command:
# /etc/init.d/CiscoMGC stop
Proceed to the next section, “Start Cisco MGC 9.3(1) on Host B”.
Start Cisco MGC 9.3(1) on Host B
To start Cisco MGC 9.3(1) on Host B:
Step 1
Log out as root and log in as mgcusr.
Step 2
Start Cisco MGC 9.3(1) on Host B. Enter the following command:
# /etc/init.d/CiscoMGC start
Proceed to the next section, “Migration Verification on Host B” to verify that the migration is successful.
Migration Verification on Host B
To verify that Host B migration is successful, enter the following commands:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-5
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Migrating Host A (Active Box)
mml
mml
mml
mml
mml
mml
mml
Note
>
>
>
>
>
>
>
rtrv-softw:all
rtrv-ne
rtrv-ne-health
rtrv-c7lnk:all
rtrv-iplnk:all
rtrv-tc:all
rtrv-dest:all
The rtrv-dest:all command verifies the following:
- Platform state is in-service
- Software processes have started
- All links are in service
Proceed to the following section, “Migrating Host A (Active Box)”.
Migrating Host A (Active Box)
To migrate Host A to Cisco MGC 9.3(1):
Remove Cisco MGC 9.2(2) from Host A
To remove Cisco MGC 9.2(2) from Host A:
Step 1
Log in as root.
Step 2
Stop the Cisco MGC. Enter the following command:
# /etc/init.d/CiscoMGC stop
Step 3
Load the CD-ROM containing Cisco MGC 9.3(1) into the CD-ROM drive. Enter the following
command:
# cd /cdrom/cdrom0
Step 4
Enter the following command:
# ./uninstall.sh
Step 5
You will be prompted for the rest of the uninstallation steps. The system displays a list of packages as
they are removed. Check the uninstall log for any errors.
Step 6
If the uninstallation procedure is successful, continue with the migration. If errors are present in the log,
contact your Cisco Support Engineer.
Proceed to the next section, “Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host A”.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-6
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Migrating Host A (Active Box)
Install Cisco MGC 9.3(1) and Cisco MGC Patches on Host A
To install Cisco MGC 9.3(1) and the latest Cisco MGC patches on Host A, refer to the “Installing the
Cisco MGC Software 9.2(x) and Higher Releases” section on page 3-3.
For the most recent released Cisco MGC patches, refer to the Release Notes for the Cisco Media
Gateway Controller Software Release 9.3(1) located at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn931.htm
Proceed to the following section, “Start Cisco MGC 9.3(1) on Host A”.
Start Cisco MGC 9.3(1) on Host A
To start Cisco MGC 9.3(1) on Host A:
Step 1
Enter the following command:
# /etc/init.d/CiscoMGC start
Step 2
Log out as root and log in as mgcusr.
Step 3
Verify that the system is running on standby. Enter the following command:
mml > rtrv-ne
Proceed to the next section, “Migration Verification on Host A”.
Migration Verification on Host A
To verify that Host A migration is successful, enter the following commands:
mml
mml
mml
mml
mml
mml
Note
>
>
>
>
>
>
rtrv-softw:all
rtrv-ne
rtrv-ne-health
rtrv-c7lnk:all
rtrv-iplnk:all
rtrv-dest:all
The rtrv-dest:all command verifies the following:
- Platform state is in-service
- Software processes have started
- All links are in service
Proceed to the following section, “Failover Testing”.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-7
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Failover Testing
Failover Testing
Use the following command to verify the PGW failover:
mml>sw-over::confirm
If no errors are found, the migration is complete. Let the system run for a day and monitor all alarms and
logs.
If errors are found and the tests fail, try to resolve the problems immediately. If problems cannot be
resolved, call Cisco TAC. You may need to back out of the migration, as described in the following
section, “Backout Procedures”.
Backout Procedures
To back out of the migration, perform the following procedures:
Backout After Migration on Host B
Stop Cisco MGC 9.3(1) on Host B
Step 1
Log in to Host B as root.
Step 2
Stop Cisco MGC 9.3(1) on Host B. Enter the following command:
# /etc/init.d/CiscoMGC stop
Proceed to the next section, “Start Cisco MGC 9.2(2) on Host A”.
Start Cisco MGC 9.2(2) on Host A
Start Cisco MGC 9.3(1) on Host A. Enter the following command:
# /etc/init.d/CiscoMGC start
Proceed to the next section, “Backout Verification”.
Backout Verification
To verify that the system is working after backing out of the migration, enter the following commands:
mml
mml
mml
mml
mml
mml
>
>
>
>
>
>
rtrv-softw:all
rtrv-ne-health
rtrv-iplnk:all
rtrv-c7lnk:all
rtrv-tc:all
rtrv-dest:all
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-8
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
Note
The rtrv-dest:all command verifies the following:
- Platform state is in-service
- Software processes have started
- All links are in service
Proceed to the following section, “Remove Cisco MGC 9.3(1) from Host B”.
Remove Cisco MGC 9.3(1) from Host B
To remove Cisco MGC 9.3(1) from Host B:
Step 1
Log out and log back in as root.
Step 2
Stop the Cisco MGC. Enter the following command:
# /etc/init.d/CiscoMGC stop
Step 3
At the prompt, enter the following command to remove the new software release you were attempting
to install:
# ./uninstall.sh
A message similar to the following is displayed:
If you answer no to the following question, you will lose
all new provisionng work.
Is the uninstall being done in order to upgrade to a new version
of the software? [y] [y,n,?,q] n
Step 4
Type n to fall back to Cisco MGC 9.2(2).
A message similar to the following is displayed:
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Step 5
Type y to start the unattended removal of the software.
Step 6
Check the uninstall log for any errors. If the uninstallation procedure is successful, continue with the
migration. If errors are present in the log, contact Cisco TAC.
Proceed to the next section.
Install Cisco MGC 9.2(2) and Cisco MGC Patches on Host B
Note
Make sure you re-install the patches that were previously loaded on Host B before you started the
migration.
To install Cisco MGC 9.2(2) and the original Cisco MGC patches on Host B, refer to the “Installing the
Cisco MGC Software 9.2(x) and Higher Releases” section on page 3-3.
For the applicable Cisco MGC9.2(2) patches, refer to the Release Notes for the Cisco Media Gateway
Controller Software Release 9.2(2) located at the following url:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-9
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn922.htm
Proceed to the following section, “Start Cisco MGC 9.2(2) on Host B”.
Start Cisco MGC 9.2(2) on Host B
Note
You may change your password at this point.
Step 1
Log in as mgcusr.
Step 2
Enter the following command to start Cisco MGC 9.2(2):
# /etc/init.d/CiscoMGC start
Proceed to the following section,
Backout Verification on Host B
To verify that the backout from Cisco MGC 9.3(1) is successful, enter the following commands:
mml
mml
mml
mml
mml
Note
>
>
>
>
>
rtrv-softw:all
rtrv-ne-health
rtrv-iplnk:all
rtrv-c7lnk:all
rtrv-dest:all
The rtrv-dest:all command verifies the following:
- Platform state is in-service
- Software processes have started
- All links are in service
Proceed to the following section, “Backout After Migration on Host B and Host A”.
Backout After Migration on Host B and Host A
Note
Make sure Host A is running in standby mode.
Stop Cisco MGC 9.3(1) on Host A
Step 1
Log in as root.
Step 2
Enter the following command to stop Cisco MGC 9.3(1):
# /etc/init.d/CiscoMGC stop
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-10
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
Proceed to the following section.
Remove Cisco MGC 9.3(1) from Host A
Step 1
Enter the following command:
# ./uninstall.sh
Step 2
Load the Cisco 9.3(1) CD-ROM into the Host A CD-ROM drive.
Step 3
Enter the following command:
# cd /cdrom/cdrom0
Step 4
At the prompt, enter the following command to remove the new software release you were attempting
to install:
# ./uninstall.sh
A message similar to the following is displayed:
If you answer no to the following question, you will lose
all new provisionng work.
Is the uninstall being done in order to upgrade to a new version
of the software? [y] [y,n,?,q] n
Step 5
Type n to fall back to Cisco MGC 9.2(2).
A message similar to the following is displayed:
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Step 6
Type y to start the unattended removal of the software.
Step 7
Check the uninstall log for any errors. If the uninstallation procedure is successful, continue with the
migration. If errors are present in the log, contact Cisco TAC.
Proceed to the following section.
Install Cisco MGC 9.2(2) and 9.2(2) Patches on Host A
Note
Step 1
Make sure you re-install the patches previously loaded on Host A before you started the migration.
For installation procedures, refer to the “Installing the Cisco MGC Software 9.2(x) and Higher Releases”
section on page 3-3.
For the applicable Cisco MGC9.2(2) patches, refer to the Release Notes for the Cisco Media Gateway
Controller Software Release 9.2(2) located at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn922.htm
Step 2
Log in as mgcusr. FTP your backup files from the remote server or remote storage.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-11
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
Make sure that you are logged in as mgcusr.
Note
Step 3
Enter the following command to restore the backup files:
% mgcrestore -d /opt/CiscoMGC/local -f mgc_XXXXX_backup
Step 4
Verify that the backup file was successfully restored. Enter the following command:
% cd /opt/CiscoMGC/etc
% ls -l
Use the ls -l command to verify whether the active link is the same link as the one before the
migration (see Step 4 on page 11-3).
Note
Proceed to the following section.
Stop Cisco MGC 9.3(1) on Host B
Log in as root and enter the following command:
# /etc/init.d/CiscoMGC stop
Start Cisco MGC 9.2(2) on Host A
Enter the following command:
# /etc/init.d/CiscoMGC start
Post Backout Verification on Host A
Verify that the backout on Host A is successful. Enter the following commands:
mml > rtrv-ne-health
The rtrv-ne-health command verifies whether Host A is in the active mode.
Note
mml
mml
mml
mml
>
>
>
>
rtrv-softw:all
rtrv-iplnk:all
rtrv-c7lnk:all
rtrv-dest
Proceed to the following section.
Remove Cisco 9.3(1) from Host B
Step 1
Log out and log back in as root.
Step 2
Stop the Cisco MGC. Enter the following command:
# /etc/init.d/CiscoMGC stop
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-12
OL-1150-15
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
Step 3
At the prompt, enter the following command to remove the new software release you were attempting
to install:
# ./uninstall.sh
A message similar to the following is displayed:
If you answer no to the following question, you will lose
all new provisionng work.
Is the uninstall being done in order to upgrade to a new version
of the software? [y] [y,n,?,q] n
Step 4
Type n to fall back to Cisco MGC 9.2(2).
A message similar to the following is displayed:
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Step 5
Type y to start the unattended removal of the software.
Step 6
Check the uninstall log for any errors. If the uninstallation procedure is successful, continue with the
migration. If errors are present in the log, try to resolve the problem. Otherwise, contact Cisco TAC.
Proceed to the following section.
Install Cisco MGC 9.2(2) and 9.2(2) Patches on Host B
Note
Make sure you re-install the patches that were previously loaded on Host B before you started the
migration.
For installation procedures, refer to the “Installing the Cisco MGC Software 9.2(x) and Higher Releases”
section on page 3-3.
For the applicable Cisco MGC9.2(2) patches, refer to the Release Notes for the Cisco Media Gateway
Controller Software Release 9.2(2) located at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn922.htm
Proceed to the following section.
Start Cisco MGC 9.2(2) on Host B
Proceed to the following section after staring Cisco 9.2(2) on Host B.
Post Backout Verification on Host B
Verify that the backout on Host B is successful. Enter the following commands:
mml
mml
mml
mml
mml
mml
>
>
>
>
>
>
rtrv-softw:all
rtrv-ne-health
rtrv-iplnk:all
rtrv-c7lnk:all
rtrv-tc:all
rtrv-dest:all
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
11-13
Chapter 11
Migrating to Cisco MGC Software Release 9.3(1)
Backout Procedures
Note
The rtrv-dest:all command verifies the following:
- Platform state is in-service
- Software processes have started
- All links are in service
Proceed to the following section.
Failover Testing
Enter the following command to verify the PGW failover:
mml>sw-over::confirm
This completes the migration to Cisco MGC software release 9.3(1).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
11-14
OL-1150-15
CH A P T E R
12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
This chapter describes scenarios for migrating to the Solaris 8 operating system and Cisco MGC
Release 9.2(2) software and up.
This chapter contains the following information:
•
Required Software, page 12-3
•
Conditions for Migration, page 12-1
•
Backing Up System Data, page 12-3
•
Backing Up the Main Memory Database, page 12-4
•
Backing Up the Cisco MGC Configuration Files, page 12-5
•
Installing Solaris 8, page 12-6
•
Restoring Data Files, page 12-7
•
Installing the Cisco MGC Software and Patches, page 12-9
•
Configuring a Second Disk, page 12-9
•
Installing the Alarm Software, page 12-11
•
Installing the Solaris 8 Patch Cluster (CSCOh015), page 12-11
•
Restoring the SNMP Configuration on PGW for Cisco MNM and BAMS, page 12-11
•
Falling Back to Solaris 2.6, page 12-12
•
Replacing Hard Disks on an Existing Solaris 8 Platform, page 12-17
Conditions for Migration
Your hardware and software environment must meet the following conditions before you can use the
procedures provided below to migrate your software to Solaris 8:
1.
Your system must have at least 2 disks.
2.
The disks in the system must be at least 18 GB in size.
3.
Your system must not be running a 32-bit kernel. To verify this do the following:
a. Enter the following UNIX command:
# isainfo -b
If the system returns the following, proceed to 3b. Otherwise, the procedure is complete.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-1
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Cautions and Notes
32
b. Enter the following to check the current kernel type:
# /usr/sbin/eeprom | grep boot-file
If the system returns the following, proceed to 3c. Otherwise the procedure is complete.
boot-file=/platform/sun4u/kernel/unix
c. The system is booting a 32-bit kernel. Check to see if the system is capable of booting a 64-bit
kernel:
# halt
ok boot -r -D kernel/sparcv9/unix
d. If so, run the following to empty the boot-file variable:
# eeprom boot-file=""
or
# eeprom boot-file="kernel/sparcv9/unix"
4.
You (or the person doing the upgrade) must be an experienced Solaris system administrator. You
must be familiar with system administration tasks such as mounting file systems and running tar to
save and restore files.
The following table lists the conditions and corresponding tasks you must know before the upgrade or
migration:
Table 12-1
Conditions for Upgrading or Migrating to Solaris 8 and Cisco MGC 9.2(2) and Up
Condition
Action
If you are upgrading the disk drive but not
upgrading the software...
Follow the procedure in the “Replacing Hard Disks
on an Existing Solaris 8 Platform” section on
page 12-17.
If the system is running Solaris 8 and DiskSuite... You must shut down and remove DiskSuite from
the system. See the “Removing the Solstice
DiskSuite” section on page 2-36 prior to installing
the new operating system version.
Cautions and Notes
Before starting the upgrade, consider the following cautions and note:
Caution
Before starting the upgrade, make sure the Cisco MGC software is shut down, and the system
administrator is logged in as root.
Caution
Always start the migration or upgrade from the standby box.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-2
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Required Software
Caution
Note
Verify the existing system status and make sure there are no major alarms. You must first resolve alarms
that are found before proceeding with the upgrade or migration.
The Cisco PGW 2200 PSTN Gateway (hereafter referred to as Cisco PGW 2200) is the new name for
the Cisco VSC 3000 and Cisco SC 2200. Some parts of this document may use these older names.
Required Software
You must have the following software:
•
Cisco Installation CD, which includes the new release of the Cisco MGC software.
•
Solaris 8 Software CD, Disk 1 of 2, 10/01 (or 2/02)
•
Solaris 8 Software CD, Disk 2 of 2, 10/01 (or 2/02)
•
Software Supplement for the Solaris 8 Operating Environment 10/01 (or 2/02) CD-ROM
If Veritas Volume Manager is not running on the platform, the following software is also required for
the backout procedure:
•
Cisco Installation CD, which includes the version of the Cisco MGC software that was originally
installed on your system.
•
Operating Environment Installation CD, part number 704-6914-10
•
Solaris 2.6 5/98 CD
Backing Up System Data
To back up system data:
Step 1
Enter the following command:
cd /opt/CiscoMGC/var/log
mkdir Solaris8
cd Solaris8
Step 2
Use an editor (such as vi) create a file called sys_tarfiles and add the following list of files to sys_tarfiles:
vi sys_tarfiles
Note
Each of the following files must be on a separate line with no leading or trailing space or tab
characters.
If an individual file in the list does not exist, an error is generated. This error can be safely
ignored.
Use ls /etc/hostname.* to determine which hostname files exist, and adjust the following list if
necessary.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-3
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Backing Up the Main Memory Database
Add the following file names to sys_tarfiles:
/etc/default
/etc/hostname.hme0
/etc/hostname.hme1
/etc/inet/hosts
/etc/inet/netmasks
/etc/inet/ntp.conf
/etc/nsswitch.conf
/etc/shadow
/etc/resolv.conf
/etc/defaultrouter
/etc/passwd
/etc/group
/etc/hosts.equiv
Step 3
Save the sys_tarfiles file. Enter the following command:
tar cvf sys.tar -I sys_tarfiles
This completes the procedures for backing up system data. Continue to the following section, Backing
Up the Main Memory Database.
Backing Up the Main Memory Database
To back up the main memory database:
Step 1
Save the main memory database information. Create a backup database by entering the following
command:
Note
Steps 1, 2, and 3 require that you are logged in as mgcusr.
Note
Some commands are specific to the main memory database and must be in your execution path;
if it is not, then you must specify the full path to the command. This path will differ, depending
on whether your system is running Cisco MGC Software Release 7.x or 9.x. Both sets of
commands are listed below. Choose the one that is appropriate for your system.
/opt/CiscoMGC/local/backupDb.sh /opt/CiscoMGC/etc/export.ttdb
Step 2
Type the following commands to create a migration file and press Enter:
a.
For systems running Release 7.x of the Cisco MGC software:
/opt/TimesTen32/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb
b.
For systems running Release 9.x of the Cisco MGC software:
/opt/TimesTen4.1/32/bin/ttMigrate -c DSN=howdydb /opt/CiscoMGC/etc/migrate.ttdb
Step 3
Create a main memory database version file which is used when the new Cisco MGC software is
installed. Start by running the main memory database version command. Then create a file with the
version information, as shown in the following example. The version command will produce an output
line similar to the following:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-4
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Backing Up the Cisco MGC Configuration Files
#
#
#
#
#
a.
TimesTen Release 6.7.8 build time July 4, 1776 12:13:14
The version file should have the number "678" (no dots) and nothing else.
Create the file like this:
echo "678" >/opt/CiscoMgc/etc/version.ttdb
Replace 678 with the version information shown in the version command
Again, the version command will differ depending on the MGC release.
Enter the following commands for systems running Release 7.x of the Cisco MGC software:
rm -f /opt/CiscoMGC/etc/version.ttdb
/opt/TimesTen32/32/bin/ttVersion
[ output = "TimesTen Release x.y.z build time... ]
echo "xyz" >/opt/CiscoMGC/etc/version.ttdb
# Replace xyz with
# version output
b.
Enter the following commands for systems running Release 9.x of the Cisco MGC software:
rm -f /opt/CiscoMGC/etc/version.ttdb
/opt/TimesTen4.1/32/bin/ttVersion
[ output = "TimesTen Release x.y.z build time... ]
echo "xyz" >/opt/CiscoMGC/etc/version.ttdb # Replace xyz with
# version output
Step 4
Verify whether the backup is successful. Enter the following commands to make sure the export.ttdb,
migrate.ttdb, and version.ttdb main memory database files are present:
cd /opt/CiscoMGC/etc
ls *.ttdb
This completes the procedures for backing up the main memory database. Continue to the following
section, Backing Up the Cisco MGC Configuration Files.
Backing Up the Cisco MGC Configuration Files
To back up the Cisco MGC configuration files:
Note
Step 1
You should be logged in as root to do this procedure.
Save the MGC configuration data.
If you are using Cisco MNM or BAMS, save the snmpd.cnf file (located in /opt/CiscoMGC/snmp) before
the migration starts. Enter the following command:
cp /opt/CiscoMGC/snmp/snmpd.cnf /opt/CiscoMGC/dialPlan
Step 2
Type the following command to move to the Cisco MGC directory and press Enter:
cd /opt/CiscoMGC
tar cvf /opt/CiscoMGC/var/log/Solaris8/MGC.tar ./etc ./dialPlan
Step 3
Use the following command to verify that configuration files were successfully backed up (the MGC.tar
and sys.tar files must be present):
cd /opt/CiscoMGC/var/log/Solaris8
ls
Step 4
At this point, all the required data has been saved in tar files in /opt/CiscoMGC/var/log/Solaris 8.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-5
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Installing Solaris 8
Caution
a.
These files must now be moved to a blank tape and remote machine so they can be recovered
after Solaris 8 is installed. You are responsible for providing the mechanism and storage
location.
Local tape drive: Use the following procedure to store the files on a local tape drive.
cd /opt/CiscoMGC/var/log/Solaris8
tar cvf /dev/rmt/0 MGC.tar sys.tar
b.
Remote file server: Using the ftp utility, transfer the MGC.tar and sys.tar files from the
/opt/CiscoMGC/var/log/Solaris8 directory to a remote file server. Make sure to use the binary mode
of ftp and verify the files are successfully transfer to the remote file server before continuing.
File back up is now complete. Continue to the next section, Installing Solaris 8.
Installing Solaris 8
At this point, the system data and MGC Configuration data have been saved in tar files on a tape and
remote file server.
To install Solaris 8:
Step 1
Shut down the system, using the following command:
/usr/sbin/shutdown -g0 -i0
Step 2
Wait for the system to return to the boot prompt then load the Solaris 8 Operating System CD.
Note
If you are replacing the hard disks, you should power off the system, label, and remove the
existing disks using proper anti-static procedures. Install the new disk drives in the same slots
the new origin disk drives were located. Finally, power up the system. Refer to the Sun System
Manual for your platform.
Step 3
Boot the system from the CD-ROM.
Step 4
Install the Solaris 8 operating system. Refer to the “Installing the Solaris 8 Operating System” section
on page 2-15 and follow the procedures up to Step 27 on page 2-31.
Note
Caution
After the Cisco MGC 9.2(2) is installed, you should configure the second disk first, then install
the Solaris 8 Patch Cluster (CSCOh015).
Do not format or modify the second disk drive. Unless the disk drives were replaced in Step 2
above, the second disk contains the original Solaris 2.6 system if Veritas Volume Manager is
being used. The second disk will be used as a fallback in case of a failure in the Solaris 8
upgrade.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-6
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Restoring Data Files
Once the Solaris 8 Operating System is installed, continue to the following section, Restoring Data Files.
Restoring Data Files
There are two methods to restore data that was saved in the section Backing Up the Cisco MGC
Configuration Files, page 12-5.
The first method, described in the “Restoring Data Files from Remote Server or Local Tape Drive”
section on page 12-7, retrieves the files from the tar file that was saved to the remote server or local tape
drive.
The second method, described in the “Restoring Data Files from the Log Partition of the Second Disk”
section on page 12-8, retrieves the files from the log partition on the second disk. This can only be used
if the second disk is set up as the log and spool partitions.
Restoring Data Files from Remote Server or Local Tape Drive
Follow these instructions to restore the system data (sys.tar) and MGC configuration files (MGC.tar) on
the platform once Solaris 8 is up and running on the primary disk:
Step 1
Log in as root and type the following command to move the MGC configuration files to the /tmp
directory. Press Enter.
# cd /tmp
Step 2
Type the following commands to create a mount point. Press Enter.
# mkdir saved
# cd /tmp/saved
Step 3
Store data files:
Local tape drive: Enter the following command to store the files on a local tape drive.
a.
# tar xvf /dev/rmt/0
Remote file server: Using the ftp utility, transfer the MGC.tar and sys.tar files from the remote file
server to the /tmp/saved directory. Make sure to use the binary mode of ftp and verify the files are
successfully transfer to the remote file server before continuing.
b.
Step 4
Type the following command and press Enter to extract the saved data. These files should be placed in
the /tmp/saved directory.
# tar xvf /tmp/saved/sys.tar
Note
Step 5
# Extract system files
Verify all the restored system files through more or vi.
Type the following commands and press Enter to create an MGC directory and extract Cisco MGC data
files:
#
#
#
#
#
cd /opt
mkdir CiscoMGC
# Create MGC directory
cd /opt/CiscoMGC
cp /tmp/saved/MGC.tar MGC.tar
tar xvf MGC.tar
# Extract MGC data files
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-7
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Restoring Data Files
Step 6
Verify that both etc and dialPlan directories are present.
Step 7
Type the following command and press Enter to reboot the platform:
# /usr/sbin/shutdown -g0 -i6
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
This completes the procedures for restoring the system data (sys.tar) and MGC configuration files
(MGC.tar). Continue to the following section, “Installing the Cisco MGC Software and Patches” section
on page 12-9.
Restoring Data Files from the Log Partition of the Second Disk
The following procedure will restore system data and Cisco MGC configuration files from the log
partition of the second disk when Solaris 8 is up and running on the primary disk. It can only be used if
the second disk contains the MGC log and spool partitions (i.e /opt/CiscoMGC/var/log and
/opt/CiscoMGC/var/spool):
Step 1
Login as root and enter the following command to move to the /tmp directory:
# cd /tmp
Step 2
Enter the following command to create a mount point:
# mkdir saved
Step 3
Enter the following command to mount saved data on /tmp/saved:
# mount –F ufs /dev/dsk/c0t1d0s3 /tmp/saved
Step 4
Enter the following command to extract saved system files:
# tar xvf /tmp/saved/Solaris8/sys.tar
Step 5
Enter the following commands to create an MGC directory:
# cd /opt
# mkdir CiscoMGC
# cd /opt/CiscoMGC
Step 6
Enter the following command to extract the MGC data files:
# tar xvf /tmp/saved/Solaris8/MGC.tar
Step 7
Unmount the /tmp/saved partition:
# umount /tmp/saved
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-8
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Installing the Cisco MGC Software and Patches
Step 8
Type the following command and press Enter to reboot the platform:
# /usr/sbin/shutdown -g0 -i6
Note
If you have installed the Solaris DiskSuite package (CSCOh016) on your system, the messages
below are displayed during system boot-up. They are normal Solaris DiskSuite start-up
messages and do not indicate any problem with your system.
WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed
This completes the procedures for restoring the system data (sys.tar) and MGC configuration files
(MGC.tar). Proceed to “Installing the Cisco MGC Software and Patches” to install the Cisco MGC
software.
Installing the Cisco MGC Software and Patches
The Cisco MGC software must be installed. For installation procedures, refer to the “Installing the Cisco
MGC Software 9.2(x) and Higher Releases” section on page 3-3.
For the most recent released Cisco MGC patches, refer to the Release Notes for the Cisco Media
Gateway Controller Software Release 9.2(2) located at the following url:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn922.htm
Caution
Make sure to stop the older software version in the active box before starting the newly-installed Cisco
MGC 9.2(2) software. Use the command /etc/init.d/CiscoMGC stop to stop the older software version
in the active box.
After installing the latest Cisco MGC software release and patches, you can now start the Cisco MGC
software by entering the following command:
# /etc/init.d/CiscoMGC start
Once the Cisco MGC Software is verified to be operating properly, proceed to migrate on the box that
has the older software version by following the procedures starting with “Backing Up System Data”
section on page 12-3.
After the two boxes are migrated and you successfully performed the failover test, you can configure the
second disk by using the procedure in the “Configuring a Second Disk” section on page 12-9 on the two
boxes.
Configuring a Second Disk
After installing the Cisco MGC Software and the post-migration testing is successful, the second disk
can be configured as a mirror of the first disk or as additional storage for the Cisco MGC Software.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-9
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Configuring a Second Disk
Note
Always start with the standby box. After the standby box is configured, perform switchover on the active
box (using the sw-over::confirm command). Perform the same procedure on the new standby box.
Solstice DiskSuite Installation
To mirror the first disk to the second disk using DiskSuite, follow the procedure in the section Installing
the Solstice DiskSuite (CSCOh016), page 2-32.
Log and Spool Software Installation
To use the second disk as additional storage for the Cisco MGC Software, the following procedure
should be followed.
Step 1
Log in to the platform as root and stop the Cisco MGC Software.
# /etc/init.d/CiscoMGC stop
Step 2
Rename the existing log and spool directories.
# cd /opt/CiscoMGC/var
# mv log log.save
# mv spool spool.save
Step 3
Follow the procedure in “Installing the Log and Spool File Systems (CSCOh005)” section on page 2-37
to install the Log/Spool package (CSCOh005).
Step 4
Move the data from saved directories to the new partitions on disk 1.
#
#
#
#
Step 5
cd /opt/CiscoMGC/var
mv log.save/* log
mv log.save/.*.seq log
mv spool.save/* spool
Remove the save directories.
# cd /opt/CiscoMGC/var
# rmdir log.save spool.save
Step 6
Change the owner, group, and file permissions of the var and spool directories to match the
/opt/CiscoMGC/var directory.
# cd /opt/CiscoMGC/var
# ls -ld . log spool
drwxrwxr-x
5 mgcusr
mgcgrp
1024 May
8 23:43 .
drwxr-xr-x
drwxr-xr-x
root
root
512 May
3584 May
8 23:42 log
8 22:54 spool
1024 May
512 May
3584 May
8 23:43 .
8 23:42 log
8 22:54 spool
3 root
3 root
# chown mgcusr:mgcgrp log spool
# chmod 775 log spool
# ls -ld . log spool
drwxrwxr-x
drwxrwxr-x
drwxrwxr-x
5 mgcusr
3 mgcusr
3 mgcusr
mgcgrp
mgcgrp
mgcgrp
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-10
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Installing the Alarm Software
Step 7
Start the Cisco MGC Software.
# /etc/init.d/CiscoMGC start
The Log and Spool software installation is now complete.
Installing the Alarm Software
Note
You must install this software if your site design requires using an external alarm relay unit.
If you are installing Solaris 8 on a Netra t 1120/1125, use the procedure in the “Alarm Card Software
Installation for Netra t 1120/1125” section on page 2-50 for alarm card software installation. For all
other platforms, use the procedure in the “Installing Lights Out Management Software” section on
page 2-47.
Installing the Solaris 8 Patch Cluster (CSCOh015)
Note
Always start with the standby box. After the standby box is configured, perform switchover on the active
box (using the sw-over::confirm command). Perform the same procedure on the newly-standby box.
Refer to “Installing the Solaris 8 Patch Cluster (CSCOh015)” section on page 2-51 for installation
procedures.
Restoring the SNMP Configuration on PGW for Cisco MNM and
BAMS
Note
Perform the following procedure on both the active and standby boxes.
To restore the SNMP configuration:
Step 1
Note
Copy back the saved snmpd.cnf file. Enter the following command:
You should be logged in as mgcusr to do this procedure.
cp /opt/CiscoMGC/dialPlan/snmpd.cnf /opt/CiscoMGC/snmp
Step 2
Determine the process ID. From the Sun Solaris command line, enter the following command:
ps -ef | grep snmpdm
Text similar to the following is displayed:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-11
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Falling Back to Solaris 2.6
root 565 1 0 Mar 20 ? 0:01 /opt/CiscoMGC/bin/snmpdm -d
mgcusr 7463 23729 0 12:33:04 pts/13 0:00 grep snmpdm
The process ID of the snmpdm daemon is the second field on the line that ends with snmpdm -d. In this
example, the process ID of the SNMP daemon is 565.
Step 3
Note
Terminate and restart the SNMP daemon. Enter the following command:
Switch to root to do this command.
kill -9 <SNMP-daemon-process-ID>
Note
The SNMP daemon restarts automatically after termination.
This completes the procedure for restoring snmp configuration file on PGW for Cisco MNM and BAMS.
Falling Back to Solaris 2.6
If the disk drives were replaced during the migration to Solaris 8, follow the procedures in the “Falling
Back to Solaris 2.6 If Hard Drives Were Replaced During the Upgrade” section on page 12-12.
If the disk drives were not replaced during the migration to Solaris 8 and Veritas Volume Manager was
used to mirror the disk drives, follow the procedures in the “Falling Back to Solaris 2.6 on the Second
Disk Drive” section on page 12-12.
Otherwise, if neither of the above options can be used to back out to the Solaris 2.6 operating system
and the original MGC software configuration has to be restored, follow the procedures in the “Restoring
the Original Cisco MGC Software” section on page 12-17.
Falling Back to Solaris 2.6 If Hard Drives Were Replaced During the Upgrade
If you replaced the hard disks as part of the upgrade to the Solaris 8 operating system and now need to
fall back to Solaris 2.6, do the following procedure:
Step 1
Stop the operating system and power down the platform.
/usr/sbin/shutdown –g0 -i5
Step 2
Remove the new disk drives and install the original disk drives in their original locations using proper
anti-static procedures. Refer to the Sun System manual for your platform.
Step 3
Power up the system.
Falling Back to Solaris 2.6 on the Second Disk Drive
If the upgrade is not successful, you can fall back to the original Solaris 2.6 environment, as follows:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-12
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Falling Back to Solaris 2.6
Step 1
Stop the operating system.
# /usr/sbin/shutdown –g0 -i0
Step 2
From the ok prompt, boot the secondary boot disk.
ok boot disk1
Step 3
Log in as mgcusr and verify that the system boots Solaris 2.6 and the MGC software starts properly.
% uname –r
5.6
Note
“5.6” indicates that the system is running the Solaris 2.6 operating system.
% mml
mml> rtrv-ne
Verify that the correct version of the MGC software is running.
Step 4
Log in again as root and start vxdiskadm.
# vxdiskadm
A screen similar to the following is displayed:
Volume Manager Support Operations
Menu: VolumeManager/Disk
1
2
3
4
5
6
7
8
9
10
11
12
13
list
Add or initialize one or more disks
Encapsulate one or more disks
Remove a disk
Remove a disk for replacement
Replace a failed or removed disk
Mirror volumes on a disk
Move volumes from a disk
Enable access to (import) a disk group
Remove access to (deport) a disk group
Enable (online) a disk device
Disable (offline) a disk device
Mark a disk as a spare for a disk group
Turn off the spare flag on a disk
List disk information
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform
Step 5
Type 4 to remove a disk for replacement.
Remove a disk for replacement
Menu: VolumeManager/Disk/RemoveForReplace
Use this menu operation to remove a physical disk from a disk
group, while retaining the disk name. This changes the state
for the disk name to a "removed" disk. If there are any
initialized disks that are not part of a disk group, you will be
given the option of using one of these disks as a replacement.
Step 6
Type list to list all disks
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-13
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Falling Back to Solaris 2.6
Enter disk name [<disk>,list,q,?] list
Disk group: rootdg
Step 7
DM NAME
DEVICE
TYPE
PRIVLEN
PUBLEN
STATE
dm rootdiska
dm rootdiskb
c0t1d0s2
sliced
4711
NODEVICE
35363560 -
Type rootdiska at the following prompt:
Enter disk name [<disk>,list,q,?] rootdiska
The following volumes will lose mirrors as a result of this
operation:
opt rootvol swapvol usr var
No data on these volumes will be lost.
The requested operation is to remove disk rootdiska from disk group
rootdg. The disk name will be kept, along with any volumes using
the disk, allowing replacement of the disk.
Select "Replace a failed or removed disk" from the main menu
when you wish to replace the disk.
Step 8
Type Enter at the following prompt to continue:
Continue with operation? [y,n,q,?] (default: y)
Removal of disk rootdiska completed successfully.
Step 9
Type n at the following prompt and then q to quit vxdiskadm:
Remove another disk? [y,n,q,?] (default: n) n
Volume Manager Support Operations
Menu: VolumeManager/Disk
1
2
3
4
5
6
7
8
9
10
11
12
13
list
Add or initialize one or more disks
Encapsulate one or more disks
Remove a disk
Remove a disk for replacement
Replace a failed or removed disk
Mirror volumes on a disk
Move volumes from a disk
Enable access to (import) a disk group
Remove access to (deport) a disk group
Enable (online) a disk device
Disable (offline) a disk device
Mark a disk as a spare for a disk group
Turn off the spare flag on a disk
List disk information
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform: q
Goodbye.
Step 10
Use the vxdisk command to verify that rootdiska is removed.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-14
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Falling Back to Solaris 2.6
# vxdisk list
Step 11
Shut down and boot from disk1.
# init 0
ok boot disk1
Step 12
Log in as root and run vxdiskadm.
# vxdiskadm
Step 13
Type 5 to replace a failed disk.
Replace a failed or removed disk
Menu: VolumeManager/Disk/ReplaceDisk
Use this menu operation to specify a replacement disk for a disk
that you removed with the "Remove a disk for replacement" menu
operation, or that failed during use. You will be prompted for
a disk name to replace and a disk device to use as a replacement.
You can choose an uninitialized disk, in which case the disk will
be initialized, or you can choose a disk that you have already
initialized using the Add or initialize a disk menu operation.
Step 14
Type list at the following prompt:
Select a removed or failed disk [<disk>,list,q,?] list
Disk group: rootdg
Step 15
DM NAME
DEVICE
TYPE
PRIVLEN
PUBLEN
STATE
dm rootdiska
-
-
-
-
REMOVED
Type rootdiska at the following prompt:
Select a removed or failed disk [<disk>,list,q,?] rootdiska
Step 16
Type list at the following prompt:
Select disk device to initialize [<address>,list,q,?] list
DEVICE
c0t0d0
c0t1d0
DISK
rootdiskb
GROUP
rootdg
STATUS
error
online
Type c0t0d0 to select disk device to initialize
The following disk device has a valid VTOC, but does not appear to have
been initialized for the Volume Manager. If there is data on the disk
that should NOT be destroyed you should encapsulate the existing disk
partitions as volumes instead of adding the disk as a new disk.
Output format: [Device_Name]
c0t0d0
Step 17
Type n and Enter when asked to encapsulate the disk. Type y and Enter when asked if you wish to
initialize the disk. Type y and Enter when asked to continue:
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
The requested operation is to initialize disk device c0t0d0 and
to then use that device to replace the removed or failed disk
rootdiska in disk group rootdg.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Falling Back to Solaris 2.6
Type Y at the following prompt:
Continue with operation? [y,n,q,?] (default: y) y
Replacement of disk rootdiska in group rootdg with disk device
c0t0d0 completed successfully.
This will begin recovery of the disk and the mirrors will re-synchronize automatically.
Step 18
Type n and Enter when asked to replace another disk the disk. Type q and Enter to quit:
Replace another disk? [y,n,q,?] (default: n) n
Volume Manager Support Operations
Menu: VolumeManager/Disk
1
2
3
4
5
6
7
8
9
10
11
12
13
list
Add or initialize one or more disks
Encapsulate one or more disks
Remove a disk
Remove a disk for replacement
Replace a failed or removed disk
Mirror volumes on a disk
Move volumes from a disk
Enable access to (import) a disk group
Remove access to (deport) a disk group
Enable (online) a disk device
Disable (offline) a disk device
Mark a disk as a spare for a disk group
Turn off the spare flag on a disk
List disk information
?
??
q
Display help about menu
Display help about the menuing system
Exit from menus
Select an operation to perform: q
Goodbye.
Note
Step 19
Allow enough time to let both disks synchronize. Depending on the system, it may take 5 to 6
hours.
Use the vxprint command to make sure disk0 is re-mirrored to disk1. When this is complete, shut down
the platform and boot.
# vxprint –ht
# init 0
ok boot
Step 20
Repeat Step 3 to verify that the correct software is running.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-16
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Replacing Hard Disks on an Existing Solaris 8 Platform
Restoring the Original Cisco MGC Software
If the neither of the previous two sections can be used to back out to the system, use the following
procedure to restore the original MGC software configuration to the platform.
Step 1
Install Solaris 2.6 Operating System using the procedures in the “Installing the Solaris 2.6 or 2.5.1
Operating System on Netra t 1120/1125, t 1400/1405 and t 100/105” section on page 8-6.
Step 2
Restore the data files using the procedures in “Restoring Data Files from Remote Server or Local Tape
Drive” section on page 12-7.
Step 3
Install the original Cisco MGC Software using the procedures in the “Installing the Cisco MGC Software
Release 9.1(5)” section on page 7-3.
Replacing Hard Disks on an Existing Solaris 8 Platform
This chapter describes the scenario for replacing the hard disks on an existing platform running the
Solaris 8 operating system and Cisco MGC 9.2(2) software.
Backup Procedure
Caution
Before restoring the mgcbackup file, you must first install the same Cisco MGC software release and the
patch level that was originally on the platform. You must also install the same version of DiskSuite and
the Cisco Security Package (CSCOh013.pkg) if these were originally on the platform. For installation
procedures, refer to the “Installing the Solstice DiskSuite (CSCOh016)” section on page 2-32 and
“Installing the Cisco Security Package (CSCOh013)” section on page 3-16.
To back up the system:
Step 1
Log in as root and stop the Cisco MGC application.
# /etc/init.d/CiscoMGC stop
Step 2
Back up the system.
a.
Local Tape Backup: Using the mgcbackup utility, back up the system to the local tape drive.
# /opt/CiscoMGC/local/mgcbackup –d /dev/rmt/0
b.
Remote File Server Backup: Using the mgcbackup utility, back up the system to local directory.
Use the mgcbackup utility to list the filename of the last backup, then use ftp to transfer the file to
a remote file system.
# /opt/CiscoMGC/local/mgcbackup –d /opt/CiscoMGC/var/log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-17
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Replacing Hard Disks on an Existing Solaris 8 Platform
The backup file is stored in the specified directory path in the following format:
mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup.tar
Note
Where:
• hostname is the name of the Cisco MGC host, such as MGC-01.
• yyyymmdd is the date the backup file is created, in a year-month-day format, such as 20011130.
• hhmmss is the time the backup file is created, in an hour-minute-second format, such as 115923.
# /opt/CiscoMGC/local/mgcbackup -l
Caution
Step 3
You must now move the backup file to a remote filer server using the ftp program so it can be
recovered after Solaris 8 is installed on the new disk. You are responsible for providing the
mechanism and storage location.
Stop the operating system and power down the platform.
# /usr/sbin/shutdown –g0 –i5
System backup is now complete.
Hard Disk Replacement Procedure
Caution
Be sure to follow the appropriate anti-static procedures when performing this procedure.
To replace the hard disk:
Step 1
Label the hard disks with their current locations and remove them from the system. Refer to your
platform’s Sun System manual for the proper procedure.
Step 2
Install the new hard disks in the same slots as the existing hard disks. Refer to your platform’s Sun
System manual for the proper procedure.
Loading the Solaris 8 operating system
Power on the platform and follow the procedures in the “Installing the Solaris 8 Operating System”
section on page 2-15 through the “Installing the Solaris 8 Patch Cluster (CSCOh015)” section on
page 2-51 to install the Solaris 8 operating system.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-18
OL-1150-15
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Replacing Hard Disks on an Existing Solaris 8 Platform
Installing the Cisco MGC Software
Caution
Install DiskSuite and the same Cisco MGC release and Cisco Security Package (CSCOh013.pkg) patch
level if they were originally on the box.
Install the same release and patch level of Cisco MGC software that was originally on the box, using the
procedures provided in the “Installing the Cisco MGC Software 9.2(x) and Higher Releases” section on
page 3-3.
Restoring the System
Step 1
To restore the system:
a.
Local Tape Backup: Using the mgcrestore utility, enter the following command to restore the
system from the local tape drive:
# /opt/CiscoMGC/local/mgcrestore –d /dev/rmt/0
b.
Remote File Server Backup: Using the ftp program, retrieve the file created in Step 2b. of the
Backup Procedure, page 12-17 section, and place it in the /opt/CiscoMGC/var/log directory. Using
the mgcrestore utility, restore the system.
# /opt/CiscoMGC/local/mgcrestore -d /opt/CiscoMGC/var/spool -f filename
where filename is the filename created in Step 2b. of the section Backup Procedure, page 12-17.
Step 2
Start the Cisco MGC software.
# /etc/init.d/CiscoMGC start
The hard disk replacement on an existing platform running the Solaris 8 operating system and Cisco
MGC 9.2(2) software is now complete.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
12-19
Chapter 12
Migrating to Solaris 8 and Cisco MGC 9.2 and Up
Replacing Hard Disks on an Existing Solaris 8 Platform
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
12-20
OL-1150-15
A P P E N D I X
A
XECfgParm.dat File Parameters
This appendix describes the parameters found in the XECfgParm.dat file for the Cisco MGC software
release 9.x and how they are used by the media gateway controller (MGC).
Understanding the XECfgParm.dat File Format
The XECfgParm.dat file contains system-wide as well as system tuning parameters. All fields in this file
are written in the parm = value format. It supports a hash mark (#) in the first column to denote the
entire line as a comment.
Parameters are prefixed with a quantifier to specify the domain of the parameter. An asterisk (*)
preceding the parameter indicates that the parameter setting should be used by the entire system. A
component name limits the scope to the specified component.
XECfgParm.dat parameters are arranged syntactically as follows:
facilityName.parameterName = parameterValue
Cisco MGC XECfgParm.dat Files
Facility Names
The following facility names are valid:
•
almM—Alarm Manager
•
amDmpr—Alarm / Measurement Dumper
•
cdrDmpr—CDR Dumper
•
CALL_CUTOFF_TIMER
•
cfgM—Configuration Manager
•
engine—Call processing engine
•
foverd—Failover Daemon
•
ioChanCtl—Controls all channel controllers
•
ioChanMgr—I/O Channel Managers
•
logger—Log Server
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-1
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
•
measM—Measurement Manager
•
mmdb—Main Memory Data Base Process
•
MML—MML
•
mmSAgt—Measurement Manager SNMP Agent
•
OPERSAGT—Operational SNMP Agent
•
pom—Provisioning Object Manager
•
procM—Process Manager
•
PROVSAGT—Provisioning SNMP Agent
•
replicator—Replicator
If no match is found for a facility-specific parameter, the file is searched for a match on the default
facility.
Special Parameters
•
callver—Call verification utility
•
diskmonitor—Disk monitor shell script
•
XE—Execution environment
Cisco MGC 9.x XECfgParm.dat File Parameter Definitions
The XECfgParm.dat file configuration parameters for the Cisco MGC software release 9.x are presented
alphabetically in Table A-1.
Caution
This list of parameters is provided as a reference. Do not edit any parameters unless they are listed in
the following table or unless you have been instructed to do so by Cisco technical support; otherwise,
your system might not work as intended.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-2
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters
Configuration Parameter
Definition
*.actiononchargetableaccessfailure
Allows you to specify the action to take when there is a
failure to access the meter pulse tariff table.
added in Release 9.5(2)
Default: 0
Valid values: 0 (Continue Call) and 1 (Release Call).
*.AllISDNLinksFailCausesFailover
added in Release 9.5(2)
Controls the severity level of the All ISDN IP Conn Fail
alarm.
Default: false
Valid values: false (alarm severity is Major) and true (alarm
severity is Critical).
This property should be set to true if your Cisco MGC hosts
are in separate geographic locations. You can also set this
parameter to true if your system is not processing SS7 calls
and you want your system to perform an automatic
switchover should all of the ISDN IP connections fail.
*.AllLinksFailCausesFailover
added in Release 9.4(1)
Controls the severity level of the following alarms:
•
All C7IP Links Fail
•
All M3UA Assoc Fail
•
All SUA Assoc Fail
Default: false
Valid values: false (alarm severity is Major) and true (alarm
severity is Critical).
This property should be set to true if your Cisco MGC hosts
are in separate geographic locations. You can also set this
parameter to true if your system is not processing SS7 calls
and you want your system to perform an automatic
switchover should all of the links fail.
*.autonomous
Enables a process, for example the engine, to be started
without the system.
Default: false
Note
*.chargingmode
added in Release 9.5(2)
Do not change this value.
Allows you to specify the charging mode for non-Intelligent
Network (IN) calls which determines the treatment of
received Metered Pulse Messages (MPMs).
Default: 1
Valid values are: 1 (AddOnCharge), 2 (ReplaceCharge), and
3 (FreeOfCharge).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-3
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.chargingtarifftype
Allows you to specify which type of tariff table (Meter Pulse
or Tariff-Rate/Scale-Factor) is to be accessed in the absence
of a tariff table identifier in the charge result.
added in Release 9.5(2)
Default: 1
Valid values are: 0 (tariff-rate/scale-factor) (default) and 1
(meter pulse).
*.chkPtPort
Port number used between peer components or processes for
check-pointing.
Value: Any unused port number.
Default: 2001
Leave this value as the default.
Note
If you have two Cisco MGC hosts in a failover
configuration, both fields in the XECfgParm.dat
files should contain the same value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-4
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.ClearingLocation
Specifies whether to override the default location field in the
call context for any call, regardless of which network device
released the call. This enables you to define a default
location in Release messages for any call, which can differ
from the default location set in the type definition of the
protocol.
This property has precedence over the value set in
the *.DefaultLocation parameter.
Note
Values:
•
0 = Normal mapping behavior, LCM will not override
the Clearing Location field in Call Context.
•
1 = LCM will override the Clearing Location in Call
Context with LOCATION_USER
•
2 = LCM will override the Clearing Location in Call
Context with LOCATION_ PRIVATE_LOCAL
•
3 = LCM will override the Clearing Location in Call
Context with LOCATION_ PUBLIC_LOCAL
•
4 = LCM will override the Clearing Location in Call
Context with LOCATION_TRANSIT
•
5 = LCM will override the Clearing Location in Call
Context with LOCATION_ PUBLIC_REMOTE
•
6 = LCM will override the Clearing Location in Call
Context with LOCATION_ PRIVATE_REMOTE
•
7 = LCM will override the Clearing Location in Call
Context with LOCATION_ INTERNATIONAL
•
8 = LCM will override the Clearing Location in Call
Context with LOCATION_ INTERWORKING
•
9 = LCM will override the Clearing Location in Call
Context with LOCATION_ LOCAL_INTERFACE
•
10 = LCM will override the Clearing Location in Call
Context with LOCATION_ LOCAL_LOCAL
•
11 = LCM will override the Clearing Location in Call
Context with LOCATION_ LOCAL_REMOTE
•
12 = LCM will override the Clearing Location in Call
Context with LOCATION_ PACKET_MANAGER
•
13 = LCM will override the Clearing Location in Call
Context with LOCATION_ UNKNOWN
Default: 0 (Normal mapping behavior)
Note
Option 13 may not be valid for all solutions.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-5
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.CPUTimerInterval
Samples the frequency of CPU utilization.
Prior to Release 9.4(1), this parameter must be set to 0
during the initial configuration of any platform with a single
CPU (including Sun Netra t 100/105, Sun Netra V 120, and
Sun Netra 120).
Default: 3000 msec (3 seconds)
Note
During the startup of the Cisco MGC software, this
parameter will be set automatically to tune the
system for optimal performance.
For Release 9.4(1) and up, this parameter is set
automatically when you specify a Cisco MGC type in the
engine.SysVirtualSwitch parameter. Any attempt to modify
this parameter is overwritten.
*.dataDir
Location of the data directory.
Default: ../var
Note
*.dataSourceName
Do not change this value.
Used by the MMDB to obtain the data source name for the
ODBC connection.
Default: howdydb
Note
*.debugLevel
Do not change this value.
Determines level of debugging detail if debugging is
initiated.
Default: high
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-6
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.DefaultLocation
Specifies whether to override the default location field in the
call context for calls released by the Cisco MGC. This
enables you to define a default location in Release messages
for calls released by the Cisco MGC, which can differ from
the default location set in the type definition of the protocol.
If the call is not released by the Cisco MGC, this
property has no impact.
Note
Values:
•
0 = Normal protocol-defined default value; LCM will
not override the default location field in call context.
•
1 = LCM will override the default location in call
context with LOCATION_USER
•
2 = LCM will override the default location in call
context with LOCATION_ PRIVATE_LOCAL
•
3 = LCM will override the default location in call
context with LOCATION_ PUBLIC_LOCAL
•
4 = LCM will override the default location in call
context with LOCATION_TRANSIT
•
5 = LCM will override the default location in call
context with LOCATION_ PUBLIC_REMOTE
•
6 = LCM will override the default location in call
context with LOCATION_ PRIVATE_REMOTE
•
7 = LCM will override the default location in call
context with LOCATION_ INTERNATIONAL
•
8 = LCM will override the default location in call
context with LOCATION_ INTERWORKING
•
9 = LCM will override the default location in call
context with LOCATION_ LOCAL_INTERFACE
•
10 = LCM will override the default location in call
context with LOCATION_ LOCAL_LOCAL
•
11 = LCM will override the default location in call
context with LOCATION_ LOCAL_REMOTE
•
12 = LCM will override the default location in call
context with LOCATION_ PACKET_MANAGER
•
13 = LCM will override the default location in call
context with LOCATION_ UNKNOWN
Default: 0 (Normal protocol-defined default value)
Note
Option 13 may not be valid for all solutions.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-7
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.desiredPlatformState
Determines the desired platform state.
Values:
•
master, if you have two (active and standby) Cisco
MGC hosts
•
slave, if you have two (active and standby) Cisco MGC
hosts
•
standalone, if you have a single-host system
Default: none
Note
*.disableMeas
The value used is site specific. For example, use the
values master and slave if you have two (active and
standby) Cisco MGC hosts. Enter standalone if you
have a single-host system.
Disables the collection of measurement data.
Values:
true = disables data collection
false = data is collected
Default: false
*.disablemultiplecdrs
added in Release 9.5(2)
Allows you to disable the multiple-CDRs-per-call (for
example, multiple occurrences of Answer and Release CDB
messages) for situations where the downstream billing
system does not support this feature.
Default: 1
Valid values are: 0 (multi CDRs enabled) and 1 (multi CDRs
disabled).
*.eventTrace
Used by developers only to trace events at the application
level.
*.FastConnect
Allows LCM messages to pass through.
Values:
0 = Passes all signals to LCM
1 = Disables signal to LCM for “CallProceeding” received
from NAS
2 = Disables signal to LCM for “CallProceeding” or
“Progress” received from NAS
3 = Disables signal to LCM for “Call Proceeding”,
“Progress”, or “Alerting” received from NAS.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-8
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.GWClearChannelAlgorithm
Allows the use of the clear channel 64K unrestricted data
transfer between gateways. Different gateways support
different codecs. There is a command to see all the codecs
supported on the gateway, including the clear channel codec.
For example on VISM, the command is dspcodecparams.
PGW will pass any string that is defined on it. The following
is what the command shows on VISM:
Codec Codec String Period (ms) Preference Type
1 - G.711u PCMU 10 8 0
2 - G.711a PCMA 10 7 8
3 - G.726-32K G726-32 10 5 2
4 - G.729a G729a 10 2 96
5 - G.729ab G729ab 10 1 96
6 - clr chan CCD 10 9 96
7 - G.726-16K G726-16 10 3 96
8 - G.726-24K G726-24 10 4 96
9 - G.726-40K G726-40 10 6 96
11 - G.723.1- G723H 30 10 96
12 - G.723.1a G723AH 30 11 96
13 - G.723.1- G723L 30 12 96
14 - G.723.1a G723AL 30 13 96
Values: null or the valid codec string
Default: null
*.homeDirRoot
Location of the home directory.
Default: /opt/CiscoMGC
Note
*.ioChanMgr.IPCTimer
added in Release 9.5(2)
Do not change this value.
Specifies the frequency at which the queue is scanned for
RSIP messages. When this parameter is left at its default
value (0), the system uses a base parameter value. You can
modify this parameter if a problem occurs.
Valid values: Any integer
Default value: 0
*.IP_Addr1
IP address of interface 1; used for signaling.
*.IP_Addr2
IP address of interface 2; used for signaling.
*.IP_Addr3
IP address of interface 3 (if installed); used for signaling.
*.IP_Addr4
IP address of interface 4 (if installed); used for signaling.
*.ipAddrLocalA
First local IP address; used for checkpointing and failover
heartbeats if you have active/standby MGC hosts.
Note
*.ipAddrLocalB
This is typically the same value as *.IP_Addr1.
Second local IP address; used for checkpointing and failover
heartbeats if you have active/standby MGC hosts.
Note
If your configuration does not use an external card,
leave this setting as the default value: 0.0.0.0.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-9
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.ipAddrPeerA
First corresponding peer IP address; used for checkpointing
and failover heartbeats.
Note
*.ipAddrPeerB
Second corresponding peer IP address; used for
checkpointing and failover heartbeats.
Note
*.IP_NextHop1
*.IP_NextHop2
*.IP_NextHop3
*.IP_NextHop4
*.IP_NextHop5
*.IP_NextHop6
*.IP_NextHop7
*.IP_NextHop8
If you have two Cisco MGC hosts in a failover
configuration, this value is the IP address of the
second host.
If your configuration does not use an external card,
leave this setting as the default value, 0.0.0.0.
Specifies the IP addresses of up to eight next hop counters.
These IP addresses are used when the next hop router IP
addresses on the Cisco PGW hosts do not match.
Default: 0.0.0.0
Valid values: An IP address expressed in dotted decimal
notation.
added in Release 9.4(1)
*.IUA.maxNasExtNodes
added in Release 9.4(1)
Specifies the maximum number of external nodes that can be
defined with an ISDN signaling type of IUA. This number
also represents the maximum number of IUA associations
that can be provisioned.
Valid value: 256
Note
*.IUA.maxNasPathsPerExtNode
added in Release 9.4(1)
Do not change this value.
Specifies the maximum number of NAS signaling services
that can be assigned to each external node with an ISDN
signaling type of IUA.
Valid value: 112
Note
*.IUA.maxNasPaths
added in Release 9.4(1)
Do not change this value.
Specifies the maximum number of IUA signaling services
that can be provisioned.
Valid value:1500
Note
Do not change this value.
*.LISupport
Enables Cisco PGW 2200 to be used for Lawful Intercept.
added in Release 9.5(2)
Note
Set this parameter to true to enable Cisco PGW 2200
support for Lawful Intercept.
Default: false
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-10
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.logDirectory
Location of the active and rotated log files.
Default: ../var/log
Make sure the log file has write permission for the
LogServer.
Note
*.logFileNamePrefix
Combined with the .log extension, defines the filename for
log files.
Default: platform
Example: engine
This setting can also redirect process messages from
the default log file to a specified log file. For
example, engine.logFileNamePrefix = engine
instructs the log server to redirect messages from the
engine process to the dedicated engine.log file. This
functions with or without *.logDirectory.
Note
*.logMsgDrop
Controls whether the log server drops debug-level messages
when the UNIX domain socket used for log server
communication is full.
Values:
•
true = debug messages are dropped
•
false = debug messages are not dropped
Default: true
Caution
If you set this parameter to false for the engine
and the engine logging level is Debug, the system
can fail at high call rates.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-11
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.logPrio
Defines the initial default logging level used by logging
clients when sending messages to the logging server. Use the
set-log MML command to change logging levels after
installation. You can specify different logging levels for
each process. For example, engine.logPrio = Info
This setting is the only way to modify the logging
level of the current MML process. The set-log
command does not affect current MML process
logging levels.
Note
This parameter provides debug level LogPrio support in
XECfgParm.dat for individual channel controllers. You can
use the following to turn on IOCC logging:
•
SS7.logPrio = Debug
•
EISUP.logPrio = Debug
•
MGCP.logPrio = Debug
•
ISDNIP.logPrio = Debug
•
ISDNL3.logPrio = Debug
•
SIP.logPrio
•
TALI.logPrio = Debug
•
TCAP.logPrio = Debug
Caution
= Debug
Be sure to use the actual process name, not the
MML name, of the channel controller. Note that
the IOCC name is case-sensitive.
Values:
•
Debug—Used only for detailed debugging messages.
Logging at this priority is not recommended during
production because this causes a large volume of
messages to be logged, which degrades system
performance and can cause failover problems.
•
Trace—These messages capture protocol traffic. This
priority is used for debugging.
•
Info—These messages indicate an operation that is
proceeding as expected.
•
Warning—These messages indicate a problem exists
that does not prevent the system from operating. This is
the normal, default logging level for production.
•
Error—These messages indicate an unexpected error
that is recoverable but degrades performance.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-12
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
*.logPrio (continued)
Definition
•
Critical—These messages indicate errors so severe that
a process cannot continue operating.
Default (Release 7.3 & earlier): Warning
Default (Release 7.4 & later): Error
Note
*.LongCallTime
Do not change this value unless you are debugging.
Used to generate ongoing Call Data Block (CDB) 1060.
CDB 1060 (on-going call event) indicates a long call in
progress.
Default: 21600000 milliseconds (6 hours)
Minimum value required: 60000 milliseconds (60 seconds)
Note
Typically, you should leave the value 21600000
milliseconds (6 hours) as the default. You can
change it, if necessary, based on billing
requirements.
If you enter a value less than the required minimum
of 60000 milliseconds, it defaults to 6 hours.
*.M3UA.maxSigServices
added in Release 9.4(1)
Defines the maximum number of M3UA signaling services.
It also defines the maximum number of M3UA routing keys.
Value: 1536
Note
Do not change this value.
*.M3UA.maxOPCs
Defines the maximum number of M3UA OPCs.
added in Release 9.4(1)
Value: 64
Note
*.M3UA.maxRoutesPerOpcDpc
added in Release 9.4(1)
Do not change this value.
Defines the maximum number of M3UA routes per
OPC/DPC pair.
Value: 2
Note
*.M3UA.maxSgp
added in Release 9.4(1)
Do not change this value.
Defines the maximum number of M3UA SS7 signaling
gateway processes.
Value: 96
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-13
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.maxLinksPerSessionSet
Sets the maximum number of SS7 links contained in a
session set. This is based on the maximum number of SS7
links in an SLT.
Value: 4
Default: 4
Note
*.maxLocationLabels
added in Release 9.6(1)
Do not change this value.
Specifies the maximum number of location labels that can be
provisioned.
Valid value: 3000
Note
*.maxNumDChansPerPort
added in Release 9.5(2)
Do not change this value.
Specifies the maximum number of D-channels that can be
provisioned per IP address or port.
Valid values: Any integer (1 to 2000)
Default value: 2000
*.maxnumRLMports
Used during provisioning to verify that the limit on the
number of unique ports for RLM links is not exceeded.
Value: 8
Default: 8
*.MgcpBehavior
Due to MGCP gateway differences in return codes, the
PGW2200 MGCPBehavior must be configured to the
appropriate value in order to properly interface with the
gateway.
Value range: Integer
•
0—No action.
– Do not use this value for switched solutions.
– Do not change this value for nailed solutions.
•
1—Value for non-IOS-based MGCP gateways such as
VISM.
•
2—Value for IOS-based gateways such as AS5300,
AS5400, and AS5350s.
Default : 0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-14
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.numberOfThreads
Prior to Release 9.4(1), the number of threads generated by
multithreaded processes such as the engine and the log
master, is specified by entering one of the following values:
Values:
•
0 = single CPU
•
1 = two CPUs
•
2 = four CPUs
Default: 0
Note
If you have a multi-CPU system (1 or 2), you must
set engine.SysGeneratedCode to true.
Note
During the startup of the Cisco MGC software, this
parameter will be set automatically to tune the
system for optimal performance.
For Release 9.4(1) and up, this parameter is set
automatically when you specify a Cisco MGC type in the
engine.SysVirtualSwitch parameter. Any attempt to modify
this parameter is overwritten.
*.OverdecadicDigitsSupported
This parameter controls the method of loading dial plan
tables and instructs the system whether to expect
overdecadic (base 16) or regular decadic (base 10) digits in
dial plans, routing, and other digit streams.
Correct setting of this parameter depends on local network
interconnect agreements and the expected data format.
Enter true to use overdecadic digits (0-F).
*.OwnClli
Common language location identifier; used for circuit query
validation when circuit queries are supported.
Value: Alphanumeric string, up to 11 characters.
Default: TTTT-SS-BB-XXX
Example: 1111-22-33-444
*.PartialCliPnoIdentity
added in Release 9.5(2)
Contains a 3-digit integer representing the PNO Identity
field of the partial CLI parameter.
Valid values: 0 (default) through 999
*.PartialCliSwitchNumber
added in Release 9.5(2)
Contains a 3-digit integer representing the Switch Number
field of the partial CLI parameter.
Valid values: 0 (default) through 999
*.PartialCliTypeOfSwitch
added in Release 9.5(2)
Contains a 2-digit integer representing the Type of Switch
field of the partial CLI parameter.
Valid values: 0 (default) through 99
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.platformId
Enables the signaling controller to run more than one
instance of the Cisco MGC software concurrently.
Default: 1
Note
Do not change this value.
*.popDataSync
Specify true if master/slave mode is being used.
*.RedirectingATree
Used to control A-number screening/analysis via A-digit
tree. This parameter allows the analysis system to use the
A-Digit tree for mapping to the BLACKLIST function on the
Redirecting CLI value. It uses the A-Digit tree to allow for
black screening on the redirecting number parameter
included in the IAM.
Currently, when the parameter MDLANumberScreening is
set to 1 in the XECfgParm.dat file, screening is done on the
redirecting number. This works when screening individual
numbers but does not allow block ranges to be screened, as
is the case when using DialPlan Screening in the Digit Tree
functions.
Use an editor such as vi to manually add the
*.RedirectingATree parameter to the XECfgParm.dat file in
the following file locations and set its value:
/opt/CiscoMGC/etc/XECfgParm.dat
/opt/CiscoMGC/etc/CONFIG_LIB/new/XECfgParm.dat
Valid values:
0 = Default. Indicates the Calling Party Number (CGPN)
that will be used for A-number screening/analysis via
A-digit tree.
1 = Indicates that the Redirecting Number should be used for
A-number screening/analysis via A-digit tree if the
incoming signaling message contains both the CPN and
Redirecting Number or just the Redirecting Number.
Note
This property is only effective when BLACKLIST is
provisioned. If Screening is data filled and this
property is set to 1, then Redirecting Number is used
for screening. However, if result types other than
BLACKLIST/SCREENING are encountered when
Redirecting Number is used during A-number Tree
Analysis, an alarm RedirectingNbrFail
(informational alarm) is generated.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-16
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.SelectTermCustGrpId
Applies only to Nailed Solutions. If this parameter is not
defined, it defaults to False.
If this parameter is set to True and CUSTGRPID of the
Originating Leg SigPath is 0000, then you must select
CUSTGRPID of the Terminating Leg SigPath.
If this parameter is set to False, you should always select
CUSTGRPID of the Originating Leg SigPath.
Default: False
*.sipFailover
added in Release 9.4(1)
Specifies whether the MGC hosts, when connected with a
SIP network, should perform an automatic switchover when
a LAN interface fails.
Default: false
Valid values: true or false
*.sm_meas_baseaddr
Indicates the memory size of the base address.
Default: 3400
Note
*.stPort
Do not change this value.
Port number used between peer components or processes.
Enter any unused port number (for example, 7000). If your
configuration uses a Cisco SLT, enter the port number on the
Cisco SLT.
*.SUA.maxSigServices
added in Release 9.4(1)
Note
If you have two Cisco MGC hosts in a failover
configuration, enter a different number for this value
in the XECfgParm.dat file on the secondary host (for
example, 7001).
Note
On a new configuration, we recommend that this
parameter be set to 0. This value allows the SLT port
to be defined using the PEERPORT parameter of
the SESSIONSET.
Note
SESSIONSET reads the port value that is defined.
However, if an *.stPort value other than 0 is defined
in XECfgParm.dat (for example, *.stPort=7001),
the SESSIONSET value gets overridden by the
value in XECfgParm.dat.
Defines the maximum number of SUA signaling services. It
also defines the maximum number of SUA routing keys.
Value: 256
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-17
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.SUA.maxOPCs
Defines the maximum number of SUA OPCs.
added in Release 9.4(1)
Value: 64
Do not change this value.
Note
*.SUA.maxRoutesPerOpcApcSsn
added in Release 9.4(1)
Defines the maximum number of SUA routes per OPC, APC,
and SSN set.
Value: 2
Do not change this value.
Note
*.SUA.maxSgp
added in Release 9.4(1)
Defines the maximum number of SUA SS7 signaling
gateway processes.
Values: 8
*.SyscheckpointEnabled
Note
Do not change this value.
Note
This parameter does not apply to Release 9.3(x).
Enables or disables checkpointing.
Values:
•
false = Disables checkpointing. Calls are not preserved
during a switchover, and status messages are not sent to
the replicator (default).
•
true = Enables checkpointing. Calls that are in the
talking state are preserved and survive a control
switchover. All status checkpointing information is sent
to the replicator on the active side.
Default: false
Note
If you have two Cisco MGC hosts in a failover
configuration, enter true. If you have a standalone
configuration, enter false.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-18
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.SysConnectDataAccess
Controls whether data access is enabled or disabled (if the
engine attempts to connect to the MMDB or to call screening
database at startup).
Values:
•
true = connect to MMDB or call screening database
•
false = do not connect to MMDB or call screening
database
Default: false
*.tablesFile
Note
This parameter must be set to true in calling
scenarios where Euro-LNP, A Number Screening, or
other features requiring real time database access are
required. Otherwise, it can remain false for an
increase in the available system memory usable for
call processing.
Note
This parameter replaces the
engine.sysScreeningCheck parameter in Cisco
MGC 7.4.
Location of the database directories.
Default: ../etc/tables.dat
Note
*.tempDir
Do not change this value.
Location of the temporary files.
Default: /tmp
Note
*.tibcoSupport
added in Release 9.5(2)
Do not change this value.
Determines whether or not the system supports a TIBCO
maintenance interface.
Default: disable
Valid values: enable or disable
*.transpathId
Identifies the local Cisco MGC host in a redundant
configuration. The IDs must be unique in an active and
standby pair.
Value: Any integer up to 2 digits.
Default (for the active host): 01
Note
If you have two Cisco MGC hosts in a failover
configuration, the number for each host must be
different in the XECfgParm.dat file.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-19
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
*.Virtual_IP_Addr1
Specifies a virtual IP address for a LAN interface. This IP
address must be within the subset of the IP address defined
for *.IP_Addr1.
added in Release 9.4(1)
Default: 0.0.0.0
Valid values: An IP address expressed in dotted decimal
notation.
*.Virtual_IP_Addr2
added in Release 9.4(1)
Specifies a virtual IP address for a LAN interface. This IP
address must be within the subset of the IP address defined
for *.IP_Addr2.
Default: 0.0.0.0
Valid values: An IP address expressed in dotted decimal
notation.
*.VSCNetworkPlacement
Determines Cisco MGC placement (AT or IXC) and bias
routing accordingly.
Values:
•
Nanp_AT
•
Nanp_IXC
•
NULL
•
0
Default: NULL
Note
CALL_CUTOFF_TIMER
If you do not set this property, all calls will route
according to called number or some other criteria,
not Carrier ID.
Provides a global system-wide timer, which is started when
a call is answered and runs for the pre-configured time.
When it expires the call is released in both directions and the
call is cleared.
Property Valid Values: 0 to 48hours (in 1 hour intervals). A
value of 0 will disable this timer.
The value set in the XECfgParm.dat file can be overridden
by the value set in the first data word of the
CALL_CUTOFF_TIMER result type.
Values: 0 - 48 hours (in 1 hour intervals)
•
0 = Disables the timer
•
1 through 48 = Specifies the time interval in 1hour
increments.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-20
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
CALL_CUTOFF_TIMER
Defines a global system-wide timer value. Timer is started
after answer for every call and runs for a pre-configured
time. When timer expires, the call is released in both
directions and is cleared. This parameter is not dynamically
reconfigurable. You must restart your system.
(modified in Release 9.5(2) patch
CSCOgs019)
Valid values:
CALL_CUTOFF_TIMER_UNITS
(added in Release 9.5(2) patch
CSCOgs019)
cfgM.recovDbFile
•
Hours: 0 (default), 1—48
•
Minutes: 0, 1—2880
•
Seconds: 0, 1—172800
Defines the unit of measurement used for the global
system-wide timer.
Valid values:
•
0 (hours) (default)
•
1 (minutes)
•
2 (seconds)
Storage location of the configuration manager recovery
information.
Default: ../var/cfgMRecovery
Note
diskmonitor.CdrRmFinished
Do not change this value.
Specifies the number of days to keep finished call detail
record (CDR) files. The default value is 0, which means that
if the Cisco BAMS is polling the Cisco MGC, CDR.bin files
remain in a user-configurable directory until they are renamed
by the Cisco BAMS (using format CDR_timestamp.finished)
and/or the disk monitor trims the file from user-configurable
directory.
Value: 0 or non-zero integer indicates days to delay before
being deleted.
Default: 0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-21
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
diskmonitor.CfgRmDirs
Specifies the maximum number of configurations that can be
stored in the configuration library. This parameter must be
manually added to the XECfgParm.dat file to activate the
disk monitor enhancement shell script. This feature allows
you to manipulate and disable the deletion of configuration
directories through XECfgParm.dat. Old configuration
directories are removed in reverse order when the indicated
limit is reached.
Default: 64
If the XECfgParm.dat file is not updated, a default value of
64 is used for the number of allowable directories. If a
default of 64 is used, the MGC will maintain up to 64
configurations in its /opt/CiscoMGC/etc/CONFIG_LIB
directory.
Entering a value of 0 disables monitoring of the number of
entries stored in the configuration library.To change the
value of this parameter, you may need to add it manually to
the XECfgParm.dat file.
The deletion of configuration directories can be disabled by
setting the diskmonitor.CfgRmDirs parameter to a value
less than or equal to 2, or greater than 64.
You can also reduce the number of allowable saved
configurations by setting the parameter to a value between 3
and 64.
Note
diskmonitor.CoreRmDays
A default value in the range of 50 to 60 should be
used to allow the disk monitor script to work
properly when using the MML command
PROV-SYNC.
Specifies how many days to keep core dump files before disk
monitor removes them automatically.
Default: 1
diskmonitor.Limit
Number of days to preserve before disk trimming is initiated.
Default: 7
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-22
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
diskmonitor.OptFileSys
List of optional file systems to monitor. Allows for optional
user-configurable file systems to be monitored. This utility
monitors the /opt file system for threshold crossing. Using this
parameter, you can monitor additional file systems (disk slices)
by setting parameter to the preferred directory, such as /tmp,
/usr or /var. The messages associated with this parameter are
sent to the platform.log file. To retrieve these messages, you
must scan the platform.log file for messages using the
following format: Filesystem file_system_name has exceeded
num percent full. For example:
Filesystem /var has exceeded 80 percent full
These files are not trimmed by disk monitor.
Default: (blank)
diskmonitor.SoftLimit
Specifies the action to be taken once the number of days
threshold set in the diskmonitor.Limit parameter is reached.
Works with diskmonitor.Threshold to prevent the disk
from filling up and stopping the Cisco MGC.
If this parameter is set to true, disk monitor deletes files day
by day until the utilization level drops below the threshold.
If this parameter is set to false, disk monitor closes and the
system generates a DISK alarm. The files can then be deleted
manually.
Default: False
Caution
diskmonitor.Threshold
If this parameter is set to FALSE and the DISK
alarm is raised, you must delete the non-required
files to bring the disk utilization below the
threshold. Otherwise, you run the risk of filling
the disk and stopping the Cisco MGC.
Erases old log files to free disk space. The threshold is the
percent the disk is full before trimming starts. Only var/log
and var/spool are monitored by default; the diskmonitor
function is local to these two directories by default.
Disk related alarms are generated only when diskmonitor is
running and the disk cannot be trimmed back to the threshold
level according to the parameter settings in XECfgParm.dat.
If the disk is 86% full and diskmonitor successfully trims
back to 80%, no alarm is generated.
Value: Any integer from 1 to 100 (% of threshold).
Default: 80
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-23
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
cdrDmpr.callDetail
Specifies that call detail record (CDR) files may be
automatically converted from binary format to ASCII,
comma-delimited format.
Default: /opt/CiscoMGC/local/cdbscript.sh
Optional: /opt/CiscoMGC/bin/converter (if binary CDR
files need to be converted to ASCII)
The default CDR file format has changed from an
ASCII format in Release 4 to a binary format in
Release 7. The ASCII file has a .csv extension.
Note
For more information on generating and viewing
CDR files, see the Cisco Media Gateway Controller
Software Release 9 Operations, Maintenance, and
Troubleshooting Guide.
dmpr.openCDR
Specifies whether the standard data dumper should write out
CDR files.
Values:
•
true = Standard data dumper opens a CDR file and log
the call data blocks (CDB).
•
false = Standard data dumper does not open a CDR file
and does not log CDBs.
Default: true
Note
engine.AuditTimerInterval
The default format for CDR files has been changed
since release 4 from an ASCII format to a binary
format. Use the dmpr.callDetail parameter to
convert the files to an ASCII format, if necessary.
Time interval in milliseconds between two batches of audits.
Value: Any positive integer.
Default: 500
Note
engine.CallLimitingControl
(added in Release 9.6(1)
This is a platform-specific value and depends on
your system installation. No auditing is available for
nailed trunks.
Allows enabling or disabling the call limiting capability on
the MGC.
Valid values:
•
0 = call limiting off (default)
•
1 = call limiting on
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-24
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.CALL_MEM_BLOCK_SIZE
Block of memory allocated per call.
Used by MDL.
Default:
Prior to Release 9.4(1): 0
•
For memory-critical configurations, use the default
value.
•
For performance-critical configurations, set this value
to 110000.
Release 9.4(1) and up: set automatically based on the type
of Cisco MGC selected in engine.SysVirtualSwitch. Any
attempt to modify this value is overwritten.
engine.CALL_MEM_CHUNK_SIZE
Memory chunks allocated from the block of memory
designated with engine.CALL_MEM_BLOCK_SIZE.
Default:
Prior to Release 9.4(1): 0
•
For memory-critical configurations, use the default
value.
•
For performance-critical configurations, set this value
to 110000.
Release 9.4(1) and up: set automatically based on the type
of Cisco MGC selected in engine.SysVirtualSwitch. Any
attempt to modify this value is overwritten.
engine.CDRencodingFormat
Specifies the call detail record (CDR) file encoding format.
Values:
•
AnsiCDB = North American
•
ItuCDB = European
•
CustCDB = Custom
Default: AnsiCDB
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-25
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.CDRmessageTypes
To specify the Call Detail Blocks (CDBs are the accounting
records written at various points in a call) that are generated
during a call, enter one of the following sets of values (each
number represents a point in a call):
•
1010, 1020, 1030, 1040, 1050, 1060, 1070,
1080—These are considered the “event-based” set of
values. Use this event-based list when you want to
receive all CDR records at predefined points in the call.
Although each of these CDBs can be specified
independently, Cisco suggests that you use the
event-based set as a "package" of CDBs for full
accounting purposes.
Note
The event-based setting is required when
operating the Cisco MGC in conjunction with
the BAMS adjunct.
•
1060, 1110—Use this value if you want end-of-call
summary-type records only.
•
1071—Use this set of values for BAMS measurements.
Refer to the chapter “Detailed CDB Description” in the
Cisco Media Gateway Controller Software Release 9 Billing
Interface Guide for details on each CDB.
engine.CDRtimeStamp
Specifies the time stamp unit in seconds or milliseconds.
To specify the CDR file time-stamp unit, enter one of the
following values:
•
S—Seconds (default).
•
M—Milliseconds. Use this parameter if your
configuration uses TCAP or if you want the millisecond
granularity in all of your CDR records.
Note
engine.CircuitReservation
The M setting is mandatory when operating the
Cisco MGC in conjunction with the BAMS
adjunct.
Enables or disables the circuit reservation feature.
Values: True, False
Default: False
engine.CMMdlFile
Location of call processing libraries.
Default: ../lib/cc
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-26
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.RelINAPCallsAfterSwOver
Defines the treatment of INAP calls in answer state after
platform switchover. This parameter is used for calls that
require INAP interaction even after the answer state.
Currently, this parameter is used only for Prepaid INAP
calls.
Values:
•
True (Release all the INAP calls after switchover)
•
False (Do not release INAP calls after switchover)
Default: True
If the value of this parameter is set to true, then
PGW will release all calls immediately. If the value
is set to False, PGW does not take any action for the
INAP prepaid calls and these calls are treated like
any normal POTS call.
Note
engine.LCMMdlFile
Location of call processing libraries.
Default: ../lib/lcm
Do not change this value.
Note
engine.MaxAuditCics
Number of circuit identification codes (CICs) that can be
audited at a specified interval.
Values:
•
24 = North America (T1)
•
32 = Europe (E1)
Default: 32
Note
engine.mdoDir
Do not change this value.
Location of call processing libraries.
Default: ../lib/
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-27
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.SendHardwareBlock
To enable the Cisco MGC to send hardware-oriented
blocking messages for any blocks that originate from the
media gateways:
•
true—Sends hardware-oriented blocking messages for
any blocks that originate from the media gateways.
•
false—Sends only maintenance-oriented blocking
messages for all blocking cases (default).
The functionality for this parameter is added in a
patch for Release 9.3(2) and up. If your system is
running Release 9.3(2) or Release 9.4(1) you must
enter this parameter in the XECfgParm.dat file
manually after installing the patch. If your system is
running Release 9.5(2), the parameter is
automatically added to the XECfgParm.dat file
during the patch installation.
Note
engine.ShortDurationCallPeriod
added in Release 9.5(2)
Allows you to specify the period used to determine a short
duration call. Calls with a duration less than the specified
value are recorded as a short duration call in the CDR.
Default: 0
Valid values are: 0—30. A setting of 0 indicates that this
parameter is disabled. Short duration calls are not recorded
in the CDR when this parameter is disabled.
engine.StartUpAuditEnabled
Audit is automatically invoked at PGW 2200 startup.
When the value is set to true the PGW 2200 automatically
starts audit when it comes up as the active host. This does not
apply to the standby host.
Default: false
engine.SysCdrCollection
Designates the format of call detail records (CDRs).
Values:
•
true = invalid for Release 7.4 and above.
•
false = generates binary format CDRs (default)
Default: false
Do not change this value. Setting this to a value of
true for Release 7.4 and higher is not valid and may
have deleterious effects on the system.
Note
engine.SysCLIval
Enables or disables Calling Line Identity (CLI) validation
processing on calls.
Values:
•
true = enables CLI validation
•
false = disables CLI validation
Default: false
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-28
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.SysGeneratedCode
Determines whether compiled or interpreted code is used.
Values:
•
true = system uses compiled code
•
false = system uses interpreted code
Default: true
Note
engine.SysGSMTimerInterval
Compiled code runs faster than interpreted code.
Typically, this value should be true. If your
configuration uses multiple CPUs, this value must be
true.
Allows group service messages (GSMs—used to advertise
the state of circuits) to be sent at a periodic rate from the SS7
side of the network to the IP side of the network.
Valid values: 1000 to 30000
Default for Cisco MGC 9.2(2): 30000
Default for Cisco MGC 9.3(1): 10000
engine.SysGRSBlockSize
Used for flow control of all automatically generated GRS,
CGB, and CGU messages which are generated by the Cisco
MGC during run time. Typically produced due to
propagation of service state changes such as MGCP
endpoints changing availability. Specifies the interval, in
milliseconds, between blocks of GRS parameters when the
engine.SysGRSBlockSize parameter is used. The timer
interval runs from the start of sending the first GRS message
in each block to the first message in the next block.
This parameter operates independently for each SS7 route
(each OPC/DPC pair).
Value: Any integer
Default: 0
Example: 1000
engine.SysMaxOverlap
Maximum number of digits required before a call is
considered complete; used in overlap signaling.
Default: 28
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-29
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.SysMdlMemoryReduction
Controls use of MDL memory reductions.
Prior to Release 9.4(1): values:
•
0 = MDL memory reductions not used (maximum
performance)
•
1 = MDL memory reduction improvements used
Default: 0
Note
For performance-critical configurations, use the
default value. For memory-critical configurations,
set this value to 1.
Note
Setting this parameter to 1 enables the memory
reduction algorithm which increases the number of
concurrent (sustained) calls possible with the
platform at the expense of call throughput
performance.
Note
During the startup of the Cisco MGC software, this
parameter will be set automatically to tune the
system for optimal performance.
Release 9.4(1) and up: set automatically based on the type
of Cisco MGC selected in engine.SysVirtualSwitch. Any
attempt to modify this value is overwritten.
engine.SysMinOverlap
Minimum number of digits required before a call is
considered valid; used in overlap signaling.
Default: 0
Do not change this value.
Note
engine.SysPropagateChanAvail
In a classic signaling controller configuration, propagates
service messages between channels in the event of a channel
failure.
Values:
•
true = messages propagated
•
false = messages not propagated (default)
Note
engine.SysSGCPRetryCount
Do not change this value.
Maximum number of simple gateway control protocol
(SGCP) retry messages after a failure.
Default: 3
Note
engine.SysSGCPREtryTimerInterval
Do not change this value.
The interval between SGCP message transmissions, in
milliseconds.
Default: 1000
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-30
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
engine.SysTraceLevel
A debugging tool that allows for different levels of engine
tracing.
Default: 3
Do not change this value.
Note
engine.SysVirtualSwitch
Indicates whether the Cisco MGC host functions as a
signaling controller or a virtual switch controller.
Values:
•
0 = signaling controller (nailed trunks, no auditing is
initiated)
•
1 = virtual switch controller (switched trunks)
Default: 0
Note
During the startup of the Cisco MGC software, this
parameter will be set automatically to tune the
system for optimal performance.
Note
For Release 9.4(1) and up, the values of the
parameters listed below are automatically set based
on the Cisco MGC type you select, to maximize
performance for that configuration. Any attempt to
change the values of these parameters is overwritten.
engine.SysMdlMemoryReduction
engine.CALL_MEM_BLOCK_SIZE
engine.CALL_MEM_CHUNK_SIZE
*.CPUTimerInterval
*.numberOfThreads
engine.VersionTimeoutValue
Defines the time out interval in number of milliseconds for
version messages sent to the MGW. This delay determines
how long the Cisco MGC will wait for response from the
MGW during the exchange of features prior to the audit.
Value: Any integer.
Default: 10000
foverd.abswitchPort
Port used for communication with the A/B switch.
Value: /dev/term/x
Example: /dev/term/b
Note
foverd.abswitchTestInterval
If your configuration does not use an A/B switch, use
the default value (/dev/null).
Time interval in milliseconds between attempts to verify that
an A/B switch is present.
Default: 30000
Note
This parameter only applies if your configuration
uses an A/B switch.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-31
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
foverd.ackTimeout
Maximum time, in milliseconds, that the failover daemon
will wait for an ACK or NOACK message to be received
from the peer failover daemon. For each message the
failover daemon sends, the peer failover daemon sends an
ACK or NOACK message to indicate that the peer is still
functioning.
Default: 1000 milliseconds (1 second).
You can change the default value to a value more
appropriate for your system installation.
Note
foverd.commRetryInterval
Time interval in milliseconds between attempts to open a
connection.
Connection types include:
•
Connection to the peer failover daemon
•
Connection to the A/B switch
•
Connection to the ARU
Default: 30000 milliseconds (30 seconds).
You can change the default value to a value more
suited to your system installation.
Note
foverd.conn1Type
Sets the connection type for connection number 1.
Values:
•
serial
•
socket
Typically, set this value to socket.
Note
foverd.conn2Type
Sets the connection type for connection number 2.
Values:
•
serial
•
socket
Note
foverd.conn3Addr
Typically, set this value to socket.
Specifies the address of the peer system.
Example: /dev/term/b
If your configuration does not use connection number 3,
enter /dev/null (default).
Note
If your configuration uses an 8-port connector as a
serial connection for failover, you must modify the
read-write permissions for the connection. For more
information, see the Release Notes for the Cisco
Media Gateway Controller Software Release 9.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-32
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
foverd.conn3Type
Sets the connection type for connection number 3.
Values:
•
serial
•
socket
Note
foverd.delayTimeout
Typically, set this value to serial.
Maximum time in milliseconds that the failover daemon can
delay at startup before sending messages to its peer. This is
also the delay offset that is added when the two failover
daemons become too closely synchronized.
Default: 1000 milliseconds (1 second)
foverd.forceShutTimeout
Maximum time in milliseconds that the failover daemon
waits before forcefully shutting down the platform.
Default: 1000 milliseconds (1 second)
foverd.graceShutTimeout
Maximum time in milliseconds that the failover daemon
waits before gracefully shutting down the process manager,
which shuts down the processes it controls.
Default: 6000 milliseconds (6 seconds)
foverd.heartbeatInterval
Maximum time in milliseconds between heartbeat messages
from the peer failover daemon. This interval defines the
frequency that the failover daemon exchanges heartbeat
messages with its peer.
Default: 1000 milliseconds (1 second).
foverd.ipLocalPortA
Port number used for IP communication.
Default: 0
Note
foverd.ipLocalPortB
If you have two Cisco MGC hosts in a failover
configuration, enter this value for the
foverd.ipPeerPortA field in the XECfgParm.dat file
on the secondary host.
Port number used for IP communication.
Default: 0
Note
foverd.ipPeerPortA
If you have two Cisco MGC hosts in a failover
configuration, enter this value for the
foverd.ipPeerPortB field in the XECfgParm.dat file
on the secondary host.
Port number used for IP communication.
Default: 0
Note
If you have two Cisco MGC hosts in a failover
configuration, enter this value for the
foverd.ipLocalPortA field in the XECfgParm.dat file
on the secondary host.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-33
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
foverd.ipPeerPortB
Port number used for IP communication.
Default: 0
If you have two Cisco MGC hosts in a failover
configuration, enter this value for the
foverd.ipLocalPortB field in the XECfgParm.dat file
on the secondary host.
Note
foverd.peerCommTimeout
Maximum time in milliseconds without communication with
the remote system. At the expiration of this period, the
remote system is assumed to be unavailable and failover is
triggered automatically.
Default: 3000 milliseconds (3 seconds)
A time out value that is too small can cause a false
failover, resulting in possible service interruptions.
Note
foverd.statusRptInterval
Time interval in milliseconds that governs the frequency
with which the failover daemon logs statistics on the
different connections and any failures it encountered
exchanging messages with its peer. Logs are created in the
log directory.
Default: 600000 milliseconds (10 minutes)
foverd.transitionTimeout
Maximum time in milliseconds allowed for transitions
between different states of the failover daemon. This timeout
determines how long the system waits for a graceful
transition to a new state before forcing the transition. If a
timeout occurs, the system is restarted.
Default: 10000 milliseconds (10 seconds).
GWNetworkContinuity
For network continuity test on VISM.
Valid values:
1 means that Network Continuity is present/requested.
0 means that no Network Continuity is present/requested.
Default: 0 (Currently this property only applies to VISM
GWs.)
This property should have value = 1 when the VISM
GW property is switched on.
Note
ioChanCtl.DPNSSTestFrames
Enables DPNSS to generate test frames.
Values:
•
true = if DPNSS is running, test frames are generated
•
false = test frames are not generated
Default: true
Note
ioChanMgr.alarmTimer
Do not change this value.
This parameter is obsolete and should be set to 0.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-34
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
ioChanMgr.evtTimer
Frequency, in milliseconds, at which the queue is scanned
for messages.
Default: 100
Note
Do not change this value.
ioChanMgr.hbTimer
This parameter is reserved for future use.
ioChanMgr.IPCsendThreshold
Specifies the maximum number of RSIPs that can be sent
from the queue during a period defined by the IPCTimer
XECfgParam.dat parameter. When this parameter is left at
its default value (0), the system uses a base value. You can
modify the value if a problem occurs.
added in Release 9.5(2)
Valid values: Any integer
Default value: 0
ioChanMgr.resumeAckTimer
Amount of time the Cisco MGC waits to get a
MGMT_RESUME_ACK_RSP message from a gateway,
after sending a MGMT_RESUME_REQ message fro a BSM
session set.
Values are 1 to 2 seconds.
Default: 1
ioChanMgr.sendThreshold
Maximum number of events sent from the queue at one time.
Default: 10
Note
ioChanMgr.sessionPauseTimer
Do not change this value.
Amount of time the Cisco MGC waits for a BSM session set
to recover from failure before declaring the session set
failure. Values are 1 to 10 sec.
Default: 8
ioChanMgr.statDiscardThreshold
Size of the control queue that triggers discarding of all
queued stat events.
Default: 40
Note
ioChanMgr.statTimer
Do not change this value.
Frequency, in milliseconds, at which measurements are
collected in the Transpath input/output system (TIOS).
Default: 30000 milliseconds
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-35
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
ioChanMgr.trace
Creates unit test tracing of line and channel state machines.
Generates a considerable amount of information to the log.
Set to a value only when you are debugging a particular
problem with line or channel service state problems.
Values:
•
0 x 0 = default
•
0 x 1 = trace
Note
logger.daemonAddr
Do not change this value.
Specifies the name of the local socket used by the log server
daemon. The daemon listens for connections on this address,
and client programs attempt to connect to the daemon at this
address.
Default: ../var/log/lsd_addr
Note
logger.fileRotateInterval
If this setting is missing from the XECfgParm.dat
file, the log server daemon does not run.
Triggers a file rotation based on the time elapsed since the
previous rotation.
Default: 1440 minutes (24 hours)
Note
logger.fileRotateSize
This timer is reset after any rotation occurs,
regardless of the cause or trigger of the rotation.
Triggers a file rotation based on the size of the active file. A
file rotation triggered by this parameter also resets the
logger.fileRotateInterval timer.
Default: 100MB
Note
logger.numThreads
The file size may grow larger than this parameter
indicates due to the verbosity of the logging levels
currently in effect.
Determines whether the PXE logger should run in a separate
thread from the rest of the application. A value of 0 runs the
logger synchronously with the application; a value of 1 runs
the logger in a separate thread.
Value: 0/1 (Values less than 0 get reset to 0; values greater
than 1 get reset to 1.)
Default: 0
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-36
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
MDLANumberScreening
Invokes the standard A-number screening on the number in
the calling number parameter, regardless of whether the call
is redirected or not.
Setting the MDLANumberScreening parameter to its default
value 0 (zero) in the XECfgParm.dat file defaults all
screening actions exclusively to the original calling party
number (A-number). No screening is done on the number in
the redirecting number parameter.
Default value: 0 (zero)
Note
MML.chg-cfg
To invoke the redirecting number screening feature,
set the value to 1 in the XEConfigParm.dat file
during initial Cisco MGC software configuration.
Timeout value for the chg-cfg MML command in
milliseconds; overrides MML.timeout.
Default: 10000 milliseconds
Note
MML.snd
Do not change this value. This MML command is
obsolete.
Timeout value for the snd MML command in milliseconds;
overrides MML.timeout.
Default: 600000 milliseconds
Note
MML.startPM
Do not change this value.
Timeout value for the startPM MML command in
milliseconds; overrides MML.timeout.
Default: /etc/init.d/CiscoMGC start
Note
MML.stopPM
Do not change this value.
Timeout value for the stopPM MML command in
milliseconds; overrides MML.timeout.
Default: /etc/init.d/CiscoMGC stop
Note
MML.timeout
Do not change this value.
Timeout for MML commands, in milliseconds.
Default: 10000 milliseconds
Note
MML.vld-cic
Do not change this value.
Timeout value for the vld-cic MML command in
milliseconds; overrides MML.timeout.
Default: 25000 milliseconds
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-37
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
pom.dataSync
Indicates that the Provisioning Object Manager (POM)
should synchronize the provisioning data at startup.
Values:
•
true = POM is enabled, data is synchronized
•
false = POM is disabled, no data synchronization
(default)
Note
If you have two Cisco MGC hosts in a failover
configuration, set this value to true. If you have a
standalone Cisco MGC, set this value to false.
Note
When the initial Cisco MGC configuration on the
active host is deployed, you must change the
pom.dataSync parameter to true in the
XECfgParm.dat file on the standby host. After
setting this parameter to true, you can start the
Cisco MGC on the standby host. As the Cisco
MGC comes up, the data on the standby host is
synchronized with the data on the active host and
the active host goes into the standby state.
To accommodate failover conditions where the
current active host can become the standby host,
you must also set the pom.dataSync parameter to
true on the current active host.
Note
pom.port
If you are trying to maintain calls during an upgrade
of a redundant system and you want to preserve your
configuration, verify that the pom.dataSync
parameter is set to false in
/opt/CiscoMGC/etc/XECfgParm.dat.
In a failover configuration, indicates the port number the
POM uses to communicate with its peer.
Value: Any integer from 4001 to 4050
Default: 4001 or default
Note
procM.almDwellInterval
This is a platform-specific value and depends on
your system installation. You should only modify
this value if the default port (4001) is being used by
another process or application.
Seconds that the process manager must wait before clearing
an alarm.
Default: 15 seconds
Note
procM.logDBFile
Do not change this value.
Specifies the location of the log level storage.
Default: ../var/procMLogTable
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-38
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
procM.minCheckHealthInterval
Seconds at which a process can generate heartbeats.
Default: 10 seconds
Note
procM.minCheckHealthTimeout
Do not change this value.
Seconds at which a timeout can occur.
Default: 20 seconds
Note
procM.minKillGracePeriod
Do not change this value.
Seconds that the process manager must wait before killing a
process after a heartbeat timeout.
Default: 5 seconds
Note
procM.recovDbFile
Do not change this value.
Storage location of the process manager persistent
information.
Default: ../var/procMRecovery
Note
procM.servFmt
Do not change this value.
Format of the process manager temporary files.
Default: PM_%d_%d_input
Note
procM.servicesDir
Do not change this value.
Location of the process manager temporary files.
Default: ../var
Note
Do not change this value.
procMprocHealthDfltAlmCat
This parameter is no longer used.
product.time
Software time stamp.
Note
product.vendor
Software vendor name.
Note
product.version
Do not change this value.
Software release version number.
Note
replicator.portCommChannelRecv
Do not change this value.
Do not change this value.
Communication port for the replicator.
Default: 2974
Note
replicator.portCommChannelSend
Do not change this value.
Communication port for the replicator.
Default: 2972
Note
replicator.portDataChannelRecv
Do not change this value.
Communication port for the replicator.
Default: 2970
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-39
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
replicator.portDataChannelSend
Communication port for the replicator.
Default: 2968
Note
Do not change this value.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-40
OL-1150-15
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Table A-1
Cisco MGC 9.x XECfgParm.dat File Configuration Parameters (continued)
Configuration Parameter
Definition
replicator.reconnectInterval
Defines the reconnect interval in number of seconds for the
replicator during a switchover.
Value: Any integer
Default: 15 seconds
Set this value to 0 for a standalone Cisco PGW.
Note
For geographically separated Cisco PGW pairs (Geographic
Separation of Active and Standby Cisco MGC Hosts), the
following replicator timer values are recommended:
•
On one PGW, replicator.reconnectInterval = 15 seconds
•
On the other PGW, replicator.reconnectInterval = 20
seconds
If the timer settings are the same on both Cisco PGWs, the
additional latency between the separated Cisco PGWs may
cause a problem in which the replicator links are continually
reconnecting and then immedately disconnecting. The timer
change prevents this problem.
SipToIsupInterworkingInd
Only applicable with SIP to ISUP (or ISUP to SIP) calls.
When the Cisco PGW receives a SIP message with
encapsulated ISUP (SIP-T, SIP-GTD), it sets the FCI/BCI
parameter in the generated ISUP message so that all
interworking-related bits have the same values as their
counterparts in the encapsulated ISUP.
If usable encapsulated ISUP is not present in the SIP
message, the Cisco PGW sets the Interworking Indicator bit
of the FCI/BCI parameter to 'no interworking'; the ISDN
User Part Indicator to 'ISUP used all the way' and the
Originating Access indicator to 'Originating access
non-ISDN'.
If desired, service providers can set the the Cisco PGW
property 'SipToIsupInterworkingInd' to 1 which will signal
in the FCI/BCI parameter in the generated ISUP message
that 'interworking has been encountered' and 'ISUP is not
used all the way' when encapsulated ISUP is not present in
SIP message.
Values:
•
0 (No Interworking Encountered)
•
1 (Interworking Encountered)
Default Value:
Note
0
If the property is absent from the XECfgParm.dat
file, Cisco PGW assumes a default value of 0.
Protocol Family: Applicable to all ansi, q761 and q767
ISUP variants.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
A-41
Appendix A
XECfgParm.dat File Parameters
Understanding the XECfgParm.dat File Format
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
A-42
OL-1150-15
A P P E N D I X
B
HP OpenView Sample SNMP Configuration
Configuring the Cisco MGC to Send Alarms to HP OpenView
This sample configuration sets up a Cisco MGC to send alarms to HP OpenView.
Step 1
Load the following MIBs in HP OpenView, in the order shown below. To load MIBs, select the Options
menu, and choose Load/Unload MIBs: SNMP.
MIB
Location
CISCO-SMI.my
/opt/TransPath/snmp
tp.my
/opt/TransPath/snmp
measurement.my
/opt/TransPath/snmp
v3-tgt.my
/opt/TransPath/snmp
SNMP-FRAMEWORK-MIB.my
ftp://ftp.cisco.com/pub/mibs/v2/
SNMP-NOTIFICATION-MIB.my
ftp://ftp.cisco.com/pub/mibs/v2/
Note
You must also install the generic HP OpenView MIB files SNMP-FRAMEWORK and
SNMP-NOTIFICATION. These files are available from your HP OpenView installation
medium.
Step 2
Open the MIB browser and select the Tools menu, then choose SNMP MIB Browser.
Step 3
Under Name or IP Address, enter the name or IP address of the Cisco MGC you are configuring.
Step 4
Under Community Name, enter public.
Step 5
Navigate to the SNMP target address table by double-clicking snmpV2 | snmpModules |
snmpTargetMIB | snmpTargetObjects | snmpTargetAddrTable | snmpTargetAddrEntry.
Step 6
Select the MIB object snmpTargetAddrRowStatus (see table below).
Step 7
Click Start Query. Two values should appear at the bottom of the window, 49: active and 50: active.
Step 8
Under MIB Instance, enter 51 (see table below).
Step 9
Under SNMP Set Value, enter 5 (see table below).
Step 10
Click Set. You should see a dialog box indicating that the values are entered successfully.
Step 11
Continue this process until all the MIB object IDs in the table below have the correct MIB instance and
SNMP set values.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
B-1
Appendix B
HP OpenView Sample SNMP Configuration
Configuring the Cisco MGC to Send Alarms to HP OpenView
Select MIB Object ID
MIB Instance
SNMP Set Value
snmpTargetAddrRowStatus
51
5
snmpTargetAddrRowStatus
52
5
snmpTargetAddrTDomain
52
.1.3.6.1.6.1.1
snmpTargetAddrTDomain
52
.1.3.6.1.6.1.1
snmpTargetAddrTAddress
51
Hex representation of NMS
IP (see note below)
snmpTargetAddrTAddress
52
Hex representation of NMS
IP (see note below)
snmpTargetAddrTimeout
51
100
smnpTargetAddrTimeout
52
100
snmpTargetAddrRetryCount
51
3
snmpTargetAddrRetryCount
52
3
snmpTargetAddrTagList
51
Manager1
snmpTargetAddrTagList
52
Manager1
snmpTargetAddrParams
51
v1ExampleParams
snmpTargetAddrParams
52
v2cExampleParams
snmpTargetAddrStorageType
51
3
snmpTargetAddrStorageType
52
3
snmpTargetAddrRowStatus
51
1
snmpTargetAddrRowStatus
52
1
Note
When you are configuring snmpTargetAddrTAddress, the address of the network management station
running HP OpenView must be entered. This SNMP field is a generic six-byte field designed to
accommodate IP and non-IP SNMP implementations. Since the Cisco MGC supports only SNMP over
IP, this field always contains the IP address of the network management system. The IP address,
however, must be converted into a six-byte hexadecimal value. This is done by converting the IP address
to hexadecimal notation, then appending two bytes of zeros as padding. For example, if the IP address
of the HP OpenView station is 172.24.236.241, the value entered for snmpTargetAddrTAddress is AC
18 EC F1 00 00.
Tip
You can verify the settings by selecting each MIB object ID and clicking Start Query. When you do
this for snmpTargetAddrRowStatus, it should show four entries set to active.
Step 12
Navigate to the snmpNotify table by clicking Up Tree four times to return to the snmpModules part of
the MIB. Then navigate down the tree by double-clicking snmpNotificationMIB | snmpNotifyObjects
| snmpNotifyTable | snmpNotifyEntry.
Step 13
As before, associate the correct MIB instance and SNMP set values with the MIB object IDs.
Select MIB Object ID
MIB Instance
SNMP Set Value
snmpNotifyRowStatus
50
5
snmpNotifyTag
50
Manager1
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
B-2
OL-1150-15
Appendix B
HP OpenView Sample SNMP Configuration
Formatting Trap Messages
Tip
snmpNotifyStorageType
50
3
snmpNotifyRowStatus
50
1
You can verify the settings by selecting each MIB OID and clicking Start Query. When you do this
for snmpNotifyRowStatus, it should show four entries set to active. When you have verified the
settings, you can close the MIB browser window.
Step 14
Click Close.
Step 15
At this point, HP OpenView should start receiving alarms from the Cisco MGC. You can verify this by,
for example, performing a set-sc-state MML command to take a signaling channel out of service.
Formatting Trap Messages
When HP OpenView receives the traps from the Cisco MGC, HP OpenView does not automatically
interpret the trap and display it in a useful manner. The trap is sent with basic information indicating the
alarm category, description, and severity. Because many failures require extra detail for troubleshooting,
you should refer to the log file on the Cisco MGC for complete alarm information and for determining
root causes.
You can, however, configure HP OpenView to format the traps into a more readily understandable
format by following the steps below:
Step 1
Open the Event Configuration window by selecting Options | Event Configuration from the
HP OpenView menu.
Step 2
Under Enterprise Name, select TransPath. The five alarm types should be displayed under Event
Identification.
Step 3
Double-click one of the event names under Event Identification; for example, commAlarm.
Step 4
Under Event Log Message, enter the message that you want logged to the HP OpenView log file when
HP OpenView receives this alarm. You can use variables from the following table in your message to
provide specific information about the alarm.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
B-3
Appendix B
HP OpenView Sample SNMP Configuration
Formatting Trap Messages
Variabl
e
Definition
Explanation
$1
tpAlarmId
Alarm identification
$2
tpAlarmCatId
Alarm category identification number
$3
tpAlarmCatName
Alarm category name
$4
tpAlarmCatDesc
Alarm category description
$5
tpAlarmSet
Alarm set/not set.
2 means the alarm is being set.
1 means the alarm is being cleared
$6
tpAlarmNotify
Alarm notified/not notified
$7
tpAlarmSeverity
Alarm severity
$8
tpAlarmReported
Alarm reported
$9
tpComponentId
Component identification number. This number
consists of two parts, the component type and
component instance.
The most significant 2 bytes signify the component
type.
The least significant 2 bytes are the sequential
instance of the type.
$10
tpComponentType
Component type identification number
$11
tpCompMMLName Short notation of the component name. It is also the
MML name that can be used in the MML session.
$12
tpCompDesc
Component description
$13
tpCompParentId
Component parent identification
$14
tpAlarmTime
Time the alarm occurred
Following is an example of an event log message string:
SC2200: ID#: $13 Name: $12 Set: $10 MMLname: $4
Severity: $8 CompID: $6 CompType: $5 CatID: $14
ParentID: $2 AlarmReported: $7
CatDesc: $11 CompDesc: $3
AlarmNotify: $9 AlarmTime: $1
Following is another example showing more simple formatting:
MGC $7 alarm $5 -- $12: $4
Step 5
Click OK to set your message.
Step 6
Repeat the procedure for each event name.
Step 7
From the Event Configuration window, select File | Save.
Step 8
Close the window.
Step 9
Verify that alarms are being received and formatted correctly by generating an alarm on the Cisco MGC
(for instance, take a signaling channel out of service to see if you get an alarm).
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
B-4
OL-1150-15
A P P E N D I X
C
Sample LAN Configurations
This appendix contains sample configurations for two LAN switches, Cisco Catalyst 5500 A and Cisco
Catalyst 5500 B, and the route switch modules.
Sample Configuration for Cisco Catalyst 5500 A
To view the current configuration of the Cisco Catalyst 5500 A, type the following command in
privileged mode, and press Enter:
Catalyst_5513A (enable) show config
Output similar to the following appears:
begin
!
#version 4.5(1)
!
set password $1$l30o$QUt/nAlYZH/WFmDoJqWAW0
set enablepass $1$tTCB$rbEX8KRDTtpVG9gsy7jc61
set prompt Catalyst_5513A
set length 24 default
set logout 20
set banner motd ^C^C
!
#system
set system baud 9600
set system modem disable
set system name Catalyst_5513A
set system location Lab1
set system contact Jim Smith 913 555-7998
!
#snmp
set snmp community read-only
public
set snmp community read-write
private
set snmp community read-write-all public
set snmp rmon disable
set snmp trap enable module
set snmp trap enable chassis
set snmp trap enable bridge
set snmp trap enable repeater
set snmp trap enable vtp
set snmp trap enable auth
set snmp trap enable ippermit
set snmp trap enable vmps
set snmp trap enable entity
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-1
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
set
set
set
set
set
set
!
#ip
set
snmp
snmp
snmp
snmp
snmp
snmp
trap enable
trap enable
trap enable
extendedrmon
extendedrmon
extendedrmon
config
stpx
syslog
vlanmode disable
vlanagent disable
enable
interface sc0 3 172.25.66.122 255.255.255.192 172.25.66.127
set interface sc0 up
set interface sl0 0.0.0.0 0.0.0.0
set interface sl0 up
set arp agingtime 1200
set ip redirect
enable
set ip unreachable
enable
set ip fragmentation enable
set ip route 0.0.0.0
172.25.66.124 1
set ip alias default
0.0.0.0
!
#Command alias
!
#vmps
set vmps server retry 3
set vmps server reconfirminterval 60
set vmps tftpserver 0.0.0.0 vmps-config-database.1
set vmps state disable
!
#dns
set ip dns disable
!
#tacacs+
set tacacs attempts 3
set tacacs directedrequest disable
set tacacs timeout 5
!
#authentication
set authentication login tacacs disable console
set authentication login tacacs disable telnet
set authentication enable tacacs disable console
set authentication enable tacacs disable telnet
set authentication login local enable console
set authentication login local enable telnet
set authentication enable local enable console
set authentication enable local enable telnet
!
#bridge
set bridge ipx snaptoether
8023raw
set bridge ipx 8022toether
8023
set bridge ipx 8023rawtofddi snap
!
#vtp
set vtp domain vsc3000
set vtp mode transparent
set vtp v2 disable
set vtp pruneeligible 2-1000
clear vtp pruneeligible 1001-1005
set vlan 1 name default type ethernet mtu 1500 said 100001 state active
set vlan 2 name green type ethernet mtu 1500 said 100002 state active
set vlan 3 name blue type ethernet mtu 1500 said 100003 state active
set vlan 4 name red type ethernet mtu 1500 said 100004 state active
set vlan 1002 name fddi-default type fddi mtu 1500 said 101002 state active
set vlan 1004 name fddinet-default type fddinet mtu 1500 said 101004 state activ
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-2
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
e bridge 0x0 stp ieee
set vlan 1005 name trnet-default type trbrf mtu 1500 said 101005 state active br
idge 0x0 stp ibm
set vlan 1003 name token-ring-default type trcrf mtu 1500 said 101003 state acti
ve parent 0 ring 0x0 mode srb aremaxhop 7 stemaxhop 7
set interface sc0 3 172.25.66.122 255.255.255.192 172.25.66.127
!
#spantree
#uplinkfast groups
set spantree uplinkfast enable rate 15 all-protocols off
#backbonefast
set spantree backbonefast disable
set spantree enable all
#vlan 1
set spantree fwddelay 4
1
set spantree hello
1
1
set spantree maxage
20
1
set spantree priority 1000 1
#vlan 2
set spantree fwddelay 4
2
set spantree hello
1
2
set spantree maxage
20
2
set spantree priority 1000 2
#vlan 3
set spantree fwddelay 4
3
set spantree hello
1
3
set spantree maxage
20
3
set spantree priority 1000 3
#vlan 4
set spantree fwddelay 4
4
set spantree hello
1
4
set spantree maxage
20
4
set spantree priority 1000 4
#vlan 1003
set spantree fwddelay 15
1003
set spantree hello
2
1003
set spantree maxage
20
1003
set spantree priority 49152 1003
set spantree portstate 1003 block 0
set spantree portcost 1003 62
set spantree portpri 1003 4
set spantree portfast 1003 disable
#vlan 1005
set spantree fwddelay 15
1005
set spantree hello
2
1005
set spantree maxage
20
1005
set spantree priority 49152 1005
set spantree multicast-address 1005 ieee
!
#cgmp
set cgmp disable
set cgmp leave disable
!
#syslog
set logging console enable
set logging server disable
set logging level cdp 2 default
set logging level mcast 2 default
set logging level dtp 5 default
set logging level dvlan 2 default
set logging level earl 2 default
set logging level fddi 2 default
set logging level ip 2 default
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-3
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
set logging level pruning 2 default
set logging level snmp 2 default
set logging level spantree 2 default
set logging level sys 5 default
set logging level tac 2 default
set logging level tcp 2 default
set logging level telnet 2 default
set logging level tftp 2 default
set logging level vtp 2 default
set logging level vmps 2 default
set logging level kernel 2 default
set logging level filesys 2 default
set logging level drip 2 default
set logging level pagp 5 default
set logging level mgmt 5 default
set logging level mls 5 default
set logging level protfilt 2 default
set logging level security 2 default
set logging server facility LOCAL7
set logging server severity 4
set logging buffer 500
set logging timestamp disable
!
#ntp
set ntp broadcastclient disable
set ntp broadcastdelay 3000
set ntp client disable
clear timezone
set summertime disable
!
#set boot command
set boot config-register 0x2
set boot system flash bootflash:RTSYNC_cat5000-sup3_4-5-1.bin
set boot system flash bootflash:RTSYNC_cat5000-sup3.4-4-1.bin
set boot system flash bootflash:cat5000-sup3.4-3-1a.bin
!
#permit list
set ip permit disable
!
#drip
set tokenring reduction enable
set tokenring distrib-crf disable
!
#igmp
set igmp disable
!
#protocolfilter
set protocolfilter disable
!
#mls
set mls enable
set mls flow destination
set mls agingtime 256
set mls agingtime fast 0 0
set mls nde disable
!
#standby ports
set standbyports enable
!
#module 1 : 2-port 10/100BaseTX Supervisor
set module name
1
set vlan 1
1/1-2
set port channel 1/1-2 off
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-4
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
set port enable
1/1-2
set port level
1/1-2 normal
set port speed
1/1-2 100
set port duplex
1/1-2 full
set port trap
1/1-2 disable
set port name
1/1-2
set port security
1/1-2 disable
set port broadcast 1/1-2 100%
set port membership 1/1-2 static
set port protocol 1/1-2 ip on
set port protocol 1/1-2 ipx auto
set cdp enable
1/1-2
set cdp interval 1/1-2 60
set trunk 1/1 on isl 1-1005
set trunk 1/2 on isl 1-1005
set spantree portfast
1/1-2 disable
set spantree portcost
1/1-2 3019
set spantree portpri
1/1-2 32
set spantree portvlanpri 1/1 0
set spantree portvlanpri 1/2 0
set spantree portvlancost 1/1 cost 3018
set spantree portvlancost 1/2 cost 3018
!
#module 2 : 2-port 10/100BaseTX Supervisor
set module name
2
set vlan 1
2/1-2
set port channel 2/1-2 off
set port enable
2/1-2
set port level
2/1-2 normal
set port speed
2/1-2 100
set port duplex
2/1-2 full
set port trap
2/1-2 disable
set port name
2/1-2
set port security
2/1-2 disable
set port broadcast 2/1-2 100%
set port membership 2/1-2 static
set port protocol 2/1-2 ip on
set port protocol 2/1-2 ipx auto
set cdp enable
2/1-2
set cdp interval 2/1-2 60
set trunk 2/1 desirable isl 1-1005
set trunk 2/2 desirable isl 1-1005
set spantree portfast
2/1-2 disable
set spantree portcost
2/1-2 3019
set spantree portpri
2/1-2 32
set spantree portvlanpri 2/1 0
set spantree portvlanpri 2/2 0
set spantree portvlancost 2/1 cost 3018
set spantree portvlancost 2/2 cost 3018
!
#module 3 : 24-port 10BaseT Ethernet
set module name
3
set module enable 3
set vlan 1
3/19-20,3/22-24
set vlan 2
3/1-18
set vlan 3
3/21
set port enable
3/1-24
set port level
3/1-24 normal
set port duplex
3/1-24 half
set port trap
3/1-24 disable
set port name
3/1-24
set port security
3/1-24 disable
set port broadcast 3/1-24 0
set port membership 3/1-24 static
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-5
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
set port protocol 3/1-24 ip on
set port protocol 3/1-24 ipx auto
set cdp enable
3/1-24
set cdp interval 3/1-24 60
set spantree portfast
3/1-24 enable
set spantree portcost
3/1-24 3100
set spantree portpri
3/1-24 32
!
#module 4 : 12-port 10/100BaseTX Ethernet
set module name
4
set module enable 4
set vlan 2
4/1-2
set vlan 3
4/7-8
set vlan 4
4/3-6
set port channel 4/1-4 off
set port channel 4/5-8 off
set port channel 4/9-12 off
set port enable
4/1-12
set port level
4/1-12 normal
set port speed
4/1-12 auto
set port trap
4/1-12 disable
set port name
4/1-12
set port security
4/1-12 disable
set port broadcast 4/1-12 0
set port membership 4/1-12 static
set port protocol 4/1-12 ip on
set port protocol 4/1-12 ipx auto
set cdp enable
4/1-12
set cdp interval 4/1-12 60
set trunk 4/1 auto isl 1-1005
set trunk 4/2 auto isl 1-1005
set trunk 4/3 auto isl 1-1005
set trunk 4/4 auto isl 1-1005
set trunk 4/5 auto isl 1-1005
set trunk 4/6 auto isl 1-1005
set trunk 4/7 auto isl 1-1005
set trunk 4/8 auto isl 1-1005
set trunk 4/9 auto isl 1-1005
set trunk 4/10 auto isl 1-1005
set trunk 4/11 off isl 1-1005
set trunk 4/12 off isl 1-1005
set spantree portfast
4/1-12 enable
set spantree portcost
4/5-8, 4/11-12 3019
set spantree portcost
4/1-4, 4/9-10 3100
set spantree portpri
4/1-12 32
set spantree portvlanpri 4/1 0
set spantree portvlanpri 4/2 0
set spantree portvlanpri 4/3 0
set spantree portvlanpri 4/4 0
set spantree portvlanpri 4/5 0
set spantree portvlanpri 4/6 0
set spantree portvlanpri 4/7 0
set spantree portvlanpri 4/8 0
set spantree portvlanpri 4/9 0
set spantree portvlanpri 4/10 0
set spantree portvlanpri 4/11 0
set spantree portvlanpri 4/12 0
set spantree portvlancost 4/1 cost 3099
set spantree portvlancost 4/2 cost 3099
set spantree portvlancost 4/3 cost 3099
set spantree portvlancost 4/4 cost 3099
set spantree portvlancost 4/5 cost 3018
set spantree portvlancost 4/6 cost 3018
set spantree portvlancost 4/7 cost 3018
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-6
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 A
set spantree portvlancost 4/8 cost 3018
set spantree portvlancost 4/9 cost 3099
set spantree portvlancost 4/10 cost 3099
set spantree portvlancost 4/11 cost 3018
set spantree portvlancost 4/12 cost 3018
!
#module 5 empty
!
#module 6 empty
!
#module 7 empty
!
#module 8 empty
!
#module 9 empty
!
#module 10 empty
!
#module 11 empty
!
#module 12 : 1-port Route Switch
set module name
12
set port level
12/1 normal
set port trap
12/1 disable
set port name
12/1
set cdp enable
12/1
set cdp interval 12/1 60
set trunk 12/1 on isl 1-1005
set spantree portcost
12/1 3005
set spantree portpri
12/1 15
set spantree portvlanpri 12/1 160
set spantree portvlancost 12/1 cost 3004 4-8,11-15
!
#module 13 empty
!
#switch port analyzer
set span 2 3/23 both inpkts disable
!set span enable
!
#cam
set cam agingtime 1-4,1003,1005 300
end
Sample Configuration for Cisco Catalyst 5500 A RSM
To view the current configuration of the Cisco Catalyst 5500 A RSM, access the RSM interface, type
the following command in privileged mode, and press Enter:
Catalyst_5513A_RSM#show run
Output similar to the following appears:
Building configuration...
Current configuration:
!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-7
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
hostname Catalyst_5513A_RSM
!
enable password cisco
!
no ip domain-lookup
!
!
!
interface Vlan2
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 2 timers 1 3
standby 2 priority 110
standby 2 preempt
standby 2 authentication VSC3000
standby 2 ip 172.25.66.60
!
interface Vlan3
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 3 timers 1 3
standby 3 priority 110
standby 3 preempt
standby 3 authentication VSC3000
standby 3 ip 209.165.200.224
!
interface Vlan4
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 4 timers 1 3
standby 4 priority 110
standby 4 preempt
standby 4 authentication VSC3000
standby 4 ip 209.165.200.224
!
router eigrp 1
network 209.165.200.224
!
ip classless
!
snmp-server community public RO
snmp-server community private RW
snmp-server chassis-id public
snmp-server enable traps snmp
snmp-server enable traps appn alert
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps rtr
!
line con 0
line aux 0
line vty 0 4
password cisco
login
!
end
Sample Configuration for Cisco Catalyst 5500 B
To view the current configuration of the Cisco Catalyst 5500 B, type the following command in
privileged mode, and press Enter:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-8
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
Catalyst_5513B (enable) show config
Output similar to the following appears:
begin
!
#version 4.5(1)
!
set password $1$7OtT$J/rAZe2CANYvHW72ZMtI10
set enablepass $1$0o8Z$xbxAzs4LlepsklB6Ju7VY.
set prompt Catalyst_5513B
set length 24 default
set logout 20
set banner motd ^C^C
!
#system
set system baud 9600
set system modem disable
set system name Catalyst_5513B
set system location Lab1
set system contact John Smith 913 555-7998
!
#snmp
set snmp community read-only
public
set snmp community read-write
private
set snmp community read-write-all public
set snmp rmon disable
set snmp trap disable module
set snmp trap disable chassis
set snmp trap disable bridge
set snmp trap disable repeater
set snmp trap disable vtp
set snmp trap disable auth
set snmp trap disable ippermit
set snmp trap disable vmps
set snmp trap disable entity
set snmp trap disable config
set snmp trap disable stpx
set snmp trap disable syslog
set snmp extendedrmon vlanmode disable
set snmp extendedrmon vlanagent disable
set snmp extendedrmon enable
!
#ip
set interface sc0 3 209.165.200.224 255.255.255.224
set interface sc0 up
set interface sl0 0.0.0.0 0.0.0.0
set interface sl0 up
set arp agingtime 1200
set ip redirect
enable
set ip unreachable
enable
set ip fragmentation enable
set ip route 0.0.0.0 209.165.200.224
set ip alias default
0.0.0.0
!
#Command alias
!
#vmps
set vmps server retry 3
set vmps server reconfirminterval 60
set vmps tftpserver 0.0.0.0 vmps-config-database.1
set vmps state disable
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-9
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
!
#dns
set ip dns disable
!
#tacacs+
set tacacs attempts 3
set tacacs directedrequest disable
set tacacs timeout 5
!
#authentication
set authentication login tacacs disable console
set authentication login tacacs disable telnet
set authentication enable tacacs disable console
set authentication enable tacacs disable telnet
set authentication login local enable console
set authentication login local enable telnet
set authentication enable local enable console
set authentication enable local enable telnet
!
#bridge
set bridge ipx snaptoether
8023raw
set bridge ipx 8022toether
8023
set bridge ipx 8023rawtofddi snap
!
#vtp
set vtp domain vsc3000
set vtp mode transparent
set vtp v2 disable
set vtp pruneeligible 2-1000
clear vtp pruneeligible 1001-1005
set vlan 1 name default type ethernet mtu 1500 said 100001 state active
set vlan 2 name green type ethernet mtu 1500 said 100002 state active
set vlan 3 name blue type ethernet mtu 1500 said 100003 state active
set vlan 4 name red type ethernet mtu 1500 said 100004 state active
set vlan 1002 name fddi-default type fddi mtu 1500 said 101002 state active
set vlan 1004 name fddinet-default type fddinet mtu 1500 said 101004 state active bridge
0x0 stp ieee
set vlan 1005 name trnet-default type trbrf mtu 1500 said 101005 state active bridge 0x0
stp ibm
set vlan 1003 name token-ring-default type trcrf mtu 1500 said 101003 state active parent
0 ring 0x0 mode srb aremaxhop 7 stemaxhop 7
set interface sc0 3 209.165.200.224 255.255.255.224 209.165.200.224
!
#spantree
#uplinkfast groups
set spantree uplinkfast disable
#backbonefast
set spantree backbonefast disable
set spantree enable all
#vlan 1
set spantree fwddelay 4 1
set spantree hello
2
1
set spantree maxage
20
1
set spantree priority 2000 1
#vlan 2
set spantree fwddelay 4 2
set spantree hello
2
2
set spantree maxage
20
2
set spantree priority 2000 2
#vlan 3
set spantree fwddelay 4 3
set spantree hello
2
3
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-10
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
set spantree maxage
20
3
set spantree priority 2000 3
#vlan 4
set spantree fwddelay 4 4
set spantree hello
2
4
set spantree maxage
20
4
set spantree priority 2000 4
#vlan 1003
set spantree fwddelay 15
1003
set spantree hello
2
1003
set spantree maxage
20
1003
set spantree priority 32768 1003
set spantree portstate 1003 block 0
set spantree portcost 1003 62
set spantree portpri 1003 4
set spantree portfast 1003 disable
#vlan 1005
set spantree fwddelay 15
1005
set spantree hello
2
1005
set spantree maxage
20
1005
set spantree priority 32768 1005
set spantree multicast-address 1005 ieee
!
#cgmp
set cgmp disable
set cgmp leave disable
!
#syslog
set logging console enable
set logging server disable
set logging level cdp 2 default
set logging level mcast 2 default
set logging level dtp 5 default
set logging level dvlan 2 default
set logging level earl 2 default
set logging level fddi 2 default
set logging level ip 2 default
set logging level pruning 2 default
set logging level snmp 2 default
set logging level spantree 2 default
set logging level sys 5 default
set logging level tac 2 default
set logging level tcp 2 default
set logging level telnet 2 default
set logging level tftp 2 default
set logging level vtp 2 default
set logging level vmps 2 default
set logging level kernel 2 default
set logging level filesys 2 default
set logging level drip 2 default
set logging level pagp 5 default
set logging level mgmt 5 default
set logging level mls 5 default
set logging level protfilt 2 default
set logging level security 2 default
set logging server facility LOCAL7
set logging server severity 4
set logging buffer 500
set logging timestamp disable
!
#ntp
set ntp broadcastclient disable
set ntp broadcastdelay 3000
set ntp client disable
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-11
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
clear timezone
set summertime disable
!
#set boot command
set boot config-register 0x2
set boot system flash bootflash:cat5000-sup3.4-5-1.bin
!
#permit list
set ip permit disable
!
#drip
set tokenring reduction enable
set tokenring distrib-crf disable
!
#igmp
set igmp disable
!
#protocolfilter
set protocolfilter disable
!
#mls
set mls enable
set mls flow destination
set mls agingtime 256
set mls agingtime fast 0 0
set mls nde disable
!
#standby ports
set standbyports enable
!
#module 1 : 2-port 10/100BaseTX Supervisor
set module name
1
set vlan 1
1/1-2
set port channel 1/1-2 off
set port enable
1/1-2
set port level
1/1-2 normal
set port speed
1/1-2 100
set port duplex
1/1-2 full
set port trap
1/1-2 disable
set port name
1/1-2
set port security
1/1-2 disable
set port broadcast 1/1-2 100%
set port membership 1/1-2 static
set port protocol 1/1-2 ip on
set port protocol 1/1-2 ipx auto
set cdp enable
1/1-2
set cdp interval 1/1-2 60
set trunk 1/1 on isl 1-1005
set trunk 1/2 on isl 1-1005
set spantree portfast
1/1-2 disable
set spantree portcost
1/1-2 3019
set spantree portpri
1/1-2 32
set spantree portvlanpri 1/1 0
set spantree portvlanpri 1/2 0
set spantree portvlancost 1/1 cost 3018
set spantree portvlancost 1/2 cost 3018
!
#module 2 : 2-port 10/100BaseTX Supervisor
set module name
2
set vlan 1
2/1-2
set port channel 2/1-2 off
set port enable
2/1-2
set port level
2/1-2 normal
set port speed
2/1-2 100
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-12
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
set port duplex
2/1-2 full
set port trap
2/1-2 disable
set port name
2/1-2
set port security
2/1-2 disable
set port broadcast 2/1-2 100%
set port membership 2/1-2 static
set port protocol 2/1-2 ip on
set port protocol 2/1-2 ipx auto
set cdp enable
2/1-2
set cdp interval 2/1-2 60
set trunk 2/1 desirable isl 1-1005
set trunk 2/2 desirable isl 1-1005
set spantree portfast
2/1-2 disable
set spantree portcost
2/1-2 3019
set spantree portpri
2/1-2 32
set spantree portvlanpri 2/1 0
set spantree portvlanpri 2/2 0
set spantree portvlancost 2/1 cost 3018
set spantree portvlancost 2/2 cost 3018
!
#module 3 : 24-port 10BaseT Ethernet
set module name
3
set module enable 3
set vlan 1
3/20-24
set vlan 2
3/17
set vlan 3
3/1-16,3/19
set port enable
3/1-24
set port level
3/1-24 normal
set port duplex
3/1-24 half
set port trap
3/1-24 disable
set port name
3/1-24
set port security
3/1-24 disable
set port broadcast 3/1-24 0
set port membership 3/1-24 static
set port protocol 3/1-24 ip on
set port protocol 3/1-24 ipx auto
set cdp enable
3/1-24
set cdp interval 3/1-24 60
set spantree portfast
3/1-24 enable
set spantree portcost
3/1-24 3100
set spantree portpri
3/1-24 32
!
#module 4 : 12-port 10/100BaseTX Ethernet
set module name
4
set module enable 4
set vlan 2
4/1-2
set vlan 3
4/7-8
set vlan 4
4/3-6
set port channel 4/1-4 off
set port channel 4/5-8 off
set port channel 4/9-12 off
set port enable
4/1-12
set port level
4/1-12 normal
set port speed
4/1-10 auto
set port speed
4/11-12 100
set port duplex
4/11-12 full
set port trap
4/1-12 disable
set port name
4/1-12
set port security
4/1-12 disable
set port broadcast 4/1-12 0
set port membership 4/1-12 static
set port protocol 4/1-12 ip on
set port protocol 4/1-12 ipx auto
set cdp enable
4/1-12
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-13
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
set cdp interval 4/1-12 60
set trunk 4/1 auto isl 1-1005
set trunk 4/2 auto isl 1-1005
set trunk 4/3 auto isl 1-1005
set trunk 4/4 auto isl 1-1005
set trunk 4/5 auto isl 1-1005
set trunk 4/6 auto isl 1-1005
set trunk 4/7 auto isl 1-1005
set trunk 4/8 auto isl 1-1005
set trunk 4/9 auto isl 1-1005
set trunk 4/10 auto isl 1-1005
set trunk 4/11 desirable isl 1-1005
set trunk 4/12 desirable isl 1-1005
set spantree portfast
4/1-12 enable
set spantree portcost
4/1,4/6-7,4/11-12 3019
set spantree portcost
4/2-5,4/8-10 3100
set spantree portpri
4/1-12 32
set spantree portvlanpri 4/1 0
set spantree portvlanpri 4/2 0
set spantree portvlanpri 4/3 0
set spantree portvlanpri 4/4 0
set spantree portvlanpri 4/5 0
set spantree portvlanpri 4/6 0
set spantree portvlanpri 4/7 0
set spantree portvlanpri 4/8 0
set spantree portvlanpri 4/9 0
set spantree portvlanpri 4/10 0
set spantree portvlanpri 4/11 0
set spantree portvlanpri 4/12 0
set spantree portvlancost 4/1 cost 3018
set spantree portvlancost 4/2 cost 3099
set spantree portvlancost 4/3 cost 3099
set spantree portvlancost 4/4 cost 3099
set spantree portvlancost 4/5 cost 3099
set spantree portvlancost 4/6 cost 3018
set spantree portvlancost 4/7 cost 3018
set spantree portvlancost 4/8 cost 3099
set spantree portvlancost 4/9 cost 3099
set spantree portvlancost 4/10 cost 3099
set spantree portvlancost 4/11 cost 3018
set spantree portvlancost 4/12 cost 3018
!
#module 5 empty
!
#module 6 empty
!
#module 7 empty
!
#module 8 empty
!
#module 9 empty
!
#module 10 empty
!
#module 11 empty
!
#module 12 : 1-port Route Switch
set module name
12
set port level
12/1 normal
set port trap
12/1 disable
set port name
12/1
set cdp enable
12/1
set cdp interval 12/1 60
set trunk 12/1 on isl 1-1005
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-14
OL-1150-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
set spantree portcost
12/1 3005
set spantree portpri
12/1 15
set spantree portvlanpri 12/1 160
set spantree portvlancost 12/1 cost 3004 4-8,11-15
!
#module 13 empty
!
#switch port analyzer
!set span 1 1/1 both inpkts disable
set span disable
!
#cam
set cam agingtime 1-4,1003,1005 300
end
Sample Configuration for Cisco Catalyst 5500 B RSM
To view the current configuration of the Cisco Catalyst 5500 B RSM, access the RSM interface, type
the following command in privileged mode, and press Enter:
Catalyst_5513B_RSM#show run
Output similar to the following appears:
Building configuration...
Current configuration:
!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Catalyst_5513B_RSM
!
enable password cisco
!
no ip domain-lookup
!
!
!
interface Vlan2
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 2 timers 1 3
standby 2 preempt
standby 2 authentication VSC3000
standby 2 ip 172.25.66.60
!
interface Vlan3
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 3 timers 1 3
standby 3 preempt
standby 3 authentication vsc3000
standby 3 ip 209.165.200.224
!
interface Vlan4
ip address 209.165.200.224 255.255.255.224
no ip redirects
standby 4 timers 1 3
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
C-15
Appendix C
Sample LAN Configurations
Sample Configuration for Cisco Catalyst 5500 B
standby 4 preempt
standby 4 authentication VSC3000
standby 4 ip 209.165.200.224
!
router eigrp 1
network 209.165.200.224
!
ip classless
!
snmp-server community public RO
snmp-server community private RW
snmp-server chassis-id public
snmp-server enable traps snmp
snmp-server enable traps appn alert
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps rtr
!
line con 0
line aux 0
line vty 0 4
password cisco
login
!
end
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
C-16
OL-1150-15
A P P E N D I X
D
Sample Installation Scripts
This appendix contains sample outputs from the following:
•
Sample Output from install.sh, page D-1
•
Updated Configuration File Sample, page D-10
•
Sample Configured snmpd.cnf File, page D-11
•
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files, page D-14
Sample Output from install.sh
Following is a sample output from the install script.
Note
For Software Release 7.4(10) and later, the install.log is renamed as MGC-install.log and stored in the
/var/adm directory. In addition, the pkgerrors.log is renamed to MGC_pkgerrors.log and moved to the
/var/adm directory.
va-cerulean# cd /cdrom/cdrom0
# ./install.sh
Use supplied admin file for unattended install? [n] [y,n,?,q] y
Install Cisco Media Gateway Controller Manager (Toolkit) package?
[n] [y,n,?,q] y
Base directory for Toolkit (default /opt/Toolkit) [?,q]
The CSCOgu000 utilities package must be installed prior to other components
but has not been detected on your system.
Would you like to install it now? [y] [y,n,?,q] y
Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q]
Enter CiscoMGC user name [mgcusr]
Enter CiscoMGC UID [20000]
Enter CiscoMGC group name [mgcgrp]
Enter CiscoMGC GID [20000]
[mgcgrp] group added
[mgcusr] user added
Modifying /etc/init.d/inetinit
Installation of <CSCOgu000> was successful.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-1
Appendix D
Sample Installation Scripts
Sample Output from install.sh
(c)1998 Cisco Systems, Inc. All Rights Reserved.
Unpublished -- rights reserved under the copyright
laws of the United States.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the Government
is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraphs
(c)(1) and (2) of Commercial Computer Software -Restricted Rights at 48 CFR 52.227-19, as applicable.
Cisco Systems, Inc.
13615 Dulles Technology Drive
Herndon, VA 20171
Installation of <CSCOga000> was successful.
Uncompressing ASP
Uncompressing DPNSS
Uncompressing EISUP
Uncompressing IOCCIP
Uncompressing IOCCTCP
Uncompressing ISDNIP
Uncompressing ISDNL3
Uncompressing ISDNPRI
Uncompressing LogServerd
Uncompressing MGCP
Uncompressing SS7
Uncompressing TALI
Uncompressing TCAP
Uncompressing almM
Uncompressing amDmpr
Uncompressing cdrDmpr
Uncompressing cfgM
Uncompressing cms
Installing converter
Uncompressing engine.no_smartalloc
Uncompressing engine.smartalloc
Uncompressing foverd
Uncompressing ioChanMgr
Uncompressing measMgr
Uncompressing mmBldCfg
Uncompressing mmdbd
Uncompressing mml
Uncompressing pom
Uncompressing procM
Uncompressing replicator
Installing libACE.so
Uncompressing lib_cmg.so
Uncompressing lib_cxn.so
Uncompressing lib_eng.so
Uncompressing lib_rmg.so
Installing libcms.so
Uncompressing libconvutil.so
Uncompressing libda.so
Uncompressing libmmdb.so
Uncompressing libpolbase.so
Uncompressing libpolcomp.so
Uncompressing libpolfiles.so
Uncompressing libpolnuman.so
Uncompressing libpolroute.so
Uncompressing libpom.so
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-2
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Output from install.sh
Uncompressing libpxe.so
Uncompressing libpxelog.so
Uncompressing librudp.so
Uncompressing libsa.so
Installing libsunmath.so.1
Installing libtten.so
Uncompressing libxe.so
Updating parameters for CiscoMGC
Updating parameters for SW_Layout.cfg
Updating parameters for getConfig
Updating parameters for log_rotate.sh
Updating parameters for startAudit.sh
Updating parameters for diagdata
Updating parameters for .cshrc
Updating parameters for .dump-prov
Updating parameters for actDPlan
Updating parameters for backup.sh
Updating parameters for cdbscript.sh
Updating parameters for config-lib
Updating parameters for diskmonitor.sh
Updating parameters for failover_nfs.sh
Updating parameters for getDPlan
Updating parameters for init.tcl
Updating parameters for listDPlan
Updating parameters for migrateDPlan.sh
Updating parameters for perf_config
Updating parameters for pmctrl
Updating parameters for reconfig-all.mml
Updating parameters for restore.sh
Updating parameters for rmsem.sh
Updating parameters for startAudit.mml
Updating parameters for stop-all
Installing /opt/CiscoMGC/man/mml.help.tar.gz
Installation of <CSCOga001> was successful.
Modifying /etc/syslog.conf
Updating parameters for .odbc.ini
Updating parameters for backupDb.sh
Updating parameters for restoreDb.sh
Uncompressing acroread.tar
Uncompressing doc.tar
Uncompressing timesten.tar
Uncompressing ttclient.tar
Uncompressing ttserver.tar
Preparing to install TimesTen 3.2 in /opt on va-cerulean
Executing TimesTen installation script...
Of the three components:
[1] TimesTen Client/Server and Data Manager
[2] TimesTen Data Manager Only
[3] TimesTen Client Only
Install in /opt/TimesTen32
Creating /opt/TimesTen32 ...
extracting /opt/ttdb-install/SunOS251/ttserver.tar ...
System logging appears to be configured correctly.
(TimesTen syslog messages seem to be recorded in the file '/var/adm/messages')
Starting the daemon for solaris ...
Server startup scripts not required - ignored
Installing TimesTen Server...
What is the DNS name, host name, or IP address of the server [va-cerulean]:
What is the TCP/IP port number that you want the TimesTen Server to listen on [23232]:
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-3
Appendix D
Sample Installation Scripts
Sample Output from install.sh
What is Filename and Location of server.odbc.ini file
[/var/TimesTen32/32/server/server.odbc.ini]:
TimesTen Connect Configuration completed.
extracting /opt/ttdb-install/SunOS251/doc.tar ...
Install complete
TimesTen installation script returned status 0
Sun Microsystems Inc.
SunOS 5.6
Generic August 1997
You have new mail.
Restoring database contents for DSN=howdydb from /opt/CiscoMGC/etc/export.ttdb
Restoring file /opt/TimesTen32/datastore/howdydb.ds1 from backup
Restoring file /opt/TimesTen32/datastore/howdydb.log1 from backup
The restore process is being initiated
Restore complete
Installation of <CSCOga002> was successful.
Uncompressing mmSAgt
Uncompressing sagt
Updating parameters for snmpd
Installation of <CSCOga003> was successful.
Installing /opt/Toolkit/Packages/Packages.tar.gz
Installing /opt/Toolkit/bytecode/cdr/cdr.tar.gz
Installing /opt/Toolkit/bytecode/log/Viewer.tar.gz
Installing /opt/Toolkit/bytecode/toolbar/toolbar.tar.gz
Installing /opt/Toolkit/bytecode/tv/tv.tar.gz
Installing /opt/Toolkit/tcl/tcl.tar.gz
Updating parameters for init.tcl
Updating parameters for toolbar.sh
Setting VERSION=8.1(1) in version.dat
Installation of <CSCOga004> was successful.
Uncompressing ASP_NotRealProtocol.mdo
Uncompressing CALLVER.mdo
Uncompressing CALLVER_GENERIC_ANALYSIS.mdo
Installing CALLVER_LCM.mdo
Uncompressing CDR_MAN.mdo
Uncompressing CONNECTION_PLANE_MANAGER.mdo
Uncompressing EISUP.mdo
Uncompressing GENERIC_ANALYSIS.mdo
Uncompressing IN_TRIGGER.mdo
Uncompressing cc.mdo
Uncompressing dummy.mdo
Uncompressing lcm.mdo
Installation of <CSCOgi000> was successful.
Uncompressing ISUPV2_FINNISH96.mdo
Uncompressing ISUPV2_FRENCH.mdo
Uncompressing ISUPV2_GERMAN.mdo
Uncompressing ISUPV2_JAPAN.mdo
Uncompressing ISUPV2_NTT.mdo
Uncompressing ISUPV2_SPANISH.mdo
Uncompressing ISUPV2_SWISS.mdo
Uncompressing ISUPV2_TOKYO.mdo
Installation of <CSCOgi001> was successful.
Uncompressing ISUPV1_POLI.mdo
Uncompressing Q767_BASE.mdo
Uncompressing Q767_BRAZIL.mdo
Uncompressing Q767_ITAL.mdo
Uncompressing Q767_ITAL_INTERCONNECT.mdo
Uncompressing Q767_MEXICAN.mdo
Uncompressing Q767_RUSS.mdo
Uncompressing Q767_SPAN.mdo
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-4
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Output from install.sh
Uncompressing Q767_SWED.mdo
Uncompressing Q767_TELSTRA.mdo
Installation of <CSCOgi002> was successful.
Uncompressing Q721_BASE.mdo
Uncompressing Q721_CHINA.mdo
Uncompressing Q721_FRENCH.mdo
Uncompressing Q721_PHILLIPINE.mdo
Installation of <CSCOgi003> was successful.
Uncompressing ANSISS7_92.mdo
Uncompressing ANSISS7_CLEAR.mdo
Uncompressing ANSISS7_STANDARD.mdo
Uncompressing T113_BELL.mdo
Installation of <CSCOgi004> was successful.
Uncompressing ISUPV3.mdo
Uncompressing ISUPV3_UK.mdo
Installation of <CSCOgi005> was successful.
Uncompressing BTNUP_BTNR167.mdo
Uncompressing BTNUP_IUP.mdo
Installation of <CSCOgi006> was successful.
Uncompressing ATT_41459.mdo
Uncompressing ATT_41459_C2.mdo
Uncompressing BELL_1268.mdo
Uncompressing BELL_1268_C3.mdo
Uncompressing ETS_300_102.mdo
Uncompressing ETS_300_121.mdo
Uncompressing ETS_300_172.mdo
Uncompressing ETS_300_356.mdo
Uncompressing NTT_INS_1500.mdo
Installation of <CSCOgi007> was successful.
Uncompressing DPNSS_BTNR188.mdo
Installation of <CSCOgi008> was successful.
Uncompressing Q761_ARGENTINA.mdo
Uncompressing Q761_AUSTRL.mdo
Uncompressing Q761_BASE.mdo
Uncompressing Q761_CHILE.mdo
Uncompressing Q761_CHINA.mdo
Uncompressing Q761_JAPAN.mdo
Uncompressing Q761_KOREAN.mdo
Uncompressing Q761_SINGAPORE.mdo
Uncompressing Q761_TAIWAN.mdo
Uncompressing Q761_THAILAND.mdo
Installation of <CSCOgi009> was successful.
Uncompressing BELL_SGCP.mdo
Installation of <CSCOgi010> was successful.
Uncompressing ASP_NotRealProtocol.so
Uncompressing CALLVER.so
Uncompressing CALLVER_GENERIC_ANALYSIS.so
Uncompressing CDR_MAN.so
Uncompressing CONNECTION_PLANE_MANAGER.so
Uncompressing EISUP.so
Uncompressing GENERIC_ANALYSIS.so
Uncompressing IN_TRIGGER.so
Uncompressing cc.so
Uncompressing dummy.so
Uncompressing lcm.so
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-5
Appendix D
Sample Installation Scripts
Sample Output from install.sh
Installation of <CSCOgg000> was successful.
Uncompressing ISUPV2_FINNISH96.so
Uncompressing ISUPV2_FRENCH.so
Uncompressing ISUPV2_GERMAN.so
Uncompressing ISUPV2_JAPAN.so
Uncompressing ISUPV2_NTT.so
Uncompressing ISUPV2_SPANISH.so
Uncompressing ISUPV2_SWISS.so
Uncompressing ISUPV2_TOKYO.so
Installation of <CSCOgg001> was successful.
Uncompressing ISUPV1_POLI.so
Uncompressing Q767_BASE.so
Uncompressing Q767_BRAZIL.so
Uncompressing Q767_ITAL.so
Uncompressing Q767_ITAL_INTERCONNECT.so
Uncompressing Q767_MEXICAN.so
Uncompressing Q767_RUSS.so
Uncompressing Q767_SPAN.so
Uncompressing Q767_SWED.so
Uncompressing Q767_TELSTRA.so
Installation of <CSCOgg002> was successful.
Uncompressing Q721_BASE.so
Uncompressing Q721_CHINA.so
Uncompressing Q721_FRENCH.so
Uncompressing Q721_PHILLIPINE.so
Installation of <CSCOgg003> was successful.
Uncompressing ANSISS7_92.so
Uncompressing ANSISS7_CLEAR.so
Uncompressing ANSISS7_STANDARD.so
Uncompressing T113_BELL.so
Installation of <CSCOgg004> was successful.
Uncompressing ISUPV3.so
Uncompressing ISUPV3_UK.so
Installation of <CSCOgg005> was successful.
Uncompressing BTNUP_BTNR167.so
Uncompressing BTNUP_IUP.so
Installation of <CSCOgg006> was successful.
Uncompressing ATT_41459.so
Uncompressing ATT_41459_C2.so
Uncompressing BELL_1268.so
Uncompressing BELL_1268_C3.so
Uncompressing ETS_300_102.so
Uncompressing ETS_300_121.so
Uncompressing ETS_300_172.so
Uncompressing ETS_300_356.so
Uncompressing NTT_INS_1500.so
Installation of <CSCOgg007> was successful.
Uncompressing DPNSS_BTNR188.so
Installation of <CSCOgg008> was successful.
Uncompressing Q761_ARGENTINA.so
Uncompressing Q761_AUSTRL.so
Uncompressing Q761_BASE.so
Uncompressing Q761_CHILE.so
Uncompressing Q761_CHINA.so
Uncompressing Q761_JAPAN.so
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-6
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Output from install.sh
Uncompressing
Uncompressing
Uncompressing
Uncompressing
Q761_KOREAN.so
Q761_SINGAPORE.so
Q761_TAIWAN.so
Q761_THAILAND.so
Installation of <CSCOgg009> was successful.
Uncompressing BELL_SGCP.so
Installation of <CSCOgg010> was successful.
Installing ca
Installing callver
Installing get_trc.sh
Installing sim
Installing simWriter
Uncompressing sp
Installation of <CSCOgt001> was successful.
Installing gen
Installing mdl
Installation of <CSCOgt002> was successful.
Updating parameters for XECfgParm.dat
Updating parameters for trigger.template
Updating parameters for migrate
Updating parameters for migrateTKGFile
Installing /opt/CiscoMGC/etc/CONFIG_LIB/migrate_mod.tar.gz
Installing /opt/CiscoMGC/etc/migrate/migrate_scr.tar.gz
Migrating .dat files in /opt/CiscoMGC/etc
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.dialPlan
Backing up .dat file
Backing up database
Sun Microsystems Inc.
SunOS 5.6
Generic August 1997
You have new mail.
migrate_XECfgParm: setting *.transpathId = 01
migrate_XECfgParm: setting *.ownTranspathId = 01
migrate_XECfgParm: setting *.peerTranspathId = 02
migrate_XECfgParm: setting foverd.conn1Type = socket
migrate_XECfgParm: setting foverd.conn2Type = socket
migrate_XECfgParm: setting *.IP_Addr1 = 172.24.238.27
migrate_XECfgParm: setting *.IP_Addr2 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr3 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr4 = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrLocalA = 172.24.238.27
migrate_XECfgParm: setting *.ipAddrLocalB = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrPeerA = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrPeerB = 0.0.0.0
migrate_XECfgParm: setting foverd.abswitchPort = /dev/null
migrate_XECfgParm: setting XE.ARUWriteDevice = /dev/null
migrate_XECfgParm: setting XE.systemType = SPARC
migrate_XECfgParm: setting foverd.ipLocalPortA = 0
migrate_XECfgParm: setting foverd.ipLocalPortB = 0
migrate_XECfgParm: setting foverd.ipPeerPortA = 0
migrate_XECfgParm: setting foverd.ipPeerPortB = 0
migrate_XECfgParm: setting replicator.portDataChannelSend = 2968
migrate_XECfgParm: setting replicator.portDataChannelRecv = 2970
migrate_XECfgParm: setting replicator.portCommChannelSend = 2972
migrate_XECfgParm: setting replicator.portCommChannelRecv = 2974
migrate_XECfgParm: setting *.SyscheckpointEnabled = false
migrate_XECfgParm: setting *.desiredPlatformState = standalone
migrate_XECfgParm: setting *.stPort = 0
migrate_XECfgParm: setting pom.dataSync = false
migrate_XECfgParm: setting *.chkPtPort = 2001
migrate_XECfgParm: setting engine.SysPropagateChanAvail = false
migrate_XECfgParm: setting engine.SysGeneratedCode = false
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-7
Appendix D
Sample Installation Scripts
Sample Output from install.sh
migrate_XECfgParm: setting engine.SysScreeningCheck = false
migrate_XECfgParm: setting engine.SysGRSTimerInterval = 0
migrate_XECfgParm: setting engine.SysGRSBlockSize = 0
migrate_XECfgParm: setting engine.SysVirtualSwitch = 0
migrate_XECfgParm: setting engine.MDLANumberScreening = 0
migrate_XECfgParm: setting diskmonitor.Limit = 7
migrate_XECfgParm: setting diskmonitor.Threshold = 80
migrate_XECfgParm: setting diskmonitor.SoftLimit = false
migrate_XECfgParm: setting *.logPrio = Error
migrate_XECfgParm: setting *.logDirectory = ../var/log
migrate_XECfgParm: setting *.logFileNamePrefix = platform
migrate_XECfgParm: setting engine.SysCdrCollection = false
migrate_XECfgParm: setting engine.CDRencodingFormat = AnsiCDB
migrate_XECfgParm: setting engine.CDRtimeStamp = S
migrate_XECfgParm: setting engine.CDRmessageTypes = "1010,1020,1030,1040,1050,1060,1070"
migrate_XECfgParm: setting *.numberOfThreads = 0
migrate_XECfgParm: setting *.dataSourceName = howdydb
migrate_XECfgParm: setting *.maxNumLinks = 32
migrate_XECfgParm: setting *.maxNumPRIL3Links = 504
migrate_XECfgParm: setting *.maxNumMGCPLinks = 1000
migrate_XECfgParm: setting *.dataCommitTime = 10
migrate_XECfgParm: setting MML.timeout = 10000
migrating version.dat
migrating propSet.dat
migrating variant.dat
migrating alarmCats.dat
migrating compTypes.dat
migrating tables.dat
migrating buckets.dat
migrating alarmTable.dat
migrating thresholds.dat
migrating measProfs.dat
migrating measCats.dat
migrating mdlProcess.dat
migrating extProcess.dat
migrating extNodeTypes.dat
migrating properties.dat
migrating dial plan and route analysis files
Migrating database from 7.1006 to 9.0
Database successfully migrated to 9.0
migrating version.dat
migrating propSet.dat
migrating variant.dat
migrating alarmCats.dat
migrating compTypes.dat
migrating tables.dat
migrating buckets.dat
migrating alarmTable.dat
migrating thresholds.dat
migrating measProfs.dat
migrating measCats.dat
migrating mdlProcess.dat
migrating extProcess.dat
migrating extNodeTypes.dat
migrating properties.dat
migrating files.dat
migrating components.dat
migrating processes.dat
migrating services.dat
migrating dial plan and route analysis files
migrating TimesTen database
migrating XECfgParm.dat ...
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-8
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Output from install.sh
starting migration ...
migrating from version 7.1005 to version 7.1006 ...
skipping... 7.0005 to 7.1006
migrating from version 7.1006 to version 9.0 ...
migration completed successfully
No data file changes required to support CMS
trigger.dat exists: not overwriting with trigger.template
Installation of <CSCOgc001> was successful.
Beginning Check of System Performance Requirements
Number of CPUs in system 1
Memory size: 128 Megabytes
The sparc processor operates at 248 MHz,
WARNING Insufficient Memory to run CiscoMGC - should be at least 2048 Megabytes!
!
Swap is total: 19224k bytes allocated + 10448k reserved = 29672k used, 589464k a
vailable
Please Verify that you have over 4000000K Available swap
install.sh: setting *.numberOfThreads = 0
Configure System for (1)Standard Performance Profile (2) Maximum Sustained Calls (3)
Maximum Call Throughput
Enter 1, 2 or 3
Configure System for (1) Standard Performance Profile (2) Maximum Sustained Calls (3)
Maximum Call Throughput
Enter 1,2, or 3
3
Optimize for Maximum Call Throughput
install.sh: setting engine.SysMdlMemoryReduction = 0
install.sh: setting engine.CALL_MEM_BLOCK_SIZE = 140000
install.sh: setting engine.CALL_MEM_CHUNK_SIZE = 140000
Installation completed Tue Sep 5 16:26:39 EDT 2000
Installation log can be found in /tmp/install.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-9
Appendix D
Sample Installation Scripts
Updated Configuration File Sample
Updated Configuration File Sample
Following is an example of an updated configuration file. This file is located in /opt/CiscoMGC/etc/.
#---------------- MGC Environment Configuration Tool Usage -------------------#
REQUIRED STARTUP PARAMETERS
#
DO NOT MOVE THESE PARAMETERS BEYOND THIS BOX
*.platformId =
1
#*.transpathId =
01
# Transpath Id for ASN
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.transpathId = 1
# Transpath Id for ASN
#*.desiredPlatformState =
standalone
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.desiredPlatformState = master
#*.SyscheckpointEnabled =
false
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.SyscheckpointEnabled = true
#*.ipAddrLocalA =
0.0.0.0
# Should be same as *.IP_Addr1
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.ipAddrLocalA = 192.168.0.1
# Should be same as *.IP_Addr1
#*.ipAddrLocalB =
0.0.0.0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.ipAddrLocalB = 127.0.0.1
#*.ipAddrPeerA =
0.0.0.0
# Failover peer's address
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.ipAddrPeerA = 0.0.0.012
# Failover peer's address
#*.ipAddrPeerB =
0.0.0.0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.ipAddrPeerB = 0.0.0.02
#*.IP_Addr1 =
0.0.0.0
# Address of interface
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03
*.IP_Addr1 = 192.168.0.1
# Address of interface on motherboard
#*.IP_Addr2 =
0.0.0.0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03
*.IP_Addr2 = 127.0.0.1
#*.IP_Addr3 =
0.0.0.0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03
*.IP_Addr3 = 127.0.0.2
#*.IP_Addr4 =
0.0.0.0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03
*.IP_Addr4 = 127.0.0.3
on motherboard
GMT 2000
GMT 2000
GMT 2000
GMT 2000
#*.stPort =
0
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.stPort = 7000
#engine.SysVirtualSwitch =
0
# 0=Nailed-Up, 1=Switched-VSC, 2=Switched-JCS
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
engine.SysVirtualSwitch = 2
# 0=Nailed-Up, 1=Switched-VSC, 2=Switched-JCS
#pom.dataSync =
false # don't synch slave data with master
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
pom.dataSync = true # don't synch slave data with master
*.numberOfThreads =
0
#engine.SysConnectDataAccess =
false # call screening using the database
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
engine.SysConnectDataAccess = true # call screening using the database
##### Last modified by kiettran/MGC Env Cfg Tool: Wed Oct 11 22:32:03 GMT 2000
*.OwnClli = TTTTSSBBXXX
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-10
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured snmpd.cnf File
Sample Configured snmpd.cnf File
The following shows a sample snmpd.cnf file.
Note
This sample configuration enables both snmpv1 and snmpv2 traps. Therefore, you will see two coldStart
traps when the software is initialized—one for version1 and one for version 2.
# Entry type: sysDescr
# Entry format: octetString
sysDescr "SNMPv3 agent from Cisco Systems, Inc."
# Entry type: sysObjectID
# Entry format: OID
sysObjectID transpath
# Entry type: sysLocation
# Entry format: octetString
sysLocation "Herndon, Virginia"
# Entry type: sysContact
# Entry format: octetString
sysContact "Cisco Systems, Inc.
+1 703 484 3000"
# Entry type: sysName
# Entry format: octetString
sysName "NSSU - MGC"
# Entry type: snmpEnableAuthenTraps
# Entry format: integer
snmpEnableAuthenTraps 1
# Entry type: MAX_THREADS
# Entry format: integer
MAX_THREADS 25
# Entry type: MAX_PDU_TIME
# Entry format: integer
MAX_PDU_TIME 80000
# Entry type: MAX_OUTPUT_WAITING
# Entry format: integer
MAX_OUTPUT_WAITING 65536
# Entry type: MAX_SUBAGENTS
# Entry format: integer
MAX_SUBAGENTS 15
# Entry type: subagent
# Entry format: octetString
#Entry type: snmpCommunityEntry
#Format: snmpCommunityIndex (text)
#
snmpCommunityName (text)
#
snmpCommunitySecurityName (text)
#
snmpCommunityContextEngineID (octetString)
#
snmpCommunityContextName (text)
#
snmpCommunityTransportTag (text)
#
snmpCommunityStorageType (nonVolatile, permanent, readOnly)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-11
Appendix D
Sample Installation Scripts
Sample Configured snmpd.cnf File
snmpCommunityEntry
snmpCommunityEntry
snmpCommunityEntry
admin mgcusr mgcusr localSnmpID - - nonVolatile
readonly public public localSnmpID - - nonVolatile
user private private localSnmpID - - nonVolatile
# Entry type: communityEntry
# Entry format: srCommunityAuthSnmpID
#
srCommunityName
#
srCommunityGroupName
#
srCommunityContextSnmpID
#
srCommunityContextName
#
srCommunityTransportLabel
#
srCommunityMemoryType
(snmpID)
(textOctetString)
(textOctetString)
(snmpID)
(textOctetString)
(textOctetString)
(integer)
# Entry type: snmpEngineBoots
# Entry format: integer
snmpEngineBoots 3
#Entry type: usmUserEntry
#Format: usmUserEngineID (octetString)
#
usmUserName (text)
#
usmUserAuthProtocol (OID)
#
usmUserPrivProtocol (OID)
#
usmUserStorageType (nonVolatile, permanent, readOnly)
#
usmTargetTag (text)
#
AuthKey (octetString)
#
PrivKey (octetString)
#Entry type: vacmAccessEntry
#Format: vacmGroupName (text)
#
vacmAccessContextPrefix (text)
#
vacmAccessSecurityModel (snmpv1, snmpv2c, snmpv2s, usm, http)
#
vacmAccessSecurityLevel (noAuthNoPriv, authNoPriv, authPriv)
#
vacmAccessContextMatch (exact, prefix)
#
vacmAccessReadViewName (text)
#
vacmAccessWriteViewName (text)
#
vacmAccessNotifyViewName (text)
#
vacmAccessStorageType (nonVolatile, permanent, readOnly)
vacmAccessEntry User - snmpv1 noAuthNoPriv exact All RemoteWrite All \
nonVolatile
vacmAccessEntry User - snmpv2c noAuthNoPriv exact All RemoteWrite All \
nonVolatile
vacmAccessEntry Guest - snmpv1 noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry Guest - snmpv2c noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry SuperUser - snmpv1 noAuthNoPriv exact All Write All \
nonVolatile
vacmAccessEntry SuperUser - snmpv2c noAuthNoPriv exact All Write All \
nonVolatile
#Entry type: vacmSecurityToGroupEntry
#Format: vacmSecurityModel (snmpv1, snmpv2c, snmpv2s, usm, http)
#
vacmSecurityName (text)
#
vacmGroupName (text)
#
vacmSecurityToGroupStorageType (nonVolatile, permanent, readOnly)
vacmSecurityToGroupEntry snmpv1 mgcusr SuperUser nonVolatile
vacmSecurityToGroupEntry snmpv1 public Guest nonVolatile
vacmSecurityToGroupEntry snmpv1 private User nonVolatile
vacmSecurityToGroupEntry snmpv2c mgcusr SuperUser nonVolatile
vacmSecurityToGroupEntry snmpv2c public Guest nonVolatile
vacmSecurityToGroupEntry snmpv2c private User nonVolatile
#Entry type: vacmViewTreeFamilyEntry
#Format: vacmViewTreeFamilyViewName (text)
#
vacmViewTreeFamilySubtree (OID)
#
vacmViewTreeFamilyMask (octetString)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-12
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured snmpd.cnf File
#
vacmViewTreeFamilyType (included, excluded)
#
vacmViewTreeFamilyStorageType (nonVolatile, permanent, readOnly)
vacmViewTreeFamilyEntry All iso - included nonVolatile
vacmViewTreeFamilyEntry All 0.0 - included nonVolatile
vacmViewTreeFamilyEntry All hrSWRunEntry.0.2147483647 ff:df excluded \
nonVolatile
vacmViewTreeFamilyEntry All hrSWRunPerfEntry.0.2147483647 ff:df excluded \
nonVolatile
vacmViewTreeFamilyEntry Write iso - included nonVolatile
vacmViewTreeFamilyEntry Write mib_2 - excluded nonVolatile
vacmViewTreeFamilyEntry RemoteWrite iso - included nonVolatile
vacmViewTreeFamilyEntry RemoteWrite mib_2 - excluded nonVolatile
vacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.1 ff:f7 excluded \
nonVolatile
vacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.2 ff:f7 excluded \
nonVolatile
vacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.3 ff:f7 excluded \
nonVolatile
vacmViewTreeFamilyEntry RemoteWrite critAppProcEntry.0.4 ff:f7 excluded \
nonVolatile
#Entry type: snmpNotifyEntry
#Format: snmpNotifyName (text)
#
snmpNotifyTag (text)
#
snmpNotifyType (trap(1), inform(2))
#
snmpNotifyStorageType (nonVolatile, permanent, readOnly)
snmpNotifyEntry 32 TrapSink trap nonVolatile
#Entry type: snmpTargetAddrEntry
#Format: snmpTargetAddrName (text)
#
snmpTargetAddrTDomain (snmpUDPDomain, snmpIPXDomain, etc.)
#
snmpTargetAddrTAddress (transport address,i.e. 192.147.142.254:0)
#
snmpTargetAddrTimeout (integer)
#
snmpTargetAddrRetryCount (integer)
#
snmpTargetAddrTagList (text)
#
snmpTargetAddrParams (text)
#
snmpTargetAddrStorageType (nonVolatile, permanent, readOnly)
#
snmpTargetAddrTMask (transport mask, i.e. 255.255.255.255:0)
#
snmpTargetAddrMMS (integer)
snmpTargetAddrEntry 34 snmpUDPDomain 127.0.0.1:0 100 3 TrapSink \
v2cExampleParams nonVolatile 255.255.255.255:0 2048
#Entry type: snmpTargetParamsEntry
#Format: snmpTargetParamsName (text)
#
snmpTargetParamsMPModel (integer)
#
snmpTargetParamsSecurityModel (snmpv1, snmpv2c, snmpv2s, usm)
#
snmpTargetParamsSecurityName (text)
#
snmpTargetParamsSecurityLevel (noAuthNoPriv,authNoPriv,authPriv)
#
snmpTargetParamsStorageType (nonVolatile, permanent, readOnly)
snmpTargetParamsEntry v1ExampleParams 0 snmpv1 public noAuthNoPriv \
nonVolatile
snmpTargetParamsEntry v2cExampleParams 1 snmpv2c public noAuthNoPriv \
nonVolatile
#Entry type: snmpNotifyFilterProfileEntry
#Format: snmpTargetParamsName (text)
#
snmpNotifyFilterProfileName (text)
#
snmpNotifyFilterProfileStorageType (nonVolatile,permanent,readOnly)
#Entry type: snmpNotifyFilterEntry
#Format: snmpNotifyFilterProfileName (text)
#
snmpNotifyFilterSubtree (OID)
#
snmpNotifyFilterMask (octetString)
#
snmpNotifyFilterType (included, excluded)
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-13
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
#
snmpNotifyFilterStorageType
(nonVolatile, permanent, readOnly)
#Entry type: httpUserNameEntry
#Format: httpUserName (text)
#
httpUserGroupName (text)
#
httpUserTransportLabel (text)
#
httpUserStorageType (nonVolatile, permanent, readOnly)
#
Password (octetString)
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
The following sample Cisco MGC 9.2(2) XECfgParm.dat files are located in the /opt/CiscoMGC/etc
directory.
# File: XECfgParm.dat
#
# Purpose:
#
# This file contains configuration parameters that may be accessed by
# XE application programs at run-time.
#
# All lines beginning with a '#' are comments and WILL NOT BE READ BY
# PROGRAMS. Thus application overrides of the default parameter values
# can be easily added and removed by removing/added a '#'.
#
#-----------------------------------------------------------------------------# Default parameter values have a facility name of "*" and
# will be used if no match is found on a specific facility name
#-----------------------------------------------------------------------------# Specific Facility names are as follows:
#
# logger
- Log Server
# foverd
- Failover Daemon
# MML
- MML
# procM
- Process Manager
# cdrDmpr
- CDR Dumper
# cfgM
- Configuration Manager
# engine
- call processing engine
# ioChanMgr - I/O Channel Managers
# pom
- Provisioning Object Manager
# measM
- Measurement Manager
# OPERSAGT - Operational SNMP Agent
# PROVSAGT - Provisioning SNMP Agent
# mmSAgt
- Measurement Manager SNMP Agent
# almM
- Alarm Manager
# replicator- Replicator
# mmdb
- TimesTen Main Memory Data Base Process
# amDmpr
- Alarm / Measurement Dumper
# ioChanCtl - controls all channel controllers
#
#----Special Paremeter Section---# callver
- call verification utility
# diskmonitor - disk monitor shell script
# XE
- Execution Environment
#
#-----------------------------------------------------------------------------#---------------- MGC Environment Configuration Tool Usage -------------------#
REQUIRED STARTUP PARAMETERS
#
DO NOT MOVE THESE PARAMETERS BEYOND THIS BOX
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-14
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
*.platformId =
1
*.transpathId = 01
# MIGRATED
*.ownTranspathId = 01
# MIGRATED
*.peerTranspathId = 02
# MIGRATED
*.MGC_CDR_NODE_ID = BUTTERFLY-HENDRIX-NODE
# MIGRATED
*.desiredPlatformState = master
# MIGRATED
*.SyscheckpointEnabled = true
# MIGRATED
*.SysConnectDataAccess = true
# MIGRATED
*.GWClearChannelAlgorithm = null
# MIGRATED
*.ipAddrLocalA = 10.82.82.11
# MIGRATED
*.ipAddrLocalB = 0.0.0.0
# MIGRATED
*.ipAddrPeerA = 10.82.80.80
# MIGRATED
*.ipAddrPeerB = 0.0.0.0
# MIGRATED
*.IP_Addr1
*.IP_Addr2
*.IP_Addr3
*.IP_Addr4
=
=
=
=
10.82.82.11
# MIGRATED
0.0.0.0
# MIGRATED
0.0.0.0
# MIGRATED
0.0.0.0
# MIGRATED
*.stPort = 7001
# MIGRATED
engine.SysVirtualSwitch = 0
# MIGRATED
pom.dataSync = true
# MIGRATED
foverd.ipLocalPortA = 1052
# MIGRATED
foverd.ipPeerPortA = 1051
# MIGRATED
foverd.ipLocalPortB = 1054
# MIGRATED
foverd.ipPeerPortB = 1053
# MIGRATED
*.numberOfThreads = 0
#-----------------# CVT Parameters
#-----------------#*.OwnClli = TTTT-SS-BB-XXX
#*.OwnClli = 1-22-33-444
#
REQUIRED STARTUP PARAMETERS
#
DO NOT MOVE THESE PARAMETERS BEYOND THIS BOX
#---------------- MGC Environment Configuration Tool Usage -------------------*.disableMeas =false
*.sm_meas_baseaddr = 3400
# T ==> Don't accumulate meas in shared mem
# shared memory based address
*.tempDir =
/tmp
# temporary directory
*.dataDir =
../var # volatile data directory
*.homeDirRoot =
/opt/CiscoMGC
*.logDirectory = ../var/log
# MIGRATED
*.logFileNamePrefix = platform
# MIGRATED
*.logPrio = Error
# MIGRATED
*.logMsgDrop =
true
*.eventTrace =
false
*.debugLevel =
high
*.tablesFile =
../etc/tables.dat # tables that can be loaded
*.autonomous
=
false
*.runAsDaemon =
true
*.chkPtPort = 2001
# MIGRATED
*.maxNumLinks = 32
# MIGRATED
*.maxLinksPerSessionSet =
4
# max links per SS7 sessionSet
*.maxNumDChansPerIOCC = 504
# MIGRATED
*.maxNumMGCPLinks = 1000
# MIGRATED
*.maxNumSIPLinks =
4
*.maxTrueOPCs =
6
# max true OPCs per MGC
*.maxCapOPCsPerTrueOPC =8 # max cap OPCs per true OPC
*.dataSourceName = howdydb
# MIGRATED
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
*.dataCommitTime = 10
# MIGRATED
*.OverdecadicDigitsSupported = false
# MIGRATED
*.DataBaseAccessError = 0
# MIGRATED
*.VirtualMemTimerInterval = 2000 # sampling frequency of virtual memory
*.MemAddressTimerInterval =1500 # sampling frequency of memory address space of processes
*.CallRateTimerInterval = 1000 # sampling frequency of the call rate computations
*.CPUTimerInterval = 1000
# MIGRATED
*.CallCutoffTimer = 0
# MIGRATED
#-----------------------------------------------------------------------# Log Server logfile locations
#-----------------------------------------------------------------------# daemonAddr is socket port for logger daemon
logger.daemonAddr = ../var/lsd_addr
# NEW logfile rotation size max in Megabytes
logger.fileRotateSize = 100
# NEW logfile rotation interval in minutes (24 hrs default)
logger.fileRotateInterval = 1440
# numThreads can be 0 or 1, if 1 then logger client runs in its
# own thread
logger.numThreads = 0
#------------------------------------------------------------------------# Facility specific parameters
#
The remainder of this file pertains to parameters and parameter overrides
#
for individual facilitites.
#
# LogPrio and autonomous are changed for debug testing only. Otherwise
# everyone should use the defaults above (except MML, see below.)
#------------------------------------------------------------------------# Specialized logging level for debug, fault isolation
#
# Usage of these debug parameters could cause the system to use up
# space more rapidly than normal. If the DISK alarm is activated because
# of this activity, certain files in /opt/CiscoMGC/var/spool will be erased.
#
#ioChanCtl.logPrio =
Debug
#SS7.logPrio =
Debug
#ioChanMgr.logPrio =
Debug
# procM.logPrio =
Debug
# engine.logPrio =
Debug
# PROVSAGT.logPrio =
Debug
# OPERSAGT.logPrio =
Debug
# mmSAgt.logPrio =
Debug
# mmdb.logPrio =
Debug
# Specialized "autonomous" flags for debug, fault isolation
# engine.autonomous =
true
# cfgM.autonomous =
true
Talk2.autonomous
=
false
#-------------# procM
#-------------procM.minCheckHealthInterval =
procM.minCheckHealthTimeout =
procM.minKillGracePeriod =
10
20
5
# smallest check health interval
# smallest check health timeout
# smallest kill grace period
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-16
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
procM.almDwellInterval =
procM.procHealthDfltAlmCat =
procM.servicesDir =
procM.servFmt
=
procM.recovDbFile =
procM.logDBFile
=
procM.runAsDaemon =
15
# seconds to wait before clearing alarm
pmDefault # default alarm category for PM
../var
# location of PM temporary FIFOs
PM_%d_%d_input # format of PM temporary FIFOs
../var/procMRecovery # PM recovery info
../var/procMLogTable # log info for recovery only
true
#------------# cfgM
#------------cfgM.recovDbFile
=
../var/cfgMRecovery
# CfgM recovery info
#------------# Engine
#------------engine.SysPropagateChanAvail = false
# MIGRATED
engine.SysGeneratedCode = true
# MIGRATED
engine.SysGRSTimerInterval = 0
# MIGRATED
engine.SysGRSBlockSize = 0
# MIGRATED
engine.SysSGCPRetryCount = 3
# max number of SGCP retry messages after failure
engine.SysSGCPRetryTimerInterval = 1000
# interval between retransmission (msec)
engine.SysCLIval = false
engine.SysToneDetect = false
engine.SysNumTrans = false
engine.SysMinOverlap = 0
engine.SysMaxOverlap = 28
engine.SysGSMTimerInterval = 30000
# GSM to be sent (milliseconds)
engine.LCMMdlFile = ../lib/lcm
# LSI call model
engine.CCMdlFile = ../lib/cc
# call context
engine.mdoDir = ../lib/
# where .mdo files live
engine.VersionTimeoutValue = 10000
# Interval for version messages (msec)
engine.MDLANumberScreening = 0
# MIGRATED
engine.SysMdlMemoryReduction = 1
# MIGRATED
*.RedirectingATree = 0
*.ClearingLocation = 0
# MIGRATED
*.DefaultLocation = 0
# MIGRATED
*.detailedCallEventCapture = 1
# MIGRATED
*.SelectTermCustGrpId = 0
# 1= Select Terminating SigPath CustGrpId if Originating
SigPath CustGrpId is 0000.
# 0= Always select Originating SigPath CustGrpId
#The following two lines are call based memory allocator settings.
#set these to 0 to disable call-based memory allocator
#This setting is memory efficient, but performance suffers.
#set these to 110000 for maximum performance. Memory usage increases.
engine.CALL_MEM_BLOCK_SIZE = 0
# MIGRATED
engine.CALL_MEM_CHUNK_SIZE = 0
# MIGRATED
# engine.SysTraceLevel = 3
*.LongCallTime = 21600000
def)
# used to configure OnGoingCallTime in ms (6hrs
engine.CDRencodingFormat = ItuCDB
# MIGRATED
engine.CDRtimeStamp = M
# MIGRATED
engine.CDRmessageTypes = "1010,1020,1030,1040,1050,1060,1070"
engine.VersionTimeoutValue = 10000
engine.StartUpAuditEnabled = false
# MIGRATED
# MIGRATED
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-17
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
#---------------------# CDR dumper (cdrDmpr)
#---------------------cdrDmpr.openCDR
= true
cdrDmpr.seqFile
= ../var/.cdr.seq
#-----------------------------------# Alarms/Measurements dumper (amDmpr)
#-----------------------------------#------------# ioChanMgr
#------------# Internal debug - only use this for low-level IOS debug
# This is bitmapped hex value:
#
1 - Managed Object tracing
#
2 - Simulation of streams devices from /dev to ../dev for
#
unit testing.
ioChanMgr.trace =
0x0
# These timers are in millisecs
# NOTE: alarms are sent autonomously as they occur, alarmTimer is outdated
# and should be set to zero
ioChanMgr.alarmTimer =
0
ioChanMgr.statTimer =
30000
#Channel manager parameters for IPC flow control.
# evtTimer(msec.) - Frequency at which the queue is scanned for Msgs.
# hbTimer(msec.) - Heart-beat timer, Not yet implemented.
# statDiscardThreshold - Size of Control Queue that triggers discarding
#
all the queued stat events.
# sendThreshold - Max. Number of Events from the Queue sent at a time.
ioChanMgr.evtTimer =
100
ioChanMgr.hbTimer =
1000
ioChanMgr.statDiscardThreshold =
40
ioChanMgr.sendThreshold =
10
#Channel manager parameters for SCC switchover on MGX
# Both sessionPauseTimer and resumeAckTimer are in seconds.
ioChanMgr.sessionPauseTimer = 8
# MIGRATED
ioChanMgr.resumeAckTimer = 1
# MIGRATED
#----------# ioChanCtl
#----------ioChanCtl.DPNSSTestFrames = true
ioChanCtl.xgcpMultiThread = true
ioChanCtl.ituIsNewZealand = false
properties
# enable threading for the IP receive loop in MGCP
# for New Zealand MTP3 set appropriate ITU
#----------# measM
#----------#
# Currently we assume 8000 XEMeas objects fit into 8 Mb of shared memory.
#
measM.sm_seg_size = 32
# size of shared memory in MB (default is 32)
measM.loadBalanceFactor = 20 # num of measmgr distribution points every 5 minutes
measM.port = default
# port to sync dynamic meas thresholds
#---------# almM
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-18
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
#---------# almM.runAsDaemon =
false
#------------# MML - since this is started and stopped by user, it
#
has the following unique requirements for logging.
#
- to alter logging levels, the logPrio parameter
#
must be changed here, then the MML process
#
started to pick up the change. The set-log
#
command does not affect any MML processes
#
#
- Currently MML must ALWAYS have autonomous=true
#------------MML.logPrio = Info
log
MML.logFileNamePrefix = mml
# causes Info and above messages to be written to the
# causes MML messages to be diverted to mml.log
MML.autonomous = true
MML.runAsDaemon = false
MML.timeout = 10000
# MIGRATED
#
resolution)
#
# individual timeout values for MML commands:
# format is: MML.<verb> = time
# (verb all lowercase)
MML.set-sc-state = 8500
MML.chg-cfg = 10000
MML.startPM = /etc/init.d/CiscoMGC start
MML.stopPM = /etc/init.d/CiscoMGC stop
MML.vld-cic = 25000
MML.snd = 600000
(note: current XE supports 1-second
#---------# XE
#---------#----------# foverd
#----------# NOTE: addresses below must be configured for the target system
#
- connTypes can be "socket", "serial", or "fifo"
# connection 1 parameters
foverd.conn1Type = socket
# MIGRATED
# connection 2 parameters
foverd.conn2Type = socket
# MIGRATED
# connection 3 parameters
foverd.conn3Type =
foverd.conn3Addr =
serial
/dev/null
foverd.heartbeatInterval = 1000
foverd.ackTimeout =
1000
foverd.abswitchTestInterval = 30000
foverd.graceShutTimeout = 6000
foverd.forceShutTimeout = 1000
foverd.commRetryInterval = 30000
foverd.statusRptInterval = 600000
foverd.peerCommTimeout =
3000
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-19
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.2(2) XECfgParm.dat Files
foverd.delayTimeout =
1000
foverd.transitionTimeout = 10000
foverd.abswitchPort = /dev/null
# MIGRATED
foverd.peerReestablishTimeout = 50000
# ----------------------------------------------------#foverd.runAsDaemon =
false
# ----------------------------------------------------#foverd.logPrio
=
Info
#----------------# Network Element
#----------------product.vendor = "Cisco Systems, Inc."
product.version = "9.2(1.6)"
product.time = "....."
#---------------------------------# POM - Provisioning Object Manager
#---------------------------------pom.port
= default
# use port 4001 when set to default
#---------------------------------# Replicator
#---------------------------------replicator.portDataChannelSend = 12968
# MIGRATED
replicator.portDataChannelRecv = 12970
# MIGRATED
replicator.portCommChannelSend = 12972
# MIGRATED
replicator.portCommChannelRecv = 12974
# MIGRATED
replicator.reconnectInterval = 15
replicator.numberReadThreads = 1
# optional thread (0=no threads,1=one thread)
#----------------# Audit properties
#----------------engine.AuditTimerInterval = 1000
# MIGRATED
engine.MaxAuditCics = 32
# MIGRATED
#---------------------------------# Disk Monitor Parameters
#---------------------------------diskmonitor.Limit = 7
# MIGRATED
diskmonitor.Threshold = 80
# MIGRATED
diskmonitor.SoftLimit = false
# MIGRATED
diskmonitor.CdrRmFinished = 1
# MIGRATED
diskmonitor.OptFileSys =
# list of optional filesystems to monitor (no trimming)
diskmonitor.CoreRmDays = 1
# MIGRATED
diskmonitor.CfgRmDirs = 64
# MIGRATED
#-------------------------------# call verification utility Parameters
#-------------------------------callver.SaveArea = ../etc/cust_specific/toolkit
#-----------------------------------------------------------------------------# End of XE Configuration Parameter File
#------------------------------------------------------------------------------
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-20
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
The following sample Cisco MGC 9.1(5) XECfgParm.dat files are located in the /opt/CiscoMGC/etc
directory.
# File: XECfgParm.dat
#
# Purpose:
#
# This file contains configuration parameters that may be accessed by
# XE application programs at run-time.
#
# All lines beginning with a '#' are comments and WILL NOT BE READ BY
# PROGRAMS. Thus application overrides of the default parameter values
# can be easily added and removed by removing/added a '#'.
#
#-----------------------------------------------------------------------------# Default parameter values have a facility name of "*" and
# will be used if no match is found on a specific facility name
#-----------------------------------------------------------------------------# Specific Facility names are as follows:
#
# logger
- Log Server
# foverd
- Failover Daemon
# MML
- MML
# procM
- Process Manager
# cdrDmpr
- CDR Dumper
# cfgM
- Configuration Manager
# engine
- call processing engine
# ioChanMgr - I/O Channel Managers
# pom
- Provisioning Object Manager
# measM
- Measurement Manager
# OPERSAGT - Operational SNMP Agent
# PROVSAGT - Provisioning SNMP Agent
# mmSAgt
- Measurement Manager SNMP Agent
# almM
- Alarm Manager
# replicator- Replicator
# mmdb
- TimesTen Main Memory Data Base Process
# amDmpr
- Alarm / Measurement Dumper
# ioChanCtl - controls all channel controllers
#
#----Special Paremeter Section---# callver
- call verification utility
# diskmonitor - disk monitor shell script
# XE
- Execution Environment
#
#-----------------------------------------------------------------------------#---------------- MGC Environment Configuration Tool Usage -------------------#
REQUIRED STARTUP PARAMETERS
#
DO NOT MOVE THESE PARAMETERS BEYOND THIS BOX
*.platformId =
1
*.transpathId =
01
# Transpath Id for ASN
*.MGC_CDR_NODE_ID =
MGC-CDR-NODE-STRING
# System Id for CDR
*.desiredPlatformState =
master
*.SyscheckpointEnabled =
true
*.SysConnectDataAccess =
false
# true, establish conn. to Data Access Subsystem
*.GWClearChannelAlgorithm =
null
# clear channel algorithm
*.ipAddrLocalA =
*.ipAddrLocalB =
*.ipAddrPeerA =
*.ipAddrPeerB =
10.0.0.21
# Should be same as *.IP_Addr1
10.128.0.32
10.0.0.19
# Failover peer's address
10.128.0.33
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-21
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
*.IP_Addr1
*.IP_Addr2
*.IP_Addr3
*.IP_Addr4
=
=
=
=
10.82.70.204
10.0.0.21
10.128.0.32
0.0.0.0
# Address of interface on motherboard
*.stPort =
7000
engine.SysVirtualSwitch =
1
# 0=Nailed-Up, 1=Switched-MGC, 2=Switched-JCS
pom.dataSync =
true # don't synch slave data with master
*.numberOfThreads = 2
#-----------------# CVT Parameters
#-----------------#*.OwnClli = TTTT-SS-BB-XXX
#*.OwnClli = 1-22-33-444
#
REQUIRED STARTUP PARAMETERS
#
DO NOT MOVE THESE PARAMETERS BEYOND THIS BOX
#---------------- MGC Environment Configuration Tool Usage -------------------*.disableMeas =false
*.sm_meas_baseaddr = 3400
# T ==> Don't accumulate meas in shared mem
# shared memory based address
*.tempDir =
/tmp
# temporary directory
*.dataDir =
../var # volatile data directory
*.homeDirRoot =
/opt/CiscoMGC
*.logDirectory =
../var/log
# NEW log directory
*.logFileNamePrefix =
platform
# NEW log prefix
*.logPrio
=
Error
*.logMsgDrop =
true
*.eventTrace =
false
*.debugLevel =
high
*.tablesFile =
../etc/tables.dat # tables that can be loaded
*.autonomous
=
false
*.runAsDaemon =
true
*.ownTranspathId =
01
*.peerTranspathId =
02
*.chkPtPort =
2001
*.maxNumLinks =
32
*.maxNumDChansPerIOCC =
504
*.maxNumMGCPLinks =
1000
*.maxNumSIPLinks =
4
*.maxTrueOPCs =
6
# max true OPCs per MGC
*.maxCapOPCsPerTrueOPC =8 # max cap OPCs per true OPC
*.dataSourceName =
howdydb
*.dataCommitTime =
10
# in millisecs
*.OverdecadicDigitsSupported =
false
# keep it here for migration purpose only
*.DataBaseAccessError =
0
# 0 = Continue, 1 = Reject call
*.VirtualMemTimerInterval = 2000 # sampling frequency of virtual memory
*.MemAddressTimerInterval =1500 # sampling frequency of memory address space of processes
*.CallRateTimerInterval = 1000 # sampling frequency of the call rate computations
*.CPUTimerInterval = 1000 # sampling frequency of CPU utilization
*.CallCutoffTimer =0 # call cutoff timer (hours)
#-----------------------------------------------------------------------# Log Server logfile locations
#-----------------------------------------------------------------------# run as daemon
logger.runAsDaemon = false
# daemonAddr is socket port for logger daemon
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-22
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
logger.daemonAddr = ../var/lsd_addr
# NEW logfile rotation size max in Megabytes
logger.fileRotateSize = 100
# NEW logfile rotation interval in minutes (24 hrs default)
logger.fileRotateInterval = 1440
# numThreads can be 0 or 1, if 1 then logger client runs in its
# own thread
logger.numThreads = 0
#------------------------------------------------------------------------# Facility specific parameters
#
The remainder of this file pertains to parameters and parameter overrides
#
for individual facilitites.
#
# LogPrio and autonomous are changed for debug testing only. Otherwise
# everyone should use the defaults above (except MML, see below.)
#------------------------------------------------------------------------#
#
#
#
#
#
#
#
#
#
#
#
#
Specialized logging level for debug, fault isolation
Usage of these debug parameters could cause the system to use up
space more rapidly than normal. If the DISK alarm is activated because
of this activity, certain files in /opt/CiscoMGC/var/spool will be erased.
ioChanCtl.logPrio =
procM.logPrio =
engine.logPrio =
Debug
PROVSAGT.logPrio =
Debug
OPERSAGT.logPrio =
Debug
mmSAgt.logPrio =
Debug
mmdb.logPrio =
Debug
Debug
Debug
# Specialized "autonomous" flags for debug, fault isolation
# engine.autonomous =
true
# cfgM.autonomous =
true
Talk2.autonomous
=
false
#-------------# procM
#-------------procM.minCheckHealthInterval =
procM.minCheckHealthTimeout =
procM.minKillGracePeriod =
procM.almDwellInterval =
procM.procHealthDfltAlmCat =
procM.servicesDir =
procM.servFmt
=
procM.recovDbFile =
procM.logDBFile
=
procM.runAsDaemon =
10
# smallest check health interval
20
# smallest check health timeout
5
# smallest kill grace period
15
# seconds to wait before clearing alarm
pmDefault # default alarm category for PM
../var
# location of PM temporary FIFOs
PM_%d_%d_input # format of PM temporary FIFOs
../var/procMRecovery # PM recovery info
../var/procMLogTable # log info for recovery only
true
#------------# cfgM
#------------cfgM.recovDbFile
=
../var/cfgMRecovery
# CfgM recovery info
#------------# Engine
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-23
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
#------------engine.SysPropagateChanAvail = false
#
engine.SysGeneratedCode = true
#
protocols
engine.SysGRSTimerInterval = 500
engine.SysGRSBlockSize = 1
engine.SysSGCPRetryCount = 3
#
engine.SysSGCPRetryTimerInterval = 1000
engine.SysCLIval = false
engine.SysToneDetect = false
engine.SysNumTrans = false
engine.SysMinOverlap = 0
engine.SysMaxOverlap = 28
engine.LCMMdlFile = ../lib/lcm
#
engine.CCMdlFile = ../lib/cc
#
engine.mdoDir = ../lib/
#
engine.VersionTimeoutValue = 10000
#
engine.MDLANumberScreening = 0
#
auto-blocking of C7 cics and ISDN sigPaths
false=interpreted(.mdo),true=compiled(.so)
max number of SGCP retry messages after failure
# interval between retransmission (msec)
LSI call model
call context
where .mdo files live
Interval for version messages (msec)
use calling party number for a number screening
engine.SysMdlMemoryReduction = 1
# NO optional memory reductions active (1=ALL)
*.ClearingLocation = 0
# 0 = Normal mapping behaviour, LCM will not override
the Clearing Location field in Call Context
*.DefaultLocation = 0
# 0 = Normal protocol defined default value, LCM will
not override the Default Location field in Call Context
*.detailedCallEventCapture = 1
#The following two lines are call based memory allocator settings.
#set these to 0 to disable call-based memory allocator
#This setting is memory efficient, but performance suffers.
#set these to 110000 for maximum performance. Memory usage increases.
engine.CALL_MEM_BLOCK_SIZE = 0
engine.CALL_MEM_CHUNK_SIZE = 0
# engine.SysTraceLevel = 3
*.LongCallTime = 21600000
def)
# used to configure OnGoingCallTime in ms (6hrs
engine.CDRencodingFormat = AnsiCDB
engine.CDRtimeStamp = S
engine.CDRmessageTypes
= "1010,1020,1030,1040,1050,1060,1070"
engine.VersionTimeoutValue = 10000
engine.StartUpAuditEnabled = false
# audit invoked at engine startup?
#---------------------# CDR dumper (cdrDmpr)
#---------------------cdrDmpr.openCDR
= true
cdrDmpr.seqFile
= ../var/.cdr.seq
#-----------------------------------# Alarms/Measurements dumper (amDmpr)
#-----------------------------------#------------# ioChanMgr
#------------# Internal debug - only use this for low-level IOS debug
# This is bitmapped hex value:
#
1 - Managed Object tracing
#
2 - Simulation of streams devices from /dev to ../dev for
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-24
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
#
unit testing.
ioChanMgr.trace =
0x0
# These timers are in millisecs
# NOTE: alarms are sent autonomously as they occur, alarmTimer is outdated
# and should be set to zero
ioChanMgr.alarmTimer =
0
ioChanMgr.statTimer =
30000
#Channel manager parameters for IPC flow control.
# evtTimer(msec.) - Frequency at which the queue is scanned for Msgs.
# hbTimer(msec.) - Heart-beat timer, Not yet implemented.
# statDiscardThreshold - Size of Control Queue that triggers discarding
#
all the queued stat events.
# sendThreshold - Max. Number of Events from the Queue sent at a time.
ioChanMgr.evtTimer =
100
ioChanMgr.hbTimer =
1000
ioChanMgr.statDiscardThreshold =
40
ioChanMgr.sendThreshold =
10
#Channel manager parameters for SCC switchover on MGX
# Both sessionPauseTimer and resumeAckTimer are in seconds.
ioChanMgr.sessionPauseTimer =
8
ioChanMgr.resumeAckTimer =
1
#----------# ioChanCtl
#----------ioChanCtl.DPNSSTestFrames = true
ioChanCtl.xgcpMultiThread = true
ioChanCtl.ituIsNewZealand = false
properties
# enable threading for the IP receive loop in MGCP
# for New Zealand MTP3 set appropriate ITU
#----------# measM
#----------#
# Currently we assume 8000 XEMeas objects fit into 8 Mb of shared memory.
#
measM.sm_seg_size = 32
# size of shared memory in MB (default is 32)
measM.loadBalanceFactor = 20 # num of measmgr distribution points every 5 minutes
measM.port = default
# port to sync dynamic meas thresholds
#---------# almM
#---------# almM.runAsDaemon =
false
#------------# MML - since this is started and stopped by user, it
#
has the following unique requirements for logging.
#
- to alter logging levels, the logPrio parameter
#
must be changed here, then the MML process
#
started to pick up the change. The set-log
#
command does not affect any MML processes
#
#
- Currently MML must ALWAYS have autonomous=true
#------------MML.logPrio = Info
log
MML.logFileNamePrefix = mml
# causes Info and above messages to be written to the
# causes MML messages to be diverted to mml.log
MML.autonomous = true
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-25
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
MML.runAsDaemon = false
MML.timeout=10000
# in milliseconds
#
(note: current XE supports 1-second
resolution)
#
# individual timeout values for MML commands:
# format is: MML.<verb> = time
# (verb all lowercase)
MML.set-sc-state = 8500
MML.chg-cfg = 10000
MML.startPM = /etc/init.d/CiscoMGC start
MML.stopPM = /etc/init.d/CiscoMGC stop
MML.vld-cic = 25000
MML.snd = 600000
#---------# XE
#---------# The next lines about ARU are here only for release 1.1
# heartbeat rate (secs): 5-255, MUST CORRESPOND TO PHYSICAL SETTING ON ARU;
# if not set, 255 will be used
XE.heartBeatRate =
60
# name of the device where ARU expects to read alarm strings from; if not set,
# /dev/tty will be used
# Set this to /dev/null if an ARU is not attached
#
or DRYCONTACT to use the Netra CMS device
XE.ARUWriteDevice =
/dev/null
#systemType: NETRA-FT
#systemType: NETRA
#systemType: SPARC
#systemType: SPARC-ARU
XE.systemType =
means
means
means
means
sheffield NETRA 1800FT
NETRA T1100,T1120
generic box without alrm LED and ARU
generic box with ARU,without alrm LED
SPARC
#----------# foverd
#----------# NOTE: addresses below must be configured for the target system
#
- connTypes can be "socket", "serial", or "fifo"
# connection 1 parameters
foverd.conn1Type = socket
foverd.ipLocalPortA = 1051
foverd.ipPeerPortA = 1052
# connection 2 parameters
foverd.conn2Type = socket
foverd.ipLocalPortB = 1053
foverd.ipPeerPortB = 1054
# connection 3 parameters
foverd.conn3Type =
foverd.conn3Addr =
serial
/dev/null
foverd.heartbeatInterval = 1000
foverd.ackTimeout =
1000
foverd.abswitchTestInterval = 30000
foverd.graceShutTimeout = 6000
foverd.forceShutTimeout = 1000
foverd.commRetryInterval = 30000
foverd.statusRptInterval = 600000
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-26
OL-1150-15
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
foverd.peerCommTimeout =
3000
foverd.delayTimeout =
1000
foverd.transitionTimeout = 10000
foverd.abswitchPort =
/dev/null
foverd.peerReestablishTimeout = 50000
# ----------------------------------------------------#foverd.runAsDaemon =
false
# ----------------------------------------------------#foverd.logPrio
=
Info
#----------------# Network Element
#----------------product.vendor = "Cisco Systems, Inc."
product.version = "9.1(5)"
product.time = "....."
#---------------------------------# POM - Provisioning Object Manager
#---------------------------------pom.port
= default
#---------------------------------# Replicator
#---------------------------------replicator.portDataChannelSend = 2968
replicator.portDataChannelRecv = 2970
replicator.portCommChannelSend = 2972
replicator.portCommChannelRecv = 2974
replicator.reconnectInterval = 15
replicator.numberReadThreads = 1
# use port 4001 when set to default
# optional thread (0=no threads,1=one thread)
#----------------# Audit properties
#----------------engine.AuditTimerInterval = 1000
engine.MaxAuditCics = 32
engine.AuditOverloadLvl = 25
#---------------------------------# Disk Monitor Parameters
#---------------------------------diskmonitor.Limit
= 7
# Minimum number of days to preserve (Trimming only
occurs when threshold is exceeded. There is no maximum number of days to preserve.)
diskmonitor.Threshold = 80
# percentage full threshold
diskmonitor.SoftLimit = false
# set to true to allow override of preserve limit
diskmonitor.CdrRmFinished = 0
# remove "finished" cdrs after X days (0 = immediate)
diskmonitor.OptFileSys =
# list of optional filesystems to monitor (no trimming)
diskmonitor.CoreRmDays = 1 # number of days to keep the core files
diskmonitor.CfgRmDirs = 64
# remove old config directories if more than X exist (0
= disable)
#-------------------------------# call verification utility Parameters
#-------------------------------callver.SaveArea = ../etc/cust_specific/toolkit
#-----------------------------------------------------------------------------# End of XE Configuration Parameter File
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
D-27
Appendix D
Sample Installation Scripts
Sample Configured Cisco MGC 9.1(5) XECfgParm.dat Files
#------------------------------------------------------------------------------
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
D-28
OL-1150-15
A P P E N D I X
E
Sample Uninstall Scripts
This appendix contains sample outputs from the following section, Removing a Previous Software
Version: Sample Output for uninstall.sh, page E-1.
Removing a Previous Software Version: Sample Output for
uninstall.sh
The following is a sample output from the uninstall script.
va-cerulean# cd /cdrom/cdrom0
va-cerulean# ./uninstall.sh
If you answer no to the following question you will lose all new provisioning work.
Note
Answer y to the following question if this uninstallation is for a software upgrade; answer n if
the uninstallation is to fall back or back out to the previous software version.
Is the uninstall being done in order to upgrade to a new version of the
software? [y] [y,n,?,q] y
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Removing /opt/CiscoMGC/etc/migrate/migrate.dat
Removing /opt/CiscoMGC/etc/migrate/migrate_4_5
Removing /opt/CiscoMGC/etc/migrate/migrate_5_6
Removing /opt/CiscoMGC/etc/migrate/migrate_6_7
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0001_7.0002
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0001_7.1
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0002_7.1
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0003_7.1
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0004_7.1
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0005_7.1006
Removing /opt/CiscoMGC/etc/migrate/migrate_7.0_7.0001
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1001_7.1002
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1002_7.1003
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1003_7.1004
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1004_7.1005
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1005_7.1006
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1006_8.0
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1006_8.0.sql
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1_7.1001
Removing /opt/CiscoMGC/etc/migrate/migrate_7.1_7.1001.sql
Removing /opt/CiscoMGC/etc/migrate/migrate_XECfgParm
Removing /opt/CiscoMGC/etc/migrate/migrate_cpp_4_5
Removing /opt/CiscoMGC/etc/migrate/migrate_cpp_5_6
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
E-1
Appendix E
Sample Uninstall Scripts
Removing a Previous Software Version: Sample Output for uninstall.sh
Removing /opt/CiscoMGC/etc/migrate/migrate_cpp_DB
Uninstalling /opt/CiscoMGC/etc/migrate/migrate_scr.tar.gz
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/dependencies.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/propLookUp.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/4.0_to_5.0/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/alarmCats.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/compTypes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/propSet.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/5.0_to_6.0/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/alarmCats.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/compTypes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/dependencies.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/measCats.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/6.0_to_7.0/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.0002/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.0002/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.0002/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.0002/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.1/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.1/compTypes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.1/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.1/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0001_to_7.1/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0002_to_7.1/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0002_to_7.1/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0002_to_7.1/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0002_to_7.1/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0003_to_7.1/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0003_to_7.1/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0003_to_7.1/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0003_to_7.1/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0004_to_7.1/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0004_to_7.1/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0004_to_7.1/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0004_to_7.1/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/dependencies.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/procGroups.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0005_to_7.1006/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/alarmCats.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/compTypes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.0001/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.0_to_7.1/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1001_to_7.1002/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1001_to_7.1002/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1001_to_7.1002/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1002_to_7.1003/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1002_to_7.1003/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1003_to_7.1004/
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
E-2
OL-1150-15
Appendix E
Sample Uninstall Scripts
Removing a Previous Software Version: Sample Output for uninstall.sh
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1003_to_7.1004/dependencies.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1003_to_7.1004/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1003_to_7.1004/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1004_to_7.1005/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1004_to_7.1005/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1004_to_7.1005/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1005_to_7.1006/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1005_to_7.1006/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1006_to_8.0/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1006_to_8.0/properties.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1006_to_8.0/services.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/components.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/dependencies.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/procGroups.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/processes.mod
Removing /opt/CiscoMGC/etc/CONFIG_LIB/7.1_to_7.1001/properties.mod
Uninstalling /opt/CiscoMGC/etc/CONFIG_LIB/migrate_mod.tar.gz
Removal of <CSCOgc001> was successful.
Removal of <CSCOgt002> was successful.
Removal of <CSCOgt001> was successful.
Removal of <CSCOgg010> was successful.
Removal of <CSCOgg009> was successful.
Removal of <CSCOgg008> was successful.
Removal of <CSCOgg007> was successful.
Removal of <CSCOgg006> was successful.
Removal of <CSCOgg005> was successful.
Removal of <CSCOgg004> was successful.
Removal of <CSCOgg003> was successful.
Removal of <CSCOgg002> was successful.
Removal of <CSCOgg001> was successful.
Removal of <CSCOgg000> was successful.
Removal of <CSCOgi009> was successful.
Removal of <CSCOgi008> was successful.
Removal of <CSCOgi007> was successful.
Removal of <CSCOgi006> was successful.
Removal of <CSCOgi005> was successful.
Removal of <CSCOgi004> was successful.
Removal of <CSCOgi003> was successful.
Removal of <CSCOgi002> was successful.
Removal of <CSCOgi001> was successful.
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
E-3
Appendix E
Sample Uninstall Scripts
Removing a Previous Software Version: Sample Output for uninstall.sh
Removal of <CSCOgi000> was successful.
Uninstalling /opt/CMM/tcl/tcl.tar.gz
Uninstalling /opt/CMM/mibs/common/common.tar.gz
Uninstalling /opt/CMM/gif/gif.tar.gz
Uninstalling /opt/CMM/bytecode/tv/tv.tar.gz
Uninstalling /opt/CMM/bytecode/toolbar/toolbar.tar.gz
Uninstalling /opt/CMM/bytecode/log/Viewer.tar.gz
Uninstalling /opt/CMM/bytecode/cmm/cmm.tar.gz
Uninstalling /opt/CMM/bytecode/cdr/cdr.tar.gz
Uninstalling /opt/CMM/bytecode/am/am.tar.gz
Uninstalling /opt/CMM/Packages/Packages.tar.gz
Removal of <CSCOga004> was successful.
kill: 544: no such process
Removal of <CSCOga003> was successful.
Sun Microsystems Inc.
SunOS 5.6
Generic August 1997
You have new mail.
Exporting database contents for DSN=howdydb into /opt/CiscoMGC/etc/export.ttdb
The Backup process is being initiated for the datastore howdydb
Files for /opt/TimesTen32/datastore/howdydb are being backed up onto standard output
Backup Complete
Successful backup, uninstall continuing
The 32-bit daemon has stopped successfully.
Modifying /etc/syslog.conf
Removal of <CSCOga002> was successful.
Removal of <CSCOga001> was successful.
Removal of <CSCOga000> was successful.
Modifying /etc/init.d/inetinit
Removal of <CSCOgu000> was successful.
Uninstallation log can be found in /tmp/uninstall.log
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
E-4
OL-1150-15
INDEX
Symbols
B
.odbc.ini file
/etc/init.d
BAMS
5-58
configuring data dumper
5-3
/opt/CiscoMGC
black list
5-3
/opt/CiscoMGC/etc
/opt/CiscoMGC/etc/active_link
booting the system
5-3
/opt/CiscoMGC/etc/CONFIG_LIB
/opt/CiscoMGC/etc/cust_specific
/opt/CiscoMGC/etc/prov_link
5-3
/opt/CiscoMGC/man
5-3
/opt/CiscoMGC/var
5-3
C
5-36, A-26
call screening database
enabling
5-4
5-4
5-57
See call detail block
/opt/CiscoMGC/var/trace
5-4
/opt/CiscoMGC directory
5-1
CDR
See call detail record file
CDRs
5-4
configuring data dumper
5-4
5-66
Cisco MGC software
removing
9-3
restarting
5-46, 5-47, 5-48
uninstalling
adding
9-3
upgrading Release 7
user, full MML privileges
5-12
5-57
5-11
5-65
9-5
5-38
command
boot
5-12
configuring data dumper
clearing location field
5-11
user, minimal MML privileges
A-number screening
5-65
configuring data dumper to support BAMS
5-4
A
alarms
5-57
CDB
5-4
alarm management
5-36
5-35
initializing
/opt/CiscoMGC/var/spool
/opt/Toolkit
5-3
call detail block
5-3
/opt/CiscoMGC/var/log
/opt/TimesTen4.1
3-5, 7-5
call detail record file, configuring
/opt/CiscoMGC/local
/opt/sun_install
5-3
5-3
/opt/CiscoMGC/snmp
5-57
5-3
/opt/CiscoMGC/etc/CONFIG_LIB/new
/opt/CiscoMGC/lib
5-57
B-number screening
5-3
5-66
3-5, 7-5
pkgrm
5-63
reboot
3-5, 7-5
restart Cisco MGC software
5-46, 5-47, 5-48
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
IN-1
Index
configuring
G
Cisco MGC
basic system information
call detail record file
failover
howdydb
5-27
5-31
provisioning object manager
5-58
I
5-43
5-10
LAN switch
initializing
10-1
call screening database
Simple Network Management Protocol
users
H
5-41
IP addresses
groups
5-35
5-32
execution environment
5-10
5-36
enable call screening database
engine parameters
groups, configuring
5-29
5-12
5-57
install.sh
5-10
command
7-4
sample output
D-1
IP address
D
specifying, Cisco MGC
5-31
data
replication
5-58
L
data dumper
configuring
5-65
LAN switch
configuring to support BAMS
default location field
5-66
configuring
5-38
overview
document
10-1
10-1
system components
conventions
10-1
i-xiii
dual configuration, data replication
5-58
M
management information base
E
man machine language
engine parameters, configuring
execution environment
configuring
parameters
5-32
5-10
measurements
configuring data dumper
5-27
media gateway
5-29, A-1
5-12
5-65
i-xiii, 10-1
MGC software directory structure
5-3
MIB
See management information base
F
MML
failover, configuring
5-41
See man machine language
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
IN-2
OL-1150-15
Index
N
T
number analysis
traps
5-57
5-12
P
U
parameters
uninstalling Cisco MGC software
XECfgParm.dat
upgrading
A-1
performance profile script
pkgrm command
9-3
Cisco MGC software
7-5
9-5
user
5-63
POM
adding, full MML privleges
See provisioning object manager
provisioning object manager
5-11
adding, minimal MML privleges
users, configuring
5-43
R
5-11
5-10
W
rebooting the system
white list
3-5, 7-5
removing a package
5-57
5-63
removing Cisco MGC software
9-3
restarting Cisco MGC software
5-46, 5-47, 5-48
X
XECfgParm.dat
5-27
configuring basic system information
S
configuring call detail record file
sample configuration
configuring engine parameters
Cisco Catalyst 5500 A
configuring failover
C-1
Cisco Catalyst 5500 A RSM
Cisco Catalyst 5500 B
C-15
D-1, D-14, D-21
Simple Network Management Protocol
configuring
5-36
5-32
5-41
enabling call screening database
5-35
initializing provisioning object manager
C-8
Cisco Catalyst 5500 B RSM
XECfgParm.dat file
C-7
5-29
parameters
5-43
A-1
sample configured file
specifying IP address
D-1, D-14, D-21
5-31
5-12
SNMP
See Simple Network Management Protocol
Solaris 8, required Software Media
switch, configuring
1-2
10-1
system
information, configuring
5-29
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
OL-1150-15
IN-3
Index
Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
IN-4
OL-1150-15