Last active
May 10, 2019 06:41
-
-
Save luisenriquecorona/4c8458ba3be084dff56888e6977a0ba8 to your computer and use it in GitHub Desktop.
Shows the network topology for the configuration that follows, which shows how to configure EIGRP over MPLS where the MPLS PE devices are taking part in the EIGRP process.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ***In this example, it is assumed that | |
| the MPLS network is configured with the MPLS PE | |
| devices participating in the EIGRP process and virtual route forwarding. | |
| Only the client-side EIGRP configuration is shown here.*** | |
| R1 Router | |
| R1(config)#interface fastethernet0/0 | |
| Enters interface configuration mode | |
| R1(config-if)#ip address 192.168.1.2 255.255.255.252 | |
| Assigns the IP address and mask | |
| R1(config-if)#no shutdown | |
| Enables the interface | |
| R1(config-if)#router eigrp 100 | |
| Creates routing process 100 | |
| R1(config-router)#network 172.16.1.0 0.0.0.255 | |
| Advertises the network in EIGRP | |
| R1(config-router)#network 192.168.1.0 0.0.0.255 | |
| Advertises the network in EIGRP | |
| R2 Router | |
| R2(config)#interface fastethernet0/0 | |
| Enters interface configuration mode | |
| R2(config-if)#ip address 192.168.2.2 255.255.255.252 | |
| Assigns the IP address and mask | |
| R2(config-if)#no shutdown | |
| Enables the interface | |
| R2(config-if)#router eigrp 100 | |
| Creates routing process 100 | |
| R2(config-router)#network 172.17.2.0 0.0.0.255 | |
| Advertises the network in EIGRP | |
| R2(config-router)#network 192.168.2.0 0.0.0.255 | |
| Advertises the network in EIGRP |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NOTE: When deploying EIGRP over Layer 3 MPLS, no changes are needed to the basic EIGRP configuration from the customer perspective. The only difference here is that the customer has to agree on the EIGRP parameters—autonomous system num- bers, authentication password, and so on—with the service provider, because these parameters are often governed by the service provider.
NOTE: The PE routers receive IPv4 routing updates from the Client routers and install them in the appropriate Virtual Routing and Forwarding (VRF) table. This part of the configuration and operation is the responsibility of the service provider.
NOTE: From the EIGRP perspective, the MPLS backbone and routers PE1 and PE2 are not visible. A neighbor relationship is established directly between routers R1 and R2; you can verify this with the show ip eigrp neighbors command output.