[j-nsp] EX4200 Junos 12.3R3.4 Processor Utilization

[Matt Hite]

Not sure about the CPU spikes, but the log spam happens on MX platform
running 12.3R1.7, too.

Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'none-process'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'ipsec-key-management'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'secure-neighbor-discovery'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'local-policy-decision-function'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'craft-control'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'jflow-service'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'ilmi'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'internal-routing-service'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'helper'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'routing-socket-proxy'
Sep 20 22:31:03  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'disk-monitoring'
Sep 20 22:31:04  sv1-e1-re1 mgd[13435]: UI_OPEN_TIMEOUT: Timeout connecting
to peer 'adaptive-services'

etc.

-M


On Fri, Sep 20, 2013 at 1:59 PM, David Miller <dmiller at tiggee.com> wrote:

>
> Anyone running the JTAC recommended version of Junos (12.3R3.4) on any
> EX4200s and collecting configs with RANCID?  If so, then I would be
> curious to see what your proc utilization looks like.
>
> What I see on my 12.3R3.4 switch is a large CPU spike whenever RANCID
> collects data.
>
> The command that seems to be the issue is:
> show version detail | no-more
>
> On my switch the following 3 log messages appear in /var/log/messages
> every time 'show version detail' is run:
>
> Jun 14 03:19:39   mgd[2139]: UI_OPEN_TIMEOUT: Timeout connecting to peer
> 'remote-operations'
> Jun 14 03:19:39   mgd[2139]: UI_OPEN_TIMEOUT: Timeout connecting to peer
> 'dhcp'
> Jun 14 03:19:40   mgd[2139]: UI_OPEN_TIMEOUT: Timeout connecting to peer
> 'autoinstallation'
>
> Top shows:
> CPU states: 39.2% user,  0.0% nice, 55.3% system,  0.1% interrupt,  5.5%
> idle
> during a run of this show command.
>
> My SNMP monitoring over time shows spikes of:
> jnxOperatingCPU.FPC0  max: 81.80
> jnxOperatingCPU.RE0   max: 35.92
>
> Anyone else seeing this as well?
>
> I can reproduce this behavior exactly on a brand new switch, upgraded to
> 12.3R3.4, with vanilla default Juniper config on it (so I don't think
> that it is my config).
>
> Am I missing some simple config option?
> set chassis routing-engine dont-blow-out-cpus-on-simple-show-cmds
>
> - DMM
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>