Flow sampling works on the address-family of layer3 subinterface, so it's under the "unit x family y", whether the unit is on an ae or a physical layer1/2 interface (since you want to sample all the traffic):
set interfaces ae4 unit 0 family inet sampling input set interfaces ae5 unit 0 family inet sampling input ... However the inline sampling «engine» must be activated on both fpc under chassis, and you'll probably activate it on all fpc of your chassis using an apply-group: set groups chassis-fpc-netflow chassis fpc <*> sampling-instance sample-1 set groups chassis-fpc-netflow chassis fpc <*> inline-services flex-flow-sizing set chassis fpc 0 apply-groups chassis-fpc-netflow set chassis fpc 1 apply-groups chassis-fpc-netflow set chassis fpc 2 apply-groups chassis-fpc-netflow ... Flex-flow-sizing exists since 15.1F5, with previous versions you must partition statically and manually the inline-sampling space. > Le 6 sept. 2018 à 17:53, Nelson, Brian <[email protected]> a écrit : > > With an MX480 running 15.1, can flow sampling be configured on an > aggregated interface? > All the examples I find are only applied to logical units of physical > interfaces. The documentation implies an ae interface is supported. > > Since the aggregated interfaces use physical interfaces from mic/fpc 0/0 > and 1/0, will I have to configure the same sampling instance on both fpc? _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
