D2.2.4: Final IPv4 to IPv6 Transition Cookbook for ... - 6NET

IST-2001-32603Deliverable D 2.2.4Figure 4-10: IPv6 traffic weathermap4.3.8.2. Routing monitoringDue to the lack of MIBs capable of monitoring IPv6 routing on Renater3 equipments, some scriptswere deployed capable of checking the status of BGP4+ peerings. Alarms are sent when peering godown.ASPath-tree was also deployed to give an overview of the routing policy in Renater. It cannot beused for operational routing monitoring but is useful for checking routing policies and make newrouting plans. Details on this tool are given in D6.2.4 [6NET-D624].4.3.8.3. Flow monitoringAt this stage, the routers on Renater3 are not capable of exporting IPv6 flows using Netflow v9.Nevertheless, a lot of work has been made to make the Netflow collector of RENATER capable ofcollecting these IPv6 flows. A first version of the collector is about to be submitted for tests to theinterested 6NET partners.4.3.9. IPv6 MulticastAn experimental IPv6 multicast network (M6Bone) is running on the Renater3 infrastructure. Itallows the connection of lots of sites, all over the world. This network allows all the sites connectedto test and develop IPv6 multicasting. It is connecting today over 80 sites and networks in Europe,Asia and Africa, making the network one of the most advanced multicast IPv6 network in theworld.45