Page 1 Part No. 060320-10, Rev. B March 2011 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide www.alcatel-lucent.com OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 2 This user guide documents Release 7.1.1 of OmniSwitch 10000 The functionality described in this guide is subject to change without notice. Copyright © 2011 by Alcatel-Lucent. All rights reserved. This document may not be reproduced in whole or in part without the express written permission of Alcatel-Lucent.
Page 3: Table Of Contents
Contents About This Guide ......................xi Supported Platforms ......................xi Who Should Read this Manual? ..................xi When Should I Read this Manual? ..................xi What is in this Manual? ..................... xi What is Not in this Manual? ..................... xii How is the Information Organized? .................
Page 4 Contents Configuring Router Capabilities ................1-29 Configuring Static Neighbors .................1-30 Configuring Redundant CMMs for Graceful Restart ..........1-31 OSPF Application Example ..................1-32 Step 1: Prepare the Routers ................1-33 Step 2: Enable OSPF ..................1-34 Step 3: Create the Areas and Backbone ............1-34 Step 4: Create, Enable, and Assign Interfaces ..........1-35 Step 5: Examine the Network ................1-36 Verifying OSPF Configuration ..................1-37 Chapter 2...
Page 5 Contents Autonomous Systems (ASs) ..................3-6 Internal vs. External BGP ..................3-7 Communities ......................3-8 Route Reflectors .......................3-9 BGP Confederations ....................3-11 Policies ........................3-12 Regular Expressions ..................3-13 Route Dampening ....................3-16 CIDR Route Notation .....................3-16 BGP Configuration Overview ..................3-17 Starting BGP .........................3-18 Disabling BGP ......................3-18 Setting Global BGP Parameters ..................3-20 Setting the Router AS Number ................3-21 Setting the Default Local Preference ..............3-21...
Page 6 Contents Routing Policies ......................3-45 Creating a Policy ....................3-45 Assigning a Policy to a Peer ...................3-50 Displaying Policies ....................3-52 Configuring Redistribution ...................3-53 Using Route Maps ...................3-53 Configuring Route Map Redistribution ............3-57 Route Map Redistribution Example ..............3-58 Configuring Redundant CMMs for Graceful Restart ..........3-59 Application Example .....................3-60 AS 100 ......................3-60 AS 200 ......................3-61...
Page 7 Contents Multicast Address Boundaries .................4-5 Concurrent Multicast Addresses ................4-6 Configuring Multicast Address Boundaries ..............4-7 Basic Multicast Address Boundary Configuration ...........4-7 Creating a Multicast Address Boundary ..............4-7 Deleting a Multicast Address Boundary ..............4-7 Verifying the Multicast Address Boundary Configuration ..........4-8 Application Example for Configuring Multicast Address Boundaries ......4-8 Chapter 5 Configuring DVMRP ....................
Page 8 Contents PIM-Sparse Mode (PIM-SM) ...................6-8 Rendezvous Points (RPs) ..................6-8 Bootstrap Routers (BSRs) .................6-9 Designated Routers (DRs) .................6-9 Shared (or RP) Trees ..................6-9 Avoiding Register Encapsulation ..............6-12 PIM-Dense Mode (PIM-DM) .................6-12 RP Initiation of (S, G) Source-Specific Join Message ...........6-13 SPT Switchover ......................6-15 PIM-SSM Support ....................6-17 Source-Specific Multicast Addresses ..............6-17 Configuring PIM ......................6-18...
Page 9 Verifying IPv6 PIM Configuration ................6-43 Appendix A Software License and Copyright Statements ............. A-1 Alcatel-Lucent License Agreement ................A-1 ALCATEL-LUCENT SOFTWARE LICENSE AGREEMENT ......A-1 Third Party Licenses and Notices .................. A-4 Index ........................Index-1 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide...
Page 10 Contents OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 11: About This Guide
About This Guide This OmniSwitch AOS Release 7 Advanced Routing Configuration Guide describes how to set up and monitor advanced routing protocols for operation in a live network environment. The routing protocols described in this manual are purchased as an add-on package to the base switch software. Supported Platforms The information in this guide applies only to OmniSwitch 10K switches.
Page 12: What Is Not In This Manual
What is Not in this Manual? About This Guide What is Not in this Manual? The configuration procedures in this manual use Command Line Interface (CLI) commands in all exam- ples. CLI commands are text-based commands used to manage the switch through serial (console port) connections or via Telnet sessions.
Page 13: Documentation Roadmap
About This Guide Documentation Roadmap Documentation Roadmap The OmniSwitch user documentation suite was designed to supply you with information at several critical junctures of the configuration process.The following section outlines a roadmap of the manuals that will help you at each stage of the configuration process. Under each stage, we point you to the manual or manuals that will be most helpful to you.
Page 14 Documentation Roadmap About This Guide Anytime The OmniSwitch CLI Reference Guide contains comprehensive information on all CLI commands supported by the switch. This guide includes syntax, default, usage, example, related CLI command, and CLI-to-MIB variable mapping information for all CLI commands supported by the switch. This guide can be consulted anytime during the configuration process to find detailed and specific information on each CLI command.
Page 15: Related Documentation
OmniSwitch Transceivers Guide Includes SFP and XFP transceiver specifications and product compatibility information. • Technical Tips, Field Notices Includes information published by Alcatel’s Customer Support group. • Release Notes Includes critical Open Problem Reports, feature exceptions, and other important information on the features supported in the current release and any limitations to their support.
Page 16: Technical Support
With 24-hour access to Alcatel-Lucent’s Service and Support web page, you’ll be able to view and update any case (open or closed) that you have reported to Alcatel-Lucent’s technical support, open a new case or access helpful release notes, technical bulletins, and manuals.
Page 17: Chapter 1 Configuring Ospf
1 Configuring OSPF Open Shortest Path First routing (OSPF) is a shortest path first (SPF), or link state, protocol. OSPF is an interior gateway protocol (IGP) that distributes routing information between routers in a single Autono- mous System (AS). OSPF chooses the least-cost path as the best path. OSPF is suitable for complex networks with large numbers of routers since it provides faster convergence where multiple flows to a single destination can be forwarded on one or more interfaces simultaneously.
Page 18: Ospf Specifications
OSPF Specifications Configuring OSPF OSPF Specifications Platforms Supported OmniSwitch 10K RFCs Supported 1370—Applicability Statement for OSPF 1850—OSPF Version 2 Management Information Base 2328—OSPF Version 2 2370—The OSPF Opaque LSA Option 3101—The OSPF Not-So-Stubby Area (NSSA) Option 3623—Graceful OSPF Restart Maximum number of Areas Maximum number of Interfaces Maximum number of Link State Database 100K...
Page 19: Ospf Defaults Table
Configuring OSPF OSPF Defaults Table OSPF Defaults Table The following table shows the default settings of the configurable OSPF parameters: Parameter Description Command Default Value/Comments Enables OSPF. ip ospf admin-state disabled Enables an interface. ip ospf interface admin-state disabled Sets the overflow interval value. ip ospf exit-overflow-interval Assigns a limit to the number of ip ospf extlsdb-limit...
Page 20: Ospf Quick Steps
OSPF Quick Steps Configuring OSPF OSPF Quick Steps The followings steps are designed to show the user the necessary set of commands for setting up a router to use OSPF: Create a VLAN using the vlan command. For example: -> vlan 5 ->...
Page 21 Configuring OSPF OSPF Quick Steps Enable the OSPF interfaces using the ip ospf interface admin-state command. For example: -> ip ospf interface vlan-5 admin-state enable You can now display the router OSPF settings by using the show ip ospf command. The output gener- ated is similar to the following: ->...
Page 22: Interface Status
OSPF Quick Steps Configuring OSPF You can display OSPF area settings using the show ip ospf area command. For example: -> show ip ospf area 0.0.0.0 Area Identifier = 0.0.0.0, Area ID Admin Status = Enabled, As set in Step 6 Operational Status = Up, Area Type...
Page 23: Ospf Overview
Configuring OSPF OSPF Overview OSPF Overview Open Shortest Path First routing (OSPF) is a shortest path first (SPF), or link-state, protocol. OSPF is an interior gateway protocol (IGP) that distributes routing information between routers in a Single Autono- mous System (AS). OSPF chooses the least-cost path as the best path. Each participating router distributes its local state (i.e., the router’s usable interfaces, local networks, and reachable neighbors) throughout the AS by flooding.
Page 24: Ospf Areas
OSPF Overview Configuring OSPF OSPF Areas OSPF allows collections of contiguous networks and hosts to be grouped together as an area. Each area runs a separate copy of the basic link-state routing algorithm (usually called SPF). This means that each area has its own topological database, as explained in the previous section.
Page 25: Classification Of Routers
Configuring OSPF OSPF Overview Classification of Routers When an AS is split into OSPF areas, the routers are further divided according to function into the follow- ing four overlapping categories: • Internal routers. A router with all directly connected networks belonging to the same area. These routers run a single copy of the SPF algorithm.
Page 26: Stub Areas
OSPF Overview Configuring OSPF Stub Areas OSPF allows certain areas to be configured as stub areas. A stub area is an area with routers that have no AS external Link State Advertisements (LSAs). In order to take advantage of the OSPF stub area support, default routing must be used in the stub area. This is accomplished by configuring only one of the stub area’s border routers to advertise a default route into the stub area.
Page 27: Not-So-Stubby-Areas
Configuring OSPF OSPF Overview Not-So-Stubby-Areas NSSA, or not-so-stubby area, is an extension to the base OSPF specification and is defined in RFC 1587. An NSSA is similar to a stub area in many ways: AS-external LSAs are not flooded into an NSSA and virtual links are not allowed in an NSSA.
Page 28: Equal Cost Multi-Path (Ecmp) Routing
OSPF Overview Configuring OSPF Equal Cost Multi-Path (ECMP) Routing Using information from its continuously updated databases, OSPF calculates the shortest path to a given destination. Shortest path is determined from metric values at each hop along a path. At times, two or more paths to the same destination will have the same metric cost.
Page 29 Configuring OSPF OSPF Overview When a takeover occurs, which can be planned (e.g., the users performs the takeover) or unplanned (e.g., the primary CMM unexpectedly fails), an OSPF router must reestablish full adjacencies with all its previ- ously fully adjacent neighbors. This time period between the restart and the reestablishment of adjacen- cies is termed graceful restart.
Page 30: Configuring Ospf
Configuring OSPF Configuring OSPF Configuring OSPF Configuring OSPF on a router requires several steps. Depending on your requirements, you may not need to perform all of the steps listed below. By default, OSPF is disabled on the router. Configuring OSPF consists of these tasks: •...
Page 31: Preparing The Network For Ospf
Configuring OSPF Configuring OSPF Preparing the Network for OSPF OSPF operates on top of normal switch functions, using existing ports, virtual ports, VLANs, etc. The following network components should already be configured: • Configure VLANs that are to be used in the OSPF network. VLANS should be created for both the backbone interfaces and all other connected devices that will participate in the OSPF network.
Page 32: Creating An Ospf Area
Configuring OSPF Configuring OSPF Removing OSPF from Memory To remove OSPF from the router memory, it is necessary to manually edit the boot.cfg file. The boot.cfg file is an ASCII text-based file that controls many of the switch parameters. Open the file and delete all references to OSPF.
Page 33 Configuring OSPF Configuring OSPF Enabling and Disabling Summarization Summarization can also be enabled or disabled when creating an area. Enabling summarization allows for ranges to be used by Area Border Routers (ABRs) for advertising routes as a single route rather than multiple routes, while disabling summarization prevents set ranges from functioning in stub and NSSA areas.
Page 34: Configuring Stub Area Default Metrics
Configuring OSPF Configuring OSPF Configuring Stub Area Default Metrics The default metric configures the type of cost metric that a default area border router (ABR) will advertise in the default summary Link State Advertisement (LSA). Use the ip ospf area default-metric command to create or delete a default metric for stub or Not So Stubby Area (NSSA) area.
Page 35: Creating Ospf Interfaces
Configuring OSPF Configuring OSPF -> ip ospf area 1.1.1.1 summary disable -> ip ospf area 1.1.1.1 default-metric 0 -> ip ospf interface vlan-5 -> ip ospf interface vlan-5 area 1.1.1.1 -> ip ospf interface vlan-5 admin-state enable -> ip ospf interface vlan-6 ->...
Page 36: Interface Authentication
Configuring OSPF Configuring OSPF Activating an Interface Once the interface is created and assigned to an area, it must be activated using the ip ospf interface admin-state command with the interface name, as shown: -> ip ospf interface vlan-213 admin-state enable The interface can be disabled using the disable keyword in place of the enable keyword.
Page 37 Configuring OSPF Configuring OSPF Modifying Interface Parameters There are several interface parameters that can be modified on a specified interface. Most of these deal with timer settings. The cost parameter and the priority parameter help to determine the cost of the route using this interface, and the chance that this interface’s router will become the designated router, respectively.
Page 38: Creating Virtual Links
Configuring OSPF Configuring OSPF Creating Virtual Links A virtual link is a link between two backbones through a transit area. Use the ip ospf virtual-link command to create or delete a virtual link. Accepted network design theory states that virtual links are the option of last resort. For more information on virtual links, see “Virtual Links”...
Page 39: Creating A Route Map
Configuring OSPF Configuring OSPF • Set. A set statement is used to modify route information before the route is redistributed into the receiving protocol. This statement is only applied if all the criteria of the route map is met and the action permits redistribution.
Page 40 Configuring OSPF Configuring OSPF -> ip route-map ospf-to-bgp sequence-number 10 match tag 8 -> ip route-map ospf-to-bgp sequence-number 10 set tag 5 To verify a route map configuration, use the show ip route-map command: -> show ip route-map Route Maps: configured: 1 max: 200 Route Map: ospf-to-bgp Sequence Number: 10 Action permit match tag 8 set tag 5...
Page 41: Configuring Access Lists
Configuring OSPF Configuring OSPF The resulting route map appears as follows: -> show ip route-map rm_1 Route Map: rm_1 Sequence Number: 10 Action permit match tag 8 set metric 1 Route Map: rm_1 Sequence Number: 20 Action permit match ip6 interface to-finance set metric 5 Sequence 10 and sequence 20 are both linked to route map rm_1 and are processed in ascending order according to their sequence number value.
Page 42: Configuring Route Map Redistribution
Configuring OSPF Configuring OSPF -> ip access-list ipaddr address 16.24.2.1/16 action deny redist-control all- subnets -> ipv6 access-list ip6addr address 2001::1/64 action permit redist-control no- subnets For more information about configuring access list commands, see the “IP Commands” chapter in the OmniSwitch CLI Reference Guide.
Page 43 Configuring OSPF Configuring OSPF -> ip redist ospf into bgp route-map ospf-to-bgp admin-state enable OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011 page 1-27...
Page 44: Route Map Redistribution Example
Configuring OSPF Configuring OSPF Route Map Redistribution Example The following example configures the redistribution of OSPF routes into a BGP network using a route map (ospf-to-bgp) to filter specific routes: -> ip route-map ospf-to-bgp sequence-number 10 action deny -> ip route-map ospf-to-bgp sequence-number 10 match tag 5 ->...
Page 45: Configuring Router Capabilities
Configuring OSPF Configuring OSPF Configuring Router Capabilities The following list shows various commands that can be useful in tailoring a router’s performance capabili- ties. All of the listed parameters have defaults that are acceptable for running an OSPF network. ip ospf exit-overflow-interval Sets the overflow interval value.
Page 46: Configuring Static Neighbors
Configuring OSPF Configuring OSPF Configuring Static Neighbors It is possible to configure neighbors statically on Non Broadcast Multi Access (NBMA), point-to-point, and point-to-multipoint networks. NBMA requires all routers attached to the network to communicate directly (unicast), and every attached router in this network becomes aware of all of its neighbors through configuration. It also requires a Designated Router (DR) “eligibility”...
Page 47: Configuring Redundant Cmms For Graceful Restart
Configuring OSPF Configuring OSPF Configuring Redundant CMMs for Graceful Restart By default, OSPF graceful restart is disabled. To enable OSPF graceful restart on OmniSwitch chassis- based switches, use the ip ospf restart-support command by entering ip ospf restart-support followed by planned-unplanned. For example, to enable OSPF graceful restart to support planned and unplanned restarts enter: ->...
Page 48: Ospf Application Example
OSPF Application Example Configuring OSPF OSPF Application Example This section will demonstrate how to set up a simple OSPF network. It uses three routers, each with an area. Each router uses three VLANs. A backbone connects all the routers. This section will demonstrate how to set it up by explaining the necessary commands for each router.
Page 49: Step 1: Prepare The Routers
Configuring OSPF OSPF Application Example Step 1: Prepare the Routers The first step is to create the VLANs on each router, add an IP interface to the VLAN, assign a port to the VLAN, and assign a router identification number to the routers. For the backbone, the network design in this case uses slot 2, port 1 as the egress port and slot 2, port 2 as ingress port on each router.
Page 50: Step 2: Enable Ospf
OSPF Application Example Configuring OSPF -> ip router router-id 2.2.2.2 These commands created VLANs 12, 23, and 20. • VLAN 12 handles the backbone connection from Router 1 to Router 2, using the IP router port 12.0.0.2 and physical port 2/1. •...
Page 51: Step 4: Create, Enable, And Assign Interfaces
Configuring OSPF OSPF Application Example The commands for this step are below: Router 1 -> ip ospf area 0.0.0.0 -> ip ospf area 0.0.0.1 These commands created area 0.0.0.0 (the backbone) and area 0.0.0.1 (the area for Router 1). Both of these areas are also enabled.
Page 52: Step 5: Examine The Network
OSPF Application Example Configuring OSPF -> ip ospf interface vlan-23 -> ip ospf interface vlan-23 area 0.0.0.0 -> ip ospf interface vlan-23 admin-state enable -> ip ospf interface vlan-20 -> ip ospf interface vlan-20 area 0.0.0.2 -> ip ospf interface vlan-20 admin-state enable IP router port 12.0.0.2 was associated to OSPF interface vlan-12, enabled, and assigned to the backbone.
Page 53: Verifying Ospf Configuration
Configuring OSPF Verifying OSPF Configuration Verifying OSPF Configuration To display information about areas, interfaces, virtual links, redistribution, or OPSF in general, use the show commands listed in the following table: show ip ospf Displays OSPF status and general configuration parameters. show ip ospf border-routers Displays information regarding all or specified border routers.
Page 54 Verifying OSPF Configuration Configuring OSPF page 1-38 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 55: Chapter 2 Configuring Ospfv3
2 Configuring OSPFv3 Open Shortest Path First version 3 (OSPFv3) is an extension of OSPF version 2 that provides support for networks using the IPv6 protocol. OSPFv2 is for IPv4 networks (see Chapter 1, “Configuring OSPF,” more information about OSPFv2). In This Chapter This chapter describes the basic components of OSPFv3 and how to configure them through the Command Line Interface (CLI).
Page 56: Ospfv3 Specifications
OSPFv3 Specifications Configuring OSPFv3 OSPFv3 Specifications Platforms Supported OmniSwitch 10K RFCs Supported RFC 1826—IP Authentication Header RFC 1827—IP Encapsulating Security Payload RFC 2553—Basic Socket Interface Extensions for IPv6 RFC 2373—IPv6 Addressing Architecture RFC 2374—An IPv6 Aggregatable Global Unicast Address Format RFC 2460—IPv6 base specification RFC 2470—OSPF for IPv6 Maximum number of Areas...
Page 57: Ospfv3 Defaults Table
Configuring OSPFv3 OSPFv3 Defaults Table OSPFv3 Defaults Table The following table shows the default settings of the configurable OSPFv3 parameters. Parameter Description Command Default Value/Comments Configures the OSPFv3 administra- ipv6 ospf admin-state enabled tive status. Configures the administrative status ipv6 ospf interface admin-state enabled for an OSPF interface.
Page 58: Ospfv3 Quick Steps
OSPFv3 Quick Steps Configuring OSPFv3 OSPFv3 Quick Steps The followings steps are designed to show the user the necessary set of commands for setting up a router to use OSPFv3: Create a VLAN using the vlan command. For example: -> vlan 5 ->...
Page 59 Configuring OSPFv3 OSPFv3 Quick Steps You can now display the router OSPFv3 settings by using the show ipv6 ospf command. The output generated is similar to the following: -> show ipv6 ospf Router ID Status = Enabled, As set in Step 5 Router ID = 5.5.5.5, # Areas...
Page 60 OSPFv3 Quick Steps Configuring OSPFv3 You can display OSPFv3 interface settings using the show ipv6 ospf interface command. For example: -> show ipv6 ospf interface test Name = test Type = BROADCAST, Admin Status = Enabled, IPv6 Interface Status = Up, Area ID Oper Status = Up,...
Page 61 Configuring OSPFv3 OSPFv3 Quick Steps You can view the contents of the Link-State Database (LDSB) using the show ipv6 ospf lsdb command. This command displays the topology information that is provided to/from neighbors. For example: -> show ipv6 ospf lsdb Area Type Link ID...
Page 62: Ospfv3 Overview
OSPFv3 Overview Configuring OSPFv3 OSPFv3 Overview Open Shortest Path First version 3 (OSPFv3) routing is a shortest path first (SPF), or link-state, protocol for IPv6 networks. OSPFv3 is an interior gateway protocol (IGP) that distributes routing information between routers in a Single Autonomous System (AS). OSPFv3 chooses the least-cost path as the best path.
Page 63: Ospfv3 Areas
Configuring OSPFv3 OSPFv3 Overview OSPFv3 Areas OSPFv3 allows collections of contiguous networks and hosts to be grouped together as an area. Each area runs a separate copy of the basic link-state routing algorithm (usually called SPF). This means that each area has its own topological database, as explained in the previous section.
Page 64: Classification Of Routers
OSPFv3 Overview Configuring OSPFv3 Classification of Routers When an AS is split into OSPFv3 areas, the routers are further divided according to function into the following four overlapping categories: • Internal area router. A router with all directly connected networks belonging to the same area. Each internal router shares the same LSDB with other routers within the same area.
Page 65: Stub Areas
Configuring OSPFv3 OSPFv3 Overview Stub Areas OSPFv3 allows certain areas to be configured as stub areas. A stub area is an area with routers that have no AS external Link State Advertisements (LSAs). In order to take advantage of the OSPFv3 stub area support, default routing must be used in the stub area. This is accomplished by configuring one or more of the stub area’s border routers to advertise a default route into the stub area.
Page 66: Equal Cost Multi-Path (Ecmp) Routing
OSPFv3 Overview Configuring OSPFv3 Equal Cost Multi-Path (ECMP) Routing Using information from its continuously updated databases, OSPFv3 calculates the shortest path to a given destination. Shortest path is determined from metric values at each hop along a path. At times, two or more paths to the same destination will have the same metric cost.
Page 67: Configuring Ospfv3
Configuring OSPFv3 Configuring OSPFv3 Configuring OSPFv3 Configuring OSPFv3 on a router requires several steps. Depending on your requirements, you may not need to perform all of the steps listed below. By default, OSPFv3 is enabled on the router. Configuring OSPFv3 consists of these tasks: •...
Page 68: Preparing The Network For Ospfv3
Configuring OSPFv3 Configuring OSPFv3 Preparing the Network for OSPFv3 OSPFv3 operates on top of normal switch functions, using existing ports, virtual ports, VLANs, etc. The following network components should already be configured: • Configure VLANs that are to be used in the OSPFv3 network. VLANS should be created for inter- faces that will participate in the OSPFv3 network.
Page 69: Creating An Ospfv3 Area
Configuring OSPFv3 Configuring OSPFv3 Removing OSPFv3 from Memory To remove OSPFv3 from the router memory, it is necessary to manually edit the boot.cfg file. The boot.cfg file is an ASCII text-based file that controls many of the switch parameters. Open the file and delete all references to OSPFv3.
Page 70: Configuring Stub Area Default Metrics
Configuring OSPFv3 Configuring OSPFv3 The first example gives specifics about area 1.1.1.1, and the second example shows all areas configured on the router. To display the parameters of an area, use the show ipv6 ospf area command as follows: -> show ipv6 ospf area 1.1.1.1 Deleting an Area To delete an area, enter the ipv6 ospf area...
Page 71: Creating Virtual Links
Configuring OSPFv3 Configuring OSPFv3 Modifying Interface Parameters There are several interface parameters that can be modified on a specified interface. Most of these deal with timer settings. The cost parameter and the priority parameter help to determine the cost of the route using this interface, and the chance that this interface’s router will become the designated router, respectively.
Page 72: Configuring Redistribution
Configuring OSPFv3 Configuring OSPFv3 Then use the ipv6 ospf virtual-link command on Router A as shown: -> ipv6 ospf virtual-link area 0.0.0.1 router 2.2.2.2 Next, enter the following command on Router B: -> ipv6 ospf virtual-link area 0.0.0.1 router 1.1.1.1 Now there is a virtual link across Area 0.0.0.1 linking Router A and Router B.
Page 73: Using Route Maps
Configuring OSPFv3 Configuring OSPFv3 Using Route Maps A route map specifies the criteria that are used to control redistribution of routes between protocols. Such criteria is defined by configuring route map statements. There are three different types of statements: • Action.
Page 74 Configuring OSPFv3 Configuring OSPFv3 Note. Configuring match statements is not required. However, if a route map does not contain any match statements and the route map is applied using the ipv6 redist command, the router redistributes all routes into the network of the receiving protocol. To modify route information before it is redistributed, use the ip route-map command with a set parame- ter.
Page 75 Configuring OSPFv3 Configuring OSPFv3 Configuring Route Map Sequences A route map may consist of one or more sequences of statements. The sequence number determines which statements belong to which sequence and the order in which sequences for the same route map are processed.
Page 76: Configuring Route Map Redistribution
Configuring OSPFv3 Configuring OSPFv3 Configuring Access Lists An IP access list provides a convenient way to add multiple IPv4 or IPv6 addresses to a route map. Using an access list avoids having to enter a separate route map statement for each individual IP address. Instead, a single statement is used that specifies the access list name.
Page 77 Configuring OSPFv3 Configuring OSPFv3 To remove a route map redistribution configuration, use the no form of the ipv6 redist command. For example: -> no ipv6 redist ospf into rip route-map ospf-to-rip Use the show ipv6 redist command to verify the redistribution configuration: ->...
Page 78: Configuring Router Capabilities
Configuring OSPFv3 Configuring OSPFv3 Configuring Router Capabilities The following list shows various commands that can be useful in tailoring a router’s performance capabili- ties. All of the listed parameters have defaults that are acceptable for running an OSPFv3 network. ipv6 ospf host Creates and deletes an OSPFv3 entry for directly attached hosts.
Page 79: Ospfv3 Application Example
Configuring OSPFv3 OSPFv3 Application Example OSPFv3 Application Example This section will demonstrate how to set up a simple OSPFv3 network. It uses three routers, each with an area. Each router uses three VLANs. A backbone connects all the routers. This section will demonstrate how to set it up by explaining the necessary commands for each router.
Page 80: Step 1: Prepare The Routers
OSPFv3 Application Example Configuring OSPFv3 Step 1: Prepare the Routers The first step is to create the VLANs on each router, add an IP interface to the VLAN, assign a port to the VLAN, and assign a router identification number to the routers. For the backbone, the network design in this case uses slot 2, port 1 as the egress port and slot 2, port 2 as ingress port on each router.
Page 81: Step 2: Load Ospfv3
Configuring OSPFv3 OSPFv3 Application Example -> vlan 20 -> ipv6 interface vlan-20 vlan 20 -> ipv6 address 2001:4::1/64 vlan-20 -> vlan 20 members port 2/3-5 untagged -> ipv6 router router-id 2.2.2.2 These commands created VLANs 12, 23, and 20. • VLAN 12 handles the backbone connection from Router 1 to Router 2, using the IP router port and physical port 2/1.
Page 82: Step 3: Create The Areas And Backbone
OSPFv3 Application Example Configuring OSPFv3 Step 3: Create the Areas and Backbone Now the areas should be created. In this case, we will create an area for each router, and a backbone (area 0.0.0.0) that connects the areas. The commands for this step are below: Router 1 ->...
Page 83: Step 5: Examine The Network
Configuring OSPFv3 OSPFv3 Application Example Router 3 -> ipv6 ospf interface vlan-23 area 0.0.0.0 -> ipv6 ospf interface vlan-31 area 0.0.0.0 -> ipv6 ospf interface vlan-30 area 0.0.0.3 IPv6 router interface vlan-23 was associated with OSPFv3 interface vlan-23, enabled, and assigned to the backbone.
Page 84: Verifying Ospfv3 Configuration
Verifying OSPFv3 Configuration Configuring OSPFv3 Verifying OSPFv3 Configuration To display information about areas, interfaces, virtual links, redistribution, or OPSFv3 in general, use the show commands listed in the following table: show ipv6 ospf Displays the OSPFv3 status and general configuration parameters. show ipv6 redist Displays the route map redistribution configuration.
Page 85: Configuring Bgp
3 Configuring BGP The Border Gateway Protocol (BGP) is an exterior routing protocol that guarantees the loop-free exchange of routing information between autonomous systems. The Alcatel-Lucent implementation supports BGP version 4 and the RFCs specified below. This chapter describes the configuration and use of BGP in IPv4 and IPv6 environments using the Command Line Interface (CLI).
Page 86 In This Chapter Configuring BGP • Configuring an IPv6 BGP Peer. See “Configuring an IPv6 BGP Peer” on page 3-68. • Configuring IPv6 BGP Networks. See “Configuring IPv6 BGP Networks” on page 3-72. • Configuring IPv6 Redistribution. See “Configuring IPv6 Redistribution” on page 3-75.
Page 87: Bgp Specifications
Configuring BGP BGP Specifications BGP Specifications Platforms Supported OmniSwitch 10K RFCs Supported 1771/4271–A Border Gateway Protocol 4 (BGP-4) 2439–BGP Route Flap Damping 3392/5492–Capabilities Advertisement with BGP-4 2385–Protection of BGP Sessions via the TCP MD5 Signature Option 1997–BGP Communities Attribute 4456–BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) 3065–Autonomous System Confederations for BGP 4273–Definitions of Managed Objects for BGP-4...
Page 88: Quick Steps For Using Bgp
Quick Steps for Using BGP Configuring BGP Quick Steps for Using BGP The following steps and points summarize enabling BGP on the OmniSwitch. For BGP to be operational, the router's unique router-id and primary address must be configured. Assign the BGP local speaker's router-id and primary IP address that uniquely identifies the router in the routing domain.
Page 89: Bgp Overview
Configuring BGP BGP Overview BGP Overview BGP (Border Gateway Protocol) is a protocol for exchanging routing information between gateway hosts in a network of autonomous systems. BGP is the most common protocol used between gateway hosts on the Internet. The routing table exchanged between hosts contains a list of known routers, the addresses they can reach, and attributes associated with the path.
Page 90: Autonomous Systems (Ass)
BGP Overview Configuring BGP BGP uses TCP as its transport protocol, eliminating the need for it to implement mechanisms for protocol message fragmentation, retransmission, acknowledgment, and sequencing information. Autonomous Systems (ASs) Exterior routing protocols were created to control the expansion of routing tables and to provide a more structured view of the Internet by segregating routing domains into separate administrations, called Autonomous Systems (ASs).
Page 91: Internal Vs. External Bgp
Configuring BGP BGP Overview Internal vs. External BGP Although BGP is an exterior gateway protocol, it can still be used inside an AS as a pipe to exchange BGP updates. BGP connections inside an AS are referred to as Internal BGP (IBGP), while BGP connections between routers in separate ASs are referred to as External BGP (EBGP).
Page 92: Communities
BGP Overview Configuring BGP Communities A community is a group of destinations that share some common property. A community is not restricted to one network or one autonomous system. Communities are used to simplify routing policies by identifying routes based on a logical property rather than an IP prefix or an AS number.
Page 93: Route Reflectors
Configuring BGP BGP Overview Route Reflectors Route reflectors are useful if the internal BGP mesh becomes very large. A route reflector is a concentra- tion router for other BGP peers in the local network, acting as a focal point for internal BGP sessions. Multiple client BGP routers peer with the central route server (the reflector).
Page 94 BGP Overview Configuring BGP AS 100 with Route Reflection BGP Reflector 1 BGP Reflector 2 BGP Client 1 BGP Client 4 BGP Client 2 BGP Client 5 BGP Client 6 BGP Client 3 Since the router clients in this scenario only peer with the router reflector, the session load per router is significantly reduced.
Page 95: Bgp Confederations
Configuring BGP BGP Overview BGP Confederations Confederations are another way of dealing with large networks with many BGP speakers. Like route reflectors, confederations are recommended when speakers are forced to handle large numbers of BGP sessions at the same time. Confederations are sub ASs within a larger AS.
Page 96: Policies
BGP Overview Configuring BGP Policies Routing policies enable route classification for importing and exporting routes. The goal of routing policies is to control traffic flow. Policies can be applied to egress and ingress traffic. Note. Policies can be applied only to IPv4 routes and not to IPv6 prefixes. Policies act as filters to either permit or deny specified routes that are being learned or advertised from a peer.
Page 97: Regular Expressions
Configuring BGP BGP Overview Regular Expressions Regular expressions are used to identify AS paths for purposes of making routing decisions. In this context, an AS path is a list of one or more unsigned 16-bit AS numbers, in the range 1 through 65535. An ordinary pattern match string looks like: 100 200 which matches any AS path containing the Autonomous System number 100 followed immediately by...
Page 98 BGP Overview Configuring BGP • It makes writing (and reading) policies much easier. • It enables the router to begin using the policies more quickly after startup. For example, to identify routes originating from internal autonomous systems, you would use the pattern: [64512-65535]$ which means “match any AS number from 64512 to 65535 (inclusive) which occurs at the end of the AS path.”...
Page 99 Configuring BGP BGP Overview Matches: 100 350 501 200 250 260 270 280 600 Doesn’t Match: 100 600 100 400 600 700 ^500 Meaning: Only routes consisting of a single AS, 500. Matches: Doesn’t Match: 500 600 100 500 600 [100-199]* Meaning: Any route which ends with any number of occurrences of AS num-...
Page 100: Route Dampening
BGP Overview Configuring BGP Route Dampening Route dampening is a mechanism for controlling route instability. If a route (or path) is frequently adver- tised and withdrawn, it can expend router resources. Route dampening categorizes a route as either behaved or ill-behaved. A well behaved route shows a high degree of stability over an extended period of time, while an ill-behaved route shows a high degree of instability over a short period of time.
Page 101: Bgp Configuration Overview
“Configuring a BGP Peer” on page 3-26. Configure optional parameters. There are many optional features available in the Alcatel-Lucent implementation of BGP. These features are described in later sections of this chapter. The following is a list of BGP features you can configure on an OmniSwitch: •...
Page 102: Starting Bgp
Starting BGP Configuring BGP Starting BGP Before BGP is operational on your router you must load it to running memory and then administratively enable the protocol using the ip load bgp ip bgp admin-state commands. Follow these steps to start BGP.
Page 103 Configuring BGP Starting BGP Function Command Enable logging of peer changes ip bgp log-neighbor-changes Tag routes from OSPF ip bgp confederation identifier OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011 page 3-19...
Page 104: Setting Global Bgp Parameters
Setting Global BGP Parameters Configuring BGP Setting Global BGP Parameters Many BGP parameters are applied on a router-wide basis. These parameters are referred to as global BGP parameters. These values are taken by BGP peers in the router unless explicitly overridden by a BGP peer command.
Page 105: Setting The Router As Number
Configuring BGP Setting Global BGP Parameters Setting the Router AS Number The router takes a single Autonomous System (AS) number. You can assign one and only one AS number to a router using the ip bgp autonomous-system command. That same router may contain peers that belong to a different AS than the AS you assign your router.
Page 106: Enabling As Path Comparison
Setting Global BGP Parameters Configuring BGP Enabling AS Path Comparison The AS path is a route attribute that shows the sequence of ASs through which a route has traveled. For example if a path originated in AS 1, then went through AS 3, and reached its destination in AS 4, then the AS path would be: 4 3 1 A shorter AS path is preferred over a longer AS path.
Page 107: Controlling The Use Of Med Values
AS. Some exit points may be given a better MED value because they lead to higher speed connections. The Alcatel-Lucent implementation of BGP allows you to control MED values in the following ways: •...
Page 108: Synchronizing Bgp And Igp Routes
Setting Global BGP Parameters Configuring BGP Synchronizing BGP and IGP Routes In a transit-AS, BGP must ensure internal reachability to external BGP routes, prior to advertising these transit routes to external ASs. Otherwise, traffic can be lost. The BGP rule is that a BGP router should not advertise to external neighbors destinations learned from IBGP neighbors unless those destinations are also known via an IGP.
Page 109: Displaying Global Bgp Parameters
Configuring BGP Setting Global BGP Parameters Displaying Global BGP Parameters The following list shows the commands for viewing the various aspects of BGP set with the global BGP commands: show ip bgp Displays the current global settings for the local BGP speaker. show ip bgp statistics Displays BGP global statistics, such as number of peers, active prefixes and paths.
Page 110: Configuring A Bgp Peer
Configuring a BGP Peer Configuring BGP Configuring a BGP Peer BGP supports two types of peers, or neighbors: internal and external. Internal sessions are run between BGP speakers in the same autonomous system (AS). External sessions are run between BGP peers in different autonomous systems.
Page 111 Configuring BGP Configuring a BGP Peer Default Value/ Parameter Description Command Comments Enable or disables maximum pre- ip bgp neighbor maximum-prefix 80 percent fix warning for a peer. warning-only Allows external peers to commu- ip bgp neighbor ebgp-multihop disabled nicate with each other even when they are not directly connected.
Page 112: Creating A Peer
Configuring a BGP Peer Configuring BGP Creating a Peer Create the peer and assign it an address using the ip bgp neighbor command. For example to create a peer with an address of 190.17.20.16 you would enter: -> ip bgp neighbor 190.17.20.16 Assign an AS number to the peer using the ip bgp neighbor remote-as command.
Page 113: Restarting A Peer
Configuring BGP Configuring a BGP Peer Peer Parameter Command Allows external peers to communicate ip bgp neighbor ebgp-multihop with each other even when they are not directly connected. Sets the BGP peer to use next hop pro- ip bgp neighbor next-hop-self cessing behavior.
Page 114: Changing The Local Router Address For A Peer Session
Configuring a BGP Peer Configuring BGP Changing the Local Router Address for a Peer Session By default, TCP connections to a peer's address are assigned to the closest interface based on reachability. Any operational local interface can be assigned to the BGP peering session by explicitly forcing the TCP connection to use the specified interface.
Page 115: Setting Peer Authentication
Configuring BGP Configuring a BGP Peer Setting Peer Authentication You can set which MD5 authentication key this router will use when contacting a peer. To set the MD5 authentication key, enter the peer IP address and key with the ip bgp neighbor md5 key command: ->...
Page 116: Configuring Aggregate Routes
Configuring Aggregate Routes Configuring BGP Configuring Aggregate Routes Aggregate routes are used to reduce the size of routing tables by combining the attributes of several differ- ent routes and allowing a single aggregate route to be advertised to peers. You cannot aggregate an address (for example, 100.10.0.0) if you do not have at least one more-specific route of the address (for example, 100.10.20.0) in the BGP routing table.
Page 117: Configuring Local Routes (Networks)
Configuring BGP Configuring Local Routes (Networks) Configuring Local Routes (Networks) A local BGP network is used to indicate to BGP that a network should originate from a specified router. A network must be known to the local BGP speaker; it also must originate from the local BGP speaker. Networks have some parameters that can be configured, such as local-preference, community, and metric.
Page 118: Configuring Network Parameters
Configuring Local Routes (Networks) Configuring BGP Configuring Network Parameters Once a local network is added to a speaker, you can configure three parameters that are attached to routes generated by the ip bgp network command. These three attributes are the local preference, the commu- nity, and the route metric.
Page 119: Viewing Network Settings
Configuring BGP Configuring Local Routes (Networks) Viewing Network Settings To view the network settings for all networks assigned to the speaker, enter the show ip bgp network command, as shown: -> show ip bgp network A display similar to the following appears: Network Mask Admin state Oper state...
Page 120: Controlling Route Flapping Through Route Dampening
Controlling Route Flapping Through Route Dampening Configuring BGP Controlling Route Flapping Through Route Dampening Route dampening minimizes the effect of flapping routes in a BGP network. Route flapping occurs when route information is updated erratically, such as when a route is announced and withdrawn at a rapid rate. Route flapping can cause problems in networks connected to the Internet, where route flapping will involve the propagation of many routes.
Page 121: Enabling Route Dampening
Configuring BGP Controlling Route Flapping Through Route Dampening Enabling Route Dampening Route dampening must be enabled before it effects routes. To enable route dampening on a BGP router, enter the ip bgp dampening command, as shown: -> ip bgp dampening To disable route dampening, enter the following: ->...
Page 122 Controlling Route Flapping Through Route Dampening Configuring BGP Setting the Reuse Value The dampening reuse value is used to determine if a route should be re-advertised. If the number of flaps for a route falls below this number, then the route is re-advertised. For example, if the reuse value is set at 150, and a route with 250 flaps exceeds the reach halflife it would be re-advertised as its flap number would now be 125.
Page 123: Clearing The History
Configuring BGP Controlling Route Flapping Through Route Dampening Clearing the History By clearing the dampening history, you are resetting all of the dampening information on all of the routes back to zero, as if dampening had just been activated. Route flap counters are reset and any routes that were suppressed due to route flapping violations are unsuppressed.
Page 124: Setting Up Route Reflection
Setting Up Route Reflection Configuring BGP Setting Up Route Reflection BGP requires that all speakers in an autonomous system be fully meshed (i.e., each speaker must have a peer connection to every other speaker in the AS) so that external routing information can be distributed to all BGP speakers in an AS.
Page 125 Configuring BGP Setting Up Route Reflection This same configuration using a route reflector would not require that all BGP speakers be fully meshed. One of the speakers is configured to be a route reflector for the group. In this case, the route reflector is Speaker C.
Page 126: Configuring Route Reflection
Setting Up Route Reflection Configuring BGP When a route reflector receives a route it, selects the best path based on its policy decision criteria. The internal peers to which the route reflector advertises depends on the source of the route. The table below shows the rules the reflector follows when advertising path information: Route Received From...
Page 127: Working With Communities
Configuring BGP Working with Communities Working with Communities Distribution of routing information in BGP is typically based on IP address prefixes or on the value of the AS_PATH attributes. To facilitate and simplify the control of routing information, destinations can be grouped into communities and routing decisions can be applied based on these communities.
Page 128: Creating A Confederation
Creating a Confederation Configuring BGP Creating a Confederation A confederation is a grouping of ASs that together form a super AS. To BGP external peers, a confedera- tion appears as another AS even though the confederation has multiple ASs within it. Within a confedera- tion ASs can distinguish among one another and will advertise routes using EBGP.
Page 129: Routing Policies
Configuring BGP Routing Policies Routing Policies BGP selects routes for subsequent advertisement by applying policies available in a pre-configured local Policy Information database. This support of policy-based routing provides flexibility by applying poli- cies based on the path (i.e. AS path list), community attributes (i.e. community lists), specific destinations (i.e.
Page 130 Routing Policies Configuring BGP Next, use the ip bgp policy aspath-list action command to set the policy action. The action of a policy is whether the route filtered by the policy is permitted or denied. Denied routes are not propagated by the BGP speaker, while permitted routes are.
Page 131 Configuring BGP Routing Policies Creating a Prefix List Policy Prefix policies filter routes based on network addresses and their masks. You can also set prefix upper and lower limits to filter a range of network addresses. To create a prefix list policy: Name the policy and specify the IP network address and mask using the ip bgp policy prefix-list command, as shown:...
Page 132 Routing Policies Configuring BGP Set the policy action using the ip bgp policy route-map action command. The policy action either permits or denies routes that match the filter. Permitted routes are advertised, while denied routes are not. For example: -> ip bgp policy route-map mapfilter 1 action deny Prefix policy mapfilter now denies routes that are filtered.
Page 133 Configuring BGP Routing Policies Route Map Options Command Configures a BGP weight value to be ip bgp policy route-map weight assigned to inbound routes when a match is found. Configures the value to strip from the ip bgp policy route-map community-strip community attribute of the routes matched by this route map instance (sequence number).
Page 134: Assigning A Policy To A Peer
Routing Policies Configuring BGP Assigning a Policy to a Peer Once policies have been created using the commands described above, the policies can be applied to routes learned from a specific peer, or route advertisements to a specific peer. The following table shows the list of commands that allow you to assign a policy to a peer: BGP Attribute Command Assigns an inbound AS path list filter to...
Page 135 Configuring BGP Routing Policies Assigning In and Out Bound Community List Policies to a Peer Community list policies filter routes based on matches made to a list of communities of which the route is a member. Communities group routes by attaching labels to them specifying a behavior (such as no export).
Page 136: Displaying Policies
Routing Policies Configuring BGP Reconfiguring Peer Policies You can configure policies and assign these policies to a BGP peer, either to control in-bound routes or out-bound routes advertisement. Additionally, it is possible to change or modify these peer policies, after they are assigned to a peer.
Page 137: Configuring Redistribution
Configuring BGP Configuring Redistribution Configuring Redistribution It is possible to configure the BGP protocol to advertise routes learned from other routing protocols (exter- nal routes) into the BGP network. Such a process is referred to as route redistribution and is configured using the ip redist command.
Page 138 Configuring Redistribution Configuring BGP Creating a Route Map When a route map is created, it is given a name (up to 20 characters), a sequence number, and an action (permit or deny). Specifying a sequence number is optional. If a value is not configured, then the default value is used.
Page 139 Configuring BGP Configuring Redistribution Deleting a Route Map Use the no form of the ip route-map command to delete an entire route map, a route map sequence, or a specific statement within a sequence. To delete an entire route map, enter no ip route-map followed by the route map name. For example, the following command deletes the entire route map named redistipv4: ->...
Page 140 Configuring Redistribution Configuring BGP Sequence 10 and sequence 20 are both linked to route map rm_1 and are processed in ascending order according to their sequence number value. Note that there is an implied logical OR between sequences. As a result, if there is no match for the tag value in sequence 10, then the match interface statement in sequence 20 is processed.
Page 141: Configuring Route Map Redistribution
Configuring BGP Configuring Redistribution Configuring Route Map Redistribution ip redist command is used to configure the redistribution of routes from a source protocol into the BGP destination protocol. This command is used on the BGP router that will perform the redistribution. A source protocol is a protocol from which the routes are learned.
Page 142: Route Map Redistribution Example
Configuring Redistribution Configuring BGP Route Map Redistribution Example The following example configures the redistribution of OSPF routes into a BGP network using a route map (ospf-to-bgp) to filter specific routes: -> ip route-map ospf-to-bgp sequence-number 10 action deny -> ip route-map ospf-to-bgp sequence-number 10 match tag 5 ->...
Page 143: Configuring Redundant Cmms For Graceful Restart
Configuring BGP Configuring Redistribution Configuring Redundant CMMs for Graceful Restart On an OmniSwitch router in a redundant CMM configuration, inter-domain routing is not disrupted during a CMM takeover/failover. BGP retains routing information using Graceful Restart mechanisms and also helps a peering BGP router perform a BGP graceful restart. This supports the continuous forwarding of inter-domain traffic flows.
Page 144: Application Example
Application Example Configuring BGP Application Example The following simple network using EBGP and IBGP will demonstrate some of the basic BGP setup commands discussed previously: AS 200 AS 300 BGP Speaker 4 BGP Speaker 5 40.0.0.2/24 50.0.0.2/24 EBGP EBGP IBGP BGP Speaker 1 BGP Speaker 2 40.0.0.1/24...
Page 145 Configuring BGP Application Example Administratively enable BGP: -> ip bgp admin-state enable BGP Speaker 2 Assign the speaker to AS 100: -> ip bgp autonomous-system 100 Peer with the other speakers in AS 100 (for internal BGP, and to create a fully meshed BGP network): ->...
Page 146 Application Example Configuring BGP Peer with the external speaker in AS 100 (for external BGP): -> ip bgp neighbor 40.0.0.1 -> ip bgp neighbor 40.0.0.1 remote-as 100 -> ip bgp neighbor 40.0.0.1 admin-state enable Administratively enable BGP: -> ip bgp admin-state enable AS 300 BGP Speaker 5 Assign the speaker to AS 300:...
Page 147: Displaying Bgp Settings And Statistics
Configuring BGP Displaying BGP Settings and Statistics Displaying BGP Settings and Statistics Use the show commands listed in the following table to display information about the current BGP config- uration and on BGP statistics: show ip bgp Displays the current global settings for the local BGP speaker. show ip bgp statistics Displays BGP global statistics, such as the route paths.
Page 148: Bgp For Ipv6 Overview
BGP for IPv6 Overview Configuring BGP BGP for IPv6 Overview IP version 6 (IPv6) is a new version of the Internet Protocol, designed as the successor to IP version 4 (IPv4), to overcome certain limitations in IPv4. IPv6 adds significant extra features that were not possible with IPv4.
Page 149 Configuring BGP BGP for IPv6 Overview • EBGP Multihop. • Other multiprotocol capabilities for VPNs, MPLS label exchanges, etc. OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011 page 3-65...
Page 150: Quick Steps For Using Bgp For Ipv6
Quick Steps for Using BGP for IPv6 Configuring BGP Quick Steps for Using BGP for IPv6 The following steps create an IPv4 BGP peer capable of exchanging IPv6 prefixes: The BGP software is not loaded automatically when the router is booted. You must manually load the software into memory by typing the following command: ->...
Page 151 Configuring BGP Quick Steps for Using BGP for IPv6 The following steps create an IPv6 BGP peer capable of exchanging IPv6 prefixes: Repeat steps 1 through 3 from the previous section to load the BGP software, assign an AS number to the local BGP speaker, and enable unicast IPv6 updates for the BGP routing process, respectively.
Page 152: Configuring Bgp For Ipv6
Configuring BGP for IPv6 This section describes the BGP for IPv6 configuration, which includes enabling and disabling IPv6 BGP unicast, configuring IPv6 BGP peers, and configuring IPv6 BGP networks using Alcatel-Lucent’s Command Line Interface (CLI) commands. Enabling/Disabling IPv6 BGP Unicast...
Page 153 Configuring BGP Configuring BGP for IPv6 BGP Peer Behavior using Local IPv6 Unicast Addresses • The local IPv6 address prefixes are exchanged between internal BGP (IBGP) speakers within the same Autonomous System (AS), unless denied by explicit policy configuration. • As Exterior BGP (EBGP) peers between different AS ignore receipt of and do not advertise prefixes with the well-known FC00::/7 prefix, prefixes longer than FC00::/7 can be configured for inter-site communication.
Page 154 Configuring BGP for IPv6 Configuring BGP -> ipv6 bgp neighbor 2001::1 activate-ipv6 Enable the BGP peer status using the ipv6 bgp neighbor admin-state command. For example, to enable the status of the IPv6 BGP peer with an IPv6 address of , you would enter: 2001::1 ->...
Page 155: Changing The Local Router Address For An Ipv6 Peer Session
Configuring BGP Configuring BGP for IPv6 -> ipv6 bgp neighbor 2021::10 Assign an AS number to the IPv6 peer using the ipv6 bgp neighbor remote-as command. For exam- ple, to assign the peer created in Step 2 to AS number 20, you would enter: ->...
Page 156: Optional Ipv6 Bgp Peer Parameters
Configuring BGP for IPv6 Configuring BGP -> ipv6 bgp neighbor 2004::1 update-source ipv6IntfVlan2 Use the no form of the ipv6 bgp neighbor update-source command to prevent the peer with an IPv6 address of 2004::1 from contacting the speaker via the IPv6 interface ipv6IntfVlan2, as shown: ->...
Page 157: Adding A Network
Configuring BGP Configuring BGP for IPv6 Adding a Network To add a local network to a BGP speaker, use the IPv6 address and mask of the local network in conjunc- tion with the ipv6 bgp network command, as shown: -> ipv6 bgp network 2001::/64 In this example, the network 2001::/64 is the local IPv6 network for this BGP speaker.
Page 158: Viewing Network Settings
Configuring BGP for IPv6 Configuring BGP To change from the default community and add a network to a community, enter the local network IPv6 address and mask in conjunction with the ipv6 bgp network community command and name, as shown: ->...
Page 159: Configuring Ipv6 Redistribution
Configuring BGP Configuring IPv6 Redistribution Configuring IPv6 Redistribution It is possible to learn and advertise IPv6 routes between different routing protocols. Such a process is referred to as route redistribution and is configured using the ipv6 redist command. IPv6 redistribution uses route maps to control how external routes are learned and distributed. A route map consists of one or more user-defined statements that can determine which routes are allowed or denied access to the network.
Page 160 Configuring IPv6 Redistribution Configuring BGP Use the show ipv6 redist command to verify the redistribution configuration: -> show ipv6 redist Source Destination Protocol Protocol Status Route Map ------------+------------+---------+-------------------- localIPv6 Enabled ipv6rm OSPFv3 RIPng Enabled ospf-to-rip Configuring the Administrative Status of the Route Map Redistribution To change the default administrative status of a route map redistribution configuration, use the status parameter with the ipv6 redist command.
Page 161: Ipv6 Bgp Application Example
Configuring BGP IPv6 BGP Application Example IPv6 BGP Application Example The following simple network using EBGP and IBGP will demonstrate some of the basic BGP setup commands discussed previously: BGP Speaker 5 AS 200 AS 300 BGP Speaker 4 30.0.0.1/24 20.0.0.1/24 2001:ABCD:B02:1::1/64 EBGP...
Page 162 IPv6 BGP Application Example Configuring BGP -> ipv6 interface Link_To_Speaker3 vlan 3 -> ipv6 address 2001:DB8:C18:1::1/64 Link_To_Speaker3 -> ipv6 bgp neighbor 2001:DB8:C18:1::2 -> ipv6 bgp neighbor 2001:DB8:C18:1::2 remote-as 100 -> ipv6 bgp neighbor 2001:DB8:C18:1::2 activate-ipv6 -> ipv6 bgp neighbor 2001:DB8:C18:1::2 admin-state enable Peer with the external speaker in AS 200 using its IPv4 address and an IPv6 forwarding interface (for IPv6 traffic): ->...
Page 163 Configuring BGP IPv6 BGP Application Example Peer with the external speaker in AS 300 using IPv4 address: -> ip interface Link_To_AS300 vlan 4 -> ip interface Link_To_AS300 address 30.0.0.2/24 -> ip bgp neighbor 30.0.0.1 -> ip bgp neighbor 30.0.0.1 remote-as 300 ->...
Page 164 IPv6 BGP Application Example Configuring BGP Peer with the external speaker in AS 100 using its IPv4 address and an IPv6 forwarding interface (for IPv6 traffic): -> ip interface Link_To_AS100 vlan 2 -> ip interface Link_To_AS100 address 20.0.0.1/24 -> ipv6 interface Link_to_AS100 vlan 2 ->...
Page 165: Displaying Ipv6 Bgp Settings And Statistics
Configuring BGP Displaying IPv6 BGP Settings and Statistics Displaying IPv6 BGP Settings and Statistics Use the show commands listed in the following table to display information about the current IPv6 BGP configuration and on IPv6 BGP statistics: show ipv6 bgp network Displays the status of all the IPv6 BGP networks or a specific IPv6 BGP network.
Page 166 Displaying IPv6 BGP Settings and Statistics Configuring BGP page 3-82 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 167: Configuring Multicast Address Boundaries
4 Configuring Multicast Address Boundaries Multicast boundaries confine scoped multicast addresses to a particular domain. Confining scoped addresses helps to ensure that multicast traffic passed within a multicast domain does not conflict with multicast users outside the domain. In This Chapter This chapter describes the basic components of scoped multicast boundaries and how to configure them through the Command Line Interface (CLI).
Page 168: Multicast Boundary Specifications
Multicast Boundary Specifications Configuring Multicast Address Boundaries Multicast Boundary Specifications Platforms Supported OmniSwitch 10K RFCs Supported 2365—Administratively Scoped IP Multicast 5132 - IP Multicast MIB Valid Scoped Address Range 239.0.0.0 to 239.255.255.255 Note. If software routing is used, the number of total flows supported is variable, depending on the number of flows and the number of routes per flow.
Page 169: Quick Steps For Configuring Multicast Address Boundaries
Configuring Multicast Address Boundaries Quick Steps for Configuring Multicast Address Boundaries Quick Steps for Configuring Multicast Address Boundaries Using Existing IP Interfaces Before attempting to configure a multicast address boundary, be sure that you have manually loaded the multicast protocol software for your network (e.g., PIM or DVMRP). Otherwise, you will receive an error stating that “the specified application is not loaded.”...
Page 170: Multicast Address Boundaries Overview
Multicast Address Boundaries Overview Configuring Multicast Address Boundaries Multicast Address Boundaries Overview Multicast Addresses and the IANA The Internet Assigned Numbers Authority (IANA) regulates unique parameters for different types of network protocols. For example, the IANA regulates addresses for IP, DVMRP, PIM, PIM-SSM, etc., and also provides a range of administratively scoped multicast addresses.
Page 171: Multicast Address Boundaries
Configuring Multicast Address Boundaries Multicast Address Boundaries Overview Multicast Address Boundaries Without multicast address boundaries, multicast traffic conflicts can occur between domains. For exam- ple, a multicast packet addressed to 239.140.120.10 from a device in one domain could “leak” into another domain.
Page 172: Concurrent Multicast Addresses
Multicast Address Boundaries Overview Configuring Multicast Address Boundaries Concurrent Multicast Addresses Because multicast boundaries confine scoped multicast addresses to a particular domain, multicast addresses can be used concurrently in more than one region in the network. In other words, scoped multi- cast addresses can be reused throughout the network.
Page 173: Configuring Multicast Address Boundaries
Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries Before configuring this feature, the multicast routing protocol (e.g., PIM or DVMRP) for your network must first be loaded to memory via the ip load command. Basic Multicast Address Boundary Configuration Configuring a multicast address boundary prevents multicast traffic that is addressed to a particular address or range of addresses from being forwarded on an interface.
Page 174: Verifying The Multicast Address Boundary Configuration
Verifying the Multicast Address Boundary Configuration Configuring Multicast Address Boundaries Verifying the Multicast Address Boundary Configuration A summary of the show commands used for verifying the multicast address boundary configuration is given here: show ip mroute-boundary Displays scoped multicast address boundaries for the switch’s router interfaces.
Page 175 Configuring Multicast Address Boundaries Application Example for Configuring Multicast Address Boundaries You are now ready to create a boundary on the core switch’s router interface. For this example, the broadest possible boundary, 239.0.0.0, will be configured on the interface. This boundary will keep all traffic addressed to multicast addresses 239.0.0.0 through 239.255.255.255 from being forwarded on the interface.
Page 176 Application Example for Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries Create an IP interface on VLAN 3. For example: -> ip interface vlan-3 address 178.20.1.1 vlan 3 Assign a boundary on the switch’s router interface. For this example, the interface is given the bound- ary 239.188.0.0/16.
Page 177 Configuring Multicast Address Boundaries Application Example for Configuring Multicast Address Boundaries The figure below illustrates all configured multicast address boundaries for this network. Internet VLAN 2 Router Port 239.x.x.x 178.10.1.1 Multicast Traffic Core Switch Training Human Resources VLAN 3 VLAN 4 Router Router 239.188.x.x...
Page 178 Application Example for Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries page 4-12 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 179: In This Chapter
5 Configuring DVMRP This chapter includes descriptions for Distance Vector Multicast Routing Protocol (DVMRP). DVMRP is a dense-mode multicast routing protocol. DVMRP, essentially a “broadcast and prune” routing protocol is designed to assist routers in propagating IP multicast traffic through a network. In This Chapter This chapter describes the basic components of DVMRP and how to configure them through the Command Line Interface (CLI).
Page 180: Chapter 5 Configuring Dvmrp
DVMRP Specifications Configuring DVMRP DVMRP Specifications Platforms Supported OmniSwitch 10K RFCs Supported 4087—IP Tunnel MIB DVMRP Version Supported DVMRPv3.255 DVMRP Attributes Supported Reverse Path Multicasting, Neighbor Discovery, Multicast Source Location, Route Report Messages, Distance metrics, Dependent Downstream Routers, Poison Reverse, Pruning, Grafting, DVMRP Tunnels DVMRP Timers Supported Flash update interval, Graft retransmissions, Neighbor...
Page 181: Quick Steps For Configuring Dvmrp
Configuring DVMRP Quick Steps for Configuring DVMRP Quick Steps for Configuring DVMRP Note. DVMRP requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM or DVMRP) is enabled globally and on an interface and when the operational status of the interface is up.
Page 182: Dvmrp Overview
DVMRP Overview Configuring DVMRP DVMRP Overview Distance Vector Multicast Routing Protocol (DVMRP) Version 3 is a multicast routing protocol that enables routers to efficiently propagate IP multicast traffic through a network. Multicast traffic consists of a data stream that originates from a single source and is sent to hosts that have subscribed to that stream. Live video broadcasts, video conferencing, corporate communications, distance learning, and distribution of software, stock quotes, and news services are examples of multicast traffic.
Page 183: Neighbor Discovery
Configuring DVMRP DVMRP Overview Neighbor Discovery DVMRP routers must maintain a database of DVMRP adjacencies with other DVMRP routers. A DVMRP router must be aware of its DVMRP neighbors on each interface. To gather this information, DVMRP routers use a neighbor discovery mechanism and periodically multicast DVMRP Probe messages to the All-DVMRP-Routers group address (224.0.0.4).
Page 184: Multicast Source Location, Route Report Messages, And Metrics
DVMRP Overview Configuring DVMRP Multicast Source Location, Route Report Messages, and Metrics When an IP multicast packet is received by a router running DVMRP, it first looks up the source network in the DVMRP routing table. The interface that provides the best route back to the source of the packet is called the upstream interface.
Page 185: Pruning Multicast Traffic Delivery
Configuring DVMRP DVMRP Overview Pruning Multicast Traffic Delivery Initially, all interfaces with downstream-dependent neighbors are included in the downstream interface list and multicast traffic is flooded down the truncated broadcast tree to all possible receivers. This allows the downstream routers to be aware of traffic destined for a particular Source, Group (S, G) pair. The down- stream routers then have the option to send prunes (and subsequent grafts) for this (S, G) pair as require- ments change.
Page 186: Dvmrp Tunnels
DVMRP Overview Configuring DVMRP DVMRP Tunnels Because not all IP routers support native multicast routing, DVMRP includes direct support for tunneling IP multicast packets through routers. Tunnel interfaces are used when routers incapable of supporting multicast traffic exist between DVMRP neighbors. In tunnel interfaces, IP multicast packets are encapsu- lated in unicast IP packets and addressed directly to the routers that do not support native multicast rout- ing.
Page 187: Configuring Dvmrp
Configuring DVMRP Configuring DVMRP Configuring DVMRP Before configuring DVMRP, consider the following: • DVMRP requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM or DVMRP) is enabled globally and on an interface and when the operational status of the interface is up.
Page 188: Enabling Dvmrp On A Specific Interface
Configuring DVMRP Configuring DVMRP Enabling DVMRP on a Specific Interface Note. It does not matter whether DVMRP is first enabled globally or on specific interfaces. However, DVMRP will not run on an interface until it is enabled both globally and on the interface. DVMRP must be enabled on an interface before any other interface-specific DVMRP command can be executed (e.g, the ip dvmrp interface metric command).
Page 189: Viewing Dvmrp Status And Parameters For A Specific Interface
Configuring DVMRP Configuring DVMRP Viewing DVMRP Status and Parameters for a Specific Interface To view current DVMRP interfaces, including their operational status and assigned metrics, use the show ip dvmrp interface command. For example: -> show ip dvmrp interface Interface Name Vlan Metric Admin-Status...
Page 190: Automatic Loading And Enabling Of Dvmrp Following A System Boot
Configuring DVMRP Configuring DVMRP Automatic Loading and Enabling of DVMRP Following a System Boot If any DVMRP command is saved to the boot.cfg file in the post-boot running directory, DVMRP will be loaded into memory automatically. The post-boot running directory refers to the directory the switch will use as its running directory following the next system boot (i.e., Working or Certified).
Page 191: Routes
Configuring DVMRP Configuring DVMRP Routes In DVMRP, source network routing information is exchanged in the same basic manner as it is in RIP. That is to say, periodic Route Report messages are sent between DVMRP neighbors. A Route Report contains the sender’s current routing table. The routing table contains entries that advertise a source network (with a mask) and a hop-count that is used as the routing metric.
Page 192: Pruning
Configuring DVMRP Configuring DVMRP Pruning DVMRP uses a flood-and-prune mechanism that starts by delivering multicast traffic to all routers in the network. This means that, initially, traffic is flooded down a multicast delivery tree. DVMRP routers then prune this flow where the traffic is unwanted. Routers that have no use for the traffic send DVMRP Prune messages up the delivery tree to stop the flow of unwanted multicast traffic, thus pruning the unwanted branches of the tree.
Page 193 Configuring DVMRP Configuring DVMRP As an example, let’s say that the following situation exists on a branch router: ip dvmrp prune-lifetime is set to 7200 seconds and three prunes for the pruned group exist on the router’s timer queue. These three prunes have remaining lifetimes of 7000 seconds, 5000 seconds, and 4500 seconds.
Page 194: Grafting
Configuring DVMRP Configuring DVMRP Grafting A pruned branch will be automatically reattached to the multicast delivery tree when the prune times out. However, the graft mechanism provides a quicker method to reattach a pruned branch than waiting for the prune to time out. As traffic is forwarded, routers that do not want multicast traffic send Prune messages to signal the upstream router to stop sending the traffic.
Page 195: Verifying The Dvmrp Configuration
Configuring DVMRP Verifying the DVMRP Configuration Verifying the DVMRP Configuration A summary of the show commands used for verifying the DVMRP configuration is given here: show ip dvmrp Displays global DVMRP parameters such as admin status, flash interval value, graft timeout value, neighbor interval value, subordinate neighbor status, number of routes, number of routes reachable, etc.
Page 196 Verifying the DVMRP Configuration Configuring DVMRP page 5-18 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 197: Configuring Pim
6 Configuring PIM Protocol-Independent Multicast (PIM) is an IP multicast routing protocol that uses routing information provided by unicast routing protocols such as RIP and OSPF. PIM is “protocol-independent” because it does not rely on any particular unicast routing protocol. PIM-Sparse Mode (PIM-SM) contrasts with flood-and-prune dense mode multicast protocols, such as DVMRP and PIM-Dense Mode (PIM-DM), in that multicast forwarding in PIM-SM is initiated only via specific requests, referred to as Join messages.
Page 198 In This Chapter Configuring PIM • Mapping an IPv6 multicast group to a PIM mode—see page 6-37. • Configuring Candidate Rendezvous Points (C-RPs) in IPv6 PIM—see page 6-38. • Configuring Candidate Bootstrap Routers (C-BSRs) in IPv6 PIM—see page 6-39. • Configuring RP-switchover for IPv6 PIM—see page 6-42.
Page 199: Pim Specifications
Configuring PIM PIM Specifications PIM Specifications Platforms Supported OmniSwitch 10K RFCs Supported 4601—Protocol Independent Multicast-Sparse Mode (PIM-SM) Protocol Specification 5060 - Protocol Independent Multicast MIB 5132 —IP Multicast MIB 3306—Unicast-Prefix-based IPv6 Multicast Addresses 3569—An Overview of Source-Specific Multicast (SSM) 3973—Protocol Independent Multicast-Dense Mode (PIM- 3376—Internet Group Management Protocol 4601—Protocol Independent Multicast-Sparse Mode (PIM-SM)
Page 200: Pim Defaults
PIM Defaults Configuring PIM PIM Defaults The following table lists the defaults for PIM configuration: Parameter Description Command Default Value/Comments PIM status ip load pim Disabled PIM load status - sparse mode ip pim sparse admin-state Disabled PIM load status - dense mode ip pim dense admin-state Disabled Priority...
Page 201 Configuring PIM PIM Defaults Parameter Description Command Default Value/Comments Neighbor loss notification interval ip pim neighbor-loss-notification- 0 seconds period Invalid register notification inter- ip pim invalid-register-notification- 65535 seconds period RP mapping notification interval ip pim rp-mapping-notification- 65535 seconds period Invalid joinprune notification ip pim invalid-joinprune-notification- 65535 seconds interval...
Page 202: Quick Steps For Configuring Pim-Dm
Quick Steps for Configuring PIM-DM Configuring PIM Quick Steps for Configuring PIM-DM Note. PIM requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM or DVMRP) is enabled globally and on an interface and when the operational status of the interface is up.
Page 203 Configuring PIM Quick Steps for Configuring PIM-DM The display for dense mode is similar to the one shown here: -> show ip pim dense Status = enabled, Source Lifetime = 210, State Refresh Interval = 60, State Refresh Limit Interval = 0, State Refresh TTL = 16 (additional table output not shown)
Page 204: Pim Overview
PIM Overview Configuring PIM PIM Overview Protocol-Independent Multicast (PIM) is an IP multicast routing protocol that uses routing information provided by unicast routing protocols such as RIP and OSPF. Note that PIM is not dependent on any particular unicast routing protocol. Downstream routers must explicitly join PIM distribution trees in order to receive multicast streams on behalf of receivers or other downstream PIM routers.
Page 205: Bootstrap Routers (Bsrs)
Configuring PIM PIM Overview Bootstrap Routers (BSRs) The role of a Bootstrap Router (BSR) is to keep routers in the network up to date on reachable C-RPs. The BSR’s list of reachable C-RPs is also referred to as an RP set. There is only one BSR per PIM domain. This allows all PIM routers in the PIM domain to view the same RP set.
Page 206 PIM Overview Configuring PIM Note. The Join message is known as a (*,G) join because it joins group G for all sources to that group. Sender 1 Receiver Designated Router (DR) RP Router Legend IGMP Join from Receiver Receiver 1 PIM Join Message from DR Note.
Page 207 Configuring PIM PIM Overview Sender 1 sends multicast data to its Designated Router (DR). The source DR then unicast-encapsulates the data into PIM-SM Register messages and sends them on to the RP. Sender 1 Source Designated Router (DR) Receiver Designated Router (DR) RP Router Legend...
Page 208: Avoiding Register Encapsulation
PIM Overview Configuring PIM Avoiding Register Encapsulation Switching to a Shortest Path Tree (SPT) topology allows PIM routers to avoid Register encapsulation of data packets that occurs in an RPT. Register encapsulation is inefficient for the following reasons: • The encapsulation and unencapsulation of Register messages tax router resources. Hardware routing does not support encapsulation and unencapsulation.
Page 209: Rp Initiation Of (S, G) Source-Specific Join Message
Configuring PIM PIM Overview RP Initiation of (S, G) Source-Specific Join Message When the data rate at the Rendezvous Point (RP) exceeds the configured RP threshold value, the RP will initiate a (S, G) source-specific Join message toward the source. Legend Encapsulated Data Exceeding RP Threshold Sender...
Page 210 PIM Overview Configuring PIM When the Sender’s DR receives the (S,G) Join, it sends data natively as well. When these data packets arrive natively at the RP, the RP will be receiving two copies of each of these packets—one natively and one encapsulated.
Page 211: Spt Switchover
Configuring PIM PIM Overview SPT Switchover The last hop Designated Router (DR) initiates the switchover to a true Shortest Path Tree (SPT) once the DR receives the first multicast data packet. This method does not use any preconfigured thresholds, such as RP threshold (as described above).
Page 212 PIM Overview Configuring PIM Once the Sender’s DR receives the (S,G) Join message, the DR sends the multicast packets natively along the Shortest Path Tree. At this point, Router X (the router shown between the Sender’s DR and the Receiver’s DR) will be receiving two copies of the multicast data—one from the SPT and one from the RPT.
Page 213: Pim-Ssm Support
Configuring PIM PIM Overview The Receiver is now receiving multicast traffic along the Shortest Path Tree between the Receiver and the Source. Sender Receiver PIM-SSM Support Protocol-Independent Multicast Source-Specific Multicast (PIM-SSM) is a highly-efficient extension of PIM. SSM, using an explicit channel subscription model, allows receivers to receive multicast traffic directly from the source;...
Page 214: Configuring Pim
Configuring PIM Configuring PIM Configuring PIM Enabling PIM on the Switch Before running PIM, you must enable the protocol by completing the following steps: • Verifying the software • Loading PIM into memory • Enabling PIM on desired IP interfaces •...
Page 215 Configuring PIM Configuring PIM tional status of the interface is up. If you wish to manually enable IPMS on the switch, use the ip multicast admin-state command. OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011 page 6-19...
Page 216: Enabling Pim On A Specific Interface
Configuring PIM Configuring PIM Checking the Current IPMS Status To view the current status of IPMS on the switch, use the show ip multicast command. For example: -> show ip multicast Status: Enabled Querying: Disabled Proxying: Disabled Spoofing: Disabled Zapping: Disabled Querier Forwarding: Disabled...
Page 217: Viewing Pim Status And Parameters For A Specific Interface
Configuring PIM Configuring PIM Viewing PIM Status and Parameters for a Specific Interface To view the current PIM interface information—which includes IP addresses for PIM-enabled interfaces, Hello and Join/Prune intervals, and current operational status—use the show ip pim interface command. For example: ->...
Page 218: Checking The Current Global Pim Status
Configuring PIM Configuring PIM Checking the Current Global PIM Status To view current global PIM enable/disable status, as well as additional global PIM settings, use the show ip pim sparse show ip pim dense command. For example: -> show ip pim sparse Status = enabled, Keepalive Period...
Page 219: Verifying Group Mapping
Configuring PIM Configuring PIM This command entry maps the multicast group 224.0.0.0/4 to PIM-SSM and specifies the priority value to be used for the entry as 50. This priority specifies the preference value to be used for this static configura- tion and provides fine control over which configuration is overridden by this static configuration.
Page 220: Pim Bootstrap And Rp Discovery
Configuring PIM Configuring PIM PIM Bootstrap and RP Discovery Before configuring PIM-SM parameters, please consider the following important guidelines. For correct operation, every PIM-SM router within a PIM-SM domain must be able to map a particular multicast group address to the same Rendezvous Point (RP). Otherwise, some receivers in the domain will not receive some groups.
Page 221: Specifying The Maximum Number Of Rps
Configuring PIM Configuring PIM The group address is listed as 224.0.0.0. The class D group mask (255.255.255.255) has been translated into the Classless Inter-Domain Routing (CIDR) prefix length of /4. The C-RP is listed as 172.21.63.11. The status is enabled. Specifying the Maximum Number of RPs You can specify the maximum number of RPs allowed in a PIM-SM domain.
Page 222: Bootstrap Routers (Bsrs)
Configuring PIM Configuring PIM Configuring a C-BSR You can use the ip pim cbsr command to configure the local router as the candidate-BSR for PIM domain. For example: -> ip pim cbsr 50.1.1.1 priority 100 mask-length 4 This command specifies the router to use its local address 50.1.1.1 for advertising it as the candidate-BSR for that domain, the priority value of the local router as a C-BSR to be 100, and the mask-length that is advertised in the bootstrap messages as 4.
Page 223: Configuring Static Rp Groups
Configuring PIM Configuring PIM The list of reachable C-RPs is also referred to as an RP set. To view the current RP set, use the show ip pim group-map command. For example: -> show ip pim group-map Origin Group Address/Pref Length RP Address Mode Precedence...
Page 224: Group-To-Rp Mapping
Configuring PIM Configuring PIM Verifying Static-RP Configuration To view current Static RP Configuration settings, use the show ip pim static-rp command. For example: -> show ip pim static-rp Group Address/Pref Length RP Address Mode Override Precedence Status ---------------------------+-------------+-----+--------+----------+-------- 224.0.0.0/4 172.21.63.11 false none enabled...
Page 225: Verifying Keepalive Period
Configuring PIM Configuring PIM Verifying Keepalive Period To view the configured keepalive period, use the show ip pim sparse command. For example: -> show ipv6 pim sparse Status = enabled, Keepalive Period = 210, Max RPs = 32, Probe Time = 5, Register Suppress Timeout = 60,...
Page 226: Verifying The Notification Period
Configuring PIM Configuring PIM Verifying the Notification Period To view the configured notification period, use the show ip pim notifications command. For example: -> show ip pim notifications Neighbor Loss Notifications Period Count Invalid Register Notifications Period = 65535 Msgs Rcvd Origin = None Group...
Page 227: Verifying Pim Configuration
Configuring PIM Verifying PIM Configuration Verifying PIM Configuration A summary of the show commands used for verifying PIM configuration is given here: show ip pim sparse Displays the status of the various global parameters for PIM-Sparse Mode. show ip pim dense Displays the status of the various global parameters for PIM-Dense Mode.
Page 228: Pim For Ipv6 Overview
PIM for IPv6 Overview Configuring PIM PIM for IPv6 Overview IP version 6 (IPv6) is a new version of the Internet Protocol, designed as the successor to IP version 4 (IPv4), to overcome certain limitations in IPv4. IPv6 adds significant extra features that were not possible with IPv4.
Page 229: Quick Steps For Configuring Ipv6 Pim-Dm
Configuring PIM Quick Steps for Configuring IPv6 PIM-DM Quick Steps for Configuring IPv6 PIM-DM Note. PIM requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM or DVMRP) is enabled globally and on an interface and when the operational status of the interface is up.
Page 230 Quick Steps for Configuring IPv6 PIM-DM Configuring PIM -> show ipv6 pim sparse Status = enabled, Keepalive Period = 210, Max RPs = 32, Probe Time = 5, Register Suppress Timeout = 60, RP Switchover = enabled, SPT Status = enabled, The display for dense mode is similar to the one shown here: ->...
Page 231: Configuring Ipv6 Pim
Configuring PIM Configuring IPv6 PIM Configuring IPv6 PIM This section describes using Alcatel-Lucent’s Command Line Interface (CLI) command to complete the following steps to configure PIM in an IPv6 environment: • Enabling/disabling IPv6 PIM on a specific interface • Enabling/disabling IPv6 PIM mode on the switch •...
Page 232: Disabling Ipv6 Pim Mode On The Switch
Configuring IPv6 PIM Configuring PIM -> ipv6 pim sparse admin-state enable To globally enable IPv6 PIM-Dense Mode on the switch, use the ipv6 pim dense admin-state command. Enter the command syntax as shown below: -> ipv6 pim dense admin-state enable Disabling IPv6 PIM Mode on the Switch To globally disable IPv6 PIM-Sparse Mode on the switch, use the ipv6 pim sparse admin-state command.
Page 233: Mapping An Ipv6 Multicast Group To A Pim Mode
Configuring PIM Configuring IPv6 PIM Mapping an IPv6 Multicast Group to a PIM Mode PIM mode is an attribute of the IPv6 multicast group mapping and cannnot be configured on an interface basis. The Dense mode or Source-Specific Multicast mode can be configured only on an IPv6 multicast group basis.
Page 234: Verifying Group Mapping
Configuring IPv6 PIM Configuring PIM Verifying Group Mapping To display the static configuration of IPv6 multicast group mappings for PIM-Dense Mode (DM), use the show ipv6 pim dense group command. For example: -> show ipv6 pim dense group Group Address/Pref Length Mode Override Precedence Status ---------------------------+-----+--------+----------+--------...
Page 235: Configuring Candidate Bootstrap Routers (C-Bsrs) For Ipv6 Pim
Configuring PIM Configuring IPv6 PIM same priority value and the same hash value, the C-RP with the highest IPv6 address is selected by the There may be multiple C-RPs defined for IPv6 in order to support different C-RPs for different zones. A particular C-RP will unicast the C-RP-Adv messages to the BSR for each scope zone for which it has state.
Page 236: Bootstrap Routers (Bsrs)
Configuring IPv6 PIM Configuring PIM Elected BSR = False, Timer = 00h:00m:00s For more information about these displays, see the “PIM Commands” chapter in the OmniSwitch CLI Reference Guide. Bootstrap Routers (BSRs) As described in the “PIM Overview” section, the role of a Bootstrap Router (BSR) is to keep routers in the network “up to date”...
Page 237: Group-To-Rp Mapping
Configuring PIM Configuring IPv6 PIM over which configuration is overridden by this static configuration. If the priority option has been defined, a value of 65535 can be used to unset the priority You can also specify whether or not this static RP configuration to override the dynamically learned RP information for the specified group using the override parameter.
Page 238: Configuring Rp-Switchover For Ipv6 Pim
Configuring IPv6 PIM Configuring PIM Configuring RP-Switchover for IPv6 PIM You can configure an RP to attempt switching to native forwarding upon receiving the first register-encap- sulated packet from the source DR in the IPv6 PIM domain. For example: -> ipv6 pim rp-switchover enable The above command enables the RP to switch to native forwarding.
Page 239: Verifying Ipv6 Pim Configuration
Configuring PIM Verifying IPv6 PIM Configuration Verifying IPv6 PIM Configuration A summary of the show commands used for verifying PIM configuration is given here: show ipv6 pim sparse Displays the status of the various global parameters for the IPv6 PIM- Sparse Mode.
Page 240 Verifying IPv6 PIM Configuration Configuring PIM page 6-44 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...
Page 241: Appendix A Software License And Copyright Statements
Licensee further acknowledges and agrees that all rights, title, and interest in and to the Licensed Materials are and shall remain with Alcatel-Lucent and its licen- sors and that no such right, license, or interest shall be asserted with respect to such copyrights and trade- marks.
Page 242 Period, a defect in the Licensed Files appears, Licensee may return the Licensed Files to Alcatel-Lucent for either replacement or, if so elected by Alcatel-Lucent, refund of amounts paid by Licensee under this License Agreement. EXCEPT FOR THE WARRANTIES SET FORTH ABOVE, THE LICENSED MATERIALS ARE LICENSED “AS IS”...
Page 243 14.Third Party Materials. Licensee is notified that the Licensed Files contain third party software and materials licensed to Alcatel-Lucent by certain third party licensors. Some third party licensors are third part beneficiaries to this License Agreement with full rights of enforcement. Please refer to the section entitled “Third Party Licenses and Notices”...
Page 244: Third Party Licenses And Notices
/flash/foss. Also, if needed, we provide all FOSS (Free and Open Source Software) source code used into this release at the following URL: https://service.esd.alcatel-lucent.com/portal/page/portal/EService/release page A-4 OmniSwitch AOS Release 7 Advanced Routing Guide...
Page 245 Index internal vs. external MED values 3-23 overview policies 3-12, 3-45 redistribution 3-75 regular expressions 3-13 restarting a peer 3-29 route dampening 3-16, 3-36 route notation 3-16 route reflection 3-9, 3-40 aggregate routes setting the AS number 3-21 3-32 setting the default local preference 3-21 application examples specifications...
Page 246 Index dependent downstream routers ip bgp graceful-restart restart-interval command 3-59 enabling ip bgp neighbor advertisement-interval command 3-31 graft acknowledgment messages ip bgp neighbor auto-restart command 3-29 graft messages ip bgp neighbor clear command 3-29 grafting 5-7, 5-16 ip bgp neighbor clear soft command 3-29 hop count ip bgp neighbor command...
Page 247 Index ip multicast status command 5-3, 6-19, 6-33 configuring ip ospf area command 1-16, 2-15 creating ip ospf area summary command 1-17 deleting ip ospf area type command 1-16, 2-15 overview ip ospf exit-overflow-interval command 1-29 specifications ip ospf extlsdb-limit command 1-29 multicast routing ip ospf host command...
Page 248 Index creating 3-47 route reflection 3-40 peer configuring 3-42 clearing statistics 3-30 redundant route reflectors 3-42 configuring 3-26 routers configuring IPv6 3-68 area border routers 1-9, 2-10 defaults 3-26 AS boundary routers 1-9, 2-10 restarting 3-29 backbone routers configuring OSPF 1-29, 2-24 6-9, 6-26, 6-40 internal routers...
Page 249: Index
Index Verify DVMRP Configuration 5-17 virtual links 1-9, 2-10 creating 1-22 deleting 1-22, 2-18 modifying 1-22, 2-18 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011 Index-5...
Page 250 Index Index-6 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2011...

This manual is also suitable for:

Omniswitch aos 7

Alcatel 060320-10, Rev. B Configuration Manual

About this Guide

Chapter 1 Configuring OSPF

Chapter 2 Configuring Ospfv3

Chapter 3 Configuring BGP

Chapter 4 Configuring Multicast Address Boundaries

Chapter 5 Configuring DVMRP

Chapter 6 Configuring PIM

Appendix A Software License and Copyright Statements

Index

Quick Links

Need help?

Questions and answers

Related Manuals for Alcatel 060320-10, Rev. B

Summary of Contents for Alcatel 060320-10, Rev. B