Multicast and Routing Guide 2910al ProCurve Switches W.14.01 www.procurve.
HP ProCurve 2910al Switch September 2009 W.14.
© Copyright 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Printed Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Electronic Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Software Feature Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Forwarding Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 IP Route Exchange Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 IP Global Parameters for Routing Switches . . . . . . . . . . . . . . . . . . . . . 3-8 ARP Age Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 IP Interface Parameters for Routing Switches . . . . . . . . . . . . . . . . . .
Enabling IP RIP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30 Changing the RIP Type on a VLAN Interface . . . . . . . . . . . . . . . . 3-30 Changing the Cost of Routes Learned on a VLAN Interface . . . . 3-30 Configuring RIP Redistribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Define RIP Redistribution Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31 Modify Default Metric for Redistribution . . . . . . . . . . . . . . . . . . .
Option 82 Field Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52 Forwarding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54 Configuration Options for Managing DHCP Client Request Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54 Multiple Option 82 Relay Agents in a Client Request Path . . . . . 3-55 Validation of Server Response Packets . . . . . . . . . . . . . . . . . . . . .
viii
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, click on Customer Care, and then click on Manuals. Printed Publications The publications listed below are printed and shipped with your switch.
Software Feature Index For the software manual set supporting your 2910al 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 Manual Management Advanced and Traffic Configuration Management 802.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management DHCP/Bootp Operation X Diagnostic Tools X Downloading Software X Multicast and Routing Access Security Guide Dynamic ARP Protection X Dynamic Configuration Arbiter X Eavesdrop Protection X Event Log X Factory Default Settings X Flow Control (802.
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Multicast and Routing Access Security Guide MAC Lockdown X MAC Lockout X MAC-based Authentication X Management VLAN Monitoring and Analysis X X Multicast Filtering X Multiple Configuration Files X Network Management Applications (SNMP) X OpenView Device Management X Passwords and Password Clear Protection X ProCurve Manager (PCM) X Ping X Port Configuration X Port Monitoring X Por
Intelligent Edge Software Features RMON 1,2,3,9 Manual Management Advanced and Traffic Configuration Management Multicast and Routing Access Security Guide X Routing X Routing - IP Static X Secure Copy X sFlow X SFTP X SNMPv3 X Software Downloads (SCP/SFTP, TFPT, Xmodem) X Source-Port Filters X Spanning Tree (STP, RSTP, MSTP) X SSHv2 (Secure Shell) Encryption X SSL (Secure Socket Layer) X Stack Management (3500yl/6200yl switches only) X Syslog X System Information X TACACS+
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Voice VLAN Multicast and Routing Access Security Guide X Web Authentication RADIUS Support X Web-based Authentication X Web UI X Xmodem X xiv
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 switches: ■ HP ProCurve 2910al Switch 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 other product documentation for the above switches, refer to “Product Documentation” on page xi. You can download documenta tion from the ProCurve Networking web site, www.procurve.com.
Getting Started Conventions ■ Boldface indicates use of a CLI command, part of a CLI command syntax, or other displayed element in general text. For example: “Use the copy tftp command to download the key from a TFTP server.” ■ Italics indicate variables for which you must supply a value when execut ing the command.
Getting Started Sources for More Information Keys Simulations of actual keys use a bold, sans-serif typeface with square brackets. For example, the Tab key appears as [Tab] and the “Y” key appears as [Y]. 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 xii.
Getting Started Sources for More Information • • • ■ Advanced Traffic Management Guide—Use this guide for information on topics such as: • ■ ■ ■ port configuration, trunking, traffic control, and PoE operation SNMP, LLDP, and other network management topics file transfers, switch monitoring, troubleshooting, and MAC address management 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: 1. Go to the ProCurve Networking web site at www.procurve.com 2. Click on Customer Care. 3. Click on Manuals. 4. Click on the product for which you want to view or download a manual. If you need further information on ProCurve switch technology, visit the ProCurve Networking web site at: www.procurve.
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 ProCurve Web Browser Interface (hereafter referred to as the “web browser interface”), use the online Help. You can access the Help by clicking on the Help text on top right side of any of the web browser interface screens.
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. The maximum number of multicast groups is 256.
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 DEFAULT_VLAN Yes No No 22 VLAN-2 Yes Yes Yes 33 VLAN-3 No No No 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: 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 IGMP Function Available With IP Addressing Available Operating Differences Without an IP Address Configured on the VLAN Without IP Addressing? Configure IGMP traffic forwarding to normal or high-priority forwarding. Yes None Age-Out IGMP group addresses when the last IGMP client on a port in the VLAN leaves the group. Yes Support Fast-Leave IGMP and Forced FastLeave IGMP (below).
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates removing the IGMP group filter before the Querier has recognized the IGMP leave. The Querier will continue to transmit the multicast group during this short time, and because the group is no longer registered the switch will then flood the multicast group to all ports. On ProCurve switches that do support Data-Driven IGMP (“Smart” IGMP), when unregistered multicasts are received the switch automatically filters (drops) them.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates In the next figure, automatic Fast-Leave operates on the switch ports for IGMP clients “3A” and “5A”, but not on the switch port for IGMP clients “7A” and 7B, Server “7C”, and printer “7D”. Fast-Leave IGMP automatically operates on the ports connected to IGMP clients 3A and 5A, but does not operate on the port connected to Switch 7X because the switch detects multiple end nodes on that port.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Configuring Fast-Leave IGMP. Syntax: [no] ip igmp fastleave < port-list > Enables IGMP fast-leaves on the specified ports in the selected VLAN. The no form of the command disables IGMP fast-leave on the specified ports in the selected VLAN. Use show running to display the ports per-VLAN on which Fast-Leave is disabled.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates Configuring Delayed Group Flush When enabled, this feature continues to filter IGMP groups for a specified additional period of time after IGMP leaves have been sent. The delay in flushing the group filter prevents unregistered traffic from being forwarded by the server during the delay period. In practice, this is rarely necessary on the switches covered in this guide, which support data-driven IGMP.
Multimedia Traffic Control with IP Multicast (IGMP) How IGMP Operates How IGMP Proxy Forwarding Works The following steps illustrate how to flood a flow from the PIM-SM domain into the PIM-DM domain when an IGMP join for that flow occurs in the PIM-DM domain (refer to figure 2-4). 1. Routing Switch 1 is configured with the IGMP proxy forwarding function to forward joins towards Border Router 1.
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 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. It may be necessary to configure multiple overlapping domains if the multicast source address can generate the same multicast address and have different best paths to the PIM-DM domain.
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.
3 IP Routing Features Contents Overview of IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 IP Tables and Caches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 ARP Cache Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 IP Route Table . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Static Route Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22 Other Sources of Routes in the Routing Table . . . . . . . . . . . . . . . . . . 3-23 Static IP Route Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Static Route States Follow VLAN States . . . . . . . . . . . . . . . . . . . . . . . 3-24 Configuring a Static IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Routing Features Contents Broadcast Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44 Prerequisites for DHCP Relay Operation . . . . . . . . . . . . . . . . . . . . . . . 3-44 Enabling DHCP Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45 Configuring an IP Helper Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45 Operating Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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: ■ 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 ■ IRDP (ICMP Router Discovery Protocol) – advertises the IP addresses of the routing interfaces on this switch to directly attached host systems ■ DHCP Relay – allows you to extend the
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 Routing Information Protocol (RIP). 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. For configuration information, see “Configuring RIP” on page 3-27.
IP Routing Features Overview of IP Routing Parameter Description Default See page 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. If decreasing the TTL causes the TTL to be 0, the router drops the packet instead of forwarding it. 64 hops Refer to the chapter titled “Configuring IP Addressing” in the Management and Configuration Guide.
IP Routing Features Overview of IP Routing 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). If the option “infinite” is configured, the internal ARP age timeout is set to 99,999,999 seconds (approximately 3.2 years). An arp-age value of 0 (zero) is stored in the configuration file to indicate that “infinite” has been configured.
IP Routing Features Overview of IP Routing ProCurve(config)# show running-config Running configuration: ; J9146A Configuration Editor; Created on release #W.14.XX hostname "8200LP" module 2 type J8702A module 3 type J8702A module 4 type J8702A ip default-gateway 15.255.120.1 ip arp-age 1000 snmp-server community "public" Unrestricted snmp-server host 16.180.1.240 "public" vlan 1 name "DEFAULT_VLAN" untagged B1-B24,C1-C24,D1-D24 ip address 15.255.120.85 255.255.248.0 exit gvrp spanning-tree Figure 3-3.
IP Routing Features Overview of IP Routing IP Interface Parameters for Routing Switches Table 3-2 lists the interface-level IP parameters for routing switches. Table 3-2. IP Interface Parameters – Routing Switches Parameter Description Default See page IP address A Layer 3 network interface address; separate IP addresses on individual VLAN interfaces. None configured Metric A numeric cost the router adds to RIP routes learned on the interface. This parameter applies only to RIP routes.
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 priority than other configured interfaces.) 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. Reconfiguring the Router ID (Optional). If you want to change the router ID setting, do the following: 1. Go to the global config context. When you do so, the CLI prompt will appear similar to the following: ProCurve(config)#_ 2.
IP Routing Features Configuring IP Parameters for Routing Switches The routing switch encapsulates IP packets in Layer 2 packets regardless of whether the ultimate destination is locally attached or is multiple router hops away. Since the routing switch’s IP route table and IP forwarding cache contain IP address information but not MAC address information, the routing switch cannot forward IP packets based solely on the information in the route table or forwarding cache.
IP Routing Features Configuring IP Parameters for Routing Switches ARP requests contain the IP address and MAC address of the sender, so all devices that receive the request learn the MAC address and IP address of the sender and can update their own ARP caches accordingly. Note: The ARP request broadcast is a MAC broadcast, which means the broadcast goes only to devices that are directly attached to the routing switch. A MAC broadcast is not routed to other networks.
IP Routing Features Configuring IP Parameters for Routing Switches Syntax: [no] ip proxy-arp Enabling Local Proxy ARP When the Local Proxy ARP option is enabled, a switch responds with its MAC address to all ARP request on the VLAN. All IP packets are routed through and forwarded by the switch. The switch prevents broadcast ARP requests from reaching other ports on the VLAN. Notes Internet Control Message Protocol (ICMP) redirects will be disabled on interfaces on which local proxy ARP is enabled.
IP Routing Features Configuring IP Parameters for Routing Switches ProCurve(vlan-1)# show ip Internet (IP) Service IP Routing : Disabled Default TTL Arp Age Domain Suffix DNS server : 64 : 20 : : VLAN -------------------DEFAULT_VLAN VLAN2100 | + | | IP Config IP Address Subnet Mask Proxy ARP ---------- --------------- --------------- -------DHCP/Bootp 15.255.157.54 255.255.248.0 Yes Yes Disabled Figure 3-5.
IP Routing Features Configuring IP Parameters for Routing Switches Note A less common type, the all-subnets broadcast, goes to all directly-attached subnets. Forwarding for this broadcast type also is supported, but most networks use IP multicasting instead of all-subnet broadcasting. Forwarding for all types of IP directed broadcasts is disabled by default. You can enable forwarding for all types if needed. You cannot enable forwarding for specific broadcast types.
IP Routing Features Configuring IP Parameters for Routing Switches 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. Disabling ICMP Messages ProCurve devices are enabled to reply to ICMP echo messages and send ICMP Destination Unreachable messages by default.
IP Routing Features Configuring IP Parameters for Routing Switches 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. The following types of ICMP Unreachable messages are generated: Note ■ Administration – The packet was dropped by the ProCurve device due to a filter or ACL configured on the device.
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 destination next-hop pair. The following example configures two static routes for traffic delivery and identifies two other null routes for which traffic should be discarded instead of forwarded. ProCurve(config)# ip route 10.10.40.0/24 10.10.10.1 ProCurve(config)# ip route 10.10.50.128/27 10.10.10.1 ProCurve(config)# ip route 10.10.20.177/32 reject ProCurve(config)# ip route 10.10.30.0/24 blackhole Configures a null route to drop traffic for the 10.50.10.
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 3-33. 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 Example: To configure the switch to filter out redistribution of static or connected 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.0 ProCurve(rip)# write memory Note The default configuration permits redistribution for all default connected routes only.
IP Routing Features Configuring RIP ProCurve(rip)# redistribute static ProCurve(rip)# write memory Syntax: [no] redistribute < connected | static > Changing the Route Loop Prevention Method RIP can use the following methods to prevent routing loops: ■ Split horizon - the routing switch does not advertise a route on the same interface as the one on which the routing switch learned the route.
IP Routing Features Configuring RIP RIP Information Type Page Redistribute Information 3-39 Restrict Information 3-39 Displaying General RIP Information To display general RIP information, enter show ip rip at any context level. The resulting display will appear similar to the following: Figure 3-7.Example of General RIP Information Listing The display is a summary of Global RIP information, information about interfaces with RIP enabled, and information about RIP peers.
IP Routing Features Configuring RIP ■ Default Metric – Sets the default metric for imported routes. This is the metric that will be advertised with the imported route to other RIP peers. A RIP metric is a measurement used to determine the 'best' path to network; 1 is the best, 15 is the worse, 16 is unreachable. ■ Route changes – The number of times RIP has modified the routing switch’s routing table. ■ Queries – The number of RIP queries that have been received by the routing switch.
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 3-8.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 3-35: 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 3-11. 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 ■ Last update timeticks – How many seconds have passed since the routing switch received an update from this neighbor. 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 Figure 3-13.
IP Routing Features Configuring IRDP The display shows if any routes, identified by the IP Address and Mask fields are being restricted from redistribution. The restrict filters are configured by the router rip restrict command described on page 3-31. 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.
IP Routing Features Configuring IRDP ■ Maximum message interval and minimum message interval - when IRDP is enabled, the routing switch sends the Router Advertisement messages every 450-600 seconds by default. The time within this interval that the routing switch selects is random for each message and is not affected by traffic loads or other network factors. The random interval minimizes the probability that a host will receive Router Advertisement messages from other routers at the same time.
IP Routing Features Configuring IRDP • 3-42 multicast - The routing switch sends Router Advertisements as multi cast packets addressed to IP multicast group 224.0.0.1. This is the default. ■ holdtime < seconds > - This parameter specifies how long a host that receives a Router Advertisement from the routing switch should consider the advertisement to be valid.
IP Routing Features Configuring DHCP Relay Displaying IRDP Information To display IRDP information, enter show ip irdp from any CLI level.
IP Routing Features Configuring DHCP Relay The DHCP relay agent is transparent to both the client and the server. Neither side is aware of the communications that pass through the DHCP relay agent. As DHCP clients broadcast requests, the DHCP relay agent receives the packets and forwards them to the DHCP server. During this process, the DHCP relay agent increases the hop count by one before forwarding the DHCP message to the server.
IP Routing Features Configuring DHCP Relay Enabling DHCP Relay The DHCP Relay function is enabled by default on a ProCurve routing switch.
IP Routing Features Configuring DHCP Relay ProCurve# show config Startup configuration: ; J9146A Configuration Editor; Created on release #W.14.XX 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 Non-Default DHCP Relay and Hop exit Count Increment settings no dhcp-relay no dhcp-relay hop-count-increment Figure 3-16.
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 DHCP Option 82 Option 82 is called the Relay Agent Information option and is inserted by the DHCP relay agent when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing the Relay Agent Information option may use the information to implement IP address or other parameter assignment policies.
IP Routing Features Configuring DHCP Relay Note The routing switch’s DHCP Relay Information (Option 82) feature can be used in networks where the DHCP server(s) are compliant with RFC 3046 Option 82 operation. DHCP Servers that are not compliant with Option 82 operation ignore Option 82 fields. For information on configuring an Option 82 DHCP server, refer to the documentation provided with the server application. Some client applications can append an Option 82 field to their DHCP requests.
IP Routing Features Configuring DHCP Relay Terminology Circuit ID: In Option 82 applications, the number of the port through which the routing switch receives a DHCP client request. On ProCurve fixed-port switches, the Circuit ID of a given port corresponds to the port number appearing on the front of the switch for that port. On ProCurve chassis switches, the port number for a given port corresponds to the internal if Index number for that port.
IP Routing Features Configuring DHCP Relay Secondary Relay Agent: In the path between a DHCP client and a DHCP server, any routing switch (configured to support DHCP operation) other than the primary relay agent. General DHCP Option 82 Requirements and Operation Requirements.
IP Routing Features Configuring DHCP Relay Relay Agent “1” Switch VLAN 4 VLAN 3 Option 82 Enabled Client Switch DHCP Option 82 Server Switch Client Client Client VLAN 3 Client VLAN 2 Relay Agent “3” Option 82 Enabled Client Switch Client Note: DHCP Option 82 does not operate with clients on VLAN 4 because DHCP requests from these clients are not routed. Relay Agent 2 does not add an Option 82 field to client requests before forwarding the requests.
IP Routing Features Configuring DHCP Relay policies supported by the target DHCP server do not distinguish between client requests from ports in different VLANs in the same routing switch) To view the MAC address for a given routing switch, execute the show system-information command in the CLI. Switch MAC Address Figure 3-21.
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 3-23. 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 3-5, below, describes relay agent management of DHCP server responses with optional validation enabled and disabled Table 3-5. Relay Agent Management of DHCP Server Response Packets.
IP Routing Features Configuring DHCP Relay ID option and a DHCP client request packet is received on a multinetted VLAN, the IP address used in the Option 82 field will identify the subnet on which the packet was received instead of the IP address for the VLAN. This enables an Option 82 DHCP server to support more narrowly defined DHCP policy boundaries instead of defining the boundaries at the VLAN or whole routing switch levels.
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 3-6. 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 ■ 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 3-62 ■ 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 3-7. Interface VLAN 1 Example of a UDP Packet-Forwarding Environment 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 3-26.
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 3-43.
Index A D address IP … 3-13 ARP arp-age … 3-10 cache … 3-6 cache table … 3-6 configuring parameters … 3-14 enabling local proxy … 3-17, 3-25 how it works … 3-14 local proxy option … 3-17 proxy … 3-16 assigning IP address … 3-13 auto port setting … 2-5 default route … 3-26 DHCP hop count, displaying … 3-47 DHCP Relay broadcast forwarding … 3-44 configuration … 3-43 enabling … 3-45 helper address … 3-45 minimum requirements … 3-44 Option 82 circuit ID … 3-50, 3-53 packet forwarding … 3-44 See also Option 8
helper address for DHCP Relay … 3-45 hop count in DHCP requests displaying configuration … 3-47 I IANA … 3-68 ICMP configuring … 3-20 disabling messages … 3-20 IGMP benefits … 2-3 configure per VLAN … 2-5 effect on filters … 2-28 Exclude Source … 2-12 Fast Leave … 2-14 high-priority forwarding … 2-5 Include Source … 2-12 IP multicast address range … 2-28 leave group … 2-12 maximum address count … 2-6 multicast group … 2-12 multimedia … 2-3 operation … 2-12, 2-13 port states … 2-5 proxy forward loop … 2-25
L leave group See IGMP. M management VLAN See Option 82. multicast group See IGMP. multimedia See IGMP.
overview … 3-27 parameters and defaults … 3-28 peer information … 3-37 redistribution … 3-32 displaying … 3-39 enabling … 3-32 redistribution filters displaying … 3-39 redistribution into RIP … 3-31 redistribution, configuring … 3-31 restrict filter information … 3-39 restrict redistribution … 3-39 route loop prevention, RIP configuration … 3-33 router ID, changing … 3-13 router, multicast, with IGMP … 2-12 S secondary relay agent … 3-51 setup screen … 1-8 static IP routes configuring … 3-22, 3-24 route ty
© Copyright 2009 Hewlett-Packard Development Company, L.P.
