Table Of Contents
Cisco BTS 10200 Softswitch Cabling and IRDP Procedures
for Medium Hardware Platform AXmp Option
The medium hardware platform AXmp/AXi option was used with optional dedicated SS7 cables.
In Release 4.1, SS7 signaling is sent via SIGTRAN to an Internet transfer point (ITP), therefore, dedicated SS7 cables are not attached to the Cisco BTS 10200 Softswitch. These cables have been deleted from this document.
In Release 4.1, four AXmp units are used (instead of two AXmp and two AXi).
06/07/2004—Added section "Set Node Addresses On the Host Machines".
This feature module is intended for use by service provider engineering and field personnel who are responsible for designing, installing, configuring, and maintaining networks that use the Cisco BTS 10200 Softswitch. The procedure in this feature module describes how to cable the medium hardware platform systems based on the Continuous Computing AXmp servers. This document is in addition to other Cisco BTS 10200 Softswitch documents that describe how to install and operate the system. Contact your Cisco account team for the documentation applicable to your specific system.
Scope and Purpose
This procedure is applicable to Cisco BTS 10200 Softswitch systems that are installed on Continuous Computing host machines, and using 2 Ethernet interfaces on each Call Agent (CA) host, and 2 Ethernet interfaces on each Element Management System (EMS) host.
Note If you are not sure about the number of interfaces to use on your system, or if you are using host machines that are not Continuous Computing-based, contact your Cisco account team for clarification.
This procedure is not applicable to Cisco BTS 10200 Softswitch systems that are already in service.
Caution Do not use this procedure to change the cabling of an in-service Cisco BTS 10200 Softswitch, because that will cause interruption of service. It is not necessary to change the cabling of in-service systems to match this document.
An example of equipment mounting for the Cisco BTS 10200 Softswitch is shown in Figure 1.
Figure 1 Equipment Mounting Configuration (Example)
The purpose of this procedure is to explain how to:
•Cable a new Cisco BTS 10200 Softswitch system
•Enable Internet Control Protocol (ICMP) Router Discovery Protocol (IRDP) functionality on the Cisco BTS 10200 Softswitch and on the Cisco routers adjacent to the Cisco BTS 10200 Softswitch
Caution Do not use this procedure to change the cabling of an in-service Cisco BTS 10200 Softswitch, because that will cause interruption of service. It you need to change the cabling of in-service system, you must first contact your network administrator or your Cisco account team for a procedure.
Before You Start
Before you start cabling the system, perform the following verifications.
1. Verify that the hosts are already mounted in the rack according to manufacturer instructions, and labeled appropriately. Your system should have the following hardware units:
–EMS Side A
–EMS Side B
–CA Side A
–CA Side B
–Cisco 2924M Ethernet Switch A
–Cisco 2924M Ethernet Switch B
–Power distribution unit (DC systems)
2. Ask your supervisor or an authorized power installer to verify that appropriate power feeds are available, as defined in the site survey documentation for your system. The electrical power for your system must come from two separate (redundant) sources, so that a single point of failure does not cause a complete system outage.
Figure 2 shows the physical interfaces and network connections.
Figure 2 Network Diagram
Acronyms and symbols used in Figure 2:
EMS/BDMS = Element Management System/Bulk Data Management System
CA/FS = Call Agent/Feature Server
EMSA = EMS/BDMS Side A; EMSB = EMS/BDMS Side B
CAA = CA/FS Side A; CAB = CA/FS Side B
OMS Hub = communication interfaces between EMS/BDMS and CA/FS over OMS Hub
VoIP = Voice over IP signaling
* = Physical IP address
** = Logical IP address
Notes for Figure 2:
1. For the AXmp host machines, NET 0 represents the ETH0 port, and NET 1 represents the QFE0 port.
2. The IP addresses shown in the figure are for illustration purposes only. IP address examples that begin with 10.89 indicate externally viewable addresses, and those beginning with 10.10 indicate internal nonroutable addresses. The actual IP address data for each Cisco BTS 10200 Softswitch is in the Network Information Data Sheet that was supplied with your specific system.
3. "To external NEs" refers to any of the following links in the service provider network:
•Uplinks for external access to hosts, used for management services (via SSH, SFTP, and so forth) and outbound billing data (via FTP)
•Uplinks for external communications, used for connection to external NEs and DNS services via IRDP-enabled network
Note NE = Network element
SSH = Secure shell
SFTP = Secure file transfer protocol (FTP)
DNS = Domain name server
IRDP = Internet control message protocol (ICMP) router discovery protocol
4. To support full system redundancy, it is necessary to connect the two external uplinks to separate routers as shown in Figure 2. Furthermore, the routers must be connected to separate networks with diverse routing paths to the applicable external NEs and services (such as OSS, DNS, media gateways, and announcement servers).
Caution If each of the external uplinks is not connected as described in Note #3, a single point of failure could cause a traffic interruption.
5. To ensure redundancy of the DNS lookup function in the event of a network outage, it is strongly recommended to have two DNS servers reachable via separate networks with diverse routing paths.
Caution If both DNS servers become unreachable, a traffic interruption will occur.
Labeling the Cables
Make sure that you have all the cables labeled before you begin. Label the cables according to the procedure in Appendix A: Cable Labeling.
Connect Ethernet Cables To EMS and CA Units
Follow these steps to connect the Ethernet cables. Refer to Figure 1 to identify the specific units in the rack.
Step 1 Obtain the 4 Ethernet cables needed for connections between the rear panel of the Element Management Systems (EMS A and EMS B) and the two Cisco 2924M Ethernet Switches (Hub A and Hub B). These cables are listed in Table 1 in Appendix B: Cable List.
Figure 3 shows the rear view of the AXmp host machine.
Note Figure 3 is not to scale.
Figure 3 Partial Rear View of the AXmp Unit Showing Ethernet Ports
Step 3 Obtain the 4 Ethernet cables needed for connections between the rear panel of the Call Agents (CA A and CA B) and the two Cisco 2924M Ethernet Switches (Hub A and Hub B). These cables are listed in Table 1 in Appendix B: Cable List.
See Figure 3 for a rear view of the AXmp host machine.
Connect CONSOLE Ethernet Cables to Alarm Panel
Connect the two CONSOLE Ethernet cables from the Alarm Panel to the Cisco 2924M Ethernet Switches as described in this section.
Note These two CONSOLE cables are specially designed for the CONSOLE connections. Make sure that you are using the correct cables.
Note One end of the CONSOLE cable is labeled "switch" and the other is labeled "net CCN". The "switch" end must connect to the Cisco 2924M Ethernet Switch (Hub) and the "net CCN" end must connect to the Alarm Panel.
Step 1 Refer to Figure 1 to identify which Cisco 2924M Ethernet Switch (Hub) is designated Ethernet Switch A and which is Ethernet Switch B.
Step 2 Connect the "net CCN" end of a CONSOLE cable to port SER 1 on the Alarm Panel, and the "switch" end to the CONSOLE port on the rear panel of Ethernet switch (Hub) A.
Step 3 Connect the "net CCN" end of a CONSOLE cable to port SER 2 on the Alarm Panel, and the "switch" end to the CONSOLE port on the rear panel of Ethernet switch (Hub) B.
The rear view of the alarm panel is shown in Figure 4. (The drawing is not to scale.)
Figure 4 Rear View of Alarm Panel
Connect CCPUnet Cables and Terminating Resistors
Follow these steps to connect the intershelf signaling (CCPUnet) cables and terminating resistors:
Step 1 Obtain the eight CCPUnet cables (four for CCPU A and four for CCPU B).
Step 2 Connect the CCPUnet cables between the machines as listed in Table 1. Make sure that you connect cables labeled CCPU A to the CCPU A ports, and cables labeled CCPU B to the CCPU B ports.
Step 3 Connect the two terminating resistors (part # CCPU 012 02150-02602 REV 00) to the Alarm Panel (Figure 4) as follows: Connect one resistor to CCPUNet HUB A port 5, and the other resistor to CCPUNet HUB B port 5.
Set Node Addresses On the Host Machines
The following procedure explains how to set or change the node addresses on the host machines. This procedure can be used on systems that are new, and on systems that are in service.
When multiple host machines are on a common CCPU Net, you must give each machine a unique node address.
Note If two or more machines on a common CCPU Net have identical node addresses, unpredictable operation can occur.
Step 1 Action: Disconnect CCPU Net A and CCPU Net B cables from the rear of one of the host machines.
Result: The red alarm light on the front of the unit will become illuminated. This is expected.
Why: The host machines communicate with each other through the CCPU Net cables. Disconnecting these cables will isolate each unit and prevent non-unique addressed units from interacting.
Step 2 Action: Attach to console port. Connect to CCN CLI. You should see the following promptnodename(XX) ccncli>
where XX is the current node address in hexadecimal and nodename is the current name of that node.
Note If you don't see this prompt, depress the following keys `control+]' followed by `.' then press the enter key two times. This will take you to the CCN CLI. If not, check your serial connection. You should be using a straight cable, connecting at 38,400bps, 8,N,1.
Result: The prompt will report the current node setting.
Step 3 Action: From the CCN CLI prompt, type the following command `initmode on'.
Result: you will receive an echo of `initmode on'.
Why: This tells the CCN (control Computer) what state the system should be in when it is powered-up or reset.
Step 4 Action: Set the jumpers on the unit.
Background: The host machines have jumpers on the receptacle that are used to set the node address of the server. This node address is used to control the node alarming and out-of-band control commands that go from node to node.
Caution The host machines should never be configured with duplicate addresses. If duplicate addresses are used, commands designated for one system may be received by more than one system, and spurious operation may result. For example, if two nodes have duplicate addresses, turning one node off may cause the second node to turn off.
Jumper Settings: The jumpers are on the rear of the receptacle that remains attached to the cabinet even when the core is removed. These jumpers are shown in Figure 5.
Figure 5 View of Jumpers and Bit Locations
Using shunt jumpers, systems may be configured to different addresses. Figure 6 shows several sample configurations.
Figure 6 Sample Jumper Configurations
The units need to be configured as follows:
Primary EMS - Node 3
Primary CA - Node 4
Secondary EMS - Node 1
Secondary CA - Node 2
Result: You will see nothing from the front panel or console connection after performing this step.
Step 5 Action: At the CLI prompt, type the following command `reset'.
Result: You will see the reset banner.
Resetting CCN hardware and software on rdu-ems-(XX), where XX was the old node address. After the reset you should seerdu-ems-(XX) ccncli>
where XX is the new address that was just set.
Step 6 Action: reconnect all the CCPU net cables to the module.
Why: This reconnects the unit to the out-of band communication network.
Step 7 Action: At the CLI prompt, type the following command `faults reset'.
Result: The red "alarm" light will turn off on the front of the unit.
Why: This command clears the fault that tripped when the CCPU Net cables were removed. The fault is a latching fault so it must be reset to clear the alarm.
Connect External Network Uplink Cables to Ethernet Switches
Follow these steps to connect the external network uplink cables to the Ethernet switches:
Step 1 Refer to Figure 1 to identify which Cisco 2924M Ethernet Switch is designated Ethernet Switch A and which is Ethernet Switch B.
Step 2 If your local network documentation calls for gigabit Ethernet, contact Cisco TAC for assistance.
Step 3 If your local network documentation calls for 100 Mb Ethernet, connect the applicable network uplink cables as listed in Table 1. Ports #21 through 24 are available for this use.
Step 4 After installing the uplink cables, record the necessary information on a copy of Table 1 or similar document according to local procedures.
Connect Intershelf Power and Grounding Cables
After obtaining approval from a supervisor, an authorized power installer should follow these steps to connect the intershelf power and grounding cables to the individual machines in the Cisco BTS 10200 Softswitch. The intershelf power cables are provided with your shipment.
Caution Ensure redundancy of power feeds to your system, so that a single point of failure does not cause a loss of traffic:
— For DC systems, power each host from two separate (redundant) DC power feeds.
— For AC systems, power Side A hosts from a separate power source than Side B.
Step 1 For DC-powered systems, connect the cables as follows:
a. Use the specific DC power cable that was provided for each machine in your shipment.
b. Connect the intershelf DC power cables from the power distribution unit (PDU) to each of the devices in the rack. There are two intershelf DC power cables per machine (one for power feed A and one for B). See Table 1 for the complete cabling list.
c. Following local electrical codes, connect the ground cables from each of the devices in the rack to the PDU grounding point (either of the two grounding screws on the PDU rear panel). See Table 1 for the complete cabling list.
Step 2 For AC-powered systems, connect the cables as follows:
a. Use the specific AC power cable that was provided for each machine in your shipment.
b. For each A Side machine (A Side EMS, CA, and Ethernet Switch) connect the intershelf AC power cable from the device to one of the AC power strips.
c. For each A Side machine (A Side EMS, CA, and Ethernet Switch) connect the intershelf AC power cable from the device to the other AC power strip.
d. Connect the intershelf AC power cable from the Alarm Panel to either of the power strips.
Connect Site Power and Grounding Cables
This section describes how to connect site power and grounding cables for DC- and AC-powered systems.
Note Cisco strongly recommends that you use uninterruptible power for both AC and DC systems. The uninterruptible supply should be engineered to support system operation through any possible power interruption.
Caution Ensure redundancy of power feeds to your system, so that a single point of failure does not cause a loss of traffic:
For DC systems, power the A and B power feeds on the PDU from two separate (redundant) DC sources.
For AC systems, power each of the power strips from separate (redundant) AC power feeds.
Note For DC systems the nominal current rating for a complete Cisco BTS 10200 Softswitch system is 26A at -48 VDC, and the maximum current rating is 40A at -48 VDC.
After obtaining approval from a supervisor, an authorized power installer should follow these steps to connect the DC power from the office batteries to the PDU.
Step 1 Following local electrical codes, connect power cables from the power distribution unit (PDU) to dual feeds ("A" and "B") on the office batteries. Use Listed two-hole crimped lugs on the PDU side of the cable.
Step 2 Following local electrical codes, connect the PDU grounding point (both of the two grounding screws on the PDU rear panel) to CO earth ground using 6 AWG wire or heavier and a Listed two-hole crimped lug.
Follow these steps to connect site AC power.
Note For installations in the U.S.A. and Canada, two separate (redundant) circuits of 20A 120 VAC are required. The circuits must be sourced from separate transformer phases on separate breakers such that a single breaker trip will not disable both. They should also have dedicated ("green wire") earth grounds back to the same distribution panel grounding point. For countries other than the U.S.A. or Canada, contact your Cisco account team for electrical requirements.
Step 1 An authorized electrician must verify that the power source is adequate for the system.
Step 2 Connect each of the power strips to a separate AC feed as designated by the electrician.
This section explains how to enable IRDP functionality on the Cisco BTS 10200 Softswitch and on the network router.
Enable IRDP on the Cisco BTS 10200 Softswitch
Follow these steps to enable IRDP on the Cisco BTS 10200 Softswitch.
Note You should already have the Cisco BTS 10200 Softswitch application software installed on the system.
Step 1 Log in to EMS Side A as root user.
Step 2 Remove the defaultrouter file from /etc.
Step 3 There should be three default routes in the routing table. Remove all three of these with the following command:
route delete net default <gateway address>
Step 4 Execute the following command:
/usr/sbin/in.rdisc -s -f
Step 5 Edit S69inet and search and replace for rdisc -s with rdisc -s -f.
Note This will ensure that reboot will enable the irdp daemon.
Step 6 Put the following lines into the S68inet file:
if [ -f /usr/sbin/in.routed ];
\mv -f /usr/sbin/in.routed /usr/sbin/in.routed.org
Enable IRDP on Adjacent Cisco Routers
If you are enabling IRDP on Cisco routers adjacent to the Cisco BTS 10200 Softswitch, follow these steps. If you have any questions about setup of these routers, contact your system administrator. If you need additional assistance, contact Cisco TAC.
Step 1 Verify that you have the Network Information Data Sheet (NIDS) applicable to this Cisco BTS 10200 Softswitch. If necessary, contact your network administrator to verify that you have the correct NIDS.
Step 2 On default gateway interfaces for Network 1 and Network 2 (as defined in the NIDS) enable IRDP using the following commands:
interface <Fast Ethernet interface number (see NIDS)>
ip irdp maxadvertinterval 4
ip irdp minadvertinterval 3
ip irdp holdtime 10
Step 3 Validate the configuration by performing the following command on both CA/FS hosts and both EMS hosts:
login as root
Step 4 View the display and verify that each default route was populated dynamically by IRDP.
Verify IRDP Functions
Follow these steps to verify that IRDP is functioning properly on the network:
CA Side A
Step 1 Login to CA Side A as root.
Step 2 Display the IRDP daemon status by entering the following command:
ps -ef|grep in.rdisc
Step 3 View the display and verify that each default route was populated dynamically by IRDP. The display should include the following information: /usr/sbin/in.rdisc -s -f. (This indicates that IRDP is running properly.)
Step 4 Display the routing table by entering the following command:
Step 5 Verify that the routing table shows two default routes, one on interface NET 0 and one on NET 1.
Step 6 Unplug the interface NET 0 link at the back of CA Side A.
Step 7 Display the routing table by entering the following command:
Step 8 Verify that the route for interface NET 0 does not appear in the routing table.
Note When a link is unplugged or plugged back in, it may take 5 to 10 seconds for the IRDP function to automatically update.
Step 9 Plug the interface NET 0 link back in to CA Side A.
Step 10 Display the routing table (netstat -rn) and verify that the route for interface NET 0 appears in the routing table again.
CA Side B
Follow these steps to verify that all interfaces are configured on all computing elements:
Step 2 (If the Cisco BTS 10200 Softswitch application software has already been installed on the system) check the interface configurations using the following command on each of the four platforms (two EMS units and two CA/FS units):
Step 3 The system should display the message Validating..... If no errors are found during validation, the system will display the message No errors found. Verify that the No errors found message is displayed.
Note If the system does display an error, contact Cisco TAC for assistance.
Step 4 If the Cisco BTS 10200 Softswitch application software has not been installed on the system, install the application using the Application Installation procedure provided by Cisco. That procedure contains the appropriate commands to check the configurations (checkCFG).
Appendix A: Cable Labeling
Cables are labeled at both ends with the cable numbers listed in Table 1. Follow these steps to create and attach the labels.
Note As listed in Table 1, some of the cables require labeling and others do not.
Step 1 Make each label by copying the applicable number from Table 1 onto the label. Be sure to duplicate the number several times onto the label, as shown in Figure 7, to make it easier to read. (If desired, make the labels for all cables in one print run.)
Step 2 On a work bench or assembly table, position a cable so that one connector is on your left and the cable goes off to the right. (See Figure 7.)
Step 3 Attach the appropriate label to the cable as shown in Figure 7.
Step 4 Turn the cable around so that the other connector is on your left with the cable going off to the right.
Step 6 Repeat these steps for all cables in the rack, using the numbers from the cable list (Table 1).
Figure 7 Labeling Specification
Figure 8 Completed Cable Example
Appendix B: Cable List
Table 1 lists the ports and cables used for signaling and system management on systems using Continuous Computing AXmp hosts. Make a copy of this table for your records, and fill in the port numbers that you use on the Cisco 2924M Ethernet switches. It is recommended that you sign or check each box in the Verified column as you connect the cables. Store this completed table in the documentation package for this unit.
Table 1 Signaling and System Management Cables for Systems with AXmp Host Machines
From (Unit, Port) To (Unit, Port) Suggested
(see footnote 1)
Uplink to router for external communications1 (Network 1)
(see footnote 1)
Uplink to router for external communications1 (Network 2)
Alarm SER 1
Alarm SER 2
CA-A CCPU A
Alarm CCPUNet A-1
EMS-A CCPU A
Alarm CCPUNet A-2
CA-B CCPU A
Alarm CCPUNet A-3
EMS-B CCPU A
Alarm CCPUNet A-4
Alarm CCPUNet A-5
CCPU 012 02150-02602 REV 00 (not a cable)
CA-A CCPU B
Alarm CCPUNet B-1
EMS-A CCPU B
Alarm CCPUNet B-2
CA-B CCPU B
Alarm CCPUNet B-3
EMS-B CCPU B
Alarm CCPUNet B-4
Alarm CCPUNet B-5
CCPU 012 02150-02602 REV 00 (not a cable)
Alarm Panel Ground
1 The ports shown are applicable to 100 Mb Ethernet uplinks. Cable No. for uplink connections are customer-defined. See the procedure for more information. If you need to connect gigabit Ethernet instead of 100Mb Ethernet, contact Cisco TAC for assistance.
2 The CONSOLE cables are specially designed for Cisco 2924M Ethernet Switch CONSOLE port access. Make sure that you are using the correct cables. One end of the CONSOLE cable is labeled "switch" and the other is labeled "net CCN". The "switch" end must connect to the Hub and the "net CCN" end must connect to the Alarm Panel.
Appendix C: Translated Safety Warnings
Statement 1071—Warning Definition
Statement 1024—Ground Conductor
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
You can find instructions for ordering documentation at this URL:
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
•Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to firstname.lastname@example.org.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Cisco TAC Website
You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
•Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:
•iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:
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.
Cisco BTS 10200 Softswitch Cabling and IRDP Procedures for Medium Hardware Platform AXmp Option
Copyright © 2004, Cisco Systems, Inc., All rights reserved.