HP Switch Software Multicast and Routing Guide for K/KA/KB.15.15 Abstract This switch software guide is intended for network administrators and support personnel, and applies to the switch models listed on this page unless otherwise noted. This guide does not provide information about upgrading or replacing switch hardware. The information in this guide is subject to change without notice.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Multimedia Traffic Control with IP Multicast (IGMP).......................................15 Overview..............................................................................................................................15 Enabling IGMP......................................................................................................................15 Configuring and displaying IGMP (CLI).....................................................................................
Enabling multicast routing on the VLAN interface to which the CLI is currently set........................39 Specifying the IP address to use as the source address for PIM protocol packets outbound on the VLAN...............................................................................................................................40 Changing the frequency at which the routing switch transmits PIM hello messages on the current VLAN..........................................................................
Configuring PIM-SM on the router.............................................................................................66 Global configuration context for supporting PIM-SM...............................................................66 Configuring global context commands..................................................................................66 VLAN context commands for configuring PIM-SM........................................................................
Shortest-path tree (SPT).......................................................................................................95 Shortest-path tree operation............................................................................................95 Restricting multicast traffic to RPTs....................................................................................96 Maintaining an active route for multicast group members....................................................
Changing the router ID.....................................................................................................117 Configuring ARP parameters.............................................................................................118 How ARP works..........................................................................................................118 About enabling proxy ARP...........................................................................................
Assigning VLANs and/or subnets to each area....................................................................145 Assigning loopback addresses to an area...........................................................................146 OSPF redistribution of loopback addresses.....................................................................147 Configuring external route redistribution in an OSPF domain (optional)........................................148 Configuring redistribution filters.................
Viewing the current IP load-sharing configuration.................................................................189 Overview of OSPF................................................................................................................189 OSPF router types............................................................................................................190 Interior routers.............................................................................................................
Matching tags.................................................................................................................211 Using set commands.............................................................................................................211 Setting the next hop.........................................................................................................211 Setting the route metric..................................................................................................
User Datagram Protocol.........................................................................246 Configuring and enabling UDP broadcast forwarding...............................................................246 Globally enabling UDP broadcast forwarding.....................................................................246 Configuring UDP broadcast forwarding on individual VLANs.................................................246 Viewing the current IP forward-protocol configuration.................
Owner router..................................................................................................................277 Backup router..................................................................................................................278 VR priority operation...................................................................................................278 Preempt mode............................................................................................................
Enabling event logging.....................................................................................................295 Describing a neighbor......................................................................................................295 Enabling nonstop forwarding for BGP.................................................................................296 Neighbor configuration and neighbor policy configuration........................................................
Configuration procedure..............................................................................................313 Tuning and optimizing BGP networks.................................................................................314 Prerequisites...............................................................................................................314 Configuring a BGP keepalive interval and holdtime.........................................................
1 Multimedia Traffic Control with IP Multicast (IGMP) Overview This chapter describes multimedia traffic control with IP multicast—Internet Group Management Protocol (IGMP) controls—to reduce unnecessary bandwidth usage on a per-port basis, and how to configure it with the switch's built-in interfaces. For general information about IGMP, see “IGMP general operation and features” (page 24). NOTE: For more information, see the Access Security Guide for your switch.
Displays IGMP configuration for a specific VLAN on the switch, including per-port data. For more information, see the Management and Configuration Guide for your switch.
Viewing IGMP high level statistics for all VLANs on the switch Syntax: show ip igmp statistics Example 3 Displaying statistics for IGMP joined groups HP Switch(config)# show ip igmp statistics IGMP Service Statistics Total VLAN's with IGMP enabled: Current count of multicast groups joined: 33 21 IGMP Joined Group Statistics VLAN ID ------1 22 33 VLAN Name -------------------------------DEFAULT_VLAN VLAN-2 VLAN-3 Total -----52 80 1100 Filtered -------50 75 1000 Standard -------0 5 99 Static -----2 0
Example 5 Displaying IGMP groups address information HP Switch(vlan-2)# show ip igmp groups IGMP Group Address Information VLAN ID ------22 22 22 Group Address -------------239.20.255.7 239.20.255.8 239.20.255.9 Expires ------------1h 2m 5s 1h 2m 5s 1h 2m 5s UpTime --------------1h 14m 5s 1h 14m 5s 1h 14m 5s Last Reporter | --------------+ 192.168.0.2 | 192.168.0.2 | 192.168.0.
You can also combine the ip igmp command with other IGMP-related commands, as described in the following sections. Configuring per-port IGMP traffic filters Syntax: vlan vid ip igmp [ auto port-list forward port-list ] | blocked port-list | Used in the VLAN context, specifies how each port should handle IGMP traffic. Default: auto.
This command disables or re-enables the ability for the switch to become querier if necessary. The no version of the command disables the querier function on the switch. The show ip igmp config command displays the current querier command. Default querier capability: Enabled Configuring the querier interval To specify the number of seconds between membership queries, enter this command with the desired interval.
Enables IGMP forced fast-leave on the specified ports in the selected VLAN, even if they are cascaded. The no form of the command disables forced fast-leave on the specified ports in the selected VLAN. Use show running to display the ports per-VLAN on which forced fast-leave is enabled. Default: Disabled show running-config forcedfastleave Displays a non-default IGMP forced fast-leave configuration on a VLAN.
Syntax: [no] igmp filter-unknown-mcast Enables interface isolation for unjoined multicast groups. IGMP is configured so that each interface with IGMP enabled will have a data-driven multicast filter associated with it, preventing unjoined IP multicast packets from being flooded. A reboot is required for the change to take effect. Default: Disabled Configuring IGMP proxy (CLI) For more information on IGMP proxy, see “IGMP general operation and features” (page 24).
Example 10 IGMP proxy border IP address command This example shows the IGMP proxy border IP addrses (111.11.111.111) being configured. HP Switch(config)# igmp-proxy-domain Bob 111.11.111.111 Example 11 Setting the lower and upper bounds for multicasting This example shows the lower and upper boundaries of the multicast address range associated with the domain named Bob. HP Switch(config)# igmp-proxy-domain Bob 111.11.111.111 234.0.0.1 HP Switch(config)# igmp-proxy-domain Bob 111.11.111.111 236.1.1.
Example 12 Showing active IGMP proxy entries HP Switch(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.
querier. If you need to disable the querier feature, do so through the IGMP configuration MIB, see “Configuring the querier function” (page 19). NOTE: IGMP configuration on the switches operates at the VLAN context level. If you are not using VLANs, configure IGMP in VLAN 1 (the default VLAN) context.
group, and all devices in the group use the same multicast group address. The multicast group running version 2 of IGMP uses three fundamental types of messages to communicate: Query A message sent from the querier (multicast router or switch) asking for a response from each host belonging to the multicast group. If a multicast router supporting IGMP is not present, the switch must assume this function to elicit group membership information from the hosts on the network.
Table 1 Comparison of IGMP operation with and without IP addressing IGMP function available with IP addressing configured on the VLAN Available without IP addressing? Operating differences without an IP address 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. Yes None Configure individual ports in the VLAN to Auto (the default)/Blocked, or Forward.
On switches that do not support data-driven IGMP, unregistered multicast groups are flooded to the VLAN rather than pruned. In this scenario, fast-leave IGMP can actually increase the problem of multicast flooding by 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.
the switch automatically retains that IGMP client in its IGMP table and continues forwarding IGMP traffic to the IGMP client until the Querier triggers confirmation that no other group members exist on the same port. This delayed leave operation means that the switch continues to transmit unnecessary multicast traffic through the port until the Querier renews multicast group status.
Figure 3 Example of unknown multicast traffic flooding on all ports connected to a querier for any VLAN In the following example, igmp filter-unknown-mcast has been configured. The multicast traffic only goes to the querier on the same VLAN as the multicast server.
Figure 4 Example of unknown multicast traffic not flooding out ports connected to queriers in separate VLANs To display the status of IGMP multicast filtering use the show ip igmp command. If the IGMP Filter Unknown Multicast setting is different from the IGMP Filter Unknown Multicast status, a reboot is required to activate the desired setting. This setting will then be reflected in the status.
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. See figure “IGMP proxy example” (page 32). 1. Configure Routing Switch 1 with the IGMP proxy forwarding function to forward joins toward Border Router 1; in addition, configure Routing Switch 1 to forward joins from VLAN 1 toward Border Router 2, as is VLAN 4 on Routing Switch 3. 2.
• The domains may have overlapping multicast ranges. • The IP address of the border router may be the same or different in each configured domain. • Duplicate IGMP joins are automatically prevented, or leaves that would remove a flow currently joined by multiple hosts. • Range overlap allows for redundant connectivity and the ability for multicasts to arrive from different border routers based on the shortest path back to the source of the traffic.
Figure 6 Proxy loop scenario About 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 multicastrouter, to act as Querier.
Well-known or reserved multicast addresses excluded 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 predefined host groups.
Syntax: [no] ip arp-mcast-replies Enables or disables accepting multicast MAC addresses in the IP multicast address range in ARP requests and replies.
2 PIM-DM (Dense Mode) For introductory and general information, see the sections beginning with “About PIM-DM” (page 55). Overview This chapter describes protocol-independent multicast (PIM) routing operation on the switches covered in this guide and how to configure it with the switch's built-in interfaces. It is assumed that you have an understanding of multimedia traffic control with IP multicast (IGMP).
[all] Enable/disable all PIM notification traps. [neighbor-loss] Enable/disable the notification trap sent when the timer for a multicast router neighbor expires and the switch has no other multicast router neighbors on the same VLAN with a lower IP address. Default: Disabled [hardware-mrt-full] Enable/disable notification trap when the hardwareMRT is full (2048 active flows.) In this state, any additional flows are handled by the software MRT, which increases processing time for the affected flows.
Example 18 Configuring PIM in the Global and PIM context In Figure 11 (page 58), the "#1" routing switch is directly connected to the multicast sources for the network. For this example, suppose that you are choosing the following: • Reduce the state-refresh time from the default 60 seconds to 30 seconds. (The routing switch transmits state-refresh packets only if it is directly connected to the multicast source.
[no]vlanvidip pim Enables multicast routing on the VLAN interface to which the CLI is currently set. The no form disables PIM on the VLAN.
interval causes it to stop transmitting multicast traffic onto the VLAN sooner, resulting in less unnecessary bandwidth usage. Changing the maximum time in seconds before the routing switch actually transmits the initial PIM hello message on the current VLAN Syntax: ip pim-dense [hello-delay 0-5] vlan [vid]ip pim-dense [hello-delay 0-5] Changes the maximum time in seconds before the routing switch actually transmits the initial PIM hello message on the current VLAN.
NOTE: Not used with the [no] form of the ip pim-dense command. Default: 3 attempts Enabling the LAN prune delay option on the current VLAN Syntax: ip pim-dense [lan-prune-delay] vlan[vid]ip pim-dense [lan-prune-delay] Enables the LAN prune delay option on the current VLAN. With lan-prune-delay enabled, the routing switch informs downstream neighbors how long it will wait before pruning a flow after receiving a prune request.
Example 19 Upstream router prune A network may have multiple routing switches sharing VLAN "X". When an upstream routing switch initially floods traffic from multicast group "X" to VLAN "Y", if one of the routing switches on VLAN "Y" does not want this traffic, it issues a prune response to the upstream neighbor. The upstream neighbor then goes into a prune pending state for group "X" on VLAN "Y". (During this period, the upstream neighbor continues to forward the traffic.
Figure 8 Multicast network with a multinetted VLAN 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.
Figure 9 Multicast routing configuration on switch #1 in Figure 8 (page 44) HP Switch(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.
[Source Address] The unicast address of the flow's source. [neighbor] The IP address of the upstream multicast router interface (VLAN) from which the multicast flow is coming. A blank field indicates that the multicast source is directly connected to the router. [VLAN] The interface on which the router receives the multicast flow.
Example 22 The show ip mroute interface command on routing switch "#2" in Figure 8 (page 44) HP Switch(config)# show ip mroute interface 29 IP Multicast Interface VLAN : 29 Protocol : PIM-DM TTL Threshold : 0 Viewing data for a specified flow (multicast group) Syntax: show ip [mroute] [multicast-ip-addr source-ip-addr] Lists the following data for the specified multicast flow (source-group pair): [Group Address] The multicast group IP address for the specified flow.
For an mroute on an originator router whose flow is no longer active - including mroutes on non-originators whose flow has been pruned — expire time indicates when the mroute entry will eventually be cleared. Multicast Routing Protocol Identifies the multicast routing protocol through which the current flow was learned. Unicast Routing Protocol Identifies the IP routing protocol through which the routing switch learned the upstream interface for the current multicast flow.
[state] Indicates whether the outbound VLAN and next-hop router for the current multicast flow are receiving datagrams. Pruned The routing switch has not detected any joins from the current multicast flow and is not currently forwarding datagrams in the current VLAN. Forwarding The routing switch has received a join for the current multicast flow and is forwarding datagrams in the current VLAN.
Example 23 Output for routing switch "#1" in Figure 8 (page 44) A populated neighbor field indicates that the multicast server is directly connected to the routing switch (neighbor field is highlighted in bold below.) HP Switch(config)# show ip mroute 239.255.255.5 10.27.30.2 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.
Example 24 PIM neighbor output This example simulates output from routing switch “#1” in Figure 8 (page 44). The data identifies the first downstream neighbor (“routing switch #2”.) HP Switch(config)# show ip pim neighbor PIM Neighbors IP Address VLAN Up Time (sec) Expire Time (sec) --------------- ---- ------------------ -----------------10.29.30.
Example 26 Output for routing switch "#1" in Figure 8 (page 44) HP Switch(config)# show ip pim interface 29 PIM Interface VLAN : 29 IP Address : 10.29.30.
Viewing PIM-specific information from the IP multicast routing table (MRT) Syntax: show ip pim [mroute] This command displays exactly the same output as the command show ip [mroute] . Viewing the PIM route entry information for the specified multicast group (flow) Syntax: show ip pim [mroute[multicast-group-address multicast-source-address]] [Group Address] Lists the specified multicast group address. [Source Address] Lists the specified multicast source address.
Example 27 Routing switch "#1" in Figure 8 (page 44) showing a multicast group from a directly connected source HP Switch(config)# show ip pim mroute 239.255.255.1 10.27.30.2 PIM Route Entry Group Address : 239.255.255.1 Source Address : 10.27.30.2 Source Mask : 255.255.255.
Example 28 PIM neighbor output This example simulates output from routing switch “#1” in Figure 8 (page 44). The data identifies the first downstream neighbor (“routing switch #2”.) HP Switch(config)# show ip pim neighbor PIM Neighbors IP Address VLAN Up Time (sec) Expire Time (sec) --------------- ---- ------------------ -----------------10.29.30.
• Static routes • Directly connected interfaces VLAN interface support The MRT supports up to 128 outbound VLANs at any given time. The sum of all outbound VLANs across all current flows on a router may not exceed 128. (A single flow may span one inbound VLAN and up to 128 outbound VLANs, depending on the VLAN memberships of the hosts actively belonging to the flow.) Flow capacity Up to 2048 flows are supported in hardware across a maximum of 128 outbound VLANs.
For the flow of a given multicast group, PIM-DM creates a tree structure between the source and the VLANs where hosts have joined the group, see Figure 10 (page 57). The tree structure consists of: • Extended branches to VLANs with hosts that currently belong to the group. • Pruned branches to VLANs with no hosts that belong to the group.
group "X", in which case the router cancels the prune state and changes the flow to the forwarding state. State-refresh packets and bandwidth conservation A multicast switch, if directly connected to a multicast source (such as a video conference application), periodically transmit state-refresh packets to downstream multicast routers. On routers that have pruned the multicast flow, the state-refresh packets keep the pruned state alive.
NOTE: When you initially enable PIM-DM, it is recommended that you leave the PIM-DM configuration parameters at their default settings. From the default, you can assess performance and make configuration changes when needed. About 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: 3. 4.
IGMP traffic high-priority disabled Enabling IP multicast routing to support PIM-DM operation has the effect of disabling IGMP traffic high-priority, if configured. ACLs and PIM The switch allows ACL filtering on unicast addresses, but not on multicast addresses. Also, an ACL does not take effect on a flow if the flow began before the ACL was configured. When to enable IGMP on a VLAN When PIM is enabled on a VLAN, it is not necessary to also enable IGMP unless there may be joins occurring on that VLAN.
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 [counter] 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. See the Management and Configuration Guide for your switch.
Message Meaning MCAST MAC add for failed (counter) mac-address Indicates a hardware problem. Check the cabling and router ports. Multicast Hardware Failed to Initialize (counter) Indicates a hardware failure that halts hardware processing of PIM traffic. The software will continue to process PIM traffic at a slower rate. Contact your HP customer care center. No IP address configured on VID vlan-id (dup-msg-cnt) PIM has detected a VLAN without an IP address.
Message Meaning or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. • Move some hosts that create multicast demand to another router. Unable to alloc a buf of size bytes for data-flow (counter) Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed.
• ipMRouteInterfaceOutMcastOctets • ipMRouteInterfaceHCInMcastOctets • ipMRouteInterfaceHCOutMcastOctets • ipMRouteBoundaryTable • ipMRouteBoundaryEntry • ipMRouteBoundaryIfIndex • ipMRouteBoundaryAddress • ipMRouteBoundaryAddressMask • ipMRouteBoundaryStatus OBJECT-TYPE • ipMRouteScopeNameTable • ipMRouteScopeNameEntry • ipMRouteScopeNameAddress • ipMRouteScopeNameAddressMask • ipMRouteScopeNameLanguage • ipMRouteScopeNameString • ipMRouteScopeNameDefault • ipMRouteScop
3 PIM-SM (Sparse Mode) For introductory information, see “PIM-SM overview” (page 92). Configuring router protocol independent multicast (PIM) For more information, see “Configuration steps for PIM-SM” (page 101). The following steps configure PIM-SM in the router PIM context (HP Switch(pim)#_): 1. Specify the VLAN interface to advertise as the Bootstrap Router (BSR) candidate and enable the router to advertise itself as a candidate BSR in a PIM-SM domain.
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, it is also necessary to enable IGMP on the VLANs supporting such receivers.
Example 30 Configuring for PIM support at the global level Using the topology (Figure 20 (page 95)), router "B" is directly connected to the DR for multicast group "X." In this case, suppose that you want to globally configure router "B" for PIM operation.
VLAN context commands for configuring PIM-SM PIM-SM must be configured on at least one VLAN in the router before it can be configured as a C-BSR or a C-RP. Enabling or disabling IGMP in a VLAN IGMP must be enabled in VLANs on edge routers where multicast receivers (end points) are connected and will be requesting to join multicast groups. Syntax: [no] ip igmp [no] vlan [vid] ip igmp Enables or disables IGMP operation in the current VLAN.
long to wait for the next hello packet from the router. If another packet does not arrive within that time, the router removes the neighbor adjacency on that VLAN from the routing table, which removes any flows running on that interface. Shortening the hello interval reduces the hello hold time. This changes how quickly other routers will stop sending traffic to the router if they do not receive a new hello packet when expected.
Changing the Lan-prune-delay interval Syntax: ip pim-sparse vlan [vid] ip ip pim-sparse vlan [vid] ip propagation-delay [250-2000] pim-sparse propagation-delay [250-2000] override-interval [500-6000] 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 downstream for a particular multicast group.
is configured with only one IP address—120-10.10.2—it is this address that will be used for the source.) • Increasing the DR priority on this VLAN from the default 1 to 100. • Leaving the other per-VLAN PIM-SM fields in their default settings.
router pim bsr-candidate Disables or re-enables the router for advertising itself as a Candidate-BSR on the VLAN interface specified by source-ip-vlan [vid]. This command is used to disable and re-enable BSR candidate operation after the bsr-candidate source-ip-vlan [vid] command has been used to enable C-BSR operation on the router. (This command operates only after the BSR source-ip-VLAN ID has been configured.
[no] 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 hold-time settings (range of 30 to 255; default 150) configured in the RPs operating in the domain.
Additionally, the following commands may be required: • To later add to or change multicast groups, or to delete multicast groups, use the command rp-candidate group-prefix [group-addr | group-mask]. • To disable C-RP operation without removing the current CRP configuration, use the command no rp-candidate. • The no form of these commands: ◦ Deletes the RP source IP VLAN configuration. ◦ Deletes the multicast group assignments configured on the router for this RP.
Syntax: [no]rp-candidate Enables C-RP operation on the router. Requires that the source IP VLAN is currently configured, but disabled. The no form of the command disables the currently configured C-RP operation, but does not change the configured C-RP settings. Adding or deleting a multicast group address Use this command if you need to modify the multicast address group configuration for a C-RP on the router.
Enables and disables the following PIM SNMP traps: all Enable/Disable all PIM notification traps. (Default: Disabled) neighbor-loss Enable/Disable the notification trap sent when the timer for a multicast router neighbor expires and the switch has no other multicast router neighbors on the same VLAN with a lower IP address. (Default: Disabled) hardware-mrt-full Enable/Disable notification trap sent when the hardware multicast routing table (MRT) is full (2048 active flows.
Statically configuring an RP to accept multicast traffic A given static RP entry should be manually configured on all routers in the PIM-SM domain. 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] [overide] [rp-ip-addr] Statically specifies the IP address of the interface to use as an RP. Up to eight static RP IP addresses can be configured.
Figure 15 Example of enabling PIM-SM in the router PIM context Enters Router PIM context. Configures and automatically enables C-BSR operation for all possible groups (224.0.0.0/4). Removes support for the default group entry for all possible groups (224.0.0.0/4). Configures staticRP support with override. HP Switch(config)# router pim HP Switch(pim)# bsr-candidate source-ip-vlan 120 HP Switch(pim)# rp-candidate source-ip-vlan 120 HP Switch(pim)# rp-candidate group-prefix 231.128.64.
Syntax: [no] rpf-override [source-ip-addr/mask-length] [rpf-ip-addr] Add, edit, or delete up to eight RPF override entries. The multicast RPF override has a multicast source address [source-ip-addr/mask-length] and an RPF address [rpf-ip-addr] pair. The no form of the command deletes the RPF override. NOTE: Only host-specific addresses are supported (i.e. “/32” addresses.) [source-ip-addr] The IPv4 address of the host from which the multicast flow originated.
Example 39 Displaying the configured RPF overrides HP Switch(config)# show ip pim rpf-override Static RPF Override Multicast Source RPF IP Address ------------------- --------------10.1.1.1/32 11.2.2.1 13.1.1.1/32 12.1.1.1 Example 40 Specifying the source parameter to troubleshoot misconfigurations HP Switch(pim)# show ip pim rpf-override source 10.1.1.1 Static RPF Override Multicast Source RPF IP Address ------------------- --------------10.1.1.1/32 11.2.2.
Example 41 Showing source-DR PIM router Source-DR PIM router. A flow's Neighbor field is empty for a PIM Router with a directly connected source. HP Switch(config)# show ip mroute IP Multicast Route Entries Total number of entries : 1 Group Address Source Address Neighbor VLAN --------------- --------------- ---------------- ---239.255.11.1 10.0.0.10 20 Example 42 Showing intermediate PIM router Flows show their adjacent PIM neighbor towards the source.
Up time (sec) The elapsed time in seconds since the router learned the information for the current instance of the indicated multicast flow. Note that on an Originator router when a forwarding flow moves to a non-forwarding state (i.e. when pruned) the Up time value for that flow is reset to 0.
it is the best path, and the specified multicast group traffic will flow through the router. RPT-tree A Yes setting indicates the route is using the RPT. A No setting indicates the route is using the applicable SPT.
Example 44 Route entry data for a specific multicast group The neighbor field indicates that the router is receiving multicast traffic from a neighboring PIM router. A blank neighbor field indicates that the multicast source is directly connected to the router instead of another PIM router. HP Switch(config)# show ip mroute 239.255.12.42 10.0.0.10 IP Multicast Route Entry Group Address : 239.255.12.42 Source Address : 10.0.0.
Viewing the current PIM status and global configuration Syntax: show ip pim Displays PIM status and global parameters. PIM Status Shows either Enabled or Disabled. Applies only to PIM-DM operation. State Refresh Interval (sec) Join/Prune Interval SPT Threshold Indicates the frequency with which the router transmits join and prune messages for the multicast groups the router is forwarding.
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. Example 47 Two configured PIM interfaces HP Switch(config)# show ip pim interface PIM Interfaces VLAN IP Address Mode ---- --------------- -----------1 10.1.10.1 sparse 2 10.2.10.
Example 48 Showing a PIM-SM interface configured on VLAN 1 HP Switch(config)# show ip pim interface 1 PIM Interface VLAN : 1 IP Address : 10.1.10.1 Mode : sparse Designated Router : 10.1.10.
Example 49 Listing of all PIM neighbors detected HP Switch(config)# show ip pim neighbor PIM Neighbors IP Address --------------10.10.10.2 10.20.10.1 VLAN ---100 200 Up Time (sec) ---------------348 410 Expire Time (sec) ---------------90 97 DR Priority ---------1 1 Syntax: show ip pim neighbor [ip-address] Lists the same information as show ip pim neighbor. See “Displaying PIM neighbor data” (page 87). Example 50 Output for a specific PIM neighbor HP Switch(config)# show ip pim neighbor 10.10.10.
Incoming VLAN VLAN ID from which a join request is received. Source IPv4 Address IP address of the source of multicast traffic in an (S,G) group. Displaying BSR data The router provides BSR information through both IP PIM and the running configuration.
Figure 17 Non-default BSR configuration listing Displaying the current RP set The BSR sends periodic RP updates to all C-RPs in the domain. These updates include the set of multicast group data configured on and reported by all C-RPs in the domain. This data does not include any static RP entries configured on any router in the domain. (To view the static RP-set information for any static RPs configured on a particular router, you must access the CLI of that specific router.
Example 51 Listing both the learned and static RP-set data HP Switch(config)# show ip pim rp-set Status and Counters - PIM-SM Static RP-Set Information Group Address Group Mask RP Address Override --------------- --------------- --------------- -------231.100.128.255 255.255.255.255 100.10.10.1 Yes Status and Counters - PIM-SM Learned RP-Set Information The static RP-set applies only to the current routing switch.
Example 54 Listing for a router that is not configured as a C-RP HP Switch(pim)# show ip pim rp-candidate This system is not a Candidate-RP Example 55 Full C-RP configuration listing HP Switch(pim)# show ip pim rp-candidate config Status and Counters - PIM-SM C-RP Information Status Line Configuration C-RP C-RP C-RP C-RP C-RP C-RP Admin Status Address Hold Time Advertise Period Priority Source IP VLAN : : : : : : This system is not a C-RP 120.10.10.
Protocol Independent Multicast (PIM) is a family of routing protocols that form multicast trees to forward traffic from multicast sources to subnets that have used a protocol such as IGMP to request the traffic. PIM relies on the unicast routing tables created by any of several unicast routing protocols to identify the path back to a multicast source (reverse path forwarding, or RPF.) With this information, PIM sets up the distribution tree for the multicast traffic.
VRRP: PIM-SM is fully interoperable with VRRP to quickly transition multicast routes in the event of a failover. MIB support on the switches covered PIM-SM supports the Protocol Independent Multicast MIB for in this guide: IPv4 (RFC 2934.) With some exceptions, PIM-SM supports the parts of the multicast routing MIB (RFC 2932) applicable to PIM-SM operation. PIM draft specifications: Compatible with PIM-SM specification ( RFC 4061.
Figure 19 Example PIM-SM domain with RPT active to support a host joining a multicast group 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". (Note that any router configured in the domain as a BSR candidate can be elected as the BSR.
Restricting multicast traffic to RPTs An alternate method to allowing the domain to use SPTs is to configure all of the routers in the domain to use only RPTs. However, doing so can increase the traffic load in the network and cause delays in packet delivery. Maintaining an active route for multicast group members The edge router itself and any intervening routers on the active tree between the members (receivers) of a multicast group and the DR for that group, send periodic joins.
If it is necessary to prevent a router from operating as a DR on a given VLAN, disable DR operation by configuring the DR priority as zero (0.) BSR Before a DR can forward encapsulated packets for a specific multicast group to an RP, it must know which router in the domain is the elected RP for that multicast group. The BSR function enables this operation by doing the following: 1. Learns the group-to-RP mappings on the C-RPs in the domain by reading the periodic advertisements each one sends to the BSR.
Intermediate routers are on the path between edge routers and the RP. This is known as a RP Tree (RPT) where only the multicast address appears in the routing table. For example: ( *, G ), where: * = a variable (wildcard) representing the IP address of any multicast source G = a particular multicast group address. NOTE: The software supports up to 100 RPs in a given PIM-SM domain.
4. that candidate is selected to support the group. Apply step 4 of this procedure if the hash function matches the longest mask length to multiple RP candidates. The C-RP having the highest IP address is selected to support the group. NOTE: In a PIM-SM domain where there are overlapping ranges of multicast groups configured on the C-RPs, discrete ranges of these groups are assigned to the domain's C-RPs in blocks of sequential group numbers.
NOTE: While the use of C-RPs and a BSR enable a dynamic selection of RPs for the multicast group traffic in a network, using static RPs involves manually configuring all routers in the domain to be aware of each static RP. This can increase the possibility of multicast traffic failure from to misconfigurations within the PIM-SM domain. Also, because a BSR does not administer static RPs, troubleshooting PIM-SM traffic problems can become more complex.
The SPT policy should be the same for all RPs in a domain. Allowing some RPs to remain configured to implement SPTs while configuring other RPs in the same domain to force RPT use can result in unstable traffic flows. (Use the [no] ip pim-sparse spt-threshold command to change between SPT and RPT operation on each router.) Application of RPs to multicast groups. In a PIM-SM domain, a given multicast group or range of groups can be supported by only one RP.
Per-router global configuration context Use these steps to enable routing and PIM operation in the global configuration context of each PIM-SM router (HP(config)#_): 1. Enable routing. (Use ip routing.) 2. Enable multicast routing. (Use ip multicast-routing.) 3. Enable PIM. (Use router pim.) 4. Configure the routing method(s) needed to reach the interfaces (VLANs) on which you want multicast traffic available for multicast receivers in your network: • Enable RIP or OSPF.
4. Option: Change one or more of the traffic control settings for the pim-sparse of a given VLAN on which PIM-SM is enabled. (Note that some VLAN context control settings apply to both PIM-SM and PIM-DM). Features accessed in VLAN- vid -pim-sparse context Operation ip-addr(page 68) Sets or resets the source IP address for PIM-SM packets sent out on the interface. Also enables PIM-SM on the interface.
Table 7 Options Accessed in Router PIM Context 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 C-RP router to be operative. (Default: 150; 0 if router is not a candidate.) rp-candidate priority 0-255 Changes the priority for the C-RP router.
Event log messages Message Meaning multicast-addr / mask address and mask. Inconsistent The mask entered for the specified multicast address does not specify sufficient bits to include the nonzero bits in the mask. pkt-type pkt, src IP [ip-addr] vid [vid-#] (not a nbr) A PIM packet was received that does not have a neighbor.. Bad parameter-name in pkt-type pkt from IP ip-addr The PIM packet was dropped because of a bad parameter in the packet from the IP address shown.
Message Meaning Inconsistent address and mask The group prefix needs a route/mask entry. For example, if you want, 224.x.x.x/4, you input 224.0.0.0/4. Pkt dropped from vid-# Received a packet from the indicated IP address and VLAN, and dropped it. ip-addr reason, vid ip-addr A packet arrived from the indicated IP address with a checksum error. Pkt rcvd with a cksum error from There was an error regarding the PIM socket, either on a sockopt call or a recvfrom call.
4 Routing Basics For an overiew of IP routing, see “Overview of IP routing” (page 111). Viewing the IP route table The IP route table is displayed by entering the CLI command show ip route from any context level in the console CLI. Here is an example of an entry in the IP route table: Increasing ARP age timeout (CLI) The address resolution protocol (ARP) age is the amount of time the switch keeps a MAC address learned through ARP in the ARP cache.
Example 56 Setting the ARP age timeout to 1000 minutes HP Switch(config)# ip arp-age 1000 Example 57 Show IP command displaying ARP age To view the value of ARP age timer, enter the show ip command. The Arp Age time value is shown in bold below. HP Switch(config)# show ip Internet (IP) Service IP Routing : Disabled Default Gateway : 15.255.120.
Example 59 Menu interface displaying the ARP age value Reconfiguring the router ID (optional) If you want to change the router ID setting, do the following: 1. Go to the global config context; the CLI prompt appears similar to the following: HP Switch(config)#_ 2. 3. 4. If OSPF is not enabled, go to step 3 (page 109); if OSPF is enabled, use no router ospf to disable OSPF operation. Use ip router-id ip-addr to specify a new router ID. (This IP address must be unique in the routing switch configuration.
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. NOTE: Internet control message protocol (ICMP) redirects are disabled on interfaces on which local proxy ARP is enabled.
HP software makes the forwarding decision based on the routing switch's knowledge of the destination network prefix. Routers cannot determine that a message is unicast or directed broadcast apart from the destination network prefix. The decision to forward or not forward the message is by definition only possible in the last-hop router.
DHCP Relay Allows you to extend the service range of your DHCP server beyond its single local network segment License requirements: In the 3500, 3500yl, 5400zl, 6600, and 8200zl switches, OSPF is included with the Premium License. In the 6200yl switches, this feature is included with the base feature set. Throughout this chapter, the switches are referred to as "routing switches." When IP routing is enabled on your switch, it behaves just like any other IP router.
Example 61 ARP cache dynamic entry 1 IP Address 207.95.6.102 MAC Address 0800.5afc.ea21 Type Dynamic Port 6 Each entry contains the destination device's IP address and MAC address. To configure other ARP parameters, see “Configuring ARP parameters” (page 118). IP route table The IP route table contains routing paths to IP destinations. NOTE: The default gateway, which you specify when you configure the basic IP information on the switch, is used only when routing is not enabled on the switch.
Example 63 IP route summary display HP Switch(config)# show ip route summary IPv4 Route Table Summary Protocol --------Connected Static Active Routes ------------1 1 To configure a static IP route, see “Static Routing” (page 122). IP forwarding cache The IP forwarding cache provides a fast-path mechanism for forwarding IP packets. The cache contains entries for IP destinations.
Table 8 IP global parameters for routing switches Parameter Description Default See page Router ID The value that routers use to identify themselves to other routers when exchanging route information. OSPF uses the router ID to identify routers. The lowest-numbered IP address configured on the lowest-numbered routing interface. 117 Enabled 118 RIP does not use the router ID.
Table 8 IP global parameters for routing switches (continued) Parameter Description Default See page NOTE: You also can enable or disable this parameter on an individual interface basis. See Table 9 (page 116). ICMP Router Discovery Protocol (IRDP) An IP protocol that a router Disabled can use to advertise the IP addresses of its router interfaces to directly attached hosts. You can enable or disable the protocol at the Global CLI Config level.
Table 9 IP interface parameters — routing switches (continued) Parameter Description Default ICMP Router Discovery Protocol (IRDP) Locally overrides the global IRDP settings. Disabled IP helper address The IP address of a UDP None configured application server (such as a BootP or DHCP server) or a directed broadcast address. IP helper addresses allow the routing switch to forward requests for certain UDP applications from a client on one subnet to a server on another subnet.
Figure 21 Example of show ip ospf command with router ID displayed Configuring ARP parameters ARP is a standard IP protocol that enables an IP routing switch to obtain the MAC address of another device's interface when the routing switch knows the IP address of the interface. ARP is enabled by default and cannot be disabled.
age, the entry times out and the software removes the entry from the table. Static entries do not age-out and can be removed only by you. • If the ARP cache does not contain an entry for the destination IP address, the routing switch broadcasts an ARP request out all of its IP interfaces. The ARP request contains the IP address of the destination. If the device with the IP address is directly attached to the routing switch, the device sends an ARP response containing its MAC address.
When proxy ARP is enabled, all valid ARP requests receive a response if the following conditions are met: • There is a route to the target IP address in the ARP request (this can be a route or default route), and the VLAN (interface) the ARP request is received on does NOT match the interface for the next hop in the matched route to get to the target IP address.
Disabling ICMP destination unreachable messages By default, when a HP 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: Administration The packet was dropped by the HP device due to a filter or ACL configured on the device.
5 Static Routing This chapter describes how to add static and null routes to the IP route table.
tag Specifies a unique integer value for a given ECMP set (destination, metric, distance.) name Assigns a name to a static route. The no form of the command deletes the specified route for the specified destination next-hop pair.
Configuring an IPv6 Route Syntax: [no] ipv6 route dest-ip-addr / prefix-length [ next-hop-gateway-addr | vlan vid | tunnel tunnel-id|blackhole|reject ] [metric metric] [distance1-255] [tag-value tagval] [name ] dest-ipv6-addr / The network prefix for the destination IPv6 address. prefix-length next-hop-gateway-addr|vlan The gateway for reaching the destination.
Figure 27 Output for Unnamed Static Routes in IPv6 Figure 28 Output for Named Static Routes in IPv6 Figure 29 Output for a Specified Named Static Route in IPv6 Figure 30 Detailed Output of Named Static Routes in IPv6 Configuring an IPv6 Route 125
Viewing static route information The show ip route static command displays the current static route configuration on the routing switch. Example 64 (page 128) shows the configuration resulting from the static routes configured in the example above. Example: Figure 31 Displaying the currently configured static routes Configuring the default route You can also assign the default route and enter it in the routing table.
Other sources of routes in the routing table The IP route table can also receive routes from the following 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.
Configuring equal cost multi-path (ECMP) routing for static IP routes ECMP routing allows multiple entries for routes to the same destination. Each path has the same cost as the other paths, but a different next-hop router. The ip load-sharing command specifies the maximum number of equal paths that can be configured. Values range from 2 to 4.
6 Routing Information Protocol To display RIP configuration information and statistics, see “Overview of RIP” (page 137). For more information on configuring RIP, see “Viewing RIP information” (page 133). Configuring RIP parameters Use the following procedures to configure RIP parameters on a system-wide and individual VLAN interface basis. Enabling RIP RIP is disabled by default. To enable it, use one of the following methods. When you enable RIP, the default RIP version is RIPv2-only.
Example Example 65 Enter RIP router context HP Switch(config)# router rip HP Switch(rip)# Example 66 Enable RIP routing HP Switch(config)# router rip enable HP Switch(rip)# Example 67 Disable RIP routing HP Switch(config)# router rip disable HP Switch(rip)# Example 68 Delete all protocol-specific information from the global context and interface context and set all protocol parameters to default values HP Switch(config)# no router rip HP Switch(rip)# Enabling IP RIP on a VLAN To enable RIP on all IP add
To change the RIP type supported on a VLAN interface, enter commands such as the following: HP HP HP HP Switch(config)# Switch(vlan-1)# Switch(vlan-1)# Switch(config)# vlan 1 ip rip v1-only exit write memory Changing the cost of routes learned on a VLAN interface By default, the switch interface increases the cost of an RIP route that is learned on the interface. The switch increases the cost by adding one to the route's metric before storing the route.
Modifying default metric for redistribution The default metric is a global parameter that specifies the cost applied to all RIP routes by default. The default value is 1. You can assign a cost from 1 to 15. Syntax: default-metric value The value can be from 1 to 15. The default is 1.
Syntax: [no] ip rip poison-reverse Poison reverse is enabled by default. Disabling Poison reverse causes the routing switch to revert to Split horizon. (Poison reverse is an extension of Split horizon.) To disable Poison reverse on an interface, and thereby enable Split horizon, enter the following: HP Switch(config)# vlan 1 HP Switch(vlan-1)# no ip rip poison-reverse Entering the command without the no option re-enables Poison reverse.
Auto-summary Status of auto-summary for all interfaces running RIP. If auto-summary is enabled, subnets will be summarized to a class network when advertising outside of the given network. 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 worst, 16 is unreachable.
Syntax: show ip rip interface [ ip-addr | vlan vlan-id ] The resulting display will appear similar to the following: HP Switch(config)# show ip rip interface RIP interface information IP Address Auth ------------------------- ---100.1.0.1 none 100.2.0.1 none 100.3.0.1 none 100.4.0.
Example: Example 71 Example of show IP rip interface output by IP address To show the RIP interface information for the interface with IP address 100.2.0.1, enter the show ip rip interface command: HP Switch# show ip rip interface 100.2.0.1 RIP interface information for 100.2.0.1 IP Address : 100.2.0.
Viewing RIP redistribution information To display RIP redistribution information, enter the show ip rip redistribute command at any context level: Example 74 Example of show IP rip redistribute output HP Switch# show ip rip redistribute RIP redistributing Route type --------connected static ospf Status -----enabled disabled disabled RIP automatically redistributes connected routes that are configured on interfaces that are running RIP and all routes that are learned via RIP.
with a higher cost is considered unreachable. Although limiting to larger networks, the low maximum hop count prevents endless loops in the network.
Table 11 RIP interface parameters (continued) Parameter Description Default loop prevention The method the routing switch uses to Poison reverse prevent routing loops caused by advertising a route on the same interface as the one on which the routing switch learned the route: • 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.
7 Open Shortest Path First Protocol (OSPF) OSPFv2 is the IPv4 implementation of the Open Shortest Path First protocol. (OSPFv3 is the IPv6 implementation of this protocol.) Beginning with software version K.15.01, the switches can be configured to run OSPFv2 either alone or simultaneously with OSPFv3. (OSPFv2 and OSPFv3 run as independent protocols on the switch and do not have any interaction when run simultaneously.) For overview information on OSPF, see “Overview of OSPF” (page 189).
Example Example 76 To enter the OSPF router context HP Switch(config)#router ospf HP Switch(ospf)# Example 77 To enable OSPF routing HP Switch(config)#router ospf enable HP Switch(ospf)# Example 78 To disable OSPF routing HP Switch(config)#router ospf disable HP Switch(ospf)# NOTE: The no router ospf enable command also disables OSPF routing. To delete all protocol-specific information from the global context and interface context and set all protocol parameters to default values.
Figure 32 Changing external route preference compatibility from RFC 1583 to RFC 2328 HP Switch(config)# router ospf HP Switch(ospf)# no rfc1583-compatibility HP Switch_8212(ospf)# show ip ospf general OSPF General Status OSPF protocol Router ID RFC 1583 compatibility : enabled : 10.10.51.1 : non-compatible Intra-area distance Inter-area distance AS-external distance : 110 : 110 : 110 Changes external route preference setting and displays new setting.
backbone Assigns the routing switch to the backbone area and automatically assigns an area ID of0.0.0.0 and an area type of normal. Using 0 or 0.0.0.0 with the above ospf-area-id option achieves the same result. The backbone area is automatically configured as a normal area type. Example To configure a backbone and a normal area with an ID of "1" (0.0.0.
from the backbone into the area (included in the metric-type operation described below.) Default: Disabled For more information, see “Not-so-stubby-area (NSSA)” (page 194), “Stub area” (page 194), and “Replacing type-3summary LSAs and type-7 default external LSAs with a type-3 default route LSA” (page 196). [metric-type[ type1 | type2 Used in NSSA ABRs only. ]] Enables injection of the type-7 default external route and type-3 summary routes into the area instead of a type 3 default route.
Figure 33 Creating stub area and NSSA assignments Assigning VLANs and/or subnets to each area After you define an OSPF area (page A-25), you can assign one or more VLANs and/or subnets to it. When a VLAN is assigned to an area, all currently configured IP addresses in that VLAN are automatically included in the assignment unless you enter a specific IP address. NOTE: All static VLANs configured on a routing switch configured for OSPF must be assigned to one of the defined areas in the AS.
NOTE: If you add a new subnet IP address to a VLAN after assigning the VLAN to an OSPF area, you must also assign the new subnet to an area: • If all subnets in the VLAN should be assigned to the same area, just execute ip ospf area ospf-area-id . • But if different subnets belong in different areas, you must explicitly assign the new subnet to the desired area. Also, to assign a VLAN to an OSPF area, the VLAN must be configured with at least one IP address.
You can enter a value for the OSPF area in the format of an IP address or a number in the range 0 to 4,294,967,295. Example: To assign user-defined loopback interface 3 on the switch to area 192.5.0.0 and include the loopback IP address 172.16.112.2 in the OSPF broadcast area, enter the following commands: HP Switch(config)# interface loopback 3 HP Switch(lo-3)# ip ospf 172.16.112.2 area 192.5.0.
Example Example 79 Assigning loopback IP addresses to OSPF areas The loopback IP address 13.3.4.5 of loopback 2 is advertised only in OSPF area 0.0.0.111. The IP addresses 14.2.3.4 and 15.2.3.4 of loopback 1 are advertised in all OSPF areas. The lines in bold below show that the IP address of loopback interface 2 is assigned to OSPF area 111. HP HP HP HP HP HP HP HP Switch(config)# interface loopback 1 Switch(lo-1)# ip address 14.2.3.4 Switch(lo-1)# ip address 15.2.3.
Enabling route redistribution This step enables ASBR operation on a routing switch, and must be executed on each routing switch connected to external routes you want to redistribute in your OSPF domain. The basic form of the redistribute command redistributes all routes of the selected type. For finer control over route selection and modification of route properties, you can specify the route-map parameter and the name of a route map.
Modifying the redistribution metric type Optional: 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.
which routes to select for either summarizing or blocking. For example, a range of 10.10.32.1/14 specifies all routes in the range of 10.10.32.1 - 10.10.35.254. [no-advertise] Use this keyword only if you want to configure the ABR to prevent advertisement to the backbone of a specified range of routes. (This has the effect of "hiding" the specified range from the backbone area.
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.) If no-advertise is not used in the command, the selected routes learned from type-7 LSAs in the area are summarized to the backbone in a type-5 LSA. [cost 1-16777215] User configured cost for an NSSA summary range. If cost is not configured, the ABR will use the algorithm defined in RFC 3101 to compute the cost and metric-type of the summarized route.
Example 81 Setting a summary cost to an area This example shows how to set the summary cost to 100 for area 10 with an address range of 10.10.0.0/16. HP Switch(ospf)# area 10 range 10.10.0.0/16 type summary cost 100 Example 82 Using a standard summary cost for an area This example shows how to use the standard method for determining the summarized cost. HP Switch(ospf)# area 10 range 10.10.0.0/16 type summary You must execute write mem to preserve these settings across reboots.
Example 88 Defining a range of internal routes to block from advertising to the backbone For the same range of routes, you can use either of the following commands to block injection of a range of summary routes (type-3 LSAs) from area 30 into the backbone. HP Switch(config)# area 30 range 10.0.0.0/8 type no-advertise HP Switch(config)# area 30 range 10.0.0.
Table “OSPF traps and associated MIB objects” (page 155) summarizes OSPF traps supported on the switches, and their associated MIB objects from RFC 1850.
ip ospf cost 1-65535 Assigns the specified cost to all networks configured on the VLAN. ip ospf ip-address cost 1-65535 Assigns the specified cost to the specified subnet on the VLAN. ip ospf all cost 1-65535 Assigns the specified cost to all networks configured on the VLAN. (Operates the same as the ip ospf cost option, above.
The value can be from 0 to 255 (with 255 as the highest priority.) If you set the priority to 0, the routing switch does not participate in DR and BDR election. Allows different settings for different subnet interfaces in the VLAN. ip ospf priority 1-255 Assigns the specified priority to all networks configured on the VLAN. ip ospf ip-address priority Assigns the specified priority to the specified subnet on the VLAN.
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 “Reconfiguring per-interface settings in a multinetted VLAN” (page 158).
Use show ip ospf interface ip-address to view the current authentication setting. NOTE: To replace the password method with the MD5 method on a given interface, overwrite the password configuration by using the MD5 form of the command shown in the next syntax description. (It is not necessary to disable the currently configured OSPF password.
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-address On an ABR directly connected to the backbone area, this value must be the IP address of an ABR (in the same area) needing a virtual link to the backbone area as a substitute for a direct physical connection.
Changing the dead interval on a virtual link For more information, see “Adjusting virtual link performance by changing the interface settings” (page 203). 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.
Changing the retransmitting 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 LSA retransmissions on the virtual link. The retransmit-interval setting must be the same on both ABRs on a given virtual link. This value is also used when retransmitting database description and link-state request packets.
HP Switch(ospf)# area 1 virtual-link 10.0.0.1 hello-interval 60 Configuring OSPF authentication on a virtual link For more information, see “Configuring OSPF authentication on a virtual link” (page 203). Authenticating the OSPF password on a virtual link Syntax: area area-id virtual-link ip-addr authentication-key key-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.
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. If it is not present, the packet is dropped. To disable MD5 authentication on an ABR interface used for a virtual link, use the no form of the command.
Example 91 show ip ospf interface command with passive configured on an interface HP Switch(vlan-1)# show ip ospf interface OSPF Interface Status IP Address ---------10.10.10.1 10.12.13.1 Status -----enabled enabled Area ID ------0.0.0.2 0.0.0.2 State ----down wait Auth-type --------none none Cost ---1 1 Priority -------1 1 Passive ------Yes No You can display the OSPF passive information for a particular VLAN, as shown in Example 92 (page 165).
Example Example 93 SPF throttling configuration The last SPF calculation was scheduled and triggered at the 100th second. A new topology event occurred at the 104th second.
Example 94 General output for the show ip ospf command HP Switch(config)# show ip ospf general OSPF General Status OSPF protocol : enabled Router ID : 17.255.134.
The following fields are shown in the OSPF general status display: Table 13 CLI display of OSPF general information Field Content OSPF protocol Whether OSPF is currently enabled. Router ID Router ID that this routing switch is currently using to identify itself. RFC 1583 compatibility Whether the routing switch is currently using RFC 1583 (compatible) or RFC 2328 (non-compatible rules for calculating external routes. Intra-area distance Administrative distance for routes within OSPF areas.
Table 14 CLI display of OSPF area information (continued) Field Content Cost Metric for the default route that the routing switch will inject into a stub area if the routing switch is an ABR for the area. This value applies only to stub areas. SPFR Number of times the routing switch has run the shortest path first route calculation for this area. ABR Number of area border routers in this area. ASBR Number of autonomous system border routers in this area.
Table 15 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. Sequence # Sequence number of the current instance of this LSA. Chksum(Hex) LSA checksum value.
ip-address Displays the OSPF interface information for the specified IP address. vlan-id Displays the OSPF interface information for the specified IP address. Table 16 (page 171) shows the information displayed for the OSPF interface. Table 16 CLI display of OSPF interface information Field Content IP Address The local IP address for this interface. Status enabled or disabled—Whether OSPF is currently enabled on this interface. Area ID The ID of the area that this interface is in.
Example Example 98 Output for show ip ospf interface HP Switch# show ip ospf interface OSPF Interface Status IP Address --------------10.3.18.36 10.3.53.36 Status -------enabled enabled Area ID -------------10.3.16.0 10.3.48.0 State ------DOWN BDR Auth-type --------none none Cost -----1 1 Pri --1 1 Passive ------no no Example 99 OSPF interface configuration Admin IP Address Area ID Status Type --------------- --------------- -------- -------172.16.30.
Example Example 100 show ip ospf interface ip-addr output HP Switch(ospf)# sho ip ospf int 10.10.50.1 OSPF Interface Status for 10.3.1836 IP Address Area ID : 10.3.18.36 : 10.3.16.0 State : BDR Cost : 1 Type : BCAST Status : enabled Auth-type : none Chain : Priority : 1 Transit Delay Hello Interval Designated Router Backup Desig. Rtr Backup Desig. Rtr : : : : : 1 10 10.3.18.34 10.3.18.36 10.3.18.
Example 103 show ip ospf neighbor detail HP-E5406zl(vlan-1)# show ip ospf neighbor detail OSPF Neighbor Information for neighbor 10.2.1.2 IP Address Router ID Interface Area Priority Options Events : : : : : : : 10.2.1.2 2.2.2.2 vlan-1 backbone n/a 0x42 7 State Designated Router Backup Designated Router Retransmit Queue Length Neighbor Uptime Dead Timer Expires : : : : : : FULL n/a n/a 0 0h:0m:14s 35 sec Example 104 Show ip ospf neighbor detail HP-E5406zl(vlan-1)# show ip ospf neighbor 10.2.1.
Example 106 Displaying OSPF statistics for VLAN traffic HP Switch(ospf)# show ip ospf statistics vlan 1 OSPF statistics for VLAN 1 OSPF Interface Status for 10.0.0.
Table 19 CLI display of OSPF statistics for VLAN subnet traffic (continued) Per-subnet OSPF statistics Field Content Total Rx Total number of OSPF packets received on each subnet interface. Total Errors Total number of errors in OSPF packet transmission on each subnet interface. Clearing OSPF statistics for all VLAN interfaces on the switch Syntax: clear ip ospf statistics Clears the OSPF statistics for all VLAN interfaces on the switch and sets all VLAN/subnet counters for OSPF traffic to zero.
router-id ip-addr Used to restrict display of LSA database or advertisements to show only the data from sources having the specified router ID. Can also be used with other subset options ( ospf-area-id, link-state-id, sequence-number, and type) to further define the source of displayed information. sequence-number integer Used to restrict display of LSA database or advertisements to show only the data from sources having the specified sequence number.
Example 108 show ip ospf link-state output OSPF Link State Database for Area 0.0.0.0 LSA Type ---------Router Router Network Summary Summary Summary Summary AsbSummary Advertising Router ID --------------10.0.8.32 10.0.8.33 10.0.8.37 10.0.8.33 10.0.8.35 10.0.8.33 10.0.8.35 10.0.8.33 Link State ID --------------10.0.8.32 10.0.8.33 10.3.2.37 10.3.16.0 10.3.16.0 10.3.17.0 10.3.17.0 10.0.8.
Example 109 Output for show ip ospf link-state advertise HP Switch(config)# show ip ospf link-state advertise OSPF Link State Database for Area 0.0.0.0 Advertisements -----------------------------------------------------------------------000202010a0008200a00082080000281a7b60054000000050a030e00ffffff0003000001... 000202010a0008210a00082180000006a5c90024010000010a0008230a03112104000002 000102010a0008230a00082380000015755d006c010000070a030600ffffff0003000001...
Example 111 Output for show IP OSPF link-state detail for a network This is an example of show ip ospf link-state detail summary for LSA detailed output. HP Switch(config)# show ip ospf link-state detail OSPF Link State Database for Area 0.0.0.0 LSA Age LSA Type Advertising Router Link State ID LSA Sequence LSA Checksum LSA Option Bits Network Mask Attached Router ID Attached Router ID : : : : : : : : : : 19 0x2 (Network) 16.93.223.84 192.22.23.24 0x80000001 0x323e E=1 MC=0 N/P=0 EA=0 DC=1 255.255.255.
Example 114 Output for show IP OSPF link-state detail for summary for NSSA This example shows show ip ospf link-state detail summary for NSSA. HP Switch(config)# show ip ospf link-state detail LSA Age LSA Type Advertising Router Link State ID LSA Sequence LSA Checksum LSA Option Bits LSA Metric Network Mask Bit E Forwarding Address External Route Tag : : : : : : : : : : : : 86 0x7 (NSSA) 16.93.226.105 16.93.49.0 0x80000003 0x6c03 E=1 MC=0 N/P=0 EA=0 DC=1 10 255.255.255.0 0 (External Metric Type1) 0.0.0.
Table 21 CLI display of OSPF neighbor information (continued) Field Description higher) are listed in the hello packets sent from the associated interface. 2WAY Communication between the two routers is bidirectional. This is the most advanced state before beginning adjacency establishment. The DR and BDR are selected from the set of neighbors in the 2Way state or greater. EXSTART The first step in creating an adjacency between the two neighboring routers.
Example 116 Example of output for show ip ospf redistribute HP Switch# show ip ospf redistribute OSPF redistributing Route type Status ---------- -------connected enabled static enabled rip enabled The display shows whether redistribution of each of the route types, connected, static, and RIP is enabled.
Table 22 CLI display of OSPF virtual neighbor information (continued) Field Description State The state of the adjacency with this virtual neighbor. The possible values are the same as the OSPF neighbor states. See the State parameter definition in “CLI display of OSPF neighbor information” (page 181). Virtual neighbors should never stay in the 2WAY state. IP Address IP address of the virtual neighbor that the routing switch is using to communicate to that virtual neighbor.
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. Example 120 Output for the show ip ospf virtual-link ip-addr command HP Switch# 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.
Example 121 Displaying OSPF SPF statistics HP Switch(ospf)# show ip ospf spf-log OSPF SPF (SHORTEST PATH FIRST) LOG Area : 0.0.0.
Example 122 Output for show IP OSPF HP Switch# show ip ospf OSPF Configuration Information OSPF protocol : enabled Router ID : 10.0.8.35 Currently defined areas: Area ID -------------backbone 10.3.16.0 10.3.32.
Table 26 CLI display of OSPF route and status information (continued) Field Description Stub Default Cost The metric for any default route we injected into a stub area if the routing switch is an ABR for the area. This value applies only to stub areas. Stub Summary LSA send or don't send — indicates the state of the no-summary option for the stub area. The value indicates if the area is "totally stubby" (no summaries sent from other areas) or just "stub" (summaries sent.
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 next-hop routes. 1 - 4 : Specifies the maximum number of equal-cost next-hop paths the router allows.
the shortest path between itself and a desired destination router in the same OSPF domain (AS.)Routed traffic in an OSPF AS is classified as one of the following: • Intra-area traffic • Inter-area traffic • External traffic The switches support the following types of LSAs, which are described in RFCs 2328 and 3101: Table 27 OSPF LSA types LSA type LSA name Use 1 Router link Describes the state of each interface on a router for a given area. Not propagated to backbone area.
Area border routers (ABRs) This type of OSPF router has membership in multiple areas . ABRs are used to connect the various areas in an AS to the backbone area for that AS. Multiple ABRs can be used to connect a given area to the backbone, and a given ABR can belong to multiple areas other than the backbone. An ABR maintains a separate LSDB for each area to which it belongs. (All routers within the same area have identical LSDBs.) The ABR is responsible for flooding summary LSAs between its border areas.
For example, in Figure 39 (page 192), the DR and BDR for 10.10.10.0 network in area 5 are determined as follows: Router A Priority: 0 Cannot become a DR or BDR Router B Priority: 1 DR for the 10.10.10.0 network Router C Priority: 2 BDR for the 10.10.10.
The DR and BDR election process is performed when one of the following events occurs: • Interface is in a waiting state and the wait time expires • Interface is in a waiting state and a hello packet is received that addresses the BDR • Change in the neighbor state occurs, such as: • Neighbor state transitions from 2 or higher • Communication to a neighbor is lost • Neighbor declares itself to be the DR or BDR for the first time OSPF area types OSPF is built upon a hierarchy of network areas.
type-1 and type-2 LSAs and routed traffic internal to the area. ASBRs are allowed in backbone areas. Normal area This area connects to the AS backbone area through one or more ABRs (physically or through a virtual link) and supports type-3 summary LSAs and type-5 external link LSAs to and from the backbone area. ASBRs are allowed in normal areas. 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.
You can configure the stub area ABR to do the following: • Suppress advertising some or all of the area's summarized internal routes into the backbone area. • Suppress LSA traffic from other areas in the AS by replacing type-3 summary LSAs and the default external route from the backbone area with the default summary route (0.0.0.0/0.) Virtual links are not allowed for stub areas.
Algorithm for AS external LSA reduction The AS external LSA reduction feature behavior changes under the following conditions: • There is one ASBR advertising (originating) a route to the external destination, but one of the following happens: • A second ASBR comes on-line. • A second ASBR that is already on-line begins advertising an equivalent route to the same destination.
Example 123 Example of show ip route command output with multiple next-hop routes HP Switch show ip route IP Route Entries Destination -----------------1.0.0.0/8 10.0.8.0/21 12.0.9.0/24 15.0.0.0/8 21.0.9.0/24 21.0.9.0/24 21.0.9.0/24 127.0.0.0/8 127.0.0.1/32 162.130.101.0/24 Gateway --------------10.0.8.1 DEFAULT_VLAN VLAN3 10.0.8.1 162.130.101.2 162.130.101.3 162.130.101.
Figure 41 Example of OSPF ECMP multiple next-hop routing (inter-area) 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 42 (page 198), one possible distribution of traffic to host devices is: • 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.
NOTE: OSPF is automatically enabled without a system reset. General configuration steps for OSPF To begin using OSPF on the routing switch: 1. In the global config context, use ip routing to enable routing (page “Enabling IP routing” (page 140).) 2. Execute router ospf to place the routing switch in the ospf context and to enable OSPF routing (page A-21.) 3. Change theOSPF RFC 1583 compliance, if needed. (See “Changing the RFC 1583 OSPF compliance setting” (page 141).) 4.
OSPF global and interface settings When first enabling OSPF, you may want to consider configuring ranges and restricting redistribution (if an ASBR is used) to avoid unwanted advertisements of external routes. You may also want to enable the OSPF trap and authentication features to enhance troubleshooting and security.
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. • If you want the VLANs and any subnets configured on the routing switch to all reside in the same area, you need to configure only that one area. (In this case, the routing switch would operate as an internal router for the area.
For the switches, the administrative distance for OSPF routes is set at 110 for all route types (external, inter-area, and intra-area.) The switch selects one route over another based on the source of the route information. To do so, the switch can use the administrative distances assigned to the sources to influence route choices. You can change the distance settings in the OSPF global context to enable preference of one route type over another.
Adjusting virtual link performance by changing the interface settings Optional: The OSPF interface parameters for this process are automatically set to their default values for virtual links. No change to the defaults is usually required unless needed for specific network conditions. These parameters are a subset of the parameters described under “Adjusting performance by changing the VLAN or subnet interface settings” (page 155).
Modules operating in nonstop mode When a switch is in standalone mode and OSPF routing is enabled, the "empty hello list" is transmitted whenever the boot or reload commands are executed. When the switch is operating in nonstop switching mode (redundant) and a single module is being reloaded or booted, the standby module will notify neighboring switches of the management module failover. If the failover fails, the "empty hello list" is transmitted before the switch is rebooted.
8 Route Policy For general information about route policy, see “Route policy overview” (page 212). Using prefix lists Prefix lists are named lists of route prefixes. They are used to match routes for inclusion in or exclusion from route policies. Creating prefix list entries A prefix list can include one or more rules, each defined by a sequence number, permit or deny instruction, prefix, and range of allowed prefix lengths.
no [ ip | ipv6 prefix-list name ] Deletes the entire prefix list identified by name. no [ ip | ipv6 prefix-list name ] [seq seq-num] Deletes the entry with the specified sequence number from the prefix list identified by name. Individual prefix list entries are made using separate commands in the general configuration context. All entries that have the same prefix list name are part of the same prefix list. Thus, the following commands, taken from a show running-config listing, constitute two prefix lists.
If the prefix list does not contain an entry with that sequence number, no description is entered. If you do not specify a sequence number, the description is attached to the first entry in the prefix list at the time the description is entered. description-string Specifies a description string of up to 80 characters. If you delete the entry to which the description is attached, the description is deleted also. Viewing prefix lists The show ip prefix-list command displays the content of prefix lists.
ip prefix-list Even: Count:4, Range-entries: 4, Sequences: 5 - 20 A detailed display of one of the prefix lists looks like this: HP Switch# show ip prefix-list name Even detail ip prefix-list Even: Count:4, Range-entries: 4, Sequences: 5 - 20 seq 5 deny 10.1.1.1/24 ge 24 le 24 Description: Permit even-numbered subnets seq 10 permit 10.1.2.1/24 ge 24 le 24 seq 15 deny 10.1.3.1/24 ge 24 le 24 seq 20 permit 10.1.4.1/24 ge 24 le 24 Creating a route map The route-map command creates a route map sequence.
Viewing route maps Syntax: show route-map [name] Displays the commands in all route maps or in a specified route map. [name] Optionally specifies the name of a route map to display. If no name is specified, all route maps are displayed. All sequences of a route map are displayed.
Matches a next hop address. [ ip | ipv6 ] [ IP-addr | IPv6-addr Specifies matching with either an IPv4 (IP) or IPv6 address, respectively. ] Specifies the IPv4 (IP) or IPv6 address, respectively, to match with. [ IP-addr | IPv6-addr ...] Optional additional addresses. A single command can specify multiple IPv4 (IP) or IPv6 addresses. A match succeeds if any of the addresses matches (logical OR.) name Specifies the name of a prefix list to match the next hop against.
connected Matches directly connected routes. static Matches static routes. rip Matches RIP routes. ospf Matches OSPF routes. ospfv3 Matches OSPFv3 routes. The no form of the command deletes the match clause from the sequence. Matching tags Syntax: [no] match tag value Matches the specified tag value with that of the route. value : Value of the route tag to match against. This is an integer value between 0 and the maximum number supported by the routing switch.
The no form of the command deletes the set clause from the sequence. Setting the tag value Syntax: [no] set tag value Sets the tag value of the route. value Value of the route tag. This is an integer value between 0 and the maximum number supported by the routing switch. The no form of the command deletes the set clause from the sequence. Route policy overview The route table in a routing switch contains routing paths to IP destinations.
The route map includes one or more sequences, each of which contains match statements and, optionally, set statements. When a route map is applied, its sequences are evaluated in order. If all the match statements in a sequence match the target route, the match succeeds and the route is permitted or denied according to the permit | deny instruction in the route-map command that defined the sequence; if the sequence contains set statements, they are applied to the target route.
Match commands The match commands described in this chapter are available for use in route maps. Multiple match commands may be used in a sequence of a route map. For most commands, only one match of a given type is permitted in a sequence.
Running configuration: ; J8697A Configuration Editor; Created on release #K.15.01.0031 hostname "South" module 1 type J8702A module 3 type J9478A ip routing vlan 1 name "DEFAULT_VLAN" untagged A19-A24,C13-C24 ip address dhcp-bootp no untagged A1-A18,C1-C12 exit vlan 31 name "VLAN31" untagged A1-A6 ip address 10.3.31.2 255.255.255.0 exit vlan 33 name "VLAN33" untagged A7-A12 ip address 10.3.33.2 255.255.255.0 exit vlan 21 name "VLAN21" untagged A13-A18 ip address 10.2.21.1 255.255.255.
Items of particular interest are: • The ip routing command enables routing on the switch. • The router ospf command enables OSPF routing on the switch. The area backbone command establishes the backbone area (area 0.) • The router rip command enables RIP routing on the switch. The redistribute connected command redistributes directly connected routes to all routers in the attached RIP domain. • The vlan commands at the end of the configuration assign routing protocols to the VLANs.
10.2.23.0/24 10.2.29.0/24 10.3.31.0/24 10.3.33.0/24 10.3.37.0/24 127.0.0.0/8 127.0.0.1/32 VLAN23 10.2.21.1 10.2.21.1 10.2.21.1 10.2.21.1 reject lo0 23 21 21 21 21 connected rip rip rip rip static connected 1 2 2 2 2 0 1 0 120 120 120 120 0 0 With this configuration, the routers and host computers in each routing domain are able to communicate with all other routers and hosts in that domain.
10.3.33.0/24 10.3.34.0/24 10.3.37.0/24 127.0.0.0/8 127.0.0.1/32 VLAN33 VLAN34 10.3.33.2 reject lo0 33 34 33 connected connected ospf IntraArea static connected 1 1 2 0 1 0 0 110 0 0 But this route table does not include all the possible routes in all domains: routes to subnets 10.1.15.x, 10.1.16.x, 10.2.21.x, and 10.2.29.x (VLANs 15, 16, 21, and 29) are missing.
ip prefix-list "Odds" seq 10 permit 10.1.13.1 255.255.255.0 ge 24 le 24 Then matching that prefix-list in a route map: route-map "PermitOdds" permit seq 10 match ip address prefix-list "Odds" exit And finally applying that route map to the redistribution of RIP routes in the North router: router ospf area backbone redistribute connected redistribute rip route-map "PermitOdds" exit The result of this is to permit redistribution of routes 10.1.11.x and 10.1.13.x, and to deny redistribution of routes 10.
10.3.33.0/24 10.3.34.0/24 10.3.37.0/24 127.0.0.0/8 127.0.0.1/32 10.2.21.1 10.2.21.1 10.2.21.1 reject lo0 21 21 21 rip rip rip static connected 2 2 2 0 1 120 120 120 0 0 To not lose the "even-numbered" routes (10.1.12.x and 10.1.14.x) in the OSPF domain, reinstate the original redistribution in the North router: router ospf area backbone redistribute connected redistribute rip exit And move the prefix list, route map, and redistribution from the North router to the South router.
10.3.37.0/24 127.0.0.0/8 127.0.0.1/32 10.3.33.2 reject lo0 33 ospf IntraArea static connected 2 0 1 110 0 0 However, it falls short in the southern RIP domain. The northern RIP routes are distributed as expected, but some of the routes from the OSPF domain are missing —10.3.32.x and 10.3.34.x. Here is the Southeast router's route table: Southeast(config)# show ip route IP Route Entries Destination --------------10.1.11.0/24 10.1.13.0/24 10.1.15.0/24 10.1.16.0/24 10.2.21.0/24 10.2.22.0/24 10.2.23.
to the OSPF domain, you could apply the metric with a set metric command in a route map in the North router: route-map "Metric25" permit seq 10 match source-protocol rip set metric 25 exit Then you could redistribute from the router ospf context: router ospf area backbone redistribute connected redistribute rip route-map "Metric25" exit The results are displayed in the Metric column of the East router's route map: East(config)# show ip route IP Route Entries Destination --------------10.1.11.0/24 10.1.12.
match ip address prefix-list "Odds" set tag 1 exit route-map "TagIn" permit seq 20 match ip address prefix-list "Evens" set tag 2 exit Set up a separate route map to match the connected routes, and assign the same tag value you used for the odd routes. This allows you to propagate both the odd and the connected routes, but not the even routes, to the southern RIP domain.
10.3.37.0/24 127.0.0.0/8 127.0.0.1/32 224 Route Policy 10.2.21.
9 ICMP Router Discovery Protocol The ICMP Router Discovery Protocol (IRDP) is used by HP 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. Configuring IRDP When IRDP is enabled, the routing switch periodically sends Router Advertisement messages out the IP interfaces on which the feature is enabled.
HP Switch(config)# ip irdp This command enables IRDP on the IP interfaces on all ports. Each port uses the default values for the IRDP parameters.
Advertisements. The default is three-fourths (0.75) the value of the maxadvertinterval parameter. If you change the maxadvertinterval parameter, the software automatically adjusts the minadvertinterval parameter to be three-fourths the new value of the maxadvertinterval parameter. If you want to override the automatically configured value, you can specify an interval from 1 to the current value of the maxadvertinterval parameter preference number Specifies the IRDP preference level of this routing switch.
10 Dynamic Host Configuration Protocol The Dynamic Host Configuration Protocol (DHCP) is used for configuring hosts with IP address and other configuration parameters without user intervention. The protocol is composed of three components: • DHCP client • DHCP server • DHCP relay agent For more information, see “Overview of DHCP” (page 237). Enabling DHCP relay The DHCP relay function is enabled by default on an HP routing switch.
Configuring a BOOTP/DHCP relay gateway The DHCP relay agent selects the lowest-numbered IP address on the interface to use for DHCP messages. The DHCP server then uses this IP address when it assigns client addresses. However, this IP address may not be the same subnet as the one on which the client needs the DHCP service.
Example 127 Assigning a gateway to an interface and then displaying the information HP Switch(vlan-22)ip bootp-gateway 12.16.18.33 HP Switch(vlan-22)# exit HP Switch(config)# show dhcp-relay bootp-gateway vlan 22 BOOTP Gateway Entries VLAN BOOTP Gateway -------------------- --------------VLAN 22 12.16.18.33 Operating notes • If the configured BOOTP gateway address becomes invalid, the DHCP relay agent returns to the default behavior (assigning the lowest-numbered IP address.
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. • You enter the no dhcp-relay hop-count-increment command at the global configuration level. The command is applied to all interfaces on the routing switch that are configured to forward DHCP requests. • This DHCP relay enhancement applies only to DHCP requests forwarded to a DHCP server.
Displays the IP helper addresses of DHCP servers configured for all static VLANS in the switch or on a specified VLAN, regardless of whether the DHCP relay feature is enabled. The vlan vlan-id parameter specifies a VLAN ID number. Example The following command lists the currently configured IP Helper addresses for VLAN 1. Example 129 Displaying IP helper addresses HP Switch(config)# show ip helper-address vlan 1 IP Helper Addresses IP Helper Address ----------------10.28.227.97 10.29.227.
Example 131 Using the CLI to view the switch MAC address HP Switch(config)# show system information Status System System System and Counters - General System Information Name : HP Switch Contact : Location : MAC Age Time (sec) : 300 Time Zone : 0 Daylight Time Rule : None Software revision : K.15.06.0000x ROM Version : K.15.
associated with the client DHCP packet and the switch remote ID. The default switch remote ID is the MAC address of the switch on which the packet was received from the client. To use the incoming VLAN's IP address or the Management VLAN IP address (if configured) for the remote ID instead of the switch MAC address, use the ip or mgmt-vlan option (below.) drop Configures the routing switch to unconditionally drop any client DHCP packet received with existing Option 82 fields.
the routing switch defaults to the mac option. See “Option 82 field content” (page 240). • ip: Specifies the IP address of the VLAN on which the client DHCP packet enters the switch. • mac: Specifies the routing switch's MAC address. (The MAC address used is the same MAC address that is assigned to all VLANs configured on the routing switch.) This is the default setting. • mgmt-vlan:Specifies the IP address of the (optional) management VLAN configured on the routing switch.
Table 28 DHCP operation for the topology in Figure Figure 46 (page 235) Client Remote ID 1 giaddr1 DHCP server X 10.38.10.1 10.39.10.1 A only If a DHCP client is in the management VLAN, its DHCP requests can go only to a DHCP server that is also in the management VLAN. Routing to other VLANs is not allowed. Y 10.38.10.1 10.29.10.1 B or C Z 10.38.10.1 10.15.10.1 B or C Clients outside of the management VLAN can send DHCP requests only to DHCP servers outside of the management VLAN.
• Because routing is not allowed between the management VLAN and other VLANs, a DHCP server must be available in the management VLAN if clients in the management VLAN require a DHCP server. • If the management VLAN IP address configuration changes after mgmt-vlan has been configured as the remote ID suboption, the routing switch dynamically adjusts to the new IP addressing for all future DHCP requests. • The management VLAN and all other VLANs on the routing switch use the same MAC address.
process, the DHCP relay agent increments the hop count before forwarding DHCP packets to the server. The DHCP server, in turn, includes the hop count from the received DHCP request in the response sent back to a DHCP client. As a result, the DHCP client receives a non-zero hop count in the DHCP response packet. Because some legacy DHCP/BootP clients discard DHCP responses that contain a hop count greater than one, they may fail to boot up properly.
For more information, see the documentation provided with the server application. Option 82 server support To apply DHCP Option 82, the routing switch must operate in conjunction with a server that supports Option 82. (DHCP servers that do not support Option 82 typically ignore Option 82 fields.) Also, the routing switch applies Option 82 functionality only to client request packets being routed to a DHCP server. DHCP relay with Option 82 does not apply to switched (non-routed) client requests.
Figure 48 Example of DHCP Option 82 Operation in a Network with a Non-Compliant Relay Agent Option 82 field content The remote ID and circuit ID subfields comprise the Option 82 field a relay agent appends to client requests. A DHCP server configured to apply a different IP addressing policy to different areas of a network uses the values in these subfields to determine which DHCP policy to apply to a given client request.
Example 132 Using walkmib to determine the circuit ID for a port on an HP chassis For example, the circuit ID for port B11 on an HP switch is "35”, see Example 132 (page 241), below. HP Switch# 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.32 = B8 ifName.33 = B9 ifName.34 = B10 ifName.35 = B11 ifName.36 = B12 ifName.37 = B13 ifName.38 = B14 ifName.39 = B15 ifName.
Option 82 configuration DHCP client request packet inbound to the routing switch Packet has no Option 82 field Packet includes an Option 82 field NOTE: In networks with multiple relay agents between a client and an Option 82 server, append can be used only if the server supports multiple Option 82 fields in a client request. If the server supports only one Option 82 field in a request, consider using the keep option.
Figure 49 Example configured to allow only the primary relay agent to contribute an Option 82 field The above combination allows for detection and dropping of client requests with spurious Option 82 fields. If none are found, the drop policy on the first relay agent adds an Option 82 field, which is then kept unchanged over the next two relay agent hops ("B" and "C".) The server can then enforce an IP addressing policy based on the Option 82 field generated by the edge relay agent ("A".
Table 29 Relay agent management of DHCP server response packets. Response packet content Option 82 configuration Valid DHCP server response append, replace, or drop1 packet without an Option 82 field. Drop the server response packet. Forward server response packet to a downstream device. Forward server response packet to a downstream device. Forward server response packet to a downstream device. Drop the server response packet. Forward server response packet to a downstream device.
Table 29 Relay agent management of DHCP server response packets. (continued) Response packet content Option 82 configuration Validation Validation enabled disabled on the (the relay default) agent packet to a downstream device. 1 packet to a downstream device. Drop is the recommended choice because it protects against an unauthorized client inserting its own Option 82 field 2 for an incoming request.
11 User Datagram Protocol For introductory information about user datagram protocol (UDP), see “UDP broadcast forwarding” (page 249). 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.
more information on UDP port numbers, refer to “TCP/UDP port number ranges” (page 248). port-name Allows use of common names for certain well-known UDP port numbers.
Example: Example 133 Displaying global IP forward-protocol status and configuration This example shows the global display showing UDP broadcast forwarding status and configured forwardig addresses for inbound UDP broadcast traffic for all VLANs configured on the routing switch. HP Switch(config)# show ip forward-protocol IP Forwarder Addresses UDP Broadcast Forwarding: Disabled VLAN: 1 IP Forward Addresses -------------------15.75.11.43 15.75.11.255 15.75.12.
For more information, including a listing of UDP/TCP port numbers, go to the Internet Assigned Numbers Authority (IANA) website at: www.iana.org Then click on: Protocol Number Assignment Services P (Under "Directory of General Assigned Numbers" heading) Port Numbers Messages related to UDP broadcast forwarding Message Meaning udp-bcast-forward: IP Routing support must be enabled first.
includes multiple subnets, the entry applies to client broadcasts with that port number from any subnet in the VLAN. For example, VLAN 1 (15.75.10.1) is configured to forward inbound UDP packets as shown in Table 30 (page 250). Table 30 Example of a UDP packet-forwarding environment Interface IP address Subnet mMask Forwarding address UDP port Notes VLAN 1 15.75.10.1 255.255.255.0 15.75.11.43 15.75.11.255 1188 1812 15.75.12.
12 Virtual Router Redundancy Protocol (VRRP) VRRP 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. Virtual Router Redundancy Protocol (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.
Default: Disabled Syntax: [no] router vrrp traps Enables or disables SNMP trap generation for the following events: New master Indicates that the sending router has transitioned to 'master' state. Authentication Failure Indicates that a VRRP packet has been received from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type. NOTE: This feature assumes the snmp-server host command has been used to configure a a trap receiver.
If an update is performed from a software version that only supported VRRPv2, all the IPv4 VRs remain in VRRPv2 mode. Syntax: version 2|3 Example: HP Switch(vlan-10-vrid-1)# version 3 Configuring a VR instance on a VLAN interface This section describes the configuration and activation commands available in the VR context. Configuring a virtual IP address (VIP) in a VR The VIP must be the same for the owner and all backups on the same network or subnet in a VR.
Figure 52 VIP assignment for owner and backup Host"A" Gateway: 10.10.10.1 VR 1 10.10.10.1/24 (Virtual IP Address) Intranet Router A Router B VLAN VID: 10 IP: 10.10.10.1/24 VLAN VID: 10 IP: 10.10.10.15/24 Router 1 Configuration VRID: 1 Status: owner Virtual IP Addr: 10.10.10.1 Switch VLAN VID: 10 Host Router 2 Configuration VRID: 1 Status: backup Virtual IP Addr: 10.10.10.1 Reconfiguring the priority for a backup When you configure a backup in a VR, it is given a default priority of 100.
Syntax: primary-ip-address [ ip-address | lowest ] NOTE: For IPv4 only. IPv6 does not have a primary-ip-address option; the primary IP address is the link-local address of the real interface over which the packet is transmitted. Specifies the VIP to designate as the source for VRRP advertisements from the VR. If there is only one VIP configured on the VR, the default setting (lowest) is sufficient.
Dynamically changing the priority of the VR NOTE: You can configure tracked interfaces or VLANs on the backup router only. Configuring track interface Syntax [no] track interface [port-list|trunk-list] Allows you to specify a port or port list, or trunk or trunk list, that will be tracked by this virtual router. If the port or trunk is down, the virtual router switches to the router specified by the priority value. The command is executed in VRID instance context.
Example: HP Switch(vlan-25-vrid-1)# no track Viewing VRRP tracked entities You can display the VRRP tracked entities by entering the command shown in this example.
Example 137 Configuring the Authentication Data Field HP Switch(vlan-2-vrid-1)# null-auth-compatibility Pinging the virtual IP of a backup router Enabling the response to a ping request The backup router can be enabled to respond to pings using the following command. For more information, see “Pinging the virtual IP of a backup router” (page 285). Syntax: [no] router vrrp virtual-ip-ping Enables or disables the response to a ping request for the switch.
Example 140 Example of VRRP global configuration information HP Switch(config)# show vrrp config global VRRP Global Configuration Information VRRP Enabled : Traps Enabled : Virtual Routers Respond to Ping Requests [Yes] : Virtual Nonstop enabled : Yes Yes Yes No Use the show vrrp command to display information about VRRP global statistics.
Example Example 141 VRRP IPv4 global statistics information HP Switch(config)# show vrrp VRRP Global Statistics Information VRRP Enabled : Yes Invalid VRID Pkts Rx : 0 Checksum Error Pkts Rx : 0 Bad Version Pkts Rx : 0 Virtual Routers Respond To Ping Requests : Yes VRRP Virtual Router Statistics Information Vlan ID Virtual Router ID Protocol Version 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 Mism
Example Example 143 VRRP IPv4 configuration display showing VIP ping status HP Switch# show vrrp config VRRP Global Configuration Information VRRP Enabled : Traps Enabled : Virtual Routers Respond To Ping Requests : VRRP Nonstop Enabled : Yes Yes Yes No VRRP Virtual Router Configuration Information VLAN ID 2 Virtual Router ID : 1 Administrative Status [Disabled] : Enabled Mode [Uninitialized] : backup Priority [100] : 150 Advertisement Interval [1] : 1 Preempt Mode [True] : True Preempt Delay Time [0] : 0
Example 144 VRRP IPv6 configuration display showing VIP ping status HP Switch# show vrrp ipv6 config VRRP Global Configuration Information VRRP Enabled Traps Enabled Virtual Routers Respond To Ping Requests VRRP Nonstop Enabled : : : : Yes Yes No No : : : : : : : : : : : 10 10 Enabled Owner 255 1 True 0 Yes 3 True VRRP Virtual Router Configuration Information VLAN ID Virtual Router ID Administrative Status [Disabled] Mode [Uninitialized] Priority [100] Advertisement Interval [1] Preempt Mode [True] Pre
Example 146 VRRP IPv6 configuration for a VLAN and VRID HP Switch# show vrrp ipv6 vlan 10 vrid 4 config VRRP Virtual Router Configuration Information VLAN ID : Virtual Router ID : Administrative Status [Disabled] : Mode [Uninitialized] : Priority [100] : Advertisement Interval [1] : Preempt Mode [True] : Preempt Delay Time [0] : Respond To Virtual IP Ping Requests [Yes] : Version [2] : 10 1 Enabled Owner 255 1 True 0 Yes 3 IPv6 Address --------------------------fe80::216:b9ff:fed1:5280 Example Example 14
Allows you to specify a time in seconds that this router will wait before taking control of the VIP and beginning to route packets. You can configure the timer on VRRP owner and backup routers. NOTE: If you have configured the preempt delay time (PDT) with a non-zero value, you must use the no form of the command to change it to 0 (zero.) Default: 0 (zero) seconds.
Example 149 VRRP IPv4 configuration listing with two owner VRs configured This example lists output indicating two owner VRs configured on the router.
Example 150 VRRP IPv6 Configuration Listing HP Switch# show vrrp ipv6 config VRRP Global Configuration Information VRRP Enabled Traps Enabled Virtual Routers Respond To Ping Requests VRRP Nonstop Enabled : : : : Yes Yes No No : : : : : : : : : : : 10 10 Enabled Owner 255 1 True 0 Yes 3 True VRRP Virtual Router Configuration Information VLAN ID Virtual Router ID Administrative Status [Disabled] Mode [Uninitialized] Priority [100] Advertisement Interval [1] Preempt Mode [True] Preempt Delay Time [0] Resp
Example 151 Displaying the IPv4 configuration for a specific VR The following command displays the configuration of a VR identified as VR 10 in VLAN 23: HP Switch(config)# show vrrp vlan 23 vrid 10 config VRRP Virtual Router Configuration Information Vlan ID : 23 Virtual Router ID : 10 Administrative Status [Disabled] : Disabled Mode [Uninitialized] : Owner Priority [100] : 255 Advertisement Interval [1] : 1 Preempt Mode [True] : True Prempt Delay Time [0] : 0 Respond to Virtual IP Ping Requests [Yes} : Yes
Example Example 153 statistics command output if global VRRP is disabled VRRP Global Statistics Information VRRP Enabled : No Viewing global VRRP statistics only Syntax: show vrrp statistics global show vrrp ipv6 statistics global Displays the global VRRP statistics for the router: • VRRP Enabled [Yes/No] • Invalid VRID Pkts Rx: VRRP packets received for a VRID that is not configured on the specific VLAN of the VRRP router.
master's IP Address The IP address used as the source IP address in the last advertisement packet received from the VR master. If this VR is the master, this is the primary IP address of the VR. If the VR is disabled, this value appears as 0.0.0.0 for IPv4, and 0:0:0:0:0:ffff:0:0 for IPv6. Associated IP Address Count Number of VIPs. Advertise Packets Rx The number of VRRP master advertisements the VR has received from other VRRP routers since the last reboot.
Example Example 155 Output for show vrrp command includes global and VR statistics The following output shows the VRRP statistics on a router having one VR (VR 1 in VLAN 10) configured.
Syntax: show vrrp vlan vid [statistics] Displays the VRRP statistics for all VRs configured on the specified VLAN. The actual statistics data per VR is the same as for the show vrrp [statistics] command shown on pages A-24 and Example 155 (page 270). Note that show vrrp vlan vid and show vrrp vlan vid statistics produce the same output. Example 157 Displaying IPv4 statistics for all VRs in a VLAN In the following example, there is one VR configured in VLAN 10.
Note that show vrrp vlan vid vrid 1 - 255 and show vrrp vlan vid vrid 1 - 255 statistics produce the same output. Viewing the "near-failovers" statistic The "near failovers" statistic tracks occurrences of near failovers on the backup VRRP routers. This makes visible any difficulties the VRRP routers are having receiving the "heartbeat" advertisement from the master router. (A "near failover" is one that is within one missed VRRP advertisement packet of beginning the master determination process.
Example Example 159 The show vrrp command with statistics Near Failovers statistic displayed is shown in bold below.
VRRP packets. Syntax: [no] debug vrrp Displays VRRP debug messages. General operation License requirements: In the 3500yl, 3800, 5400zl, 6600, and 8200zl switches, VRRP is included with the Premium License. In the 6200yl switches, this feature is included with the base feature set. VRRP supports router redundancy through a prioritized election process among routers configured as members of the same virtual router (VR.
Figure 53 Example of using VRRP to provide redundant network access VR parameter VRID (Virtual Router ID) Status Virtual IP Address VR Source MAC Address Priority Router 1 VR configuration Router 2 VR configuration Operation 1 1 owner backup One owner and one or more backups are allowed in a given VR. 10.10.100.1 10.10.100.1 The IP address configured for VLAN 100 in R1 (the owner) is also configured as the VIP for VRRP in both R1 and R2.
In Figure 53 (page 275): • Host "A" uses 10.10.100.1 as its next-hop gateway out of the subnet, as represented by the VR (VR 1.) • • • • "Owns" the VR's (virtual) IP address • Transmits ARP responses that associate the VR's VIP with the (shared) source MAC address for VR 1. During normal operation, Router 1 forwards the routed traffic for host "A." If Router 1 fails or otherwise becomes unavailable: a.
NOTE: All routers in a given VR must belong to the same network (or subnet, in the case of a multinetted VLAN.) Virtual IP address (VIP) The VIP associated with a VR must be a real IP address already configured in the associated VLAN interface on the owner router in the VR. If the VIP is an IPv6 address, a link-local address must be configured before adding a global IPv6 address.
Backup router There must be at least one backup router. A given VR instance on a backup router must be configured with the same VIP as the owner for that VR (and both routers must belong to the same network or subnet.) Router 2 in Figure 53 (page 275) illustrates this point. VR priority operation In a backup router's VR configuration, the virtual router priority defaults to 100. (The priority for the configured owner is automatically set to the highest value: 255.
• Neighbor reachability • Autoconfiguration of unicast addresses • Resolution of destination addresses • Changes to link-layer addresses. An instance of Neighbor Discovery is triggered on a device when a new or changed IPv6 address is detected. VRRPv3 provides a faster failover to a backup router by not using standard ND procedures. A failover to a backup router can occur in approximately three seconds without any interaction with hosts and with a minimum of VRRPv3 traffic.
• 512 VRRPv2 and VRRPv3 sessions, in any mix • 32 IP addresses per VR • Each VR uses one MAC address as described under “Virtual router MAC address” (page 278). • If an IP address is deleted on a VLAN interface, one of the following occurs: • VR owner: If the VR uses the same IP address as a VIP, that IP address is deleted from the VR. • VR backup: If the VR has a VIP in the same subnet as that of the deleted IP address, that VIP will be deleted from the VR.
a. On another router with an interface in the same network or subnet as is the owner configured in step “1” (page 280), enter the global configuration context and enable VRRP: router vrrp ipv4 enableor router vrrp ipv6 enable b. Configure (and enter) the same VR instance as was configured for the owner in step “1” (page 280): vlan vid vrrp vrid 1 - 255 (for IPv4) vrrp ipv6 vrid 1-255 (for IPv6) c.
Figure 54 Example of a basic VRRP configuration 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.1 MAC Addr: 00-00-5E-00-01-01 Priority: 255 Switch VLAN VID: 10 Host"A Router 2 Configuration VRID: 1 Status: backup Virtual IP Addr: 10.10.10.
Example 161 VRRP configuration for Router 1 (R1) in Figure 54 (page 282) HP HP HP HP HP HP Switch(config)# router vrrp Switch(config)# vlan 10 Switch(vlan-10)# vrrp vrid 1 Switch(vlan-10-vrid-1)# owner Switch(vlan-10-vrid-1)# virtual-ip-address 10.10.10.
If a VLAN is configured with more than 32 subnets and it is necessary to apply VRRP to all of these subnets, it is necessary to associate more than one VIP with a VR. Because a VLAN on the routers supports up to 32 VRs, applying VRRP to a higher number of subnets in the VLAN requires multiple VIPs in one or more VRs. If the owner of a VR is associated with multiple VIPs, the backup routers belonging to the same VR must also be associated with the same set of VIPs.
Pinging the virtual IP of a backup router When in compliance with RFC 3768 , only owner VRs reply to ping requests (ICMP echo requests) to the VIP. When the virtual IP ping option is enabled, a backup VR operating as the master can respond to ping requests made to the VIP. This makes it possible to test the availability of the default gateway with ping. A non-owner VR that is not master drops all packets to the VIP. NOTE: This feature is not a part of RFC 3768.
receive any VRRP packets and the master down time expires, the owner router can take control of its VIP immediately. If the value of the master down time (3 * advertisement interval) is greater than the preempt delay time, the owner router will wait until the PDT expires before taking control of its VIP. Selecting a value for the PDT You should select the value for the PDT carefully to allow time for OSPF to populate the owner router's route tables.
Standards compliance VRRP on the switches includes the following: • Complies with RFC 3768 VRRP version 2. • Complies with RFC 5798 version 3 with two exceptions—advertisement intervals below one second are not supported, and accept mode is not supported (only ping application for virtual-ip-ping). • Compatible with HP Series 9300m routers, the HP 9408sl router, and the HP Series 8100fl switches. (VRRP on these devices is based on RFC 2338.
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 cannot be configured as a tracking VLAN for that VR. • Ports that are part of a trunk cannot be tracked. • A port that is tracked cannot be included in a trunk.
13 Border Gateway Protocol (BGP) Introduction BGPv4 (RFC 4271) is the defacto internet exterior gateway protocol used between ISPs. The characteristics of BGP are: • Controls route propagation and the selection of optimal routes, rather than route discovery and calculation, which makes BGP different from interior gateway protocols such as OSPF and RIP. • Uses TCP to enhance reliability. • Supports CIDR.
Table 31 Global BGP configuration commands (continued) Command syntax Description Default CLI reference Border Gateway Protocol (BGP) process. Configuring a BGP routing process Syntax: router bgp as-# no router bgp Configures a BGP routing process. To remove the routing process, use theno form of the command. This command is used in the configuration context only.
Re-enabling state contained within nodes of BGP processes Syntax: [no] enable disable Re-enables the state contained within this node and all child nodes of the Border Gateway Protocol (BGP) process. The disable command disables the state contained within this node and all child nodes. The default is for the state to be disabled.
Table 32 Global BGP policy configuration commands (continued) Command syntax Description Default CLI reference value of infinity (max possible) to routes that are missing the Multi Exit Discriminator (MED) attribute (making the path without a MED value the least desirable path), use the bgp bestpath med missing-as-worst command in router configuration mode. [no] bgp default-metric med-out Causes a BGP MED to be set on routes when they are advertised to peers.
Enables the comparison of the Multi Exit Discriminator (MED) for paths from neighbors in different autonomous systems. To disallow the comparison, use the no form of this command. The MED is one of the parameters that is considered when selecting the best path among many alternative paths. The path with a lower MED is preferred over a path with a higher MED. During the best-path selection process, MED comparison is done only among paths from the same autonomous system.
Assigning value of infinity to routes missing MED attribute Syntax: [no] bgp bestpath med-missing-as-worst To configure a Border Gateway Protocol (BGP) routing process to assign a value of infinity (max possible) to routes that are missing the Multi Exit Discriminator (MED) attribute (making the path without a MED value the least desirable path), use the bgp bestpath med missing-as-worst command in router configuration mode.
BGP graceful restart Table 33 Graceful restart commands Command syntax Description Default CLI reference bgp Configures BGP graceful-restart graceful restart timers. { restart-time val | [stalepath-time val]} (page 295) [no] bgp Enables or disables log-neighbor-changes BGP event logging. [prefix-list prefix-list-name] (page 295) [no] neighbor Describes a neighbor.
Enabling nonstop forwarding for BGP Syntax: [no] nonstop Configured under BGP routing context, enables nonstop forwarding for BGP on the 8200 series devices and enables the router to retain the ip forwarding table across redundancy switchover.
Table 34 Neighbor configuration and neighbor policy configuration commands (continued) Command syntax Description Default CLI reference This value defaults to the globally configured preference if it is not specified. (page 294) before it is exported into BGP [no] neighbor ipv4-addr weight weight Preferences are the first criteria of comparison for route selection.
Adding an entry to the BGP neighbor table in router configuration mode Syntax: neighbor ipv4-addr remote-as as-# no neighbor ipv4-addr Adds an entry to the BGP neighbor table in router configuration mode. To remove an entry from the table, use the no form of this command. Specifying a neighbor with an autonomous system number that matches the autonomous system number specified in the router bgp global configuration command identifies the neighbor as internal to the local autonomous system.
Specifying the number of times the autonomous system can appear in an AS path Syntax: [no]neighbor ipv4-addr allowas-in num-loops Specifies the number of times this autonomous system can appear in an AS path. When not configured, or when using theno version of the command, the value of as-loops is set to its default value of 1.
Comparing preferences for route selection Syntax: [no] neighbor ipv4-addr weight weight Preferences are the first criteria of comparison for route selection. This value defaults to the globally configured preference if it is not specified. Sending a community's attribute to a BGP neighbor Syntax: [no]neighbor ipv4-addr send-community To specify that a community’s attribute should be sent to a BGP neighbor, use the neighbor send-community command in address family or router configuration mode.
Using the router's outbound interface address as next hop Syntax: [no] neighbor ipv4-addr next-hop-self Forces BGP to use the router's outbound interface address as the next hop for the route updates to the peer. Specifying no peering connection to peer Syntax: [no] neighbor ipv4-addr passive If enabled, does not initiate a peering connection to the peer.
Synchronizing BGP-IGP Table 35 BGP-IGP synchronization commands Command syntax Description Default CLI reference [no] redistribute protocol [route-map route-map-name] Specifies routes to export into BGP. This command causes routes from the specified protocol to be considered for redistribution into BGP. (page 302) [no] neighbor ipv4-addr route-map route-map-name [[in] | [out]] Route maps control the redistribution of routes between protocols.
Optional transitive Transitive attribute between ASs. A BGP router not supporting this attribute can still receive routes with this attribute and advertise them to other peers. Optional non-transitive If a BGP router does not support this attribute, it will not advertise routes with this attribute. The category of each BGP path attribute is described in the following table.
Figure 56 AS_PATH attribute Usually a BGP router does not receive routes containing the local AS number to avoid routing loops. NOTE: The current implementation supports using the neighbor allow-as-loop command to receive routes containing the local AS number. The AS_PATH attribute can be used for route selection and filtering. BGP gives priority to the route with the shortest AS_PATH length if other factors are the same.
Figure 57 NEXT_HOP attribute MED (MULTI_EXIT_DISC) The MED attribute is exchanged between two neighboring ASs, each of which does not advertise the attribute to any other AS. Similar to metrics used by IGP, MED is used to determine the best route for traffic going into an AS. When a BGP router obtains multiple routes to the same destination but with different next hops, it considers the route with the smallest MED value the best route if other conditions are the same.
Figure 59 LOCAL_PREF attribute COMMUNITY The COMMUNITY attribute is used to simplify routing policy usage, and to ease management and maintenance. It identifies a collection of destination addresses having identical attributes, without physical boundaries in between, and having nothing to do with the local AS. Well known community attributes involve: Internet By default, all routes belong to the Internet community. Routes with this attribute can be advertised to all BGP peers.
• Prefer the route with the lowest IGP cost to the BGP next hop. IGP cost is determined by comparing the preference, then the weight, then the metric, and finally the metric2 of the two resolving routes. • If “ip load-sharing” is enabled, BGP inserts up to n most recently received paths in the IP routing table. This allows eBGP multipath load sharing. The maximum value of n is currently 4. The default value of n, when “ip load-sharing” is disabled, is 1.
NOTE: • BGP implements load sharing only on routes that have the same WEIGHT, LOCAL_PREF, ORIGIN, AS_PATH, MED and IGP COST. • BGP load sharing is applicable between eBGP peers and between iBGP peers. • If multiple routes to the same destination are available, BGP selects the configured number of routes for load sharing. The maximum number of routes for load sharing is currently 4. Load sharing is enabled by default.
• RFC1997: BGP Communities Attribute • RFC2796: BGP Route Reflection • RFC4724: Graceful Restart Mechanism for BGP BGP extensions Route reflection By design, IBGP peers do not advertise iBGP routes to other iBGP peers. In order for iBGP peers to learn all the routes within the autonomous system as well as all the external routes, the iBGP peers would have to be fully meshed. This means for n iBGP peers there would have to be n*(n-1)/2 iBGP sessions.
Route refresh When the inbound policy-filter for a peer changes, the routes advertised by the peer must be presented to the policy-filter engine to take effect. This means that all the routes that were received from a peer will have to be preserved in the router and this would raise the demand on memory and CPU resources of the router.
Follow these steps to create a BGP connection: To do... Use the command... Enter global configuration context configuration Enter BGP context router bgp as-number Enable BGP enable Specify a BGP Router ID bgp router-id ip-address Remarks Not enabled by default Optional. By default, the global router ID is used.
Allowing establishment of an eBGP connection to a non-directly connected peer In general, direct physical links should be available between eBGP peers. If not, you can use the neighbor ip-address ebgp-multihop command to establish a TCP connection over multiple hops between two peers. Follow these steps to allow establishment of eBGP connection to a non-directly connected peer. To do... Use the command...
Configuring BGP route attributes Prerequisites Before configuring this task, you should have configured BGP basic functions. Configuration procedure You can configure BGP route attributes to influence BGP route selection. Follow these steps to configure BGP route attributes. To do... Use the command...
CAUTION: • Using a routing policy can set preferences for routes matching it. Routes not matching it use the default preferences. • If other conditions are identical, the route with the smallest MED value is selected as the best external route. • Using the neighbor next-hop-self command can specify the router as the next hop for routes sent to a peer.
CAUTION: • The maximum keepalive interval should be one third of the holdtime and no less than 1 second. The holdtime is no less than 3 seconds unless it is set to 0. • Intervals set with the neighbor timers command are preferred to those set with the timers command. • If the router has established a neighbor relationship with a peer, you need to reset the BGP connection to validate the new set timers.
NOTE: A device can act as both the GR Restarter and GR Helper simultaneously. Follow these steps to configure BGP GR. To do... Use the command...
To do... Use the command...
HP HP HP HP HP HP HP Switch(ospf)# enable Switch(ospf)# area 0 Switch(ospf)# network 2.2.2.2/32 Switch(ospf)# network 9.1.1.1/24 Switch(ospf)# exit Switch(config)# vlan 300 Switch(vlan-300)# ip ospf # Configure Switch C HP HP HP HP HP HP HP HP HP HP HP HP HP HP Switch(config)# router bgp 65009 Switch(bgp)# bgp router-id 3.3.3.3 Switch(bgp)# neighbor 2.2.2.2 remote-as 65009 Switch(bgp)# neighbor 2.2.2.
The output shows that Switch B has established an iBGP peer relationship with Switch C and an eBGP peer relationship with Switch A. # Display the BGP routing table on Switch A. HP Switch(bgp)# show ip bgp Local AS : 100 Local Router-id : 20.0.0.1 BGP Table Version : 0 Status codes: * - valid, > - best, i - internal, e external, s - stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Nexthop Metric LocalPref Weight AsPath ---------------------------------------------------------*> 8.1.1.
Status codes: * - valid, > - best, i - internal, e - external, s - stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Nexthop Metric LocalPref Weight AsPath --------------------------------------------------------*>e 2.2.2.2/32 3.1.1.1 0 0 65009? *>e 3.1.1.0/24 3.1.1.1 0 0 65009? *>e 8.1.1.0/24 0 0 65008i *>e 8.1.1.0/24 0 0 65008i Two routes 2.2.2.2/32 and 9.1.1.0/24 have been added in Switch A’s routing table. # Display the BGP routing table on Switch C.
HP HP HP HP HP Switch(config)# router bgp 10 Switch(bgp)# bgp router-id 1.1.1.1 Switch(bgp)# neighbor 200.1.2.2 remote-as 20 Switch(bgp)# network 9.1.1.0/255.255.255.0/8 Switch(bgp)# exit # Configure Switch B. HP HP HP HP HP Switch(config)# bgp 20 Switch(bgp)# bgp router-id 2.2.2.2 Switch(bgp)# neighbor 200.1.2.1 remote-as 10 Switch(bgp)# neighbor 200.1.3.2 remote-as 30 Switch(bgp)# exit # Configure Switch C. HP HP HP HP Switch(config)# bgp 30 Switch(bgp)# bgp router-id 3.3.3.
3. Configure the BGP community. # Configure a routing policy. route-map bgp-out permit seq 10 HP Switch(route-map-bgp-out)# set community no-export HP Switch(route-map-bgp-out)# exit # Apply the routing policy. HP Switch(config)# bgp 10 HP Switch(bgp)# neighbor 200.1.2.2 route-map bgp-out out # Display the route on Switch B. HP Switch(config)# show ip bgp 9.1.1.0/24 Local AS : 20 Local Router-id : 2.2.2.2 BGP Table Version : 3 Network : 9.1.1.0/24 Nexthop : 200.1.2.1 Peer : 200.1.2.
HP Switch(bgp)# neighbor 192.1.1.2 remote-as 200 # Add network 1.0.0.0/8 to the BGP routing table. HP Switch(bgp)# network 1.0.0.0 HP Switch(bgp)# exit # Configure Switch B. HP HP HP HP HP HP Switch(config)# router bgp 200 Switch(bgp)# bgp router-id 2.2.2.2 Switch(bgp)# neighbor 192.1.1.1 remote-as 100 Switch(bgp)# neighbor 193.1.1.1 remote-as 200 Switch(bgp)# neighbor 193.1.1.1 next-hop-self Switch(bgp)# exit # Configure Switch C.
4. Verify the above configuration. # Display the BGP routing table on Switch B. HP Switch(config)# show ip bgp Local AS : 200 Local Router-id : 200.1.2.2 BGP Table Version : 1 Status codes: * - valid, > - best, i - internal, e - external, s - stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Nexthop Metric LocalPref Weight AsPath -----------------------------------------------------------*>i 1.0.0.0/24 200.1.3.1 0 0 100i # Display the BGP routing table on Switch D.
Figure 64 Network diagram for BGP path selection configuration Device Interface IP address Device Interface IP address Switch A Vlan101 1.0.0.0/8 Switch D Vlan400 195.1.1.1/24 Vlan100 192.1.1.1/24 Vlan300 194.1.1.1/24 Vlan200 193.1.1.1/24 Vlan400 195.1.1.2/24 Vlan100 192.1.1.2/24 Vlan200 193.1.1.2/24 Vlan300 194.1.1.2/24 Switch B Switch C Configuration procedure 1. 2. Configure IP addresses for interfaces (omitted.) Configure OSPF on Switch B, C, and D. # Configure Switch B.
HP Switch(config)# router bgp 100 HP Switch(bgp)# neighbor 192.1.1.2 remote-as 200 HP Switch(bgp)# neighbor 193.1.1.2 remote-as 200 # Add network 1.0.0.0/8 to the BGP routing table on Switch A. HP Switch(bgp)# network 1.0.0.0/8 HP Switch(bgp)# exit # Configure Switch B. HP HP HP HP Switch(config)# router bgp 200 Switch(bgp)# neighbor 192.1.1.1 remote-as 100 Switch(bgp)# neighbor 194.1.1.1 remote-as 200 Switch(bgp)# exit # Configure Switch C.
4. Configure attributes for route 1.0.0.0/8, making Switch D give priority to the route learned from Switch C. # Configure a higher MED value for the route 1.0.0.0/8 advertised from Switch A to peer 192.1.1.2. # Define a prefix-list to permit route 1.0.0.0/8. HP Switch(config)# ip prefix-list pl_1 permit 1.0.0.0/24 # Define two routing policies, apply_med_50, which sets the MED for route 1.0.0.0/8 to 50, and apply_med_100, which sets the MED for route 1.0.0.0/8 to 100.
HP Switch(config)# router bgp 200 HP Switch(bgp)# neighbor 193.1.1.1 route-map localpref in HP Switch(bgp)# exit # Display the routing table on Switch D. HP Switch(config)# show ip bgp Local AS : 100 Local Router-id : 194.1.1.1 BGP Table Version : 1 Status codes: * - valid, > - best, i - internal, e - external, s - stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Nexthop Metric LocalPref Weight AsPath ------------------------------------------------------*>e 1.0.0.0/24 200.1.3.
Configuration procedure 1. Configure Switch A. # Configure IP addresses for interfaces (omitted.) # Configure the eBGP connection. HP Switch(config)# router bgp 65008 HP Switch(bgp)# bgp router-id 1.1.1.1 # Configure BGP GR stalepath-timeout (optional.) HP Switch(bgp)# bgp graceful-restart stalepath-time 360 HP Switch(bgp)# neighbor 200.1.1.1 remote-as 65009 # Add network 8.0.0.0/8 to the BGP routing table. HP Switch(bgp)# network 8.0.0.0/8 # Enable GR for BGP Peer. HP Switch(bgp)# neighbor 200.1.1.
3. Configure Switch C. # Configure IP addresses for interfaces (omitted.) # Configure the iBGP connection. HP Switch(config)# router bgp 65009 HP Switch(bgp)# bgp router-id 3.3.3.3 HP Switch(bgp)# neighbor 9.1.1.1 remote-as 65009 # Configure BGP to redistribute direct routes. HP Switch(bgp)# redistribute connected BGP Configuration Example # Enable GR for BGP Peer. HP Switch(bgp)# neighbor 9.1.1.
Displays specific information on the route and the BGP path attributes of the route. HP Switch(bgp)# show ip bgp 11.0.0.0/8 Local AS : 100 Local Router-id : Network Peer Metric Weight Best Type AS-Path Communities : : : : : : : : 11.0.0.0/8 10.0.102.40 0 0 No external 200 200:20 100:50 Nexthop : 10.0.102.40 Origin : incomplete Local Pref : Calc. Local Pref: 100 Valid : Yes Stale : No Network Peer Metric Weight Best Type AS-Path Communities : : : : : : : : 11.0.0.0/8 10.0.102.
127.0.0.0/8 reject 127.0.0.1/32 lo0 static connected 0 1 0 0 Synopsis: show ip route bgp [ipv4-addr] Displays only the BGP routes in the IP routing table. ipv4-addr IP address entered to filter the output to display only a particular host or network in the BGP routing table. HP Switch(bgp)# show ip route bgp IP Route Entries Destination Gateway VLAN Type Sub-Type Metric Dist. ---------------------------------------------------------------11.0.0.0/8 10.0.102.153 1 bgp 0 20 22.0.0.0/8 10.0.102.
HP Switch(bgp)# show ip bgp community 20 regexp “2” Local AS : 100 Local Router-id : 10.0.102.138 Status codes: * - valid, > - best, i - internal, e - external, s - stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Nexthop Metric LocalPref Weight AsPath -----------------------------------------------------------* e 11.0.0.0/8 10.0.102.40 0 0 200 ? Synopsis: show ip bgp community comm-num...
Network Nexthop Community -----------------------------------------------------------*>e 22.0.0.0/8 10.0.102.40 200:20 100:50 ? *e 22.0.0.0/8 10.0.102.198 no-export ? Synopsis: show ip bgp neighbor [ipv4-addr] Displays information about the state of BGP’s IPv4 peering sessions. HP Switch(bgp)# show ip bgp neighbor 10.0.102.40 BGP Neighbor 10.0.102.40 BGP Version : 4 Remote Router ID : 10.0.102.
Local Policy Denied Prefixes -----------------------------Routemap Bad lead AS Exceeded Max-prefix Exceeded Allow-as in Total Outbound --------0 n/a n/a n/a 0 Number of NLRIs in the update sent Inbound -------0 0 0 0 0 Max Min --------- -------1 0 Synopsis: show ip bgp as-path Displays the list of AS_PATHs that BGP has learned from the routing information it has received.
Figure 66 Solution 1 — Campus iBGP Devices A WAN Gateway Router B Enterprise Core Router C Enterprise Core Router (Campus Edge) D Campus Core Routing Switch E Campus Distribution Routing Switch F Edge Switch In the figure above, multiple campus domains are segmented by using BGP in the enterprise core. Traditionally, HP solutions have been used with devices E and F, facing the client or server network edges.
Figure 67 Multiple internal AS deployment with Campus iBGP solution The core routing switch (device C) can establish eBGP peering with the Enterprise Core. It is possible to utilize the foundation Campus iBGP feature to satisfy some of these solutions.
You have the alternative of using static routes or BGP to connect to your service provider. For multi-homing or policy control, you can choose to deploy BGP. This may be used for internet connectivity. Foundation iBGP solutions do not carry full internet routing tables, so the diagram above requires that 1) only default routes are taken from the internet and 2) multiple VRF instances do not exist at a single physical remote site.
Index A ABR Configuring Ranges, 201 Configuring virtual link, 202 ARP Cache table, 112 Configuring parameters, 118 Overview, 118 Proxy Enabling, 119 Local, 110 B Bootp Viewing a BOOTP gateway, 229 BSR Change priority setting, 72 Configuration Election, 97 Fault recovery, 97 Non-default configuration, 89 C C-RP Change hold time, 75 Election priority, 75 Enabling or disabling, 74 Router C-RP status and configruation, 91 Specify VLAN interface, 73 Command syntax area area-id virtual-link, 161, 162, 163 area
no ip irdp, 226 no ip load-sharing, 188 no ip local-proxy-arp, 110 no ip multicast routing, 66 no ip multicast-routing, 37 no ip ospf, 158, 159 no ip ospf ip-addr passive, 164 no ip pim-dense, 40 no vlan vid, 40 no ip pim-sparse lan-prune-delay vlan vid ip pim-sparse lan-prune-delay, 69 no ip proxy-arp, 110 no ip rip, 130 no ip rip poison-reverse, 133 no ip route, 66, 122 no ip routing, 66, 140 no ip udp-bcast-forward, 246 no ipv6 prefix-list, 205 no ipv6 route, 124 no match, 209, 210 no match interface vla
neighbor, 54 show ip pim bsr, 89 show ip pim interface, 51, 85, 86 show ip pim mroute, 50, 53, 85 show ip pim neighbor, 50, 51, 55, 87, 88 show ip pim pending, 88 show ip pim rp-candidate , 91 show ip pim rp-pending, 88 show ip pim rp-set, 90 show ip pim rpf-override, 79 show ip rip, 133 show ip rip interface, 135 show ip route bgp, 332 show ipv6 prefix-list, 207 show route-map, 209 show vrrp config, 264 show vrrp config global, 264 show vrrp statistics, 268 show vrrp statistics global, 268 show vrrp vlan,
Configuring, 233 Server support, 239 OSPF ABR, 191 Area types, 193 AS external LSA reduction, 196 AS external LSAs Type-3 summary LSAs, 195 ASBR, 191 Assigning loopback address, 146 Authentication Virtual link, 203 Backbone area, 193 Blocking advertisement Defining range, 153 Blocking range ASBR or NSSA, 154 Change administrative distance, 201 Change administrative distance default, 154 Changing interface settings virtual link, 203 VLAN, 155 Changing traps, 154 Changing VLAN interface, 202 Compliance settin
R RIP Changing RIP type, 130 Changing the RIP metric, 131 Enabling, 129 Globally, 129 Route redistribution, 132 VLAN, 130 Global parameters, 138 Interface parameters, 138 Modifying metric Redistribution, 132 Parameters and defaults, 138 Redistribution filters, 139 Redistribution into RIP, 139 Viewing, 133 Viewing interface information, 134 Viewing peer information, 136 Viewing redistribution filters, 137 Viewing redistribution information, 137 RIP authentication key Configuring, 130 RIP parameters Configuri
