|
|
March, 2001
Hardware and Firmware Compatibility
Obtaining Technical Assistance
This document describes the Cisco MGX 8260 software release 1.2.2 (R01.02.02).
The hardware and firmware (boot code) versions for the FCS Release 1.2.2 components are highlighted in the following compatibility matrix:
:
| Card type | 800-Level | Hardware Version | Firmware Version | ||
|---|---|---|---|---|---|
| Current | Minimum | Current | Minimum | ||
MGX8260 | 800-06541 | -02 D2 | -01 A0 | N/A | N/A |
SCC5FC-4FE | 800-06392 | -01 F1 | -01 F0 | 01.02.02 | 01.01.03 |
SCC5FC-4OC3 | 800-06474 | -01 A1 | -01 A0 | 01.02.02 | 01.02.00 |
DMCFC-6T3 | 800-06326 | -01 F1 | -01 B0 | N/A | N/A |
SCCBC-4FE | 800-06325 | -01 C0 | -01 C0 | N/A | N/A |
T1E1BC-50NR | 800-06322 | -01 D0 | -01 D0 | N/A | N/A |
T3E3BC-6DSX | 800-06324 | -01 D0 | -01 D0 | N/A | N/A |
T1E1BC-RED | 800-06323 | -01 C1 | -01 B1 | N/A | N/A |
BSCFC-6T3 | 800-06397 | -02 C3 | -02 C0 | 01.02.02 | 01.01.03 |
NSCFC-8TDM | 800-06407 | -03 B0 | -02 A0 | 01.02.02 | 01.01.03 |
NSCFC-16TDM | 800-06408 | -03 B0 | -02 A0 | 01.02.02 | 01.01.03 |
NSCFC-8DSP | 800-06406 | -03 B0 | -02 A0 | 01.02.02 | 01.01.03 |
NSCFC-16DSP | 800-06405 | -03 B0 | -02 A0 | 01.02.02 | 01.01.03 |
OC3MMBC-4 | 800-06393 | -01 A0 | -01 A0 | N/A | N/A |
OC3SMIBC-4 | 800-06396 | -01 A0 | -01 A0 | N/A | N/A |
T1E1BC-RJ48 | 800-06463 | -01 A0 | -01 A0 | N/A | N/A |
SCC5FC-4FE/B | 800-15982 | -01 A0 | -01 A0 | 01.02.02 | 01.01.03 |
SCC5FC-4OC3/B | 800-16007 | -01 A0 | -01 A0 | 01.02.02 | 01.02.00 |
This section describes the new features in this release, and summarizes features from release 1.2.1.
This release contains the following new MGCP features:
This feature assures high quality transmission of DTMF tones through voice channels using G.726 or G.729 compression. This is important for calls that convey user information using inband DTMF tones. For example, an automated banking system may ask customers to enter account information using a touch-tone phone.
The Cisco MGX 8260 media gateway implements this feature by transferring DTMF information using RTP messages rather than voiceband signals. The local system detects the inband DTMF tones, suppresses their transmission as a voiceband signals, and relays the DTMF information to the remote system using RTP Named Telephone Events (NTE). The remote system interprets the RTP messages and regenerates the DTMF tones. This feature complies with IETF RTP standards.
This feature is always enabled and has no configuration options.
This software release optimizes a voice channel for data when it detects modem signals so it can support V.90-compliant modems. When a modem tone is detected, echo cancellation (ECAN), voice activity detection (VAD) and comfort noise generation are disabled and automatic upspeed to G.711 or 64K clear channel is enabled. A NTFY message is sent to the call agent, indicating the modem upspeed state.
The following existing commands have new parameters that support the modem detection and upspeed feature:
| Command | Description |
|---|---|
chmpc | Change MPC defaults |
lsmpc | List MPC defaults |
For more information, see Documentation Updates.
This software release provides support for multichassis deployments of E1 lines.
Release 1.2.1 introduced the following new features:
These include feature operation and support of E1 for the EMEA market.
Release 1.2.1 also introduced the following diagnostic commands:
| Command | Description |
|---|---|
stopdisk | Inhibit access to the hard disk. |
ping | Test connectivity to a remote host. |
lstrace | Show the most recent exception information and the CPU usage since the last reboot. |
lsprofiler | Show the current CPU usage. |
For more information, see Documentation Updates.
This section describe the software upgrade paths and security key requirements for software upgrade.
The following section describes the upgrade path and requirements.
R01.02.02 S/W supports upgrades from the following releases:
Boot flash update is required for all upgrades.
After upgrading to R01.02.02 or R01.02.01, the security key is required to download (tftp) software and bootflash images. To determine the security key code, use the dspkey command.
 |
Note When upgrading software from earlier releases (R01.02.00 or earlier), the security key code is not required. |
You do not need to clear the configuration database for this upgrade.
Because this upgrade changes the database, perform the upgrade procedures in the Cisco Command LIne Interface Guide. Refer to Upgrading Software Images in Chapter 3, Card Management.
This section describes changes to the BERT test and lists the open and closed caveats.
The following patterns were removed from the onbertds1 command:
(7) All ones
(8) All zeros
(9) Alternate ones and zeros
(10) Double alternate ones and zeros
(11) 3 in 24
(12) 1 in 16
(13) 1 in 8
The following caveats are open in this release.
.
| Identifiers | Description | Impact | Workaround |
|---|---|---|---|
CSCdr88819 | Multiple tftp connections cause the tTftp task to crash. | This only occurs when scripts are run on NT | Use tftp from a workstation. Don't run scripts on NT. |
CSCds54346 | The etherline task sends 1605 trap on addethln on SCC. | An Ethernet line alarm clear trap (1605) is sent when Ethernet lines are added. | The Ethernet lines should be in the no alarm state when they are added. |
CSCds56950 | Packet loss after adding more than 220 channels in E1 mode. | Packet loss after adding more than 220 channels on the same NSC when in the E1 mode. | Distribute channels on different NSC cards. |
CSCds60659 | End points stuck after 40 calls/sec with 10% COT run in 2 hrs. | After 2 hour run at 40 calls/sec with 10% COT, some endpoints are stuck. No new calls can be made on these endpoints until they are forced to clear. Other than COT, the system behaves normally and calls are not impacted. | None |
CSCds63355 | WebViewer with 5 users. | This problem only happens when 5 users log in at exactly same time and our web server cannot dispatch resources when 5 users request the same page. | The probability of this situation is small and hard to produce. A more powerful web server can handle this situation. |
CSCds86631 | The first 2 time slots fail the T1 TDM BERT test. | First and second timeslots intermittently fail the TDM BERT tests. | This occurs only with COMET chip Rev. E and F. |
CSCdt00032 | Cells lost when there are 2300 connections. | Cells are ocassionally dropped when there are 2300 connections with 4 Ethernet lines active. | None |
CSCdt00517 | DTMF mid signal duration is not working correctly. | A DTMF signal may not be detected if the signal duration is borderline. | None |
CSCdt05677 | Unplugging the redundant BSC affects calls in Active BSC. | With traffic running on established connections on a BSC configured with redundancy, ATM cells are dropped on the active BSC. ATM cells are dropped on the active BSC when the stand-by BSC is removed or reset. | None |
CSCdt08975 | The standby SCC fails after SCC and BSC switchover. | After simultaneous switchover of both BSC and SCC cards, for a number of times, the standby SCC restarts and then goes into the Failed state. | Reset the standby SCC to return it to the active state. |
CSCdt10260 | BIP-8 bit does not report cell crash error in the CbtPrintStatus function. | On the NSC card, when cubit receives crashed cells, the BIP-8 bit is set to high (non-zero). But this information is not reflected in CbtPrintStatus function. | None |
CSCdt13469 | NSC channel fail and address error messages in the event log. | Some endpoints are stuck if the call traffic overloads the same NSC, which supports 10 calls/sec/NSC. | Spread call traffic among several NSCs. |
CSCdt13497 | MRPC errors in event log and 502 responses to MGCP. | Some MGCP events in the event log are not explained in the user documentation. | N/A |
CSCdt25507 | No reason given and no interrogation possible for clock problems. | This feature is not supported. | None |
CSCdt25771 | Trunk IP lines do not respond to ICMP redirect messages. | For every RTP packet sent, 2 more packets are generated, the ICMP redirect and the RTP packet forwarded by the router to the SIP phone. This causes a threefold increase in bandwidth on the voice path. | This scenario only occurs when both media gateways are on the same subnet. |
CSCdt27330 | Event log should display session and group switchovers. | When a backhaul session or group switchover occurs, no event is placed in the event log. | None |
CSCdt27477 | Incorrect clock source card type displayed after entering the chsclksrc command. | After changing the secondary clocking source, the Clock Source Card Type field displayed by lsclksrc shows the secondary clocking source rather than the current clocking source. | None |
CSCdt31117 | Misleading information on T1 lines in the documentation. | The MGX 8260 documentation for DS1/T1 lines states that the received direction is always set to robbed bit. Change this to state that the default signal mode for DS1/T1 lines in the receive direction is none, rather than robbed bit signalling. | N/A |
CSCdt32628 | E1MC: Bearer path dropped on NSC switchover when using a snake configuration. | During an NSC switch over, a major alarm may occur and the connection drop when an E1 line on one NSC card is connected to a E1 line on a redundant pair of NSCs. | None |
CSCdt33468 | SCC card failure - no failure reason. | Sometimes the SCC card failure reason is "none", even after a legitimate failure. | None |
CSCdt34657 | The dbrstr command can fail catastrophically. | Affects database restoral. | Do not invoke clrndcnf prior to dbrstr. |
CSCdt34667 | The dbbkup command can damage the existing backup file. | Affects database backup. | Look for an existing config file (scc.rx.xx.xx.cfg) prior to initiating dbbkup. If such file exists, rename it before initiating dbbkup. Check both the active and standby SCCs. |
CSCdt34675 | Standby SCCs files not updated by upgd command. | Affects software upgrade. | After all service cards of a group (for example, all NSCs) are upgraded, logon to standby SCC and copy the service card image file to the default file. For the NSC: For the BSC: |
CSCdt36019 | SCC switched over after clrndcnf with error. | After entering the clrndcnf command, slot9 SCC unexpectedly logs a major, and then fatal event, and switches over. This occurs even though both SCCs have identical hardware revisions. | Do not issue clrndcnf while the delvports command is active. |
CSCdt37063 | The dbrstr command should check the software version. | A database from an older version of software can be restored on a newer version, which might have a different structure. | None |
CSCdt38399 | dbbkup command does not store config file to the standby SCC. | Affects database backup to the standby SCC. | After dbbkup is complete, transfer (tftp) it from the chassis to an external server. Later, when ready to dbrstr, download this file prior to doing dbrstr. Alternatively, after dbbkup is complete, move the config file to the Standby SCC manually. For example: moveFile2Target <ZERO based Standby SCC Slot Num>, "scc_rx.xx.xx.cfg", "scc_rx.xx.xx.cfg",3 |
CSCdt41862 | Idle code byte set in wrong channel. | Loss of voice in some channels. | None |
This release introduced new features that fixed the following caveats.
:
| Identifiers | Description |
|---|---|
CSCds00481 | Need a way to test DSEs capacity. |
CSCds76656 | MGX returns error 500 to CRCX even though the endpoint is correct. |
CSCds79877 | MGX does not comply with the RFC specs 2327 (t,c,m parameters). |
CSCds80380 | MGCP with empty requested events parameter does not work. |
CSCds85875 | MGX crashed while calls were added. |
CSCds86597 | Invalid addvport parameters for T1. |
CSCds89303 | MGCP event log & debug statements to print MGCP function name. |
CSCds89942 | Ethernet lines are down but connections are still being made. |
CSCds90162 | MPC logs a repetitive error for timers that clogs the eventlog. |
CSCds90738 | NSC card, when reset, sends RAI in error. |
CSCds91565 | Calls lost when SCC card physically pulled. |
CSCds92443 | SCC switchover causes the gateway address to be lost. |
CSCds92543 | TFTP image ends up in root instead of IMAGE/.. |
CSCdt00079 | Active card switched over (BIM SAR FAIL) with >2400 connections. |
CSCdt00142 | Similar to CSCds76656: # of Sdp Payload types > 8 returns 500. |
CSCdt00144 | MGCP - no reply to MDCX. |
CSCdt00382 | The mgcp_parmlines.h and mgcp_if.h files contain the same defines. |
CSCdt00462 | SCS-reset message should reset the COT process as well. |
CSCdt03011 | MPC and PCC should check the physical slot in etherLineInactive Trp. |
CSCdt04528 | Adding a session to the 6th fault-tolerant set fails. |
CSCdt04860 | The source code debugger is not working for the SCC. |
CSCdt06185 | The WebViewer response is very slow when using Netscape4.7. |
CSCdt06190 | AUEP returns 200 when endpoint is down or in alarm. |
CSCdt07125 | Continuous exceptions reported when they occur before the event log is initiated. |
CSCdt07202 | Multiple disk db commits in PRC may slow down the system. |
CSCdt08751 | The WebViewer shows a red dot for E1 lines when there is no alarm. |
CSCdt08962 | Packetization period 20ms/30ms produces noise in voice paths. |
CSCdt09760 | MRPC event swapped port and txId fields. |
CSCdt10735 | D-channels lost on NSC reset. |
CSCdt11243 | The chprotocol command does not set the protocol on the standby SCC. |
CSCdt13061 | Starting TEIs in the Dlsap Profile are not showing a valid range. |
CSCdt13541 | No Response to MDCX & DLCX at 10CPS. |
CSCdt14129 | For Etherline traps, use GetCardState not SiwCardState. |
CSCdt15447 | COT fails on PRI-SS7 calls. |
CSCdt17830 | Voice ports are deleted when a connection is made. |
CSCdt17843 | BSC FPGA die shrink requires a new download scheme. |
CSCdt19689 | BSC switchover occurring while doing an SCC switchover. |
CSCdt20253 | In CRCX m: INACTIVE, if one tone is provided for COT, need to reject. |
CSCdt23680 | MGCP AUCX returning 515 instead of 200. |
CSCdt26133 | The addvport command fails when no daughter card resides on the NSC card. |
CSCdt26199 | IPDC - SCS with multiple loopback returns an error. |
CSCdt27170 | Verify rmSvcParams on standby. |
CSCdt33077 | Remove the all-calls from WebViewer to be consistent with 121MR. |
CSCdt33122 | Gateway IP deleted when clrndcnf command is issued. |
CSCdt33673 | AUCX returning incorrect Connection ID (I:). |
This section describes the commands introduced or changed in releases 1.2.1 and 1.2.2. These additions and changes apply to the Cisco MGX 8260 Command Line Interface Guide.
Release 1.2.2 changes the chmpc and lsmpc commands. The chmpc command has two new parameters and the lmpc command lists these two new parameters.
Configure default MPC parameters.
chmpc DefTypeNetwork DefPktnPeriod DefBandwidth DefEchoCancel DefSilenceSupp DefTypeOfService DefResourceRes DefCOTReceiveTone DefCOTTransmitTone DefEncodingType DefReportFxMdmDet DefModemUpspeed
Syntax Description
DefTypeNetwork The type of network. 1 = voIp 2 = voAtm 3 = local DefPktnPeriod Packetization period in milliseconds. Value: fixed at 10 DefBandwidth The network bandwidth in kbps. Values: 8 and 64 kbps DefEchoCancel Enables or disables echo cancellation. 1 = off 2 = on DefSilenceSupp Enables or disables silence suppression. 1 = off 2 = on DefTypeOfService The type of Service. Values: 1-256, where 1 indicates no service type DefResourceRes The resource reservation type. 1 = bestEffort 2 = guaranteed 3 = notUsed 4 = controlledLoad DefCOTReceiveTone The default receive tone. For transponder COT, when the media gateway controller does not supply the tones, the default tone the gateway receives is the default COT receive tone. 1 = co1 (2010 Hz) 2 = co2 (1780 Hz) DefCOTTransmitTone The default transmit tone. For transponder COT, when the media gateway controller does not supply the tones, the default tone the gateway transmits is the default COT transmit tone. 1 = co1 2 = co2 DefEncodingType The type of voice encoding when not specified by the MGC: 1 = PCMA—A-law encoding 2 = PCMU—Mu-law encoding 3 = G729A 4 = G72632K DefReportFxMdmDet Enables or disables the modem upspeed reporting to the call agent. Values: 1 = Disable reporting 2 = Enable reporting DefModemUpspeed The modem up-speed encoding used when the line card detects modem tone on the active connection. Values: 1 = clearChannel 2 = g711 (G.711 u-law for T1 or G.711 a-law for E1)
Defaults
DefTypeNetwork: 3
DefPktnPeriod: 10
DefBandwidth: 64
DefEchoCancel: 1
DefSilenceSupp: 1
DefTypeOfService: 2
DefResourceRes: 1
DefCOTReceiveTone: 1
DefCOTTransmitTone: 2
DefEncodingType: 1
DefReportFxMdmDet: 2
DefModemUpspeed: 1
Command Modes
Security level 2
Command History
1.2 This command was first introduced. 1.2.2 Added modem and upspeed parameters.
Release
Modification
Usage Guidelines
Use this command to configure default MPC parameters.
Examples
The following command changes the upspeed encoding to G.711.
chmpc * * * * * * * * * * * 2
Related Commands
lsmpc List MPC information.
Command
Description
List MPC parameters.
lsmpcSyntax Description
The command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Security level 5
Command History
1.2 This command was first introduced. 1.2.2 Listing extended to include new parameters.
Release
Modification
Usage Guidelines
Use this command to list the default MPC parameters.
Examples
The following example displays MPC parameters.
lsmpc
=========================================================================
MPC Parameters (lsmpc)
=========================================================================
Default Type of Network : local
Packetization Period : 10
Bandwidth : 64
Echo Cancellation : off
Silence Suppression : off
Type of Service : 1
Resource Reservation : bestEffort
Default COT Receive Tone : co2
Default COT Transmit Tone : co1
Default Encoding Type : pcmu
Report Modem Upspeed Detection : yes
Modem Up-speed Option : clearChannel
The last two parameters indicate whether the Modem Detection feature is enabled or not, and the type of modem upspeed configured.
Related Commands
chmpc Change MPC information.
Command
Description
Inhibit access to the hard disk.
stopdisk option
Syntax Description
Option The number of the hard disk to stop. Values: 0 or 1.
Defaults
Option: 0
Command Modes
Security level 1
Command History
1.2.1 This command was first introduced.
Release
Modification
Usage Guidelines
This command inhibits access to the hard disk. Since the disk enters the power-cycle, you need to cycle the power off then back on to activate the IDE. Alternatively, unplug the SCC cards and plug them back in. This command is required before Power Reset.
Test connectivity to a remote host.
ping IP_Address numPkg option
Syntax Description
IP_Address The IP address of the host to test, expressed in standard dot notation. numPkg The number of test packets to send. Values: >=1 option The optional setting. 0 = No option 1 = Suppress output 2 = Do not route packets past the local network. 3 = Print debugging messages.
Defaults
IP_Address: none
numPkg: 1
option: 0
Command Modes
Security level 1
Command History
1.2.1 This command was first introduced.
Release
Modification
Usage Guidelines
Use this command to tests connectivity to a remote host.
Examples
The following examples show typical command usage:
ping 172.17.38.168
ping 172.17.38.168 2
ping 172.17.38.168 2 3
List trace information
lstraceSyntax Description
The command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Security level 1
Command History
1.2.1 This command was first introduced.
Release
Modification
Usage Guidelines
Use this command to show the most recent exception information and the CPU usage, before reboot.
Related Commands
lsprofiler List CPU usage.
Command
Description
List CPU usage.
lsprofilerSyntax Description
The command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Security level 1
Command History
1.2.1 This command was first introduced.
Release
Modification
Usage Guidelines
Use this command to show the current CPU usage for the last 1 minute for all the tasks executing on the card.
Related Commands
lstrace List trace information.
Command
Description
The following Cisco publications contain additional information related to the operation of Cisco MGX 8260 Media Gateway.
| Documentation | Description |
Cisco MGX 8260 Hardware Installation Guide DOC-7810966= | This book describes the procedures for hardware installation and initial software setup. |
Cisco MGX 8260 Command Line Interface Guide DOC-7810987= | This book describes how to configure MGX 8260 Media Gateways from the command line interface. |
Cisco WebViewer Guide DOC-7811012= | This book describes how to use the Cisco WebViewer tool. |
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site 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. (0102R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Sat Sep 28 13:40:29 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.