Pages

Wednesday, January 19, 2011

Anycast RP

Anycast RP provide RP load balancing and RP redundancy in the network. Each source and receiver of the network will communicate to the nearest RP to request or send a multicast traffic.The source information will be transmitted between two RPs via MSDP protocol in order to sync the source information between MSDP peer. 

In this exmaple we have configured R1 and R2 as RP. They announce themselves by using the Auto-RP protocol. MSDP forms a peer relationship between R1 and R2. The RP address has been configure to 1.1.1.1/24 identical to both routers. Loopback 1 is used as a source of msdp peer in order to establish the relationship between them. Please see the diagram between for the network detail.




Configuration


R1

!
interface Loopback0
 description RP1 address
 ip address 1.1.1.1 255.255.255.0
 ip pim sparse-mode
!
interface Loopback1
 description MSDP address
 ip address 192.168.1.1 255.255.255.0
!
interface FastEthernet0/0
 ip address 10.1.1.1 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 10.1.2.1 255.255.255.0
 ip pim sparse-mode

ip pim send-rp-announce Loopback0 scope 5
ip pim send-rp-discovery Loopback0 scope 5
ip msdp peer 192.168.2.1 connect-source Loopback1
!


R2

interface Loopback0
 description RP2 address
 ip address 1.1.1.1 255.255.255.0
 ip pim sparse-mode
!
interface Loopback1
 description MSDP address
 ip address 192.168.2.1 255.255.255.0
!
interface FastEthernet0/0
 ip address 10.1.1.2 255.255.255.0
 ip pim sparse-mode
!
interface FastEthernet0/1
 ip address 10.1.3.1 255.255.255.0
 ip pim sparse-mode

ip pim send-rp-announce Loopback0 scope 5
ip pim send-rp-discovery Loopback0 scope 5
ip msdp peer 192.168.1.1 connect-source Loopback1
!





debug ip msdp peer


*Mar  1 00:30:58.099: MSDP(0): 192.168.2.1: Sending TCP connect
*Mar  1 00:30:58.191: %MSDP-5-PEER_UPDOWN: Session to peer 192.168.2.1 going up
*Mar  1 00:30:58.191: MSDP(0): 192.168.2.1: TCP connection established
*Mar  1 00:30:59.139: MSDP(0): 192.168.2.1: Sending Keepalive message to peer
*Mar  1 00:31:00.139: MSDP(0): 192.168.2.1: Building SA message from SA cache
*Mar  1 00:31:05.443: MSDP(0): 192.168.2.1: Received 3-byte msg 0 from peer
*Mar  1 00:31:05.447: MSDP(0): 192.168.2.1: Keepalive TLV


Verify configuration

R2#sh ip msdp peer
MSDP Peer 192.168.1.1 (?), AS ?
  Connection status:
    State: Up, Resets: 0, Connection source: Loopback1 (192.168.2.1)
    Uptime(Downtime): 00:13:41, Messages sent/received: 14/14
    Output messages discarded: 0
    Connection and counters cleared 00:14:35 ago
  SA Filtering:
    Input (S,G) filter: none, route-map: none
    Input RP filter: none, route-map: none
    Output (S,G) filter: none, route-map: none
    Output RP filter: none, route-map: none
  SA-Requests:
    Input filter: none
  Peer ttl threshold: 0
  SAs learned from this peer: 1     ( SA learned a source from peer)
  Input queue size: 0, Output queue size: 0
  MD5 signature protection on MSDP TCP connection: not enabled


No comments:

Post a Comment