Part No. 060320-10, Rev. K March 2015 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide www.alcatel-lucent.
This user guide documents AOS Release 7.3.4 for the OmniSwitch 10K and OmniSwitch 6900. The functionality described in this guide is subject to change without notice. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright © 2015 by Alcatel-Lucent.
Contents About This Guide .......................................................................................................... xi Supported Platforms .......................................................................................................... xi Who Should Read this Manual? ........................................................................................ xi When Should I Read this Manual? ....................................................................................
Contents Configuring Router Capabilities ............................................................................1-28 Converting Local Interfaces into OSPF Passive Interface Using Route Map ........1-29 Configuring Static Neighbors .................................................................................1-30 Configuring Redundant CMMs for Graceful Restart .............................................1-31 OSPF Application Example ..................................................................
Contents IS-IS Quick Steps ............................................................................................................3-5 IS-IS Overview ................................................................................................................ 3-8 IS-IS Packet Types .................................................................................................3-10 IS-IS Areas ...........................................................................................................
Contents Regular Expressions ........................................................................................4-13 Route Dampening ...................................................................................................4-16 CIDR Route Notation .............................................................................................4-16 BGP Configuration Overview .......................................................................................4-17 Starting BGP ...................
Contents AS 200 .............................................................................................................4-55 AS 300 .............................................................................................................4-56 Displaying BGP Settings and Statistics ........................................................................4-57 BGP for IPv6 Overview ................................................................................................
Contents Multicast Addresses and the IANA ..........................................................................5-4 Administratively Scoped Multicast Addresses ..................................................5-4 Source-Specific Multicast Addresses ................................................................5-4 Multicast Address Boundaries .................................................................................5-5 Concurrent Multicast Addresses ............................................
Contents IPv6 PIM Defaults ....................................................................................................7-5 Quick Steps for Configuring PIM-DM ...........................................................................7-7 PIM Overview .................................................................................................................7-9 PIM-Sparse Mode (PIM-SM) ...................................................................................
Contents Disabling IPv6 PIM on a Specific Interface ....................................................7-35 Viewing IPv6 PIM Status and Parameters for a Specific Interface .................7-35 Enabling IPv6 PIM Mode on the Switch .........................................................7-35 Disabling IPv6 PIM Mode on the Switch ........................................................7-36 Checking the Current Global IPv6 PIM Status ...............................................
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 and OmniSwitch 6900 switches.
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 examples. CLI commands are text-based commands used to manage the switch through serial (console port) connections or via Telnet sessions. Procedures for other switch management methods, such as web-based (WebView or OmniVista) or SNMP, are outside the scope of this guide.
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.
Documentation Roadmap About This Guide The OmniSwitch AOS Release 7 Data Center Switching Guide includes configuration information for data center networks using virtualization technologies (SPBM and UNP) and Data Center Bridging protocols (PFC, ETC, and DCBX). Anytime The OmniSwitch AOS Release 7 CLI Reference Guide contains comprehensive information on all CLI commands supported by the switch.
About This Guide Related Documentation Related Documentation The following are the titles and descriptions of all the related OmniSwitch user manuals: • OmniSwitch 10K Getting Started Guides Describes the hardware and software procedures for getting an OmniSwitch up and running. Also provides information on fundamental aspects of OmniSwitch software architecture.
Technical Support About This Guide Technical Support An Alcatel-Lucent service agreement brings your company the assurance of 7x24 no-excuses technical support. You’ll also receive regular software updates to maintain and maximize your Alcatel-Lucent product’s features and functionality and on-site hardware replacement through our global network of highly qualified service delivery partners.
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 Autonomous 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.
OSPF Specifications Configuring OSPF OSPF Specifications Platforms supported OmniSwitch 10K, 6900 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 10 Maximum number of interfaces per router 128 Maximum number of interfaces per area 100 Maximum number of Link State Database entries 100K Maximum n
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 0 Assigns a limit to the number of External Link-State Database (LSDB) entries.
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: 1 Create a VLAN using the vlan command. For example: -> vlan 5 -> vlan 5 admin-state enable 2 Assign a router IP address and subnet mask to the VLAN using the ip interface command. For example: -> ip interface vlan-5 vlan 5 address 120.1.4.1 mask 255.0.0.0 3 Assign a port to the created VLANs using the vlan members command.
Configuring OSPF OSPF Quick Steps 9 Enable the OSPF interfaces using the ip ospf interface admin-state command. For example: -> ip ospf interface vlan-5 admin-state enable 10 You can now display the router OSPF settings by using the show ip ospf command.
OSPF Quick Steps Configuring OSPF 11 You can display OSPF area settings using the show ip ospf area command. For example: -> show ip ospf area 0.0.0.
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 Autonomous 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.
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.
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 following 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. • Area border routers. A router that attaches to multiple areas. Area border routers run multiple copies of the SPF algorithm, one copy for each attached area.
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.
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. The primary difference is that selected external routing information can be imported into an NSSA and then redistributed into the rest of the OSPF routing domain.
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. In the network illustration below, there are two paths from Source router A to Destination router B.
Configuring OSPF OSPF Overview Graceful Restart on Switches with Redundant CMMs A chassis-based switch with two Chassis management Modules (CMMs) can support redundancy where if the primary CMM fails or goes offline for any reason, the secondary CMM is instantly notified. The secondary CMM automatically assumes the primary role. This switch between the primary and secondary CMMs is known as takeover. When a takeover occurs, which can be planned (e.g., the users performs the takeover) or unplanned (e.g.
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: • Set up the basics of the OSPF network by configuring the required VLANs, assigning ports to the VLANs, and assigning router identification numbers to the routers involved.
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. A VLAN should exist for each instance in which the backbone connects two routers.
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. For the operation to take effect the switch needs to be rebooted. Creating an OSPF Area OSPF allows a set of network devices in an AS system to be grouped together in areas.
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. (Configuring ranges is described in “Setting Area Ranges” on page 1-18.) For example, to enable summarization for Area 1.1.1.
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. Specify the stub area and select a cost value or a route type, as shown: -> ip ospf area 1.1.1.1 default-metric 0 cost 50 or -> ip ospf area 1.1.1.
Configuring OSPF -> -> -> -> -> -> -> -> ip ip ip ip ip ip ip ip ospf ospf ospf ospf ospf ospf ospf ospf Configuring OSPF area 1.1.1.1 default-metric 0 interface vlan-5 interface vlan-5 area 1.1.1.1 interface vlan-5 admin-state enable interface vlan-6 interface vlan-6 area 0.0.0.0 interface vlan-6 admin-state enable admin-state enable 2 Enter the following on Router A: -> -> -> -> -> -> -> ip ip ip ip ip ip ip load ospf ospf ospf ospf ospf ospf ospf area 1.1.1.1 area 1.1.1.
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. Interface Authentication OSPF allows for the use of authentication on configured interfaces.
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.
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” on page 1-9 and refer to the figure on page 1-9.
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. The ip route-map command is used to configure route map statements and provides the following action, match, and set parameters: ip route-map action ... ip route-map match ... ip route-map set ...
Configuring OSPF Configuring OSPF 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 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.
Configuring OSPF Configuring OSPF 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. To add match and set statements to an existing route map sequence, specify the same route map name and sequence number for each statement.
Configuring OSPF Configuring OSPF 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. The route map is then applied to all the addresses contained within the access list.
Configuring OSPF Configuring OSPF To remove a route map redistribution configuration, use the no form of the ip redist command.
Configuring OSPF Configuring OSPF Configuring Router Capabilities The following list shows various commands that can be useful in tailoring a router’s performance capabilities. 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. The overflow interval is the time whereby the router will wait before attempting to leave the database overflow state.
Configuring OSPF Configuring OSPF Converting Local Interfaces into OSPF Passive Interface Using Route Map Passive interfaces do not accept or send routing updates. In an OSPF network, an interface can be configured as passive (by setting the hello interval and dead interval to “0”) mainly to add this interface in the updates to the OSPF neighbor.
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” flag to be set for every neighbor.
Configuring OSPF Configuring OSPF Configuring Redundant CMMs for Graceful Restart By default, OSPF graceful restart is disabled. To enable OSPF graceful restart on OmniSwitch chassisbased switches, use the ip ospf restart-support command by entering ip ospf restart-support followed by planned-unplanned.
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. The following diagram is a simple OSPF network. It will be created by the steps listed on the following pages: VLAN 10 Interface 10.0.0.1 Area 0.0.0.
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. Router 1 connects to Router 2, Router 2 connects to Router 3, and Router 3 connects to Router 1 using 10/100 Ethernet cables.
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. • VLAN 23 handles the backbone connection from Router 2 to Router 3, using the IP router port 23.0.0.2 and physical port 2/2. • VLAN 20 handles the device connections to Router 2, using the IP router port 20.0.0.2 and physical ports 2/3-5.
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. Router 2 -> ip ospf area 0.0.0.0 -> ip ospf area 0.0.0.2 These commands created Area 0.0.0.0 (the backbone) and Area 0.0.0.2 (the area for Router 2). Both of these areas are also enabled. Router 3 -> ip ospf area 0.0.0.0 -> ip ospf area 0.
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. IP router port 23.0.0.2 was associated to OSPF interface vlan-23, enabled, and assigned to the backbone. IP router port 20.
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. show ip ospf ext-lsdb Displays external Link State Advertisements from the areas to which the router is attached.
Verifying OSPF Configuration page 1-38 Configuring OSPF OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
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,” for 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).
OSPFv3 Specifications Configuring OSPFv3 OSPFv3 Specifications Platforms supported OmniSwitch 10K, 6900 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 2740—OSPF for IPv6 Maximum number of areas 5 Maximum number of interfaces per router 20 Maximum number of interfaces pe
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 tive status. enabled Configures the administrative status ipv6 ospf interface admin-state for an OSPF interface. enabled Configures OSPFv3 redistribution. ipv6 redist disabled Configures timers for Shortest Path First (SPF) calculation.
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: 1 Create a VLAN using the vlan command. For example: -> vlan 5 -> vlan 5 admin-state enable 2 Create an IPv6 interface on the vlan using the ipv6 interface command. For example: -> ipv6 interface test vlan 1 3 Configure an IPv6 address on the vlan using the ipv6 address command.
Configuring OSPFv3 OSPFv3 Quick Steps 9 You can now display the router OSPFv3 settings by using the show ipv6 ospf command.
OSPFv3 Quick Steps Configuring OSPFv3 11 You can display OSPFv3 interface settings using the show ipv6 ospf interface command.
Configuring OSPFv3 OSPFv3 Quick Steps 12 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 Advertising Rtr Sequence # Age ----------------+----------+------------+-----------------+----------+--------0.0.0.0 Router 0 172.28.4.28 8000003b 203 0.0.0.0 Router 0 172.28.4.29 80000038 35 0.0.0.0 Network 9 172.28.4.
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. Each participating router distributes its local state (i.e.
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.
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. • Area border router (ABR). A router that attaches to multiple areas and to the backbone area.
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.
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. In the network illustration below, there are two paths from Source router A to Destination router B.
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: • Set up the basics of the OSPFv3 network by configuring the required VLANs, assigning ports to the VLANs, and assigning router identification numbers to the routers involved.
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. VLAN configuration is described in “Configuring VLANs” in the OmniSwitch AOS Release 7 Network Configuration Guide.
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. For the operation to take effect the switch needs to be rebooted. Creating an OSPFv3 Area OSPFv3 allows a set of network devices in an Autonomous System (AS) to be grouped together in areas.
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 command as shown: -> no ipv6 ospf area 1.1.1.
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.
Configuring OSPFv3 Configuring OSPFv3 2 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 3 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.
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. An action statement configures the route map name, sequence number, and whether or not redistribution is permitted or denied based on route map criteria. • Match. A match statement specifies criteria that a route must match.
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 parameter.
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. To add match and set statements to an existing route map sequence, specify the same route map name and sequence number for each statement.
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. The route map is then applied to all the addresses contained within the access list.
Configuring OSPFv3 Configuring OSPFv3 To remove a route map redistribution configuration, use the no form of the ipv6 redist command.
Configuring OSPFv3 Configuring OSPFv3 Configuring Router Capabilities The following list shows various commands that can be useful in tailoring a router’s performance capabilities. 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. ipv6 ospf mtu-checking Enables or disables the use of Maximum Transfer Unit (MTU) checking on received OSPFv3 database description packets.
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. The following diagram is a simple OSPFv3 network. It will be created by the steps listed on the following pages. VLAN 10 Area 0.0.0.1 Router 1 Router ID 1.
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.
Configuring OSPFv3 -> -> -> -> vlan ipv6 ipv6 vlan OSPFv3 Application Example 20 interface vlan-20 vlan 20 address 2001:4::1/64 vlan-20 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 2001:2::2/64 and physical port 2/1. • VLAN 23 handles the backbone connection from Router 2 to Router 3, using the IP router port 2001:5::1/64 and physical port 2/2.
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 -> ipv6 ospf area 0.0.0.0 -> ipv6 ospf area 0.0.0.1 These commands created and enabled area 0.0.0.0 (the backbone) and area 0.0.0.1 (the area for Router 1). Router 2 -> ipv6 ospf area 0.0.0.0 -> ipv6 ospf area 0.0.0.
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. IPv6 router interface vlan-31 was associated with OSPFv3 interface vlan-31, enabled, and assigned to the backbone.
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. show ipv6 ospf border-routers Displays information regarding all or specified border routers.
3 Configuring IS-IS Intermediate System-to-Intermediate System (IS-IS) is an International Organization for Standardization (ISO) dynamic routing specification. IS-IS is a shortest path first (SPF), or link state protocol. It is an interior gateway protocol (IGP) that distributes routing information between routers in a single Autonomous System (AS) in IP as well as in OSI environments. IS-IS chooses the least-cost path as the best path.
IS-IS Specifications Configuring IS-IS IS-IS Specifications RFCs Supported 1142-OSI IS-IS Intra-domain Routing Protocol 1195-OSI IS-IS for Routing in TCP/IP and Dual Environments 3373-Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Pointto-Point Adjacencies 3567-Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication 2966-Prefix Distribution with two-level IS-IS (Route Leaking) support 2763-Dynamic Host name exchange support 3719-Recommendations for Inte
Configuring IS-IS IS-IS Defaults Table IS-IS Defaults Table The following table shows the default settings of the configurable IS-IS parameters.
IS-IS Defaults Table Configuring IS-IS Parameter Description Command Default Value/Comments IS-IS VLAN interface type ip isis vlan interface-type broadcast Hello authentication (per VLAN) ip isis vlan hello-auth-type none CSNP time interval (per VLAN) ip isis vlan csnp-interval 10 seconds (broadcast) 5 seconds (point-to-point) IS-IS level (per VLAN) ip isis vlan level-capability Level-1/2 LSP time interval (per VLAN) ip isis vlan lsp-pacing-interval 100 milliseconds IS-IS passive interfa
Configuring IS-IS IS-IS Quick Steps IS-IS Quick Steps The following steps are designed to show the user the necessary set of commands for setting up a router to use IS-IS: 1 Create a VLAN using the vlan command. For example: -> vlan 5 name "vlan-5" 2 Assign a port to the VLAN using the vlan command. For example: -> vlan 5 port default 2/1 3 Assign an IP address to the VLAN using the ip interface command. For example: -> ip interface vlan-5 address 120.1.4.1 mask 255.0.0.
IS-IS Quick Steps LSP Wait Adjacency Check L1 Auth Type L2 Auth Type L1 Wide Metrics-only L2 Wide Metrics-only L1 LSDB Overload L2 LSDB Overload L1 LSPs L2 LSPs Last SPF SPF Wait Hello-Auth Check Csnp-Auth Check Psnp-Auth Check L1 Hello-Auth Check L1 Csnp-Auth Check L1 Psnp-Auth Check L2 Hello-Auth Check L2 Csnp-Auth Check L2 Psnp-Auth Check Area Address Configuring IS-IS : : : : : : : : : : : : : : : : : : : : : : Max :5 sec, Initial :0 sec, Second :1 sec Loose None None Disabled Disabled Disabled Disa
Configuring IS-IS IS-IS Quick Steps ------------------------------------------------------------------------------vlans : 1 ============================================================================== OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 3-7
IS-IS Overview Configuring IS-IS IS-IS Overview IS-IS is an SPF or link state protocol. IS-IS is also an IGP that distributes routing information between routers in a single AS. It supports pure IP and OSI environments, as well as dual environments (both IP and OSI). However, it is deployed extensively in IP-only environments. IS-IS uses a two-level hierarchy to support large routing domains. A large routing domain may be administratively divided into areas, with each router residing in exactly one area.
Configuring IS-IS IS-IS Overview Adjacencies control the distribution of routing protocol packets. Routing protocol packets are sent and received only on adjacencies. In particular, distribution of topological database updates proceeds along adjacencies. After establishing adjacencies, routers will build a link-state packet (LSP) based upon their local interfaces that are configured for IS-IS and prefixes learned from other adjacent routers.
IS-IS Overview Configuring IS-IS IS-IS Packet Types IS-IS transmits data in little chunks known as packets. There are four packet types in IS-IS. They are: • Intermediate System-to-Intermediate System Hello (IIH)—Used by routers to detect neighbors and form adjacencies. • Link State Packet (LSP)—Contains all the information about adjacencies, connected IP prefixes, OSI end system, area address, etc.
Configuring IS-IS IS-IS Overview An area’s topology is visible only to the members of that area. Routers inside a given area do not know the detailed topology outside the area. This isolation of knowledge enables the protocol to reduce routing traffic by concentrating on small areas of an AS, as compared to treating the entire AS as a single link state domain. In IS-IS, the router belongs entirely to a single area.
IS-IS Overview Configuring IS-IS Graceful Restart on Stacks with Redundant Switches OmniSwitch stacks with two or more switches support redundancy; if the primary switch fails or goes offline, the secondary switch is instantly notified. The secondary switch automatically assumes the primary role. This transition from secondary to primary is known as takeover. When the router is in the graceful restart mode, it informs its neighbors of the restart.
Configuring IS-IS IS-IS Overview If the restarting router, Router X, is identified as the Designated Router (DIS) on the network segment S at the beginning of the helping relationship, the helper neighbor, Router Y, will maintain Router X as the DIS until the helping relationship is terminated. If there are multiple adjacencies with the restarting Router X, Router Y will act as a helper on all other adjacencies.
Configuring IS-IS Configuring IS-IS Configuring IS-IS Configuring IS-IS on a router requires several steps. Depending on your requirements, you may need to perform all the steps listed below. By default, IS-IS is disabled on the router. Configuring IS-IS consists of the following tasks: • Set up the basics of the IS-IS network by configuring the required VLANs and assigning ports to the VLANs. This is described in “Preparing the Network for IS-IS” on page 3-15. • Enable IS-IS.
Configuring IS-IS Configuring IS-IS Preparing the Network for IS-IS IS-IS operates over normal switch functions, using existing ports, virtual ports, VLANs, etc. However, the following network components should already be configured: • Configure VLANs that are to be used in the IS-IS network. VLANs should be created for all the connected devices that will participate in the IS-IS network. VLAN configuration is described in “Configuring VLANs” in the OmniSwitch AOS Release 7 Network Configuration Guide.
Configuring IS-IS Configuring IS-IS Removing IS-IS To remove IS-IS 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 IS-IS. For the operation to take effect the switch needs to be rebooted. Creating an IS-IS Area ID IS-IS allows a set of network devices in an AS to be grouped together in areas. Each area is identified by an area ID.
Configuring IS-IS Configuring IS-IS -> ip isis vlan 10 address-family v6 To disable IPv4/IPv6 IS-IS circuit on a particular VLAN, use the no form of the ip isis interface, as shown: -> no ip isis vlan 10 address-family v6 Enabling a IS-IS VLAN Circuit Once the circuit is created, it must be enabled using the ip isis vlan admin-state command, as shown: -> ip isis vlan 10 admin-state enable Configuring the IS-IS Level The Autonomous System is divided into multiple areas to reduce the control traffic and
Configuring IS-IS Configuring IS-IS When the level capabilities are configured both globally and on per-interface basis, the combination of the two settings will decide the potential adjacency.
Configuring IS-IS Configuring IS-IS Note. IS-IS routes are not summarized by default. If you do not specify the level while configuring the summarization, level-1/2 routes are summarized by default. IS-IS IPv6 route summarization allows users to create aggregate IPv6 addresses that include multiple groups of IPv6 addresses for a given IS-IS level. IPv6 Routes redistributed from other routing protocols also can be summarized. It is similar to the OSPF area-range command.
Configuring IS-IS Configuring IS-IS Simple Authentication Simple authentication works by including the password in the packet. This helps to protect the routers from a configuration mishap. To enable simple authentication with plain text key on a router, enter the ip isis auth-type command, as shown: -> ip isis auth-type simple key 12345 Here, only routers with simple authentication and simple key “12345” will be able to use the configured interface.
Configuring IS-IS Configuring IS-IS To disable the authentication check for IS-IS PDUs, enter the following: -> ip isis auth-check disable If disabled, the authentication PDUs are generated and the IS-IS PDUs are authenticated on receipt. An error message will be generated in case of a mismatch; but PDUs will not be rejected. Note. By default, authentication check is enabled. IS-IS authentication can be enabled globally for Hello, CSNP, and PSNP packets.
Configuring IS-IS Configuring IS-IS IS-IS Circuit Level Authentication IS-IS authentication can be enabled for Hello packets at a circuit level using ip isis vlan hello-auth-type command. For example, to enable MD5 authentication of Hello PDUs on the IS-IS circuit, enter the following: -> ip isis vlan 10 hello-auth-type md5 key 12345 IS-IS authentication can also be enabled for Hello packets at different levels of an IS-IS circuit using ip isis vlan level hello-auth-type.
Configuring IS-IS Configuring IS-IS The following table shows the various interface parameters that can be set: ip isis vlan csnp-interval Configures the time interval in seconds to send Complete Sequence Number PDUs (CSNP) from the specified VLAN circuit. ip isis vlan lsp-pacing-interval Configures the interval between IS-IS Link State PDUs (LSP) sent from the specified circuit.
Configuring IS-IS Configuring IS-IS Using Route Maps A route map specifies the criteria that are used to control redistribution of routes between protocols. Such criteria are defined by configuring route map statements. There are three different types of statements: • Action—An action statement configures the route map name, sequence number, and whether or not redistribution is permitted or denied based on route map criteria. • Match—A match statement specifies criteria that a route must match.
Configuring IS-IS Configuring IS-IS tributed into the IS-IS network. All other routes with a different metric value are dropped. Note. Configuring match statement is not required. However, if a route map does not contain any match statement and the route map is applied using the ip 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 parameter.
Configuring IS-IS Configuring IS-IS 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. To add match and set statements to an existing route map sequence, specify the same route map name and sequence number for each statement.
Configuring IS-IS Configuring IS-IS Configuring Access Lists An IP access list provides a convenient way to add multiple IPv4 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. The route map is then applied to all the addresses contained within the access list.
Configuring IS-IS Configuring IS-IS Use the show ip redist command to verify the redistribution configuration: -> show ip redist Source Destination Protocol Protocol Status Route Map ------------+------------+---------+-------------------OSPF ISIS Enabled ospf-to-isis RIP ISIS Enabled rip-to-isis Configuring the Administrative Status of the Route Map Redistribution The administrative status of a route map redistribution configuration is enabled by default.
Configuring IS-IS Configuring IS-IS IS-IS allows redistributing Level-1 IS-IS routes into Level-2 IS-IS routes. This is termed as Level-1 to Level-2 Leaking. This release also supports the prefix distribution from the level-2 IS-IS routes to level-1 IS-IS routes. The following example configures the IS-IS Level-1 to Level-2 Leaking routes using a route map (is2is) to filter specific routes.
Configuring IS-IS Configuring IS-IS Configuring Router Capabilities The following table lists various commands that can be useful in tailoring a router’s performance capabilities. All the listed parameters have defaults that are acceptable for running an IS-IS network. ip isis overload Sets the IS-IS router to operate in the overload state. ip isis overload-on-boot Configures the router to be in the overload state. ip isis strict-adjacency-check Enables or disables the adjacency check configuration.
Configuring IS-IS IS-IS Application Example IS-IS Application Example This section will demonstrate how to set up a simple IS-IS network. It uses two routers, each with an area. Each router is a L1-L2 capable router and can communicate with different areas. This section will demonstrate how to set it up by explaining the necessary commands for each router. The following diagram is a simple IS-IS network. This network will be created using the steps explained below.
IS-IS Application Example Configuring IS-IS -> vlan 5 port default 1/10 -> ipv6 interface vlan-isis vlan 5 -> ipv6 address 2001::2/64 vlan-isis Step 2: Enable IS-IS The next step is to load and enable IS-IS on each router. The commands for this are shown below (the commands are the same on each router): -> ip load isis -> ip isis admin-state enable Step 3: Create and Enable Area ID Now the areas should be created and enabled. The commands for this are shown below: Router 1 -> ip isis area-id 00.
Configuring IS-IS IS-IS Application Example Step 6: Examine the Network After the network has been created, you can check various aspects of it using show commands: • For IS-IS in general, use the show ip isis statistics command. • For SPF details, use the show ip isis spf command. • For summarization details, use the show ip isis summary-address command. • To check for adjacencies formed with neighbors, use the show ip isis adjacency command. • For routes, use the show ip isis routes command.
Multi-Topology IS-IS Overview Configuring IS-IS Multi-Topology IS-IS Overview Multi-topology (M-ISIS) support is necessary in IS-IS to support network domains in which non-dual stack IS-IS routers exist. The default protocol behavior of IS-IS is to construct shortest paths through the network using the routers' MAC addresses with no regard to the different IP address families supported.
Configuring IS-IS Multi-Topology IS-IS Overview For backwards compatibility with non M-ISIS aware routers, even if M-ISIS capability is enabled, AOS IS-IS will continue to exchange IPv4 prefixes in the default IPv4 reachability TLVs (and not in the M-ISIS TLVs in MT ID 0). SPF processing for IPv4 will include default IPv4 Reachability TLVs along with those received in MT ID 0 TLVs (if any).
Verifying IS-IS Configuration Configuring IS-IS Verifying IS-IS Configuration To verify information about adjacent routers, summary-address, SPF, or IS-IS in general, use the show commands listed in the following table: show ip isis adjacency Displays information about IS-IS adjacent routers. show ip isis database Displays IS-IS LSP database information of the adjacent routers. show ip isis hostname Displays the database of IS-IS host names.
4 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). The Alcatel-Lucent implementation of BGP-4 and Multiprotocol Extensions to BGP-4 is based on several RFCs listed below.
In This Chapter Configuring BGP In This Chapter The topics and configuration procedures in this chapter include: • Setting up global BGP parameters, such as a router’s Autonomous System (AS) number and default local preference. See “Setting Global BGP Parameters” on page 4-20. • Configuring a BGP peer and setting various parameters on that peer, such as timers, soft reconfiguration, and policies. See “Configuring a BGP Peer” on page 4-26. • Configuring the advertising of IPv4 routes for IPv4 BGP peer.
Configuring BGP BGP Specifications BGP Specifications Platforms Supported OmniSwitch 10K, 6900 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 4486–Subcode
Quick Steps for Using BGP Configuring BGP Quick Steps for Using BGP The following steps and points summarize enabling BGP on the OmniSwitch. 1 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.
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. BGP is a distance vector protocol, like the Routing Information Protocol (RIP).
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).
Configuring BGP BGP Overview • Support for two new optional transitive attributes AS4_PATH and AS4_AGGREGATE. These attribute are used when new BGP speakers are interacting with OLD BGP speaker. • To establish a neighbor relationship between non-mappable BGP 4-octet ASNs with BGP 2-octet ASNs the reserved 2-octet ASN AS_TRANS 23456 is used. • The 4-octet AS Specific Extended Community as specified in RFC 5668 will be used with non- mappable 4-octet ASNs.
BGP Overview Configuring BGP 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). ASs with more than one connection to the outside world are called multi-homed transit ASs, and can be used to transit traffic by other ASs.
Configuring BGP BGP Overview 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. A BGP speaker can use this attribute in conjunction with other attributes to control which routes to accept, prefer, and pass on to other BGP neighbors.
BGP Overview Configuring BGP Route Reflectors Route reflectors are useful if the internal BGP mesh becomes very large. A route reflector is a concentration 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). The router reflectors then peer with each other.
Configuring BGP BGP Overview Since the router clients in this scenario only peer with the router reflector, the session load per router is significantly reduced. Route Reflectors are discussed further in “Setting Up Route Reflection” on page 4-41. 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.
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. Policies act as filters to either permit or deny specified routes that are being learned or advertised from a peer.
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 200, anywhere within the AS path list.
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, 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.
Configuring BGP ^500 [100-199]* 500 (900|950)$ BGP Overview Matches: 100 350 501 200 250 260 270 280 600 Doesn’t Match: 100 600 100 400 600 700 Meaning: Only routes consisting of a single AS, 500. Matches: 500 Doesn’t Match: 500 600 100 500 600 Meaning: Any route which ends with any number of occurrences of AS numbers in the range 100 to 199, followed by 500, followed by either a 900 or 950.
BGP Overview Configuring BGP Route Dampening Route dampening is a mechanism for controlling route instability. If a route (or path) is frequently advertised 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. This instability is also known as flapping.
Configuring BGP BGP Configuration Overview BGP Configuration Overview The following steps and points summarize configuring BGP. Not all of the following are necessary. For the necessary steps to enable BGP on the OmniSwitch, see “Quick Steps for Using BGP” on page 4-4. 1 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.
Starting BGP Configuring BGP Starting BGP Before BGP is operational on the router must load it to running memory and then administratively enable the protocol using the ip load bgp and ip bgp admin-state commands. Follow these steps to start BGP. 1 Configure the router's unique router-id and primary address. Assign the BGP local speaker's router-id and primary IP address that uniquely identifies the router in the routing domain.
Configuring BGP Starting BGP Function Command Sets a confederation identification value for the local BGP speaker ip bgp confederation identifier OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 4-19
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. This section describes how to enable or disable BGP global parameters.
Configuring BGP Setting Global BGP Parameters Setting the Router AS Number The router takes a single Autonomous System (AS) number. The user 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. In such a case these BGP peers with a different AS would be considered external BGP (EBGP) peers and the communication with those peers would be EBGP.
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. The AS path is always advertised in BGP route updates, however you can control whether BGP uses this attribute when comparing routes.
Configuring BGP Setting Global BGP Parameters Controlling the use of MED Values The Multi Exit Discriminator, or MED, is used by border routers (i.e., BGP speakers with links to neighboring autonomous systems) to help choose between multiple entry and exit points for an autonomous system. It is only relevant when an AS has more than one connection to a neighboring AS. If all other factors are equal, the path with the lowest MED value takes preference over other paths to the neighbor AS.
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. This is known as synchronization.
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. show ip bgp aggregate-address Displays aggregate configuration information.
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. Internal neighbors may be located anywhere within the same autonomous system while external neighbors are adjacent to each other and share a subnet. Internal neighbors may or may not share a subnet.
Configuring BGP Configuring a BGP Peer Default Value/ Comments Parameter Description Command Enable or disables maximum prefix warning for a peer. ip bgp neighbor maximum-prefix warning-only 80 percent Allows external peers to communicate with each other even when they are not directly connected. ip bgp neighbor ebgp-multihop disabled Configures the BGP peer name.
Configuring a BGP Peer Configuring BGP Creating a Peer 1 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 2 Assign an AS number to the peer using the ip bgp neighbor remote-as command. For example to assign the peer created in Step 1 to AS number 100, you would enter: -> ip bgp neighbor 190.17.20.
Configuring BGP Configuring a BGP Peer Peer Parameter Command Allows external peers to communicate with each other even when they are not directly connected. ip bgp neighbor ebgp-multihop Sets the BGP peer to use next hop processing behavior. ip bgp neighbor next-hop-self Configures the local BGP speaker to wait ip bgp neighbor passive for this peer to establish a connection. Enables or disables the stripping of private autonomous system numbers from the AS path of routes destined to this peer.
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. The ip bgp neighbor update-source command sets the local interface address or the name through which this BGP peer can be contacted.
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: -> ip bgp neighbor 123.24.5.6 md5 key keyname The peer with IP address 123.24.5.6 will be sent messages using “keyname” as the encryption password. If this is not the password set on peer 123.24.5.
Configuring a BGP Peer Configuring BGP -> ip bgp neighbor 2.2.2.2 update-source Loopback0 See the OmniSwitch AOS Release 7 Network Configuration Guide for more information about configuring an IP Loopback0 interface.
Configuring BGP Configuring Aggregate Routes Configuring Aggregate Routes Aggregate routes are used to reduce the size of routing tables by combining the attributes of several different 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. Aggregate routes do not need to be known to the local BGP speaker.
Configuring Local Routes (Networks) Configuring BGP 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.
Configuring BGP Configuring Local Routes (Networks) 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 community, and the route metric. Local Preference The local preference is a degree of preference to be given to a specific route when there are multiple routes to the same destination.
Configuring Local Routes (Networks) Configuring BGP 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 ---------------+---------------+-----------+---------155.132.40.0 255.255.255.0 disabled not_active 155.132.1.3 255.255.255.
Configuring BGP Controlling Route Flapping Through Route Dampening 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.
Controlling Route Flapping Through Route Dampening Configuring BGP 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: -> no ip bgp dampening Configuring Dampening Parameters There are several factors in configuring route dampening.
Configuring BGP Controlling Route Flapping Through Route Dampening 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.
Controlling Route Flapping Through Route Dampening Configuring BGP 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. Dampening information on the route will start re-accumulating as soon as the command is entered and the statistics are cleared.
Configuring BGP Setting Up Route Reflection 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. However, fully meshed configurations are difficult to scale in large networks.
Setting Up Route Reflection Configuring BGP 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. When the route reflector (Speaker C) receives route information from Speaker A it advertises the information to Speaker B. This set up eliminates the peer connection between Speakers A and B.
Configuring BGP Setting Up Route Reflection 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... Route Advertised To...
Setting Up Route Reflection Configuring BGP To configure a redundant route reflector for this router, use the ip bgp cluster-id command. For example to set up a redundant route reflector at 190.17.21.16, you would enter: -> ip bgp cluster-id 190.17.21.
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.
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 confederation appears as another AS even though the confederation has multiple ASs within it. Within a confederation ASs can distinguish among one another and will advertise routes using EBGP. 1 Specify the confederation identifier for the local BGP router. This value is used to identify the confed- eration affiliation of routes in advertisements.
Configuring BGP Configuring Redistribution Configuring Redistribution It is possible to configure the BGP protocol to advertise routes learned from other routing protocols (external routes) into the BGP network. Such a process is referred to as route redistribution and is configured using the ip redist command. BGP redistribution uses route maps to control how external routes are learned and distributed.
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. To create a route map, use the ip route-map command with the action parameter.
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.
Configuring Redistribution Configuring BGP -> ip route-map rm_1 sequence-number 10 action permit -> ip route-map rm_1 sequence-number 10 match tag 8 -> ip route-map rm_1 sequence-number 10 set metric 1 To configure a new sequence of statements for an existing route map, specify the same route map name but use a different sequence number.
Configuring BGP Configuring Redistribution To add addresses to an access list, use the ip access-list address (IPv4) or the ipv6 access-list address (IPv6) command. For example, the following commands add addresses to an existing access list: -> ip access-list ipaddr address 16.24.2.1/16 -> ipv6 access-list ip6addr address 2001::1/64 Use the same access list name each time the above commands are used to add additional addresses to the same access list.
Configuring Redistribution Configuring BGP -> ip redist ospf into bgp route-map ospf-to-bgp admin-state disable The following command example enables the administrative status: -> ip redist ospf into rip route-map ospf-to-bgp admin-state enable 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 ip ip ip ip ip route-map route-map route-map route-map route-m
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.
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 BGP Speaker 4 40.0.0.2/24 BGP Speaker 5 50.0.0.2/24 EBGP AS 300 EBGP IBGP BGP Speaker 1 40.0.0.1/24 10.0.0.1/24 20.0.0.1/24 BGP Speaker 3 20.0.0.2/24 30.0.0.2/24 BGP Speaker 2 50.0.0.1/24 10.0.0.2/24 30.0.0.1/24 AS 100 In the above network, Speakers 1, 2, and 3 are part of AS 100 and are fully meshed.
Configuring BGP Application Example 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): -> ip bgp neighbor 30.0.0.2 -> ip bgp neighbor 30.0.0.2 remote-as 100 -> ip bgp neighbor 30.0.0.2 admin-state enable -> ip bgp neighbor 10.0.0.1 -> ip bgp neighbor 10.0.0.1 remote-as 100 -> ip bgp neighbor 10.0.0.
Application Example Configuring BGP Administratively enable BGP: -> ip bgp admin-state enable AS 300 BGP Speaker 5 Assign the speaker to AS 300: -> ip bgp autonomous-system 300 Peer with the external speaker in AS 100 (for external BGP): -> ip bgp neighbor 50.0.0.1 -> ip bgp neighbor 50.0.0.1 remote-as 100 -> ip bgp neighbor 50.0.0.
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 configuration 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. show ip bgp aggregate-address Displays aggregate configuration information.
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. These include automatic configuration of hosts, extensive multicasting capabilities, and built-in security using authentication headers and encryption.
Configuring BGP Quick Steps for Using BGP for IPv6 Quick Steps for Using BGP for IPv6 The following steps create an IPv4 BGP peer capable of exchanging IPv6 prefixes: 1 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: -> ip load bgp 2 Assign an Autonomous System (AS) number to the local BGP speaker in this router. You can change the default AS number to fit your network requirements.
Quick Steps for Using BGP for IPv6 Configuring BGP The following steps create an IPv6 BGP peer capable of exchanging IPv6 prefixes: 1 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. 2 Create an IPv6 BGP peer entry. The local BGP speaker should be able to reach this peer. The IPv6 address you assign the peer should be valid.
Configuring BGP 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.
Configuring BGP for IPv6 Configuring BGP IPv6 Peer Command Defaults The following table lists the default values for many of the peer commands: Parameter Description Command Default Value/ Comments Enables or disables BGP peer. ipv6 bgp neighbor admin-state disabled Assigns an AS number to the BGP peer. ipv6 bgp neighbor remote-as 1 Configures the time interval for updates between external BGP peers.
Configuring BGP Configuring BGP for IPv6 Parameter Description Command Default Value/ Comments Enables or disables the stripping of private autonomous system numbers from the AS path of routes destined to this peer. ipv6 bgp neighbor remove-private-as disabled Enables or disables BGP peer soft reconfiguration. ipv6 bgp neighbor soft-reconfiguration enabled Configures this peer as a member ip bgp confederation neighbor of the same confederation as the local BGP speaker.
Configuring BGP for IPv6 Configuring BGP 3 Enable IPv6 unicast capability for the IPv4 BGP peer using the ip bgp neighbor activate-ipv6 command, as shown: -> ip bgp neighbor 190.17.20.16 activate-ipv6 4 Set the IPv6 next hop address for IPv6 prefixes advertised to the IPv4 BGP peer using the ip bgp neighbor ipv6-nexthop command, as shown: -> ip bgp neighbor 190.17.20.16 ipv6-nexthop 2001::1 5 Enable the BGP peer status using the ip bgp neighbor admin-state command.
Configuring BGP Configuring BGP for IPv6 4 Enable IPv6 unicast capability to the IPv6 BGP peer using the ip bgp neighbor activate-ipv6 command, as shown: -> ipv6 bgp neighbor fe80::2d0:95ff:fee2:6ed0 activate-ipv6 5 Enable the BGP peer status using the ipv6 bgp neighbor admin-state command.
Configuring BGP for IPv6 Configuring BGP -> ipv6 bgp neighbor 2001::1 2 Assign an AS number to the IPv6 peer using the ipv6 bgp neighbor remote-as command. For example, to assign the peer created in Step 1 to AS number 10, you would enter: -> ipv6 bgp neighbor 2001::1 remote-as 10 3 Set the IPv4 next hop address for IPv4 prefixes advertised to the IPv6 BGP peer using the ipv6 bgp neighbor ipv4-nexthop command, as shown: -> ipv6 bgp neighbor 2001::1 ipv4-nexthop 190.17.20.
Configuring BGP Configuring BGP for IPv6 Optional IPv6 BGP Peer Parameters Peer Parameter Command Enables or disables BGP peer. ipv6 bgp neighbor admin-state Assigns an AS number to the BGP peer. ipv6 bgp neighbor remote-as Configures the time interval for updates between external BGP peers. ipv6 bgp neighbor advertisement-interval Enables or disables BGP peer automatic restart.
Configuring BGP for IPv6 Peer Parameter Configuring BGP Command Configures the local transport endpoint ipv6 bgp neighbor update-source address for this neighbor's peering session. Configures the local IPv6 interface ipv6 bgp neighbor update-source-address from which the peer will be connected if the peer is configured with its linklocal address. Configures the IPv4 next hop addresses ipv6 bgp neighbor ipv4-nexthop for IPv4 prefixes advertised between BGP peers.
Configuring BGP Configuring BGP for IPv6 Use the no form of the ipv6 bgp neighbor update-source-address command to prevent the peer with an IPv6 address of 2001::1 from contacting the speaker via the IPv6 address 2004::2, as shown: -> no ipv6 bgp neighbor 2001::1 update-source-address Note. If a BGP peer is configured with its link-local address, use the ‘update-source’ parameter to specify the name of the IPv6 interface from which this peer is reachable.
Configuring BGP for IPv6 Configuring BGP Configuring a BGP Peer with the IPv6 Loopback0 Interface An IPv6 Loopback0 virtual interface is used to identify a consistent IPv6 address for network management purposes. The IPv6 Loopback0 interface is not bound to any VLAN or other physical interface, so it will always remain operationally active. This differs from other IPv6 interfaces, If there are no active ports in the VLAN, all IPv6 interfaces associated with that VLAN are not active.
Configuring BGP Configuring BGP for IPv6 Configuring IPv6 BGP Networks A local IPv6 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 and must also originate from the local BGP speaker. Networks have certain parameters that can be configured, such as local-preference, community, metric, etc. Note that the network specified must be known to the router, whether it is connected, static, or dynamically learned.
Configuring BGP for IPv6 Configuring BGP -> ipv6 bgp network 2001::/64 local-preference 600 The local preference for routes generated by the network is now changed from the default value to 600. Community Communities are a way of grouping BGP destination addresses that share some common property. Adding the local network to a specific community indicates that the network shares a common set of properties with the rest of the community.
Configuring BGP Network Network Network Network Network Network Configuring BGP for IPv6 address admin state oper state metric local preference community string = = = = = = 2525:500:600::/64, enabled, active, 0, 0, OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 4-73
Configuring IPv6 Redistribution Configuring BGP 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.
Configuring BGP Configuring IPv6 Redistribution Use the show ipv6 redist command to verify the redistribution configuration: -> show ipv6 redist Source Destination Protocol Protocol Status Route Map ------------+------------+---------+-------------------localIPv6 BGP 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 BGP Application Example Configuring BGP IPv6 BGP Application Example The following simple network using EBGP and IBGP will demonstrate some of the basic BGP setup commands discussed previously: AS 200 BGP Speaker 5 30.0.0.1/24 BGP Speaker 4 20.0.0.1/24 2001:ABCD:B02:1::1/64 AS 300 EBGP EBGP IBGP BGP Speaker 1 10.0.0.1/24 20.0.0.2/24 2001:DB8:C17:1::1/64 2001:DB8:C18:1::1/64 2001:ABCD:B02:1::2/64 BGP Speaker 3 2001:DB8:C18:1::2/64 2001:DB8:C19:1::2/64 BGP Speaker 2 10.0.0.2/24 30.0.0.
Configuring BGP -> -> -> -> ipv6 ipv6 ipv6 ipv6 IPv6 BGP Application Example bgp bgp bgp bgp neighbor neighbor neighbor neighbor 2001:DB8:C18:1::2 2001:DB8:C18:1::2 remote-as 100 2001:DB8:C18:1::2 activate-ipv6 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): -> ip interface Link_To_AS200 vlan 4 -> ip interface Link_To_AS200 address 20.0.0.
IPv6 BGP Application Example Configuring BGP 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 -> ip bgp neighbor 30.0.0.
Configuring BGP IPv6 BGP Application Example 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 -> ipv6 address 2001:ABCD:B02:1::1/64 Link_to_AS100 -> -> -> -> -> ip ip ip ip ip bgp bgp bgp bgp bgp neighbor neighbor neighbor neighbor neighbor 20.0.0.2 20.0.0.2 20.0.0.2 20.0.0.2 20.0.0.
Displaying IPv6 BGP Settings and Statistics Configuring BGP 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. show ipv6 bgp path Displays the known IPv6 BGP paths for all the routes or a specific route. show ipv6 bgp routes Displays the known IPv6 BGP routes.
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 policies based on the path (AS path list), community attributes (community lists), specific destinations (prefix lists and prefix6 lists), and so on. You could also configure route maps to include all of the above in a single policy.
Routing Policies Configuring BGP 2 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. For example: -> ip bgp policy aspath-list aspathfilter “^100 200$” action permit The AS path policy aspathfilter now permits routes that match the regular expression ^100 200$.
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: 1 Name the policy and specify the IP network address and mask using the ip bgp policy prefix-list command, as shown: -> ip bgp policy prefix-list prefixfilter 12.0.0.0 255.0.0.
Routing Policies Configuring BGP 3 Optionally, you can set a minimum length of the prefix to be matched in the policy using the ip bgp policy prefix6-list ge command. For example: -> ip bgp policy prefix6-list uniqLocal FC00::/48 ge 48 Prefix policy uniqLocal now denies routes after FC00::/48 4 Optionally, you can set a maximum length of the prefix to be matched in the policy using the ip bgp policy prefix6-list le command.
Configuring BGP Route Map Options Routing Policies Command Configures the local preference value for ip bgp policy route-map lpref the route map. Configures the action to be taken when setting local preference attribute for a local matching route. ip bgp policy route-map lpref-mode Configures a matching community primitive for the route map. ip bgp policy route-map match-community Configures a matching mask primitive in ip bgp policy route-map match-mask the route map.
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 IPv4 and IPv6 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 a BGP peer.
Configuring BGP Routing Policies BGP Attribute Command Assigns an inbound or outbound policy map to an IPv6 BGP peer. ipv6 bgp neighbor route-map Invokes an inbound or outbound policy reconfiguration for an IPv6 BGP peer. ipv6 bgp neighbor clear soft Policies that should affect routes learned from a peer use the in- prefix, and policies that affect routes being advertised to a peer use the out- prefix.
Routing Policies Configuring BGP The route map policy prefixfilter must be previously created using the ip bgp policy prefix-list command. To assign the same policy to route advertisements to the peer, enter the peer IP address with the ip bgp neighbor out-prefixlist command, as shown: -> ip bgp neighbor 172.22.2.
Configuring BGP Routing Policies Assigning Inbound and Outbound Policies to an IPv6 Peer The following sections describes assigning various policies to an IPv6 BGP peer. Assigning In and Outbound AS Path Policy AS path policies filter routes based on matches made to a set AS list in the route. An AS list is a list of all the ASs the route crosses until its destination.
Routing Policies Configuring BGP Assigning In and Outbound Prefix6 List Policy Prefix6 list policies filter IPv6 routes based on a specific IPv6 network address, or a range of IPv6 network addresses.
Configuring BGP Routing Policies Displaying Policies The following commands are used to display the various policies configured on a BGP router: show ip bgp policy aspath-list Displays information on policies based on AS path criteria. show ip bgp policy community- Displays information on policies based on community list criteria. list show ip bgp policy prefix-list Displays information on policies based on route prefix criteria.
Routing Policies page 4-92 Configuring BGP OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
5 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).
Multicast Boundary Specifications Configuring Multicast Address Boundaries Multicast Boundary Specifications Platforms Supported OmniSwitch 10K, 6900 RFCs Supported 2365—Administratively Scoped IP Multicast 5132 - IP Multicast MIB Valid Scoped Address Range 239.0.0.0 to 239.255.255.255 License Requirements Advanced License required on OmniSwitch 6900 only. Note.
Configuring Multicast Address Boundaries Quick Steps for Configuring Multicast Address Boundaries Quick Steps for Configuring Multicast Address Boundaries Using Existing IP Interfaces 1 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.
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. For more information, refer to the section below.
Configuring Multicast Address Boundaries Multicast Address Boundaries Overview Multicast Address Boundaries Without multicast address boundaries, multicast traffic conflicts can occur between domains. For example, a multicast packet addressed to 239.140.120.10 from a device in one domain could “leak” into another domain. If the other domain contains a device attempting to send a separate multicast packet with the same address, a conflict may occur.
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 multicast addresses can be reused throughout the network. This allows network administrators to conserve limited multicast address space. The figure below shows multicast addresses 239.140.120.
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.
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. For more information about the displays that result from these commands, see the OmniSwitch AOS Release 7 CLI Reference Guide.
Configuring Multicast Address Boundaries Application Example for Configuring Multicast Address Boundaries 4 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. To assign the boundary, use the ip mroute-boundary command.
Application Example for Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries 7 Create an IP interface on VLAN 3. For example: -> ip interface vlan-3 address 178.20.1.1 vlan 3 8 Assign a boundary on the switch’s router interface. For this example, the interface is given the bound- ary 239.188.0.0/16. This boundary will keep all traffic addressed to multicast addresses 239.188.0.0 through 239.188.255.255 from being forwarded on the interface: -> ip mroute-boundary vlan-3 239.
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 178.10.1.1 239.x.x.x Multicast Traffic Core Switch Training Human Resources 239.188.x.x Multicast Traffic VLAN 3 Router Port 178.20.1.1 VLAN 4 Router Port 178.30.1.1 239.188.0.0/16 239.188.x.x Multicast Traffic 239.188.0.0/16 239.0.0.
Application Example for Configuring Multicast Address Boundaries page 5-12 Configuring Multicast Address Boundaries OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
6 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).
DVMRP Specifications Configuring DVMRP DVMRP Specifications Platforms Supported OmniSwitch 10K, 6900 RFCs supported 1075 - Distance Vector Multicast Routing Protocol, Version1 4087—IP Tunnel MIB 2715—Interoperability Rules for Multicast Routing Protocols draft-ietf-idmr-dvmrp-v3-09.txt - Distance Vector Multicast Routing Protocol, Version 3 DVMRP version supported DVMRPv3.
Configuring DVMRP DVMRP Defaults Parameter Description Command Default Value/Comments Route expiration timeout ip dvmrp route-timeout 140 seconds Interface distance metric ip dvmrp interface metric 1 Subordinate neighbor status ip dvmrp subord-default true OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 6-3
Quick Steps for Configuring DVMRP 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. However, if you wish to manually enable IPMS on the switch, use the ip multicast admin-state command.
Configuring DVMRP DVMRP Overview 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.
DVMRP Overview Configuring DVMRP 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). Each Probe message includes a Neighbor List of DVMRP routers known to the transmitting router.
Configuring DVMRP DVMRP Overview 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. If the packet arrived on that upstream interface, then it is a candidate for forwarding to one or more downstream interfaces.
DVMRP Overview Configuring DVMRP 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 downstream routers then have the option to send prunes (and subsequent grafts) for this (S, G) pair as requirements change.
Configuring DVMRP DVMRP Overview 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 encapsulated in unicast IP packets and addressed directly to the routers that do not support native multicast routing.
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. However, if you wish to manually enable IPMS on the switch, use the ip multicast admin-state command.
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). An interface can be any IP router port that has been assigned to an existing VLAN.
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 Oper-Status --------------+------+--------+-------------+-------------vlan-2 2 1 Enabled Enabled Current assigned metric is shown as 1.
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). If the command syntax ip dvmrp admin-state enable is saved to the boot.
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.
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.
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. When the branch router sends a prune upstream for this group, a prune-lifetime value of 4500 seconds will be inserted into the prune packet.
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.
Verifying the DVMRP Configuration Configuring DVMRP 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. show ip dvmrp interface Displays the DVMRP interface table, which lists all multicast-capable interfaces.
7 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.
In This Chapter Configuring PIM • Mapping an IPv6 multicast group to a PIM mode—see page 7-37. • Configuring Candidate Rendezvous Points (C-RPs) in IPv6 PIM—see page 7-38. • Configuring Candidate Bootstrap Routers (C-BSRs) in IPv6 PIM—see page 7-39. • Configuring RP-switchover for IPv6 PIM—see page 7-42. • Verifying IPv6 PIM configuration—see page 7-43. For detailed information about PIM commands, see the “PIM Commands” chapter in the OmniSwitch AOS Release 7 CLI Reference Guide.
Configuring PIM PIM Specifications PIM Specifications Platforms supported OmniSwitch 10K, 6900 RFCs supported 2365—Administratively Scoped IP Multicast 4601—Protocol Independent Multicast-Sparse Mode (PIM-SM) Protocol Specification 4007 - IPv6 Scoped IP Multicast 5060 - Protocol Independent Multicast MIB 5132 —IP Multicast MIB 3569—An Overview of Source-Specific Multicast (SSM) 3973—Protocol Independent Multicast-Dense Mode (PIM-DM) 5059—Bootstrap Router (BSR) Mechanism for PIM 5240—Protocol Independen
PIM Defaults Configuring PIM PIM Defaults The following table lists the defaults for the 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 ip pim ssm group Disabled Priority ip pim dense group Disabled C-BSR mask length ip pim cbsr 30 bits Priority ip pim cbsr 64 Static RP configuration ip pim
Configuring PIM Parameter Description PIM Defaults Command Default Value/Comments Neighbor loss notification interval ip pim neighbor-loss-notificationperiod 0 seconds Invalid register notification interval ip pim invalid-register-notificationperiod 65535 seconds RP mapping notification interval ip pim rp-mapping-notificationperiod 65535 seconds Invalid joinprune notification interval ip pim invalid-joinprune-notification- 65535 seconds period Interface election notification interval ip pim
PIM Defaults Configuring PIM Parameter Description Command Default Value/Comments Graft retry interval ipv6 pim interface graft-retryinterval 3 seconds Stub ipv6 pim interface stub Disabled page 7-6 OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
Configuring PIM Quick Steps for Configuring PIM-DM 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. However, if you wish to manually enable IPMS on the switch, use the ip multicast admin-state command.
Quick Steps for Configuring PIM-DM Configuring PIM The display for dense mode is similar to the one shown here: -> show ip pim dense Status Source Lifetime State Refresh Interval State Refresh Limit Interval State Refresh TTL = enabled, = 210, = 60, = 0, = 16 (additional table output not shown) For more information about these displays, see the “PIM Commands” chapter in the OmniSwitch AOS Release 7 CLI Reference Guide.
Configuring PIM PIM Overview 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.
PIM Overview Configuring PIM 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. A C-RP periodically sends out messages, known as C-RP advertisements.
Configuring PIM PIM Overview 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. Depending on the network configuration, multiple routers may exist between the receiver’s DR and the RP router. In this case, the (*, G) Join message travels hop-by-hop toward the RP.
PIM Overview Configuring PIM 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.
Configuring PIM PIM Overview 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. • Register encapsulation may require that data travel unnecessarily over long distances.
PIM Overview Configuring PIM 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 Source-Specific Join Native Traffic DR ! RP DR Source-Specific Join Receiver Note. To configure the RP threshold value, use the ip pim rp-threshold command.
Configuring PIM PIM Overview 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. The RP drops the register-encapsulated packets and forwards only the native packets. Legend Register-Encapsulated Traffic Sender Native Traffic DR DR RP The RP receives both native and encapsulated data.
PIM Overview Configuring PIM 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). Instead, the switchover is initiated automatically, as long as the SPT status is enabled on the switch. Important. SPT status must be enabled for SPT switchover to occur.
Configuring PIM PIM Overview 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. This router drops the packets arriving via the RP tree and forwards only those packets arriving via the SPT.
PIM Overview Configuring PIM The Receiver is now receiving multicast traffic along the Shortest Path Tree between the Receiver and the Source. Sender DR RP DR 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; an RP tree model is not used.
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 • Enabling PIM globally on the switch Note. These steps are common for enabling PIM in the IPv4 as well as IPv6 environments. For information on completing these steps, refer to the sections below.
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. Checking the Current IPMS Status To view the current status of IPMS on the switch, use the show ip multicast command.
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.
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 or show ip pim dense command.
Configuring PIM Configuring PIM This command entry maps the multicast group 225.0.0.0/24 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 configuration and provides fine control over which configuration is overridden by this static configuration. Values may range from 0 to 128. If the priority option has been defined, a value of 65535 can be used to unset the priority.
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.
Configuring PIM Configuring PIM The group address is listed as 225.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. Important. PIM must be globally disabled on the switch before changing the maximum number of RPs.
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.
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 ---------+---------------------------+-------------+-----+----------BSR 225.0.0.0/24 172.21.63.11 asm 192 BSR 225.0.0.0/24 214.0.0.7 asm 192 Static 232.0.0.
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 ---------------------------+-------------+-----+--------+----------+-------225.0.0.0/24 172.21.63.
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 Keepalive Period Max RPs Probe Time Register Suppress Timeout RP Switchover SPT Status = = = = = = = enabled, 210, 32, 5, 60, enabled, enabled, You can also use the show ip pim dense, show ipv6 pim sparse, and show ipv6 pim dense commands to view the configured keepalive period.
Configuring PIM Configuring PIM Verifying the Notification Period To view the configured notification period, use the show ip pim notifications command.
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. show ip pim ssm group Displays the static configuration of multicast group mappings for PIMSource-Specific Multicast (SSM) mode.
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. These include automatic configuration of hosts, extensive multicasting capabilities, and built-in security using authentication headers and encryption.
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. However, if you wish to manually enable IPMS on the switch, use the ip multicast admin-state command.
Quick Steps for Configuring IPv6 PIM-DM -> show ipv6 pim sparse Status Keepalive Period Max RPs Probe Time Register Suppress Timeout RP Switchover SPT Status Configuring PIM = = = = = = = enabled, 210, 32, 5, 60, enabled, enabled, The display for dense mode is similar to the one shown here: -> show IPv6 pim dense Status Source Lifetime State Refresh Interval State Refresh Limit Interval State Refresh TTL = = = = = enabled, 210, 60, 0, 16 (additional table output not shown) For more information about
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 • IPv6 PIM Bootstrap and RP Discovery • Configuring a C-RP for IPv6 PIM • Configuring Candidate Bootstrap Routers (C-BSRs) for IPv6 PIM • Configuring static RP groups for IPv6 PIM • Configuring
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.
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. Mapping an IPv6 Multicast Group to PIM-DM To statically map an IPv6 multicast group(s) to PIM-Dense Mode (DM), you can use the ipv6 pim dense group command.
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.
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 DR. 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. Verifying the Changes Check the maximum number of RPs using the show ipv6 pim sparse command.
Configuring IPv6 PIM Configuring PIM Elected BSR Timer = False, = 00h:00m:00s For more information about these displays, see the “PIM Commands” chapter in the OmniSwitch AOS Release 7 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” on reachable Candidate Rendezvous Points (C-RPs). BSRs are elected from a set of Candidate Bootstrap Routers (C-BSRs).
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. As specifying the priority value obsoletes the override option, you can use either the priority or override parameter only.
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-encapsulated 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. -> ipv6 pim rp-switchover disable The above command disables the RP from switching to native forwarding.
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 PIMSparse Mode. show ipv6 pim dense Displays the status of the various global parameters for the IPv6 PIMDense Mode. show ipv6 pim ssm group Displays the static configuration of IPv6 multicast group mappings for PIM-Source-Specific Multicast (SSM).
Verifying IPv6 PIM Configuration page 7-44 Configuring PIM OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015
8 Configuring a Multicast Border Router The OmniSwitch support of interoperability between Protocol-Independent Multicast (PIM) and Distance Vector Multicast Routing Protocol (DVMRP) is based on rules defined in RFC 2715 and multicast border router (MBR) functionality defined in the PIM-SM specification (RFC 4601). The supported MBR functionality allows receivers and sources within PIM and DVMRP domains to communicate and satisfy RFC 2715 rules.
OmniSwitch MBR Specifications Configuring a Multicast Border Router OmniSwitch MBR Specifications Platforms Supported OmniSwitch 10K, 6900 RFCs Supported 4601—Protocol Independent Multicast-Sparse Mode (PIM-SM) Protocol Specification 3973—Protocol Independent Multicast-Dense Mode (PIM-DM) 2715—Interoperability Rules for Multicast Routing Protocols draft-ietf-idmr-dvmrp-v3-09.
Configuring a Multicast Border Router Multicast Border Router Overview Multicast Border Router Overview The multicast border router (MBR) functionality implemented for the OmniSwitch supports interoperability between a PIM and DVMRP domain. Interoperability between PIM and other protocols or between multiple PIM domains is not supported. In addition, PIM support refers only to PIM-DM and PIM-SM (PIM-SSM is not supported).
Configuring a Multicast Border Router Configuring a Multicast Border Router PIM Overview This section provides a brief overview of the OmniSwitch PIM implementation. The use of PIM throughout this chapter refers to PIM-DM and PIM-SM. For more detailed information about using PIM-SM and PIM-DM, see Chapter 7, “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.
Configuring a Multicast Border Router Configuring a Multicast Border Router Enabling/Disabling MBR By default, MBR is disabled for the switch. To enable MBR functionality, use the ip mroute mbr command. For example: -> ip mroute mbr admin-state enable To disable MBR functionality for the switch, use the ip mroute mbr command with the disable option. For example: .
Configuring a Multicast Border Router MBR All Sources Status MBR Operational Status Configuring a Multicast Border Router = disabled, = enabled Configuring DVMRP Default Route Advertisement Advertising a default route on a DVMRP interface on the MBR provides a method for ensuring that sources inside the PIM domain can reach all routers inside the DVMRP domain. To enable default route advertisement for a specific DVMRP interface, use the ip dvmrp interface mbr-default-information command.
Configuring a Multicast Border Router Configuring a Multicast Border Router Example 2: DVMRP Default Route In this example, the switch is configured to act as an MBR but also enables DVMRP to advertise the default route on "vlan-6", but not on "vlan-4". -> -> -> -> -> -> -> -> -> -> -> ip ip ip ip ip ip ip ip ip ip ip load pim pim interface "vlan-2" pim interface "vlan-3" pim dense group 225.0.0.
Verifying the MBR Configuration Configuring a Multicast Border Router Verifying the MBR Configuration A summary of the show commands used for verifying the OmniSwitch MBR configuration is given here: show ip mroute mbr Displays the MBR administrative status and the MBR protocol registration status for PIM and DVMRP. show ip pim sparse show ip pim dense Displays the global parameter configuration for PIM-SM or PIM-DM, including the PIM operational status for MBR and the PIM route notification status.
A Software License and Copyright Statements This appendix contains Alcatel-Lucent and third-party software vendor license and copyright statements. Alcatel-Lucent License Agreement ALCATEL-LUCENT SOFTWARE LICENSE AGREEMENT IMPORTANT. Please read the terms and conditions of this license agreement carefully before opening this package. By opening this package, you accept and agree to the terms of this license agreement.
Alcatel-Lucent License Agreement Software License and Copyright Statements 3. Confidentiality. Alcatel-Lucent considers the Licensed Files to contain valuable trade secrets of Alcatel-Lucent, the unauthorized disclosure of which could cause irreparable harm to Alcatel-Lucent. Except as expressly set forth herein, Licensee agrees to use reasonable efforts not to disclose the Licensed Files to any third party and not to use the Licensed Files other than for the purpose authorized by this License Agreement.
Software License and Copyright Statements Alcatel-Lucent License Agreement Alcatel-Lucent, Licensee agrees to return to Alcatel-Lucent or destroy the Licensed Materials and all copies and portions thereof. 10. Governing Law. This License Agreement shall be construed and governed in accordance with the laws of the State of California. 11. Severability.
Third Party Licenses and Notices Software License and Copyright Statements Third Party Licenses and Notices Legal Notices applicable to any software distributed alone or in connection with the product to which this document pertains, are contained in files within the software itself located at: /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.
Index A aggregate routes BGP 4-33 application examples BGP 4-4, 4-54 BGP IPv6 4-59 DVMRP 6-4 IS-IS 3-5, 3-31 multicast address boundaries 5-3, 5-8 OSPF 1-4, 1-32, 2-4, 2-25 area border routers 1-8, 1-9, 2-9, 2-10 areas 1-8, 2-9 assigning interfaces 1-19 backbones 1-8 creating 1-16, 2-15 deleting 1-17, 2-16 NSSAs 1-11 ranges 1-18 route metrics 1-18, 2-16 specifying type 1-16, 2-15 status 1-17, 2-15 stub 1-10, 2-11 summarization 1-17 Totally Stubby 1-11 AS 4-6 AS boundary routers 1-9, 2-10 AS path policies as
Index defaults 6-2 dependent downstream routers 6-7 enabling 6-10 graft acknowledgment messages 6-8 graft messages 6-8 grafting 6-8, 6-17 hop count 6-7 IGMP 6-5 interface metric 6-7 loading 6-10 metrics 6-7 multicast source location 6-7 neighbor communications 6-13 neighbor discovery 6-6 overview 6-5 poison reverse 6-7 probe messages 6-6 prune messages 6-8 pruning 6-8, 6-15 reverse path forwarding check 6-7 reverse path multicasting 6-5 route report messages 6-6, 6-7, 6-14 routes 6-14 specifications 6-2 tu
Index ip isis interface auth-type command 3-20 ip isis interface command 3-16 ip isis interface csnp-interval command 3-23 ip isis interface lsp-pacing-interval command 3-23 ip isis interface retransmit-interval command 3-23 ip isis overload command 3-30 ip isis overload-on-boot command 3-30 ip isis strict-adjacency-check command 3-30 ip load bgp command 4-18 ip load dvmrp command 6-10 ip load isis command 3-15 ip load ospf command 1-15, 2-14 ip mroute-boundary command 5-3, 5-7, 8-2, 8-5 ip multicast statu
Index backbones 1-8 classification of routers 1-9, 2-10 configuring 1-14, 2-13 configuring routers 1-28, 2-24 defaults 1-3, 2-3 ECMP routing 1-12, 2-12 enabling 1-15 filters 1-22 graceful restart on switches 1-13 interfaces 1-19, 2-16 interior gateway protocols 1-7, 2-8 link-state protocol 1-7, 2-8 loading software 1-15, 2-14 MD5 encryption 1-20 modifying interfaces 1-21, 2-17 NBMA routing 1-12 overview 1-7, 2-8 preparing the network 1-15, 2-14 redistribution policies 1-22 routers 1-9, 2-10 simple authenti
Index show ip bgp neighbors statistics command 4-30, 4-69 show ip bgp neighbors timer command 4-57 show ip bgp network command 4-36 show ip bgp path command 4-57 show ip bgp policy aspath-list command 4-57 show ip bgp policy community-list command 4-57 show ip bgp policy prefix-list command 4-57 show ip bgp policy route-map command 4-57 show ip bgp routes command 4-57 show ip bgp statistics command 4-57 show ip dvmrp command 6-12 show ip dvmrp interface command 6-12 show ip dvrmp prune command 6-16 show ip
Index Index-6 OmniSwitch AOS 7 Advanced Routing Configuration Guide March 2015
