[GTER] RES: MX104 com CPU alto
Diogo Montagner
diogo.montagner at gmail.com
Thu Aug 3 21:42:29 -03 2017
Dah uma olhada nas autenticacoes rejeitadas. Eu imagino que vc deve ter um
numero alto de rejeicoes.
On Fri, 4 Aug 2017 at 01:20, Soares <soares.silva at tnetsolucoes.com.br>
wrote:
> Diogo,
> Esta em 15
>
> interfaces {
> pp0 {
> unit "$junos-interface-unit" {
> ppp-options {
> chap;
> pap;
> }
> pppoe-options {
> underlying-interface "$junos-underlying-interface";
> server;
> }
> keepalives interval 15;
> family inet {
> filter {
> input "$junos-input-filter";
> output "$junos-output-filter";
> }
> unnumbered-address "$junos-loopback-interface";
> }
> }
> }
> }
>
>
> -----Mensagem original-----
> De: gter [mailto:gter-bounces at eng.registro.br] Em nome de Diogo Montagner
> Enviada em: quarta-feira, 2 de agosto de 2017 22:33
> Para: Grupo de Trabalho de Engenharia e Operacao de Redes <
> gter at eng.registro.br>
> Cc: Noc <noc at tnetsolucoes.com.br>
> Assunto: Re: [GTER] MX104 com CPU alto
>
> O seu jpppd e authd eatao altos.
>
> Isso pode indicar muitas autenticacoes negativas. Neste caso, pppoe
> lockout e/ou jailed authentication podem resolver esse problema.
>
> Qual eh o valor do ppp keepalive que vc configurou ?
>
> On Thu, 3 Aug 2017 at 05:48, Soares <soares.silva at tnetsolucoes.com.br>
> wrote:
>
> > Boa tarde.
> >
> > Subimos recentemente um MX104 para funcionar como BRAS-PPPOE.
> >
> > No momento estamos com 1860 clientes.
> > A CPU está batendo no 50%. Gostaria de uma ajuda para identificar o
> > que está causando este processamento.
> >
> > >show system processes extensive
> > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU
> COMMAND
> > 10 root 1 155 52 0K 16K RUN 729.7H
> > 50.49% idle
> > 1732 root 3 46 0 199M 90056K sigwai 74.7H 21.88%
> > jpppd
> > 1733 root 1 8 0 182M 80532K wait 32.5H
> > 8.74% authd
> > 1589 root 8 45 0 179M 102M ucond 23.3H 2.69%
> > bbe-smgd
> > 1559 root 2 -26 -26 64516K 24020K nanslp 44.0H 2.54%
> > chassisd
> > 40 root 1 -8 0 0K 16K syncer 85:38
> > 0.10% syncer
> > 1564 root 1 42 0 61508K 38752K select 530:38 0.00%
> mib2d
> > 1568 root 1 41 0 76488K 28356K select 452:55 0.00%
> pfed
> > 1737 root 1 40 0 31800K 24236K select 368:50 0.00%
> snmpd
> > 1731 root 3 49 0 168M 62360K sigwai 202:12 0.00%
> > jl2tpd
> > 12 root 1 -36 -139 0K 16K WAIT 156:28
> > 0.00% swi7: clock
> > 36 root 1 155 52 0K 16K pgzero 140:58
> > 0.00% pagezero
> >
> > > show chassis routing-engine
> > Routing Engine status:
> > Slot 0:
> > Current state Master
> > Election priority Master (default)
> > Temperature 30 degrees C / 86 degrees F
> > CPU temperature 37 degrees C / 98 degrees F
> > DRAM 3968 MB (4096 MB installed)
> > Memory utilization 29 percent
> > 5 sec CPU utilization:
> > User 21 percent
> > Background 0 percent
> > Kernel 31 percent
> > Interrupt 1 percent
> > Idle 47 percent
> > 1 min CPU utilization:
> > User 22 percent
> > Background 0 percent
> > Kernel 28 percent
> > Interrupt 1 percent
> > Idle 49 percent
> > 5 min CPU utilization:
> > User 22 percent
> > Background 0 percent
> > Kernel 29 percent
> > Interrupt 1 percent
> > Idle 48 percent
> > 15 min CPU utilization:
> > User 22 percent
> > Background 0 percent
> > Kernel 30 percent
> > Interrupt 1 percent
> > Idle 48 percent
> >
> >
> > --
> > gter list https://eng.registro.br/mailman/listinfo/gter
> >
> --
> ./diogo -montagner
> JNCIE-SP 0x41A
> --
> gter list https://eng.registro.br/mailman/listinfo/gter
>
> --
> gter list https://eng.registro.br/mailman/listinfo/gter
>
--
./diogo -montagner
JNCIE-SP 0x41A
More information about the gter
mailing list