Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 © 2004 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID EIGRP FOR MANAGED SERVICES FUNCTIONALITY PRESENTATION DONNIE SAVAGE CHETAN.

Similar presentations


Presentation on theme: "1 © 2004 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID EIGRP FOR MANAGED SERVICES FUNCTIONALITY PRESENTATION DONNIE SAVAGE CHETAN."— Presentation transcript:

1 1 © 2004 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID EIGRP FOR MANAGED SERVICES FUNCTIONALITY PRESENTATION DONNIE SAVAGE CHETAN KHETANI SANGITA PANDYA INTERNET TECHNOLOGIES DIVISION DECEMBER 2004

2 222 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Agenda INTRODUCTION AND TECHNOLOGY OVERVIEW Functionality Description EIGRP Route Propagation Behaviour EIGRP Changes Operation Scenarios Configuration and Troubleshooting 222 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID

3 333 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Service Provider Converged Network VPN for Many Managed Services MANAGED IPT MANAGED Routing MANAGED Extranet MANAGED Internet Gateway MANAGED Security MANAGED CPE V i r t u a l P r i v a t e N e t w o r k Customer Branch Customer Branch VM VPN B VM Customer HQ Service Level Agreement for MANAGED Services

4 444 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Managed Routing Revenue Opportunity Over 50% of Cisco Enterprise Customers Deploy IP Routing with EIGRP IP/MPLS VPN Backbone EIGRP AS-1 PE-1 CE-1 EIGRP AS-1 PE-2 PE © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID CE-2

5 555 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Robust EIGRP Support BENEFITS: Service Provider: Simplest point of entry into enterprises existing architecture Enterprise: Least disruption to current network design Cisco Exclusive VPN A/Site 1 VPN C/Site 2 VPN A/Site 2 VPN B/Site 2 VPN C/Site 1 CE A1 CE B3 CE A3 CE A2 CE 1 B1 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 16.1/ / /16 RIPv2 Static OSPF RIPv2 BGP OSPF RIPv2 BGP 12.2/16 CE B2 Cisco IOS Supports the Industrys Most Comprehensive and Robust Routing Protocol Support: RIP, OSPF, BGP, ISIS, Including EIGRP © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID

6 666 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Managed EIGRP Benefits for SPs and Enterprises: Impose little requirements or no restrictions on customer networks CE and C routers are NOT required to run newer code (CE/C upgrades recommended for full SoO functionality) Customer sites may be same or different Autonomous Systems Customer sites may consist of several connections to the MPLS VPN backbone Customer sites may consist of one or more connections not part of the MPLS VPN backbone (backdoor links)

7 777 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: MPLS VPN Network PP PP PE CE PE CE VPN_A VPN_B VPN_A VPN_B VPN_A Provider Edge Customer Edge Provider Router VRF Interface MP-BGP Sessions LDP PE-CE Routing Protocol EIGRP, Static,RIPv2,EBGP,OSPF CE MPLS Core

8 888 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: EIGRP for MPLS VPN PE-CE VPN A/Site 1 VPN C/Site 2 VPN A/Site 2 VPN B/Site 2 VPN B/Site 1 VPN C/Site 1 CE A1 CE B3 CE A3 CE A2 CE 1 B1 CE 2 B1 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 16.1/ / / / /16 EIGRP BGP 12.2/16 CE B2 EIGRP

9 999 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID VPN A/Site 1 VPN C/Site 2 VPN A/Site 2 VPN B/Site 2 VPN B/Site 1 VPN C/Site 1 CE A1 CE B3 CE A3 CE A2 CE 1 B1 CE 2 B1 PE 1 PE 2 PE 3 P1P1 P2P2 P3P3 16.1/ / / / /16 EIGRP BGP 12.2/16 CE B2 Technology Overview: MPLS VPN Routes Distribution Step 2 Step 4 Step 1 Step 3 Step 5 EIGRP

10 10 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: Routing Information Distribution Step 1: From site (CE) to service provider (PE) E.g. EIGRP, RIPv2, OSPF, or BGP (or static routing on PE) Step 2: Export to providers BGP at ingress PE Step 3: Within/across service provider(s) (among PEs): Via MP-IBGP Step 4: Import from providers BGP at egress PE Step 5: From service provider (PE) to site (CE) E.g. EIGRP, RIPv2, OSPF, or BGP (or static routing on PE)

11 11 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: EIGRP PE/CE Deployment In this network, we have two corporate sites, connected by a leased line and VPN through a service provider EIGRP routes redistributed into BGP at B, and back into EIGRP at C, appear as external routes at Site 2 We want them to appear as internal routes SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN EXTERNAL

12 12 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: EIGRP PE/CE Deployment As routes are redistributed into BGP as B, extended communities containing the EIGRP metrics are attached to them As routes are redistributed back into EIGRP at C, these extended communities are used to reconstruct the routes as internals The VPN is considered a 0 cost link in this configuration SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN INTERNAL

13 13 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN INTERNAL Technology Overview: EIGRP PE/CE Deployment router-c#show ip eigrp vrf VRF-RED topology IP-EIGRP Topology Table for AS(1)/ID( ) Routing Table:VRF-PINK P /24, 1 successors, FD is via (409600/128256), Ethernet3/0 P /24, 1 successors, FD is ip vrf VRF-RED rd :20 exit.... router eigrp 1 address-family ipv4 vrf VRF-RED autonomous-system 101 network redistribute BGP 101 metric exit-address-family

14 14 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN NO BACKDOOR LINK Technology Overview: EIGRP PE/CE Deployment 12.0(27)SV 12.0(21.1)SY2 12.0(21.1)S2 Backdoor links were not supported products/sw/iosswrel/ps183 9/products_feature_guide09 186a db3.htmlhttp://www.cisco.com/en/US/ products/sw/iosswrel/ps183 9/products_feature_guide09 186a db3.html

15 15 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: EIGRP PE/CE Backdoor Links The biggest danger with backdoor links is possible routing loops Site1 advertises a network through the back door to site 2 C prefers this route, and redistributes it into BGP B prefers the BGP route, and redistributes it into EIGRP, forming a loop The solution is to automatically tag all the routes originating in site 1 so they will be rejected by C This tag is called the Site of Origin (SoO) SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN

16 16 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID SERVICE PROVIDER SITE 1 SITE 2 A B C D VPN Technology Overview: EIGRP PE/CE Backdoor Links The SoO is set on all PE routers on the interface connecting to the PE, and on backdoor link routers The CE will always reject the marked EIGRP learned routes, and prefer the BGP learned routes You can then set the backdoor link so the path through the VPN is always preferred over the backdoor link route-map SoOrigin permit 10 set extcommunity soo 100:1.... interface FastEthernet 0/0 ip vrf sitemap SoOrigin....

17 17 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Technology Overview: EIGRP MIB Support EIGRP Traffic Statistics AS Number Hellos Sent/Received Updates Sent/Received Queries Sent/Received Replies Sent/Received EIGRP Topology Data Destination Net/Mask Active State Feasible Successors Origin Type Distance Reported Distance EIGRP Interface Data Peer Count Reliable/Unreliable Queues Pacing Pending Routes Hello Interval EIGRP Neighbor Data Peer Address Peer Interface Hold Time Up Time SRTT/RTO Version AND MANY MORE…

18 18 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID BGP/MPLS VPN With EIGRP between PE-CE Technology Overview: EIGRP PE/CE Prefix Limits Generic Redistribution: To limit the number of redistributed routes/prefixes MPLS VPN PE-CE: To limit the number of prefixes on a given PE router as follows: For the whole VPN or For individual CEs/neighbors neighbor maximum-prefix [ ] [warning-only] [[restart ][restart-count ][reset-time ][dampened]] redistribute maximum-prefix [ ] [warning-only][[restart ] [restart-count ] [reset-time ][dampened]] CE PE1 PE VRF 1 VRF 2 VRF L VRF L+1 … VRF 3

19 19 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Summary Native EIGRP on PE to CE links Avoids translating all EIGRP routes to external routes Redistribution of EIGRP metrics preserved across BGP cloud though use of Extended Community attributes Impose little requirements or no restrictions on customer networks CE and C routers are NOT required to run newer code (CE/C upgrades recommended for full SoO functionality) Customer sites may be same or different Autonomous Systems Customer sites may consist of several connections to the MPLS VPN backbone Customer sites may consist of one or more connections not part of the MPLS VPN backbone (backdoor links) Note: Backdoor linksEIGRP Site of Origin is not supported in the initial release; this support was added in 12.3(8)T and S

20 20 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Summary (Cont.) EIGRP Route Type and Metric Preservation The MPLS VPN backbone is running BGP; Normal redistribution of EIGRP into BGP and vice versa on the PEs results in intersite EIGRP routes appearing as external routes resulting in all routes traversing the MPLS VPN backbone becoming less preferable than the routes that do not traverse the MPLS VPN backbone To solve this; If the sites are non-EIGRP: PEs originate External EIGRP routes using the configured default metric; if no default metric is configured, the routes will not be redistributed into EIGRP If the sites are in different EIGRP Autonomous System: PEs originate External EIGRP routes using the configured default metric; if no default metric is configured, the routes will not be redistributed into EIGRP if the sites are in the same EIGRP Autonomous System: PEs originate EIGRP routes using the originating EIGRP metrics and route types from the originating EIGRP AS

21 21 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Agenda Introduction and Technology Overview FUNCTIONALITY DESCRIPTION EIGRP Route Propagation Behaviour EIGRP Changes Operation Scenarios Configuration and Troubleshooting 21 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID

22 22 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID EIGRP Route Propagation Behavior MPLS VPN Backbone AS-1 AS-2 AS x.x 10.1.x.x 10.3.x.x

23 23 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID MPLS VPN Backbone AS-1 AS-2 AS x.x 10.1.x.x 10.3.x.x EIGRP Route Propagation Behavior EIGRP Routes Are Advertised into BGP Backbone Preserving the EIGRP Route Type and Metric Information in the BGP Extended Community Attribute EIGRP Internal

24 24 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID MPLS VPN Backbone AS-1 AS-2 AS x.x 10.1.x.x 10.3.x.x BGP Redistributes Routes into EIGRP Using Route Type and Metric Information Extracted from BGP Extended Community Information EIGRP Route Propagation Behavior EIGRP AS1: Internal EIGRP AS2: External EIGRP AS1: External EIGRP AS1: Internal EIGRP AS2: External

25 25 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID MPLS-VPN Backbone EIGRP AS-1 PE-1 CE-1 EIGRP AS-1 PE-2 CE-2 PE-3 Route Redistribution and Avoiding Routing Loop VPN-IPv4 Update RD:Net-1, Next-hop=PE-1 RT=xxx:xxx EIGRP-Route-Type= internal EIGRP-VecMetric=B,L,D,R.M,H EIGRP redistributes into BGP: EIGRP-Route-Type= internal EIGRP-VecMetric=B,L,D,R.M,H EIGRP originates as Internal Route with initial BW, Load, Delay, Reliability, MTU, Hop

26 26 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Route Redistribution and Avoiding Routing Loop MPLS-VPN Backbone EIGRP AS-1 CE-1 EIGRP AS-1 CE-2 BGP redistributes into EIGRP : EIGRP-Route-Type= internal EIGRP-VecMetric=B,L,D,R.M,H PE-2 PE-1 PE-3

27 27 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID MPLS-VPN Backbone EIGRP AS-1 CE-1 EIGRP AS-1 CE-2 Route Redistribution and Avoiding Routing Loop PE-2 PE-1 EIGRP computes new VecMetric: EIGRP-Route-Type= internal EIGRP-VecMetric=B,L,D,R.M,H EIGRP installs Route as: Internal, BW, Load, Delay, Reliability, MTU, Hop PE-3

28 28 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID PE-3 MPLS-VPN Backbone EIGRP AS-1 CE-1 EIGRP AS-1 CE-2 PE-2 PE-1 Route Redistribution and Avoiding Routing Loop PE-2 sees higher cost from CE-2 than PE-1 so will not redistribute route back into BGP CE-2 uses split horizon to prevent route reflection to PE-3

29 29 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: General CE runs EIGRP as before PE runs an EIGRP-VRF process per vrf/AS EIGRP routes are distributed to sites customer via MP-iBGP on the MPLS-VPN backbone Each EIGRP-VRF process needs to be redistributed into MP-iBGP and vice-versa MP-iBGP will carry extended community information across the MPLS-VPN backbone to other customer sites BGP Basic Configuration Address-family vpnv4 neighbor x.x.x.x activate neighbor x.x.x.x send-community extended Address-family ipv4 vrf redistribute EIGRP no auto-summary no synchronization exit-address-family

30 30 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID New Extended Communities MPLS/VPN backbone is MP-BGP There are no EIGRP adjacencies or EIGRP updates in MPLS/VPN backbone EIGRP information is carried across MPLS/VPN backbone by MP-BGP in new extended communities (set and used by PEs)

31 31 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID New Extended Communities: EIGRP Information Type 0x8800 Usage: EIGRP Route Metric information Appended Values: Flags + TAG

32 32 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID New Extended Communities: EIGRP Metric Information Type 0x8801 Usage: EIGRP Route Metric information Appended Values: AS + Delay Type 0x8802 Usage: EIGRP Route Metric Information Values: Reliability + Hop + BW Type 0x8803 Usage: EIGRP Route Metric Information Values: Reserve +Load + MTU

33 33 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID New Extended Communities: EIGRP External Information Type 0x8804 Usage: EIGRP Ext Route Information Values: Remote AS + Remote ID Type 0x8805 Usage: EIGRP Ext Route Information Values: Remote Protocol + Remote Metric

34 34 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID New Extended Communities: EIGRP External Protocol External ProtocolDefines the external protocol that this route was learned by; the following values are assigned: IGRP-1OSPF-6 EGRP-2IS-IS-7 Static-3EGP-8 RIP-4BGP-9 HELLO-5IDRP-10

35 35 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: PEMetric Preservation EIGRP metric can be set on the PE by the command: redistribute BGP metric B D R L M Used to set the metric for BGP routes redistributed into EIGRP EIGRP will look for BGP extended community information, and if found, use BGP extended community information to recreate the original EIGRP route; if the extended community information is missing, the metric values provided will be used for the external route created default-metric B D R L M Used to set the metric for any non-eigrp route being redistributed into EIGRP If the Route is BGP, EIGRP will look for BGP extended community information, and if found, use BGP extended community information to recreate the original EIGRP route; if the extended community information is missing, the metric values provided will be used for the external route created B=Bandwidth D=Delay R=Reliability L=Load M=MTU

36 36 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: PENon-EIGRP Routes If a route is received via BGP, and the route has no extended community information for EIGRP: The route will be advertised to the CE as an external EIGRP route using the metric supplied on the redistribution or default-metric statement; if no metric is configured, the route will not be advertised to the CE

37 37 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: PESame AS If a route is received via BGP with extended community information for EIGRP and the AS number matches: The route is advertised to the CE as the same type of route (Int/Ext) as it was in the originating site The Extended Community information will be used to set the metric with the VPN itself appearing as a zero-cost link Recreated External routes will also contain all of the external data associated with the route in the originating site (originating router, originating protocol, etc.)

38 38 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: PEDifferent AS If a route is received via BGP with extended community information for EIGRP and the AS number doesnt match: The route is advertised to the CE as an external EIGRP route; the route will *NOT* use the Extended Community information as it did not originate from the same AS

39 39 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Agenda Introduction and Technology Overview Functionality Description EIGRP Route Propagation Behaviour EIGRP Changes Operation SCENARIOS Configuration and Troubleshooting 39 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID

40 40 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Scenarios Customer sites all belong to the same EIGRP autonomous system Customer sites have BACKDOOR links Customer sites belong to different EIGRP autonomous systems Customer sites contain one or more non-EIGRP site

41 41 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Single AS Scenario Routes are redistributed from EIGRP into MP-BGP on the sending PE, with the route information encoded in the Extended Community attributes Routes are recreated by receiving PE and sent to the CE as an EIGRP route; the same route type and metric as the original route will be used to recreate the EIGRP route The recreated route will be sent to the CE from the receiving PE with the same metric it contained on the sending PE Note: the MPLS/VPN link looks like it has Zero metric

42 42 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Single AS Scenario MPLS VPN Super Backbone AS-1 VPN Red PE Network X Internal or External VPNv4 Route Internal or External Original Route recreated

43 43 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Single AS with Backdoor Link Scenario Routes are redistributed from EIGRP into MP-BGP on the sending PE, with the route information encoded in the Extended Community attributes Routes are recreated by receiving PE and sent to the CE as an EIGRP route; the same route type and metric as the original route will be used to recreate the EIGRP route The recreated route will be sent to the CE from the receiving PE with the same metric it contained on the sending PE Note: the MPLS/VPN link looks like it has Zero metric The path each site will use to reach prefixes belonging to the other site will be based on metric The backdoor link can be only as a failover by increasing its metric

44 44 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Single AS with Backdoor Link Scenario MPLS VPN Super Backbone AS-1 VPN Red Backdoor Link PE Network X Internal or External Original Route recreated Internal or External VPNv4 Route

45 45 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Multiple AS Scenario Routes are redistributed from EIGRP into MP-BGP on the sending PE, with the route information encoded in the Extended Community attributes On PEs running the same EIGRP AS, the routes are recreated and sent to the CE as an EIGRP route The same route type and metric as the original route will be used to recreate the EIGRP route The recreated route will be sent to the CE from the receiving PE with the same metric it contained on the sending PE On PEs running a different EIGRP AS, the routes are redistributed into EIGRP as External routes (originating protocol = BGP) The redistribution metric will be used for these routes

46 46 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Multiple AS Scenario MPLS VPN Super Backbone AS-1 AS-2 VPN Red Network X PE Internal VPNv4 Route Route Created as External using configured default metric PE Internal External Route Recreated As Internal

47 47 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Non-EIGRP Scenario Routes are redistributed from some other protocol into MP-BGP on the sending PE, without the Extended Community attributes Since there are no Extended Community attributes, the routes are redistributed into EIGRP on the receiving PE as External routes, with the originating protocol appearing as BGP The redistribution metric defined on the redistribute bgp or default-metric statement will be used to determine the metric on the redistributed External routes

48 48 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Operation: Non-EIGRP Scenario MPLS VPN Super Backbone OSPFEIGRP AS1 VPN Red PE Network X Redistributed into BGP VPNv4 Route External Route Created as External using configured default metric

49 49 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Agenda Introduction and Technology Overview Functionality Description EIGRP route propagation behavior EIGRP changes Operation Scenarios CONFIGURATION AND TROUBLESHOOTING 49 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID

50 50 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Configuration New config commands: Support for address-family syntax added One EIGRP Router process can support multiple EIGRP-VRF processes The number of EIGRP-VRF processes is limited to the available system resources and the number of supported VRFs on a given platform For example: router EIGRP 1 address-family ipv4 vrf vrf-red autonomous-system 69 There is always an EIGRP-VRF process created for the default routing table EIGRP Router Process EIGRP-VRF Process

51 51 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Configuration The AS used by a given EIGRP-VRF process is bounded to the scope of the VRF it is configured for For example: router EIGRP 42 address-family ipv4 vrf vrf-red autonomous-system 42 address-family ipv4 vrf vrf-green autonomous-system 42 All of the three EIGRP-VRF processes are unique and will NOT share neighbors, routing information, or topology information

52 52 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Configuration Single Instance router EIGRP 1 network address-family ipv4 vrf vrf-red network autonomous-system 42 redistribute BGP 100 metric exit-address-family address-family ipv4 vrf vrf-green network antonymous-system 99 redistribute BGP 101 metric metric exit-address-family no eigrp log-neighbor-changes Commands for Default Routing Table Commands for vrf-red Commands for vrf-green Commands for Default Routing Table

53 53 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Configuration Multiple Instance router EIGRP 1 address-family ipv4 vrf vrf-red network autonomous-system 42 redistribute BGP 100 metric exit-address-family no eigrp log-neighbor-changes router EIGRP 2 address-family ipv4 vrf vrf-green network autonomous-system 99 redistribute BGP 101 metric exit-address-family no eigrp log-neighbor-changes Commands for Default Routing Table Commands for vrf-red Commands for vrf-green Commands for Default Routing Table Commands for Default Routing Table

54 54 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Troubleshooting Show commands show ip EIGRP event show ip EIGRP neighbor show ip EIGRP interface show ip EIGRP topology show ip protocol Note: use * as the vrf-name to specify all vrfs

55 55 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Troubleshooting Clear commands clear ip EIGRP event clear ip EIGRP neighbor *clear ip EIGRP topology Note: Hidden command use * as the vrf-name to specify all vrfs

56 56 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID Troubleshooting Debug commands debug ip EIGRP debug ip EIGRP neighbor debug ip EIGRP notifications debug ip EIGRP summary Note: use * as the vrf-name to specify all vrfs use

57 57 © 2004 Cisco Systems, Inc. All rights reserved. Presentation_ID


Download ppt "1 © 2004 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID EIGRP FOR MANAGED SERVICES FUNCTIONALITY PRESENTATION DONNIE SAVAGE CHETAN."

Similar presentations


Ads by Google