Downloads |
 Feedback
|
Table Of Contents
Implementing Multiprotocol BGP for IPv6
Information About Implementing Multiprotocol BGP for IPv6
Multiprotocol BGP Extensions for IPv6
Multiprotocol BGP for the IPv6 Multicast Address Family
Nonstop Forwarding and Graceful Restart for MP-BGP IPv6 Address Family
How to Implement Multiprotocol BGP for IPv6
Configuring an IPv6 BGP Routing Process and BGP Router ID
Configuring IPv6 Multiprotocol BGP Between Two IPv6 Peers
Configuring IPv6 Multiprotocol BGP Between Two Peers Using Link-Local Addresses
Configuring an IPv6 Multiprotocol BGP Peer Group
Advertising IPv4 Routes Between IPv6 BGP Peers
Assigning BGP Administrative Distance for Multicast BGP Routes
Generating IPv6 Multicast BGP Updates
Configuring the IPv6 BGP Graceful Restart Capability
Clearing IPv6 BGP Route Dampening Information
Clearing IPv6 BGP Flap Statistics
Verifying IPv6 Multiprotocol BGP Configuration and Operation
Sample Output from the show bgp ipv6 Command
Sample Output from the show bgp ipv6 summary Command
Sample Output from the show bgp ipv6 dampened-paths Command
Sample Output from the debug bgp ipv6 dampening Command
Sample Output from the debug bgp ipv6 updates Command
Configuration Examples for Multiprotocol BGP for IPv6
Example: Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer
Example: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
Example: Configuring an IPv6 Multiprotocol BGP Peer Group
Example: Advertising IPv4 Routes Between IPv6 Peers
Feature Information for Implementing Multiprotocol BGP
for IPv6
Implementing Multiprotocol BGP for IPv6
First Published: May 5, 2008Last Updated: July 30, 2010This module describes how to configure multiprotocol Border Gateway Protocol (BGP) for IPv6. BGP is an Exterior Gateway Protocol (EGP) used mainly to connect separate routing domains that contain independent routing policies (autonomous systems). Connecting to a service provider for access to the Internet is a common use for BGP. BGP can also be used within an autonomous system and this variation is referred to as internal BGP (iBGP). Multiprotocol BGP is an enhanced BGP that carries routing information for multiple network layer protocol address families, for example, IPv6 address family and for IP multicast routes. All BGP commands and routing policy capabilities can be used with multiprotocol BGP.
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. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Implementing Multiprotocol BGP for IPv6" section.
Use Cisco Feature Navigator to find information about platform support and Cisco 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
•
Information About Implementing Multiprotocol BGP for IPv6
•
•
•
Information About Implementing Multiprotocol BGP for IPv6
•
•
Multiprotocol BGP Extensions for IPv6
Multiprotocol BGP is the supported EGP for IPv6. Multiprotocol BGP extensions for IPv6 supports the same features and functionality as IPv4 BGP. IPv6 enhancements to multiprotocol BGP include support for an IPv6 address family and network layer reachability information (NLRI) and next hop (the next router in the path to the destination) attributes that use IPv6 addresses.
Multiprotocol BGP for the IPv6 Multicast Address Family
The multiprotocol BGP for the IPv6 multicast address family feature provides multicast BGP extensions for IPv6 and supports the same features and functionality as IPv4 BGP. IPv6 enhancements to multicast BGP include support for an IPv6 multicast address family and network layer reachability information (NLRI) and next hop (the next router in the path to the destination) attributes that use IPv6 addresses.
Multicast BGP is an enhanced BGP that allows the deployment of interdomain IPv6 multicast. Multiprotocol BGP carries routing information for multiple network layer protocol address families; for example, IPv6 address family and for IPv6 multicast routes. The IPv6 multicast address family contains routes used for RPF lookup by the IPv6 PIM protocol, and multicast BGP IPV6 provides for inter- domain transport of the same. Users must use multiprotocol BGP for IPv6 multicast when using IPv6 multicast with BGP because the unicast BGP learned routes will not be used for IPv6 multicast.
Multicast BGP functionality is provided through a separate address family context. A subsequent address family identifier (SAFI) provides information about the type of the network layer reachability information that is carried in the attribute. Multiprotocol BGP unicast uses SAFI 1 messages, and multiprotocol BGP multicast uses SAFI 2 messages. SAFI 1 messages indicate that the routes are only usable for IP unicast, but not IP multicast. Because of this functionality, BGP routes in the IPv6 unicast RIB must be ignored in the IPv6 multicast RPF lookup.
A separate BGP routing table is maintained to configure incongruent policies and topologies (for example, IPv6 unicast and multicast) by using IPv6 multicast RPF lookup. Multicast RPF lookup is very similar to the IP unicast route lookup.
No MRIB is associated with the IPv6 multicast BGP table. However, IPv6 multicast BGP operates on the unicast IPv6 RIB when needed. Multicast BGP does not insert or update routes into the IPv6 unicast RIB.
Nonstop Forwarding and Graceful Restart for MP-BGP IPv6 Address Family
The graceful restart capability is supported for IPv6 BGP unicast, multicast, and VPNv6 address families, enabling Cisco nonstop forwarding (NSF) functionality for BGP IPv6. The BGP graceful restart capability allows the BGP routing table to be recovered from peers without keeping the TCP state.
NSF continues forwarding packets while routing protocols converge, therefore avoiding a route flap on switchover. Forwarding is maintained by synchronizing the FIB between the active and standby RP. On switchover, forwarding is maintained using the FIB. The RIB is not kept synchronized; therefore, the RIB is empty on switchover. The RIB is repopulated by the routing protocols and subsequently informs FIB about RIB convergence by using the NSF_RIB_CONVERGED registry call. The FIB tables are updated from the RIB, removing any stale entries. The RIB starts a failsafe timer during RP switchover, in case the routing protocols fail to notify the RIB of convergence.
The Cisco BGP address family identifier (AFI) model is designed to be modular and scalable, and to support multiple AFI and subsequent address family identifier (SAFI) configurations.
How to Implement Multiprotocol BGP for IPv6
When configuring multiprotocol BGP extensions for IPv6, you must create the BGP routing process, configure peering relationships, and customize BGP for your particular network.
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuring an IPv6 BGP Routing Process and BGP Router ID
BGP uses a router ID to identify BGP-speaking peers. The BGP router ID is 32-bit value that is often represented by an IPv4 address. By default, the Cisco IOS XE software sets the router ID to the IPv4 address of a loopback interface on the router. If no loopback interface is configured on the router, then the software chooses the highest IPv4 address configured to a physical interface on the router to represent the BGP router ID. When configuring BGP on a router that is enabled only for IPv6 (the router does not have an IPv4 address), you must manually configure the BGP router ID for the router. The BGP router ID, which is represented as a 32-bit value using an IPv4 address syntax, must be unique to the BGP peers of the router.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring IPv6 Multiprotocol BGP Between Two IPv6 Peers
Restrictions
By default, neighbors that are defined using the neighbor remote-as command in router configuration mode exchange only IPv4 unicast address prefixes. To exchange other address prefix types, such as IPv6 prefixes, neighbors must also be activated using the neighbor activate command in address family configuration mode for the other prefix types, as shown for IPv6 prefixes.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring IPv6 Multiprotocol BGP Between Two Peers Using Link-Local Addresses
Configuring IPv6 multiprotocol BGP between two IPv6 routers (peers) using link-local addresses requires that the interface for the neighbor be identified by using the update-source command and that a route map be configured to set an IPv6 global next hop.
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
router bgp autonomous-system-number
Example:Router(config)# router bgp 65000
Enters router configuration mode for the specified routing process.
Step 4
neighbor {ip-address | ipv6-address | peer-group-name} remote-as as-number
Example:Router(config-router)# neighbor FE80::XXXX:BFF:FE0E:A471 remote-as 64600
Adds the link-local IPv6 address of the neighbor in the specified remote autonomous system to the IPv6 multiprotocol BGP neighbor table of the local router.
•
Step 5
neighbor {ip-address | ipv6-address | peer-group-name} update-source interface-type interface-number
Example:Router(config-router)# neighbor FE80::XXXX:BFF:FE0E:A471 update-source gigabitethernet0/0/0
Specifies the link-local address over which the peering is to occur.
•
Step 6
address-family ipv6 [vrf vrf-name] [unicast | multicast | vpnv6]
Example:Router(config-router)# address-family ipv6
Specifies the IPv6 address family, and enters address family configuration mode.
•
•
Step 7
neighbor {ip-address | peer-group-name | ipv6-address} activate
Example:Router(config-router-af)# neighbor FE80::XXXX:BFF:FE0E:A471 activate
Enables the neighbor to exchange prefixes for the IPv6 address family with the local router using the specified link-local addresses.
Step 8
neighbor {ip-address | peer-group-name | ipv6-address} route-map map-name {in | out}
Example:Router(config-router-af)# neighbor FE80::XXXX:BFF:FE0E:A471 route-map nh6 out
Applies a route map to incoming or outgoing routes.
Step 9
exit
Example:Router(config-router-af)# exit
Exits address family configuration mode, and returns the router to router configuration mode.
Step 10
Repeat Step 9.
Example:Router(config-router)# exit
Exits router configuration mode, and returns the router to global configuration mode.
Step 11
route-map map-tag [permit | deny] [sequence-number]
Example:Router(config)# route-map nh6 permit 10
Defines a route map and enters route-map configuration mode.
Step 12
match ipv6 address {prefix-list prefix-list-name | access-list-name}
Example:Router(config-route-map)# match ipv6 address prefix-list cisco
Distributes any routes that have a destination IPv6 network number address permitted by a prefix list, or performs policy routing on packets.
Step 13
set ipv6 next-hop ipv6-address [link-local-address] [peer-address]
Example:Router(config-route-map)# set ipv6 next-hop 2001:DB8::1
Overrides the next hop advertised to the peer for IPv6 packets that pass a match clause of a route map for policy routing.
•
•
Note
If you specify only the global IPv6 next-hop address (the ipv6-address argument) with the set ipv6 next-hop command after specifying the neighbor interface (the interface-type argument) with the neighbor update-source command in Step 5, the link-local address of the interface specified with the interface-type argument is included as the next-hop in the BGP updates. Therefore, only one route map that sets the global IPv6 next-hop address in BGP updates is required for multiple BGP peers that use link-local addresses.
Troubleshooting Tips
If peering is not established by this task, it may be because of a missing route map set ipv6 next-hop command. Use the debug bgp ipv6 update command to display debugging information on the updates to help determine the state of the peering.
Configuring an IPv6 Multiprotocol BGP Peer Group
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
Advertising IPv4 Routes Between IPv6 BGP Peers
If an IPv6 network is connecting two separate IPv4 networks, it is possible to use IPv6 to advertise the IPv4 routes. Configure the peering using the IPv6 addresses within the IPv4 address family. Set the next hop with a static route or with an inbound route map because the advertised next hop will usually be unreachable. Advertising IPv6 routes between two IPv4 peers is also possible using the same model.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Assigning BGP Administrative Distance for Multicast BGP Routes
Perform this task to specify an administrative distance for multicast BGP routes to be used in RPF lookups for comparison with unicast routes.
Caution
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Generating IPv6 Multicast BGP Updates
Perform this task to generate IPv6 multicast BGP updates that correspond to unicast IPv6 updates received from a peer.
The MBGP translate-update feature generally is used in an MBGP-capable router that peers with a customer site that has only a BGP-capable router; the customer site has not or cannot upgrade its router to an MBGP-capable image. Because the customer site cannot originate MBGP advertisements, the router with which it peers will translate the BGP prefixes into MBGP prefixes, which are used for multicast-source Reverse Path Forwarding (RPF) lookup.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the IPv6 BGP Graceful Restart Capability
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Resetting IPv6 BGP Sessions
SUMMARY STEPS
1.
2.
DETAILED STEPS
Clearing External BGP Peers
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Clearing IPv6 BGP Route Dampening Information
SUMMARY STEPS
1.
2.
DETAILED STEPS
Clearing IPv6 BGP Flap Statistics
SUMMARY STEPS
1.
2.
DETAILED STEPS
Verifying IPv6 Multiprotocol BGP Configuration and Operation
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
•
•
•
•
•
Sample Output from the show bgp ipv6 Command
In the following example, entries in the IPv6 BGP routing table are displayed using the show bgp ipv6 command:
Router> show bgp ipv6 unicastBGP table version is 12612, local router ID is 192.168.99.70Status codes: s suppressed, d damped, h history, * valid, > best, i - internalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 2001:DB8:E:C::2 0 3748 4697 1752 i* 2001:DB8:0:CC00::10 1849 1273 1752 i* 2001:618:3::/48 2001:DB8:E:4::2 1 0 4554 1849 65002 i*> 2001:DB8:0:CC00::10 1849 65002 i*> 2001:620::/35 2001:DB8:0:F004::10 3320 1275 559 i* 2001:DB8:E:9::2 0 1251 1930 559 i* 2001:DB8::A 0 3462 10566 1930 559 i* 2001:DB8:20:1::110 293 1275 559 i* 2001:DB8:E:4::2 1 0 4554 1849 1273 559 i* 2001:DB8:E:B::2 0 237 3748 1275 559 i* 2001:DB8:E:C::2 0 3748 1275 559 iSample Output from the show bgp ipv6 summary Command
In the following example, the status of all IPv6 BGP connections is displayed using the show bgp ipv6 summary command with the unicast keyword:
Router# show bgp ipv6 unicast summaryBGP router identifier 172.30.4.4, local AS number 200BGP table version is 1, main routing table version 1Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd2001:DB8:101::2 4 200 6869 6882 0 0 0 06:25:24 ActiveSample Output from the show bgp ipv6 dampened-paths Command
In the following example, IPv6 BGP dampened routes are displayed using the show bgp ipv6 dampened-paths command with the unicast keyword:
Router# show bgp ipv6 unicast dampening dampened-pathsBGP table version is 12610, local router ID is 192.168.7.225Status codes: s suppressed, d damped, h history, * valid, > best, i - internalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork From Reuse Path*d 3FFE:1000::/24 3FFE:C00:E:B::2 00:00:10 237 2839 5609 i*d 2001:228::/35 3FFE:C00:E:B::2 00:23:30 237 2839 5609 2713 iSample Output from the debug bgp ipv6 dampening Command
In the following example, debugging messages for IPv6 BGP dampening packets are displayed using the debug bgp ipv6 dampening command with the unicast keyword:
Router# debug bgp ipv6 unicast dampening00:13:28:BGP(1):charge penalty for 2001:DB8:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2001:DB8:0:1:1::/80 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:13:28:BGP(1):charge penalty for 2001:DB8:0:5::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty is 100000:16:03:BGP(1):charge penalty for 2001:DB8:0:1::/64 path 2 1 with halflife-time 15 reuse/suppress 750/200000:16:03:BGP(1):flapped 2 times since 00:02:35. New penalty is 189200:18:28:BGP(1):suppress 2001:DB8:0:1:1::/80 path 2 1 for 00:27:30 (penalty 2671)00:18:28:halflife-time 15, reuse/suppress 750/200000:18:28:BGP(1):suppress 2001:DB8:0:1::/64 path 2 1 for 00:27:20 (penalty 2664)00:18:28:halflife-time 15, reuse/suppress 750/2000Sample Output from the debug bgp ipv6 updates Command
In the following example, debugging messages for IPv6 BGP update packets are displayed using the debug bgp ipv6 updates command with the unicast keyword:
Router# debug bgp ipv6 unicast updates14:04:17:BGP(1):2001:DB8:0:2::2 computing updates, afi 1, neighbor version 0, table version 1, starting at ::14:04:17:BGP(1):2001:DB8:0:2::2 update run completed, afi 1, ran for 0ms, neighbor version 0, start version 1, throttled to 114:04:19:BGP(1):sourced route for 2001:DB8:0:2::1/64 path #0 changed (weight 32768)14:04:19:BGP(1):2001:DB8:0:2::1/64 route sourced locally14:04:19:BGP(1):2001:DB8:0:2:1::/80 route sourced locally14:04:19:BGP(1):2001:DB8:0:3::2/64 route sourced locally14:04:19:BGP(1):2001:DB8:0:4::2/64 route sourced locally14:04:22:BGP(1):2001:DB8:0:2::2 computing updates, afi 1, neighbor version 1, table version 6, starting at ::14:04:22:BGP(1):2001:DB8:0:2::2 send UPDATE (format) 2001:DB8:0:2::1/64, next 2001:DB8:0:2::1, metric 0, path14:04:22:BGP(1):2001:DB8:0:2::2 send UPDATE (format) 2001:DB8:0:2:1::/80, next 2001:DB8:0:2::1, metric 0, path14:04:22:BGP(1):2001:DB8:0:2::2 send UPDATE (prepend, chgflags:0x208) 2001:DB8:0:3::2/64, next 2001:DB8:0:2::1, metric 0, path14:04:22:BGP(1):2001:DB8:0:2::2 send UPDATE (prepend, chgflags:0x208) 2001:DB8:0:4::2/64, next 2001:DB8:0:2::1, metric 0, pathConfiguration Examples for Multiprotocol BGP for IPv6
•
•
•
•
Example: Configuring a BGP Process, BGP Router ID, and IPv6 Multiprotocol BGP Peer
The following example enables IPv6 globally, configures a BGP process, and establishes a BGP router ID. Also, the IPv6 multiprotocol BGP peer 2001:DB8:0:CC00:: is configured and activated.
ipv6 unicast-routing!router bgp 65000no bgp default ipv4-unicastbgp router-id 192.168.99.70neighbor 2001:DB8:0:CC00::1 remote-as 64600address-family ipv6 unicastneighbor 2001:DB8:0:CC00::1 activateExample: Configuring an IPv6 Multiprotocol BGP Peer Using a Link-Local Address
The following example configures the IPv6 multiprotocol BGP peer FE80::XXXX:BFF:FE0E:A471 over Gigabit Ethernet interface 0/0/0 and sets the route map named nh6 to include the IPv6 next-hop global address of Gigabit Ethernet interface 0/0/0 in BGP updates. The IPv6 next-hop link-local address can be set by the nh6 route map (not shown in the following example) or from the interface specified by the neighbor update-source command (as shown in the following example).
router bgp 65000neighbor FE80::XXXX:BFF:FE0E:A471 remote-as 64600neighbor FE80::XXXX:BFF:FE0E:A471 update-source gigabitethernet0/0/0address-family ipv6neighbor FE80::XXXX:BFF:FE0E:A471 activateneighbor FE80::XXXX:BFF:FE0E:A471 route-map nh6 outroute-map nh6 permit 10match ipv6 address prefix-list ciscoset ipv6 next-hop 2001:DB8:5y6::1ipv6 prefix-list cisco permit 2001:DB8:2Fy2::/48 le 128ipv6 prefix-list cisco deny ::/0
Note
Example: Configuring an IPv6 Multiprotocol BGP Peer Group
The following example configures the IPv6 multiprotocol BGP peer group named group1:
router bgp 65000no bgp default ipv4-unicastneighbor group1 peer-groupneighbor 2001:DB8:0:CC00::1 remote-as 64600address-family ipv6 unicastneighbor group1 activateneighbor 2001:DB8:0:CC00::1 peer-group group1Example: Advertising IPv4 Routes Between IPv6 Peers
The following example advertises IPv4 routes between IPv6 peers when the IPv6 network is connecting two separate IPv4 networks. Peering is configured using IPv6 addresses in the IPv4 address family configuration mode. The inbound route map named rmap sets the next hop because the advertised next hop is likely to be unreachable.
router bgp 65000!neighbor 6peers peer-groupneighbor 2001:DB8:yyyy::2 remote-as 65002address-family ipv4neighbor 6peers activateneighbor 6peers soft-reconfiguration inboundneighbor 2001:DB8:yyyy::2 peer-group 6peersneighbor 2001:DB8:yyyy::2 route-map rmap in!route-map rmap permit 10set ip next-hop 10.21.8.10Where to Go Next
If you want to implement more IPv6 routing protocols, refer to the Implementing RIP for IPv6 or the Implementing IS-IS for IPv6 module.
Additional References
Related Documents
BGP and multiprotocol BGP commands: complete command syntax, command mode, defaults, usage guidelines, and examples
"BGP Commands," Cisco IOS IP Routing Protocols Command Reference
Cisco Nonstop Forwarding
"Cisco Nonstop Forwarding," Cisco IOS XE High Availability Configuration Guide
IPv6 supported feature list
"Start Here: Cisco IOS XE Software Release Specifics for IPv6 Features," Cisco IOS XE IPv6 Configuration Guide
IPv6 commands: complete command syntax, command mode, defaults, usage guidelines, and examples
Cisco IOS master command list, all releases
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
None
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Implementing Multiprotocol BGP
for IPv6Table 6 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 6 Feature Information for Implementing Multiprotocol BGP for IPv6
IPv6—NSF and Graceful Restart for MP-BGP IPv6 Address Family
Cisco IOS XE Release 3.1S
IPv6 BGP supports Cisco Nonstop Forwarding and graceful restart.
The following sections provide information about this feature:
•
IPv6 Multicast Address Family Support for Multiprotocol BGP
Cisco IOS XE Release 2.1
The multiprotocol BGP for the IPv6 multicast address family feature provides multicast BGP extensions for IPv6 and supports the same features and functionality as IPv4 BGP.
The following sections provide information about this feature:
•
IPv6 Routing—Multiprotocol BGP Extensions for IPv6
Cisco IOS XE Release 2.1
Multiprotocol BGP extensions for IPv6 supports the same features and functionality as IPv4 BGP.
The following sections provide information about this feature:
•
IPv6 Routing—Multiprotocol BGP Link-Local Address Peering
Cisco IOS XE Release 2.1
IPv6 supports multiprotocol BGP link-local address peering.
The following sections provide information about this feature:
•
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
Any Internet Protocol (IP) addresses and phone numbers 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.
© 2001-2011 Cisco Systems, Inc. All rights reserved.
