The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Bridge Control Protocol (BCP) Support feature provides support for BCP to Cisco devices, as described in RFC 3518. The Cisco implementation of BCP is a VLAN infrastructure that does not require the use of subinterfaces to group Ethernet 802.1Q trunks and the corresponding PPP links. This approach enables users to process VLAN encapsulated packets without having to configure subinterfaces for every possible VLAN configuration.
Feature History for the BCP Support feature
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.
•Information About BCP Support
•How to Bridge a Range of VLAN IDs
•Configuration Examples for BCP Support
Each individual VLAN ID can be configured only once, as either part of a single VLAN ID range or on a subinterface.
To configure the BCP Support feature, you must understand the following concept:
In the traditional, subinterface-based approach to VLANs, a subinterface is created for every necessary VLAN ID, and then the application or protocol attributes are configured on every subinterface. In the VLAN range approach, a single VLAN ID range is created, and the application or protocol attributes are configured on the range as a whole.
This section contains the following procedures:
•Configuring a Range of VLAN IDs
•Enabling the Negotiation of IEEE 802.1Q-Tagged Packets
In this task, you create a range of VLAN IDs and then assign the VLAN ID range to the serial interface.
1. enable
2. configure terminal
3. no ip routing
4. bridge number protocol ieee
5. interface type number
6. vlan-range dot1q start-range end-range [native]
7. description description
8. bridge-group number
9. exit
10. interface type number
11. encapsulation ppp
12. bridge-group number
In this task, you enable the negotiation of IEEE 802.1Q-tagged packets.
1. enable
2. configure terminal
3. interface type number
4. ppp bcp tagged-frame
This section provides the following configuration examples:
•Bridging a Range of VLAN IDs: Example
•Bridging a Range of VLAN IDs over Multiple Interfaces: Example
•Bridging a Range of VLAN IDs from Untagged Packets: Example
•Enabling the Negotiation of IEEE 802.1Q-Tagged Packets: Example
The following example bridges tagged 802.1Q packets that have VLAN IDs from 1 to 500. Ingress packets that have VLAN IDs outside of this range are dropped.
no ip routing
!
bridge 1 protocol ieee
!
interface ethernet 0
vlan-range dot1q 1 500
bridge-group 1
!
interface serial 0
encapsulation ppp
bridge-group 1
The following example bridges two ranges of VLAN IDs. Packets with a VLAN ID from 1 to 600 are bridged by serial interface 0, and packets with a VLAN ID from 800 to 4000 are bridged by serial interface 1.
no ip routing
!
bridge 1 protocol ieee
bridge 2 protocol ieee
!
interface ethernet 0
vlan-range dot1q 1 600
bridge-group 1
vlan-range dot1q 800 4000
bridge-group 2
!
interface serial 0
encapsulation ppp
bridge-group 1
!
interface serial 1
encapsulation ppp
bridge-group 2
The following example bridges untagged packets with a VLAN ID from 1 to 500:
interface ethernet 0
vlan-range dot1q 1 500 native
bridge-group 1
The following example enables the negotiation of IEEE 802.1Q-tagged packets on serial interface 4/0:
interface serial 4/0
ppp bcp tagged-frame
The following sections provide references related to BCP support:
|
|
---|---|
3518 |
Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) |
2878 |
Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) |
1638 |
PPP Bridging Control Protocol (BCP) |
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Bridging Command Reference at http://www.cisco.com/en/US/docs/ios/bridging/command/reference/br_book.html or the Cisco IOS IBM Networking Command Reference at http://www.cisco.com/en/US/docs/ios/ibm/command/reference/ibm_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
New Commands
•debug tbridge virtual-port
•ppp bcp tagged-frame
•vlan-id dot1q
•vlan-range dot1q