IPv6 Multicast RENATER4

1
IPv6 Multicast - RENATER-4

• Florence.Picard_at_c-s.fr
• Jerome.Durand_at_renater.fr

2
Where are we ?
3
Where are we ?

• eMBGP IPv6 mcast peerings with Renater Testbed
  and Géant
• Inbound Filtering
• RENATER Testbed relaxed Filter with prefixes up
  to /64
• Géant strict filtering (same filters as for
  IPv6 unicast)
• Currently no outbound filtering
• Currently no local pref

4
Where are we ?

• PIM
• Disabled on IPv6 interfaces that connect partners
  except Geant
• MLD
• Disabled on every IPv6 interface where there is
  no host

5
Issues

• Interconnection with testbed
• How long will we have the 4GE ?
• GEANT peering policy
• Seems that Dante wants to review the policy
• Wait and see...!

6
Next steps

• Native connection towards customers that are
  ready
• Deployement on every NR
• Activating IPv6 multicast
• Establishing iMBGP IPv6 mcast peering with RRs
• Configuring M6Bone global RP as static global RP
• Configuring scope boundaries
• First, testing the service with 2 customers
• GIP Renater, RAP ?
• End of May
• Then, opening the service to other customers

7
Next steps

• FM6Bone migration
• NRI-DOM dedicated to
• FM6Bone tunnels
• RP support
• Rennes6 installation at Interxion
• Réunion to be migrated on Rennes6
• End of May

8
Next steps

• RPs on RENATER
• 2 embedded-RPs on NRI-DOM
• Renater Scope
• Already configured
• RP address 200166030001
• Global Scope
• Not yet configured. Deadline mid-may
• RENATER community expected to use this RP
• M6bone as static global RP on NRs

9
Next steps

• Scope management
• Scope boundary
• To be deployed on client/partner links when
  deploying IPv6 multicast on each NR
• On every interface where PIM is activated for
  IPv6
• Implementation has began on NRI-B
• Commands used
• On Cisco 720x official command available
• On Cisco 124xx hidden command for the moment

10
Next steps

• Monitoring
• Monitoring MIB not available
• MBGP IPv6 multicast peerings supervision with
  Nagios
• Update of the current BGP script used for IPv4
  unicast/multicast and IPv6 unicast
• SSH connection on routers
• In progress

11
Next steps

• Dbeacon
• Installed on Leeds
• Dbeacon Group for IPv6 multicast to be defined
• Writing a procedure for customers
• Will explain how to install a Dbeacon and to
  configure the RENATER Dbeacon group
• Will be sent to the sites when asking for the
  IPv6 multicast service
• End of June

12
Next steps

• AS-Path-Tree
• Requests sent to NR Lyon
• Duplicating and adapting the script done for IPv6
  unicast
• End of May

13
Next steps

• Looking glass
• IPv6 RPF information address ? show ipv6 rpf
  address
• IPv6 PIM neighbors ? show ipv6 pim neighbor
  details
• IPv6 mroute group address ? show ipv6 mroute
  group address
• BGP IPv6 multicast prefix prefix ? show bgp
  ipv6 multicast prefix
• BGP IPv6 multicast neighbor ? show bgp ipv6
  multicast neighbor
• SM will add these commands for the next looking
  glass release.

14
Next steps

• QOSmetrics
• QOSmetrics configured for "RENATER channels"
• will be done for both IPv4 IPv6 multicast
• FXA JD

15
Next steps

• Netflow
• 720x for tunneling router and RP are netflow
  capable for IPv6 multicast
• Need to update the collector to check what is
  happening
• To be done at a later stage
• FXA JD

16
Questions

• Use BGP unicast for RPF
• Makes it possible to make IPv6 multicast
  deployment EASY !
• MBGP still used when we need it
• Non-RENATER peers
• Customers who want MBGP
• Cutomers behind tunnels or dedicated multicast
  connections
• Move slowly with few pilot customers to test the
  thing. Then generalize.

17
Questions

• Service enabling process
• With actual specifications, customers can enable
  the service just enabling PIM
• No need that they tell us!

• Advantages
• Easier to manage
• A single IPv6 (ucastmcast) package offered
• Stimulates sites to use the service as they have
  it by default

• Disadvantages
• More difficult to trace the multicast service
  users
• More difficult to understand if users do the
  correct thing

18
Questions

• Service enabling process - tunnels
• Different as before as a new interface is needed
• Will be solved with the tunnel broker when
  multicast is supported
• When do we accept a new tunnel and how do we
  configure it?
• The site netadmin has to ask for the service (or
  to give its acknowledgement)
• The same prefix will be routed for unicast AND
  multicast
• What do we do today with sites not matching these
  constraints?
• Where do we store the information about the
  tunnel? SSONOC to come up with a conclusion on
  that one.

19
Questions

• Service enabling process - Embedded RP of RENATER
• How do customers ask to use our embedded-RP?
• When they ask they are given a multicast prefix
  (derived from the RP address and their unicast
  prefix)
• SAGA ?

20
Questions

• M6Bone management
• Agreement not to have that managed by the NOC
  (too much extra work)
• Do we want to keep that "production" router in
  the testbed as it is today?
• Could we move the service in RENATER and have
  that managed by the GIP RENATER?
• Hardwaresoftware maintenance NOC
• Configuration management RENATER

21
Questions

• IPv4/IPv6 multicast translation
• Move the service on RENATER-4
• Now in testbed and GIP RENATER
• One of the 2 H323 gatekeepers of RENATER can be
  used for this purpose
• Of course still in RENATER's hands

22
Questions

• Routers collocation
• With IPv4 mcast dedicated 720x ?
• Router with tunnels and RP router ?

23
(No Transcript)