Table of Contents
Advertisement
cable bundle
•
•
•
Specify generic (that is, not downstream or upstream) cable interface configurations, such as source-
verify or Address Resolution Protocol (ARP) handling, on the master interface. Do not specify generic
configuration on nonmaster interfaces.
If you configure an interface as part of a bundle and it is not the master interface, all generic cable
configuration for this interface is removed. This includes the IP address, access groups, PIM
configuration, and any other IP Layer 3 configurations. The master interface configuration then applies
to all interfaces in the bundle.
We recommend configuring the no ip address command on all slave interfaces. This command is
Tip
optional but recommended, because the show ip interface brief command reports an interface as being
not OK if its configuration does not include some form of the ip address command. Specifying no ip
address corrects this.
When creating subinterfaces over the bundle master, the bundle master is not assigned any IP address
and only the subinterfaces are assigned IP addresses, helper addresses, and other Layer 3 configurations.
The reason the bundle master is not assigned an IP address is because CMs are associated with
subinterfaces rather than with a bundle master.
Cable interface bundling is applicable only in two-way cable configurations. It is not supported in telco-
Note
return configurations.
If you shut down or remove the master interface in a bundle, no data packets is sent to any of the
interfaces in this bundle. Packets are still physically received from nonmaster interfaces that have not
been shut down, but those packets are discarded. This means that CMs connected to those interfaces are
not disconnected immediately, but CMs coming online are not able to obtain an IP address, download
their configuration file, or renew their IP address assignment if the DHCP lease expires.
If you shut down a slave interface, only this shutdown interface is affected.
When using bundled interfaces, the show interface cable command divides the interface counters
Note
between the master and slave interfaces. The output for the master interface shows the upstream packets
per second count, while the output for the slave interfaces shows the downstream packets per second
count.
Examples
See the following example to configure interface 25 to be the master interface:
Router(config)# interface cable 3/0
Router(config-if)# cable bundle 25 master
Router(config-if)#
07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down
Cisco Broadband Cable Command Reference Guide
2-20
If you attempt to add an interface to a bundle as slave interface and an IP address is assigned to this
interface, the command fails. You must remove the IP address configuration before you can add the
interface to a bundle.
If you have configured an IP address on a bundled interface and the interface is not the master
interface, a warning message appears.
Do not create subinterfaces on a slave interface. In Cisco IOS Release 12.2(15)BC2 and later
releases, this is specifically prohibited. In prior releases, a warning message appeared when trying
to create a subinterface on a slave interface, but the subinterface was still created.
Chapter 2
Cisco CMTS Configuration Commands
OL-1581-08
Advertisement
Table of Contents
