Release Notes for Cisco 6920 RateMux Multiplexer for Release 2.1

These release notes for the Cisco 6920 RateMux multiplexer support RateMux Release 2.1. These release notes are updated as needed to describe new features; memory requirements; hardware support; and changes to the microcode, configuration software, and related documents.

For a list of caveats that apply to Release 2.1, see the "Open CaveatsRelease 2.1" section.

These release notes discuss the following topics:

Introduction

The Cisco 6920 RateMux multiplexer is a real-time bandwidth management solution for digital cable operators and digital video service providers. The Cisco 6920 uses high-speed programmable DSPs to dynamically perform real-time rate conversion and bitstream manipulation on encoded MPEG-2 streams. This maximizes audio, video, and data signal throughput and effectively widens bandwidth capability, while ensuring quality transmission at full transponder link rates.

The Cisco 6920 accepts up to 15 MP&ML MPG-2 input signals through DHEI or DVB-ASI compliant interfaces. The unit's programmable statistical remultiplexing engine then performs real-time Variable Bit Rate (VBR) and Constant Bit Rate (CBR) rate conversion and bitstream manipulation processing to the input streams.

Using a proprietary statistical model, the processed streams are then recombined into a highly efficient, multiplexed program transport stream while maintaining video quality. The Cisco 6920 processing engine, aside from performing static grooming, also supports PID filtering and PCR jitter removal.

System Requirements

Hardware Supported

The hardware components supported in this release include:

C6920-CHAS Chassis
C6920-FRNTPLN Front Plane
C6920 POWER Power Supply Assembly
C6920-PWRPC PowerPC Card
C6920-DSP3 DSP Card with 3 DSPs
C6920-DVB-I/O DVB I/O Card (3 in, 2 out)
C6920-DVB-INPUT DVB Input Card (4 out)
C6920-DHEI-I/O DHEI I/O Card (3 in, 1 out)
C6920-DHEI-INPUT DHEI Input Card (4 in)

Upgrading to a New Software Release

Note These instructions assume that you have BootLoader version 148 or later running on your Cisco 6920.

To upgrade the Cisco 6920, you need the following files:

connect.exe---Windows application to connect to the BootLoader on the Cisco 6920.
binstall181.fls---Special file required to upgrade the BootLoader.
dhei_io_r2_147.ld---Reprograms the DHEI I/O card.
dvb_io_r2_147.ld---Reprograms the DVB I/O card.
dvb4_in_125.ld---Reprograms the DVB Input card.
dhei4_in_124.ld---Reprograms the DHEI Input card.
dsp3_141.ld---Reprograms the DSP card.
ppc2.1.ld and ppcenv2.1.ld---Reprograms the PowerPC card.

Cisco recommends that you use Windows NT and a crossover Ethernet cable to connect your PC to the Cisco 6920.

To upgrade the Cisco 6920 firmware:

Step 1 Copy the files to the PC.

Create a directory on your PC and populate it with all the listed files.

Step 2 Verify the Hyperterminal connection and get the BootLoader version number and the IP and Ethernet addresses.

Connect a regular serial cable to the DEBUG port on the PowerPC card. Start a Hyperterminal session on that connection (57,600, 8 bits, no parity, 1 stop bit, flow control = none).

Reset the Cisco 6920 and press the Enter key at 2- to 5-second intervals until the BootLoader menu appears on the screen (on older systems, depending on hardware and firmware configuration, this can take anywhere from 5 to 60 seconds). The first few lines will show the BootLoader revision number and the IP and Ethernet addresses being used by the Cisco 6920. Make a note of them---you will need them later.

The default addresses are 192.168.0.200 and 00:22:33:44:55:66, respectively.

Caution Hyperterminal on Windows 95 does not consistently operate properly with the Cisco 6920. (It displays output, but ignores any input).

Caution The BootLoader will start the PowerPC application if no keys are pressed within a few seconds. To avoid this, press Enter, then leave the Cisco 6920 in this configuration.

Step 3 Set up the Ethernet connection.

Connect the crossover cable from your PC to the Cisco 6920. Make sure that the IP addresses are on the same network. From your PC you should be able to successfully ping the Cisco 6920.

Step 4 Load the new BootLoader code.

Reset the Cisco 6920, then connect to the Cisco 6920 using the connect.exe program (connection should be established within 10 seconds).

At the top-level menu, select A: Download Boot Code Firmware.

At the "INFO: Waiting for BootLoader file ..." message, download file binstall181.fls using the File and Download selections. The following messages should appear:

About to reprogram BootLoader ... Erasing FLASH ... Programming FLASH ... BootLoader was reprogrammed, you can reset the system ...

This completes the BootLoader upgrade.

Caution In this phase, the BootLoader is being reprogrammed. A major failure, such as a power off, causes the Flash memory on the PowerPC card to be corrupted. If this happens, the only corrective action is to send the board back to Cisco for reprogramming. Even if you fail to see any output on the Hyperterminal window, do NOT reset the PowerPC card for at least 2 minutes.

Step 5 Program the PowerPC board.

Reset the Cisco 6920, then connect to the Cisco 6920 using the connect.exe program. Connection should be established within 10 seconds.

At the BootLoader top menu, select F: Easy Chassis Download.

At the Do you want to be in CHASSIS mode? [n]: prompt, type n and press Enter.

You are prompted to load the PPC card Flash. At the Do you want to load the PPC file?[n]:prompt, type y, press Enter, then load file PPC2.1.ld.

At the Do you want to erase the Application Configuration? [y]: prompt, press Enter. If you want to save the previous configuration, type y and press Enter. At the Do you want to load the board parameters? [n]: prompt, type y, press Enter, then load file PPCenv2.1.ld.

When prompted, type the IP address, Ethernet address, and card name.

Step 6 Program all other boards in the chassis.

Perform the regular field firmware upgrade.

Reset the Cisco 6920, then connect to the Cisco 6920 using the connect.exe program. Connection should be established within 10 seconds.

At the BootLoader top menu, select F: Easy Chassis Download.

At the Do you want to be in CHASSIS mode? [n]: prompt, type y then press Enter. The BootLoader will take some time to configure all the boards in the chassis (up to 60 seconds).

For each board in the chassis, you will be asked whether you want to perform a software upgrade. Type y then press Enter for the cards that you want to program. At the INFO: Waiting for Module ... message, download the correct file using the File and Download selections. Use the following files:

dhei_io-r2_147.ld---for DHEI I/O cards
dvb_io_r2_147.ld---for DVB I/O cards
dsp3_141.ld---for DSP cards
dvb4_in_125.ld---for DVB input cards
dhei4_in_124.ld---for DHEI input cards

You will be prompted to load the PPC card Flash memory. Because this was already done in Step 5, press ENTER when prompted to load any files or to erase the application configuration.

At this point, the Cisco 6920 has been upgraded. Reset the Cisco 6920. After approximately 60 seconds, connect from a Netscape browser.

Note Any additional .ld and .fls files are for support use only.

File and Module Revision Numbers

For identification purposes, following is a list of revision numbers for all files and modules.

DHEI Input Board---Version 124 (file dhei4_in_124.ld)

FPGALOAD---Ver 123 (file dhei4_in_123.fls)
DVB Input Board---Version 125 (file dvb4_in_125.ld)

FPGALOAD---Ver 123 (file dvb4_in_123.fls)
DHEI I/O Board---Version 147 (file dhei_io_r2_147.ld)

DSPDIAG1---Ver 124 (file memdiag124.fls)

DSPDIAG2---Ver 129 (file getandout129.fls)

DSPDIAG3---Ver 129 (file getandput129.fls)

DSPDIAG4---Ver 127 (file prdtdiag127.fls)

FPGALOAD---Ver 135 (file dhei_io_r2_135.fls)
DVB I/O Board---Version 147 (file dvb_io_r2_147.ld)

DSPDIAG1---Ver 124 (file memdiag124.fls)

DSPDIAG2---Ver 129 (file getandout129.fls)

DSPDIAG3---Ver 129 (file getandput129.fls)

DSPDIAG4---Ver 127 (file prdtdiag127.fls)

FPGALOAD---Ver 131 (file dvb_io_r2_131.fls)
DSP Board---Version 141 (file dsp3_141.ld)

DSPDIAG1---Ver 124 (file memdiag124.fls)

DSPDIAG3---Ver 129 (file getandput129.fls)

DSPDIAG4---Ver 127 (file prdtdiag127.fls)

FPGALOAD---Ver 125 (file dsp3_125.fls)
Bootloader--- Version 181 (file binstall181.fls)

PPCAPP---Ver 198 (file main198.fls)

DEMUX---Ver 159 (file dsp_dmux159.fls)

MUX---Ver 164 (file dsp_mux164.fls)

PPC---Ver 113 (file ppc113.fls)

DSP---Ver 116 (file dsp116.fls)

DHIN---Ver 113 (file inp113.fls)

DHOUT---Ver 126 (file outp_r2_126.fls)

DVIN---Ver 114 (file dvbinp114.fls)

DVOUT---Ver 123 (file dvboutp123.fls)

CMBOUT---Ver 101 (file dvb_comboutp101.fls)

New and Changed Information

The following section lists the new features supported in Release 2.1.

New Features in Release 2.1

Default for Output PSI Data Rate

The default for Output PSI Data Rate has been changed to 500 (in milliseconds).

Disable Private Table Selection

A new check box, Disable Private Table Collection, has been added to the Advanced page of the RateMux Manager browser interface. Unless this option is selected, in addition to collecting PAT and PMT of table ID 0x2, the Cisco 6920 starts collecting tables that are carried in the transport packets with the same PID as PMT_PID and have table IDs of 0x40, 0x41, 0xc and 0xc1.

The Cisco 6920 collects these special tables for every incoming program. The collection process usually takes 15 seconds. If every incoming program contains all four of these special tables, the collection finishes in under 15 seconds. Otherwise, the collection times out in 15 seconds. For that reason, after enabling the private table collection, wait at least 30 seconds before clicking Program Select to start configuring the output transponder. Clicking Program Select causes the Cisco 6920 to copy the latest snapshot of the PSI data (including the special tables) to the user's EditList.

When you click Apply to commit the output transponder configuration, the snapshot of the special tables becomes part of the Cisco 6920's output PSI data.

Monitor Rate Page Display

The Monitor Rate Page now displays a bar chart instead of a table to allow viewing of the input and output bit rates for each video stream selected in the channel lineup. The bar chart can be customized for color and representation of scale.

Custom Browser Logo

A feature has been implemented to allow the storage of a customer-generated logo for the browser in FLASH memory.

To use a custom logo on the web browser, use the following procedure:

1. Convert the logo file from a .gif file to a .fls file by using the srec2fls utility running in a DOS window. The syntax is:

srec2fls -f inputfile -0 outputfile [-da] [-t type] [-e entrypoint]

[-v version] [-s memorysize]

where

inputfile

the name of the input file

outputfile

the name of the file to be generated

type

used as the type of the output file. It is also used to determine whether the input file should be interpreted as an executable file in S-Record format (types 2, 6, 7, 8, 11, 12, 13, 14, 15) or as a binary file.

entrypoint

the entry point of an executable file

version

the version number to be used (maximum seven characters)

memorysize

the maximum size of the internal buffer (default is 1 MB)

-d

provides more information

-a

generates the output in ASCII format

inputfile	the name of the input file
outputfile	the name of the file to be generated
type	used as the type of the output file. It is also used to determine whether the input file should be interpreted as an executable file in S-Record format (types 2, 6, 7, 8, 11, 12, 13, 14, 15) or as a binary file.
entrypoint	the entry point of an executable file
version	the version number to be used (maximum seven characters)
memorysize	the maximum size of the internal buffer (default is 1 MB)
-d	provides more information
-a	generates the output in ASCII format

For example, to convert the file logo.gif into a FLASH file logo.fls with version number 745, the command is:

srec2fls -f logo.gif -o logo.fls -t 0x24 -v 745

srec2fls -f logo.gif -o logo.fls -t 36 -v 745

2. Download the .fls file into the PowerPC FLASH by using the bootloader (menu choice "Download Flash Modules"). The partition type in Hexidecimal for this logo FLASH file is 0x24.

3. Add or change the variable OEMLOGO to OEMLOGO=YES and save it to FLASH.

Note Any string except NONE assigned to OEMLOGO is the same as YES.

Application Notes

Control Across Gateways

It is possible to control the Cisco 6920 across gateways. In order to do so, the environment variable GATEWAY has to be defined; for example, "GATEWAY=10.0.0.6". Only one gateway can be specified. For information on how to define an environment variable, refer to the "Upgrading to a New Software Release" section.

Using the EEPROM on the PowerPC Card to Store Variables

The EEPROM on the PowerPC card is currently used as follows:

If there is no EEPROM on the PowerPC card, the Ethernet address is stored in FLASH, and any modifications can be done from the Environment menu in the Bootloader.
If the EEPROM is present and its content is valid, the ETHERADDR variable in the Environment is assigned the value read from the EEPROM at start up.
If the EEPROM is present and its content is not valid, the ETHERADDR variable in the Environment is used.

The following applies to PowerPC cards with the EEPROM present:

To program the content of the EEPROM with an Ethernet address, and permanently store the Ethernet address on the PowerPC board, use the "Manufacturing Menu" in the Bootloader. From there, load the Ethernet address into the EEPROM. ETHERADDR in the Environment will also be updated.

During "EasyChassisDownload", after loading the file ppcenvxxx.ld, the prompt "Enter New Ethernet Address" will not appear. If the content of the EEPROM is valid (previously written by the user), ETHERADDR has the value from the EEPROM. Otherwise, it has the value from FLASH.

If the ETHERADDR is changed in "Change Environment Parameter" and "Add Environment Parameter", two different results are possible:

1. If "Save Environment to Flash" is not selected, the new Ethernet address only will be valid until the next reset.

2. If "Save Environment to Flash" is selected, the new Ethernet address will not be stored in the ETHERADDR environment variable, which will keep the old value.

Revision Number in FLASH

A new environment variable "Version" has been defined. When a board is loaded using the .ld file (or more than one .ld file for the PowerPC card), this variable will contain the version number of that file (VERSION=2.0.4 if loading ppc2.0.4.ld and ppcenv2.0.4.ld). This applies to the environment variables on all boards. (For each board you should expect the version number from the appropriate .ld file.)

In order to keep track of cases where individual FLASH partitions are loaded (for example, by using the .fls files), this variable is erased from the environment if any FLASH partitions are modified.

Caveats

Open Caveats---Release 2.1

This section describes possibly unexpected behavior by Release 2.1.

CSCdr02160

: This release does not support a Maximum Rate for the Video PID in a program.

CSCdr02179

: It is not possible to select the same PID as part of two programs in the same output stream.

CSCdr02183

: It is not possible to select programs not currently present in one of the input streams.

CSCdr02185

: The SNMP agent is not enabled in this release.

CSCdr02188

: PCRs carried on PIDs different from Audio and Video (in particular PCRs that are shared across programs) are not handled correctly and result in drifts.

CSCdr19329

: DHEI 256 QAM at 38.8 Mbps is not supported in this release.

CSCdr30637

: Transponder names entered in the user interface are not stored and may be lost after a power failure.

CSCdr30669

: Adjustment steps of the output bit rate are too high. For some applications, the bit rate must be adjustable in smaller steps.

CSCdr30678

: The ability for names to be assigned to selected services in the configuration overview is not supported in this release.

CSCdr32575

: There currently is no way to drop or add individual channels to one output without a full reconfiguration of that output.

CSCdr39861

: The PCR jitter of the output stream occasionally exceeds +/- 500 ns.

CSCdr54584

: When switching between outputs in the browser, the previous output configuration values are carried over to the new output, which can cause confusion.

CSCdr59330

: An occasional audio decoder buffer overflow occurs with AC-3 audio in regard to the AC-3 standard. However, it does comply with the MPEG-2 audio buffer decoder model.

CSCdr66012

: When using two browsers showing two different outputs, the Monitor Rate window may display incorrect values.

CSCdr66998

: The PARAMS partition is occasionally corrupted when the C6920 is reset right after a save operation of the environment.

CSCdr69251

: TP packetizer doesn't handle the case: PUSI= zero.

CSCdr70550

: The Cisco 6920 may fail during 40% or more high rate reduction configurations after a long period of operation. Cycle the power or push the reset button to clear the problem.

CSCdr70654

: Executing a ForceMap incorrectly maps the PCR PID when using a harmonic source which has PCR on an audio PID.

CSCdr71655

: The ForceMap option does not remap PIDs specified in the PassThru window.

CSCdr73203

: PassThru PIDs may not appear after a rebuild after clicking Apply.

CSCdr73556

: When there are three or more I/O cards in the Cisco 6920, trying to rename any I/O port in the Transponder Map returns an error.

CSCdr75905

: In the Monitor Rate screen, magenta is the only color currently supported for output.

Resolved Caveats---Release 2.1

All the caveats listed in this section are resolved in Release 2.1.

CSCdr08158

: DMX audio (programs with audio-only streams) may experience some audio breakup or missing audio.

CSCdr02168

: The feature to rename Output Streams does not work properly.

CSCdr02171

: Only two audio PIDs per program can be played at this time.

CSCdp97260

: During configuration changes, not all internal resources (SPIDs) are released. Over time, this causes the system to run out of those resources. The system has to be reset to resolve this problem.

CSCdr02611

: PSI task hangs when encountering system errors such as failure to allocate memory, or failure to disable an Input PID.

CSCdr08480

: Descriptors are not being parsed correctly.

CSCdr28341

: Output PSI only generates PMTs and ignores tables of other types.

CSCdr45575

: Incoming PSI data is not handled correctly where multiple PMTs share the same PID.

CSCdr48450

: When IRT has no RF source, the Cisco 6920 does not display collected PSI data.

CSCdr48481

: Output configurations not being saved when unit is reset.

CSCdr50331

: Incorrect bandwidth assignment for PSI data.

CSCdr06521

: PMT parameters set but not used.

CSCdr08472

: "--" incorrectly displayed as "-1" in the output sections of EditMaps and EditQos pages.

CSCdr09391

: Error in submitting program selection in EditMap page.

CSCdr09992

: Memory corruption when doing Apply in EditMaps.

CSCdr20450

: The time between two PCR stamps will sometimes exceed 40 ms., while the standard specifies no more than 40 ms.

CSCdr29100

: The DSP resets when any of the video PIDs is scrambled, but the associated audio PID is not.

CSCdr30639

: DVB-reserved PIDs are used with automatic PID remapping.

CSCdr30654

: The default PSI rate is too low. The default value has been changed to 500 ms.

CSCdr30704

: Clicking Help now links to the user documentation on CCO.

CSCdr32555

: If an attempt is made to upload an erased configuration file to the host PC, the uploaded file grows until the disk space is exhausted.

CSCdr34331

: TS buffer overflow with multiple audio/teletext PassThru PIDs.

CSCdr37436

: In EditQos page, if one program is selected and psiomit is checked, clicking Apply results in an error message.

CSCdr44283

: The PowerPC code should automatically detect the size of the DSP it is trying to load.

CSCdr44354

: SNMP: Incorrect entity parent position for boards.

CSCdr50016

: Web browser connectivity issues.

CSCdr50205

: When the PAT table is longer than 183 bytes, the PUSI bit in the output transport packet is incorrectly set when there is no beginning of section on the packet.

CSCdr50408

: Options in the Advanced Window are inconsistent.

CSCdr58280

: The system can fail to release resources if an "Apply" fails.

CSCdr59912

: The default setting of Private Table Collection is incorrectly set to Disabled.

CSCdr60270

: Using the set top box, when selecting 7 video programs and 45 DMX audio channels, audio channels cannot be heard.

CSCdr62215

: Invalid descriptors were observed in the PMTs of the outgoing PSI data when Private Table Collection was enabled.

CSCdr54578
CSCdr59284

: Audio associated with video drops after a period of operation.

CSCdr65804

: Memory leak occurs when repeatedly loading EditMaps and Program Select.

CSCdr64779

: When harmonic feed has two inputs, one at 3mbps and the other at 6mbps, and the 3mbps channel shares a DSP with another channel, it causes drift errors in the debug log.

CSCdr64930

: If any inputs carry invalid data, the Cisco 6920 can experience blackouts.

CSCdr66993

: In the manufacturing menu in the bootloader, there should be an option to read the Ethernet address from EEPROM and to determine if EEPROM is present.

CSCdr68450

: When the system is configured for heavy rate reduction, all video channels occasionally go black.

CSCdr70551

: If the DHEI input is momentarily removed and replaced, the RateMux starts producing video with buffer underflows.

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com
Telnet: cco.cisco.com
Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
- From North America, call 408 526-8070
- From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com

Language	E-mail Address
English	tac@cisco.com
Hanzi (Chinese)	chinese-tac@cisco.com
Kanji (Japanese)	japan-tac@cisco.com
Hangul (Korean)	korea-tac@cisco.com
Spanish	tac@cisco.com
Thai	thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Documentation Feedback

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 and value your comments.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)

Table of Contents

Release Notes for Cisco 6920 RateMux Multiplexer for Release 2.1