Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Broadband Processing Engines

Virtual Interfaces on the Cisco uBR-MC5X20S/U Card

Downloads

Table Of Contents

Configuring Virtual Interfaces on the Cisco uBR-MC5X20S/U Card

Contents

Prerequisites for Virtual Interfaces

Restrictions for Virtual Interfaces

Virtual Interfaces

HCCP N+1 Redundancy Support

Information About Virtual Interfaces

Feature Overview

Cisco uBR-MC5X20S/U Physical Port Assignments

Default Port Mapping

Virtual Interface Port Mapping

SNMP Support for Virtual Interfaces

Benefits

How to Configure the Virtual Interfaces Feature

Mapping Upstreams to a Downstream Port

Removing the Mapping from an Upstream

Monitoring the Virtual Interfaces Feature

Using the Command-Line Interface

Using SNMP Commands

Configuration Examples for Virtual Interfaces

1x4 Configuration

1x6 Configuration

1x8 Configuration

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

cable upstream connector

cable upstream max-ports

Mapping Worksheet


Configuring Virtual Interfaces on the Cisco uBR-MC5X20S/U Card

This document describes the Virtual Interfaces feature, which enables more flexible upstream allocation and usage on the Cisco uBR-MC5X20S and Cisco uBR-MC5X20U Broadband Processing Engine (BPE) cable interface line cards. By default, each model of these cards assigns four upstreams per downstream, but the Virtual Interfaces feature allows providers to associate any combination of upstreams (up to 8) to each downstream.

Feature Specifications for Virtual Interfaces

Feature History
Release
Modification

12.2(15)BC1

The Virtual Interface feature was introduced for the Cisco uBR-MC5X20S cable interface line card on the Cisco uBR10012 router.

12.2(15)BC2

Support was added for the Cisco uBR-MC5X20U cable interface line card.

Supported Platforms

Cisco uBR10012 router


Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

This document includes the following major sections:

•Prerequisites for Virtual Interfaces

•Restrictions for Virtual Interfaces

•Information About Virtual Interfaces

•How to Configure the Virtual Interfaces Feature

•Monitoring the Virtual Interfaces Feature

•Configuration Examples for Virtual Interfaces

•Additional References

•Command Reference

Prerequisites for Virtual Interfaces

The Virtual Interfaces feature has the following prerequisites:

•The Cisco uBR10012 router must be running Cisco IOS Release 12.2(15)BC1 or later Cisco IOS Release 12.2 BC release to support Virtual Interfaces on the Cisco uBR-MC5X20S card.

•The Cisco uBR10012 router must be running Cisco IOS Release 12.2(15)BC2 or later to support Virtual Interfaces on the Cisco uBR-MC5X20U card.

•You must be using the Cisco uBR-MC5X20S or Cisco uBR-MC5X20U cable interface line card. Virtual Interfaces are not supported on any other cable interfaces.

Restrictions for Virtual Interfaces

The Virtual Interfaces features have the following restrictions and limitations.

Virtual Interfaces

•Virtual Interfaces are supported only on the Cisco uBR-MC5X20S and Cisco uBR-MC5X20U cable interface line cards:

–When using the Cisco uBR-MC5X20S card, you must be using Cisco IOS Release 12.2(15)BC1 or later.

–When using the Cisco uBR-MC5X20U card, you must be using Cisco IOS Release 12.2(15)BC2 or later.

•The physical upstream and downstream ports being used for Virtual Interfaces must be located on the same Cisco uBR-MC5X20S/U card.

•Cisco IOS Release 12.2(15)BC1 does not support SNMP management of virtual interfaces.

HCCP N+1 Redundancy Support

•The Cisco uBR-MC5X20S/U card supports Virtual Interfaces and Hot-Standby Connection-to-Connection (HCCP) N+1 redundancy only when running Cisco IOS Release 12.2(15)BC2 or later. If you are using Cisco IOS Release 12.2(15)BC1 and have configured virtual interfaces on a cable interface, you must not assign that interface to any HCCP groups.

Note A cable interface is considered configured for Virtual Interfaces when one or more of its upstream ports is mapped to a different virtual upstream connector than the default configuration.

•If you have upgraded the Cisco uBR10012 router to Cisco IOS Release 12.2(15)BC2, and then later decide to downgrade to Cisco IOS Release 12.2(15)BC1, you must manually configure the Virtual Interfaces configuration on the Protect interfaces. If you do not do so, the Cisco uBR-MC5X20S card cannot succesfully switch over.

•When a cable interface is configured for Virtual Interfaces, an HCCP N+1 switchover always switches over the complete cable interface line card, even when only one of the Working interfaces on the card has failed.

•When using one Protect interface to protect multiple Working Cisco uBR-MC5X20S/U cards, all of the Working interfaces must be configured either to use Virtual Interfaces or to use the default connector configuration. You cannot use the same Protect interface to protect some Working interfaces that use Virtual Interfaces and other interfaces that do not use Virtual Interfaces.

Note The only exception to the above rule is if you use the hccp track command on the Working interfaces that do not use Virtual Interfaces. This forces the entire cable interface line card to switch over when a switchover occurs.

•The Working Cisco uBR-MC5X20S/U cards do not need to use the same Virtual Interfaces configuration to be included in the same HCCPgroup. Because the entire Cisco uBR-MC5X20S/U card is switched over when Virtual Interfaces are configured, you can simplify the HCCP configuration by specifying a bitmask of all one's (0xFFFFFFFF) when using the hccp channel-switch command.

Information About Virtual Interfaces

This section describes the Virtual Interfaces feature:

•Feature Overview

•Cisco uBR-MC5X20S/U Physical Port Assignments

•SNMP Support for Virtual Interfaces

•Benefits

Feature Overview

The Virtual Interfaces feature provides additional flexibility and efficiency in the allocation and usage of the upstreams on the Cisco uBR-MC5X20S and Cisco uBR-MC5X20U cards, which are part of the new Broadband Processing Engine (BPE) series of cable interfaces that are available for the Cisco uBR10012 universal broadband router.

The BPE support on the Cisco uBR-MC5X20S/U card provides the processing power necessary to allow configurable MAC domains, so that the upstreams are no longer fixed by their physical location, but can be assigned to a virtual upstream channel. The virtual upstream channel can then be assigned to any of the five downstreams on the card, depending on the particular requirements of each MAC domain.

Note Do not confuse the virtual upstream channels that are used by the Virtual Interfaces feature with the logical ports that are defined in the DOCSIS 2.0 specifications.

Cisco uBR-MC5X20S/U Physical Port Assignments

Figure 1 shows the front panel of the Cisco uBR-MC5X20U cable interface line card, which uses dense connectors. The front panel for the Cisco uBR-MC5X20S card is similar.

Figure 1 Cisco uBR-MC5X20U Front Panel (Dense Connectors)

The physical connectors for the upstreams and downstreams are labeled from left to right as you face the card. The twenty upstream connectors are labeled from US0 to US19, and the five downstream connectors are similarly labeled from DS0 to DS4.

Default Port Mapping

By default, the Cisco uBR-MC5X20S/U cable interface line card sequentially maps four upstreams to each of the card's five downstream ports. Table 1 lists the default mapping of the upstream ports, using the labels for the downstream and upstream ports that are on the front panel of the card.

Table 1 Default Interface to Port Mapping 

Port Set
Physical Ports
CLI Cable Interface Label

Domain #1

DS0 RF

CX/Y/0

US0

CX/Y/0 U0

US1

CX/Y/0 U1

US2

CX/Y/0 U2

US3

CX/Y/0 U3

Domain #2

DS1 RF

CX/Y/1

US4

CX/Y/1 U0

US5

CX/Y/1 U1

US6

CX/Y/1 U2

US7

CX/Y/1 U3

Domain #3

DS2 RF

CX/Y/2

US8

CX/Y/2 U0

US9

CX/Y/2 U1

US10

CX/Y/2 U2

US11

CX/Y/2 U3

Domain #4

DS3 RF

CX/Y/3

US12

CX/Y/3 U0

US13

CX/Y/3 U1

US14

CX/Y/3 U2

US15

CX/Y/3 U3

Domain #5

DS4 RF

CX/Y/4

US16

CX/Y/4 U0

US17

CX/Y/4 U1

US18

CX/Y/4 U2

US19

CX/Y/4 U3


Table 2 also shows the default mapping for the upstream ports on the Cisco uBR-MC5X20S/U cable interface line card, using a different format that matches the alignment of the upstreams on the card's front panel.

Table 2 Default Upstream Port Assignments for the Cisco uBR-MC5X20S/U Cable Interface Line Card

 
Physical Ports (upstream, as labeled on the card)
Physical Ports (downstream)
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

Domain #1
(DS0, CX/Y/0)

0

1

2

3

                               

Domain #2
(DS1, CX/Y/1)

       

0

1

2

3

                       

Domain #3
(DS2, CX/Y/2)

               

0

1

2

3

               

Domain #4
(DS3, CX/Y/3)

                       

0

1

2

3

       

Domain #5
(DS4, CX/Y/4)

                               

0

1

2

3


The X and Y in the CLI Cable Interface Label column in Table 1 and in the Physical Ports column in Table 2 refer to the physical card slot in which the card is installed. The value for X can range from 5 to 8, and the value for Y can be either 0 or 1. For example, to configure upstream port 16 (US16) when using the default configuration for a Cisco UBR-MC5X20S/U card in slot 5/1, you would give the following commands: 

Router# configure terminal 

Router(config)# interface cable 5/1/4 

Router(config-if)# cable upstream 0 sub-command... 

Router(config-if)# cable upstream 0 sub-command... 

Router(config-if)# cable upstream 0 sub-command...

Virtual Interface Port Mapping

Cisco IOS Release 12.2(15)BC1 introduced the ability to change the fixed, default mappings, so that you can associate any combination of upstreams (up to 8) with a particular downstream port. This allows you to create virtual DOCSIS MAC domains that do not depend on the physical location of the upstreams on the card.

For example, Table 3 shows a Cisco uBR-MC5X20S/U card where the first two upstreams are configured with 8 upstreams each, and the third downstream with 4 upstreams. The other two downstreams are not currently in use.

Table 3 Typical Virtual Upstream Channel Assignments for the Cisco uBR-MC5X20S/U Cable Interface Line Card

 
Physical Ports (upstream, as labeled on the card)
Physical Ports (downstream)
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

Domain #1
(DS0, CX/Y/0)

0

1

2

3

4

5

6

7

                       

Domain #2
(DS1, CX/Y/1)

               

0

1

2

3

4

5

6

7

       

Domain #3
(DS2, CX/Y/2)

                               

0

1

2

3

Domain #4
(DS3, CX/Y/3)

                                       

Domain #5
(DS4, CX/Y/4)

                                       

You do not need to assign upstream ports sequentially, but this is recommended because it simplifies network management and troubleshooting.

SNMP Support for Virtual Interfaces

Cisco IOS Release 12.2(15)BC2 introduced support for SNMP management of virtual interfaces. This support involves changes in the operation of the tables in the ENTITY-MIB and the IF-MIB.

To enable SNMP support for Virtual Interfaces, Cisco IOS Release 12.2(15)BC2 changed how the entPhysicalTable in the ENTITY-MIB displays the information for cable interface line cards. In previous releases, the cable interface line card was the parent to one or more MAC domains, and each MAC domain then was the parent to one downstream and one or more upstreams.

Because an upstream can now be associated with any MAC domain and downstream in Cisco IOS Release 12.2(15)BC2, the ENTITY-MIB no longer associates upstreams and downstreams with specific MAC domains, but instead shows all of them as being children of the line card. The entityPhysicalParentRelPos also now numbers the upstreams in sequential order, followed by the downstreams, so that on the Cisco uBR-MC5X20S cards, the upstreams are numbered from 0 to 19, and the downstreams from 20 to 24.

Figure 2 shows the difference in how the entPhysicalTable in the ENTITY-MIB organized a Cisco uBR-MC5X20S cable interface line card in previous releases and in Cisco IOS Release 12.2(15)BC2. For consistency, all cable interface line cards use this approach, even if they do not support the Virtual Interfaces feature.

Figure 2 ENTITY-MIB Changes for Virtual Interface Support on Cable Interface Line Cards

The following are the key points in how the ENTITY-MIB shows the physical relationship of objects when the Virtual Interfaces feature is configured:

•The entPhysicalTable shows information only about the physical card and its connectors. This table's configuration is fixed when the router boots or when a new card is installed in the chassis, and this configuration is not updated to show any logical/virtual mappings.

The entPhysicalTable index numbers for the card and its ports never change unless the card is physically removed and another type of card is installed in its slot. For example, if the entPhysicalName.50 object returns a value of "Cable6/1-US0" after the router boots, it always returns this value, no matter how the card and its upstream ports are configured.

For example, the Cisco uBR-MC5X20S and Cisco uBR-MC5X20U cards contain 20 upstreams, which the entPhysicalTable numbers from 0 to 19, regardless of how the upstreams are mapped using Virtual Interfaces. Similarly, the entPhysicalParentRelPos objects number the 20 upstreams as children 0 through 19, and the 5 downstreams as children 20 through 24. This numbering never changes, regardless of the Virtual Interfaces configuration.

•The mapping between the physical upstream connectors and the virtual upstream interfaces is shown in the entityAliasMappingTable. Each entry in this table contains the ifDescr index (as defined in the ifTable in the IF-MIB) that maps to the physical connector that is being used for that interface. The Virtual Interfaces feature automatically updates the entityAliasMappingTable to show the mapping between the physical upstream connectors and the virtual interfaces, whenever the cable upstream connector is used.

For more information on using SNMP to monitor virtual interfaces, see the "Using SNMP Commands" section.

Benefits

The Virtual Interfaces feature provides the following benefits to cable service providers and their partners and customers:

•Simplifies the installation of the Cisco uBR-MC5X20S/U cable interface line card when it replaces an existing cable card. The Cisco uBR-MC5X20S/U card can be initially configured to match the downstream and upstream configuration of the existing card, and then the service providers can modify that configuration in response to their customers' needs.

•Allows service providers to configure their MAC domains according to a particular class of service, so that downstreams and upstreams are grouped together by application (such as commercial services, residential customers, and so forth).

•Allows service providers to add the Cisco uBR-MC5X20S/U card to existing cable networks with minimal installation time and costs by allowing existing configurations to be adapted to the new card. For example, if a provider is currently using Cisco uBR-MC16C cards, the existing configurations can be easily adapted to the Cisco uBR-MC5X20S/U card by configuring the card to have three MAC domains of one downstream and 6 upstreams.

•Allows service providers to use configurable MAC domains, so that they can respond to customer demands and usage in a more flexible and dynamic manner. If more capacity is required in one MAC domain, it can be provided by reconfiguring the Cisco uBR-MC5X20S/U card, as opposed to creating a new MAC domain by installing new cable cards.

•The Virtual Interfaces feature can be combined with the CMTS Load Balancing feature to provide load balancing for the configurable MAC domains.

How to Configure the Virtual Interfaces Feature

This section describes the following tasks that are required to implement the Virtual Interfaces feature:

•Mapping Upstreams to a Downstream Port

•Removing the Mapping from an Upstream

Mapping Upstreams to a Downstream Port

This section describes how to configure the maximum number of upstreams on a Cisco uBR-MC5X20S/U cable interface line card, and then to map one or more upstreams to a particular downstream port on the card.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable cx/y/z

4. cable upstream max-ports n

5. cable upstream u connector n

6. exit

7. exit

DETAILED STEPS

Note The following procedure assumes that upstream ports have not been changed from the default configuration. If you have already mapped an upstream port to a virtual interface, you must first cancel that assignment, using the no version of the cable upstream connector command, before proceeding with the new assignment.

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Router#

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Router(config)#

Enters global configuration mode.

Step 3 

interface cable cx/y/z

Example:

Router(config)# interface cable 5/1/0

Router(config-if)#

Enters interface configuration mode for the specified cable interface (MAC domain).

•x = card slot number (can range from 5 to 8)

•y = card subslot number (can be 0 or 1)

•z = downstream number (can range from 0 to 5)

Step 4 

cable upstream max-ports n

Example:

Router(config-if)# cable upstream max-ports 6

Router(config-if)#

Specifies the maximum number of upstream ports that should be supported on each MAC domain. The valid range is 1 to 8, with a default of 4.

Step 5 

cable upstream u connector n

Example:

Router(config-if)# cable upstream 0 connector 4

Router(config-if)# cable upstream 1 connector 5

Router(config-if)# cable upstream 2 connector 6

Router(config-if)# cable upstream 3 connector 7

Router(config-if)# cable upstream 4 connector 8

Router(config-if)# cable upstream 5 connector 9

Router(config-if)#

Maps the virtual upstream channel u for this downstream to the physical port n. The valid range for u is 0 to one less than the max-ports value. The valid range for n is 0 to 19.

Note Repeat this command for each virtual upstream channel to be configured.

Step 6 

exit

Example:

Router(config-if)# exit

Router(config)#

Exits interface configuration mode.

Step 7 

exit

Example:

Router(config)# exit

Router#

Exits global configuration mode.

Removing the Mapping from an Upstream

This section describes how to remove the virtual interface mapping for one or more upstreams on the Cisco uBR-MC5X20S cable interface line card.

Caution Removing the mapping from an upstream port also shuts down the port. The upstream port must be remapped to another physical port before it can come online again.

SUMMARY STEPS

1. enable

2. configure terminal

3. no snmp-server ifindex persist

4. interface cable cable x/y/z

5. cable upstream max-ports 4

6. no cable upstream u connector n

7. end

8. copy running-config startup-config

9. reload

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Router#

Enables privileged EXEC mode. Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Router(config)#

Enters global configuration mode.

Step 3 

no snmp-server ifindex persist

Example:

Router(config)# no snmp-server ifindex persist

Router(config)#

(Required for Cisco IOS Release 12.2(15)BC1, optional for later releases) Removes the persistence of ifIndex values across reloads of the router.

Note After you reload the router with the new configuration, you can reenable the ifIndex persistence.

Step 4 

interface cable cx/y/z

Example:

Router(config)# interface cable 5/1/0

Router(config-if)#

Enters interface configuration mode for the specified cable interface (MAC domain).

•x = card slot number (can range from 5 to 8)

•y = card subslot number (can be 0 or 1)

•z = downstream number (can range from 0 to 5)

Step 5 

cable upstream max-ports 4

Example:

Router(config-if)# cable upstream max-ports 4

Router(config-if)#

Resets the interface to its default configuration of 4 upstream ports per downstream.

Step 6 

no cable upstream u connector n

Example:

Router(config-if)# no cable upstream 0 connector 4

Router(config-if)# no cable upstream 1 connector 6

Router(config-if)#

Removes the mapping for the virtual upstream channel u to the physical port n, and resets the upstream to its default value. The valid range for u is 0 to one less than the max-ports value. The valid range for n is 0 to 19.

Note Repeat this command for each virtual upstream channel that should be unconfigured.

Step 7 

end

Example:

Router(config-if)# exit

Router#

Exits interface configuration mode and returns to privileged EXEC mode.

Step 8 

copy running-config startup-config

Example:

Router# copy running-config startup-config

Router#

Saves the new configuration in the NVRAM memory.

Step 9 

reload

Example:

Router# reload

Reloads the router and installs the new configuration.

Monitoring the Virtual Interfaces Feature

This section provides the following sections on how you can monitor the operation of the Virtual Interfaces feature, using either command-line interface (CLI) commands or Simple Network Management Protocol (SNMP) commands:

•Using the Command-Line Interface

•Using SNMP Commands

Using the Command-Line Interface

In Cisco IOS Release 12.2(15)BC1 and later releases, the show controller cable upstream command now includes a line that shows whether the upstream has been mapped to a physical port. 

Router# show controller cable 8/0/2 u3 

 Cable8/0/2 Upstream 3 is up

  Frequency 10.000 MHz, Channel Width 1.600 MHz, 16-QAM Symbol Rate 1.280 Msps

  This upstream is mapped to physical port 16 

  Spectrum Group is overridden

  US phy SNR_estimate for good packets - 30.5581 dB

  Nominal Input Power Level 0 dBmV, Tx Timing Offset 2983

  Ranging Backoff automatic (Start 0, End 3)

  Ranging Insertion Interval automatic (60 ms)

  Tx Backoff Start 0, Tx Backoff End 4

  Modulation Profile Group 3

  Concatenation is enabled

  Fragmentation is enabled

  part_id=0x0952, rev_id=0x00, rev2_id=0x00

  nb_agc_thr=0x0000, nb_agc_nom=0x0000

  Range Load Reg Size=0x2C

  Request Load Reg Size=0x07

  Minislot Size in number of Timebase Ticks is = 4

  Minislot Size in Symbols = 32

  Bandwidth Requests = 0x169C2

  Piggyback Requests = 0x27A

  Invalid BW Requests= 0x0

  Minislots Requested= 0xA251A

  Minislots Granted  = 0xA2513

Using SNMP Commands

To monitor virtual interfaces using SNMP commands, use the following procedure. This procedure uses the example of a Cisco uBR-MC5X20S card that is installed in slot 8/1 in a Cisco uBR10012 router. The exact index numbers that are used depends on the number and type of other cards that are installed in the chassis.

Step 1 Walk the ENTITY-MIB to collect the index numbers in the entPhysicalTable that refer to the physical connectors for the upstreams on the card that is using the Virtual Interfaces feature. The most convenient object to use for this is entPhysicalName, which specifies both the card's slot number and the connector's number. For example: 

entPhysicalName.81 = Cable8/1-US0 

entPhysicalName.82 = Cable8/1-US1 

entPhysicalName.83 = Cable8/1-US2 

entPhysicalName.84 = Cable8/1-US3 

entPhysicalName.85 = Cable8/1-US4 

entPhysicalName.86 = Cable8/1-US5 

entPhysicalName.87 = Cable8/1-US6 

entPhysicalName.88 = Cable8/1-US7 

entPhysicalName.89 = Cable8/1-US8 

entPhysicalName.90 = Cable8/1-US9 

entPhysicalName.91 = Cable8/1-US10 

entPhysicalName.92 = Cable8/1-US11 

entPhysicalName.93 = Cable8/1-US12 

entPhysicalName.94 = Cable8/1-US13 

entPhysicalName.95 = Cable8/1-US14 

entPhysicalName.96 = Cable8/1-US15 

entPhysicalName.97 = Cable8/1-US16 

entPhysicalName.98 = Cable8/1-US17 

entPhysicalName.99 = Cable8/1-US18 

entPhysicalName.100 = Cable8/1-US19

In this example, the entPhysicalTable uses index numbers 81 through 99 to refer to the physical connectors for the upstreams on the card that is installed in slot 8/1.

Note The index numbers shown in entPhysicalTable never change during normal operation of the router. This index numbering is guaranteed to remain the same until you either reboot the router or until you change the router's physical configuration by adding or removing hardware components.

Step 2 Using the index numbers for the upstream connectors, retrieve the corresponding rows in the entAliasMappingIdentifierTable. This returns the ifIndex value for the virtual upstream interface that is using each physical upstream connector. For example: 

entAliasMappingIdentifier.81.0 = ifIndex.28 

entAliasMappingIdentifier.82.0 = ifIndex.29 

entAliasMappingIdentifier.83.0 = ifIndex.30 

entAliasMappingIdentifier.84.0 = ifIndex.31 

entAliasMappingIdentifier.85.0 = ifIndex.33 

entAliasMappingIdentifier.86.0 = ifIndex.34 

entAliasMappingIdentifier.87.0 = ifIndex.35 

entAliasMappingIdentifier.88.0 = ifIndex.36 

entAliasMappingIdentifier.89.0 = ifIndex.38 

entAliasMappingIdentifier.90.0 = ifIndex.39 

entAliasMappingIdentifier.91.0 = ifIndex.40 

entAliasMappingIdentifier.92.0 = ifIndex.41 

entAliasMappingIdentifier.93.0 = ifIndex.43 

entAliasMappingIdentifier.94.0 = ifIndex.44 

entAliasMappingIdentifier.95.0 = ifIndex.45 

entAliasMappingIdentifier.96.0 = ifIndex.46 

entAliasMappingIdentifier.97.0 = ifIndex.48 

entAliasMappingIdentifier.98.0 = ifIndex.49 

entAliasMappingIdentifier.99.0 = ifIndex.50 

entAliasMappingIdentifier.100.0 = ifIndex.51

Note If an entAliasMappingIdentifier entry does not contain an ifIndex, it indicates that this particular physical upstream connector is not currently mapped to a virtual upstream interface.

Step 3 Using the ifIndex numbers retrieved from Step 2, retrieve the corresponding ifDescr entries to obtain the description for each virtual upstream interface that is mapped to each physical upstream connector. Using the above example, the connector mappings resolve to the following: 

entAliasMappingIdentifier.81.0 = ifIndex.28 (ifDescr.28 = Cable8/1/0-upstream0) 

entAliasMappingIdentifier.82.0 = ifIndex.29 (ifDescr.29 = Cable8/1/0-upstream1)

entAliasMappingIdentifier.83.0 = ifIndex.30 (ifDescr.30 = Cable8/1/0-upstream2) 

entAliasMappingIdentifier.84.0 = ifIndex.31 (ifDescr.31 = Cable8/1/0-upstream3)

entAliasMappingIdentifier.85.0 = ifIndex.33 (ifDescr.33 = Cable8/1/1-upstream0) 

entAliasMappingIdentifier.86.0 = ifIndex.34 (ifDescr.34 = Cable8/1/1-upstream1) 

entAliasMappingIdentifier.87.0 = ifIndex.35 (ifDescr.35 = Cable8/1/1-upstream2) 

entAliasMappingIdentifier.88.0 = ifIndex.36 (ifDescr.36 = Cable8/1/1-upstream3)  

entAliasMappingIdentifier.89.0 = ifIndex.38 (ifDescr.38 = Cable8/1/2-upstream0) 

entAliasMappingIdentifier.90.0 = ifIndex.39 (ifDescr.39 = Cable8/1/2-upstream1) 

entAliasMappingIdentifier.91.0 = ifIndex.40 (ifDescr.40 = Cable8/1/2-upstream2) 

entAliasMappingIdentifier.92.0 = ifIndex.41 (ifDescr.41 = Cable8/1/2-upstream3) 

entAliasMappingIdentifier.93.0 = ifIndex.43 (ifDescr.43 = Cable8/1/3-upstream0) 

entAliasMappingIdentifier.94.0 = ifIndex.44 (ifDescr.44 = Cable8/1/3-upstream1) 

entAliasMappingIdentifier.95.0 = ifIndex.45 (ifDescr.45 = Cable8/1/3-upstream2) 

entAliasMappingIdentifier.96.0 = ifIndex.46 (ifDescr.46 = Cable8/1/3-upstream3) 

entAliasMappingIdentifier.97.0 = ifIndex.48 (ifDescr.48 = Cable8/1/4-upstream0) 

entAliasMappingIdentifier.98.0 = ifIndex.49 (ifDescr.49 = Cable8/1/4-upstream1) 

entAliasMappingIdentifier.99.0 = ifIndex.50 (ifDescr.50 = Cable8/1/4-upstream2) 

entAliasMappingIdentifier.100.0 = ifIndex.51 (ifDescr.51 = Cable8/1/4-upstream3)


Step 4 (Optional) Whenever you use the cable upstream connector command to configure the Virtual Interfaces feature, retrieve the corresponding entAliasMappingIdentifier rows to obtain the new port mappings. In the above example, upstream 2 on C8/1/4 is mapped to physical upstream connector 18 (entPhysicalTable index 99), and the ENTITY-MIB shows the following for these two upstreams: 

entPhysicalName.81 = Cable8/1-US0 

entPhysicalName.99 = Cable8/1-US18 

entAliasMappingIdentifier.81 = ifIndex.28 (ifDescr.28 = Cable8/1/0-upstream0) 

entAliasMappingIdentifier.99 = ifIndex.50 (ifDescr.50 = Cable8/1/4-upstream2) 


This port can be mapped to physical upstream connector 0 (entPhysicalTable index 81) with the 
following commands:

Router(config)# interface cable 8/1/4 

Router(config-if)# cable upstream 2 connector 0 

Router(config-if)#

After the cable upstream connector command is used, the ENTITY-MIB is updated as follows. (Note that only the entAliasMappingIdentifier objects have changed.) 

entPhysicalName.81 = Cable8/1-US0 

entPhysicalName.99 = Cable8/1-US18 

entAliasMappingIdentifier.81 = ifIndex.50 (ifDescr.50 = Cable8/1/4-upstream2) 

entAliasMappingIdentifier.99 =

The above example shows that physical connector upstream 0 is now mapped to the virtual interface upstream 2 on Cable 8/1/4, and that physical connector upstream 18 is no longer in use. Its entAliasMappingIdentifier will return NULL until the cable upstream connector command maps another virtual upstream to this particular physical connector.

Configuration Examples for Virtual Interfaces

This section lists sample configurations for the Virtual Interfaces feature on a Cisco uBR-MC5X20S cable interface line card.

•1x4 Configuration

•1x6 Configuration

•1x8 Configuration

1x4 Configuration

The following sample configuration shows a typical configuration for mapping 4 upstreams to the fifth downstream on a Cisco uBR-MC5X20S/U cable interface card. The relevant lines for the virtual interface mapping are shown in bold.

Note The cable upstream max-ports command is not needed because the default for this command is 4. 

interface Cable8/0/4

 ip address 10.10.84.1 255.255.255.0

 cable downstream annex B

 cable downstream modulation 64qam

 cable downstream interleave-depth 32

 cable downstream frequency 459000000

 cable downstream channel-id 0

 no cable downstream rf-shutdown

 cable upstream 0 connector 16 

 cable upstream 0 frequency 15008000

 cable upstream 0 power-level 0

 no cable upstream 0 shutdown

 cable upstream 1 connector 17 

 cable upstream 1 frequency 20000000

 cable upstream 1 power-level 0

 no cable upstream 1 shutdown

 cable upstream 2 connector 18 

 cable upstream 2 frequency 15008000

 cable upstream 2 power-level 0

 no cable upstream 2 shutdown

 cable upstream 3 connector 12 

 cable upstream 3 frequency 25008000

 cable upstream 3 power-level 0

 no cable upstream 3 shutdown

1x6 Configuration

The following sample configuration shows a typical configuration for mapping 6 upstreams to the second downstream on the Cisco uBR-MC5X20S/U cable interface card. The relevant lines for the virtual interface mapping are shown in bold. 

!

interface Cable8/0/1 

 ip address 10.10.71.1 255.255.255.0

 ip helper-address 10.10.71.1

 no keepalive

 cable downstream annex B

 cable downstream modulation 64qam

 cable downstream interleave-depth 32

 cable downstream frequency 123000000

 cable downstream channel-id 0

 no cable downstream rf-shutdown

 cable upstream max-ports 6 

 cable upstream 0 connector 0 

 cable upstream 0 frequency 19008000

 cable upstream 0 power-level 0

 no cable upstream 0 shutdown

 cable upstream 1 connector 1 

 cable upstream 1 frequency 20000000

 cable upstream 1 power-level 0

 no cable upstream 1 shutdown

 cable upstream 2 connector 2 

 cable upstream 2 frequency 21008000

 cable upstream 2 power-level 0

 no cable upstream 2 shutdown

 cable upstream 3 connector 3 

 cable upstream 3 frequency 22000000

 cable upstream 3 power-level 0

 no cable upstream 3 shutdown

 cable upstream 4 connector 4 

 cable upstream 4 frequency 23008000

 cable upstream 4 power-level 0 

 no cable upstream 4 shutdown 

 cable upstream 5 connector 5 

 cable upstream 5 frequency 26000000

 cable upstream 5 power-level 0

 no cable upstream 5 shutdown

1x8 Configuration

The following sample configuration shows a typical configuration for mapping 8 upstreams to the third downstream on the Cisco uBR-MC5X20S/U cable interface card. The relevant lines for the virtual interface mapping are shown in bold. 

!

interface Cable8/0/2

 ip address 10.10.82.1 255.255.255.0

 no keepalive

 cable downstream annex B

 cable downstream modulation 64qam

 cable downstream interleave-depth 32

 cable downstream frequency 465000000

 cable downstream channel-id 0

 no cable downstream rf-shutdown

 cable upstream max-ports 8 

 cable upstream 0 connector 15 

 cable upstream 0 frequency 15008000

 cable upstream 0 power-level 0

 cable upstream 0 channel-width 200000

 cable upstream 0 minislot-size 64

 cable upstream 0 modulation-profile 2 

 no cable upstream 0 shutdown 

 cable upstream 1 connector 14 

 cable upstream 1 frequency 20000000

 cable upstream 1 power-level 0

 cable upstream 1 channel-width 400000

 cable upstream 1 minislot-size 32

 cable upstream 1 modulation-profile 3

 no cable upstream 1 shutdown

 cable upstream 2 connector 13 

 cable upstream 2 frequency 25008000

 cable upstream 2 power-level 0

 cable upstream 2 channel-width 800000

 cable upstream 2 minislot-size 16

 cable upstream 2 modulation-profile 3

 no cable upstream 2 shutdown

 cable upstream 3 connector 12 

 cable upstream 3 frequency 10000000

 cable upstream 3 power-level 0

 cable upstream 3 modulation-profile 3

 no cable upstream 3 shutdown

 cable upstream 4 connector 11 

 cable upstream 4 frequency 7504000

 cable upstream 4 power-level 0

 cable upstream 4 channel-width 3200000

 cable upstream 4 modulation-profile 3

 no cable upstream 4 shutdown

 cable upstream 5 connector 10 

 cable upstream 5 frequency 10496000

 cable upstream 5 power-level 0

 cable upstream 5 channel-width 200000

 cable upstream 5 minislot-size 64

 cable upstream 5 modulation-profile 3

 no cable upstream 5 shutdown

 cable upstream 6 connector 9 

 cable upstream 6 frequency 15008000

 cable upstream 6 power-level 0

 cable upstream 6 channel-width 400000

 cable upstream 6 minislot-size 32

 cable upstream 6 modulation-profile 2

 no cable upstream 6 shutdown

 cable upstream 7 connector 8 

 cable upstream 7 frequency 28000000

 cable upstream 7 power-level 0

 cable upstream 7 channel-width 3200000

 cable upstream 7 modulation-profile 2

 no cable upstream 7 shutdown

 cable privacy kek life-time 300

 cable privacy tek life-time 180

Additional References

For additional information related to Virtual Interfaces, refer to the following references:

Related Documents

Related Topic
Document Title

CMTS Command Reference

Cisco Broadband Cable Command Reference Guide, at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

Cisco IOS Release 12.2 Command Reference

Cisco IOS Release 12.2 Configuration Guides and Command References, at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/index.htm


Standards

Standards1
Title

SP-RFIv1.1-I09-020830

Data-over-Cable Service Interface Specifications Radio Frequency Interface Specification, version 1.1

1 Not all supported standards are listed.


MIBs

MIBs1
MIBs Link

No new or modified MIB objects are supported by the Virtual Interfaces feature.

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

1 Not all supported MIBs are listed.


RFCs


Technical Assistance

Description
Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

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


Command Reference

This section documents the following new or modified commands that are needed to document the Virtual Interfaces feature.

•cable upstream connector

•cable upstream max-ports

Note Other cable-specific commands are documented in the
Cisco Broadband Cable Command Reference Guide, at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.

cable upstream connector

To map an upstream port to a physical port on the Cisco uBR-MC5X20S/U cable interface line card for use with a particular downstream, use the cable upstream connector command in cable interface configuration mode. To remove the mapping and shut down the upstream port, use the no form of this command.

cable upstream virtual-port connector physical-port

no cable upstream virtual-port connector physical-port

Syntax Description

virtual-port

Specifies the upstream port number for the virtual channel assignment. The number of virtual channels is configured with the cable upstream max-ports command, and the valid range is from 0 to one less than the current value set with the cable upstream max-ports command.

Tip The default value for max-ports command is 4, which means the default range for virtual-port is 0 to 3.

physical-port

Specifies the upstream port number for the actual physical port to be assigned. The valid range is 0 to 19, with no default.


Defaults

By default, the Cisco uBR-MC5X20S/U cable interface line card uses a fixed configuration, in which each downstream is allocated four upstream ports.

Command Modes

Interface configuration (cable interface only)

Command History

Release
Modification

12.2(15)BC1

This command was introduced to support the Cisco uBR-MC5X20S cable interface line card.

12.2(15)BC2

Support was added for the Cisco uBR-MC5X20U card. Also, the entAliasMappingTable in the ENTITY-MIB was updated to show the mapping between the physical upstream connectors and the virtual upstream channels.


Usage Guidelines

The cable upstream connector command changes the default assignment of upstream ports to MAC domains on the Cisco uBR-MC5X20S/U card. This command creates a virtual upstream for a downstream and assigns it to a particular physical port.

The default port mapping assigns four upstream ports to each of the downstream ports (MAC domains). The ports are assigned sequentially, in the order in which they appear on the card's front panel.

The no version of this command removes the upstream port mapping and shuts down the upstream port. The port must be remapped to another physical port before it can come online again.

Tip Use the cable upstream max-ports command to set the maximum number of upstream ports per downstream before using the cable upstream connector command.

Table 4 shows the default port mapping.