- •Acknowledgments
- •Introduction
- •Assessment Test
- •Answers to Assessment Test
- •Service Provider Networks
- •Scalability
- •Traffic Engineering
- •Quality of Service
- •MPLS Label Stack
- •Shim Header
- •MPLS Architecture
- •Control
- •Forwarding
- •MPLS Label Switching
- •MPLS Network Components
- •Device Output
- •Label-Switched Paths
- •MPLS Applications
- •MPLS and ATM
- •Overlay
- •Quality of Service
- •Traffic Engineering
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •Routing Review
- •Frame-Mode MPLS Working Example
- •Network Routing Protocol Examples
- •MPLS Step by Step
- •Label Distribution
- •Assigning Labels
- •Troubleshooting and Verification
- •Device Configuration
- •IGP Verification
- •CEF Verification
- •MPLS Verification
- •Label Distribution and Bindings
- •Binding Verification
- •Troubleshooting the Network
- •Hiding Service Provider Devices
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •Frame-Mode MPLS and ATM
- •Frame-Mode MPLS and ATM Configuration
- •Cell-Mode MPLS
- •Label Binding with ATM
- •Cell-Mode Label Switching
- •VC Merge
- •Loop Prevention
- •Cell-Mode MPLS Configuration
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •VPNs 101
- •Point-to-Point Connections
- •Virtual Private Networks
- •Categories of VPNs
- •VPN Routing
- •Peer-to-Peer VPNs
- •Optimal Routing
- •Peer-to-Peer Security
- •Peer-to-Peer VPN Routing
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •Service Provider Configuration
- •MPLS VPNs
- •Virtual Router
- •Virtual Routing and Forwarding Tables
- •MPLS Operational Overview
- •MP-BGP Configuration
- •An MPLS VPN Example
- •Route Distinguisher
- •MP-IBGP Configuration Example
- •Initial Network Configuration
- •MP-IBGP Configuration
- •Verification
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •A Review of VPNs
- •Configuring a Simple MPLS VPN
- •Configuring VRF Interfaces
- •Running RIP in an MPLS VPN
- •Configuring RIPv2 with Address-Family ipv4
- •Configuring Redistribution
- •Route Targets
- •Configuring Route Targets
- •A Review of Simple VPN Configuration
- •Configuring MPLS in the Service Provider Network
- •Simple VPN Configuration
- •Configuring the PE-CE Routing Protocol
- •Lab: Configuring an MPLS VPN
- •Configuring POP Routers
- •VPN Configuration
- •Raleigh Running-Config
- •Atlanta Running-Config
- •Peer 1 Running-Config
- •Peer 2 Running-Config
- •Verification with Ping
- •Routing Table Isolation
- •Verifying VRF Routes
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •MP-BGP and OSPF
- •A Review of OSPF
- •OSPF Router Types
- •Link State Advertisements
- •OSPF for MPLS VPNs
- •OSPF Super-Backbone
- •Preventing Routing Loops
- •Path Selection
- •MPLS VPN OSPF Lab
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •Static Routing
- •Device Configuration
- •VPN Configuration
- •Raleigh Running-Config
- •Atlanta Running-Config
- •Peer Router Configuration
- •Verification with Ping
- •Verifying Static VRF Routes
- •E-BGP and MPLS VPNs
- •Device Configuration
- •E-BGP Operation
- •AS-Override
- •VPN Configuration
- •Raleigh Running-Config
- •Atlanta Running-Config
- •Peer Router Configuration
- •Peer 1 Running-Config
- •Peer 2 Running-Config
- •Verification with Ping
- •Advanced MPLS VPN Topologies
- •Simple VPNs
- •Central Services MPLS VPN Topology
- •Overlay MPLS VPN Topology
- •Summary
- •Exam Essentials
- •Key Terms
- •Review Questions
- •Answers to Review Questions
- •Challenge Lab 1
- •MPLS
- •MP-IBGP
- •Answer to Lab 1.1
- •Answer to Lab 1.2
- •Answer to Lab 1.3
- •Challenge Lab 2
- •Tag Switching
- •MP-IBGP
- •Answer to Lab 2.1
- •Answer to Lab 2.2
- •Answer to Lab 2.3
- •Challenge Lab 3
- •VRF Configuration
- •RIPv2
- •Redistribution
- •Answer to Lab 3.1
- •Answer to Lab 3.2
- •Answer to Lab 3.3
- •Challenge Lab 4
- •VRF Configuration
- •OSPF
- •Redistribution
- •Answer to Lab 4.1
- •Answer to Lab 4.2
- •Answer to Lab 4.3
- •Challenge Lab 5
- •VRF Configuration
- •Static Routes and Redistribution
- •Answer to Lab 5.1
- •Answer to Lab 5.2
- •Challenge Lab 6
- •VRF Configuration
- •E-BGP Configuration
- •Answer to Lab 6.1
- •Answer to Lab 6.2
- •Service Provider Network Configuration with OSPF
- •Router Configuration
- •Routing Tables
- •Tags
- •Service Provider Network Configuration with IS-IS
- •Router Configuration
- •Routing Tables
- •Tag Switching Forwarding Tables
- •Glossary
422 Appendix B Service Provider Tag Switching with OSPF and IS-IS
router bgp 65002
no synchronization
bgp log-neighbor-changes redistribute connected
neighbor 192.168.3.9 remote-as 65000 no auto-summary
!
ip classless
no ip http server
!
!
line con 0 exec-timeout 0 0 privilege level 15 logging synchronous transport input none
ip netmask-format decimal line aux 0
line vty 0 4 privilege level 15 password cisco logging synchronous login
ip netmask-format decimal
!
end
Routing Tables
This section shows you the routing tables of each network device in the example network. Notice that the Core router has no knowledge of the peer router subnets and the peer routers have no knowledge of the core service provider networks. The Atlanta and Raleigh POP routers have full knowledge of all the subnets in the network.
Copyright ©2002 SYBEX, Inc., Alameda, CA |
www.sybex.com |
Service Provider Network Configuration with OSPF 423
Peer 1 Routing Table
On the Peer 1 router, internal service provider routes do not show up in the routing table:
Peer1#show ip route
.
. Output Omitted
.
Gateway of last resort is not set
|
192.168.1.0 255.255.255.255 is subnetted, 1 |
subnets |
C |
192.168.1.1 is directly connected, Loopback0 |
|
|
192.168.2.0 255.255.255.255 is subnetted, 1 |
subnets |
B |
192.168.2.1 [20/0] via 192.168.3.6, 00:08:15 |
|
|
192.168.3.0 255.255.255.252 is subnetted, 2 |
subnets |
B |
192.168.3.8 [20/0] via 192.168.3.6, 00:08:15 |
|
C |
192.168.3.4 is directly connected, Serial0 |
|
Atlanta Routing Table
On the Atlanta POP router, all routes (both peer and service provider) are displayed in the routing table:
Atlanta#show ip route
.
. Output Omitted
.
Gateway of last resort is not set
204.134.83.0 255.255.255.0 is variably subnetted, 5 subnets, 2 masks
O204.134.83.8 255.255.255.252
[110/1562] via 204.134.83.6, 00:10:08, Serial0/0 C 204.134.83.1 255.255.255.255 is directly
connected, Loopback0
O204.134.83.3 255.255.255.255
[110/1563] via 204.134.83.6, 00:10:08, Serial0/0
Copyright ©2002 SYBEX, Inc., Alameda, CA |
www.sybex.com |
424 Appendix B Service Provider Tag Switching with OSPF and IS-IS
O204.134.83.2 255.255.255.255
[110/782] via 204.134.83.6, 00:10:08, Serial0/0 C 204.134.83.4 255.255.255.252 is directly
connected, Serial0/0
192.168.1.0 255.255.255.255 is subnetted, 1 subnets
B192.168.1.1 [20/0] via 192.168.3.5, 00:22:47 192.168.2.0 255.255.255.255 is subnetted, 1 subnets
B192.168.2.1 [200/0] via 204.134.83.3, 00:09:24 192.168.3.0 255.255.255.252 is subnetted, 2 subnets
B192.168.3.8 [200/0] via 204.134.83.3, 00:09:24 C 192.168.3.4 is directly connected, Serial0/1
Core Routing Table
On the Core router, only internal service provider routes show up in the routing table:
Core#show ip route
.
. Output Omitted
.
Gateway of last resort is not set
204.134.83.0 255.255.255.0 is variably subnetted, 5 subnets, 2 masks
C 204.134.83.8 255.255.255.252 is directly connected, Serial0/0
O204.134.83.1 255.255.255.255
[110/782] via 204.134.83.5, 00:10:51, Serial0/1
O204.134.83.3 255.255.255.255
[110/782] via 204.134.83.10, 00:10:51, Serial0/0
C204.134.83.2 255.255.255.255 is directly connected, Loopback0
C204.134.83.4 255.255.255.252 is directly connected, Serial0/1
Copyright ©2002 SYBEX, Inc., Alameda, CA |
www.sybex.com |
Service Provider Network Configuration with OSPF 425
Raleigh Routing Table
On the Raleigh POP router, both service provider and peer routers are displayed in the routing table:
Raleigh#show ip route
.
. Output Omitted
.
Gateway of last resort is not set
204.134.83.0 255.255.255.0 is variably subnetted, 5 subnets, 2 masks
C 204.134.83.8 255.255.255.252 is directly connected, Serial0/3
O204.134.83.1 255.255.255.255
[110/1563] via 204.134.83.9, 00:11:17, Serial0/3 C 204.134.83.3 255.255.255.255 is directly
connected, Loopback0
O204.134.83.2 255.255.255.255
[110/782] via 204.134.83.9, 00:11:17, Serial0/3
O204.134.83.4 255.255.255.252
[110/1562] via 204.134.83.9, 00:11:17, Serial0/3 192.168.1.0 255.255.255.255 is subnetted, 1 subnets
B192.168.1.1 [200/0] via 204.134.83.1, 00:10:33 192.168.2.0 255.255.255.255 is subnetted, 1 subnets
B192.168.2.1 [20/0] via 192.168.3.10, 00:24:05 192.168.3.0 255.255.255.252 is subnetted, 2 subnets
C192.168.3.8 is directly connected, Serial0/1
B192.168.3.4 [200/0] via 204.134.83.1, 00:10:34
Peer 2 Routing Table
On the Peer 2 router, no service provider routes are displayed in the routing table:
Peer2#show ip route
.
. Output Omitted
.
Copyright ©2002 SYBEX, Inc., Alameda, CA |
www.sybex.com |