Thanks ytti indeed we've PFC4 here: Mod Sub-Module Model Serial Hw Status ---- --------------------------- ------------------ ----------- ------- ------- 1 Distributed Forwarding Card WS-F6K-DFC4-E SALxxxx 1.2 Ok 2 Distributed Forwarding Card WS-F6K-DFC4-E SALxxx 1.2 Ok 3 Policy Feature Card 4 VS-F6K-PFC4 SALxxx 3.0 Ok 3 CPU Daughterboard VS-F6K-MSFC5 SALxxx 3.0 Ok 5 Distributed Forwarding Card WS-F6K-DFC4-A SALxxx 1.4 Ok
yes it's a long trip the path around 1k km Cheers Il giorno gio 21 mag 2020 alle ore 06:41 Saku Ytti <[email protected]> ha scritto: > On Wed, 20 May 2020 at 23:45, james list <[email protected]> wrote: > > Hey, > > > Dear experts > > my customer have some multicast flows which are detected sometime with > > peaks/latency. > > > They report 10-15 ms average latency and sometimes they detect 500-600 > ms. > > I wouldn't put it past measuring error. Is 10-15ms expected? I.e. this > is like 1000km? > > However based on just information available, perhaps flows timeout > periodically and hit the control-plane. I think SUP2T like PFC3 before > it punts all mcast, then programs flow in HW, then subsequently > hardware format it. If so, perhaps you can tune with multicast flow > timers. > > > - what I can use to try to decode pcap taken on Arista switch to check if > > the latency is really obtained checking protocol market timestamp ? > > Several samples, coffee and time. > > -- > ++ytti > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
