HP ProCurve Switch Software Multicast and Routing Guide 3500 switches 3500yl switches 5400zl switches 6200yl switches 6600 switches 8200zl switches Software version K.14.
HP ProCurve 3500 Switches 3500yl Switches 5400zl Switches 6200yl Switch 6600 Switches 8200zl Switches September 2009 K.14.
© Copyright 2005–2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change with out notice. All Rights Reserved. Disclaimer This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of HewlettPackard.
Contents Product Documentation About Your Switch Manual Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Printed Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Electronic Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Software Feature Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii 1 Getting Started Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Multimedia Traffic Control with IP Multicast (IGMP) Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 IGMP General Operation and Features . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 IGMP Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multicast Flow Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 General Configuration Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 PIM-DM Operating Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Configuring PIM-DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Static Rendezvous Point (Static-RP) . . . . . . . . . . . . . . . . . . . . . . . 4-17 Operating Rules and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Configuration Steps for PIM-SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Per-Router Global Configuration Context . . . . . . . . . . . . . . . . . . . . . . 4-20 Per-VLAN PIM-SM Configuration . . . . . . . . . .
Listing Data for an Active Multicast Group . . . . . . . . . . . . . . . . . 4-48 Listing All VLANs Having Currently Active PIM Flows . . . . . . . . 4-50 Displaying PIM-Specific Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51 Displaying the Current PIM status and Global Configuration . . 4-51 Displaying Current PIM Entries Existing In the Multicast Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring IP Parameters for Routing Switches . . . . . . . . . . . . . . . 5-15 Configuring IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Changing the Router ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15 Configuring ARP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 How ARP Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 Enabling Proxy ARP . . . . .
Changing the Cost of Routes Learned on a VLAN Interface . . . . 5-33 Configuring RIP Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34 Define RIP Redistribution Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34 Modify Default Metric for Redistribution . . . . . . . . . . . . . . . . . . . 5-35 Enable RIP Route Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35 Changing the Route Loop Prevention Method . . . . . . . . . . . . . . . . . .
Configuring OSPF on the Routing Switch . . . . . . . . . . . . . . . . . . . . . . 5-62 1. Enable IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62 2. Enable Global OSPF Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62 3. Changing the RFC 1583 OSPF Compliance Setting . . . . . . . . . 5-63 4. Assign the Routing Switch to OSPF Areas . . . . . . . . . . . . . . . . 5-65 5. Assign VLANs and/or Subnets to Each Area . . . . . . . . . . . . . . 5-69 6.
Displaying OSPF SPF Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 5-117 Displaying OSPF Route Information . . . . . . . . . . . . . . . . . . . . . . 5-119 Displaying OSPF Traps Enabled . . . . . . . . . . . . . . . . . . . . . . . . . 5-121 Debugging OSFP Routing Messages . . . . . . . . . . . . . . . . . . . . . . 5-121 OSPF Equal-Cost Multipath (ECMP) for Different Subnets Available Through the Same Next-Hop Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option 82 Field Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-138 Forwarding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-141 Configuration Options for Managing DHCP Client Request Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-141 Multiple Option 82 Relay Agents in a Client Request Path . . . . 5-142 Validation of Server Response Packets . . . . . . . . . . . . . . . . . . . .
Basic Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15 Associating More Than One Virtual IP Address With a VR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17 Configuring VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VRRP Statistics Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39 Displaying Global VRRP Statistics Only . . . . . . . . . . . . . . . . . . . . 6-39 Displaying Statistics for All VRRP Instances on the Router . . . . 6-40 Displaying Statistics for All VRRP Instances in a VLAN . . . . . . . 6-42 Displaying Statistics for a Specific VRRP Instance . . . . . . . . . . . 6-43 Displaying the “Near-Failovers” Statistic . . . . . . . . . . . . . . . . . . .
Product Documentation About Your Switch Manual Set Note For the latest version of all ProCurve switch documentation, including Release Notes covering recently added features, please visit the ProCurve Networking Web site at www.procurve.com/manuals. Printed Publications The two publications listed below are printed and shipped with your switch. The latest version of each is also available in PDF format on the ProCurve Web site, as described in the Note at the top of this page.
Software Feature Index For the software manual set supporting your 3500/3500yl/5400zl/6200yl/6600/ 8200zl switch model, this feature index indicates which manual to consult for information on a given software feature. Note This Index does not cover IPv6 capable software features. For information on IPv6 protocol operations and features (such as DHCPv6, DNS for IPv6, Ping6, and MLD Snooping), refer to the IPv6 Configuration Guide. Intelligent Edge Software Features.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Multicast and Routing Access Security Guide 802.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Factory Default Settings X Flow Control (802.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Multiple Configuration Files X Network Management Applications (SNMP) X Out-of-Band Management (OOBM) X OpenView Device Management X Multicast and Routing Passwords and Password Clear Protection X ProCurve Manager (PCM) X Ping X Port Configuration X Port Monitoring X Port Security X Port Status X Port Trunking (LACP) X Port-Based Access Control (802.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management sFlow X SFTP X SNMPv3 X Software Downloads (SCP/SFTP, TFPT, Xmodem) X Multicast and Routing Source-Port Filters Access Security Guide X Spanning Tree (STP, RSTP, MSTP) X SSHv2 (Secure Shell) Encryption X SSL (Secure Socket Layer) X Stacking (3500/3500yl/6200yl/6600 switches only) X Syslog X System Information X TACACS+ Authentication X Telnet Access X TFTP X Time Protocols (Time
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Web-based Authentication Web UI Multicast and Routing Access Security Guide X X xxiii
xxiv
1 Getting Started Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Screen Simulations . . . . . . . . . . . . . . . . .
Getting Started Introduction Introduction This guide is intended for use with the following ProCurve switches: ■ 8200zl switches ■ 6600 switches ■ 5400zl switches ■ 3500, 3500yl and 6200yl switches It describes how to use the command line interface (CLI), Menu interface, and web browser to configure, manage, monitor, and troubleshoot switch opera tion. For an overview of product documentation for the above switches, refer to “Product Documentation” on page xiii.
Getting Started Conventions Syntax: aaa port-access authenticator < port-list > Command Prompts In the default configuration, your switch displays a CLI prompt similar to the following example: ProCurve 8212zl# To simplify recognition, this guide uses ProCurve to represent command prompts for all switch models. For example: ProCurve# (You can use the hostname command to change the text in the CLI prompt.) Screen Simulations Displayed Text.
Getting Started Sources for More Information Sources for More Information For information about switch operation and features not covered in this guide, consult the following sources: ■ Note Feature Index—For information on which manual to consult for a given software feature, refer to the “Software Feature Index” on page xiv.
Getting Started Sources for More Information • ■ ■ ■ ■ file transfers, switch monitoring, troubleshooting, and MAC address management Advanced Traffic Management Guide—Use this guide for information on topics such as: • VLANs: Static port-based and protocol VLANs, and dynamic GVRP VLANs • spanning-Tree: 802.1D (STP), 802.1w (RSTP), and 802.
Getting Started Sources for More Information Getting Documentation From the Web To obtain the latest versions of documentation and release notes for your switch, go to the ProCurve Networking manuals web page at www.hp.com/go/ procurve/manuals. Online Help Menu Interface If you need information on specific parameters in the menu interface, refer to the online help provided in the interface. For example: Online Help for Menu Figure 1-2.
Getting Started Sources for More Information Command Line Interface If you need information on a specific command in the CLI, type the command name followed by help. For example: Figure 1-3. Example of CLI Help Web Browser Interface If you need information on specific features in the HP ProCurve Web Browser Interface (hereafter referred to as the “web browser interface”), use the online Help.
Getting Started Need Only a Quick Start? Need Only a Quick Start? IP Addressing If you just want to give the switch an IP address so that it can communicate on your network, or if you are not using VLANs, ProCurve recommends that you use the Switch Setup screen to quickly configure IP addressing. To do so, do one of the following: ■ Enter setup at the CLI Manager level prompt. Procurve# setup ■ In the Main Menu of the Menu interface, select 8.
2 Multimedia Traffic Control with IP Multicast (IGMP) Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 IGMP General Operation and Features . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 IGMP Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 IGMP Operating Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Basic Operation . . . . . .
Multimedia Traffic Control with IP Multicast (IGMP) Overview Overview This chapter describes multimedia traffic control with IP multicast (IGMP) to reduce unnecessary bandwidth usage on a per-port basis, and how to config ure it with the switch’s built-in interfaces: For general information on how to use the switch’s built-in interfaces, refer to these chapters in the Management and Configuration Guide for your switch: Note 2-2 ■ Chapter 3, “Using the Menu Interface” ■ Chapter 4, “Using the Command
Multimedia Traffic Control with IP Multicast (IGMP) IGMP General Operation and Features IGMP General Operation and Features IGMP Features Feature Default Menu CLI view igmp configuration n/a — page 2-7 show igmp status for multicast groups used by the selected VLAN n/a — Yes enabling or disabling IGMP (Requires VLAN ID Context) disabled — page 2-9 per-port packet control auto — page 2-10 IGMP traffic priority normal — page 2-11 querier enabled — page 2-11 fast-leave disabled —
Multimedia Traffic Control with IP Multicast (IGMP) IGMP General Operation and Features Note IGMP configuration on the switches covered in this guide operates at the VLAN context level. If you are not using VLANs, then configure IGMP in VLAN 1 (the default VLAN) context. IGMP Terms 2-4 ■ IGMP Device: A switch or router running IGMP traffic control features. ■ IGMP Host: An end-node device running an IGMP (multipoint, or multicast communication) application.
Multimedia Traffic Control with IP Multicast (IGMP) IGMP General Operation and Features IGMP Operating Features Basic Operation In the factory default configuration, IGMP is disabled. To enable IGMP ■ If multiple VLANs are not configured, you configure IGMP on the default VLAN (DEFAULT_VLAN; VID = 1). ■ If multiple VLANs are configured, you configure IGMP on a per-VLAN basis for every VLAN where this feature is to be used.
Multimedia Traffic Control with IP Multicast (IGMP) IGMP General Operation and Features Notes Whenever IGMP is enabled, the switch generates an Event Log message indicating whether querier functionality is enabled. IP multicast traffic groups are identified by IP addresses in the range of 224.0.0.0 to 239.255.255.255. Also, incoming IGMP packets intended for reserved, or “well-known” multicast addresses automatically flood through all ports (except the port on which the packets entered the switch).
Multimedia Traffic Control with IP Multicast (IGMP) CLI: Configuring and Displaying IGMP CLI: Configuring and Displaying IGMP IGMP Commands Used in This Section show ip igmp configuration page 2-7 ip igmp page 2-9 high-priority-forward page 2-11 auto <[ethernet] page 2-10 blocked <[ethernet] page 2-10 forward <[ethernet] page 2-10 querier page 2-11 show ip igmp Refer to the section titled “Internet Group Management Protocol (IGMP) Status” in appendix B of
Multimedia Traffic Control with IP Multicast (IGMP) CLI: Configuring and Displaying IGMP For example, suppose you have the following VLAN and IGMP configurations on the switch: VLAN ID VLAN Name IGMP Enabled Forward with High Priority Querier 1 Yes No No DEFAULT_VLAN 22 VLAN-2 Yes Yes Yes 33 VLAN-3 No No Yes You could use the CLI to display this data as follows: Figure 2-1.
Multimedia Traffic Control with IP Multicast (IGMP) CLI: Configuring and Displaying IGMP Enabling or Disabling IGMP on a VLAN. You can enable IGMP on a VLAN, along with the last-saved or default IGMP configuration (whichever was most recently set), or you can disable IGMP on a selected VLAN. Syntax: [no] ip igmp Enables IGMP on a VLAN. Note that this command must be executed in a VLAN context. For example, here are methods to enable and disable IGMP on the default VLAN (VID = 1).
Multimedia Traffic Control with IP Multicast (IGMP) CLI: Configuring and Displaying IGMP Configuring Per-Port IGMP Traffic Filters. Syntax: vlan < vid > ip igmp [auto < port-list > | blocked < port-list > | forward < port-list >] Used in the VLAN context, this command specifies how each port should handle IGMP traffic. (Default: auto.
Multimedia Traffic Control with IP Multicast (IGMP) CLI: Configuring and Displaying IGMP Configuring IGMP Traffic Priority. Syntax: [no] vlan < vid > ip igmp high-priority-forward This command assigns “high” priority to IGMP traffic or returns a high-priority setting to “normal” priority. (The traffic will be serviced at its inbound priority.) (Default: normal.) ProCurve(config)# vlan 1 ip igmp high-priority-forward Configures high priority for IGMP traffic on VLAN 1.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates How IGMP Operates The Internet Group Management Protocol (IGMP) is an internal protocol of the Internet Protocol (IP) suite. IP manages multicast traffic by using switches, multicast routers, and hosts that support IGMP. (In Hewlett-Pack ard’s implementation of IGMP, a multicast router is not necessary as long as a switch is configured to support IGMP with the querier feature enabled.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates in the join request is determined by the requesting application running on the IGMP client.) When a networking device with IGMP enabled receives the join request for a specific group, it forwards any IP multicast traffic it receives for that group through the port on which the join request was received. When the client is ready to leave the multicast group, it sends a Leave Group message to the network and ceases to be a group member.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Table 2-1.Comparison of IGMP Operation With and Without IP Addressing IGMP Function Available With IP Addressing Available Operating Differences Without an IP Address Configured on the VLAN Without IP Addressing? Forward multicast group traffic to any port on the VLAN that has received a join request for that multicast group. Yes None Forward join requests (reports) to the Querier.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Automatic Fast-Leave IGMP Fast-Leave IGMP. Depending on the switch model, Fast-Leave is enabled or disabled in the default configuration.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Because of the multicast flooding problem mentioned above, the IGMP FastLeave feature is disabled by default on all ProCurve switches that do not support Data-Driven IGMP. (See the table above.) The feature can be enabled on these switches via an SNMP set of this object: hpSwitchIgmpPortForceLeaveState..
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates does not wait for the actual Querier to verify that there are no other group members on port A3. If the switch itself is the Querier, it does not query port A3 for the presence of other group members. Note that Fast-Leave operation does not distinguish between end nodes on the same port that belong to different VLANs.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates “X” member on that port. If the port does not receive a join request for that group within the forced-leave interval, the switch then blocks any further group “X” traffic to the port. Configuring Forced Fast-Leave IGMP Syntax: [no] vlan < vid > ip igmp forcedfastleave Enables IGMP Forced Fast-Leave on the specified ports in the selected VLAN, even if they are cascaded. (Default: Disabled.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates IGMP Proxy Forwarding Note For more information about PIM-DM and PIM-SM, see the chapters “PIM-DM (Dense Mode)” and “PIM-SM (Sparse Mode)” in this guide. When a network has a border router connecting a PIM-SM domain to a PIM-DM domain, the routers that are completely within the PIM-DM domain have no way to discover multicast flows in the PIM-SM domain.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Border router 1 PIM SM DOMAIN Multicast traffic source (Multicast address 235.1.1.1 Border router 2 VLAN 2 Routing Switch 1 Proxy joins towards Border router 1 Routing Switch 3 VLA N4 VL AN Routing Switch 2 5 VLAN 3 PIM DM DOMAIN VLAN 1 Initial IGMP join For 235.1.1.1 Proxy joins towards Border router 2 Figure 2-4. IGMP Proxy Example 2-20 4.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates CLI Commands for IGMP Proxy Configuration Syntax: [no] igmp-proxy-domain [ ] Add or leave a multicast domain. The no form of the command is used to remove a multicast domain. All VLANs associated with the domain must first be removed for this command to work. See the no form of igmp-proxy in the VLAN context command.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates The example below shows the lower and upper boundaries of the multicast address range associated with the domain named Bob. ProCurve(config)# igmp-proxy-domain Bob 111.11.111.111 234.0.0.1 ProCurve(config)# igmp-proxy-domain Bob 111.11.111.111 236.1.1.1 Figure 2-6. Setting the Lower and Upper Bounds for Multicasting VLAN Context Command The following command is performed when in VLAN context mode.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates IGMP Proxy Show Command Syntax: show igmp-proxy < entries | domains | vlans > Shows the currently active IGMP proxy entries, domains, or vlans. ProCurve(config)# show igmp-proxy entries Total number of multicast routes: 2 Multicast Address ----------------234.43.209.12 235.22.22.12 226.44.3.3 Border Address -------------192.168.1.1 15.43.209.1 192.168.1.1 VID ----1 1 2 Multicast Domain -----George SAM George Figure 2-7.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates ProCurve(config)# show igmp-proxy vlans IGMP PROXY VLANs VID -----1 1 1 2 4 4 Multicast Domain ---------------George Sam Jane George George Bill Active entries -------------1 1 0 1 0 0 Figure 2-9. Example Showing Active IGMP Proxy VLANs Operating Notes for IGMP Proxy Forwarding 2-24 ■ You can configure up to 12 multicast domains.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Caution ■ You must remove all VLAN associations with the domain name before that domain name can be removed. ■ The appropriate border routers must be used for each VLAN, or PIM-DM will not forward the traffic. This could occur when multiple border routers exist.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates PIM SM DOMAIN Routing Switch 1 (Border router) PIM DM DOMAIN VLAN 1 Proxy VLAN 2 to 1 Routing Switch 2 Routing Switch 3 Proxy VLAN 1 to 2 VLAN 2 Figure 2-10.
Multimedia Traffic Control with IP Multicast (IGMP) Using the Switch as Querier Using the Switch as Querier The function of the IGMP Querier is to poll other IGMP-enabled devices in an IGMP-enabled VLAN to elicit group membership information. The switch performs this function if there is no other device in the VLAN, such as a multicast router, to act as Querier.
Multimedia Traffic Control with IP Multicast (IGMP) Excluding Well-Known or Reserved Multicast Addresses from IP Multicast Filtering Excluding Well-Known or Reserved Multicast Addresses from IP Multicast Filtering Each multicast host group is identified by a single IP address in the range of 224.0.0.0 through 239.255.255.255. Specific groups of consecutive addresses in this range are termed “well-known” addresses and are reserved for pre defined host groups.
Multimedia Traffic Control with IP Multicast (IGMP) Excluding Well-Known or Reserved Multicast Addresses from IP Multicast Filtering Notes IP Multicast Filters. This operation applies to the ProCurve Series 5400zl switches, the Series 3500yl switches, the switch 6200yl, the switch 8212zl, the Series 5300xl switches, as well as the 1600M, 2400M, 2424M, 4000M, and 8000M, but not to the Series 2500, 2650, Series 4100gl, Series 4200vl, or 6108 switches (which do not have static traffic/security filters).
Multimedia Traffic Control with IP Multicast (IGMP) Excluding Well-Known or Reserved Multicast Addresses from IP Multicast Filtering 2-30
3 PIM-DM (Dense Mode) Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 PIM-DM Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PIM-DM (Dense Mode) Overview Overview This chapter describes protocol-independent multicast routing operation on the switches covered in this guide and how to configure it with the switch’s built-in interfaces, and assumes an understanding of multimedia traffic con trol with IP multicast (IGMP), which is described in chapter 2, “Multimedia Traffic Control with IP Multicast (IGMP)”.
PIM-DM (Dense Mode) Introduction Introduction Feature Default Menu CLI Web Configure PIM Global n/a — 3-12 — Configure PIM VLAN Interface n/a — 3-15 — Disabled — 3-23 — 0 (Forward All) — 3-28 — Display PIM Route Data Display PIM Status In a network where IP multicast traffic is transmitted for multimedia applica tions, such traffic is blocked at routed interface (VLAN) boundaries unless a multicast routing protocol is running.
PIM-DM (Dense Mode) Feature Overview Feature Overview PIM-DM on the switches covered in this guide includes: ■ 3-4 Routing Protocol Support: PIM uses whichever unicast routing proto col is running on the routing switch. These can include: • RIP • OSPF • Static routes • Directly connected interfaces ■ VLAN Interface Support: Up to 128 outbound VLANs are supported in the multicast routing table (MRT) at any given time.
PIM-DM (Dense Mode) PIM-DM Operation PIM-DM Operation PIM-DM operates at the router level to direct traffic for a particular multicast group along the most efficient path to the VLANs having hosts that have joined that group. A unicast source address and a multicast group address comprise a given source/group (S/G) pair. Multicast traffic moving from a source to a multicast group address creates a flow to the area(s) of the network requiring the traffic.
PIM-DM (Dense Mode) PIM-DM Operation Video Server Multicast Tree Routing Switch (PIM) Routing Switch (PIM & IGMP) Switch/IGMP Switch/IGMP Switch/IGMP Hosts Routing Switch (PIM & IGMP) Switch/IGMP Switch/IGMP Hosts Figure 3-1.
PIM-DM (Dense Mode) PIM-DM Operation Multicast Flow Management This section provides details on how the routing switch manages forwarding and pruned flows. This information is useful when planning topologies to include multicast support and when viewing and interpreting the Show com mand output for PIM-DM features. Initial Flood and Prune. As mentioned earlier, when a router running PIM DM receives a new multicast flow, it initially floods the traffic to all down stream multicast routers.
PIM-DM (Dense Mode) PIM-DM Operation These multicast switches support the state refresh feature but must handle periodic flood-prune cycles for the downstream routers that lack this feature. Video Server 8212zl #4 Video Server Video Server These multicast switches support the state refresh feature and do not require periodic flood-prune cycles for a given multicast group, which frees up bandwidth for other uses.
PIM-DM (Dense Mode) Terminology General Configuration Elements The configured elements PIM-DM requires are: Note 1. IP routing enabled on all routing switches you want to carry routed multicast traffic. 2. Configure the routing method(s) needed to reach the interfaces (VLANs) on which you want multicast traffic available for hosts in your network: • Enable RIP or OSPF at both the global and VLAN levels on the routers where there are connected hosts that may issue multicast joins.
PIM-DM (Dense Mode) PIM-DM Operating Rules Multicast Address: In IP multicast traffic on the switch, this is a single IP address that can be used by a group of related or unrelated clients wanting the same data. A single S/G pair consists of unicast source address and a multicast group address. Sometimes termed a “multicast group address”. See also “Source” and “S/G Pair”.
PIM-DM (Dense Mode) Configuring PIM-DM Configuring PIM-DM Command Page PIM Global Context Commands [no] ip multicast-routing 3-12 [no] router pim 3-12 state-refresh 3-13 trap 3-13 PIM Interface Context Commands [no] ip pim-dense 3-15 [ ip-addr < any | source-ip-address >] 3-15 [ hello-interval ] 3-15 [ hello-delay ] 3-16 [ graft-retry-interval ] 3-16 [ max-graft-retries ] 3-17 [ lan-prune-delay ] 3-17 [ propagation-delay ] 3-18 [ override-delay ] 3-18 [ ttl-threshold ] 3-19 3-
PIM-DM (Dense Mode) Configuring PIM-DM PIM-DM requires configuration on both the global level and on the VLAN (interface) level. The recommended configuration order is: 1. Enable IGMP on all VLANs where hosts may join a multicast group. 2. Enable the following at the global level. • IP routing • IP multicast routing • Router PIM and any non-default, global PIM settings you want to apply • Router RIP, Router OSPF, and/or a static route 3.
PIM-DM (Dense Mode) Configuring PIM-DM Syntax: router pim state-refresh < 10 - 300 > Executed in the PIM context, this command sets the interval in seconds between successive State Refresh messages orig inated by the routing switch. Note that only the routing switch connected directly to the unicast source initiates state-refresh packets. All other PIM routers in the network only propagate these state-refresh packets.
PIM-DM (Dense Mode) Configuring PIM-DM To configure global-level PIM operation for the “8212zl #1” routing switch, you would use the commands shown in figure 3-3, below. ProCurve(config)# ip routing ProCurve(config)# ip multicast-routing ProCurve(config)# router rip ProCurve(rip)# exit ProCurve(config)# router pim ProCurve(pim)# state-refresh 45 ProCurve(pim)# trap hardware-mrt-full ProCurve(pim)# write mem ProCurve(pim)# exit Enables IP routing. Enables multicast routing. Enables RIP.
PIM-DM (Dense Mode) Configuring PIM-DM After configuring the global-level PIM operation on a routing switch, go to the device’s VLAN context level for each VLAN you want to include in your multicast routing domain. (Refer to “PIM VLAN (Interface) Configuration Context”, below. PIM VLAN (Interface) Configuration Context Syntax: [no] ip pim-dense [no] vlan < vid > ip pim Enables multicast routing on the VLAN interface to which the CLI is currently set. The no form disables PIM on the VLAN.
PIM-DM (Dense Mode) Configuring PIM-DM For example, if multiple routers are connected to the same VLAN and the routing switch requests multicast traffic, all routers on the VLAN receive that traffic. (Those which have pruned the traffic will drop it when they receive it.
PIM-DM (Dense Mode) Configuring PIM-DM Syntax: ip pim-dense [ max-graft-retries < 1 - 10 > vlan < vid > ip pim-dense [ max-graft-retries < 1 - 10 > Changes the number of times the routing switch will retry sending the same graft packet to join a flow. If a Graft Ack response is not received after the specified number of retries, the routing switch ceases trying to join the flow.
PIM-DM (Dense Mode) Configuring PIM-DM Syntax: ip pim-dense [ propagation-delay < 250-2000 >] vlan < vid > ip pim-dense [ propagation-delay < 250-2000 >] ip pim-dense [ override-interval < 500 - 6000 >] vlan < vid > ip pim-dense [ override-interval < 500 - 6000 >] A routing switch sharing a VLAN with other multicast routers uses these two values to compute the lan-prune-delay setting (above) for how long to wait for a PIM-DM join after receiving a prune packet from downstream for a particular multicast gr
PIM-DM (Dense Mode) Configuring PIM-DM Syntax: ip pim-dense [ ttl-threshold < 0 - 255 > ] vlan < vid > ip pim-dense [ ttl-threshold < 0 - 255 > ] Sets the multicast datagram time-to-live (router hop-count) threshold for the VLAN. Any IP multicast datagrams or state refresh packets with a TTL less than this threshold will not be forwarded out the interface. The default value of 0 means all multicast packets are forwarded out the interface.
PIM-DM (Dense Mode) Configuring PIM-DM Video Server On the three routing switches, VLAN 25 is multinetted with subnets that match in only one instance. Since subnet 10.38.10.x exists on VLAN 25 in all routing switches, it serves as the source IP address for multicast traffic outbound on VLAN 25 for the network. 8212zl #1 VLAN 25 10.38.10.1 10.38.11.1 Note the common subnet instance in (multinetted) VLAN 25 (10.38.10.x). 10.38.12.1 VLAN 27 10.27.30.1 VLAN 29 8212zl #3 10.29.30.
PIM-DM (Dense Mode) Configuring PIM-DM ProCurve(config)# show run ... ip routing Enables IP routing; required for multicast routing. ... vlan 29 name "VLAN29" untagged A11-A15,A17 ip address 10.29.30.1 255.255.255.0 ip igmp exit Multinetting and IGMP enabled in VLAN 25. vlan 25 name "VLAN25" untagged A20-A24 ip address 10.38.10.1 255.255.255.0 ip address 10.38.11.1 255.255.255.0 ip address 10.38.12.1 255.255.255.0 ip igmp exit vlan 27 name "VLAN27" untagged A6-A10,A18 ip address 10.27.30.1 255.255.255.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Displaying PIM Data and Configuration Settings Command Page show ip mroute 3-23 [ interface < vid >] 3-24 [< multicast-ip-addr > < source-ip-addr >] 3-25 show ip pim [ interface [< vid >]] 3-28 3-29 3-30 [ mroute 3-31 [< multicast-group-address> < multicast-source-address >]] 3-32 neighbor [< ip-address >] 3-22 3-34 3-35
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Displaying PIM Route Data Syntax: show ip mroute Without parameters, lists all VLANs actively forwarding routed, multicast traffic. Group Address: The multicast address of the specific multicast group (flow). Source Address: The unicast address of the multicast group source. Neighbor: The IP address of the upstream multicast router interface (VLAN) from which the multicast traffic is coming.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Syntax: show ip mroute [ interface < vid >] Lists these settings: VLAN: The VID specified in the command. Protocol Identity: PIM-DM only. TTL: The time-to-live threshold for packets forwarded through this VLAN. When configured, the routing switch drops multi cast packets having a TTL lower than this value.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Syntax: show ip mroute [< multicast-ip-addr > < source-ip-addr >] Lists the following data for the specified flow (multicast group): Group Address: The multicast group IP address for the current group. Source Address: The multicast source address < source-ip-addr > for the current group. Source Mask: The subnet mask applied to the multicast source address < source-ip-addr >.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Multicast Routing Protocol: Identifies the multicast routing protocol through which the current flow was learned. Unicast Routing Protocol: Identifies the routing protocol through which the routing switch learned the upstream interface for the current multicast flow. The listed protocol will be either RIP, OSPF, or Static Route.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings ProCurve(config)# 10.27.30.2 show ip mroute 239.255.255.5 IP Multicast Route Entry Group Address : 239.255.255.5 Source Address : 10.27.30.2 Source Mask : 255.255.255.0 Neighbor : 10.30.229.1 VLAN : 27 Up time (sec) : 408 Expire Time (sec) : 150 A blank Neighbor field indicates that the multicast server is directly connected to the routing switch.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Displaying PIM Status Syntax: show ip pim Displays PIM status and global parameters. PIM Status: Shows either enabled or disabled. State Refresh Interval (sec): A PIM routing switch originates state refresh messages to inform its neighbors of the active flows it is currently routing. This updates the current flow data on PIM routers that join or rejoin a multicast network after the initial flood and prune.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Syntax: show ip pim [interface] Lists the PIM interfaces (VLANs) currently configured in the routing switch. VLAN: Lists the VID of each VLAN configured on the switch to support PIM-DM. IP Address: Lists the IP addresses of the PIM interfaces (VLANs). Mode: Shows dense only. ProCurve(config)# show ip pim interface PIM Interfaces VLAN ---25 27 29 IP Address --------------10.38.10.1 10.27.30.1 10.29.30.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Syntax: show ip pim [interface [< vid >]] Displays the current configuration for the specified VLAN (PIM interface). Refer to table 3-1, below. ProCurve(config)# show ip pim interface 29 PIM Interface VLAN : 29 IP Address : 10.29.30.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Field Default Control Command Override Interval (msec) 2500 vlan < vid > ip pim-dense override-interval < 500 - 6000 > Propagation Delay 500 (msec) vlan < vid > ip pim-dense propagation-delay < 250-2000 > SR TTL Threshold (router hops) 0 vlan < vid > ip pim-dense ttl-threshold < 0 - 255 > LAN Prune Delay Yes vlan < vid > ip pim-dense lan-prune-delay LAN Delay Enabled No Shows Yes if all multicast routers on the current VLAN in
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings This output shows the routing switch is receiving two multicast groups from an upstream device at 10.27.30.2. The “0” metric shows that the routing switch is directly connected to the multicast source. ProCurve(config)# show ip pim mroute PIM Route Entries Group Address --------------239.255.255.1 239.255.255.5 Source Address --------------10.27.30.2 10.27.30.2 Metric ---------0 0 Metric Pref ---------0 0 Figure 3-13.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings DownStream Interfaces: – VLAN: Lists the VID of the destination VLAN on the nexthop multicast router. – Prune Reason: Identifies the reason for pruning the flow to the indicated VLAN: • Prune: A neighbor multicast router has sent a prune request. • Assert: Another multicast router connected to the same VLAN has been elected to provide the path for the specified multicast group traffic.
PIM-DM (Dense Mode) Displaying PIM Data and Configuration Settings Syntax: show ip pim [neighbor] Lists PIM neighbor information for all PIM neighbors connected to the routing switch: IP Address: Lists the IP address of a neighbor multicast router. VLAN: Lists the VLAN through which the routing switch connects to the indicated neighbor. Up Time: Shows the elapsed time during which the neighbor has maintained a PIM route to the routing switch.
PIM-DM (Dense Mode) Operating Notes Syntax: show ip pim [neighbor [< ip-address >]] Lists the same information as show ip pim neighbor (page 3-34) for the specified PIM neighbor: This example simulates output from Routing Switch “#1” in Figure 3-4 on Page 3-20. The data is from the first downstream neighbor ( Routing Switch “#2”). ProCurve(config)# show ip pim neighbor 10.29.30.2 PIM Neighbor IP Address VLAN : 10.29.30.2 : 29 Up Time (sec) : 26 Expire Time (sec) : 79 Figure 3-16.
PIM-DM (Dense Mode) Operating Notes Flow Capacity. The routing switch provides an ample multicast environ ment, supporting 2048 multicast flows in hardware across a maximum of 64 VLANs. (A flow comprises a unicast source address and a multicast group address, regardless of the number of active hosts belonging to the multicast group at any given time.) IGMP Traffic High-Priority Disabled.
PIM-DM (Dense Mode) Troubleshooting Troubleshooting Symptom: Noticeable slowdown in some multicast traffic. If the switch is supporting more than 1022 active flows. This generates the message Unable to learn HW IP multicast groups, table FULL in the Event Log because there is no room in the hardware Multicast Routing Table to add another Multicast Group.
PIM-DM (Dense Mode) Messages Related to PIM Operation Messages Related to PIM Operation These messages appear in the Event Log and, if Syslog Debug is configured, in the designated Debug destinations. Note The value displayed at the end of each PIM Event Log message (and SNMP trap messages, if trap receivers are configured) indicates the number of times the switch has detected a recurring event since the last reboot.
PIM-DM (Dense Mode) Messages Related to PIM Operation Message Meaning I/F removal with IP < ip-addr > on vid < vlan-id > () Indicates that a PIM interface (VLAN) has been removed from the router as a result of an IP address change or removal. MCAST flow < multicast-address > < sourceaddress > not rteing (rsc low) () The indicated multicast flow is not routing. The routing switch is low on memory resources as a result of too many flows for the number of configured VLANs.
PIM-DM (Dense Mode) Messages Related to PIM Operation Message Meaning Rcvd pkt from rtr < ip-address >, unkwn pkt type < value > () A packet received from the router at < ip-address > is an unknown PIM packet type. (The < value > variable is the numeric value received in the packet.) Rcvd pkt ver# < ver-num >, from < ip-address >, expected < ver-num > () The versions of PIM-DM on the sending and receiving routers do not match.
PIM-DM (Dense Mode) Applicable RFCs Message Meaning Unable to alloc a msg buffer for < text-message > () Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed. Reduce the number of VLANs or the number of features in use. Remedies include one or more of the following: • Reduce the number of configured VLANs by moving some VLANs to another router.
PIM-DM (Dense Mode) Exceptions to Support for RFC 2932 - Multicast Routing MIB Exceptions to Support for RFC 2932 Multicast Routing MIB These MIB objects are not supported in the switches covered in this guide.
4 PIM-SM (Sparse Mode) Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Feature Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 PIM-SM Operation and Router Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 PIM-SM Operation . . . . . . . . . . . . . . .
PIM-SM (Sparse Mode) Contents VLAN Context Commands for Configuring PIM-SM . . . . . . . . . . . . . . 4-28 Enabling or Disabling IGMP in a VLAN . . . . . . . . . . . . . . . . . . . . . 4-28 Enabling or Disabling PIM-SM Per-VLAN . . . . . . . . . . . . . . . . . . . 4-29 Changing the Interval for PIM-SM Neighbor Notification . . . . . 4-30 Changing the Randomized Delay Setting for PIM-SM Neighbor Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PIM-SM (Sparse Mode) Contents Displaying BSR Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61 Displaying BSR Status and Configuration . . . . . . . . . . . . . . . . . . 4-61 Listing Non-Default BSR Configuration Settings . . . . . . . . . . . . . 4-62 Displaying the Current RP Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63 Displaying Candidate-RP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PIM-SM (Sparse Mode) Introduction Introduction Feature Default CLI Enable PIM-SM Support Disabled 4-26 Configure PIM-SM on VLAN Interfaces Disabled 4-28 Configure Router PIM Context Bootstrap Router Candidate Rendezvous-Point Candidate Notification Traps Shortest-Path Tree Disabled 4-35 4-37 4-41 4-42 Display Multicast Route Data n/a 4-47 Display PIM-Specific Data n/a 4-51 Display PIM Neighbor Data n/a 4-57 Display BSR and C-RP Data n/a 4-61 Display Current RP-Set n/a 4-63 Display
PIM-SM (Sparse Mode) Feature Overview and group members are sparsely distributed over a wide area can result in unnecessary multicast traffic on routers outside the distribution paths needed for traffic between a given multicast source and the hosts belonging to the multicast group. In such networks, PIM-SM can be used to reduce the effect of multicast traffic flows in network areas where they are not needed.
PIM-SM (Sparse Mode) Terminology software covered in this guide.) Note that BSR operation does not extend to statically configured RPs. (For more on this topic, refer to “Static Rendezvous Point (Static-RP)” on page 4-17.) ■ IGMP Compatibility: PIM-SM is compatible with IGMP version 2, and is fully interoperable with IGMP for determining multicast flows. ■ VRRP: PIM-SM is fully interoperable with VRRP to quickly transition multicast routes in the event of a failover.
PIM-SM (Sparse Mode) Terminology C-RP: See Candidate Rendezvous Point, above. Designated Router (DR): Within a given VLAN or network, the router elected to forward a multicast flow from its IP source (in the VLAN or network) to the appropriate rendezvous point (either an RP or static-RP) in the PIM-SM domain. Edge Router: Any router directly connected to a host or other endpoint in the network. Flow: Multicast traffic having one source and one multicast group address (destination).
PIM-SM (Sparse Mode) Terminology RP: See Rendezvous Point, above. RPT: See Rendezvous Point Tree. RP-Set: A complete list of multicast-group-to-RP mappings the BSR has learned and distributed to the C-RPs in a given PIM-SM domain. The learned RP-set applies only to C-RPs, and not to static-RPs. (Note, however, that the show ip pim rp-set command lists both the learned RP-set from the BSR and any static-RPs configured on the router.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types PIM-SM Operation and Router Types Unlike PIM-DM, PIM-SM assumes that most hosts do not want to receive multicast traffic, and uses a non-flooding multicast model to direct traffic for a particular multicast group from the source to the VLAN(s) where there are multicast receivers that have joined the group. As a result, this model sends traffic only to the routers that specifically request it.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types intermediate PIM-SM routers leading to the PIM-SM edge router(s) for the multicast receiver(s) requesting the traffic. (If the RP has no current join requests for the group, then the traffic is dropped at the RP.) Rendezvous Point (RP) Elected To Support Multicast Group “X” In default PIM-SM operation, the RPT path forms to deliver the first multicast packet from Group “X” to Host “Y”.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types page 4-67.) When completed, the switchover from the RPT to a shorter SPT can reduce unnecessary traffic concentrations in the network and reduce multicast traffic throughput delays. Note that the switchover from RPT to SPT is not instantaneous. For a short period, packets for a given multicast group may be received from both the RPT and the SPT. Also, in some topologies, the RPT and the SPT to the same edge router may be identical.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Border Routers and Multiple PIM-SM Domains Creating multiple domains enables a balancing of PIM-SM traffic within a network. Defining PIM-SM domain boundaries requires the use of PIM border routers (PMBRs), and multiple PMBRs can be used between any two domains. Note As of March 2006, the software covered by this guide does not support PMBR operation for PIM-SM networks.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Where multiple PIM-SM routers exist in a VLAN, the following criteria is used to elect a DR: 1. The router configured with the highest DR priority in the VLAN is elected. 2. If multiple routers in the VLAN are configured with the highest DR priority, then the router having the highest IP address is elected. In a given domain, each VLAN capable of receiving multicast traffic from a unicast source should have at least one DR.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Note Where static RPs are configured in the domain to support the same multicast group(s) as one or more (dynamic) C-RPs, then the RP-set data has the precedence for assigning RPs for these groups unless the static-RPs have been configured with the override option and if the multicast group mask for the static-RP equals or exceeds the same mask for the applicable C-RP(s). Refer to the Note on page 4-17. BSR Configuration and Election.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Note that the routers requesting multicast traffic are either edge routers directly connected to specific multicast receivers using IGMP to request the traffic, or are intermediate routers on the path between the edge routers and the RP. This operation forms an RP Tree (RPT) where only the destination multicast address appears in the RP routing table.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Candidate-RP Election. Within a PIM-SM domain, different RPs support different multicast addresses or ranges of multicast addresses. (That is, a given PIM-SM multicast group or range of groups is supported by only one active RP, although other candidate RPs can also be configured with overlap ping or identical support.) A candidate RP’s group-prefix configuration identifies the multicast groups the RP is enabled to support.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types Configuring a C-RP to support a given multicast group does not ensure election of the C-RP to support that group unless the group is excluded from all other RPs in the domain. Refer to “Redundant Group Coverage Provides Fault-Tolerance” on page 4-17. Also, within a PIM-SM domain, a router can be configured as a C-RP available for a given multicast group or range of groups and as the static RP for a given multicast group or range of groups.
PIM-SM (Sparse Mode) PIM-SM Operation and Router Types For these reasons, use of static-RPs should be limited to applications where no viable alternatives exist, or where the network is stable and requires configuring and maintaining only a few routers.
PIM-SM (Sparse Mode) Operating Rules and Recommendations ■ Static-RPs are not included in the RP-set messages generated by the BSR, and do not generate advertisements. ■ If a static-RP becomes unavailable, it is necessary to remove and/or replace the configuration for this RP in all routers in the domain. Configuration. Refer to “Statically Configuring an RP To Accept Multicast Traffic” on page 4-42. Operating Rules and Recommendations Guideline for Configuring Candidate RPs and BSRs.
PIM-SM (Sparse Mode) Configuration Steps for PIM-SM PIM-SM and PIM-DM. These two features cannot both be enabled on the same router at the same time. Supporting PIM-SM Across a PIM Domain. To properly move multicast traffic across a PIM-SM domain, all routers in the domain must be configured to support PIM-SM. That is, a router without PIM-SM capability blocks routed multicast traffic in a PIM-SM domain.
PIM-SM (Sparse Mode) Configuration Steps for PIM-SM Per-Router Global Configuration Context Use these steps to enable routing and PIM operation in the global configura tion context of each PIM-SM router (ProCurve(config)#_) 1. Enable routing. (Use ip routing.) 2. Enable multicast routing. (Use ip multicast-routing.) 3. Enable PIM. (Use router pim.) 4.
PIM-SM (Sparse Mode) Configuration Steps for PIM-SM b. Use ip pim-sparse to enter the VLAN’s pim-sparse context and do one of the following: – Enable PIM-SM on the VLAN and allow the default option (any) to dynamically determine the source IP address for the PIM-SM packets sent from this VLAN interface. – Enable PIM-SM on the VLAN and specify an IP address for the PIM-SM packets sent from this VLAN interface. (The specified IP address must already be statically configured on the VLAN.
PIM-SM (Sparse Mode) Configuration Steps for PIM-SM Features Accessed in Operation VLAN-< vid >-pim-sparse Context override-interval* (page 4-33) Resets the override interval of the LAN Prune Delay configured on the interface. (Default: 2500 milliseconds) propagation-delay* (page 4-33) Resets the delay interval for triggering LAN Prune Delay packets on the interface. (Default: 500 milliseconds) dr-priority (page 4-33) Resets the priority of the interface in the Designated Router election process.
PIM-SM (Sparse Mode) Configuration Steps for PIM-SM 4. Optional: In the PIM router context, change one or more of the traffic control settings in the following table. Options Accessed in Router PIM Context Operation rp-candidate group-prefix < group-addr/group-mask > Enter an address and mask to define an additional multicast group or a range of groups. rp-candidate hold-time < 30 - 255 > Tells the BSR how long it should expect the sending Candidate-RP router to be operative.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Configuring PIM-SM on the Router Command Page Global Context Commands [no] ip routing 4-26 [ no ] ip multicast-routing 4-26 [no] router < rip | ospf > 4-26 [no] ip route < src-ip-addr/mask >< dest > 4-26 [no] router pim 4-26 VLAN context 4-28 [no] ip igmp 4-28 ip pim-sparse [ip-address] hello-interval hello-delay nbr-timeout lan-prune-delay override-interval propagation-delay dr-priority 4-29 4-33 4-30 4-31 4-32 4-32 4-33 4-33 4-33 rou
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Global Configuration Context for Supporting PIM-SM Before configuring specific PIM-SM settings, it is necessary to enable IP routing, IP multicast-routing, an IP routing protocol, and PIM in the global configuration context. Also, if the router operates as an edge router for any end points (receivers) expected to join multicast groups, then it is also necessary to enable IGMP on the VLANs supporting such receivers.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Example of Configuring for PIM Support at the Global Level In default PIM-SM operation, the STP path activates and the RPT path drops off after the first multicast packet for a group is received via the Rendezvous Point (RP).
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router ProCurve(config)# show running-config Running configuration: ; J8693A Configuration Editor; Created on release #K.11.XX hostname "ProCurve" module 2 type J8705A module 1 type J8702A ip routing snmp-server community "public" Unrestricted vlan 1 name "DEFAULT_VLAN" Global Routing Configuration untagged A1-A24, B1-B24 for PIM-SM Support ip address 10.10.10.1 255.255.255.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Enabling or Disabling PIM-SM Per-VLAN Syntax: ip pim-sparse [ip-addr < any | < ip-addr >>] vlan < vid >] ip pim-sparse [ip-addr < any | < ip-addr >>] no [vlan < vid >] ip pim-sparse This command enables or disables PIM-SM in the designated VLAN interface and sets the source (and designated router) IP address for PIM-SM packets sent from the interface.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the Interval for PIM-SM Neighbor Notification Syntax: ip pim-sparse hello-interval < 5 - 300 > vlan < vid > ip pim-sparse hello-interval < 5 - 300 > Changes the frequency at which the router transmits PIM “Hello” messages on the current VLAN. The router uses “Hello” packets to inform neighboring routers of its presence.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the Randomized Delay Setting for PIM-SM Neighbor Notification Syntax: ip pim-sparse hello-delay < 0 - 5 > vlan < vid > ip pim-sparse hello-delay < 0 - 5 > Changes the maximum time in seconds before the router actually transmits the initial PIM Hello message on the current VLAN.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Enabling or Disabling LAN Prune Delay Syntax: [no] ip pim-sparse lan-prune-delay [no] vlan < vid > ip pim-sparse lan-prune-delay Enables the LAN Prune Delay option on the current VLAN. With lan-prune-delay enabled, the router informs downstream neighbors how long it will wait before pruning a flow after receiving a prune request.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the LAN-Prune-Delay Interval Syntax: ip pim-sparse propagation-delay < 250-2000 > vlan < vid > ip pim-sparse propagation-delay < 250-2000 > ip pim-sparse override-interval < 500 - 6000 > vlan < vid > ip pim-sparse override-interval < 500 - 6000 > A router sharing a VLAN with other multicast routers uses these two values to compute the lan-prune-delay setting (above) for how long to wait for a PIM-SM join after receiving a prune packet from do
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Example of Configuring PIM-SM Support in a VLAN Context PIM-SM support must be configured in each VLAN where you want PIM-SM forwarding of multicast traffic. This example illustrates the following perVLAN configuration steps: ■ Enabling PIM-SM on VLAN 120 and allow the default “any” option to select a source IP address for PIM-SM packets forwarded from this VLAN. (Because the VLAN in this example is configured with only one IP address—120-10.10.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Router PIM Context Commands for Configuring PIM SM Operation This section describes the commands used in the Router PIM context to: Note ■ enable or disable SNMP trap status for PIM events (default: disabled) ■ configure candidate Bootstrap Router (BSR) operation ■ configure candidate Rendezvous Point (RP) operation or the (optional) static Rendezvous Point (RP) operation Before configuring BSR, RP, and SNMP trap operation for PIM-SM, it is nec
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the Priority Setting for a BSR-Candidate Router. Syntax: bsr-candidate priority < 0 - 255 > [no] router pim bsr-candidate priority < 0 - 255 > Specifies the priority to apply to the router when a BSR election process occurs in the PIM-SM domain. The candidate with the highest priority becomes the BSR for the domain. If the highest priority is shared by multiple routers, then the candidate having highest IP address becomes the domain’s BSR.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the Bootstrap Router Message Interval. Syntax: bsr-candidate bsm-interval < 5 - 300 > [no] router pim bsr-candidate bsm-interval < 5 - 300 > Specifies the interval in seconds for sending periodic RP-Set messages on all PIM-SM interfaces on a router operating as the elected BSR in a domain. Note: This setting must be smaller than the rp-candidate holdtime settings (range of 30 - 255; default 150) configured in the RPs operating in the domain.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Syntax: [no] rp-candidate source-ip-vlan < vid > [group-prefix < group-addr/mask] [no] router pim rp-candidate source-ip-vlan < vid > [group-prefix < group addr/mask] This command configures C-RP operation as follows: • specifies the VLAN interface from which the RP IP address will be selected for advertising the router as an RP candidate. Note that only one VLAN on the router can be configured for this purpose at any time.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router group-prefix < group-addr/mask >: Specifies the multicast group(s) to advertise as supported by the RP candidate. Use this option when you want to enable the Candidate-RP and simultaneously configure it to support a subset of multicast addresses or ranges of addresses instead of all possible multicast addresses. A group prefix can specify all multicast groups (224.0.0.0 239.255.255.255), a range (subset) of groups, or a single group.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Enabling or Disabling Candidate-RP Operation. Use this command when the router is already configured with a source IP VLAN ID and you want to enable or disable C-RP operation on the router. Syntax: [no] rp-candidate Enables Candidate-RP operation on the router. Requires that the source IP VLAN is currently configured, but disabled (page 4-37).
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing a Candidate-RP’s Election Priority. This priority is significant when multiple Candidate-RPs in a given domain are configured to support one or more of the same multicast groups. Syntax: rp-candidate priority < 0 - 255 > Changes the current priority setting for a candidate-RP. Where multiple candidate-RPs are configured to support the same multicast group(s), the candidate having the highest priority is elected.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Changing the Global Join-Prune Interval on the Router Syntax: router pim join-prune-interval <5 - 65535> Sets the interval in seconds at which periodic PIM-SM join/ prune messages are to be sent on the router’s PIM-SM inter faces. This setting is applied to every PIM-SM interface on the router. (Default: 60 seconds) Note: All routers in a PIM-SM domain should have the same join-prune-interval setting.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Syntax: router pim rp-address < rp-ip-addr > < group-addr/group-mask > [override] [no] router pim rp-address < rp-ip-addr > < group-addr/group-mask> [override] < rp-ip-addr >: Statically specifies the IP address of the interface to use as an RP. Up to four static-RP IP addresses can be configured. (Each address can be entered multiple times for different multicast groups or group ranges.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router Figure 4-7 illustrates the following configuration steps for the Router PIM context: ■ Enabling BSR operation on the router, including specifying a source IP address. ■ Enabling C-RP operation on the router. ■ Replacing the default multicast group range (all) with a smaller range (231.128.24.0/18) and a single group address (230.255.1.1/32). ■ Enabling static-RP with an override on this router for a single group address (231.128.64.
PIM-SM (Sparse Mode) Configuring PIM-SM on the Router ProCurve(pim)# show running Running configuration: . . . router pim bsr-candidate bsr-candidate source-ip-vlan 120 bsr-candidate priority 1 rp-address 120.10.10.2 231.128.64.255 255.255.255.255 rp-candidate rp-candidate source-ip-vlan 120 rp-candidate group-prefix 230.255.1.1 255.255.255.255 rp-candidate group-prefix 231.128.64.0 255.255.192.0 rp-candidate hold-time 150 exit Figure 4-8.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying PIM-SM Data and Configuration Settings Command Page show ip mroute 4-47 [< group-addr > < source-ip-addr >] 4-48 [ interface [< vid >]] 4-50 show ip pim [mroute] [< group-address> < source-address >] 4-52 4-53 [interface] [ vid ] 4-55 4-55 [neighbor] [ ip-address ] 4-57 4-58 [pending] [ ip-address ] 4-59 [rp-pending] [ ip-address ] 4-60 bsr 4-61 rp-set 4-63 [static | learned ] rp-candidate [config] 4-4
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying Multicast Route Data The commands in this section display multicast routing information on pack ets sent from multicast sources to IP multicast groups detected by the routing switch. Listing Basic Route Data for Active Multicast Groups Syntax: show ip mroute Lists the following data for all VLANs actively forwarding routed, multicast traffic. Group Address: The multicast address of the specific multicast group (flow).
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Listing Data for an Active Multicast Group Syntax: show ip mroute [< group-addr > < source-addr >] Lists the following data for the specified flow (multicast group): Group Address: The multicast group IP address for the current group. Source Address: The source IP address < source-ip-addr> for the current group. Source Mask: The subnet mask applied to the multicast source address < source-ip-addr >.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Unicast Routing Protocol: Identifies the IP routing protocol through which the router learned the upstream interface for the current multicast flow. The listed protocol will be either RIP, OSPF, or Static Route. Downstream Interfaces: VLAN: Lists the VID of the VLAN the router is using to send the outbound packets of the current multicast flow to the next-hop router.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Listing All VLANs Having Currently Active PIM Flows Syntax: show ip mroute interface [< vid >] Lists these settings: VLAN: The VID specified in the command. Protocol: PIM-SM or PIM-DM. TTL: The time-to-live threshold for packets forwarded through this VLAN. When configured, the router drops multicast pack ets having a TTL lower than this value.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying PIM-Specific Data The commands in this section display PIM-specific multicast routing informa tion for IP multicast groups detected by the router. Displaying the Current PIM status and Global Configuration Syntax: show ip pim Displays PIM status and global parameters. PIM Status: Shows either enabled or disabled. State Refresh Interval (sec): Applies only to PIM-DM operation. Refer to “Displaying PIM Status” on page 3-28.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying Current PIM Entries Existing In the Multicast Routing Table Syntax: show ip pim mroute Shows PIM-specific information from the IP multicast routing table (IP MRT). When invoked without parameters, lists all PIM entries currently in the router’s IP MRT. Group Address: Lists the multicast group addresses currently active on the router. Source Address: Lists the multicast source address for each Group Address.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying a Specific PIM Entry Stored in the Multicast Routing Table Syntax: show ip pim mroute [< multicast-group-address > < multicast-source-address >] Displays the PIM route entry information for the specified multicast group (flow): Group Address: Lists the specified multicast group address. Source Address: Lists the specified multicast source address. Source Mask: Lists the network mask for the multicast source address.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings DownStream Interfaces: – VLAN: Lists the VID of the destination VLAN on the nexthop multicast router. – Prune Reason: Identifies the reason for pruning the flow to the indicated VLAN: • Prune: A neighbor multicast router has sent a prune request. • Assert: Another multicast router connected to the same VLAN has been elected to provide the path for the specified multicast group traffic.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Listing Currently Configured PIM Interfaces Syntax: show ip pim interface Lists the PIM interfaces (VLANs) currently configured in the router. VLAN: Lists the VID of each VLAN configured on the switch to support PIM-DM. IP Address: Lists the IP addresses of the PIM interfaces (VLANs). Mode: Shows dense or sparse, depending on which PIM protocol is configured on the router.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings ProCurve(config)# show ip pim interface 1 PIM Interface VLAN : 1 IP Address : 10.1.10.1 Mode : sparse Designated Router : 10.1.10.1 Hello Interval (sec) Hello Delay (sec) : 30 : 5 Override Interval (msec) Propagation Delay (msec) Neighbour Timeout : 2500 : 500 : 180 Lan Prune Delay Lan Delay Enabled DR Priority : Yes : No : 1 Figure 4-17. Example Showing a PIM-SM Interface Configured on VLAN 1 Table 4-1.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying PIM Neighbor Data These commands enable listings of either all PIM neighbors the router detects or the data for a specific PIM neighbor. Syntax: show ip pim neighbor Lists PIM neighbor information for all PIM neighbors connected to the router: IP Address: Lists the IP address of a neighbor multicast router. VLAN: Lists the VLAN through which the router connects to the indicated neighbor.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Syntax: show ip pim neighbor [< ip-address >] Lists the same information as show ip pim neighbor (page 3-34) for the specified PIM neighbor. ProCurve(config)# show ip pim neighbor 10.10.10.2 PIM Neighbor IP Address VLAN : 10.10.10.2 : 100 Up Time (sec) : 678 Expire Time (sec) : 93 DR Priority : 1 Figure 4-19.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying Pending Join Requests Use the show ip pim pending and show ip pim rp-pending commands to display the pending join requests received on the switch. Syntax: show ip pim pending [< ip-address >] Displays the joins received on the switch from downstream devices that want to join a specified (*,G) or (S,G) multicast group (flow) address or all multicast groups known on the switch.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Syntax: show ip pim rp-pending [< ip-address >] Displays the joins received on the switch from downstream devices that want to listen to the multicast traffic in all (*,G) or (S,G) multicast groups (flows) that a specified Rendezvous Point (RP) address or all RPs in the domain are responsible for. A join remains in a pending state until traffic is received for the flow.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying BSR Data The router provides BSR information through both IP PIM and the running configuration. Displaying BSR Status and Configuration Syntax: show ip pim bsr Lists the identity, configuration, and time data of the currently elected BSR for the domain, plus the BSR-candidate configuration, the Candidate-RP configuration and the supported multicast groups on the current router.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Listing Non-Default BSR Configuration Settings The show running command includes the current non-default BSR configura tion settings on the router. ProCurve(config)# show running Running configuration: . . . ip routing snmp-server community "public" Unrestricted vlan 1 . . . vlan 120 . Example of Non-Default BSR . Candidate Configuration in the .
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying the Current RP Set The BSR sends periodic RP updates to all Candidate RPs in the domain. These updates include the set of multicast group data configured on and reported by all Candidate-RPs in the domain. This data does not include any static-RP entries configured on any router in the domain.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings ProCurve(config)# show ip pim rp-set learned Status and Counters - PIM-SM Learned RP-Set Information Group Address --------------231.100.128.0 232.240.255.252 237.255.248.1 239.10.10.240 239.10.10.240 Group Mask --------------255.255.240.0 255.255.255.252 255.255.255.255 255.255.255.240 255.255.255.252 RP Address --------------100.10.10.1 100.10.10.1 100.10.10.1 120.10.10.2 120.10.10.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Displaying Candidate-RP Data Displaying the Router’s Candidate-RP Status and Configuration Syntax: show ip pim rp-candidate [ config ] rp-candidate: Lists the current Candidate-RP status and, if the status is enabled for C-RP operation, includes the current C RP configuration on the router.
PIM-SM (Sparse Mode) Displaying PIM-SM Data and Configuration Settings Listing Non-Default C-RP Configuration Settings The show running command includes the current non-default C-RP configura tion settings on the router. ProCurve(config)# show running Running configuration: . . . ip routing snmp-server community "public" Unrestricted vlan 1 . . . vlan 120 . . .
PIM-SM (Sparse Mode) Operating Notes Operating Notes Eliminating Redundancy in Support for a Multicast Group. Configur ing only one router in a domain as an RP for supporting traffic for a specific multicast group eliminates support redundancy for that group. In this case, if that router becomes unavailable then the group will be excluded from the domain. Excluding Multicast Groups.
PIM-SM (Sparse Mode) Event Log Messages Event Log Messages Message Meaning < multicast-addr >/< mask > Inconsistent address and mask. The mask entered for the specified multicast address does not specify sufficient bits to include the nonzero bits in the mask. pkt, src IP < ip-addr > vid < vid- A PIM packet was received that doesn't have a neighbor.
PIM-SM (Sparse Mode) Event Log Messages Message Meaning Illegal operation in BSR state machine An illegal state/event combination has been detected in the BSR state machine. Malformed Candidate-RP adv recvd from < ip-addr > The switch received a malformed C-RP-advertisement. MCAST MAC add for < mac-addr > failed The indicated interface could not join the multicast group for PIM packets.
PIM-SM (Sparse Mode) Event Log Messages Message Meaning Rcvd unkwn addr fmly in pkt from < ip-addr > A PIM packet with an unknown address family was received. Rcvd pkt with bad len from < ip-addr > A PIM packet with an inconsistent length was received from the indicated IP address. Send error(< error-# >) on < packet-type > pkt on VID < vid-# > Send packet failed on the indicated VLAN.
5 IP Routing Features Contents Overview of IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 IP Tables and Caches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 ARP Cache Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 IP Route Table . . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Static Route Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25 Other Sources of Routes in the Routing Table . . . . . . . . . . . . . . . . . . 5-26 Static IP Route Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26 Static Route States Follow VLAN States . . . . . . . . . . . . . . . . . . . . . . . 5-27 Configuring a Static IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Designated Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49 OSPF Area Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 Backbone Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 Normal Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52 Not-So-Stubby-Area (NSSA) . . . . . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Configuring OSPF Authentication on a Virtual Link . . . . . . . . . . 5-94 OSPF Passive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-97 Displaying OSPF Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-98 Displaying General OSPF Configuration Information . . . . . . . . . 5-99 Displaying OSPF Area Information . . . . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-131 Configuring an IP Helper Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132 Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132 Hop Count in DHCP Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132 Disabling the Hop Count in DHCP Requests . . . . . . . . . . . . . . .
IP Routing Features Overview of IP Routing Overview of IP Routing The switches covered in this guide offer the following IP routing features, as noted: License Requirements ■ IP Static Routes – up to 256 static routes ■ RIP (Router Information Protocol) – supports RIP Version 1, Version 1 compatible with Version 2 (default), and Version 2 ■ OSPF (Open Shortest Path First) – the standard routing protocol for handling larger routed networks ■ IRDP (ICMP Router Discovery Protocol) – advertises the IP
IP Routing Features Overview of IP Routing IP Interfaces On the routing switches, IP addresses are associated with individual VLANs. By default, there is a single VLAN (Default_VLAN) on the routing switch. In that configuration, a single IP address serves as the management access address for the entire device. If routing is enabled on the routing switch, the IP address on the single VLAN also acts as the routing interface. Each IP address on a routing switch must be in a different subnet.
IP Routing Features Overview of IP Routing ARP Cache Table The ARP cache contains entries that map IP addresses to MAC addresses. Generally, the entries are for devices that are directly attached to the routing switch. An exception is an ARP entry for an interface-based static IP route that goes to a destination that is one or more router hops away.
IP Routing Features Overview of IP Routing Administrative Distance. The IP route table contains the best path to a destination. When the software receives paths from more than one of the sources listed above, the software compares the administrative distance of each path and selects the path with the lowest administrative distance. The administrative distance is a protocol-independent value from 1 – 255.
IP Routing Features Overview of IP Routing Note You cannot add static entries to the IP forwarding cache. IP Route Exchange Protocols The switch supports the following IP route exchange protocols: ■ Routing Information Protocol (RIP) ■ Open Shortest Path First (OSPF) These protocols provide routes to the IP route table. You can use one or more of these protocols, in any combination. The protocols are disabled by default.
IP Routing Features Overview of IP Routing Parameter Description Default See page Proxy ARP An IP mechanism a router can use to answer an ARP request on behalf of a host, by replying with the router’s own MAC address instead of the host’s. Disabled 5-19 Time to Live (TTL) The maximum number of routers (hops) through which a packet can pass before being discarded. Each router decreases a packet’s TTL by 1 before forwarding the packet.
IP Routing Features Overview of IP Routing ARP Age Timer The ARP age is the amount of time the switch keeps a MAC address learned through ARP in the ARP cache. The switch resets the timer to zero each time the ARP entry is refreshed and removes the entry if the timer reaches the ARP age. You can increase the ARP age timeout maximum to 24 hours or more with this command: Syntax: [no] ip arp-age <[1...1440] | infinite> Allows the ARP age to be set from 1 to 1440 minutes (24 hours).
IP Routing Features Overview of IP Routing ProCurve(config)# show ip Internet (IP) Service IP Routing : Disabled Default Gateway Default TTL Arp Age Domain Suffix DNS server : 15.255.120.1 : 64 : 1000 : : VLAN | IP Config IP Address Subnet Mask Proxy ARP -------------------- + ---------- --------------- --------------- -------DEFAULT_VLAN | Manual 15.255.111.13 255.255.248.0 No Figure 5-2.
IP Routing Features Overview of IP Routing You can set or display the arp-age value using the menu interface (Menu > Switch Configuration > IP Config). ProCurve 12-June-2007 14:45:31 ===========================- TELNET - MANAGER MODE ====================== Switch Configuration - Internet (IP) Service IP Routing : Disabled Default Gateway : 15.255.120.1 Default TTL : 64 Arp Age : 1000 IP Config [Manual] : Manual IP Address : 15.255.111.11 Subnet Mask : 255.255.248.
IP Routing Features Configuring IP Parameters for Routing Switches Configuring IP Parameters for Routing Switches The following sections describe how to configure IP parameters. Some param eters can be configured globally while others can be configured on individual VLAN interfaces. Some parameters can be configured globally and overridden for individual VLAN interfaces. Note This section describes how to configure IP parameters for routing switches.
IP Routing Features Configuring IP Parameters for Routing Switches on the routing switch and OSPF is restarted with a reboot. (User-Configured loopback interfaces are always higher priority than other configured inter faces.) However, you prefer, you can explicitly set the router ID to any valid IP address, as long as the IP address is not in use on another device in the network. Note To display the router ID, enter the show ip ospf CLI command at any Manager EXEC CLI level.
IP Routing Features Configuring IP Parameters for Routing Switches For more information on the router ID, refer to “IP Global Parameters for Routing Switches” on page 5-10 and “Changing the Router ID” on page 5-15. To change the router ID, enter a command such as the following: ProCurve(config)# ip router-id 209.157.22.26 Syntax: Syntax: ip router-id < ip-addr > The < ip-addr > can be any valid, unique IP address.
IP Routing Features Configuring IP Parameters for Routing Switches routing switch must encapsulate the packet and address it to the MAC address of a locally attached device, the next-hop router toward the IP packet’s destination. To obtain the MAC address required for forwarding a datagram, the routing switch does the following: ■ First, the routing switch looks in the ARP cache (not the static ARP table) for an entry that lists the MAC address for the IP address.
IP Routing Features Configuring IP Parameters for Routing Switches Note If the routing switch receives an ARP request packet that it is unable to deliver to the final destination because of the ARP time-out and no ARP response is received (the routing switch knows of no route to the destination address), the routing switch sends an ICMP Host Unreachable message to the source.
IP Routing Features Configuring IP Parameters for Routing Switches Notes Internet Control Message Protocol (ICMP) redirects will be disabled on interfaces on which local proxy ARP is enabled. CLI Commands To enable local proxy ARP, you must first enter vlan context, for example: ProCurve(config) vlan 1 Then enter the command to enable local proxy ARP: ProCurve(vlan-1)ip local-proxy-arp Syntax: [no] ip local-proxy-arp Enables the local proxy ARP option.
IP Routing Features Configuring IP Parameters for Routing Switches Configuring Forwarding Parameters The following configurable parameters control the forwarding behavior of ProCurve routing switches: ■ Time-To-Live (TTL) threshold ■ Forwarding of directed broadcasts All these parameters are global and thus affect all IP interfaces configured on the routing switch. To configure these parameters, use the procedures in the following sections.
IP Routing Features Configuring IP Parameters for Routing Switches To disable the directed broadcasts, enter the following CLI command: ProCurve(config)# no ip directed-broadcast Configuring ICMP You can configure the following ICMP limits: ■ Burst-Normal – The maximum number of ICMP replies to send per second. ■ Reply Limit – You can enable or disable ICMP reply rate limiting.
IP Routing Features Configuring IP Parameters for Routing Switches ProCurve(config)# ip icmp echo broadcast-request Disabling ICMP Destination Unreachable Messages By default, when a ProCurve device receives an IP packet that the device cannot deliver, the device sends an ICMP Unreachable message back to the host that sent the packet.
IP Routing Features Configuring Static IP Routes Disabling ICMP Redirects You can disable ICMP redirects on the ProCurve routing switch only on a global basis, for all the routing switch interfaces.
IP Routing Features Configuring Static IP Routes Other Sources of Routes in the Routing Table The IP route table can also receive routes from these other sources: ■ Directly-connected networks: One route is created per IP interface. When you add an IP interface, the routing switch automatically creates a route for the network the interface is in. ■ RIP: If RIP is enabled, the routing switch can learn about routes from the advertisements other RIP routers send to the routing switch.
IP Routing Features Configuring Static IP Routes Static Route States Follow VLAN States IP static routes remain in the IP route table only so long as the IP interface to the next-hop router is up. If the next-hop interface goes down, the software removes the static route from the IP route table. If the next-hop interface comes up again, the software adds the route back to the route table. This feature allows the routing switch to adjust to changes in network top ology.
IP Routing Features Configuring Static IP Routes Syntax: [no] ip route < dest-ip-addr >/< mask-length > | reject | blackhole > [metric < metric>] [ distance<1-255> ] [tag-value ] Allows the addition and deletion of static routing table entries. A route entry is identified by a destination (IP address/Mask Length) and next-hop pair. The next-hop can be either a gateway IP address, a VLAN, or the keyword “reject” or “black hole”.
IP Routing Features Configuring Static IP Routes distance Specifies the administrative distance to asso ciate with a static route. If not specified, this value is set to a default of 1. For more on this topic, refer to “Administrative Distance” on page 5-9. (Range: 1 - 255) tag Specifies a unique integer value for a given ECMP set (destination, metric, distance). The no form of the command deletes the specified route for the specified destination next-hop pair.
IP Routing Features Configuring Static IP Routes ProCurve(config)# ip route 127.10.144.21/24 10.10.10.2 metric 12 distance 10 ProCurve(config)# ip route 127.10.144.21/24 10.10.10.3 metric 12 distance 10 Configures an ECMP set with 2 different gateways to the same destination address. Figure 5-8. Example of an ECMP Set With the Same Destination But Different Next-hop Routers.
IP Routing Features Configuring RIP Configuring RIP This section describes how to configure RIP using the CLI interface. To display RIP configuration information and statistics, see “Displaying RIP Information” on page 5-37. Overview of RIP Routing Information Protocol (RIP) is an IP route exchange protocol that uses a distance vector (a number representing distance) to measure the cost of a given route.
IP Routing Features Configuring RIP Note ICMP Host Unreachable Message for Undeliverable ARPs. If the routing switch receives an ARP request packet that it is unable to deliver to the final destination because of the ARP timeout and no ARP response is received (the routing switch knows of no route to the destination address), the routing switch sends an ICMP Host Unreachable message to the source.
IP Routing Features Configuring RIP Parameter Description Default metric A numeric cost the routing switch adds to RIP routes 1 learned on the interface. This parameter applies only to RIP routes. IP address The routes that a routing switch learns or advertises The routing switch can be controlled.
IP Routing Features Configuring RIP Note IP routing must be enabled prior to enabling RIP. The first command in the preceding sequence enables IP routing. Enabling IP RIP on a VLAN To enable RIP on all IP addresses in a VLAN, use ip rip in the VLAN context. when the command is entered without specifying any IP address, it is enabled in all configured IP addresses of the VLAN.
IP Routing Features Configuring RIP Note RIP considers a route with a metric of 16 to be unreachable. Use this metric only if you do not want the route to be used. In fact, you can prevent the switch from using a specific interface for routes learned though that interface by setting its metric to 16.
IP Routing Features Configuring RIP Note Do not enable redistribution until you have configured the redistribution filters. Otherwise, the network might get overloaded with routes that you did not intend to redistribute. Example: To configure the switch to filter out redistribution of static, connected, or OSPF routes on network 10.0.0.0, enter the following commands: ProCurve(config)# router rip ProCurve(rip)# restrict 10.0.0.0 255.0.0.
IP Routing Features Configuring RIP To enable redistribution of connected and static IP routes into RIP, enter the following commands.
IP Routing Features Configuring RIP Displaying RIP Information All RIP configuration and status information is shown by the CLI command show ip rip and options off that command. The following RIP information can be displayed: RIP Information Type Page General Information 5-37 Interface Information 5-39 Peer Information 5-40 Redistribute Information 5-42 Restrict Information 5-42 Displaying General RIP Information To display general RIP information, enter show ip rip at any context level.
IP Routing Features Configuring RIP The display is a summary of Global RIP information, information about interfaces with RIP enabled, and information about RIP peers. The following fields are displayed: ■ RIP protocol – Status of the RIP protocol on the router. RIP must be enabled here and on the VLAN interface for RIP to be active. The default is disabled. ■ Auto-summary – Status of Auto-summary for all interfaces running RIP.
IP Routing Features Configuring RIP Displaying RIP Interface Information To display RIP interface information, enter the show ip rip interface command at any context level. The resulting display will appear similar to the following: Figure 5-11.Example of Show IP RIP Interface Output See “RIP Interface Information” on the previous page for definitions of these fields.
IP Routing Features Configuring RIP The information in this display includes the following fields, which are defined under ““RIP Interface Information” on page 5-38: IP Address, Status, Send mode, Recv mode, Metric, and Auth. The information also includes the following fields: ■ Bad packets received – The number of packets that were received on this interface and were not processed for any reason.
IP Routing Features Configuring RIP The resulting display will appear similar to the following: ProCurve# show ip rip peer RIP peer information IP Address --------------100.1.0.100 100.2.0.100 100.3.0.100 100.10.0.100 Bad routes ----------0 0 0 0 Last update timeticks -------------------1 0 2 1 Figure 5-14. Example of Show IP RIP Peer Output This display lists all neighboring routers from which the routing switch has received RIP updates.
IP Routing Features Configuring RIP Displaying RIP Redistribution Information To display RIP redistribution information, enter the show ip rip redistribute command at any context level: ProCurve# show ip rip redistribute RIP redistributing Route type Status --------- ----connected enabled static disabled ospf disabled Figure 5-16.
IP Routing Features Configuring OSPF Configuring OSPF Feature Default Page Enable IP Routing and Global OSPF Routing disabled 5-62 Changing the RFC 1583 OSPF Compliance Setting enabled 5-63 Assign the Routing Switch to OSPF Areas n/a 5-65 Assign VLANs and/or Subnets to Each Area n/a 5-69 disabled 5-73 External Route Redistribution Configure Ranges on an ABR To Reduce Advertising n/a Use Administrative Distance To Influence Route Choices Generate OSPF Traps Cost Per Interface 5-76 5-79
IP Routing Features Configuring OSPF Terminology Area Border Router (ABR): An OSPF-enabled router having interfaces on two or more OSPF areas. (Refer to “Area Border Routers (ABRs)” on page 5-47.) Autonomous System (AS): A single interior gateway protocol (IGP) domain such as an OSPF or RIP domain. Autonomous System Boundary Router (ASBR): An OSPF-enabled router having interfaces in multiple IGP domains, such as an ASBR with member ship in both a normal area of an OSPF domain and a RIP domain.
IP Routing Features Configuring OSPF Link-State Advertisement (LSA): A message sent by a router to its neigh bors to advertise the existence of a route to a destination known by the originating router. Refer to Table 5-5 on page 5-46. Normal Area: Exists within an OSPF domain and connects to the backbone area through one or more ABRs (either physically or through a virtual link).
IP Routing Features Configuring OSPF Overview of OSPF OSPF is a link-state routing protocol applied to routers grouped into OSPF areas identified by the routing configuration on each routing switch. The protocol uses link-state advertisements (LSAs) transmitted by each router to update neighboring routers regarding its interfaces and the routes available through those interfaces. Each routing switch in an area also maintains a Link State Database (LSDB) that describes the area topology.
IP Routing Features Configuring OSPF OSPF Router Types Interior Routers This type of OSPF router belongs to only one area. Interior routers flood type 1 LSAs to all routers in the same area, and maintain identical link state databases (LSDBs). In figure 5-18, below, routers R1, R3, R4, and R6 are all interior routers because all of their links are to other routers in the same area. Area 0 (Backbone) Interior Router R1 R5 R2 a2 Are R3 Area 1 R4 R6 Interior Routers Figure 5-18.
IP Routing Features Configuring OSPF Area Border Router (ABR) Area 0 (Backbone) Area Border Router (ABR) R1 R5 R2 R3 Area 1 a2 Are R4 R6 Figure 5-19. Example of Deploying ABRs To Connect Areas to the Backbone Autonomous System Boundary Router (ASBR) This type of OSPF router runs multiple Interior Gateway protocols and serves as a gateway to other autonomous systems operating with interior gateway protocols.
IP Routing Features Configuring OSPF Priority is configurable by using the vlan < vid > ip ospf priority < 0-255 > command at the interface level. You can use this parameter to help bias one router as the DR. (For more on this command, refer to “Priority Per-Interface” on page 5-83.) If two neighbors share the same priority, the router with the highest router ID is designated as the DR. The router with the next highest router ID is designated as the BDR. For example, in figure 5-20, the DR and BDR for 10.
IP Routing Features Configuring OSPF Notes By default, the router ID is typically the lowest-numbered IP address or the lowest-numbered (user-configured) loopback interface configured on the device. For more information or to change the router ID, see “Changing the Router ID” on page 5-15. If multiple networks exist in the same OSPF area, the recommended approach is to ensure that each network uses a different router as its DR.
IP Routing Features Configuring OSPF All areas in an AS must connect with the backbone through one or more area border routers (ABRs). If a normal area is not directly connected to the backbone area, it must be configured with a virtual link to an ABR that is directly connected to the backbone. The remaining area types do not allow virtual link connections to the backbone area.
IP Routing Features Configuring OSPF Not-So-Stubby-Area (NSSA) Beginning with software release K.12.xx, this area is available and connects to the backbone area through one or more ABRs.
IP Routing Features Configuring OSPF Stub Area This area connects to the AS backbone through one or more ABRs. It does not allow an internal ASBR, and does not allow external (type 5) LSAs. A stub area supports these actions: ■ Advertise the area’s summary routes to the backbone area. ■ Advertise summary routes from other areas.
IP Routing Features Configuring OSPF ■ injected into the backbone area and then propagated to any other OSPF areas (except stub areas) within the local OSPF Autonomous System (AS). If the AS includes an NSSA, there are two additional options: • If the NSSA includes an ASBR, you can suppress advertising some or all of its summarized external routes into the backbone area. • Replace all type-3 summary LSAs and the default external route from the backbone area with the default summary route (0.0.0.0/0).
IP Routing Features Configuring OSPF Replacing Type-3 Summary LSAs and Type-7 Default External LSAs with a Type-3 Default Route LSA By default, a routing switch operating as an ABR for a stub area or NSSA injects non-default, summary routes (LSA type 3) into the stub areas and NSSAs. For NSSAs, the routing switch also injects a type-7 default external route. You can further reduce LSA traffic into these areas by using no-summary.
IP Routing Features Configuring OSPF Equal Cost Multi-Path Routing The Equal Cost Multi-Path (ECMP) feature allows OSPF to add routes with multiple next-hop addresses and with equal costs to a given destination in the Forwarding Information Base (FIB) on the routing switch. For example, if you display the IP Route table by entering the show ip route command, multiple next-hop routers are listed for the same destination network (21.0.9.0/24) as shown in Figure 5-22.
IP Routing Features Configuring OSPF Also, according to the distributed algorithm used in the selection of ECMP next-hop routes: ■ Intra-area routes are preferred to inter-area routes. ■ Inter-area routes are preferred to external routes through a neighboring autonomous system. In addition, ECMP ensures that all traffic forwarded to a given host address follows the same path, which is selected from the possible next-hop routes.
IP Routing Features Configuring OSPF However, the forwarding software distributes traffic across the three possible next-hop routes in such a way that all traffic for a specific host is sent to the same next-hop router. As shown in Figure 5-24, one possible distribution of traffic to host devices is as follows: ■ Traffic to host 10.10.0.1 passes through next-hop router 12.0.9.2. ■ Traffic to host 10.10.0.2 passes through next-hop router 13.0.9.3. ■ Traffic to host 10.10.0.
IP Routing Features Configuring OSPF General Configuration Steps for OSPF To begin using OSPF on the routing switch, perform the steps outlined below: 1. In the global config context, use ip routing to enable routing (page 5-62). 2. Execute router ospf to place the routing switch in the ospf context and to enable OSPF routing (page 5-62). 3. Change the OSPF RFC 1583 compliance, if needed. (Refer to “3. Changing the RFC 1583 OSPF Compliance Setting” on page 5-63.) 4.
IP Routing Features Configuring OSPF 12. Optional: Configure OSPF interface authentication. 13. Configure virtual links for any areas not directly connected to the back bone. Configuration Rules ■ If the switch is to operate as an ASBR, you must enable redistribution (step 7 on page 5-59). When you do that, ASBR capability is automatically enabled. For this reason, you should first configure redistribution filters on the ASBR. Otherwise, all possible external routes will be allowed to flood the domain.
IP Routing Features Configuring OSPF Parameter Default restrict Disabled rfc-1583-compatibility Enabled metric-type type2 trap < ospf-trap > Note Page Enabled Set global level parameters in the ospf context of the CLI. To access this context level, ensure that routing is enabled, then execute router ospf at the global CONFIG level. For example: ProCurve (config)# router ospf ProCurve (ospf)# Table 5-7.
IP Routing Features Configuring OSPF Configuring OSPF on the Routing Switch 1. Enable IP Routing Syntax: [no] ip routing Executed at the global configuration level to enable IP routing on the routing switch. Default: Disabled The no form of the command disables IP routing. (Global OSPF and RIP routing must be disabled before you disable IP routing.) ProCurve(config)# ip routing 2.
IP Routing Features Configuring OSPF 3. Changing the RFC 1583 OSPF Compliance Setting In OSPF domains supporting multiple external routes from different areas to the same external destination, multiple AS-external-LSAs advertising the same destination are likely to occur. This can cause routing loops and the network problems that loops typically generate.
IP Routing Features Configuring OSPF ProCurve(config)# router ospf ProCurve(ospf)# no rfc1583-compatibility ProCurve_8212(ospf)# show ip ospf general Changes external route preference setting and displays new setting. OSPF General Status OSPF protocol Router ID RFC 1583 compatibility : enabled : 10.10.51.
IP Routing Features Configuring OSPF 4. Assign the Routing Switch to OSPF Areas After you globally enable OSPF on the routing switch (in the previous step), use this command to assign one or more OSPF areas within your autonomous system (AS). A routing switch can belong to one area or to multiple areas. (Participation in a given, assigned area requires configuring one or more VLANs or subnets and assigning each to the desired area. Refer to page 5-69.
IP Routing Features Configuring OSPF Configuring an OSPF Backbone or Normal Area. Syntax: area < ospf-area-id | backbone > [normal] no area < ospf-area-id | backbone > After using router ospf to globally enable OSPF and enter the global OSPF context, execute this command to assign the routing switch to a backbone or other normal area. The no form of the command removes the routing switch from the specified area. Default: No areas.
IP Routing Features Configuring OSPF Configuring a Stub or NSSA Area. Syntax: area < ospf-area-id > stub < 0-16777215 > [no-summary] area < ospf-area-id > < nssa > < 0-16777215 > [no-summary] [metric-type < type1 | type2 >] no area < ospf-area-id > After using router ospf to globally enable OSPF and enter the global OSPF context, execute this command to assign the routing switch to a stub area or NSSA. (Does not apply to backbone and normal OSPF area ABRs.
IP Routing Features Configuring OSPF [no-summary]: Where the routing switch is an ABR for a stub area or an NSSA, this option reduces the amount of LSA traffic entering the area from the backbone by replacing the injection of type-3 summary routes with injection of a type-3 default summary route. For NSSAs, this command also disables injection of the type-7 default external route from the backbone into the area (included in the metric-type operation described below).
IP Routing Features Configuring OSPF The following examples of configuring a stub area and an NSSA on a routing switch use an (arbitrary) cost of “10”. ProCurve(ospf)# area 2 stub 10 Assigns a stub area with a cost of 10. ProCurve(ospf)# area 3 nssa 10 Assigns an NSSA with a cost of 10 and, by default, uses a Type2 default cost metric for Type-7 (external) route LSAs received from the backbone.
IP Routing Features Configuring OSPF Syntax: vlan < vid ># ip ospf [ ip-addr | all ] area < ospf-area-id > Executed in a specific VLAN context to assign the VLAN or individual subnets in the VLAN to the specified area. Requires that the area is already configured on the routing switch (page 5-65). When executed without specifying an IP address or using the all keyword, this command assigns all configured networks in the VLAN to the specified OSPF area.
IP Routing Features Configuring OSPF The operator could use the following commands to configure the above assignments: ProCurve(ospf)# vlan 10 ProCurve(vlan-10)# ip ospf 10.10.10.1 area 5 ProCurve(vlan-10)# ip ospf 10.10.11.1 area 5 ProCurve(vlan-10)# ip ospf 10.10.12.1 area 6 6. Optional: Assigning Loopback Addresses to an Area After you define the OSPF areas to which the switch belongs, you can assign a user-defined loopback address to an OSPF area.
IP Routing Features Configuring OSPF Syntax: interface loopback <0-7># ip ospf < lo-ip-address > cost < number > Executed in a specific loopback context to modify the cost used to advertise the loopback address (and subnet) to the area border router (ABR). Requires that the specified loopback interface is already configured with an IP address on the switch. loopback interface <0-7>: Defines the loopback context for executing the cost assignment.
IP Routing Features Configuring OSPF ProCurve(config)# interface loopback 1 ProCurve(lo-1)# ip address 14.2.3.4 ProCurve(lo-1)# ip address 15.2.3.4 ProCurve(lo-1)# exit ProCurve(config)# interface loopback 2 ProCurve(lo-2)# ip address 13.3.4.5 ProCurve(lo-2)# ip ospf 15.2.3.4 area 0.0.0.111 ProCurve(lo-2)# exit Assigns the IP address of loopback interface 2 to OSPF area 111. Figure 5-27.
IP Routing Features Configuring OSPF connected, and OSPF routes into RIP routes.) The steps for configuring external route redistribution to support ASBR operation include the following: Note 1. Configure redistribution filters to exclude external routes that you do not want redistributed in your OSPF domain. 2. Enable route redistribution. 3. Modify the default metric for redistribution (optional). 4. Modify the redistribution metric type (optional). 5.
IP Routing Features Configuring OSPF Note Do not enable redistribution until you have configured the redistribution “restrict” filters. Otherwise, the network might get overloaded with routes that you did not intend to redistribute. Syntax: [no] router ospf redistribute < connected | static | rip > Executed on an ASBR to globally enable redistribution of the specified route type to the OSPF domain through the area in which the ASBR resides. static: Redistribute from manually configured routes.
IP Routing Features Configuring OSPF 4. Modifying the Redistribution Metric Type. The redistribution metric type is used by default for all routes imported into OSPF. Type 1 metrics are the same “units” as internal OSPF metrics and can be compared directly. Type 2 metrics are not directly comparable, and are treated as larger than the largest internal OSPF metric. Syntax: router ospf metric-type < type1 | type2 > Globally reconfigures the redistribution metric type on an ASBR.
IP Routing Features Configuring OSPF Syntax: area < ospf-area-id > range < ip-addr/mask-length > [no-advertise] [ type < summary | nssa >] Use this command on a routing switch intended to operate as an ABR for the specified area to do either of the following: ■ Simultaneously create the area and corresponding range setting for routes to summarize or block. ■ For an existing area, specify a range setting for routes to summarize or block.
IP Routing Features Configuring OSPF nssa: Specifies external routes (type-7 LSAs) in the configured range of route advertisements. If no-advertise (above) is used in the command, then the ABR prevents the selected external routes from being summarized in a type-5 LSA and advertised to the backbone. (Configure this option where an ABR for an NSSA advertises external routes that you do not want propagated to the backbone.
IP Routing Features Configuring OSPF ProCurve(config)# area 7 range 192.51.0.0/16 type nssa Defines the range of external routes in the Area 7 NSSA to advertise to the backbone. ProCurve(config)# area 7 range 192.51.0.0/16 no-advertise type nssa Defines the range of external routes in the Area 7 NSSA to block from advertising to the backbone. Figure 5-31. Example of Allowing or Blocking a Range of External Route Advertisements to the Backbone 9.
IP Routing Features Configuring OSPF 10: Optional: Change OSPF Trap Generation Choices OSPF traps (defined by RFC 1850) are supported on the routing switches covered by this guide. OSPF trap generation is disabled by default, but you can use the following command to enable generation of any or all of the supported OSPF traps. Syntax: [no] trap < trap-name | all > Used in the OSPF configuration context to enable or disable OSPF traps. The no form disables the specified trap.
IP Routing Features Configuring OSPF For example, if you wanted to monitor the neighbor-state-change and inter face-receive-bad-packet traps, you would use the following commands to configure the routing switch to enable the desired trap. The show command verifies the resulting OSPF trap configuration.
IP Routing Features Configuring OSPF Cost Per-Interface. Syntax: ip ospf [ ip-address | all ] cost < 1 - 65535 > Used in the VLAN context to indicate the overhead required to send a packet across an interface. You can modify the cost to differentiate between 100 Mbps and 1000 Mbps (1 Gbps) links. Allows different costs for different subnets in the VLAN. ip ospf cost < 1 - 65535 >: Assigns the specified cost to all networks configured on the VLAN.
IP Routing Features Configuring OSPF Hello Interval Per Interface. Syntax: ip ospf [ ip-address | all ] hello-interval < 1 - 65535 > Used in the VLAN context to indicate the length of time between the transmission of hello packets from the routing switch to adjacent neighbors. The value can be from 1 – 65535 seconds. The default is 10 seconds.. Allows different settings for different subnet interfaces in the VLAN.
IP Routing Features Configuring OSPF Retransmit Interval Per-Interface. Syntax: ip ospf [ ip-address | all ] retransmit-interval < 0 - 3600 > Used in the VLAN context to enable changing the retransmission interval for link-state advertisements (LSAs) on an interface. The default is 5 seconds. Allows different settings for different subnet interfaces in the VLAN. ip ospf priority < 1 - 255 >: Assigns the specified retransmit interval to all networks configured on the VLAN.
IP Routing Features Configuring OSPF Examples of Changing Per-Interface Settings. Suppose that VLAN 30 is multinetted, with two subnets in area 1 and one subnet in area 5: vlan 30 ip ospf 10.10.30.1 area 0.0.0.1 ip ospf 10.10.31.1 area 0.0.0.1 ip ospf 10.10.32.1 area 0.0.0.5 If you wanted to quickly reconfigure per-interface OSPF settings for VLAN 30, such as those listed below, you could use the commands shown in Figure 5-33.
IP Routing Features Configuring OSPF 12. Optional: Configuring OSPF Interface Authentication OSPF supports two methods of authentication for each VLAN or subnet— simple password and MD5. In addition, the value can be disabled, meaning no authentication is performed. Only one method of authentication can be active on a VLAN or subnet at a time, and if one method is configured on an interface, then configuring the alternative method on the same interface automatically overwrites the first method used.
IP Routing Features Configuring OSPF OSPF MD5 Authentication. Syntax: ip ospf md5-auth-key-chain < chain-name-string > no ip ospf [ ip-address ] authentication Used in the VLAN interface context to configure MD5 authentication for all interfaces in the VLAN or for a specific subnet. The MD5 authentication takes effect immediately, and all OSPF packets transmitted on the interface contain the designated key. All OSPF packets received on the interface are checked for the key.
IP Routing Features Configuring OSPF 13. Configuring an ABR To Use a Virtual Link to the Backbone All ABRs (area border routers) must have either a direct, physical or indirect, virtual link to the OSPF backbone area (0.0.0.0 or 0). If an ABR does not have a physical link to the area backbone, the ABR can use a virtual link to provide a logical connection to another ABR having a direct physical connection to the area backbone.
IP Routing Features Configuring OSPF Configuring a Virtual Link Syntax: ip ospf area < area-id > virtual-link < ip-address> Used on a pair of ABRs at opposite ends of a virtual link in the same area to configure the virtual link connection. < area-id >: This must be the same for both ABRs in the link, and is the area number of the virtual link transit area in either decimal or dotted decimal format.
IP Routing Features Configuring OSPF To configure the virtual link on routing switch “A”, enter the following command specifying the area 1 interface on routing switch “C”: ProCurve(ospf)# area 1 virtual-link 209.157.22.1 To configure the virtual link on routing switch “C”, enter the following command specifying the area 1 interface on routing switch “A”: ProCurve(ospf)# area 1 virtual-link 10.0.0.
IP Routing Features Configuring OSPF Dead Interval on a Virtual Link. Syntax: area < area-id > virtual link < ip-address > dead-interval < 1 - 65535 > Used in the router OSPF context on both ABRs in a virtual link to change the number of seconds that a neighbor router waits for a hello packet from the specified interface before declaring the interface “down”. This should be some multiple of the Hello interval. The dead-interval setting must be the same on both ABRs on a given virtual link.
IP Routing Features Configuring OSPF Retransmit Interval on a Virtual Link. Syntax: area < area-id > virtual link < ip-address > retransmit-interval < 1 - 3600 > Used in the router OSPF context on both ABRs in a virtual link to change the number of seconds between link-state advertisement (LSA) retransmissions on the virtual link. The default is 5 seconds. The retransmit-interval setting must be the same on both ABRs on a given virtual link.
IP Routing Features Configuring OSPF Example. To change the hello-interval on the virtual link configured for the network in figure 5-34 on page 5-89 to 60 seconds: ■ On routing switch “A” (IP address 10.0.0.1) you would use the following command to reconfigure the current hello-interval to 60 seconds: ProCurve(ospf)# area 1 virtual-link 209.157.22.1 hello-interval 60 ■ On routing switch “C” (IP address 209.157.22.
IP Routing Features Configuring OSPF OSPF Password Authentication on a Virtual Link. Syntax: area < area-id > virtual-link < ip-addr > authentication-key < octet-string > no area 1 virtual-link < ip-address > authentication Used to configure password authentication in the router OSPF context on both ABRs in a virtual link . The password takes effect immediately, and all OSPF packets transmitted on the link contain this password.
IP Routing Features Configuring OSPF OSPF MD5 Authentication on a Virtual Link. Syntax: ip ospf md5-auth-key-chain < chain-name-string > no ip ospf [ ip-address ] authentication Used to configure MD5 authentication in the router OSPF context on both ABRs in a virtual link . The MD5 authentication takes effect immediately, and all OSPF packets transmitted on the link contain the designated key. Every OSPF packet received on the interface for the virtual link on each ABR is checked for the key.
IP Routing Features Configuring OSPF OSPF Passive OSPF sends link-state advertisements (LSAs) to all other routers in the same Autonomous System (AS). To limit the flooding of LSAs throughout the AS you can configure OSPF to be passive. OSPF does not run in the AS, but it does advertise the interface as a stub link into OSPF. Routing updates are accepted by a passive interface, but not sent out. There is a limit of 512 total active and passive interfaces, but only a total of 128 can be active interfaces.
IP Routing Features Configuring OSPF ProCurve(config) show ip ospf interface vlan 4 OSPF configuration and statistics for VLAN 4 OSPF Interface Status for 10.10.10.1 IP Address: AreaID State Cost Type : 10.10.10.1 : 0.0.0.2 Status : enabled Passive : Yes : DOWN : 1 : BCAST Auth-type : none Chain : Priority : 1 Transit Delay : 1 Hello Interval : 10 Designated Router: Backup Desig. Rtr: Retrans Interval Rtr Dead Interval Events Passive : : : : 5 40 0 yes Figure 5-36.
IP Routing Features Configuring OSPF Displaying General OSPF Configuration Information To display general OSPF configuration information, enter show ip ospf general at any CLI level: ProCurve# show ip ospf general OSPF General Status OSPF protocol Router ID RFC 1583 compatibility : enabled : 10.0.8.
IP Routing Features Configuring OSPF Field Content Inter-area distance the administrative distance for routes between areas within the same OSPF domain AS-external the administrative distance for routes between the OSPF domain and other, Exterior Gateway Protocol domains Default import metric the default metric that will be used for any routes redistributed into OSPF by this routing switch Default import metric type the metric type (type 1 or type 2) that will be used for any routes redistributed
IP Routing Features Configuring OSPF The [ospf-area-id] parameter shows information for the specified area. If no area is specified, information for all the OSPF areas configured is displayed. The OSPF area display shows the following information: Table 5-10. CLI Display of OSPF Area Information Field Content Area ID The identifier for this area. Type The area type, which can be either “normal” or “stub”.
IP Routing Features Configuring OSPF Syntax: show ip ospf external-link-state The OSPF external link state display shows the following information: Table 5-11. CLI Display of OSPF External Link State Information Field Content Link State ID LSA ID for this LSA. Normally, the destination of the external route, but may have some “host” bits set. Router ID Router ID of the router that originated this external LSA. Age Current age (in seconds) of this LSA.
IP Routing Features Configuring OSPF ProCurve# show ip ospf external-link-state advertise OSPF External LSAs Advertisements ----------------------------------------------------------------------000302050a0307000a00082580000005d99f0024ffffff008000000a0000000000000000 000302050a0308000a00082580000005cea90024ffffff008000000a0000000000000000 000302050a0309000a00082580000005c3b30024ffffff008000000a0000000000000000 000302050a030a000a00082580000005b8bd0024ffffff008000000a0000000000000000 000002050a0321000a0008248
IP Routing Features Configuring OSPF Field Content State The current state of the interface.
IP Routing Features Configuring OSPF Displaying OSPF Interface Information for a Specific VLAN or IP Address To display OSPF interface information for a specific VLAN or IP address, enter show ip ospf interface < ip-addr > at any CLI level. For example: ProCurve(ospf)# sho ip ospf int 10.10.50.1 OSPF Interface Status for 10.3.1836 IP Address Area ID State Cost Type : 10.3.18.36 : 10.3.16.0 : BDR : 1 : BCAST Transit Delay Hello Interval Designated Router Backup Desig.
IP Routing Features Configuring OSPF Table 5-13. CLI Display of OSPF Interface Information – VLAN or IP Address Field Content Type Will always be BCAST for interfaces on this routing switch. Point-to-point or NBMA (frame relay or ATM) type interfaces are not supported on the switches covered in this guide. Transit Delay Configured transit delay for this interface. Retrans Interval Configured retransmit interval for this interface. Hello Interval Configured hello interval for this interface.
IP Routing Features Configuring OSPF To clear the OSPF statistics for all VLAN interfaces on the switch and set all VLAN/subnet counters for OSPF traffic to zero, enter the clear ip ospf statistics command at any CLI level. ProCurve(ospf)# show ip ospf statistics vlan 1 OSPF statistics for VLAN 1 OSPF Interface Status for 10.0.0.
IP Routing Features Configuring OSPF Per-VLAN OSPF Statistics Field Content Tx/Rx LSA Packet Count Number of link-state acknowledgement packets sent/ received on each subnet interface OSPF errors Number of errors detected on the VLAN subnet during OSPF packet exchange ProCurve(ospf)# show ip ospf statistics 10.0.0.2 OSPF Interface Statistics IP Address Total Tx Total Rx Total Errors --------------- --------------- --------------- -------------10.0.0.2 15 15 15 Figure 5-44.
IP Routing Features Configuring OSPF Displaying OSPF Link State Information To display OSPF link state information, enter show ip ospf link-state at any CLI level. When you enter this command, the switch displays an output similar to the following for all configured areas: OSPF Link State Database for Area 0.0.0.0 Advertising LSA Type Link State ID Router ID ---------- --------------- --------------Router 10.0.8.32 10.0.8.32 Router 10.0.8.33 10.0.8.33 Network 10.3.2.37 10.0.8.37 Summary 10.3.16.0 10.0.8.
IP Routing Features Configuring OSPF Field Content Sequence # Sequence number of the current instance of this LSA. Chksum(Hex) LSA checksum value. Syntax show ip ospf link-state [status] [subset-options] [< advertise [subset options] >] : advertise: Displays the hexadecimal data in LSA packets (advertisements) for the OSPF area(s) configured on the routing switch. The output can also be filtered by area (area id), link-state-id, router-id, sequence-number, and/or type.
IP Routing Features Configuring OSPF type < router | network | summary | as-summary | external | multicast | nssa > Used to restrict display of LSA database or advertisements to show only the data from sources having the specified type. Can also be used with other subset options (ospf-area id, link-state-id, router-id, and sequence-number) to further define the source of displayed information.
IP Routing Features Configuring OSPF Displaying OSPF Neighbor Information To display OSPF information for all neighbors, enter show ip ospf neighbor at any CLI level: OSPF Neighbor Information Router ID --------------10.0.8.34 10.3.53.38 Pri --1 1 IP Address --------------10.3.18.34 10.3.53.38 NbIfState --------DR DR State -------FULL FULL Rxmt QLen --------0 0 Events --------6 6 Figure 5-47.
IP Routing Features Configuring OSPF Field Description State The state of the conversation (the adjacency) between your routing switch and the neighbor. The possible values are: • INIT – A Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor. (The switch itself did not appear in the neighbor's Hello packet.) All neighbors in this state (or higher) are listed in the Hello packets sent from the associated interface.
IP Routing Features Configuring OSPF Displaying OSPF Redistribution Information As described under “2. Enable Route Redistribution” on page 5-74, you can configure the routing switch to redistribute connected, static, and RIP routes into OSPF. When you redistribute a route into OSPF, the routing switch can use OSPF to advertise the route to its OSPF neighbors.
IP Routing Features Configuring OSPF This display shows the configured restrict entries. Displaying OSPF Virtual Neighbor Information If virtual links are configured on the routing switch, you can display OSPF virtual neighbor information by entering show ip ospf virtual-neighbor at any CLI level. OSPF Virtual Interface Neighbor Information Router ID --------------10.0.8.33 10.0.8.36 Area ID --------------10.3.16.0 10.3.16.0 State -------FULL FULL IP Address --------------10.3.17.33 10.3.18.
IP Routing Features Configuring OSPF Displaying OSPF Virtual Link Information If virtual links are configured on a routing switch, you can display OSPF virtual link information by entering show ip ospf virtual-link at any CLI level. ProCurve# show ip ospf virtual-link OSPF Virtual Interface Status Transit AreaID --------------10.3.16.0 10.3.16.0 Neighbor Router --------------10.0.8.33 10.0.8.36 Authentication --------------none none Interface State -------------P2P P2P Figure 5-51.
IP Routing Features Configuring OSPF Example:. To get OSPF virtual link information for IP address 10.0.8.33, enter show ip ospf virtual-link 10.0.8.33. A display similar to the following is shown. ProCurve# show ip ospf virtual-link 10.0.8.33 OSPF Virtual Interface Status for interface 10.0.8.33 Transit AreaID : 10.3.16.0 Neighbor Router : 10.0.8.33 Authentication : none Interface State : P2P Events : 1 Dead Interval : 40 Chain Transit Delay Rtr Interval Hello Interval : : 1 : 5 : 10 Figure 5-52.
IP Routing Features Configuring OSPF Displaying OSPF SPF Statistics To display the log used to record shortest-path-first (SPF) calculations on an OSPF-enabled routing switch, enter the show ip ospf spf-log command at any CLI level. The SPF algorithm recalculates the routes in an OSPF domain when a change in the area topology is received.
IP Routing Features Configuring OSPF ProCurve(ospf)# show ip ospf spf-log OSPF SPF (SHORTEST PATH FIRST) LOG Area : 0.0.0.100 spf instance --------------1 2 3 4 5 6 7 8 9 10 - Number of times SPF executed : 12 Reason -------------------------Router LS Update Router LS Update Generated RTR LSA Generated NTW LSA Network LS Update Network LS Update Generated RTR LSA Router LS Update Generated RTR LSA Re-Init Figure 5-53. Displaying OSPF SPF Statistics Table 5-21.
IP Routing Features Configuring OSPF Displaying OSPF Route Information To display OSPF route and other OSPF configuration information, enter show ip ospf at any CLI level: ProCurve# show ip ospf OSPF Configuration Information OSPF protocol Router ID : enabled : 10.0.8.35 Currently defined areas: Area ID --------------backbone 10.3.16.0 10.3.32.
IP Routing Features Configuring OSPF Syntax: show ip ospf This screen has a lot of information, most of it already covered in other show commands. The following table shows definitions for the fields: Table 5-22. CLI Display of OSPF Route and Status Information Field Description OSPF protocol enabled or disabled – indicates if OSPF is currently enabled. Router ID The Router ID that this routing switch is currently using to identify itself.
IP Routing Features Configuring OSPF Displaying OSPF Traps Enabled In the default configuration, OSPF traps are disabled. Use this command to view which OSPF traps have been enabled. Syntax: show ip ospf traps Lists the OSPF traps currently enabled on the routing switch. For more information on OSPF trap use, refer to “10: Optional: Change OSPF Trap Generation Choices” on page 5-80. Debugging OSFP Routing Messages The debug ip ospf command turns on the tracing of OSPF packets.
IP Routing Features Configuring OSPF Equal-Cost Next-Hop Routes 10.1.0.0/16 Router “3” Workstation Router “B” Router “A” 10.2.0.0/16 10.3.0.0/16 Router “C” 10.32.0.0/16 Router “D” Router “4” Router “1” 10.42.0.0/16 Router “2” Figure 5-55. Example of Load-Sharing Traffic to Different Subnets Through Equal-Cost Next-Hop Routers Example of a Routing Table for the Network in Figure 5-55 Destination Subnet Router “A” Next Hop 10.1.0.0/16 Router “C” 10.2.0.0/16 Router “D” 10.3.0.
IP Routing Features Configuring OSPF When OSPF is enabled and multiple, equal-cost, next-hop routes are available for traffic destinations on different subnets, this feature, by default, enables load-sharing among up to four nexthop routes. The no form of the command disables this loadsharing so that only one route in a group of multiple, equalcost, next-hop routes is used for traffic that could otherwise be load-shared across multiple routes.
IP Routing Features Configuring IRDP Configuring IRDP The ICMP Router Discovery Protocol (IRDP) is used by ProCurve routing switches to advertise the IP addresses of their router interfaces to directly attached hosts. IRDP is disabled by default. You can enable the feature on a global basis or on an individual VLAN interface basis. When IRDP is enabled, the routing switch periodically sends Router Adver tisement messages out the IP interfaces on which the feature is enabled.
IP Routing Features Configuring IRDP messages from other routers at the same time. The interval on each IRDPenabled routing switch interface is independent of the interval on other IRDP-enabled interfaces. The default maximum message interval is 600 seconds. The default minimum message interval is 450 seconds. ■ Preference - If a host receives multiple Router Advertisement messages from different routers, the host selects the router that send the message with the highest preference as the default gateway.
IP Routing Features Configuring IRDP for the routing switch to the hold time specified in the new advertisement. If the hold time of an advertisement expires, the host discards the adver tisement, concluding that the router interface that sent the advertisement is no longer available. The value must be greater than the value of the maxadvertinterval parameter and cannot be greater than 9000. The default is three times the value of the maxadvertinterval parameter.
IP Routing Features Configuring DHCP Relay Configuring DHCP Relay Overview The Dynamic Host Configuration Protocol (DHCP) is used for configuring hosts with IP address and other configuration parameters without user inter vention. The protocol is composed of three components: ■ DHCP client ■ DHCP server ■ DHCP relay agent The DHCP client sends broadcast request packets to the network; the DHCP servers respond with broadcast packets that offer IP parameters, such as an IP address for the client.
IP Routing Features Configuring DHCP Relay Broadcast Forwarding The packets are forwarded using broadcast forwarding if the IP address of the DHCP server is a subnet address or IP broadcast address (255.255.255.255). The DHCP relay agent sets the DHCP server IP address to broadcast IP address and will be forwarded to all VLANs with configured IP interfaces (except the source VLAN).
IP Routing Features Configuring DHCP Relay You must be in VLAN context to use this command, for example: ProCurve# config ProCurve(config)# vlan 1 ProCurve(vlan-1)# Syntax: ip bootp-gateway Allows you to configure an IP address for the DHCP relay agent to use for DHCP requests. The IP address must have been configured on the interface. Default: Lowest-numbered IP address If the IP address has not already been configured on the interface (VLAN), you will see the message shown in Figure 5-58.
IP Routing Features Configuring DHCP Relay ProCurve(vlan-22)ip bootp-gateway 12.16.18.33 ProCurve(vlan-22)# exit ProCurve(config)# show dhcp-relay bootp-gateway vlan 22 BOOTP Gateway Entries VLAN BOOTP Gateway -------------------- -------------VLAN 22 12.16.18.33 Figure 5-59.
IP Routing Features Configuring DHCP Relay Configuring an IP Helper Address To add the IP address of a DHCP server for a specified VLAN on a routing switch, enter the ip helper-address command at the VLAN configuration level as in the following example: ProCurve(config)# vlan 1 ProCurve(vlan-1)# ip helper-address To remove the DHCP server helper address, enter the no form of the command: ProCurve(vlan-1)# no ip helper-address < ip-addr > Operating Notes ■ You can configure up to 4000 IP helper
IP Routing Features Configuring DHCP Relay To reset the default function which increases the hop count in each DHCP request forwarded to a DHCP server, enter the following command: ProCurve(config)# dhcp-relay hop-count-increment Operating Notes ■ By default, the DHCP relay agent increases the hop count in each DHCP request by one. You must enter the no dhcp-relay hop-count-increment command to disable this function.
IP Routing Features Configuring DHCP Relay ProCurve# show config Startup configuration: ; J8697A Configuration Editor; Created on release #K.11.00 hostname “ProCurve” cdp run module 1 type J8702A ip default-gateway 18.30.240.1 snmp-server community “public” Unrestricted vlan 1 name “DEFAULT_VLAN” untagged A1 ip address 18.30.240.180 255.255.248.0 no untagged A2-A24 exit no dhcp-relay Non-Default DHCP Relay and Hop no dhcp-relay hop-count-increment Count Increment settings Figure 5-60.
IP Routing Features Configuring DHCP Relay Displaying the Hop Count Setting To verify the current setting for increasing the hop count in DHCP requests, enter the show dhcp-relay command. Note that the current setting is displayed next to DHCP Request Hop Count Increment.
IP Routing Features Configuring DHCP Relay addressing it will return to the client through the usual DHCP server response packet. This operation provides several advantages over DHCP without Option 82: Note ■ An Option 82 DHCP server can use a relay agent’s identity and client source port information to administer IP addressing policies based on client and relay agent location within the network, regardless of whether the relay agent is the client’s primary relay agent or a secondary agent.
IP Routing Features Configuring DHCP Relay For information on configuring policies on a server running DHCP Option 82, refer to the documentation provided for that application. Relay Agent “1” (Routing Switch) with DHCP Option 82 Enabled 10.10.30.1 10.10.20.2 VLAN 10 10.10.10.1 VLAN 20 10.10.20.1 Switch “B” 10.10.20.3 Switch “A” 10.10.10.
IP Routing Features Configuring DHCP Relay request. For a DHCP server response to an Option 82 client request, the routing switch can optionally perform a validation check to determine whether to forward or drop the response. Each Option 82 relay agent in the path between a DHCP client and an Option 82 DHCP server can be configured with a unique forwarding policy, which enhances DHCP policy control over discrete areas of a network.
IP Routing Features Configuring DHCP Relay with Option 82 fields.) Response packets from an Option 82 server are routed back to the primary relay agent (routing switch), and include an IP addressing assignment for the requesting client and an exact copy of the Option 82 data the server received with the client request. The relay agent strips off the Option 82 data and forwards the response packet out the port indicated in the response as the Circuit ID (client access port).
IP Routing Features Configuring DHCP Relay • Use the Management VLAN option if a Management VLAN is config ured and you want all DHCP clients on the routing switch to use the same IP address. (This is useful if you are applying the same IP addressing policy to DHCP client requests from ports in different VLANs on the same routing switch.
IP Routing Features Configuring DHCP Relay the sequential index number for that port position in the slot. (To view the Index number assignments for ports in the routing switch, use the walkmib ifname command.) For example, the Circuit ID for port B11 on a ProCurve switch is “35”. (See Figure 5-65, below.) ProCurve# walkmib ifname ifName.1 = A1 ifName.2 = A2 ifName.3 = A3 ifName.4 = A4 ifName.25 = B1 ifName.26 = B2 ifName.27 = B3 ifName.28 = B4 ifName.29 = B5 ifName.30 = B6 ifName.31 = B7 ifName.
IP Routing Features Configuring DHCP Relay Forwarding Policies DHCP Option 82 on ProCurve switches offers four forwarding policies, with an optional validation of server responses for three of the policy types (append, replace, or drop).
IP Routing Features Configuring DHCP Relay Option 82 Configuration Drop DHCP Client Request Packet Inbound to the Routing Switch Packet Has No Option 82 Field Packet Includes an Option 82 Field Append an Option 82 Field Drop causes the routing switch to drop an inbound client request with an Option 82 field already appended. If no Option 82 fields are present, drop causes the routing switch to add an Option 82 field and forward the request.
IP Routing Features Configuring DHCP Relay Relay Agent “A” Client VLAN 20 VLAN 10 DROP Relay Agent “B” VLAN 20 VLAN 30 APPEND Relay Agent “C” VLAN 10 VLAN 20 APPEND DHCP Option 82 Server Figure 5-67. Example Configured To Allow Multiple Relay Agents To Contribute an Option 82 Field This is an enhancement of the previous example. In this case, each hop for an accepted client request adds a new Option 82 field to the request.
IP Routing Features Configuring DHCP Relay With validation enabled, the relay agent applies stricter rules to variations in the Option 82 field(s) of incoming server responses to determine whether to forward the response to a downstream device or to drop the response due to invalid (or missing) Option 82 information. Table 5-23, below, describes relay agent management of DHCP server responses with optional validation enabled and disabled Table 5-23. Relay Agent Management of DHCP Server Response Packets.
IP Routing Features Configuring DHCP Relay Multinetted VLANs On a multinetted VLAN, each interface can form an Option 82 policy boundary within that VLAN if the routing switch is configured to use IP for the remote ID suboption.
IP Routing Features Configuring DHCP Relay Syntax: dhcp-relay option 82 < append [validate] | replace [validate] | drop [validate] | keep > [ip | mac | mgmt-vlan] — Continued — drop: Configures the routing switch to unconditionally drop any client DHCP packet received with existing Option 82 field(s). This means that such packets will not be forwarded. Use this option where access to the routing switch by untrusted clients is possible.
IP Routing Features Configuring DHCP Relay Example of Option 82 Configuration In the routing switch shown below, option 82 has been configured with mgmt vlan for the Remote ID. ProCurve(config)# dhcp-relay option 82 append mgmt-vlan The resulting effect on DHCP operation for clients X, Y, and Z is shown in table 5-24. Routing Switch Management VLAN VLAN 300 10.39.10.1 (secondary IP) DHCP Server “A” Client “X” 10.38.10.1 (primary IP) VLAN 200 DHCP Server “B” 10.29.10.1 Client “Y” 10.28.10.
IP Routing Features Configuring DHCP Relay Operating Notes ■ 5-148 This implementation of DHCP relay with Option 82 complies with the following RFCs: • RFC 2131 • RFC 3046 ■ Moving a client to a different port allows the client to continue operating as long as the port is a member of the same VLAN as the port through which the client received its IP address.
IP Routing Features Configuring DHCP Relay ■ Relay agents without Option 82 can exist in the path between Option 82 relay agents and an Option 82 server. The agents without Option 82 will forward client requests and server responses without any effect on Option 82 fields in the packets.
IP Routing Features UDP Broadcast Forwarding UDP Broadcast Forwarding Overview Some applications rely on client requests sent as limited IP broadcasts addressed to a UDP application port. If a server for the application receives such a broadcast, the server can reply to the client.
IP Routing Features UDP Broadcast Forwarding Table 5-25. Example of a UDP Packet-Forwarding Environment Interface VLAN 1 IP Address Subnet Mask 15.75.10.1 255.255.255.0 Forwarding Address UDP Port Notes 15.75.11.43 1188 15.75.11.255 1812 15.75.12.255 1813 Unicast address for forwarding inbound UDP packets with UDP port 1188 to a specific device on VLAN 2. Broadcast address for forwarding inbound UDP packets with UDP port 1812 to any device in the 15.75.11.0 network.
IP Routing Features UDP Broadcast Forwarding Configuring and Enabling UDP Broadcast Forwarding To configure and enable UDP broadcast forwarding on the switch: 1. Enable routing. 2. Globally enable UDP broadcast forwarding. 3. On a per-VLAN basis, configure a forwarding address and UDP port type for each type of incoming UDP broadcast you want routed to other VLANs.
IP Routing Features UDP Broadcast Forwarding — Continued from the preceding page. — < ip-address >: This can be either of the following: • The unicast address of a destination server on another subnet. For example: 15.75.10.43. • The broadcast address of the subnet on which a destination server operates. For example, the following address directs broadcasts to All hosts in the 15.75.11.0 subnet: 15.75.11.255.
IP Routing Features UDP Broadcast Forwarding Displaying the Current IP Forward-Protocol Configuration Syntax show ip forward-protocol [ vlan < vid >] Displays the current status of UDP broadcast forwarding and lists the UDP forwarding address(es) configured on all static VLANS in the switch or on a specific VLAN. Global Display Showing UDP Broadcast Forwarding Status and Configured Forwarding Addresses for Inbound UDP Broadcast Traffic for All VLANs Configured on the routing switch. Figure 5-70.
IP Routing Features UDP Broadcast Forwarding Operating Notes for UDP Broadcast Forwarding Maximum Number of Entries. The number of UDP broadcast entries and IP helper addresses combined can be up to 16 per VLAN, with an overall maximum of 2048 on the switch. (IP helper addresses are used with the switch’s DHCP Relay operation. For more information, refer to “Configuring DHCP Relay” on page 5-127.
IP Routing Features UDP Broadcast Forwarding 5-156
6 Virtual Router Redundancy Protocol (VRRP) Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Virtual Router (VR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Router Redundancy Protocol (VRRP) Contents Configuring Track VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 Removing all Tracked Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 Failover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29 Failback Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29 Displaying VRRP Tracked Entities . . . . . . . . . . . .
Virtual Router Redundancy Protocol (VRRP) Overview Overview In many networks, edge devices are often configured to send packets to a statically configured default router. If this router becomes unavailable, the devices that use it as their first-hop router become isolated from the network. VRRP uses dynamic failover to ensure the availability of an end node’s default router. This is done by assigning the IP address used as the default route to a “virtual router”, or VR.
Virtual Router Redundancy Protocol (VRRP) Terminology Terminology Backup: A router configured in a VR as a Backup to the Owner configured for the same VR. There must be a minimum of one Backup in a VR to support VRRP operation if the Owner fails. Every backup is created with a configurable priority (default: 100) that determines the precedence for becoming the Master of the VR if the Owner or another Backup operating as the Master becomes unavailable.
Virtual Router Redundancy Protocol (VRRP) General Operation General Operation VRRP supports router redundancy through a prioritized election process among routers configured as members of the same virtual router (VR). On a given VLAN, a VR includes two or more member routers configured with a virtual IP address that is also configured as a real IP address on one of the routers, plus a virtual router MAC address.
Virtual Router Redundancy Protocol (VRRP) General Operation Figure 6-1, below, illustrates a virtual router on VLAN 100 supported by Router 1 (R1) and Router 2 (R2). Intranet Router 1 (R1) Router 2 (R2) VLAN VID: 100 VLAN VID: 100 IP: 10.10.100.1 IP: 10.10.100.5 VR 1 Router 1 Configuration Router 2 Configuration VRID: 1 Status: Owner Virtual IP Addr: 10.10.100.1 MAC Addr: 00-00-5E-00-01-01 Priority: 255 VRID: 1 Status: Backup Virtual IP Addr: 10.10.100.
Virtual Router Redundancy Protocol (VRRP) General Operation In figure 6-1: 1. 2. 3. Host “A” uses 10.10.100.1 as its next-hop gateway out of the subnet, as represented by the virtual router (VR 1). • Router 1 (the configured Owner) advertises itself as the Master in the VR supporting the gateway and: – “owns” the VR’s (virtual) IP address – transmits ARP responses that associate the VR’s virtual IP address with the (shared) source MAC address for VR 1.
Virtual Router Redundancy Protocol (VRRP) General Operation Virtual Router (VR) A Virtual Router (VR) instance consists of one Owner router and one or more Backup routers belonging to the same network. Any VR instance exists within a specific VLAN, and all members of a given VR must belong to the same subnet. In a multinetted VLAN, multiple VRs can be configured. The Owner operates as the VR’s Master unless it becomes unavailable, in which case the highest-priority backup becomes the VR’s Master.
Virtual Router Redundancy Protocol (VRRP) General Operation Note that if the configured Owner in a VR becomes unavailable, then it is no longer the Master for the VR and a Backup router in the VR is elected to assume the role of Master, as described under “Backup Router” on page 6-10. A subnetted VLAN allows multiple, virtual IP addresses.
Virtual Router Redundancy Protocol (VRRP) General Operation Owner Router An Owner router for a VR is the default Master router for the VR, and operates as the Owner for all subnets included in the VR. As mentioned earlier, the VRRP priority on an Owner router is always 255 (the highest). Note On a multinetted VLAN where multiple subnets are configured in the same VR, the router must be either the Owner for all subnets in the VR or a Backup for all subnets in the VR.
Virtual Router Redundancy Protocol (VRRP) General Operation VRRP and ARP The Master for a given VR responds to ARP requests for the virtual IP addresses with the VR’s assigned MAC address. The virtual MAC address is also used as the source MAC address for the periodic advertisements sent by the current Master.
Virtual Router Redundancy Protocol (VRRP) General Operation ■ When a VR is active you cannot change any of the following on that VR: • priority • advertisement interval • preempt mode • virtual IP address ■ A VR exists within a single VLAN interface. If the VLAN is multinetted, then a separate VR can be configured within the VLAN for each subnet. A VLAN allows up to 32 VRs and the switch allows up to 2048 VRs. ■ All routers in the same VR must belong to the same network or subnet.
Virtual Router Redundancy Protocol (VRRP) Steps for Provisioning VRRP Operation Steps for Provisioning VRRP Operation Basic Configuration Process This process assumes the following for VRRP operation: ■ VLANs on the selected routers are already configured and IP-enabled. ■ IP routing is enabled ■ The network topology allows multiple paths for routed traffic between edge devices. 1. Configure the Owner for VRRP operation and a VR instance. a.
Virtual Router Redundancy Protocol (VRRP) Steps for Provisioning VRRP Operation 2. Configure a Backup for the same VR instance as for the Owner in step 1. a. On another router with an interface in the same network or subnet as is the Owner (configured in step 1), enter the global configuration context and enable VRRP. router vrrp b. Configure (and enter) the same VR instance as was configured for the Owner in step 1. vlan < vid > vrrp vrid < 1 - 255 > c.
Virtual Router Redundancy Protocol (VRRP) Steps for Provisioning VRRP Operation Example Configuration In VR 1, below, R1 is the Owner and the current Master router, and R2 is the (only) Backup in the VR. If R1 becomes unavailable, VR 1 fails over to R2. Host “A” Gateway: 10.10.10.1 VR 1 10.10.10.1 (Virtual IP Address) Intranet Router 1 (R1) Router 2 (R1) VLAN VID: 10 IP: 10.10.10.1 VLAN VID: 10 IP: 10.10.10.23 Router 1 Configuration VRID: 1 Status: Owner Virtual IP Addr: 10.10.10.
Virtual Router Redundancy Protocol (VRRP) Steps for Provisioning VRRP Operation ProCurve(config)# router vrrp ProCurve(config)# vlan 10 ProCurve(vlan-10)# vrrp vrid 1 ProCurve(vlan-10-vrid-1)# owner ProCurve(vlan-10-vrid-1)# virtual-ip-address 10.10.10.1 255.255.255.
Virtual Router Redundancy Protocol (VRRP) Steps for Provisioning VRRP Operation Associating More Than One Virtual IP Address With a VR This need arises if a VLAN is configured with more than 32 subnets and it is necessary to apply VRRP to all of these subnets. Because a VLAN on the routers covered by this Guide supports up to 32 VRs, applying VRRP to a higher number of subnets in the VLAN requires multiple virtual IP addresses in one or more VRs.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Configuring VRRP Enabling VRRP in the Global Configuration Context VRRP can be configured regardless of the global VRRP configuration status. However, enabling a VR and running VRRP requires enabling it in the global configuration context. Syntax: [no] router vrrp Enables or disables VRRP operation in the global configura tion context. IP routing must be enabled before enabling VRRP on the router.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP For example, the following commands enable VRRP at the global configura tion level and then display the current global VRRP configuration: ProCurve(config)# router vrrp ProCurve(config)# show vrrp config global VRRP Global Configuration Information VRRP Enabled Traps Enabled : Yes : Yes Figure 6-5.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Configuring a VR Instance on a VLAN Interface The preceeding section describes the command for creating and entering a VR context. This section describes the configuration and activation com mands available in the VR context. Assigning Owner and Backup Status. Each VRRP router must be config ured as either the Owner of the VR instance or a Backup for the instance.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Configuring a Virtual IP address in a VR. The virtual IP address must be the same for the Owner and all Backups on the same network or subnet in a VR. Syntax: virtual-ip-address < owner-ip-addr >/mask-length > virtual-ip-address < owner-ip-addr > < mask > Used in a VR context of a VLAN to assign an IP address/mask combination to a VR instance.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Reconfiguring the Priority for a Backup. When you configure a Backup in a VR, it is given a default priority of 100. This command is intended for use where it is necessary to establish a precedence among the Backup routers on the same network or subnet in a given VR. Syntax: priority < 1 - 254 > Used in a VR context of a VLAN where the router is configured as a Backup.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Changing VR Advertisement Interval and Source IP Address The advertisement interval is used in one of two ways, depending on whether a VRRP router is operating as a Master or a Backup. Syntax: advertise-interval < 1 - 255 > ■ When a VRRP router is operating as Master, this value specifies the interval at which the router sends an advertisement notifying the other VRRP routers on the network or subnet that a Master is active.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Syntax: primary-ip-address < ip-address | lowest > Specifies the virtual IP address to designate as the source for VRRP advertisements from the VR. If there is only one virtual IP address configured on the VR, the default setting (lowest) is sufficient. Where there are multiple virtual IP addresses in the same VR and you want to designate an advertisement source other than the lowest IP Address, use this command.
Virtual Router Redundancy Protocol (VRRP) Configuring VRRP Preempt Mode on VRRP Backup Routers This command applies to VRRP Backup routers only, and is used to minimize network disruption due to unnecessary preemption of the Master operation among Backup routers. Syntax: [no] preempt-mode Disables or re-enables Preempt mode. In the default mode, a Backup router coming up with a higher priority than another Backup that is currently operating as Master will take over the Master function.
Virtual Router Redundancy Protocol (VRRP) Dynamically Changing the Priority of the VR Dynamically Changing the Priority of the VR The dynamic priority change feature provides the ability to dynamically change the priority of the virtual router (VR) when certain events occur. The Backup VR releases virtual IP address control by reducing its priority when tracked entities such as ports, trunks, or VLANs go down.
Virtual Router Redundancy Protocol (VRRP) Dynamically Changing the Priority of the VR Note A Backup VR switches to priority zero instead of its configured value when all its tracked entities go down. An Owner VR always uses priority 255 and never relinquishes control voluntarily. CLI Commands The following commands are used for this feature. Note You can only configure tracked interfaces or VLANs on the Backup router.
Virtual Router Redundancy Protocol (VRRP) Dynamically Changing the Priority of the VR Configuring Track VLAN The track vlan command allows you to specify a VLAN or range of VLANs to be tracked by the VR. Notes VR operation must be down before executing this command. Use the no enable command to disable VR operation. The VR’s operating VLAN can’t be configured as a tracking VLAN for that VR.
Virtual Router Redundancy Protocol (VRRP) Dynamically Changing the Priority of the VR Syntax: no track The command allows you to remove tracking for all config ured track entities (ports, trunks, and VLANs). The command is executed in VRID instance context. For example: ProCurve(vlan-25-vrid-1)# no track Failover Operation Failover operation involves handing off of the VR’s control of the virtual IP to another VR.
Virtual Router Redundancy Protocol (VRRP) Dynamically Changing the Priority of the VR Syntax: failback Forces the Backup VR to take ownership of the VR instance. This command only takes effect if the Backup VR instance has a higher priority than the current Owner, which is normal VRRP router behavior. The command is executed in VRID instance context. Displaying VRRP Tracked Entities You can display the VRRP tracked entities by entering the command shown in Figure 6-9.
Virtual Router Redundancy Protocol (VRRP) Using the Pre-empt Delay Timer Using the Pre-empt Delay Timer Overview In order to maintain availability of the default gateway router, the Virtual Router Redundancy Protocol (VRRP) advertises a “virtual” router to the hosts. At least two other physical routers are configured to be virtual routers, but only one router provides the default router functionality at any given time. If the Owner router or its VLAN goes down, the Backup router takes over.
Virtual Router Redundancy Protocol (VRRP) Using the Pre-empt Delay Timer Syntax: [no] preempt-delay-time <1-600 > Allows you to specify a time in seconds that this router will wait before taking control of the virtual IP address and beginning to route packets. You can configure the timer on VRRP Owner and Backup routers. Note: If you have configured the Preempt Delay Timer with a non-zero value, you must use the no form of the command to change it to 0 (zero). Default: 0 (zero) seconds.
Virtual Router Redundancy Protocol (VRRP) Using the Pre-empt Delay Timer During this waiting period, if the Owner router receives a VRRP packet for its virtual IP address from the Backup router, it will wait until the PDT expires before taking control of its virtual IP address. If the Owner router does not receive any VRRP packets and the Master down time expires, the Owner router can take control of its virtual IP address immediately.
Virtual Router Redundancy Protocol (VRRP) Using the Pre-empt Delay Timer Possible Configuration Scenarios Preempt Delay Time = Zero Seconds. This is the default behavior. It works in the same way that VRRP works currently. Preempt Delay Time is Greater Than or Equal to the Master Down Time (3 times the advertisement interval). a. An Owner Virtual Router after reboot—waits for the Master Down Time. If the Owner router does not receive a packet during this time, it becomes the Master.
Virtual Router Redundancy Protocol (VRRP) Using the Pre-empt Delay Timer Error Messages Error Error Message Attempting to assign the preempt delay time to the Virtual Router before declaring it as an Owner or Backup The Virtual Router must be defined as an Owner or Backup router first. Attempting to assign an out of range preempt delay time Invalid input: to the Virtual Router instance. Attempting to change the preempt delay time value when the Virtual Router is active.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data Displaying VRRP Configuration and Statistics Data VRRP Configuration Data Displaying the VRRP Global Configuration Syntax: show vrrp config global This command displays the configuration state for the global VRRP configuration and VRRP trap generation. For example: ProCurve(config)# show vrrp config global VRRP Global Configuration Information VRRP Enabled : No Traps Enabled : Yes Figure 6-10.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data ProCurve(config)# show vrrp config VRRP Global Configuration Information VRRP Enabled Traps Enabled : Yes : Yes VRRP Virtual Router Configuration Information Vlan ID : 10 Virtual Router ID : 10 Administrative Status [Disabled] : Disabled Mode [Uninitialized] : Owner Priority [100] : 255 Advertisement Interval [1] : 1 Preempt Mode [True] : True Primary IP Address : Lowest IP Address Subnet Mask --------------- ----
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data Displaying a Specific VR Configuration Syntax: show vrrp vlan 23 vrid 10 config Displays the configuration for a specific VR in a specific VLAN.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data VRRP Statistics Data All command outputs shown in this section assume that VRRP is enabled at the global configuration level. If global VRRP is disabled, these commands produce the following output: VRRP Global Statistics Information VRRP Enabled : No Figure 6-13.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data Displaying Statistics for All VRRP Instances on the Router Syntax: show vrrp [statistics] Displays the following VRRP statistics: ■ global VRRP statistics for the router ■ VRRP statistics for all VRs configured on the router: • State: Indicates whether the router is a Backup or the current Master of the VR. • Uptime: The amount of time the router has been up since the last reboot.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data • Mismatched Interval Pkts: The number of VRRP packets received from other routers (since the last reboot) with an advertisement interval that is differ ent from the interval configured on the current VR. (Note that VRRP packets received with an interval mismatch are dropped. • Mismatched IP TTL Pkts: The number of VRRP packets received with the IP TTL field not set to 255. Such packets are dropped.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data ProCurve(config)# show vrrp VRRP Global Statistics Information VRRP Enabled Protocol Version Invalid VRID Pkts Rx Checksum Error Pkts Rx Bad Version Pkts Rx : : : : : Yes 2 0 0 0 VRRP Virtual Router Statistics Information Vlan ID Virtual Router ID State Up Time Virtual MAC Address Master's IP Address Associated IP Addr Count Advertise Pkts Rx Zero Priority Rx Bad Length Pkts Mismatched Interval Pkts Mismatched IP
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data ProCurve(config)# show vrrp vlan 10 VRRP Virtual Router Statistics Information Vlan ID Virtual Router ID State Up Time Virtual MAC Address Master's IP Address Associated IP Addr Count Advertise Pkts Rx Zero Priority Rx Bad Length Pkts Mismatched Interval Pkts Mismatched IP TTL Pkts : : : : : : : : : : : : 10 10 Master 6 mins 00005e-00010a 10.10.10.
Virtual Router Redundancy Protocol (VRRP) Displaying VRRP Configuration and Statistics Data ProCurve(config)# show vrrp VRRP Global Statistics Information VRRP Enabled Protocol Version Invalid VRID Pkts Rx Checksum Error Pkts Rx Bad Version Pkts Rx : : : : : Yes 2 0 0 0 VRRP Virtual Router Statistics Information Vlan ID Virtual Router ID State Up Time Virtual MAC Address Master's IP Address Associated IP Addr Count Advertise Pkts Rx Zero Priority Rx Bad Length Pkts Mismatched Interval Pkts Mismatched IP
Virtual Router Redundancy Protocol (VRRP) Standards Compliance Standards Compliance VRRP on the switches supported by this Guide includes the following: ■ Complies with RFC 3768 Virtual Router Redundancy Protocol (VRRP), except for maximum number of VRs per VLAN, which is 32 on the routers covered by this Guide. ■ Compatible with ProCurve Series 9300m routers, the ProCurve 9408sl router, and the ProCurve Series 8100fl switches. (VRRP on these devices is based on RFC 2338.
Virtual Router Redundancy Protocol (VRRP) Operating Notes Operating Notes 6-46 ■ VRRP Advertisements Not Reaching the Backup(s): If a Master is forwarding traffic properly, but its Backup(s) are prevented from receiving the Master’s VRRP advertisements, then both routers will operate in the Master mode for the VR. If this occurs, traffic for the applicable gateway will continuously alternate between routers (sometimes termed “flapping”).
Virtual Router Redundancy Protocol (VRRP) Operating Notes Dynamic Priority Change Operating Notes ■ There are no backward compatibility issues with the VRRP dynamic priority change feature. If a VRRP router has an older firmware version that does not have the dynamic priority change feature, it will not have the needed configuration options. ■ The VR’s operating VLAN can’t be configured as a tracking VLAN for that VR. ■ Ports that are part of a trunk can’t be tracked.
Virtual Router Redundancy Protocol (VRRP) Event Log Messages Event Log Messages Message Meaning Failure to send out pkt for vrid < vrid-# >, vid < vid-# > A VRRP packet could not be sent out for the indicated VR on the specific VLAN due to any system-dependent problem. If packets could not be sent out, the expected protocol operation may be hampered. No VR with vrid < vrid-# > found on vid < vid-# > Indicates a VRRP packet received for a VR that does not exist on the VLAN.
Virtual Router Redundancy Protocol (VRRP) Event Log Messages Message Meaning — Continued from Previous Page — Vrid < vrid-# >, Vid < vid-# > recd pkt with bad IP-TTL A VRRP packet was received by the indicated VR on the indicated VLAN with an IP TTL value not equal to 255. Vrid < vrid-# >, Vid < vid-# > recd pkt with checksum error The indicated VR on the indicated VLAN has received a VRRP advertisement packet with a checksum error. The VR has therefore dropped that packet.
Virtual Router Redundancy Protocol (VRRP) Error Messages Error Messages Track Interface Message Description VR must be defined as “backup” first You have to declare a VR as Backup before assigning a track interface to it. Invalid input: You have to assign a valid port or trunk to the VR instance. VR operation must be “down” prior to modifying VR’s parameters You cannot change the track interface when the VR is active. Use the no enable command to disable the VR.
Index Symbols A ABR definition … 5-47 OSPF … 5-47 ACL operation with PIM … 3-36 address IP … 5-15 administrative distance, OSPF … 5-79 advertisement, OSPF … 5-46 area … 5-65 retransmit interval … 5-84 retransmit interval in virtual link … 5-92 area range, OSPF configuring … 5-76 area, OSPF assigning VLAN to … 5-69, 5-71 configuring … 5-65 definition … 5-50 displaying area information … 5-99 ARP arp-age … 5-12 cache … 5-8 cache table … 5-8 configuring parameters … 5-17 enabling local proxy … 5-19, 5-20, 5-2
add multicast group … 4-40 change hold time … 4-40 configuring operation … 4-38 defined … 4-6 display config … 4-65 display status … 4-65 displaying current set … 4-63 election priority … 4-41 enabling or disabling … 4-40 multicast groups … 4-38 specify VLAN interface … 4-38 with PIM-SM router … 4-6 D debug VRRP … 6-44 default route … 5-29 default settings ip multicast-routing, disabled … 3-12 PIM interface configuration settings … 3-30 PIM-DM … 3-3 recommendation to keep defaults … 3-9 router pim state re
F failback, VRRP … 6-29 failover, VRRP … 6-3, 6-29 filters effect of IGMP … 2-29 maximum allowed … 2-6 See also OSPF and RIP.
interface parameters … 5-14 interior gateway protocol … 5-44 IP static routes administrative distance … 5-28 blackhole … 5-24, 5-27 configuration … 5-27 default route … 5-11, 5-25 default route, configuring … 5-29 display … 5-29 maximum … 5-6 null interface … 5-25 null route … 5-24, 5-26 reject … 5-27 VLAN state … 5-26 loopback interface … 5-50 null routes … 5-24 overview … 5-6 parameter configuring … 5-15 Proxy ARP, enabling … 5-19 route exchange protocols … 5-10 router ID … 5-48, 5-49, 5-50 routing table
remote ID … 5-137, 5-138 requirements … 5-137 secondary relay agent … 5-137 server support … 5-135 validating server response packets … 5-143 OSPF ABR … 5-44, 5-45, 5-47 ABR, connection requirement … 5-65 ABR, range configuration … 5-59 administrative distance … 5-59, 5-79 advertisement, blocking … 5-78 advertisements … 5-77 area … 5-45, 5-50, 5-59 assigning VLAN to … 5-69, 5-71 configuring … 5-65 area border router … 5-44, 5-47 area configuration … 5-65 area information … 5-99 area range configuring … 5-76
NSSA … 5-45, 5-46, 5-50, 5-52 NSSA, configuring … 5-67 overview … 5-46 parameters, default global … 5-60 parameters, default interface … 5-61 passive … 5-96 password … 5-86 password, virtual link … 5-94 priority … 5-59, 5-81, 5-83 range, blocking … 5-78 redistribution … 5-75 enabling … 5-74 metric … 5-75 metric type … 5-76 redistribution filters displaying … 5-113 redistribution information … 5-113 redistribution, configuring … 5-74 redistribution, loopback interface … 5-72 restrict redistribution filters,
flood and prune … 3-6, 3-7, 3-28 flood and prune cycle … 3-35 flow … 3-6, 3-9 flow, bridged … 3-37 flow, equalizing … 3-38, 3-39, 3-40, 3-41 flow, hardware … 3-10, 3-13 flow, multicast, limit … 3-10, 3-38 flow, software … 3-10, 3-13 flow, VLAN limit … 3-4 forwarding state … 3-7 general operation … 3-5 graft packets … 3-16, 3-17 group entry, age-out … 3-25 hello hold-time … 3-15, 3-30 hello interval, effect … 3-15 host … 3-9 IGMP required, per VLAN … 3-9 IGMP requirement … 3-36 IGMP version 1 … 3-4 IGMP vers
compatible draft versions … 4-6 configuration … 4-27, 4-56 configuring candidate-RPs … 4-37 Designated Router … 4-12 display BSR data … 4-61 display config … 4-51 display C-RP config … 4-65 display RP set … 4-63 display status … 4-51 displaying settings … 4-46 DR … 4-7 priority … 4-57 draft versions 1 and 2 … 4-6 enable/disable SNMP Traps … 4-41 entries in routing table … 4-52 event log messages … 4-68 expire time … 4-48, 4-57 features … 4-5 flow capacity … 4-5 flow, defined … 4-7 flow, hardware … 4-41 flow
Pre-empt Delay Timer … 6-31 backward compatibility … 6-34 PDT value … 6-33 with older devices … 6-32 Premium License OSPF … 5-6 overview, list of features … -xviii PIM-DM … 3-2 PIM-SM … 4-5 VRRP … 6-3 primary relay agent … 5-137 priority IP multicast traffic … 2-5 ProCurve switch documentation … -xvii protocols IP route exchange … 5-10 Proxy ARP, enabling … 5-19 proxy forwarding, IGMP … 2-19 prune, defined … 4-7 Q query See IGMP. quick start … 1-8 R redistribution … 5-113 See OSPF and RIP.
S secondary relay agent … 5-137 setup screen … 1-8 Shortest Path Tree, defined … 4-8 SPF algorithm displaying OSPF statistics … 5-117 SPT defined … 4-8 operation … 4-10 PIM-SM traffic … 4-42 static IP routes configuring … 5-24, 5-26 route types … 5-24 See also IP routing. Static Rendezvous Point See static-RP.
disable global … 6-18 disable on VR … 6-25 disabled during configuration … 6-20 disabling operation … 6-28 display all instances … 6-40 configuration for all VRs … 6-36 global configuration … 6-36 statistics per VLAN … 6-42 statistics, global … 6-39 statistics, specific instance … 6-43 uptime … 6-40 VR, specific … 6-38 displaying tracked entities … 6-30 dropped packets … 6-46 dynamic priority change … 6-26 election process … 6-5 enable global … 6-18 enable on VR … 6-25 event log … 6-18 event log messages …
advertisement interval, change … 6-23 changes … 6-12 configure an instance … 6-20 deactivate … 6-12 defined … 6-4 IP address … 6-12 IP address limit … 6-46 IP address, delete … 6-46 MAC address … 6-5, 6-8 MAC address, source … 6-6 maximum in a VLAN … 6-8 maximum per switch … 6-12 maximum per VLAN … 6-12 membership … 6-8 multiple IP addresses … 6-17 multiple VRs in VLAN … 6-8 multiple, in a VLAN … 6-9 operation … 6-8 owner IP address … 6-21 subnet limit per VLAN … 6-46 virtual IP address … 6-21 virtual IP ad
ProCurve 5400zl Switches Installation and Getting Startd Guide Technology for better business outcomes To learn more, visit www.hp.com/go/procurve/ © Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
