76 8600 50121h 8600 smart routers routing protocols configuration guide

8600 Smart Routers Routing Protocols Configuration Guide 76.8600-50121H 15.05.2015 Document Information Revision History Document No Date Description of Changes 76.8600-50121H 15.05.2015 Added support of 8615 Smart Router stacked and 8665 Smart Router Updates applied: • Equal Cost Multipath (ECMP) • 3.6 Route Aggregation Changes and updates applied in 10.3.1 VRRP Configuration Reworked 5.10 Route Redistribution and added: 5.10.2 IS-IS Routes Redistribution from L2 to L1 and 5.10.3 Redistribution between IS-IS L1 to L1 Instances Added: • 6.4 IS-IS L1 to L1 Route Redistribution Configuration • 3.12 BGP Multipath 76.8600-50121G 29.10.2014 Added 8602 Smart Router and 8615 Smart Router Added a note clarifying the support of unnumbered links in 1.7 OSPF Unnumbered Links Updates and changes applied in Equal Cost Multipath (ECMP) Changes and updates applied in 10.3.1 VRRP Configuration Added 2.4 OSPF Authentication Added 3.2 Router ID Changes and updates in BGP Configuration Examples 76.8600-50121F 13.01.2014 Renewed related documentation table in 8600 Smart Routers Technical Documentation Added ECMP support in ELC1 line card in Equal Cost Multipath (ECMP) Added 3.10 BGP Failover Added support of BFD for single hop BGP in Bidirectional Forwarding Detection Updates applied in 6.1 IS-IS Basic Configuration Added a configuration example of 8.1.4 Single Hop BGP Added clarification of VRRP multiple instances configuration to an interface in 10.2.1 VRRP Parameters Added ELC1 support of VRRP + IRB and VRRP + ELP in 10.3.1 VRRP Configuration VRRP master and backup roles corrected in 11.1.2 Router–2 Configuration Updates and corrections applied in 8.2 BFD Configuration for Static Routes Changes applied in 3.3 BGP Attributes and reworked 3.3.6 COMMUNITY Attribute 8600 Smart Routers Routing Protocols Configuration Guide 76.8600-50121H © 2015 Coriant This revision of the manual documents the following network elements and the corresponding feature packs or higher 8602 Smart Router FP7.0 8605 Smart Router FP1.6 8607 Smart Router FP1.1 8609 Smart Router, 8611 Smart Router FP7.0 8615 Smart Router FP7.0 8620 Smart Router FP4.1 8630 Smart Router, 8660 Smart Router FP7.0 8665 Smart Router FP7.0 If a different feature pack of the 8600 Smart Routers in use, please refer to the relevant product document program on the Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking > 8600 Smart Routers> Technical Documentation The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated © 2015 Coriant All rights reserved This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied Users must take full responsibility for their application of any products Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 8600 Smart Routers Routing Protocols Configuration Guide 76.8600-50121H © 2015 Coriant Document Information Terms and Abbreviations 76.8600-50121H © 2015 Coriant Term Explanation ABR Area Border Router AFI Authority and Format Identifier ARP Address Resolution Protocol AS Autonomous System ASBR Autonomous System Border Router BFD Bidirectional Forwarding Detection BGP Border Gateway Protocol CDC Control and DC Power Card CLI Command Line Interface CPU Central Processing Unit CSPF Constrained Shortest Path First DCN Data Communications Network DD Database Description DiffServ Differentiated Services DR Designated Router eBGP External Border Gateway Protocol ECMP Equal Cost Multipath EGP Exterior Gateway Protocol ELP Ethernet Layer Protection ES-IS End System to Intermediate System iBGP Internal Border Gateway Protocol ICMP Internet Control Message Protocol IFC Interface Module Concentrator IFM Interface Module IGP Interior Gateway Protocol IIH IS-IS Hello IP Internet Protocol IRB Integrated Routing and Bridging IS-IS Intermediate System to Intermediate System LAG Link Aggregation LAN Local Area Network LDP Label Distribution Protocol LSA Link State Advertisement 8600 Smart Routers Routing Protocols Configuration Guide Document Information LSP Label Switched Path LSP Link State Packet LU1 Line Unit in 8665 Smart Router MAC Media Access Control MDA Message Digest Authentication MED Multi Exit Discriminator MPLS Multiprotocol Label Switching NBMA Non-Broadcast Multiaccess NET Network Entity Title NSAP Network Service Access Point NSEL NSAP selector NSSA Not-So-Stubby Area ORF Outbound Route Filter OSPF Open Shortest Path First QoS Quality of Service RFC Request For Comments (IETF documents) RFD Route Flap Damping RIB Routing Information Base RID Router ID RR Route Reflector RSVP-TE Resource Reservation Protocol with Traffic Engineering Extensions RT Route Target SAFI Subsequent Address Family Identifier SCM Switching and Control Module SLA Service Level Agreement SPF Shortest Path First SOO Site of Origin TCP Transmission Control Protocol TE Traffic Engineering TED Traffic Engineering Database TLV Type Length Value VLAN Virtual LAN VPN Virtual Private Network VRF Virtual Routing and Forwarding VRRP Virtual Router Redundancy Protocol 8600 Smart Routers Routing Protocols Configuration Guide 76.8600-50121H © 2015 Coriant Table of Contents Table of Contents About This Manual 11 Objectives 11 Audience 11 8600 Smart Routers Technical Documentation .11 Interface Numbering Conventions 15 Documentation Feedback 15 8600 Smart Routers Discontinued Products 16 OSPF 17 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Overview 17 OSPF Hierarchical Routing 17 1.2.1 Autonomous System 17 1.2.2 Areas 18 OSPF Hello Messages and Link State Advertisements 18 Extensions for Support of Differentiated Services-Aware MPLS Traffic Engineering 19 OSPF Graceful Restart 19 Fast OSPF Adjacency Establishment 19 OSPF Unnumbered Links 20 OSPF References 21 OSPF Configuration Examples 22 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Basic Configuration 22 Interface Configuration 22 Area Configuration 23 OSPF Authentication 23 TE Configuration 24 Graceful Restart Configuration 24 Fast OSPF Convergence 25 Fast OSPF Adjacency Establishment Configuration 26 2.8.1 Enabling Hello replies 26 2.8.2 Designated Router (DR) Wait Time Configuration 27 2.9 OSPF Unnumbered Links Configuration 29 2.10 OSPF Status 29 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide Table of Contents Border Gateway Protocol 31 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 Overview 31 Router ID 34 BGP Attributes 35 3.3.1 ORIGIN Attribute 36 3.3.2 AS PATH Attribute 36 3.3.3 NEXT HOP Attribute 37 3.3.4 LOCAL PREFERENCE Attribute 38 3.3.5 ATOMIC AGGREGATE Attribute 39 3.3.6 COMMUNITY Attribute 39 3.3.7 AGGREGATOR Attribute 40 3.3.8 MED Attribute 41 Managing Route Preferences 42 BGP Routing Policy 43 3.5.1 Route Map 44 Route Aggregation 46 3.6.1 Configuration Parameters 48 3.6.2 BGP IP VPN Route Aggregation 48 3.6.3 Route Aggregation Support 49 Route Flap Damping 50 3.7.1 RFD Configuration 51 Route Refresh 52 Increasing AS Scalability 52 3.9.1 Route Reflector 52 3.9.2 AS Confederation 54 BGP Failover 55 3.10.1 iBGP and Multihop eBGP Sessions 55 3.10.2 Single Hop eBGP 56 3.10.3 Performance of BGP Failover 57 BGP Multiprotocol Extensions 57 3.11.1 BGP Labeled Unicast 57 BGP Multipath 57 3.12.1 Limitations and Restrictions 59 BGP References 60 BGP Configuration Examples 61 4.1 4.2 4.3 Basic Configurations 61 4.1.1 BGP Peers Configuration 62 4.1.2 BGP Routing Policy Configuration 66 4.1.3 BGP Authentication 68 4.1.4 BGP Connection Reset 68 Route Aggregation Configuration 69 4.2.1 NODE-1 Configuration 69 4.2.2 NODE-2 Configuration 70 4.2.3 Configuration Status 70 4.2.4 Configuration with Suppression Disabled 71 Advanced Configurations 72 4.3.1 Route Reflector Configuration 72 4.3.2 Configuring AS Confederation 76 8600 Smart Routers Routing Protocols Configuration Guide 76.8600-50121H © 2015 Coriant Table of Contents IS-IS 80 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 Overview 80 Routing Areas 80 Addressing 81 Multihoming 82 Multiarea Routing 82 Open Shortest Path Algorithm 83 Adjacencies and Hello Packets 83 Link-State Database and Link-State Packets 83 Route Summarization 83 Route Redistribution 84 5.10.1 Redistribution of Static and IGP Routes 84 5.10.2 IS-IS Routes Redistribution from L2 to L1 84 5.10.3 Redistribution between IS-IS L1 to L1 Instances 85 5.11 Authentication 87 5.12 Extensions for Support of Differentiated Services-Aware MPLS Traffic Engineering 87 5.13 IS-IS References 87 IS-IS Configuration Examples 88 6.1 6.2 6.3 6.4 Bidirectional Forwarding Detection 96 7.1 7.2 7.3 7.4 IS-IS Basic Configuration 88 6.1.1 IS-IS Process Configuration 89 6.1.2 IS-IS Interface Configuration 89 IS-IS Area Configuration 90 6.2.1 Router Configuration 91 6.2.2 Router Configuration 92 6.2.3 Router Configuration 92 Fast IS-IS Convergence 93 IS-IS L1 to L1 Route Redistribution Configuration 94 6.4.1 Configuration Summary 94 6.4.2 Configuring Routes Redistribution 94 Overview 96 BFD in Dynamic Routing 97 BFD in Static Routing 98 BFD References 98 BFD Configuration Examples 99 8.1 8.2 76.8600-50121H © 2015 Coriant BFD Configuration with Routing Protocols 99 8.1.1 OSPF 99 8.1.2 IS-IS 99 8.1.3 RSVP-TE 100 8.1.4 Single Hop BGP 100 BFD Configuration for Static Routes 103 8600 Smart Routers Routing Protocols Configuration Guide Table of Contents 8.2.1 BFD Status 104 Equal Cost Multipath (ECMP) 106 9.1 9.2 9.3 Overview 106 ECMP Network Application 106 ECMP Operation 107 9.3.1 Dynamic Routing 107 9.3.2 Static Routing 108 9.3.3 Forwarding Plane Functions 108 9.3.4 Scalability 109 10 Virtual Router Redundancy Protocol 110 10.1 Introduction 110 10.2 Operation 110 10.2.1 VRRP Parameters .112 10.2.2 VRRP Timers 113 10.3 VRRP Supported Features 115 10.3.1 VRRP Configuration 115 10.3.2 VRRP Object Tracking .116 10.3.3 VRRP with IRB 117 10.3.4 VRRP Accept Data 118 10.4 VRRP Faults .118 10.5 VRRP References .118 11 VRRP CLI Configuration Examples 119 11.1 VRRP Configuration 119 11.1.1 Router–1 Configuration 120 11.1.2 Router–2 Configuration 121 11.2 VRRP with IRB Configuration 122 11.3 VRRP Status 124 8600 Smart Routers Routing Protocols Configuration Guide 10 76.8600-50121H © 2015 Coriant 10 Virtual Router Redundancy Protocol Fig 41 VRRP Switchover Fig 41 presents a situation where Router-1 loses connection to the Ethernet switch In this case, Router-2 will automatically switch to be the master and forward traffic After VRRP mastership transition, the Ethernet switch will be notified by gratuitous ARP message sent by Router-2 This allows Ethernet switches with learning capabilities to update their MAC forwarding tables On the other hand, Ethernet switches without learning capabilities, they always send traffic to both routers connected, thus traffic is not affected by switchover Gratuitous ARP messages not affect RNC because the IP address and MAC address not change The Ethernet switches shown in the examples above can be replaced by internal switching capability of either RNC or the 8660 Smart Router (see 10.3.3 VRRP with IRB) 10.2.1 VRRP Parameters The preemption parameter is used to control a mastership transition of the backup router, or to prevent a backup router to assume a mastership role With the preemption parameter, it is possible to overwrite the default skew_time (see 10.2.2 VRRP Timers), or to disable preemption (i.e mastership transition based on the priorities) The default behavior is immediate takeover, which means that previously defined skew_time rule is obeyed With the option ”no preemption” set, a mastership is not transferred as long as the master is active The option “fast preemption” can be used to skip the preemption_time (including skew_time) entirely, which will make the transition to master role faster, but it should be used only if the VRRP group has no more than two VRRP routers Unless the “fast preemption” option is used, specified preemption_time is in addition of the skew_time In practice, when a neighbor decrements own priority, it is because of object tracking (see 10.3.2 VRRP Object Tracking) In this case, it is desired that the mastership transition happens as soon as possible Therefore, if the decrease in neighbor's priority leads to preemption, then the preemption_time is skipped Also, it is possible to disable preemption_time skipping by using parameter wait_on_decrement, which will revert back to the behavior defined by [RFC3768] 8600 Smart Routers Routing Protocols Configuration Guide 112 76.8600-50121H © 2015 Coriant 10 Virtual Router Redundancy Protocol VRRP group priority is defined in a range 254 with default 100 and the router with the highest VRRP group priority is the master If the interface IP address is the same as the virtual IP address of the VRRP group, then the router is considered to be the address owner The priority of the address owner is always 255 The virtual IP address can be assigned freely However, it should be derived from a subnet the interface is connected, to allow VRRP to operate correctly The VRRP group advertisement interval is defined in a range 10 (default is second) Longer interval can be used to decrease traffic and load to the system that is caused by VRRP advertisement messages This might be useful in cases where there are many VRRP sessions active simultaneously The same advertisement interval value must be set to all routers within the same VRRP group Multiple VRRP instances can be configured to a single interface or VLAN as long as each instance has a different VRRP ID This can be used to achieve simple load sharing by using different virtual IP addresses for different routes However, VRRP by itself does not have load sharing capabilities VRRP groups are specific to a port or VLAN interface and can be reused on multiple VLANs The delay_after_init parameter is used to add a delay for VRRP mastership transition after an initialization of the VRRP session This parameter is mainly to address possible issues when an interface where VRRP is configured comes up before a connectivity to the master is established In this situation, advertisements are not received, therefore preemption timer cannot be started and as result the backup router takes the mastership role This issue might occur during the boot up, when VRRP is used with IRB and the IRB interface comes up before the physical interfaces, see 10.3.3 VRRP with IRB 10.2.2 VRRP Timers VRRP uses different timers to control the mastership transitions These timers cannot be directly set but are controlled by VRRP parameters described in this chapter and in 10.2.1 VRRP Parameters A master_down_interval is used to define a time the backup router(s) must wait for an advertisement from the master before declaring that the master is no longer active The master_down_interval is calculated as follows: master_down_interval = 3*advertisement_interval + skew_time A timer called master_down_timer is used to track master_down_interval When an advertisement is received from the master the master_down_timer is reset to the master_down_interval and the timer starts to countdown If the master_down_timer reaches zero before the next reset by an advertisement, then the backup router will declare that the master is not active Due to the fact that backup routers not communicate with other routers there is a short period of time when multiple routers can assume master role simultaneously This situation can cause duplication of traffic It is also possible that the router with the highest priority will not be the first to switch to mastership role To avoid this problem, a parameter known as skew_time is introduced It is a period of time in seconds that is waited before a router switches to a master role, after it has noticed that the master is no longer active skew_time = [(256 - priority)/256] seconds 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 113 10 Virtual Router Redundancy Protocol The preemption_time defines the time a backup router must wait before assuming the mastership role, if the current master has lower priority The preemption_time is used to ensure that a router has enough time to create stable upstream connections, before it can assume mastership role The preemption parameter can be used to define the preemption_time When a backup router notices that it has higher priority than the master, a new preemption_timer is scheduled with a value defined by preemption_time A mastership role will be assumed after the preemption_timer expires The following table presents the starting conditions and initial timer values of a VRRP backup router Event Master_Down_Timer Reset to Preemption_Timer Scheduled Interface up delay_after_init + master_down_interval — Normal advertisement received master_down_interval — Neighbor seen the first time (0 priority set) Normal preemption  MAX(remaining_value, skew_time) — Fast preemption  — Neighbor seen the first time (better priority set) master_down_interval (clears delay_after_init) — Neighbor seen the first time (worse priority set) master_down_interval (clears delay_after_init) Normal preemption  preemption_time + remaining master_down_timer Fast preemption  preemption_time Normal preemption  MAX(remaining_value, skew_time) — Fast preemption  — Neighbor modified priority (better priority set) master_down_interval — Neighbor modified priority (worse priority set) master_down_interval Normal preemption  remaining master_down_timer Neighbor modified priority (0 priority set) Fast preemption  wait_on_decrement  preemption_time + remaining master_down_timer Object tracking uses own delay timer, which can be used to dampen flapping on the tracked objects Object tracking is described in 10.3.2 VRRP Object Tracking Object Tracking Event Description State change in tracked object Start/restart tracking_delay timer Tracking delay timer ready Modify priority, send advertisement with new priority 8600 Smart Routers Routing Protocols Configuration Guide 114 76.8600-50121H © 2015 Coriant 10 Virtual Router Redundancy Protocol 10.3 VRRP Supported Features 10.3.1 VRRP Configuration In the 8600 NEs, VRRP is implemented according to [RFC3768] specifications VRRP is only supported on Ethernet interfaces of the following NEs: • 8615 Smart Router • 8615 Smart Router stacked • IFC2 line card (8630 Smart Router, 8660 Smart Router) • ELC1 line card (8630 Smart Router, 8660 Smart Router) • LU1 (8665 Smart Router) Interface Configuration VRRP Support Interface Configuration 8615 Smart Router 8615 Smart Router Stacked ELC1 IFC2 Line Card LU1 Port Yes Yes Yes Yes Yes VLAN Yes Yes Yes Yes Yes QinQ — — — — — With Virtual Routing and Forwarding (VRF) Yes Yes Yes Yes Yes With Integrated Routing and Bridging (IRB) Yes Yes Yes Yes Yes With Link Aggregation (LAG) Yes Yes Yes Yes Yes6 With Ethernet Layer Protection (ELP) — Yes Yes Yes Yes6 VRRP authentication, VRRP with IPv6 addresses and Multiple virtual IP addresses on one VRRP group are not supported Only with 10GBASE-R/1000BASE-X 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 115 10 Virtual Router Redundancy Protocol 10.3.2 VRRP Object Tracking VRRP by itself is unable to detect failures in upstream connections This is because VRRP communicates only with the LAN that it is directly connected For example, in case shown in Fig 40, if Router-1 loses connection to the cell site, then Router-2 would be better choice to be the master However, the connection between Router-1 and Router-2 would still operational and there would be no mastership transition Object tracing is implemented to address this issue, it allows VRRP to track the state of interfaces, track presence of routes in RIB and track the state of arbitrary Bidirectional Forward Detection (BFD) sessions In case of a failure, the VRRP group priority can be reduced by a predefined amount That amount must be set in object tracking configuration, and it is defined in a range of 255 Object tracking can be also used to monitor the current master This is useful because mastership transition takes quite long time if it relies only on VRRP advertisement messages Typical hello interval is one second, therefore, it can take up to seconds plus skew_timefor mastership transition This time can be reduced significantly when object tracking is used For this type of tracking a special neighborhood tracking feature is supported, which allows a router to track single neighbor and assume mastership immediately when the tracked neighbor becomes inactive Tracking delay option can also be used to add additional dampening to tracking This adds a timer (tracking_delay), which is started whenever a change occurs on tracked object and a new priority is evaluated only after this timer expires The tracking_delay timer operates as follows: The timer starts with, tracking_delay = A When subsequent changes occur new timer is scheduled with an increment “N” based on, tracking_delay = MIN(A+B*2^(N-1), C) Where: • A - is initial delay; • B - is multiplier; • C - is the maximum delay Each parameter above has to be given when this option is set The timers are reset when a period of twice the maximum delay is elapsed without changes When using directly connected routes and a L2 Ethernet switching in the upstream side (Fig 40 PSN side), it is possible to get into a situation where ARP either has not yet been resolved, or has already expired on the backup router when a mastership switchover is performed This can happen when there is no traffic flowing trough the backup router and this might lead to traffic break for several seconds after transition to master role This behavior can be avoided by either using static ARP entries, or by ensuring that there is a periodic traffic Periodic traffic can be generated using for example BFD with long interval (several seconds) 8600 Smart Routers Routing Protocols Configuration Guide 116 76.8600-50121H © 2015 Coriant 10 Virtual Router Redundancy Protocol 10.3.3 VRRP with IRB Since VRRP operates only in single LAN, it requires at least one switch to operate The 8630 Smart Router, 8660 Smart Router and 8665 Smart Router can be used to implement the switching functionality by using Integrated Routing and Bridging (IRB) This is useful if an external switch is not available and the RNC does not have internal switching capability either If additional switches are already present, there is a risk of creating Ethernet loops within IRB In such case, an extra care must be exercised to avoid loops Fig 42 VRRP with IRB An application example where IRB should be used is shown in Fig 42 In this case, the RNC does not have an internal switching capability IRB can be configured to both routers to add the required switching functionality In that case, VRRP will be operating on the logical IRB interface For more details about IRB, please refer to 8600 Smart Routers Ethernet Configuration Guide When VRRP is configured to an IRB interface, it is possible to get into a situation where the IRB interface comes up before the connected physical interfaces In this case, the VRRP instance cannot communicate with the neighboring node and assumes mastership role If the neighboring node has a higher priority, this will lead to an unnecessary mastership role transition(s) To prevent this behavior, there is a CLI command option “delay_after_init” that sets a delay for the transition to master role when a VRRP session is initialized 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 117 10 Virtual Router Redundancy Protocol 10.3.4 VRRP Accept Data By the standard definition routers not accept data with destination to a virtual IP address This makes it impossible to receive Internet Control Message Protocol (ICMP) requests destined to a virtual IP addresses However, in some cases ICMP packets are useful for verifying connectivity In such cases, accept data option can be enabled to allow the current master to reply ICMP echo requests 10.4 VRRP Faults Fault Name Description State transition from backup to master VRRP generates delta fault when transition from backup to master occurs This is done due to the fact that such transitions are typically an indication of some problems in the master router Conflict in VRRP configuration All routers in the same VRRP group share the same configuration and when a conflict is detected, a fault is raised These faults are generated in the backup routers, when they receive VRRP advertisement messages that conflict with the backup routers own configuration Tracked object down This fault is generated when tracked object goes down 10.5 VRRP References Reference Description [RFC3768] RFC3768 (2004–04), Virtual Router Redundancy Protocol (VRRP) 8600 Smart Routers Routing Protocols Configuration Guide 118 76.8600-50121H © 2015 Coriant 11 VRRP CLI Configuration Examples 11 VRRP CLI Configuration Examples It is advisable to always refer to 8600 Smart Routers CLI Commands Manual for the latest information on: • Default values to avoid unnecessary configuration; • Available configuration options and parametric range 11.1 VRRP Configuration This chapter provides VRRP CLI configuration examples The configuration scenario used is depicted in Fig 43 Fig 43 VRRP Configuration Topology In Fig 43, two VRRP groups will be created with two different types of object tracking The configuration for both VRRP routers is identical, with only exception of VRRP group priorities assignment that are different 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 119 11 VRRP CLI Configuration Examples The VRRP group 10 in Router–1 is used to route traffic from RNC with gateway address 1.1.1.10 to the PSN VRRP group priority is configured to 150 and Router–1 will be the master for VRRP group 10 because Router–2 has lower priority assigned for the group Object tracking will be used to monitor the interface connected to the PSN network If state of the interface goes down, priority of the VRRP group will be decreased and that will lead to mastership transition VRRP group 11 is configured to have lower priority in Router–1 than in Router–2 Thus Router–1 will act as a backup for gateway 1.1.1.11 Router–1 will become a master if Router–2 becomes inactive or the connection between RNC and Router–2 is lost BFD tracking is used to react as fast as possible to the failure 11.1.1 Router–1 Configuration VRRP group 10 configuration Step Create a VRRP group with an ID 10 and priority 150 This will be the master session for traffic using the default gateway address 1.1.1.10 There may be several different VRRP group instances with different IP address under any interface VRRP group ID is unique only under the interface where it is defined router-1(config)# interface ge 11/1/0 router-1(cfg-if[ge11/1/0])# ip vrrp 10 1.1.1.10 priority 150 Step Set preemption mode to fast Default is immediate takeover router-1(cfg-if[ge11/1/0])# ip vrrp 10 preempt fast Step Enable VRRP ICMP echo requests to the VRRP group router-1(cfg-if[ge11/1/0])# ip vrrp 10 accept-data Step Create second tracking object instance to monitor interface state towards the PSN Start interface tracking Note there can be many track statements in any VRRP group By default tracking is not enabled router-1(cfg-if[ge11/1/0])# track track2 router-1(cfg-track[track2])# target interface ge 11/1/1 Step Track interface and decrease priority by 60 in case of failure The decrement interval is defined in range 255 In this example, when a failure occur VRRP group priority will be decreased from 150 to 90 and a backup session can switch to master state if it has priority lower than 90 router-1(cfg-track[track2])# interface ge 11/1/0 router-1(cfg-if[ge11/1/0])# ip vrrp 10 track track2 decrement 60 8600 Smart Routers Routing Protocols Configuration Guide 120 76.8600-50121H © 2015 Coriant 11 VRRP CLI Configuration Examples VRRP group 11 configuration Step Create a VRRP group with an ID 11 and priority 95 This will be the backup session for traffic using the default gateway address 1.1.1.11 router-1(config)# interface ge 11/1/0 router-1(cfg-if[ge11/1/0])# ip vrrp 11 1.1.1.11 priority 95 Step Set preemption mode to fast router-1(cfg-if[ge11/1/0])# ip vrrp 11 preempt fast Step Enable VRRP ICMP echo requests to the VRRP group router-1(cfg-if[ge11/1/0])# ip vrrp 11 accept-data Step Start BFD session towards other VRRP router router-1(cfg-if[ge11/1/0])# ip bfd 1.1.1.1 Step Create tracking object instance router-1(cfg-if[ge11/1/0])# track track1 Step Tracking object is bound to BFD session router-1(cfg-track[track1])# target ip bfd ge 11/1/0 1.1.1.1 router-1(cfg-track[track1])# exit Step Enable VRRP neighbor tracking router-1(cfg-track[track1])# interface ge 11/1/0 router-1(cfg-if[ge11/1/0])# ip vrrp 11 track track1 neighbor 1.1.1.1 11.1.2 Router–2 Configuration VRRP group 10 configuration: Step Create a VRRP group with an ID 10 and assign priority 95 This will be the backup session for traffic using the default gateway address 1.1.1.10 router-2(config)# interface ge 6/0/0 router-2(cfg-if[ge6/0/0])# ip vrrp 10 1.1.1.10 priority 95 Step Set preemption mode to fast router-2(cfg-if[ge6/0/0])# ip vrrp 10 preempt fast Step Enable VRRP ICMP echo requests to the VRRP group router-2(cfg-if[ge6/0/0])# ip vrrp 10 accept-data Step Start BFD session towards other VRRP router router-2(cfg-if[ge6/0/0])# ip bfd 1.1.1.2 Step Create a tracking object instance and set the target interface bound to BFD session router-2(cfg-if[ge6/0/0])# track track1 router-2(cfg-track[track1])# target ip bfd ge 6/0/0 1.1.1.2 Step Enable monitoring VRRP neighbor router-2(cfg-track[track1])# interface ge 6/0/0 router-2(cfg-if[ge6/0/0])# ip vrrp 10 track track1 neighbor 1.1.1.2 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 121 11 VRRP CLI Configuration Examples VRRP group 11 configuration Step Create a VRRP group 11 and assign priority 150 This will be the master session for traffic using the default gateway address 1.1.1.11 router-2(cfg-if[ge6/0/0])# ip vrrp 11 1.1.1.11 priority 150 Step Set preemption mode router-2(cfg-if[ge6/0/0])# ip vrrp 11 preempt fast Step Enable VRRP ICMP echo requests to the VRRP group router-2(cfg-if[ge6/0/0])# ip vrrp 11 accept-data Step Create tracking object instance router-2(cfg-if[ge6/0/0])# track track2 router-2(cfg-track[track2])# Step Set the target interface of the tracked object router-2(cfg-track[track2])# target interface ge 6/0/1 router-2(cfg-track[track2])# interface ge 6/0/0 router-2(cfg-if[ge6/0/0])# Step Enable tracking object to the VRRP group and set the priority decrement interval router-2(cfg-if[ge6/0/0])# ip vrrp 11 track track2 decrement 60 11.2 VRRP with IRB Configuration This chapter provides an example of how to configure VRRP with IRB When VRRP is used with IRB, an additional IRB interface configuration is required and the details of IRB configuration are covered in 8600 Smart Routers Ethernet Applications Configuration Guide 8600 Smart Routers Routing Protocols Configuration Guide 122 76.8600-50121H © 2015 Coriant 11 VRRP CLI Configuration Examples Fig 44 VRRP with IRB Configuration Topology To accomplish this configuration, the following steps are required: • Create a bridging instance • Set the IRB forwarding-mode flexible in the case ELC1 line card is used • Binding the bridging instance to an interface(s) • Configure an IRB interface • Create a VRRP group IFC2 line card based IRB configuration flow is covered in this example Router-1 configuration: Step Create a bridging instance with an ID router-1(config)# bridging-instance bridge1 10 router-1(cfg-bridge-inst[10])# Step Bind the bridging instance to interface ge11/1/0 router-1(cfg-bridge-inst[10])# interface ge 11/1/0 router-1(cfg-if[ge11/1/0])# bridging bridging-instance bridge1 router-1(cfg-if[ge11/1/0])# no shutdown router-1(cfg-if[ge11/1/0])# exit Step Bind the bridging instance to interface ge11/1/1 router-1(cfg-bridge-inst[10])# interface ge 11/1/1 router-1(cfg-if[ge11/1/1])# bridging bridging-instance bridge1 router-1(cfg-if[ge11/1/1])# no shutdown 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 123 11 VRRP CLI Configuration Examples Step Configure an IRB interface router-1(cfg-if[ge11/1/1])# interface irb10 router-1(cfg-if[irb10])# ip address 1.1.1.2/24 router-1(cfg-if[irb10])# no shutdown Step Create a VRRP group with an ID and priority router-1(cfg-if[irb10])# ip vrrp 10 1.1.1.10 priority 150 Step Wait minutes (300000 ms) after the VRRP initialization before mastership role can be assumed router-1(cfg-if[irb10])# ip vrrp 10 delay-after-init 300000 Router-2 configuration: Step Create a bridging instance with an ID router-2(config)# bridging-instance bridge1 10 router-2(cfg-bridge-inst[10])# Step Bind the bridging instance to interface ge6/0/0 router-2(cfg-bridge-inst[10])# interface ge 6/0/0 router-2(cfg-if[ge6/0/0])# bridging bridging-instance bridge1 router-2(cfg-if[ge6/0/0])# no shutdown router-2(cfg-if[ge6/0/0])# exit Step Bind the bridging instance to interface ge6/0/1 router-2(cfg-bridge-inst[10])# interface ge 6/0/1 router-2(cfg-if[ge6/0/1])# bridging bridging-instance bridge1 router-2(cfg-if[ge6/0/1])# no shutdown Step Configure an IRB interface router-2(cfg-if[ge6/0/1])# interface irb10 router-2(cfg-if[irb10])# ip address 1.1.1.1/24 router-2(cfg-if[irb10])# no shutdown Step Create a VRRP group with an ID and priority router-2(cfg-if[irb10])# ip vrrp 10 1.1.1.10 priority 95 Step Wait minutes (300000 ms) after the VRRP initialization before mastership role can be assumed router-2(cfg-if[irb10])# ip vrrp 10 delay-after-init 300000 11.3 VRRP Status VRRP status can be inspected by using any of the commands outlined in the following table Command Description show ip vrrp interface The command displays local VRRP interface status show ip vrrp interface ge11/1/0 The command displays status of the specified VRRP interface show ip vrrp interface ge11/1/0 vrid 10 The command displays status of the specified VRRP interface group ID show ip vrrp interface ge 11/1/0 log The command displays recent log events of the specified VRRP interface 8600 Smart Routers Routing Protocols Configuration Guide 124 76.8600-50121H © 2015 Coriant 11 VRRP CLI Configuration Examples Command Description show track The command displays information about the current state of the tracking object show track track1 The command displays information about the state of the specified tracking object show track track1 log The command displays latest log events of the tracking object of interest The following figures illustrate some examples of what VRRP status of the configuration depicted in Fig 43 Fig 45 VRRP Status Fig 46 VRRP Interface Status 76.8600-50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 125 11 VRRP CLI Configuration Examples Fig 47 VRRP Specific Interface Status Fig 48 VRRP Tracking Object Status 8600 Smart Routers Routing Protocols Configuration Guide 126 76.8600-50121H © 2015 Coriant ... and/or other countries 76. 8600- 50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 8600 Smart Routers Routing Protocols Configuration Guide 76. 8600- 50121H © 2015 Coriant... fi-documentation@tellabs.com 76. 8600- 50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 15 8600 Smart Routers Discontinued Products 8600 Smart Routers Discontinued Products 8600 Smart Routers. .. 76. 8600- 50121H © 2015 Coriant 8600 Smart Routers Routing Protocols Configuration Guide 29 OSPF Configuration Examples Fig OSPF Parameters and Statistics 8600 Smart Routers Routing Protocols Configuration