HP VPN Firewall Appliances Appendix Protocol Reference

ManualsBrandsHP ManualsComputer AccessoriesHP ProCurve Switch xl Access Controller Module

101

102

103

104

105

106

107

108

109

110

Table Of Contents

Title Page
Contents
IP routing basics
- Routing table
- Dynamic routing protocols
- Route preference
- Load sharing
- Route backup
- Route recursion
- Route redistribution
Static routing
Default route
RIP
- Overview
- RIP operation
- RIP versions
- RIP message format
- Supported RIP features
- Protocols and standards
OSPF
- Overview
- OSPF packets
- LSA types
- OSPF area
- Router types
- Route types
- Route calculation
- OSPF network types
- DR and BDR
  - DR and BDR election
- Protocols and standards
IS-IS
- Overview
- Terminology
- IS-IS address format
- NET
- IS-IS area
  - Level-1 and Level-2
  - Route leaking
- IS-IS network types
  - Network types
  - DIS and pseudonodes
- IS-IS PDUs
- Supported IS-IS features
- Protocols and standards
BGP
- BGP speaker and BGP peer
- BGP message types
- BGP path attributes
- BGP route selection
- BGP route advertisement rules
- BGP load balancing
- Settlements for problems in large-scale BGP networks
- MP-BGP
  - MP-BGP extended attributes
  - Address family
- BGP configuration views
- Protocols and standards
IPv6 static routing
IPv6 default route
RIPng
- Overview
- RIPng working mechanism
- RIPng packet format
  - Basic format
  - RTE format
- RIPng packet processing procedure
  - Request packet
  - Response packet
- Protocols and standards
OSPFv3
- Overview
- Packets
- LSA types
- Timers
- Supported features
- Protocols and standards
IPv6 IS-IS
- Overview
IPv6 BGP
Multicast overview
- Overview
- Multicast models
- Multicast architecture
  - Multicast addresses
    - IP multicast addresses
    - Ethernet multicast MAC addresses
  - Multicast protocols
- Multicast packet forwarding mechanism
Multicast routing and forwarding
- Overview
- RPF check mechanism
  - RPF check process
  - RPF check implementation in multicast
- Static multicast routes
  - Changing an RPF route
  - Creating an RPF route
- Multicast forwarding across unicast subnets
- Multicast traceroute
IGMP
- Overview
- IGMP versions
- IGMPv1 overview
- IGMPv2 overview
  - Querier election mechanism
  - "Leave group" mechanism
- IGMPv3 overview
  - Enhancements in control capability of hosts
  - Enhancements in query and report capabilities
- IGMP SSM mapping
- IGMP proxying
- Protocols and standards
PIM
- Overview
- PIM-DM overview
- PIM-SM overview
- Administrative scoping overview
  - Relationship between admin-scoped zones and the global-scoped zone
- PIM-SSM overview
- Relationship among PIM protocols
- Protocols and standards
MSDP
- Overview
- How MSDP works
- Protocols and standards
IPv6 multicast routing and forwarding
- Overview
- RPF check mechanism
- RPF check implementation in IPv6 multicast
- IPv6 multicast forwarding across IPv6 unicast subnets
IPv6 PIM
- Overview
- IPv6 PIM-DM overview
- IPv6 PIM-SM overview
- IPv6 PIM-SSM overview
- Relationship among IPv6 PIM protocols
- Protocols and standards
MLD
- Overview
- MLD versions
- How MLDv1 works
- How MLDv2 works
- MLD message types
  - MLD query message
  - MLD report message
- MLD SSM mapping
- MLD proxying
- Protocols and standards
Support and other resources
- Contacting HP
  - Subscription service
- Related information
  - Documents
  - Websites
- Conventions
Index

4. When RP 6 receives the SA messages from RP 4 and RP 5 (suppose RP 5 has a higher IP address):

Although RP 4 and RP 5 are in the same AS (AS 3) and both are MSDP peers of RP 6, because RP

5 has a higher IP address, RP 6 accepts only the SA message from RP 5.

5. When RP 7 receives the SA message from RP 6:

Because the SA message is from a static RPF peer (RP 6), RP 7 accepts the SA message and

forwards it to other peer (RP 8).

6. When RP 8 receives the SA message from RP 7:

A BGP or MBGP route exists between two MSDP peers in different ASs. Because the SA message

is from an MSDP peer (RP 7) in a different AS, and the MSDP peer is the next hop on the BGP or

MBGP route to the source-side RP, RP 8 accepts the message and forwards it to its other peer (RP

9).

7. When RP 9 receives the SA message from RP 8:

Because RP 9 has only one MSDP peer, RP 9 accepts the SA message.

SA messages from paths other than those described previously are not accepted or forwarded by MSDP

peers.

Intra-domain Anycast RP through MSDP

Anycast RP refers to an application that enables load balancing and redundancy backup between two

or more RPs within a PIM-SM domain by configuring the same IP address for, and establishing MSDP

peering relationships between, these RPs.

As shown in Figure 64, w

ithin a PIM-SM

domain, a multicast source sends multicast data to multicast

group G, and Receiver is a member of the multicast group.

To implement Anycast RP:

1. Configure the same IP address (known as Anycast RP address, typically a private address) on

Router A and Router B. Be sure to configure a 32-bit subnet mask (255.255.255.255) for the

Anycast RP address. Namely, be sure to configure the Anycast RP address to a host address.

2. Configure these interfaces as C-RPs.

3. Establish an MSDP peering relationship between Router A and Router B. An MSDP peer address

must be different from the Anycast RP address.

NOTE:

Usually an Anycast RP address is configured on a logic interface, like a loopback interface.