Hi,
Just to update everyone on this, this is still repeating on the latest
recommended release (which as of now is 14.1-X53-D30)
Dec 11 01:46:16 ar-0.csit.lax.queryfoundry.net sflowd[1340]:
ipc_pipe_read cannot exceed pipe size 1500 bytes
Dec 11 01:46:16 ar-0.csit.lax.queryfoundry.net pfex: Sflow client:
Socket to sflowd closed
Dec 11 01:46:16 ar-0.csit.lax.queryfoundry.net pfex: pfe_bcm sflow ipc
error 0
Dec 11 01:46:37 ar-0.csit.lax.queryfoundry.net last message repeated
309 times
Dec 11 01:46:37 ar-0.csit.lax.queryfoundry.net sflowd[1340]:
ipc_pipe_read cannot exceed pipe size 1500 bytes
Dec 11 01:46:37 ar-0.csit.lax.queryfoundry.net pfex: Sflow client:
Socket to sflowd closed
Dec 11 01:46:37 ar-0.csit.lax.queryfoundry.net pfex: pfe_bcm sflow ipc
error 0
.
[email protected]# run show version
fpc0:
--------------------------------------------------------------------------
Hostname: ar-0.csit.lax.queryfoundry.net
Model: ex4300-48t
Junos: 14.1X53-D30.3
JUNOS EX Software Suite [14.1X53-D30.3]
JUNOS FIPS mode utilities [14.1X53-D30.3]
JUNOS Online Documentation [14.1X53-D30.3]
JUNOS EX 4300 Software Suite [14.1X53-D30.3]
JUNOS Web Management Platform Package [14.1X53-D30.3]
JUNOS py-base-powerpc [14.1X53-D30.3]
fpc1:
--------------------------------------------------------------------------
Hostname: ar-0.csit.lax.queryfoundry.net
Model: ex4300-48t
Junos: 14.1X53-D30.3
JUNOS EX Software Suite [14.1X53-D30.3]
JUNOS FIPS mode utilities [14.1X53-D30.3]
JUNOS Online Documentation [14.1X53-D30.3]
JUNOS EX 4300 Software Suite [14.1X53-D30.3]
JUNOS Web Management Platform Package [14.1X53-D30.3]
JUNOS py-base-powerpc [14.1X53-D30.3]
On 10/31/2015 05:33 AM, Adam Rothschild wrote:
Hi Paul,
Was just curious -- were you able to identify a fix for this?
About to open a JTAC case on same. :)
Best,
-a
On Wed, Apr 8, 2015 at 10:13 PM, Paul S. <[email protected]> wrote:
Hi guys,
Picked up a few EX4300s to use as L3 switches, so far they've worked well.
Deployed a few new ones today, upgraded them to the latest recommended by
JTAC and set them up in a 2 member VC. I also turned on graceful switchover,
commit synchronization and non-stop-routing.
fpc0:
--------------------------------------------------------------------------
Model: ex4300-48p
JUNOS EX Software Suite [13.2X51-D30.4]
fpc1:
--------------------------------------------------------------------------
Model: ex4300-48p
JUNOS EX Software Suite [13.2X51-D30.4]
Then, I tried to turn sflow on. It works, sends samples to the collectors,
but is spamming the logs with this.
Apr 9 02:00:36 ar-0 pfex: pfe_bcm sflow ipc error 0
Apr 9 02:00:50 ar-0 last message repeated 22 times
Apr 9 02:02:50 ar-0 last message repeated 183 times
I'm not exactly sure of what this means, anyone ever see it around before
and can it be ignored or should I turn sflow off for now?
Thanks.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
