If anyone has contacted jtac and has a PR to reference I would appreciate it (publically or privately). We are evaluating moving from 14.1 to 16.1R6 but I haven't yet tested v6 IPFIX.
-Michael >>-----Original Message----- >>From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf >>Of João Lyma. >>Sent: Friday, December 01, 2017 2:53 PM >>To: juniper-nsp@puck.nether.net >>Subject: Re: [j-nsp] IPV6 IPFIX Flow issues "nodata" on flow collector. >> >>Hi Gustavo, >> >>Same problem here... >>I use nfdump with nfsen. >>Router: MX480 with JUNOS 16.1R3.10 64-bit kernel >>JNPR-10.3-20160927.337663_build >> >>Regards, >> >>Lyma >> >> >>Em 30/11/2017 00:13, Gustavo Santos escreveu: >>> Hi, >>> >>> Anyone else had issues with Junos 16.1R4 with IPV6 and IPFIX? >>> >>> Here we use Plixer Scrutinizer as Flow collector and analyzer. IPv4 >>> flow >>> monitoring is working as intended. With IPv6 , looks like the collector >>> is >>> don´t know what to do with the data the Router is sending (MX480). >>> >>> After a Call , looks like the router is not sending the correct >>> templates >>> to Scrutinizer, the only information it can identify is the current >>> interface traffic from the flows. But no source and destination ipv6 >>> address. >>> >>> I already opened a JTAC support, but looks like the JTAC doesn´t even >>> have >>> a clue... I asked a friend that have the same router at another ISP and >>> he >>> have the same issue with NFSEN/FASTNETMON.. >>> _______________________________________________ >>> juniper-nsp mailing list juniper-nsp@puck.nether.net >>> https://puck.nether.net/mailman/listinfo/juniper-nsp >>_______________________________________________ >>juniper-nsp mailing list juniper-nsp@puck.nether.net >>https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
