Part No. 060216-10, Rev. E December 2007 OmniSwitch 6800 Series OmniSwitch 6850 Series OmniSwitch 9000 Series Advanced Routing Configuration Guide www.alcatel-lucent.
This user guide documents release 6.3.1 of the OmniSwitch 6800 Series, OmniSwitch 6850 Series, and OmniSwitch 9000 Series. The functionality described in this guide is subject to change without notice. Copyright © 2007 by Alcatel-Lucent. All rights reserved. This document may not be reproduced in whole or in part without the express written permission of Alcatel-Lucent. Alcatel-Lucent® and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent.
Contents About This Guide .......................................................................................................... xi Supported Platforms .......................................................................................................... xi Who Should Read this Manual? ....................................................................................... xii When Should I Read this Manual? ...................................................................................
Contents Using Route Maps ...........................................................................................1-24 Configuring Route Map Redistribution ...........................................................1-28 Route Map Redistribution Example ................................................................1-29 Configuring Router Capabilities ............................................................................1-30 Configuring Static Neighbors ............................................
Contents Chapter 3 Configuring IS-IS ........................................................................................................ 3-1 In This Chapter ................................................................................................................3-1 IS-IS Specifications .........................................................................................................3-2 IS-IS Defaults Table ................................................................................
Contents Route Dampening ...................................................................................................4-17 CIDR Route Notation .............................................................................................4-17 BGP Configuration Overview .......................................................................................4-18 Starting BGP .................................................................................................................
Contents Application Example .....................................................................................................4-60 AS 100 .............................................................................................................4-60 AS 200 .............................................................................................................4-61 AS 300 .............................................................................................................
Contents Chapter 6 Configuring DVMRP ................................................................................................... 6-1 In This Chapter ................................................................................................................6-1 DVMRP Specifications ...................................................................................................6-2 DVMRP Defaults .................................................................................................
Contents Enabling PIM on the Switch ..................................................................................7-18 Verifying the Software ....................................................................................7-18 Loading PIM into Memory ..............................................................................7-19 Enabling IPMS ................................................................................................7-19 Enabling PIM on a Specific Interface .................
Contents Configuring RP-Switchover for IPv6 PIM .............................................................7-41 Verifying RP-Switchover ................................................................................7-42 IPv6 PIM-SSM Support ................................................................................................7-42 Source-Specific Multicast Addresses .....................................................................7-42 PIM-SSM Specifications .................................
About This Guide This OmniSwitch 6800/6850/9000 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 This information in this guide applies to the following products: • OmniSwitch 9600 (with Jadvrout.img file installed) • OmniSwitch 9700 (with Jadvrout.
Who Should Read this Manual? The audience for this user guide is network administrators and IT support personnel who need to configure, maintain, and monitor switches and routers in a live network. However, anyone wishing to gain knowledge on how advanced routing software features are implemented in the OmniSwitch 6800 Series, OmniSwitch 6850 Series, and OmniSwitch 9000 Series switches will benefit from the material in this configuration guide.
How is the Information Organized? Chapters in this guide are broken down by software feature. The titles of each chapter include protocol or feature names (e.g., OSPF, PIM-SM) with which most network professionals will be familiar. Each software feature chapter includes sections that will satisfy the information requirements of casual readers, rushed readers, serious detail-oriented readers, advanced users, and beginning users. Quick Information.
Stage 2: Gaining Familiarity with Basic Switch Functions Pertinent Documentation: Hardware Users Guide Switch Management Guide Once you have your switch up and running, you will want to begin investigating basic aspects of its hardware and software. Information about switch hardware is provided in the Hardware Users Guide.
Related Documentation The following are the titles and descriptions of all the related OmniSwitch 6800/6850/9000 user manuals: • OmniSwitch 6800 Series Getting Started Guide Describes the hardware and software procedures for getting an OmniSwitch 6800 Series switch up and running. Also provides information on fundamental aspects of OmniSwitch software and stacking architecture.
• OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide Includes network configuration procedures and descriptive information on all the software features and protocols included in the advanced routing software package. Chapters cover multicast routing (DVMRP and PIM-SM), and OSPF. • OmniSwitch Transceivers Guide Includes information on Small Form Factor Pluggable (SFPs) and 10 Gbps Small Form Factor Pluggables (XFPs) transceivers.
User Manual CD All user guides are included on the User Manual CD that accompanied your switch. This CD also includes user guides for other Alcatel-Lucent data enterprise products. In addition, it contains a stand-alone version of the on-line help system that is embedded in the OmniVista network management application. Besides the OmniVista documentation, all documentation on the User Manual CD is in PDF format and requires the Adobe Acrobat Reader program for viewing.
page -xviii OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide December 2007
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 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 (per router) 32 Maximum number of Interfaces (per router) 3200 Maximum number of Interfaces (per area) 100 Maximum number of Link State Database entries (per router) 96K Maximum number of adjace
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 status disabled Enables an interface. ip ospf interface status disabled Enables OSPF redistribution. ip ospf redist status 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 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 command.
Configuring OSPF OSPF Quick Steps 7 Create an OSPF interface for each VLAN created in Step 1, using the ip ospf interface command. The OSPF interface should use the same interface name used for the VLAN router IP created in Step 2. For example: -> ip ospf interface vlan-5 Note. The interface name cannot have spaces. 8 Assign the OSPF interface to the area and the backbone using the ip ospf interface area command. For example: -> ip ospf interface vlan-5 area 0.0.0.
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 Stacks with Redundant Switches OmniSwitch 6800 and OmniSwitch 6850 stacks with two or more switches can support redundancy where if the primary switch fails or goes offline for any reason, the secondary switch is instantly notified. The secondary switch automatically assumes the primary role. This switch between the primary and secondary switches is known as takeover. When a takeover occurs, which can be planned (e.g.
OSPF Overview Configuring OSPF Graceful Restart on Switches with Redundant CMMs OmniSwitch 9000 chassis 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-19.) 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 ip ospf ospf ospf ospf ospf ospf ospf ospf ospf Configuring OSPF area 1.1.1.1 summary disable area 1.1.1.1 default-metric 0 interface vlan-5 interface vlan-5 area 1.1.1.1 interface vlan-5 status enable interface vlan-6 interface vlan-6 area 0.0.0.0 interface vlan-6 status enable status 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 status command with the interface name, as shown: -> ip ospf interface vlan-213 status 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 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. Creating a Virtual Link To create a virtual link, commands must be submitted to the routers at both ends of the link. The router being configured should point to the other end of the link, and both routers must have a common area.
Configuring OSPF Configuring OSPF 1 Create a route map, as described in “Using Route Maps” on page 1-24. 2 Configure redistribution to apply a route map, as described in “Configuring Route Map Redistribution” on page 1-28. Note. An OSPF router automatically becomes an Autonomous System Border Router (ASBR) when redistribution is configured on the router. Using Route Maps A route map specifies the criteria that are used to control redistribution of routes between protocols.
Configuring OSPF Configuring OSPF To optionally filter routes before redistribution, use the ip route-map command with a match parameter to configure match criteria for incoming routes. For example, -> ip route-map ospf-to-bgp sequence-number 10 match tag 8 The above command configures a match statement for the ospf-to-bgp route map to filter routes based on their tag value. When this route map is applied, only OSPF routes with a tag value of eight are redistributed into the BGP network.
Configuring OSPF Configuring OSPF 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 Sequence 10 and sequence 20 are both linked to route map rm_1 and are processed in ascending order according to their sequence number value. Note that there is an implied logical OR between sequences. As a result, if there is no match for the tag value in sequence 10, then the match interface statement in sequence 20 is processed. However, if a route matches the tag 8 value, then sequence 20 is not used. The set statement for whichever sequence was matched is applied.
Configuring OSPF Configuring OSPF Configuring Route Map Redistribution The ip redist command is used to configure the redistribution of routes from a source protocol into the destination protocol. This command is used on the router that will perform the redistribution. Note. An OSPF router automatically becomes an Autonomous System Border Router (ASBR) when redistribution is configured on the router. A source protocol is a protocol from which the routes are learned.
Configuring OSPF Configuring OSPF Route Map Redistribution Example The following example configures the redistribution of OSPF routes into a BGP network using a route map (ospf-to-bgp) to filter specific routes: -> ip route-map ospf-to-bgp sequence-number 10 action deny -> ip route-map ospf-to-bgp sequence-number 10 match tag 5 -> ip route-map ospf-to-bgp sequence-number 10 match route-type external type2 -> ip route-map ospf-to-bgp sequence-number 20 action permit -> ip route-map ospf-to-bgp sequence-num
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 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 Switches in a Stack for Graceful Restart By default, OSPF graceful restart is disabled. To enable OSPF graceful restart support on OmniSwitch 6800 and OmniSwitch 6850 switches, use the ip ospf restart-support command by entering ip ospf restart-support followed by planned-unplanned.
Configuring OSPF Configuring OSPF Configuring Redundant CMMs for Graceful Restart By default, OSPF graceful restart is disabled. To enable OSPF graceful restart on OmniSwitch 9000 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-20 -> ip ospf interface vlan-20 area 0.0.0.2 -> ip ospf interface vlan-20 status 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.0.0.
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-40 OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide Configuring OSPF December 2007
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 RFCs Supported RFC 1826—IP Authentication Header RFC 1827—IP Encapsulating Security Payload RFC 2553—Basic Socket Interface Extensions for IPv6 RFC 2373—IPv6 Addressing Architecture RFC 2374—An IPv6 Aggregatable Global Unicast Address Format RFC 2460—IPv6 base specification RFC 2470—OSPF for IPv6 draft-ietf-ospf-ospfv3-update-11—OSPF for IPv6 draft-ietf-ospf-ospfv3-mib-09—MIB for OSPFv3 Maximum number of Areas (per router) 5 Maximum number
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 status tive status. enabled Configures the administrative status ipv6 ospf interface status for an OSPF interface. enabled Enables 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 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 6800/6850/9000 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 port default 2/3-5 -> 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 IPv6 router interface vlan-12 was associated with OSPFv3 interface vlan-12, enabled, and assigned to the backbone. IPv6 router interface vlan-23 was associated with OSPFv3 interface vlan-23, enabled, and assigned to the backbone. IPv6 router interface vlan-20, which connects to end stations and attached network devices, was associated with OSPFv3 interface vlan-20, enabled, and assigned to Area 0.0.0.2. Router 3 -> ipv6 ospf interface vlan-23 area 0.0.0.
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 level (per interface) ip isis interface level-capability Level-1/2 IS-IS authentication check ip isis auth-check enabled LSP time interval (per interface) ip isis interface lsp-pacing-inter- 100 milliseconds val IS-IS passive interface ip isis interface passive Retransmission time of LSP on a point-to-point interface ip isis interface retransmit-inter- 5 seconds val Hello authentication for the
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 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.0 vlan 5 3 Assign a port to the VLAN using the vlan command.
IS-IS Quick Steps Configuring IS-IS L1 LSDB Overload : Disabled L2 LSDB Overload : Disabled L1 LSPs : 177 L2 LSPs : 177 Last SPF : FRI OCT 26 05:04:09 2007 SPF Wait : Max :10000 ms, Initial :1000 ms, Second :1000 ms Hello-Auth Check : Enabled Csnp-Auth Check : Enabled Psnp-Auth Check : Enabled L1 Hello-Auth Check : Enabled L1 Csnp-Auth Check : Enabled L1 Psnp-Auth Check : Enabled L2 Hello-Auth Check : Enabled L2 Csnp-Auth Check : Enabled L2 Psnp-Auth Check : Enabled Area Address : 49.
Configuring IS-IS IS-IS Quick Steps Auth Type : None Metric : 10 Hello Timer : 9 Hello Mult : 3 Priority : 64 Passive : No ----------------------------------------------------------------------------Interface : intf2 Level Capability : L2 Oper State : UP Admin State : UP Auth-Type : None Circuit Id : 0 Retransmit Int : 5 Type : Pt-to-Pt LSP Pacing Int : 100 Mesh Group : Inactive CSNP Int : 10 Level : L2 Adjacencies : 0 Desg IS : 1720.2116.
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 6850 stacks with two or more switches support redundancy, where 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-14. • Enable IS-IS.
Configuring IS-IS Configuring IS-IS • Assign ports to the VLANs. The physical ports participating in the IS-IS network must be assigned to the created VLANs. Assigning ports to a VLAN is described in “Assigning Ports to VLANs,” in the OmniSwitch 6800/6850/9000 Network Configuration Guide. • Set the area ID (optional). The routers participating in the IS-IS network must be assigned an area identification number.
Configuring IS-IS Configuring IS-IS 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. The area ID is a 1–13 byte variable length integer, which specifies the area address of an IS-IS routing process. For creating an IS-IS area first assign area ID to each router present in the network by using the ip isis area-id command. There can be more than one router in an area.
Configuring IS-IS Configuring IS-IS The level capability can be configured globally on the router or on specific interfaces. By default, the router can operate at both levels.
Configuring IS-IS Configuring IS-IS • When the router is globally configured to act at Level-1, the potential adjacency will also be Level-1. If the interface is configured at Level-2 capability, the router will not form potential adjacency with the neighbor. • When the router is globally configured to act at Level-2, the potential adjacency will also be at Level-2. If the interface is configured at Level-1 capability, the router will not form potential adjacency with the neighbor.
Configuring IS-IS Configuring IS-IS If the encrypt-key parameter is used to configure the password through the CLI, then its value should be the same as the one that appears in the configuration snapshot. Note. By default, the authentication is disabled and no authentication type is configured Simple Authentication Simple authentication works by including the password in the packet. This helps to protect the routers from a configuration mishap.
Configuring IS-IS Configuring IS-IS MD5 Authentication MD5 authentication can be used to protect the system from malicious actions. MD5 authentication can be used to encrypt information sent over the network. MD5 authentication works by using shared secret key. Key is used to sign the packets with an MD5 checksum, so that the packets cannot be forged or tampered with. Since the key is not included in the packet, snooping the key is not possible.
Configuring IS-IS Configuring IS-IS To enable the authentication of PSNP PDUs globally, enter the following: -> ip isis psnp-auth Level Authentication You can enable authentication and configure the authentication types for specific IS-IS levels globally using ip isis level auth-type command. For example: -> ip isis level 2 auth-type md5 encrypt-key 7a1e441a014b4030 The above example configures the authentication type as MD5 for level 2 IS-IS PDUs and the key. Note.
Configuring IS-IS Configuring IS-IS Note. Both the ip isis interface hello-auth-type and ip isis interface level hello-auth-type can be configured for the authentication of either simple or MD5 type with the password specified either in plain text or in encrypted form. For the explanations about the authentication types and the key types refer Simple authentication and MD5 authentication.
Configuring IS-IS Configuring IS-IS To set the LSP interval to 120 seconds, enter the following: -> ip isis interface vlan-101 lsp-pacing-interval 120 To set the LSP retransmit interval to 100 seconds, enter the following: -> ip isis interface lan-3 retransmit-interval 100 Note. The retransmit interval should be greater than the expected round-trip delay between two devices.This will avoid any needless retransmission of PDUs.
Configuring IS-IS Configuring IS-IS Configuring Redistribution Using Route Maps It is possible to configure the IS-IS protocol to advertise routes learned from other routing protocols (ASexternal routes) into the IS-IS network. Such a process is referred to as route redistribution and is configured using the ip redist command. IS-IS redistribution uses route maps to control how external routes are learned and distributed.
Configuring IS-IS Configuring IS-IS Refer to the “IP Commands” chapter in the OmniSwitch CLI Reference Guide for more information about the ip route-map command parameters and usage guidelines. Once a route map is created, it is then applied using the ip redist command. See “Configuring Route Map Redistribution” on page 3-28 for more information. 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).
Configuring IS-IS Configuring IS-IS 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 IS-IS Configuring IS-IS a result, if there is no match for the metric value in sequence 10, then the match interface statement in sequence 20 is processed. However, if a route matches the metric value 8, then sequence 20 is not used. The set statement for whichever sequence was matched is applied. A route map sequence may contain multiple match statements. If these statements are of the same kind (e.g., match metric 5, match metric 8, etc.
Configuring IS-IS Configuring IS-IS Configuring Route Map Redistribution The ip redist command is used to configure the redistribution of routes from a source protocol into the ISIS destination protocol. This command is used on the IS-IS router that will perform the redistribution. A source protocol is a protocol from which the routes are learned. A destination protocol is the one into which the routes are redistributed.
Configuring IS-IS Configuring IS-IS Route Map Redistribution Example The following example configures the redistribution of RIP routes into an IS-IS network using a route map (rip-to-isis) to filter specific routes: -> ip route-map rip-to-isis sequence-number 10 action deny -> ip route-map rip-to-isis sequence-number 10 match metric 5 -> ip route-map rip-to-isis sequence-number 20 action permit -> ip route-map rip-to-isis sequence-number 20 match ipv4-interface intf_isis -> ip route-map rip-to-isis sequen
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 Configuring IS-IS Configuring Redundant Switches in a Stack for Graceful Restart By default, IS-IS graceful restart is disabled. When graceful restart is enabled, the router can either be a helper or a restarting router. When graceful restart is enabled on the router, the helper mode is automatically enabled by default. To configure IS-IS graceful restart support on OmniSwitch 6850 Series switches, use the ip isis graceful-restart command. Note.
IS-IS Application Example Configuring IS-IS 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. VLAN 5 Interface 10.4.1.
Configuring IS-IS IS-IS Application Example Router 2 -> vlan 5 name vlan-isis -> ip interface vlan-isis address 10.4.1.2 mask 255.0.0.0 vlan 5 -> vlan 5 port default 1/10 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 status enable Step 3: Create and Enable Area ID Now the areas should be created and enabled.
Verifying IS-IS Configuration Configuring IS-IS Router 2 -> ip isis interface vlan-isis -> ip isis interface vlan-isis status enable 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.
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 as defined in RFC 4271. The Alcatel-Lucent implementation of BGP is designed for enterprise networks, specifically for border routers handling a public network connection, such as the organization’s Internet Service Provider (ISP) link.
Configuring BGP • Configuring redistribution using route maps. See “Configuring Redistribution” on page 4-53. • Enabling IPv6 BGP Unicast. See “Enabling/Disabling IPv6 BGP Unicast” on page 4-68. • Configuring an IPv6 BGP Peer. See “Configuring an IPv6 BGP Peer” on page 4-68. • Configuring IPv6 BGP Networks. See “Configuring IPv6 BGP Networks” on page 4-73. • Configuring IPv6 Redistribution. See “Configuring IPv6 Redistribution” on page 4-76.
Configuring BGP BGP Specifications BGP Specifications RFCs Supported 4271–A Border Gateway Protocol 4 (BGP-4) 2439–BGP Route Flap Damping 3392–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 4760–Multiprotocol Extensions for BGP-4 2545–Use of BGP-4 Multipr
Quick Steps for Using BGP Configuring BGP Quick Steps for Using BGP 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. By default the AS number is 1, but you may want to change this number to fit your network requirements.
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. The OmniSwitch implementation supports BGP-4, the latest version of BGP, as defined in RFC 1771.
BGP Overview Configuring BGP BGP is intended for use in networks with multiple autonomous systems. It is not intended to be used as a LAN routing protocol, such as RIP or Open Shortest Path First (OSPF). In addition, when BGP is used as an internal routing protocol, it is best used in autonomous systems with multiple exit points as it includes features that help routers decide among multiple exit paths.
Configuring BGP BGP Overview Internal vs. External BGP Although BGP is an exterior gateway protocol, it can still be used inside an AS as a pipe to exchange BGP updates. BGP connections inside an AS are referred to as Internal BGP (IBGP), while BGP connections between routers in separate ASs are referred to as External BGP (EBGP). 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.
BGP Overview Configuring BGP Communities A community is a group of destinations that share some common property. A community is not restricted to one network or one autonomous system. Communities are used to simplify routing policies by identifying routes based on a logical property rather than an IP prefix or an AS number. 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.
Configuring BGP BGP Overview 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.
BGP Overview Configuring BGP In the diagram above, Clients 1, 2, and 3 peer with Reflector 1, and Clients 4, 5, and 6 peer with Reflector 2. Reflector 1 and 2 peer with each other.
Configuring BGP BGP Overview BGP Confederations Confederations are another way of dealing with large networks with many BGP speakers. Like route reflectors, confederations are recommended when speakers are forced to handle large numbers of BGP sessions at the same time. Note. This feature is not supported in the IPv6 BGP environment. Confederations are sub ASs within a larger AS. Inside each sub AS, all the rules of IBGP apply.
BGP Overview Configuring BGP Policies Routing policies enable route classification for importing and exporting routes. The goal of routing policies is to control traffic flow. Policies can be applied to egress and ingress traffic. Note. Policies can be applied only to IPv4 routes and not to IPv6 prefixes. Policies act as filters to either permit or deny specified routes that are being learned or advertised from a peer.
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, you would use the pattern: [64512-65535]$ which means “match any AS number from 64512 to 65535 (inclusive) which occurs at the end of the AS path.
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 The Route Selection Process Several metrics are used to make BGP routing decisions. These metrics include the route’s local preference, the AS Path, and the Multi-Exit Discriminator (MED). These metrics are organized into a hierarchy such that if a tie results, the next important criteria is used to break the tie until a decision is made for the route path. BGP selects the best path to an autonomous system from all known paths and propagates the selected path to its neighbors.
Configuring BGP BGP Overview Route Dampening Route dampening is a mechanism for controlling route instability. If a route is enabled and disabled frequently, it can cause an abundance of UPDATE and WITHDRAWN messages to expend speaker 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.
BGP Configuration Overview Configuring BGP 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 Load the BGP protocol. See “Starting BGP” on page 4-19. 2 Set up router-wide parameters, such as the router’s AS number, default local preference, and enable the BGP protocol. See “Setting Global BGP Parameters” on page 4-20.
Configuring BGP Starting BGP Starting BGP Before BGP is operational on your router you must load it to running memory and then administratively enable the protocol using the ip load bgp and ip bgp status commands. Follow these steps to start BGP. 1 Install advanced routing image file in the active boot directory.
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. You can assign one and only one AS number to a router using the ip bgp autonomous-system command. That same router may contain peers that belong to a different AS than the AS you assign your router. 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 The default behavior of BGP requires that it must be synchronized with the IGP before BGP may advertise transit routes to external ASs. It is important that your network is consistent about the routes it advertises, 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.
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 the route paths. show ip bgp aggregate-address Displays aggregate configuration information. show ip bgp dampening Displays the current route dampening configuration settings.
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 usually share a subnet.
Configuring BGP Parameter Description Configuring a BGP Peer Default Value/ Comments Command Enable or disables maximum pre- ip bgp neighbor maximum-prefix fix warning for a peer. warning-only 80 percent Allows external peers to commu- ip bgp neighbor ebgp-multihop nicate with each other even when they are not directly connected. disabled Configures the BGP peer name. peer IP address ip bgp neighbor description Sets the BGP peer to use next hop ip bgp neighbor next-hop-self processing behavior.
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 Aggregate Routes Configuring BGP 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 BGP Configuring Local Routes (Networks) Configuring Local Routes (Networks) A local BGP network is used to indicate to BGP that a network should originate from a specified router. A network must be known to the local BGP speaker; it also must originate from the local BGP speaker. Networks have some parameters that can be configured, such as local-preference, community, and metric.
Configuring Local Routes (Networks) Configuring BGP Configuring Network Parameters Once a local network is added to a speaker, you can configure three parameters that are attached to routes generated by the ip bgp network command. These three attributes are the local preference, the 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 BGP Configuring Local Routes (Networks) Viewing Network Settings To view the network settings for all networks assigned to the speaker, enter the show ip bgp network command, as shown: -> show ip bgp network A display similar to the following appears: Network Mask Admin state Oper state ---------------+---------------+-----------+---------155.132.40.0 255.255.255.0 disabled not_active 155.132.1.3 255.255.255.
Controlling Route Flapping Through Route Dampening Configuring BGP Controlling Route Flapping Through Route Dampening Route dampening minimizes the effect of flapping routes in a BGP network. Route flapping occurs when route information is updated erratically, such as when a route is announced and withdrawn at a rapid rate. Route flapping can cause problems in networks connected to the Internet, where route flapping will involve the propagation of many routes.
Configuring BGP Controlling Route Flapping Through Route Dampening Enabling Route Dampening Route dampening is disabled by default. 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.
Controlling Route Flapping Through Route Dampening Configuring BGP Setting the Reuse Value The dampening reuse value is used to determine if a route should be re-advertised. If the number of flaps for a route falls below this number, then the route is re-advertised. For example, if the reuse value is set at 150, and a route with 250 flaps exceeds the reach halflife it would be re-advertised as its flap number would now be 125.
Configuring BGP Controlling Route Flapping Through Route Dampening Clearing the History By clearing the dampening history, you are resetting all of the dampening information on all of the routes back to zero, as if dampening had just been activated. Route flap counters are reset and any routes that were suppressed due to route flapping violations are unsuppressed. Dampening information on the route will start re-accumulating as soon as the command is entered and the statistics are cleared.
Setting Up Route Reflection Configuring BGP Setting Up Route Reflection BGP requires that all speakers in an autonomous system be fully meshed (i.e., each speaker must have a peer connection to every other speaker in the AS) so that external routing information can be distributed to all BGP speakers in an AS. However, fully meshed configurations are difficult to scale in large networks.
Configuring BGP Setting Up Route Reflection This same configuration using a route reflector would not require that all BGP speakers be fully meshed. One of the speakers is configured to be a route reflector for the group. In this case, the route reflector is Speaker C. 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.
Setting Up Route Reflection Configuring BGP When a route reflector receives a route it, selects the best path based on its policy decision criteria. The internal peers to which the route reflector advertises depends on the source of the route. The table below shows the rules the reflector follows when advertising path information: Route Received From... Route Advertised To...
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 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 (i.e. AS path list), community attributes (i.e. community lists), specific destinations (i.e. prefix lists), etc. 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 2 Set the policy action using the ip bgp policy route-map action command. The policy action either permits or denies routes that match the filter. Permitted routes are advertised, while denied routes are not. For example: -> ip bgp policy route-map mapfilter 1 action deny Prefix policy mapfilter now denies routes that are filtered. 3 Add various conditions to the route map policy.
Configuring BGP Route Map Options Routing Policies Command Configures a BGP weight value to be ip bgp policy route-map weight assigned to inbound routes when a match is found. Configures the value to strip from the community attribute of the routes matched by this route map instance (sequence number).
Routing Policies Configuring BGP Assigning a Policy to a Peer Once policies have been created using the commands described above, the policies can be applied to routes learned from a specific peer, or route advertisements to a specific peer. The following table shows the list of commands that allow you to assign a policy to a peer: BGP Attribute Command Assigns an inbound AS path list filter to a BGP peer.
Configuring BGP Routing Policies Assigning In and Out Bound Community List Policies to a Peer Community list policies filter routes based on matches made to a list of communities of which the route is a member. Communities group routes by attaching labels to them specifying a behavior (such as no export). To filter routes learned from a peer by the community list, enter the peer’s IP address with the ip bgp neighbor in-communitylist command as shown: -> ip bgp neighbor 172.22.2.
Routing Policies Configuring BGP Reconfiguring Peer Policies You can configure policies and assign these policies to a BGP peer, either to control in-bound routes or out-bound routes advertisement. Additionally, it is possible to change or modify these peer policies, after they are assigned to a peer. Once the policies have been modified, they have to be re-applied to the peer. To re-apply the policies to only the peer under consideration, you can use the in-reconfigure and the out-reconfigure commands.
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 number 50 is used by default. 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 Sequence 10 and sequence 20 are both linked to route map rm_1 and are processed in ascending order according to their sequence number value. Note that there is an implied logical OR between sequences. As a result, if there is no match for the tag value in sequence 10, then the match interface statement in sequence 20 is processed. However, if a route matches the tag 8 value, then sequence 20 is not used.
Configuring BGP Configuring Redistribution Configuring Route Map Redistribution The ip redist command is used to configure the redistribution of routes from a source protocol into the BGP destination protocol. This command is used on the BGP router that will perform the redistribution. A source protocol is a protocol from which the routes are learned. A destination protocol is the one into which the routes are redistributed.
Configuring Redistribution Configuring BGP Route Map Redistribution Example The following example configures the redistribution of OSPF routes into a BGP network using a route map (ospf-to-bgp) to filter specific routes: -> ip route-map ospf-to-bgp sequence-number 10 action deny -> ip route-map ospf-to-bgp sequence-number 10 match tag 5 -> ip route-map ospf-to-bgp sequence-number 10 match route-type external type2 -> ip route-map ospf-to-bgp sequence-number 20 action permit -> ip route-map ospf-to-bgp seq
Configuring BGP Configuring Redistribution Configuring Redundant CMMs for Graceful Restart On OmniSwitch devices in a redundant CMM configuration, during a CMM takeover/failover, interdomain routing is disrupted. Alcatel-Lucent Operating System BGP needs to retain forwarding information, also help a peering router performing a BGP restart to support continuous forwarding for interdomain traffic flows by following the BGP graceful restart mechanism. By default, BGP graceful restart is enabled.
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 BGP Speaker 1 40.0.0.1/24 10.0.0.1/24 20.0.0.1/24 AS 300 EBGP IBGP 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 Administratively enable BGP: -> ip bgp status enable BGP Speaker 2 Assign the speaker to AS 100: -> ip bgp autonomous-system 100 Peer with the other speakers in AS 100 (for internal BGP, and to create a fully meshed BGP network): -> ip bgp neighbor 30.0.0.2 -> ip bgp neighbor 30.0.0.2 remote-as 100 -> ip bgp neighbor 30.0.0.2 status 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 Peer with the external speaker in AS 100 (for external BGP): -> ip bgp neighbor 40.0.0.1 -> ip bgp neighbor 40.0.0.1 remote-as 100 -> ip bgp neighbor 40.0.0.1 status enable Administratively enable BGP: -> ip bgp status 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 BGP for IPv6 Overview • IPv6 route aggregation. • Policy-based route processing for IPv6 prefixes and peers. • Routemap, prefix-list, community-list, and aspath-list policies. • Graceful Restart capability for IPv6 prefixes. • EBGP Multihop. • Other multiprotocol capabilities for VPNs, MPLS label exchanges, etc.
Quick Steps for Using BGP for IPv6 Configuring BGP Quick Steps for Using BGP for IPv6 The following steps create an IPv4 BGP peer capable of exchanging IPv6 prefixes: 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.
Configuring BGP Quick Steps for Using BGP for IPv6 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 for IPv6 Configuring BGP Configuring BGP for IPv6 This section describes the BGP for IPv6 configuration, which includes enabling and disabling IPv6 BGP unicast, configuring IPv6 BGP peers, and configuring IPv6 BGP networks using Alcatel-Lucent’s Command Line Interface (CLI) commands. Enabling/Disabling IPv6 BGP Unicast By default, BGP peers exchange only IPv4 unicast address prefixes.
Configuring BGP Configuring BGP for IPv6 Configuring an IPv4 BGP Peer to Exchange IPv6 Prefixes A BGP peer that is identified by its IPv4 address can be used to exchange IPv6 prefixes. However, to do this both the peers should be enabled with IPv6 BGP unicast and should have interfaces that support IPv6 addresses.
Configuring BGP for IPv6 Configuring BGP Configuring an IPv6 BGP Peer Using Link-Local IPv6 Addresses to Exchange IPv6 Prefixes To configure an IPv6 BGP peer using its link-local IPv6 address to exchange IPv6 prefixes, follow the steps mentioned below: 1 Create an IPv6 BGP peer with which the BGP speaker will establish peering using its link-local IPv6 address with the ipv6 bgp neighbor command, as shown: -> ipv6 bgp neighbor fe80::2d0:95ff:fee2:6ed0 2 Assign an AS number to the IPv6 peer using the ipv6
Configuring BGP Configuring BGP for IPv6 Changing the Local Router Address for an IPv6 Peer Session By default, TCP connections to an IPv6 peer's address are assigned to the closest interface based on reachability. Any operational local IPv6 interface can be assigned to the IPv6 BGP peering session by explicitly forcing the TCP connection to use the specified interface. The ipv6 bgp neighbor update-source command sets the local IPv6 interface address or name through which this BGP peer can be contacted.
Configuring BGP for IPv6 Configuring BGP Optional IPv6 BGP Peer Parameters Peer Parameter Command The interval, in seconds, between BGP retries ipv6 bgp neighbor conn-retryto set up a connection via the transport protocol interval with another peer. Enables or disables a BGP speaker to send a default route to its peer.
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 Local Preference Local preference is an attribute that specifies the degree of preference to be given to a specific route when there are multiple routes to the same destination. This attribute is propagated throughout the autonomous system and is represented by a numeric value. The higher the number, the higher the preference.
Configuring BGP Configuring BGP for IPv6 Viewing Network Settings To view the network settings for all IPv6 networks assigned to the speaker, enter the show ipv6 bgp network command, as shown: -> show ipv6 bgp network A display similar to the following appears: Network Admin state Oper state ----------------------+-----------+-----------2525:500:600::/64 enabled active To display a specific IPv6 network, enter the same command with the network IPv6 address and mask, as shown: -> show ipv6 bgp network 25
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 The administrative status of a route map redistribution configuration is enabled by default.
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 ipv6 IPv6 BGP Application Example interface Link_To_Speaker3 vlan 3 address 2001:DB8:C18:1::1/64 Link_To_Speaker3 bgp neighbor 2001:DB8:C18:1::2 bgp neighbor 2001:DB8:C18:1::2 remote-as 100 bgp neighbor 2001:DB8:C18:1::2 activate-ipv6 bgp neighbor 2001:DB8:C18:1::2 status 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 interfac
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.
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 RFCs Supported 2365—Administratively Scoped IP Multicast 2932—IPv4 Multicast Routing MIB Maximum Multicast Flows per Network 400 (with hardware routing; see note below) Interface (NI) Module Valid Scoped Address Range 239.0.0.0 to 239.255.255.255 Note.
Configuring Multicast Address Boundaries Quick Steps for Configuring Multicast Address Boundaries 3 Configure a multicast address boundary on the IP interface. Information must include the IP address assigned at step 2, as well as a scoped multicast address and the corresponding subnet mask. For example: -> ip mroute-boundary vlan-2 239.120.0.0 255.255.0.0 Note. Optional. To verify the multicast boundary configuration, enter the show ip mroute-boundary command.
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 Because multicast address boundaries are part of the Advanced Routing software, the advanced routing image must be present in an OmniSwitch, before you can begin configuring the feature. In addition, the multicast routing protocol (e.g., PIM-SM or DVMRP) for your network must first be loaded to memory via the ip load command.
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 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 Note. The ip interface command is not supported in Release 5.3.1. For this release use the vlan router ip command instead. See the OmniSwitch CLI Reference Guide for more information. 8 Assign a boundary on the switch’s router interface. For this example, the interface is given the bound- ary 239.188.0.
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 6800/6850/9000 Advanced Routing Configuration Guide December 2007
6 Configuring DVMRP This chapter includes descriptions for Distance Vector Multicast Routing Protocol (DVMRP). DVMRP is a dense-mode multicast routing protocol. DVMRP—which is 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 RFCs Supported 2667—IP Tunnel MIB IETF Internet-Drafts Supported Distance-Vector Multicast Routing Protocol MIB draft-ietf-idmr-dvmrp-v3-11.txt DVMRP Version Supported DVMRPv3.
Configuring DVMRP Quick Steps for Configuring DVMRP Quick Steps for Configuring DVMRP Note. DVMRP requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM-SM 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 status command.
Quick Steps for Configuring DVMRP Configuring DVMRP Note. Optional. To verify DVMRP interface status, enter the show ip dvmrp interface command. The display is similar to the one shown here: Address Vlan Metric Admin-Status Oper-Status -----------------+------+--------+-------------+------------178.14.1.
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: • The advanced routing image must be present in the switch’s current running directory (i.e., Working or Certified) before DVMRP can be enabled or configured. • DVMRP requires that IP Multicast Switching (IPMS) is enabled.
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 status 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 (by default, every 60 seconds). 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 • 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-41. • Verifying IPv6 PIM configuration—see page 7-43. For detailed information about PIM commands, see the “PIM Commands” chapter in the OmniSwitch CLI Reference Guide.
Configuring PIM PIM Specifications PIM Specifications RFCs Supported 2362—Protocol Independent Multicast-Sparse Mode (PIM-SM) Protocol Specification 2934—Protocol Independent Multicast MIB for Ipv4 2932—Ipv4 Multicast Routing MIB 3973—Protocol Independent Multicast-Dense Mode (PIM-DM) 3376—Internet Group Management Protocol 4601—Protocol Independent Multicast-Sparse Mode (PIM-SM) Internet Drafts Supported draft-ietf-pim-sm-v2-new-05.
PIM Defaults Configuring PIM PIM Defaults The following table lists the defaults for PIM configuration: Parameter Description Command Default Value/Comments PIM status ip load pim Disabled PIM load status - sparse mode ip pim sparse status Disabled PIM load status - dense mode ip pim dense status 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 static-rp Di
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
Quick Steps for Configuring PIM-DM Configuring PIM Quick Steps for Configuring PIM-DM . Note PIM requires that IP Multicast Switching (IPMS) is enabled. IPMS is automatically enabled when a multicast routing protocol (either PIM or DVMRP) is enabled globally and on an interface and when the operational status of the interface is up. However, if you wish to manually enable IPMS on the switch, use the ip multicast status command.
Configuring PIM Quick Steps for Configuring PIM-DM 6 Save your changes to the Working directory’s boot.cfg file by entering the following command: -> write memory Note. Optional. To verify PIM interface status, enter the show ip pim interface command.
PIM Overview Configuring PIM PIM Overview Protocol-Independent Multicast (PIM) is an IP multicast routing protocol that uses routing information provided by unicast routing protocols such as RIP and OSPF. Note that PIM is not dependent on any particular unicast routing protocol. Downstream routers must explicitly join PIM distribution trees in order to receive multicast streams on behalf of receivers or other downstream PIM routers.
Configuring PIM PIM Overview Bootstrap Routers (BSRs) The role of a Bootstrap Router (BSR) is to keep routers in the network up to date on reachable C-RPs. The BSR’s list of reachable C-RPs is also referred to as an RP set. There is only one BSR per PIM domain. This allows all PIM routers in the PIM domain to view the same RP set. A C-RP periodically sends out messages, known as C-RP advertisements.
PIM Overview Configuring PIM Note. The Join message is known as a (*,G) join because it joins group G for all sources to that group. Sender 1 Receiver Designated Router (DR) RP Router Legend IGMP Join from Receiver Receiver 1 PIM Join Message from DR Note. 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.
Configuring PIM PIM Overview Sender 1 sends multicast data to its Designated Router (DR). The source DR then unicast-encapsulates the data into PIM-SM Register messages and sends them on to the RP.
PIM Overview Configuring PIM Avoiding Register Encapsulation Switching to a Shortest Path Tree (SPT) topology allows PIM routers to avoid Register encapsulation of data packets that occurs in an RPT. Register encapsulation is inefficient for the following reasons: • The encapsulation and unencapsulation of Register messages tax router resources. Hardware routing does not support encapsulation and unencapsulation. • Register encapsulation may require that data travel unnecessarily over long distances.
Configuring PIM PIM Overview RP Initiation of (S, G) Source-Specific Join Message When the data rate at the Rendezvous Point (RP) exceeds the configured RP threshold value, the RP will initiate a (S, G) source-specific Join message toward the source. Legend Encapsulated Data Exceeding RP Threshold Sender 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.
PIM Overview Configuring PIM When the Sender’s DR receives the (S,G) Join, it sends data natively as well. When these data packets arrive natively at the RP, the RP will be receiving two copies of each of these packets—one natively and one encapsulated. 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.
Configuring PIM PIM Overview SPT Switchover The last hop Designated Router (DR) initiates the switchover to a true Shortest Path Tree (SPT) once the DR receives the first multicast data packet. This method does not use any preconfigured thresholds, such as RP threshold (as described above). 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. SPT status is enabled by default.
PIM Overview Configuring PIM Once the Sender’s DR receives the (S,G) Join message, the DR sends the multicast packets natively along the Shortest Path Tree. At this point, Router X (the router shown between the Sender’s DR and the Receiver’s DR) will be receiving two copies of the multicast data—one from the SPT and one from the RPT. This router drops the packets arriving via the RP tree and forwards only those packets arriving via the SPT.
Configuring PIM PIM Overview The Receiver is now receiving multicast traffic along the Shortest Path Tree between the Receiver and the Source.
Configuring PIM Configuring PIM Configuring PIM Enabling PIM on the Switch By default, PIM protocol is disabled on a 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 -> ls working Listing Directory /flash/working: drw drw -rw -rw -rw -rw -rw -rw 2048 2048 164 662998 2791518 296839 698267 876163 Jan Jan Jan Jan Jan Jan Jan Jan 1 1 1 1 1 1 1 1 04:37 05:58 04:32 04:36 04:36 04:36 04:37 04:37 ./ ../ boot.cfg Kadvrout.img Kbase.img Kdiag.img Keni.img Kos.img The Kadvrout.img file is present in the current running configuration (in this case, Working). (additional table output not shown) Note.
Configuring PIM Configuring PIM Checking the Current IPMS Status To view the current status of IPMS on the switch, use the show ip multicast command.
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 -> show ip pim sparse Status Keepalive Period Max RPs Probe Time Register Checksum Register Suppress Timeout RP Threshold SPT Status = = = = = = = -> show ip pim dense Status Source Lifetime State Refresh Interval State Refresh Limit Interval State Refresh TTL enabled, 210, 32, 5, header, 60, 1, = enabled, = = = = enabled, 210, 60, 0, = 16 Mapping an IP Multicast Group to a PIM Mode PIM mode is an attribute of the IP multicast group mapping and cannnot be configured on
Configuring PIM Configuring PIM You can also specify whether or not this static configuration overrides the dynamically learned group mapping 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. By default, the priority option is not set, and the override option is set to false. Use the no form of this command to remove a static configuration of a SSM mode group mapping.
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 224.0.0.0. The class D group mask (255.255.255.255) has been translated into the Classless Inter-Domain Routing (CIDR) prefix length of /4. The C-RP is listed as 172.21.63.11. The status is enabled. Specifying the Maximum Number of RPs You can specify the maximum number of RPs allowed in a PIM-SM domain. (The switch’s default value is 32.) Important. PIM must be globally disabled on the switch before changing the maximum number of RPs.
Configuring PIM Configuring PIM 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. The value of the priority is considered for the selection of CBSR for PIM domain. The higher the value, the higher the priority. Use the no form of this command to remove the local routers’ candidacy as the BSR.
Configuring PIM Configuring PIM Note. 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 224.0.0.0/4 172.21.63.11 asm 192 BSR 224.0.0.0/4 214.0.0.7 asm 192 Static 232.0.0.
Configuring PIM Configuring PIM Group Address/Pref Length RP Address Mode Override Precedence Status ---------------------------+-------------+-----+--------+----------+-------224.0.0.0/4 172.21.63.11 asm false none enabled Group-to-RP Mapping Using one of the mechanisms described in the sections above, a PIM-SM router receives one or more possible group-range-to-RP mappings.
Configuring PIM RP Switchover SPT Status Configuring PIM = 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 Msgs Rcvd = 0 Origin = None Group = None RP = None Invalid Join Prune Notifications Period = 65535 Msgs Rcvd = 0 Origin = None Group = None RP = None RP Mapping Notifications Period = 65535 Count = 0 Interface Election Notifications Period = 65535 Count = 0 page 7-30 OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide December 2007
Configuring PIM PIM-SSM Support 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. In other words, a Shortest Path Tree (SPT) between the receiver and the source is created without the use of a Rendezvous Point (RP). By default, PIM software supports Source-Specific Multicast.
Verifying PIM Configuration Configuring PIM 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.
Configuring PIM PIM for IPv6 Overview 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.
Quick Steps for Configuring IPv6 PIM-DM Configuring PIM Note. The IPv6 interface on which the PIM is enabled must be an already configured IPv6 interface on the switch 4 Map the IPv6 PIM-Dense Mode (DM) protocol for a multicast group via the ipv6 pim dense group command. For example: -> ipv6 pim dense group ff0e::1234/128 5 Globally enable the IPv6 PIM protocol by entering the following command. By default, PIM protocol status is disabled.
Configuring PIM Configuring IPv6 PIM Configuring IPv6 PIM This section describes PIM for IPv6 configuration, which includes 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, and Configuring RP-switchover for IPv6 PIM using AlcatelLucent’s Command Line Interface (CLI) commands.
Configuring IPv6 PIM Configuring PIM -> ipv6 pim dense status enable Disabling IPv6 PIM Mode on the Switch To globally disable IPv6 PIM-Sparse Mode on the switch, use the ipv6 pim sparse status command. Enter the command syntax as shown below: -> ipv6 pim sparse status disable To globally disable IPv6 PIM-Dense Mode on the switch, use the ipv6 pim dense status command.
Configuring PIM Configuring IPv6 PIM value obsoletes the override option, you can use either the priority or override parameter only. By default, the priority option is not set, and the override option is set to false. Use the no form of this command to remove a static configuration of a dense mode group mapping.
Configuring IPv6 PIM Configuring PIM IPv6 PIM Bootstrap and RP Discovery Before configuring IPv6 PIM-SM parameters, please consider the following important guidelines. For correct operation, every IPv6 PIM-SM router within an IPv6 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 IPv6 PIM -> show ipv6 pim candidate-rp RP Address Group Address Priority Interval Status ------------------+---------------+---------+---------+-------3000::11 FF00::/8 192 60 enabled The group address is listed as FF00::/8. The C-RP is listed as 3000::11. The status is enabled. For more information about these displays, see the “PIM Commands” chapter in the OmniSwitch CLI Reference Guide.
Configuring IPv6 PIM Configuring PIM disabled. For more information on static RP status and configuration, refer to “Configuring Static RP Groups” below. A C-RP periodically sends out messages, known as C-RP advertisements. When a BSR receives one of these advertisements, the associated C-RP is considered reachable (if a valid route to the network exists). The BSR then periodically sends an updated list of reachable C-RPs to all neighboring routers in the form of a Bootstrap message. Note.
Configuring PIM Configuring IPv6 PIM Note. If static RP status is specified, the method for group-to-RP mapping provided by the Bootstrap mechanism and C-RP advertisements is automatically disabled. For more information on this alternate method of group-to-RP mapping, refer to page 7-26. To view current Static RP Configuration settings, use the show ipv6 pim static-rp command.
IPv6 PIM-SSM Support Configuring PIM Verifying RP-Switchover To view the status of the RP-switchover capability, use the show ipv6 pim sparse command. -> 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 IPv6 PIM-SSM Support IPv6 Protocol-Independent Multicast Source-Specific Multicast (IPv6 PIM-SSM) is a highly efficient extension of IPv6 PIM.
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 Configuring PIM page 7-44 December 2007 OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide
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 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.
Alcatel-Lucent License Agreement 10. Governing Law. This License Agreement shall be construed and governed in accordance with the laws of the State of California. 11. Severability. Should any term of this License Agreement be declared void or unenforceable by any court of competent jurisdiction, such declaration shall have no effect on the remaining terms herein. 12. No Waiver.
Third Party Licenses and Notices Third Party Licenses and Notices The licenses and notices related only to such third party software are set forth below: A. Booting and Debugging Non-Proprietary Software A small, separate software portion aggregated with the core software in this product and primarily used for initial booting and debugging constitutes non-proprietary software, some of which may be obtained in source code format from Alcatel-Lucent for a limited period of time.
Third Party Licenses and Notices C. Linux Linux is written and distributed under the GNU General Public License which means that its source code is freely-distributed and available to the general public. D. GNU GENERAL PUBLIC LICENSE: Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Third Party Licenses and Notices verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope.
Third Party Licenses and Notices b Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c Accompany it with the information you received as to the offer to distribute corresponding source code.
Third Party Licenses and Notices consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
Third Party Licenses and Notices Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program.
Third Party Licenses and Notices Material copyright Linux Online Inc. Design and compilation copyright (c)1994-2002 Linux Online Inc. Linux is a registered trademark of Linus Torvalds Tux the Penguin, featured in our logo, was created by Larry Ewing Consult our privacy statement URLWatch provided by URLWatch Services. All rights reserved. E. University of California Provided with this product is certain TCP input and Telnet client software developed by the University of California, Berkeley. F.
Third Party Licenses and Notices H. Apptitude, Inc. Provided with this product is certain network monitoring software (“MeterWorks/RMON”) licensed from Apptitude, Inc., whose copyright notice is as follows: Copyright (C) 1997-1999 by Apptitude, Inc. All Rights Reserved. Licensee is notified that Apptitude, Inc. (formerly, Technically Elite, Inc.), a California corporation with principal offices at 6330 San Ignacio Avenue, San Jose, California, is a third party beneficiary to the Software License Agreement.
Third Party Licenses and Notices L. Wind River Systems, Inc. Provided with this product is certain software (“Run-Time Module”) licensed from Wind River Systems, Inc.
Index A aggregate routes BGP 4-32 application examples BGP 4-4, 4-60 BGP IPv6 4-66 DVMRP 6-3 IS-IS 3-5, 3-32 multicast address boundaries 5-2, 5-8 OSPF 1-4, 1-34, 2-4, 2-25 area border routers 1-8, 1-9, 2-9, 2-10 areas 1-8, 2-9 assigning interfaces 1-20 backbones 1-8 creating 1-17, 2-15 deleting 1-18, 2-16 NSSAs 1-11 ranges 1-19 route metrics 1-19, 2-16 specifying type 1-17, 2-15 status 1-18, 2-15 stub 1-10, 2-11 summarization 1-18 Totally Stubby 1-11 AS 4-6 AS boundary routers 1-9, 2-10 AS path policies as
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 tunnels 6-9, 6-17 verifying the configuration 6-17 dyna
ip ospf area command 1-17, 2-15, 3-16 ip ospf area summary command 1-18 ip ospf area type command 1-17, 2-15 ip ospf exit-overflow-interval command 1-30 ip ospf extlsdb-limit command 1-30 ip ospf host command 1-30, 2-24 ip ospf interface area command 1-20 ip ospf interface auth-key command 1-21 ip ospf interface auth-type command 1-21, 3-19, 3-20 ip ospf interface command 1-20, 2-16, 3-16 ip ospf interface cost command 1-22, 3-22 ip ospf interface dead-interval command 1-22, 3-22 ip ospf interface hello-int
NBMA routing 1-12 overview 1-7, 2-8 preparing the network 1-16, 2-14 redistribution policies 1-23 routers 1-9, 2-10 simple authentication 1-21 specifications 1-2, 2-2 stub areas 1-10, 2-11 verify configuration 1-39, 2-30, 3-34 virtual links 1-9, 1-22, 2-10, 2-17 OSPF filters 1-23, 3-24 OSPF interfaces 1-20, 2-16 assigning to areas 1-20 authentication 1-21 creating 1-20, 3-16 enabling 1-21 modifying 1-22, 2-17 OSPF redistribution policies 1-23 deleting 1-26, 1-28, 2-20, 2-23, 3-26, 3-28, 4-55, 4-57, 4-76 P
show ip ospf area stub command 1-18, 2-16 show ip ospf interface command 1-20, 2-16 show ip pim group-map command 7-27 show ip pim sparse command 7-21 show ip redist command 4-63 show ipv6 bgp neighbors command 4-82 show ipv6 bgp neighbors timers command 4-82 show ipv6 bgp network command 4-75 show ipv6 bgp path command 4-82 show ipv6 bgp routes command 4-82 show ipv6 pim dense command 7-34 show ipv6 redist command 4-77 Source-Specific Multicast (SSM) see PIM-SSM source-specific multicast addresses 5-4 spec
page -6 OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide December 2007
