Paul, I am getting the same thing as you.
coresw1# show interfaces ge-1/0/30 vlan-tagging; unit 10 { vlan-id 10; family inet { address 172.16.10.1/24; } } unit 20 { vlan-id 20; family inet { address 172.16.20.1/24; } } coresw1# show | compare [edit protocols] + sflow { + interfaces ge-1/0/30.10; + interfaces ge-1/0/30.20; + } coresw1# commit check [edit protocols sflow] 'interfaces ge-1/0/30.10' sFlow can only be run on .0 interfaces error: configuration check-out failed Mike Gonnason On Thu, Mar 19, 2015 at 11:56 AM, Mike Gonnason <gonna...@gmail.com> wrote: > Hi Paul, > > I am just setting up a pair of EX4300 in a VC on 13.2X51-D30.4. Let me > attempt the config and see what happens. > > Mike Gonnason > > On Thu, Mar 19, 2015 at 6:47 AM, Paul S. <cont...@winterei.se> wrote: > >> Nobody ran into this one? >> >> Weird. >> >> >> On 3/16/2015 午後 10:40, Paul S. wrote: >> >>> Hi, >>> >>> In the past, I used to deploy similar configs on non-ELS switches, and >>> they mostly worked just fine with sflow. >>> >>> sw# show interfaces xe-0/2/0 >>> ether-options { >>> 802.3ad ae1; >>> } >>> >>> {master:0}[edit] >>> sw# show interfaces ae1 >>> description "Trunked to <>"; >>> vlan-tagging; >>> aggregated-ether-options { >>> minimum-links 1; >>> link-speed 10g; >>> } >>> unit 20 { >>> vlan-id 20; >>> family inet { >>> address <>; >>> >>> } >>> family inet6 { >>> address <>; >>> >>> } >>> } >>> >>> {master:0}[edit] >>> >>> Nothing but a port that's been trunked through another L2 switch. >>> >>> You could turn on sflow for this using `set protocols sflow interface >>> xe-0/2/0.20` and that would be the end of it. >>> >>> Now though, it says that enabling sflow on any other unit than 0 is "not >>> allowed." >>> >>> [edit protocols sflow] >>> 'interfaces xe-0/2/0.20' >>> sFlow can only be run on .0 interfaces >>> error: configuration check-out failed >>> >>> I'm running the Juniper recommended version of code on this one. >>> >>> Model: ex4300-48t >>> JUNOS EX Software Suite [13.2X51-D30.4] >>> >>> Having it on unit 0 produces no sflow datagrams (as expected, to be >>> honest) >>> >>> Collector Udp-port No. of samples >>> address >>> 10.100.10.100 6343 0 >>> >>> What are my options to make this switch work with the current way it is >>> set up, and have sflow exporting enabled? >>> >>> Thanks for reading! >>> >>> >>> >> _______________________________________________ >> 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