M4R4 specs

1
M4R4 specs

• Jerome.Durand_at_renater.fr
• These slides are the property of GIP RENATER,
  France. Any use of this material, even partial,
  is illegal without consentement of the author.

2
MSDP changes
3
References legend

• draft-ietf-mboned-msdp-deploy-06.txt
• RFC 3618 - MSDP
• RFC 3446 - Anycast RP with MSDP

RP
POP
Customer MSDP peer
MSDP peering - no mesh-group
MSDP peering - mesh-group (one color one
mesh-group)
4
Actual solution
RC
RC
RENATER-4
5
ProsCons

• Works, no complex peer-RPF rules as mesh-groups
  are used
• No redundancy, if one RP crashs, we loose half of
  the customers
• Having MSDP on each POP useless in that case,
  RP's could peer directly with the customers
• Hierarchy of mesh-groups useless

6
Objectives

• Simplify the architecture
• Usage of multicast does not justify such a
  complex architecture
• Have same redundancy for IPv4 unicast and IPv4
  multicast
• The service must never depend on a single router

7
Proposal
RC
RC
RC
RC
8
ProsCons

• As good as what we have today for redundancy, but
  really simplified !
• RP's can be setup on dedicated platforms
• No redundancy, if one RP crashs, we loose half of
  the customers

9
Backup possible
RC
RC
RC
RC
We have to propose the backup MSDP service but it
should remain up to the customer
10
Equipment used
1240x (NRs)
720x (dedicated routers)
11
Migration...

• Deploy the 2 new routers as anycast-RP's
• Include them in the MESH-GROUP of Anycast-RP's
• Start migrating MSDP peerings of few pilot sites
  on these routers
• Check and move on with all other customers
• Remove MSDP from core routers

12
MBGP
13
MBGP and customers

• 0.0.0.0/0 must be sent to the customers
• This is what is done today
• Sending only some RENATER prefix and configuring
  a default mroute is NOT POSSIBLE
• Problems with MSDP

14
ASM and/or SSM
15
ASM is like antibiotics...It's not automatic !!!

• RENATER provides both ASM and SSM service
• Customers can choose to have SSM but not ASM
• No RP
• No MSDP
• Opposite is not true as ASM deployment enables
  SSM service.
• Make sure that we don't force anyone to do MSDP
• Some processes to change maybe in NOC and GIP
  RENATER

16
NOC in same PIM domain
17
NOC

• Now in the same PIM domain
• Need to move the NOC in another PIM domain
• Have the NOC as any other site (much better for
  understanding customers concerns)
• Keep almost a zero usage of the RP's

18
Scoping

• Still under discussions

19
Scoping

• Do we want to have a scope reserved for RENATER
  community ?
• Dedicated addresses
• Not only based on TTL
• Makes it possible to have a good addressing
  architecture
• Address allocation

20
Monitoring
21
Remember

• We need to make sure the service is delivered
• We need to make sure there is no impact on
  network operations
• " It's multicast fault..."
• Heard of that ?
• This must never happen anymore! Advanced
  monitoring will help.

22
Monitoring

• Weathermap with IPv4 multicast traffic. This must
  be public information
• Internal RENATER traffic
• Traffic toward peers (customers ISP's)
• Weathermap for given groups/sources
• http//netmon.grnet.gr/multicast-map.shtml
• Must be public as well

23
Monitoring

• List of all multicast addresses used on the
  network
• PIM neighbors
• Alarms when PIM is configured and the neighbor is
  not here anymore
• Accounting of PIM neighbors
• At time T, I want to be able to know how many PIM
  neighbors there are

24
Monitoring

• MSDP peerings
• Alarms when peerings go down
• Numbers of SA received/sent on each peering
• MBGP peerings
• Alarms when peerings are not established
• Numbers of prefixes received/sent on each peering

25
Monitoring

• SAP announcements
• Number of announcements
• Ensure traffic for SAP group is normal
• Routers must not listen SAP announcements
• End-to-end multicast
• DBeacon
• Must be mandatory for customers to call us
• NTP synchronization
• Be proactive! The matrix must be green forever

26
Monitoring

• Looking glass
• IPv4 RPF information address ? show ip rpf
  address
• IPv4 PIM neighbors ? show ip pim neighbor
• IPv4 PIM mroute group address ? show ip mroute
  group address
• BGP IPv4 multicast summary ? show bgp ipv4
  multicast summary
• BGP IPv4 multicast prefix ? show bgp ipv4
  multicast prefix
• MSDP active source cache for a group ? show ip
  msdp sa-cache group
• SM will add these commands for the next looking
  glass release

27
Monitoring

• Advanced looking glass
• Let's drive the users through troubleshooting
  advices
• Problem encountered
• I can't receive
• I can't send
• Ask questions
• What is your source/group address
• Make a simple diagnostic
• "I can't receive your source/group via MSDP"
• "I don't receive your prefix via MBGP"
• Give some advices
• Check TTL that you use to send...
• Please configure a dbeacon and call this number
  0800 77 47 95 ?
• NOC to achieve this work