Cisco Systems 10200 Moving Core Files

3-29

Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.x

OL-16000-07

Chapter 3 Monitoring and Backing Up the BTS

Moving Core Files

Adding Static Routes

To add static routes to all Cisco BTS 10200 systems, perform the following steps:

Step 1 From the shell or window of the primary call agent, change directory to /opt/utils.

cd /opt/utils

Step 2 Edit S96StaticRoutes using an editor.

Step 3 Add the subnet of NTP server, DNS server, external archive server and any other machine to the file,

which user wants to have access to Cisco BTS 10200 system in the following format:

route add -net <destination network> <network gateway>

Note All NTP, DNS traffic, traffic to external archive server, and traffic from other machine to Cisco BTS

10200 system (eg. login), should all go through management networks. (i.e. network gateway in

management network). This is particularly important in CA system because CA has both management

and signaling network. If user does not specify explicitly in this file, those traffic will be directed to

signaling network, because signaling network is the default one in CA/FS.

Step 4 Make sure there is a soft link pointing from /etc/rc3.d/S96StaticRoutes to /opt/utils/S96StaticRoutes.

ls -l /etc/rc3.d/S96StaticRoutes

Step 5 After editing, close the file, and run S96StaticRoutes.

/etc/rc3.d/S96StaticRoutes

Step 6 Repeat Step 1 to Step 5 on the secondary CA.

Step 7 Verify the connectivity by pinging the DNS server, NTP server, external archive server, or any machine

that user just added in that file.

LAF Alarm Information

Refer to the following link to see the LAF alarm information.

Moving Core Files

BTS creates and stores core files in the bin directory for the binary executable that generated the core.

Core files are large (2–4 GB) and eventually cause a disk full condition resulting in a switchover. When

a BTS platform system generates a core file, the BTS creates an alarm. The Core File Present—Audit 25

(major) alarm indicates a core is present in the BTS. The primary cause of this alarm is that a network

element process crashed.

Document Name Link to the Document

Cisco BTS 10200 Troubleshooting Guide http://www.cisco.com/en/US/docs/voice_ip_comm/bts/

6.0/troubleshooting/guide/07tg01.html#wp1938289

Contents

Main Page CONTENTS Page Page Page Page Page Preface Organization Document Change History Obtaining Documentation and Submitting a Service Request Page Page Starting and Shutting Down the BTS Meeting Power Requirements Starting BTS Hardware Shutting Down BTS Hardware Starting BTS Software Page Page Managing BTS Users and Commands Using EMS Logging into the EMS Using CLI Managing Users Page Page Managing Commands Adapter and User Security Solaris OS Security and BTShard Package Page Page Operator Interface Vulnerabilities in H.323 Message Processing Authentication, Authorization and Accounting Support Pluggable Authentication Module Support User Security Account Management Sun Microsystems Configurations Page Solaris OS Patches Trace Normal Forms (TNF) Support XML Libraries Device GLM Patch Security CE Patch Security Bad_Trap Patch Java SDK Patches Page Monitoring and Backing Up the BTS Detecting and Preventing BTS Congestion Monitoring BTS Hardware Checking BTS System Health Using BTS System-Health Reports Checking BTS System Time Checking the OS Log of Each Host Machine Checking Disk Mirroring on Each Host Machine CA/FS Side A CA/FS Side B EMS Side A EMS Side B Auditing Databases and Tables Exporting Provisioned Data 3-9 Limitations Creating Numbering Resource Utilization/Forecast (NRUF) Reports Creating Reports for Nonrural Primary and Intermediate Carriers Creating Reports for Rural Primary and Intermediate Carriers Page Page Backing Up the Software Image Full Database Auditing Checking Shared Memory From CA/FS Side A From CA/FS Side B Backing Up the Full BTS Backing Up the CA/FS Backing up the EMS/BDMS Backing up the EMS Database Using FTP to Setup File Transfer Using SFTP to Setup File Transfer Page Archiving Your Database Examining Heap Usage Checking the DNS Server Log Archive Facility (LAF) Secure Transfer of Files Other Capabilities Provisioning LAF Example 1 Example 2 Example 3 Setup Non-Interactive SSH Login to External Archive Server Adding Static Routes LAF Alarm Information Moving Core Files Page Operating the BTS Managing Subscribers Page Page Page Viewing Calls Using Status and Control Commands Page Using Show and Change Commmands Using ERAC Commands Page Page Managing Transactions Scheduling Commands Limitations Page Managing External Resources Viewing BTS System-Wide Status Page Managing Trunk Groups and Trunks Page Page Page Page Page Page Page Page Managing Subscriber Terminations Page Page Page Managing Gateways Page Managing Other External Resources Page Learning External Resource Dependencies Page Page Page 5-24 Source Token 5-25 5-26 Figure 5-3 ISDN Administrative and Operational Maintenance States for a Trunking Gateway 5-27 GigE Support Prerequisites Provisioning the GigE Interface Page Page Using BTS Measurements Using Measurements Learning the Measurement Types ISDN Measurements Page Page Call Processing Measurements Page Page Page Page Page Page MGCP Adapter Measurements DQoS Measurements SIP Measurements Page Page Service Interaction Manager Measurements POTS Local FS Measurements Page Page Page Page Page POTS Application Server Measurements POTS Miscellaneous FS Measurements Page POTS Class of Service FS Measurements POTS Screen List Editing FS Measurements POTS Customer Originated Trace FS Measurements POTS Automatic Callback, Recall, and Call Return Measurements Page POTS Limited Call Duration (Prepaid/Postpaid) with RADIUS Interface to AAA Measurements POTS Call Forwarding Combination Measurements AIN Services FS Measurements Page SCCP Protocol Measurements Page TCAP Protocol Measurements Page Page Page SUA Measurements Page M3UA Protocol Measurements Page SCTP Measurements Page Page IUA Measurements Page ISUP MeasurementsI Page Page Page 6-50 6-51 ISUP (ANSI) Measurements Page Page ISUP (France) Measurements ISUP (Poland) Measurements ISUP (ITU-China) Measurements Page Page ISUP (ITU-Mexico) Measurements Page ISUP (ITU-HongKong) Measurements Page Audit Measurements SIP Interface Adapter Measurements Page Call Detail Block Measurements Page Event Messaging Measurements Dynamic QoS Measurements PCMM Measurements SNMP Protocol Measurements Trunk Group Usage Measurements Page Page Announcement Measurements H.323 Protocol Measurements Page Page Page Call Tools Measurements AIN Tools Measurements PCT Tools Measurements CPU Usage Measurements Memory Usage Measurements Disk Usage Measurements Network I/O Usage Measurements Page System Load Usage Measurements Disk I/O Usage Measurements ENUM Measurements Diameter Message Counters Single Number Reach Counters Using the BTS SNMP Agent Managing User Access to the SNMP Agent Viewing SNMP Trap Reports Page Viewing and Managing BTS Components Page Querying the SNMP Agent Enabling NMS to Query/Poll Solaris SNMP Agent Page Page APPENDIX A Feature Tones Tones per Feature Page Page request when Page Tone Frequencies and Cadences Page Page APPENDIX B FIM/XML Understanding the Configurable FIM/XML Feature Advantages of the FIM/XML Tool Tool Requirements Writing an External FIM/XML File Defining Features Elements in the External FIM/XML File Define Element Precedence-Exception Element Inhibit Others Element Inhibit Me Element Response Profile Element Error Operation Installing the FIM/XML File Using the Offline FIM/XML Tool Page FIM/XML File and Shared iFC File Features Defined in FIM/XML and Shared iFC Provisioning iFC Defining a New feature as the Originating Feature Defining a VSC Defining the SIP Trigger Profile Feature Configuration Feature Restrictions and Limitations