Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IOS and NX-OS Software

IGMP-Triggered VDOC Broadcast Support on the Cisco CMTS Routers

Downloads

Table Of Contents

IGMP-Triggered VDOC Broadcast Support on the Cisco CMTS Routers

Finding Feature Information

Contents

Prerequisites for Configuring VDOC Broadcast

Restrictions for Configuring VDOC Broadcast

Information About Configuring VDOC Broadcast

How to Configure VDOC Broadcast

Configuring the Primary and Secondary Bonding Group

Prerequisites

Restrictions

Configuring the RCC Template

Dynamic RCC Selection

RCC Assignment across SPAs

Prerequisites

Configuring the Multicast Static Group

Multicast Static Group

Prerequisites

Configuration Examples for VDOC Broadcast

Configuring the Primary and Secondary Bonding Groups: Example

Configuring the RCC Template: Example

Configuring the Multicast Static Group: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

Feature Information for Configuring VDOC Broadcast


IGMP-Triggered VDOC Broadcast Support on the Cisco CMTS Routers

First Published: December 17, 2008
Last Updated: February 16, 2009

The Cisco universal broadband router supports the video over DOCSIS (VDOC) Broadcast feature enabling multiple system operators (MSOs) to broadcast video content on RF-spanned downstream signals.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for Configuring VDOC Broadcast

•Restrictions for Configuring VDOC Broadcast

•Information About Configuring VDOC Broadcast

•How to Configure VDOC Broadcast

•Configuration Examples for VDOC Broadcast

•Additional References

•Command Reference

•Feature Information for Configuring VDOC Broadcast

Prerequisites for Configuring VDOC Broadcast

Table 1shows the hardware compatibility prerequisites for the VDOC broadcast feature.

Table 1 Cable Hardware Compatibility Matrix for the VDOC Broadcast Feature

CMTS Platform
Processor Engine
Cable Interface Line Cards

Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.2(33)SCB

•PRE2

•PRE4

Cisco uBR10-MC5X20S/U/H


The software prerequisites for the VDOC broadcast feature are:

•The Cable Modem Termination System (CMTS) and the cable modem must have the latest DOCSIS 3.0 setup with Multicast DSID-based Forwarding (MDF) and Dynamic Bonding Change (DBC) capability.

•The Cisco uBR10012 router must have the M-CMTS setup.

•The cable modem software must support channel change capability via Receive Channel Configuration (RCC) TLV (49.5) in the DBC message.

•Support for DOCSIS 3.0 channel bonding.

Restrictions for Configuring VDOC Broadcast

•This feature is supported only for DOCSIS3.0 cable modems that have modular primary downstream.

•The VDOC Broadcast feature supports:

–Only one tuner per cable modem.

–3-channel and 4-channel cable modems only.

–Only one video stream per IP set-top box.

–Only one IP set-top box for every cable modem.

•IGMPv3 configuration is required on the bundle interface.

•Secondary bonding groups used for video streams must be created using only one downstream RF channel.

•The secondary bonding group must not be used for forwarding by other features such as VOD and service flow attribute-based forwarding interface selection.

Information About Configuring VDOC Broadcast

The VDOC Broadcast feature facilitates broadcasting video over Data Over Cable Service Interface Specification (DOCSIS). Video streams are broadcast to one or more downstream RF channels using static multicast. Depending on the video stream selected for viewing by the IP set-top box, the multi-tuner cable modem is tuned to the appropriate RF channel carrying the specific video stream.

The process to broadcast video over the cable is given below.

1. When a user selects a channel, the IP set-top box sends an Internet Group Management Protocol (IGMP) join message to the specific bonding group.

2. The CMTS locates the secondary bonding group that has the video streaming channel and the RCC template that contains the channel corresponding to the secondary bonding group.

3. The CMTS sends a DBC-REQ message to the modem. The DBC-REQ message contains the DSID. It also contains a new RCC (that contains frequencies for the primary bonding group and the secondary bonding group that was selected in Step 2), if the modem is not currently tuned to the frequencies selected in Step 2.

4. The cable modem retunes to the new channel and receives the video stream.

Note In the case of subsequent channel changes, the IP set-top box sends an IGMP leave message for the old video stream. CMTS responds with the DBC-REQ message to remove the DSID corresponding to this stream.

How to Configure VDOC Broadcast

This section describes the configuration tasks that are performed when using the VDOC broadcast feature on the Cisco CMTS platforms. You can use the command-line interface (CLI) commands to complete the configuration.

1. Configuring the Primary and Secondary Bonding Group

2. Configuring the RCC Template

3. Configuring the Multicast Static Group

Configuring the Primary and Secondary Bonding Group

This section describes the configuration tasks to configure the MAC domain and the bonding group. Follow the summary steps to complete the configuration.

Configure the modular-cable controller for four RF-channels, two of which will be used for primary bonding group and the other two will be used for broadcasting video specific bonding groups.

Prerequisites

•The modular controller is already configured for RF channels used for the primary and secondary bonding groups. The RF channels used for secondary bonding groups are non-primary capable and can be served by legacy EQAM. The "udp-port" option can be used instead of "depi-remote-id".

•The MAC domain is configured by specifying the fiber-node configuration.

Restrictions

Secondary bonding groups must be constructed using only one RF channel.

SUMMARY STEPS

1. enable

2. configure terminal

3. controller modular-cable slot/subslot/bay

4. cable bonding-group-id id_num [secondary]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

controller modular-cable slot/subslot/bay

Example:

Router(config)# controller modular-cable 1/0/0

Enters the controller configuration mode.

•slot— The slot where the Wideband SIP resides. On the Cisco uBR10012 router, slots 1 and 3 can be used for the Wideband SIP.

•subslot—The subslot where the Wideband SIP resides. On the Cisco uBR10012 router, subslot 0 is always specified.

•bay—The bay in the Wideband SIP where the Wideband SPA is located. Valid values are 0 (upper bay) and 1 (lower bay).

Step 4 

cable bonding-group-id id_num [secondary]

Example:

Router(config-if)# cable bonding-group-id 2 secondary

Specifies a bonding group ID and indicates whether the bonding group is a primary or secondary bonded channel.

•id_num—A unique bonding group ID. Valid values are 1 to 255. The bonding group ID must be unique for each wideband channel on the CMTS.

•secondary—Specifies that the bonding group is a secondary bonding group. If the secondary keyword is not used, the bonding group is a primary bonding group.

Note Run the show interface wideband interface command to make sure the interfaces are up and running.

Configuring the RCC Template

This section describes the configuration tasks to configure the RCC template.

RCC templates must be configured and then applied on the MAC domain interface. With 3-channel cable modems, the first two channels are part of the primary bonding group, and the third channel is used for video. If two RF channels are used for carrying video streams, then two RCC templates must be configured.

Dynamic RCC Selection

Dynamic RCC selection feature facilitates multicast forwarding selection. RCC selection happens after the multicast forwarding selection algorithm identifies that the stream being requested is related to the VDOC Broadcast feature. It will select the RCC that is superset of the cable modem's primary bonding group, and the secondary bonding group upon which the stream is forwarded.

RCC Assignment across SPAs

The VDOC Broadcast feature requires modems to be tuned to RF-spanned channels carrying video streams. The RF-spanned channels originate from a SPA other than the SPA hosting the primary bonding group assigned to the cable modem. RCCs are generated from RCC templates that contain Receive Channels (RC) from multiple SPAs.

Limitations while assigning the RCCs are:

•For static multicast streams, only SPA downstreams can be used in RCC templates.

•Encrypted multicast or unicast traffic is not supported on the RC from a secondary SPA.

•For encrypted or unicast downstream VDOC broadcast , traffic will not be forwarded to CPEs even when the cable modem is properly tuned to the downstream.

Prerequisites

Modular controller and MAC domain configuration must be complete before you proceed to configuring the RCC template.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable slot/subslot/bay

4. cable rcc-template index

5. rcp-id rcp-id

6. receive-module index first-channel-center-frequency

7. receive-channel index center-frequency Hz connected-receive-module index [primary]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface cable slot/subslot/bay

Example:

Router(config)# interface cable 8/0/0

Associates the RCC template to a MAC domain. Enters interface configuration mode.

•slot/subslot/bay— The MAC domain address.

Step 4 

cable rcc-template index

Example:

Router(config)# cable rcc-template 1


Defines the RCC template for a Receive Channel Profile (RCP) outside the MAC domain configuration mode.

•index— The RCP index value.

Step 5 

rcp-id rcp-id

Example:

Router(config-rcc-template)# rcp-id 0010000004


Configures the RCP ID.

•rcp-id— The RCP ID.

Step 6 

receive-module index first-channel-center-frequency Hz

Example:

Router(config-rcc-template)#receive-module 1 first-channel-center-frequency 453000000


Configures the receive module.

•Hz— Assigned center frequency of the first channel of the receive module channel block in hertz.

Step 7 

receive-channel index center-frequency Hz connected-receive-module index [primary]

Example:

Router(config-rcc-template)# receive-channel 1 center-frequency 453000000 connected-receive-module 1 primary


Configures the receive channel.

•Hz— center frequency of a receive channel in Hz.

•connected-receive-module index—The RM index to which the current RM is assigned to attach. The configuration will be rejected if the connected-receive-module has not been previously configured.

•primary— (Optional) Indicates an RCC can be derived with this channel designated as the cable modem's primary channel.

Note Run the show cable mac-domain cable interface rcc command to verify that RCC templates are applied to the MAC domain.

Configuring the Multicast Static Group

This section describes the configuration tasks to configure the multicast static group.

One or more IGMP static groups corresponding to the broadcast video channels are configured on the specified secondary bonding group. The same groups should be specified under the cable bundle interface as part of the ip igmp static-group command.

Multicast Static Group

Multicast static group configuration is used to statically forward (broadcast) video streams on secondary bonding groups. This configuration specifies certain video streams should be broadcasted on particular bonding groups.

Prerequisites

•Multicast routing must be configured on the CMTS.

•PIM sparse-mode must be configured on the bundle interface.

•IGMP version 3 must be configured on the bundle interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface bundle1

4. ip igmp static-group {* | group-address [source {source-address | ssm-map}] | class-map class-map-name}

5. interface wideband-cable slot/subslot/bay:wideband-channel

6. cable igmp static-group [multicast group] source [source IP] [subinterface number]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode. Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface bundle1

Example:

Router# interface bundle1

The bundle interface.

Step 4 

ip igmp static-group {* | group-address [source {source-address | ssm-map}] | class-map class-map-name}

Example:

Router (config)# ip igmp static-group 224.0.0.0


Configures static group membership entries on an interface.

•*—Places the interface into all created multicast route (mroute) entries.

•group-address—IP multicast group address to configure as a static group member on the interface.

•source—(Optional) Statically forwards a (S, G) channel out of the interface.

•source-address—(Optional) IP address of a system where multicast data packets originate.

•ssm-map—(Optional) Configures Source Specific Multicast (SSM) mapping to be used on the interface to determine the source associated with this group. The resulting (S, G) channels are statically forwarded.

•class-map class-map-name—Attaches an Internet Group Management Protocol (IGMP) static group range class map to the interface.

Step 5 

interface wideband-cable slot/subslot/bay:wideband-channel

Example:

Router# interface wideband-cable1/0/0:1

The current configuration and status for a wideband channel.

•slot—The slot where the Wideband SIP resides. On the Cisco uBR10012 router, slots 1 and 3 can be used for the Wideband SIP.

•subslot—The subslot where the Wideband SIP resides. On the Cisco uBR10012 router, subslot 0 is always specified.

•bay—The bay in the Wideband SIP where the Wideband SPA is located. Valid values are 0 (upper bay) and 1 (lower bay).

•wideband-channel—The wideband channel number.

Step 6 

cable igmp static-group [multicast group] source [source IP] [subinterface number]

Example:

Router(config-if)# cable igmp static-group 224.0.0.0

Configures the cable per physical downstream Static Multicast support on the Cisco CMTS.

•multicast group—Multicast IP address of the group.

•source [source IP]— (Optional) Source IP address for SSM.

•subinterface number—Subinterface number. The default is 0 for the main interface.

Note If the subinterface is configured at the virtual bundle interface, the subinterface number option must be configured to match up with the desired subinterface devices.

Configuration Examples for VDOC Broadcast

This section describes a sample configuration example for configuring the VDOC broadcast feature.

This configuration supports four video channels (IGMP groups) over two bonding groups, with two channels over one bonding group each. Depending on the video channel selected by the cable modem's set-top box, the cable modem tunes to frequencies in either RCC template 1 or 2.

•Configuring the Primary and Secondary Bonding Groups: Example

•Configuring the RCC Template: Example

•Configuring the Multicast Static Group: Example

Configuring the Primary and Secondary Bonding Groups: Example

The following example shows how to configure the primary and secondary bonding groups. 

Router(config)# controller modular-cable 1/0/0

 ip-address 192.0.2.0

 modular-host subslot 6/0

 rf-channel 0 cable downstream channel-id 24

 rf-channel 0 frequency 453000000 annex B modulation 256qam interleave 32

 rf-channel 0 ip-address 192.0.2.0 mac-address 0090.f001.930c depi-remote-id 20000

 rf-channel 1 cable downstream channel-id 25

 rf-channel 1 frequency 459000000 annex B modulation 256qam interleave 32

 rf-channel 1 ip-address 192.0.2.0 mac-address 0090.f001.930c depi-remote-id 21000

 rf-channel 2 cable downstream channel-id 26

 rf-channel 2 frequency 465000000 annex B modulation 256qam interleave 32

 rf-channel 2 ip-address 192.0.2.0 mac-address 0090.f001.930c depi-remote-id 21001

 rf-channel 3 cable downstream channel-id 27

 rf-channel 3 frequency 471000000 annex B modulation 256qam interleave 32

 rf-channel 3 ip-address 192.0.2.0 mac-address 0090.f001.930c depi-remote-id 21002

!

Router(config)# interface Wideband-Cable1/0/0:0

cable bundle 1

 cable bonding-group-id 1

 cable rf-channel 0 bandwidth-percent 80

 cable rf-channel 1

!

Router(config)# interface Wideband-Cable1/0/0:1

 cable bundle 1

 cable bonding-group-id 2 secondary

 cable rf-channel 2

!

Router(config)# interface Wideband-Cable1/0/0:2

 cable bundle 1

 cable bonding-group-id 3 secondary

 cable rf-channel 3

!

Router(config)# interface Modular-Cable1/0/0:0

 cable bundle 1

 cable rf-bandwidth-percent 10

!

cable fiber-node 1

 downstream Modular-Cable 1/0/0 rf-channel 0-3

!

Configuring the RCC Template: Example

The following example shows how to apply the RCC templates to the MAC-domain host interface.

The frequencies used to configure the MAC domain and bonding group are also used here. 

Router(config)# cable rcc-template 1

  rcp-id 00 10 18 33 81

  receive-module 1 first-center-frequency 453000000

  receive-channel 1 center-frequency 453000000 connected-receive-module 1 primary

  receive-channel 2 center-frequency 459000000 connected-receive-module 1

  receive-channel 3 center-frequency 465000000 connected-receive-module 1

!

Router(config)# cable rcc-template 2

  rcp-id 00 10 18 33 81

  receive-module 1 first-center-frequency 453000000

  receive-channel 1 center-frequency 453000000 connected-receive-module 1 primary

  receive-channel 2 center-frequency 459000000 connected-receive-module 1

  receive-channel 3 center-frequency 471000000 connected-receive-module 1

!

Router(config)# interface Cable6/0/0

 downstream Modular-Cable 1/0/0 rf-channel 0 upstream 0-3

cable rcc-template 1

cable rcc-template 2

 no cable packet-cache

 cable bundle 1

 cable downstream channel-id 119

 cable downstream annex B

 cable downstream modulation 256qam

 cable downstream interleave-depth 32

 cable downstream frequency 615000000

 cable downstream rf-shutdown

 cable upstream max-ports 4

 cable upstream 0 connector 0

 cable upstream 0 frequency 10000000

 cable upstream 0 docsis-mode tdma

 cable upstream 0 channel-width 1600000 1600000

 cable upstream 0 minislot-size 4

 cable upstream 0 range-backoff 3 6

 cable upstream 0 modulation-profile 21

 no cable upstream 0 shutdown

 cable upstream 1 connector 1

 cable upstream 1 docsis-mode tdma

 cable upstream 1 channel-width 1600000 1600000

 cable upstream 1 minislot-size 4

 cable upstream 1 range-backoff 3 6

 cable upstream 1 modulation-profile 21

 cable upstream 1 shutdown

 cable upstream 2 connector 2

 cable upstream 2 docsis-mode tdma

 cable upstream 2 channel-width 1600000 1600000

 cable upstream 2 minislot-size 4

 cable upstream 2 range-backoff 3 6

 cable upstream 2 modulation-profile 21

 cable upstream 2 shutdown

 cable upstream 3 connector 3

 cable upstream 3 docsis-mode tdma

 cable upstream 3 channel-width 1600000 1600000

 cable upstream 3 minislot-size 4

 cable upstream 3 range-backoff 3 6

 cable upstream 3 modulation-profile 21

 cable upstream 3 shutdown

!

Configuring the Multicast Static Group: Example

The following example shows how to configure IGMP static groups on the bundle interface and on bonding groups. 

Router(config)# interface Bundle1

 ip address 192.0.2.8 255.255.255.0

 ip pim sparse-mode

 ip helper-address 2.39.16.1

 ip igmp static-group 224.0.2.1 

 ip igmp static-group 224.0.2.2 

 ip igmp static-group 224.0.2.3 

 ip igmp static-group 224.0.2.4 

 cable arp filter request-send 3 2

 cable arp filter reply-accept 3 2 

!

Router(config)# interface Wideband-Cable1/0/0:1

 cable bundle 1

Router(config)#cable igmp static-group 224.0.2.3

Router(config)#cable igmp static-group 224.0.2.4

 cable bonding-group-id 2 secondary

 cable rf-channel 2

!

Router(config)#interface Wideband-Cable1/0/0:2

 cable bundle 1

Router(config)#cable igmp static-group 224.0.2.1

Router(config)#cable igmp static-group 224.0.2.2

 cable bonding-group-id 3 secondary

 cable rf-channel 3

!

Additional References

The following sections provide references related to configuring the VDOC Broadcast feature.

Related Documents

Related Topic
Document Title

CMTS Command Reference

Cisco IOS CMTS Cable Command Reference http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Cisco uBR10012 Universal Broadband Router Documentation

Cisco uBR10012 Universal Broadband Router Hardware Installation Guide http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/guide/hig.html

Cisco uBR10012 Universal Broadband Router Software Configuration Guide http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/configuration/guide/scg.html

Cisco uBR10012 Universal Broadband Router Release Notes

http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_release_notes_list.html


Standards

Standard
Title

None

 

MIBs

MIB
MIBs Link

None

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs


RFCs

RFC
Title

None

 

Technical Assistance

Description
Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/public/support/tac/home.shtml


Command Reference

For information about commands, see the Cisco IOS CMTS Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.

Feature Information for Configuring VDOC Broadcast

Table 2 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release. Unless noted otherwise, subsequent releases of that Cisco IOS software release also support that feature.

Table 2 Feature Information for Configuring VDOC Broadcast

Feature Name
Releases
Feature Information

IGMP-Triggered VDOC Broadcast Support

12.2(33)SCB

The Cisco universal broadband router supports video over DOCSIS (VDOC) feature enabling multiple system operators (MSOs) to broadcast video content on RF-spanned downstream signals.

The following sections provide information about this feature:

•Configuring the Primary and Secondary Bonding Group

•Configuring the RCC Template

•Configuring the Multicast Static Group


CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2009 Cisco Systems, Inc. All rights reserved.