Jump to content
Калькуляторы

Juniper MX80 - отвалился без прелюдий Junos: 13.3R7.3

Reply to this topic

smart85   

smart85
Posted (edited) · Report post

Коллеги, добрый день!

Вчера отвалился бордер, МХ80, софт Junos: 13.3R7.3

Перестал отвечать на SSH, SNMP, отвалились пиры, развалился ae, в логах:

Dec 14 22:48:34 MX80-1 tfeb0 TNPC CM received unknown trigger (type Queue, id 1)

Dec 14 22:49:40 MX80-1 tfeb0 TNPC CM received unknown trigger (type Queue, id 1)

Dec 14 22:50:10 MX80-1 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/1 - ATTACHED state - acting as standby link

Dec 14 22:50:10 MX80-1 lacpd[1378]: LACPD_TIMEOUT: xe-0/0/1: lacp current while timer expired current Receive State: CURRENT

Dec 14 22:50:10 MX80-1 /kernel: ae_bundlestate_ifd_change: bundle ae0: bundle IFD minimum links not met 0 < 1

Dec 14 22:50:10 MX80-1 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/0 - ATTACHED state - acting as standby link

Dec 14 22:50:10 MX80-1 lacpd[1378]: LACPD_TIMEOUT: xe-0/0/0: lacp current while timer expired current Receive State: CURRENT

Dec 14 22:50:10 MX80-1 lacpd[1378]: LACP_INTF_DOWN: ae0: Interface marked down due to lacp timeout on member xe-0/0/0

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (Internal AS NNNN) changed state from Established to Idle (event Stop) (instance master)

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event Stop) (instance master)

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event Stop) (instance master)

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event Stop) (instance master)

Dec 14 22:50:10 MX80-1 rpd[1465]: bgp_ifachange_group:7408: NOTIFICATION sent to XXXX (External AS NNNN): code 6 (Cease) subcode 6 (Other Configuration Change), Reason: Interface change for the peer-group

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event Stop) (instance master)

Dec 14 22:50:10 MX80-1 rpd[1465]: bgp_ifachange_group:7408: NOTIFICATION sent to XXXX (External AS NNNN): code 6 (Cease) subcode 6 (Other Configuration Change), Reason: Interface change for the peer-group

Dec 14 22:50:10 MX80-1 mib2d[1462]: SNMP_TRAP_LINK_DOWN: ifIndex 520, ifAdminStatus up(1), ifOperStatus down(2), ifName ae0

Dec 14 22:50:10 MX80-1 rpd[1465]: bgp_ifachange_group:7408: NOTIFICATION sent to XXXX (External AS NNNN): code 6 (Cease) subcode 6 (Other Configuration Change), Reason: Interface change for the peer-group

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_OSPF_NBRDOWN: OSPF neighbor XXXX (realm ospf-v2 ae0.1301 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)

Dec 14 22:50:10 MX80-1 rpd[1465]: RPD_OSPF_NBRDOWN: OSPF neighbor XXXX (realm ospf-v2 ae0.1405 area 0.0.0.0) state changed from Full to Down due to KillNbr (event reason: interface went down)

Dec 14 22:50:13 MX80-1 tfeb0 TNPC CM received unknown trigger (type Queue, id 1)

Dec 14 22:50:13 MX80-1 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/1 - DETACHED state - will not carry traffic

Dec 14 22:50:13 MX80-1 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/0 - DETACHED state - will not carry traffic

Dec 14 22:50:15 MX80-1 alarmd[1498]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 0 Major Errors

Dec 14 22:50:15 MX80-1 craftd[1361]: Major alarm set, FPC 0 Major Errors

Dec 14 22:50:15 MX80-1 tfeb0 MQCHIP(0) MALLOC Pre-Q Reference Count underflow - decrement below zero

Dec 14 22:50:16 MX80-1 tfeb0 CMLC: Error seting error, no opcode handle

Dec 14 22:50:17 MX80-1 tfeb0 CMLC: action for error, no opcode handle

Dec 14 22:50:17 MX80-1 tfeb0 CMLC: action for error, no opcode handle

Dec 14 22:50:17 MX80-1 tfeb0 TOE Pkt Xfer:** WEDGE DETECTED IN PFE 0 stream 0 TOE host packet transfer: reason code 0x1

Dec 14 22:50:17 MX80-1 tfeb0 CMLC: Error seting error, no opcode handle

Dec 14 22:50:18 MX80-1 tfeb0 CMLC: action for error, no opcode handle

Dec 14 22:50:18 MX80-1 tfeb0 CMLC: action for error, no opcode handle

Dec 14 22:50:18 MX80-1 tfeb0 Host Loopback:HOST LOOPBACK WEDGE DETECTED IN PATH ID 0

Dec 14 22:50:18 MX80-1 tfeb0 TNPC CM received unknown trigger (type Queue, id 1)

Dec 14 22:50:34 MX80-1 rpd[1465]: bgp_hold_timeout:4304: NOTIFICATION sent to XXXX (External AS NNNN): code 4 (Hold Timer Expired Error), Reason: holdtime expired for XXXX (External AS NNNN), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 4288571519 snd_nxt: 4288571557 snd_wnd: 65536 rcv_nxt: 2436634691 rcv_adv: 2436651075, hold timer out 90s, hold timer remain 0s

Dec 14 22:50:34 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event HoldTime) (instance master)

Dec 14 22:50:34 MX80-1 rpd[1465]: bgp_hold_timeout:4304: NOTIFICATION sent to XXXX (External AS NNNN): code 4 (Hold Timer Expired Error), Reason: holdtime expired for XXXX (External AS NNNN), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 3032129018 snd_nxt: 3032129056 snd_wnd: 66608 rcv_nxt: 209540101 rcv_adv: 209556485, hold timer out 90s, hold timer remain 0s

Dec 14 22:50:34 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event HoldTime) (instance master)

Dec 14 22:50:46 MX80-1 rpd[1465]: RPD_OSPF_NBRDOWN: OSPF neighbor XXXX (realm ospf-v2 xe-0/0/3.0 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead)

Dec 14 22:50:49 MX80-1 tfeb0 Packet send failed

Dec 14 22:50:54 MX80-1 last message repeated 3 times

Dec 14 22:51:09 MX80-1 last message repeated 6 times

Dec 14 22:51:09 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:09 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:09 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179309602. States to be processed - 132741

Dec 14 22:51:14 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:14 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:14 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179313798. States to be processed - 140872

Dec 14 22:51:14 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:14 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:15 MX80-1 rpd[1465]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Dec 14 22:51:19 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:19 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:19 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179323475. States to be processed - 154125

Dec 14 22:51:19 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:19 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:20 MX80-1 rpd[1465]: bgp_hold_timeout:4304: NOTIFICATION sent to XXXX (Internal AS NNNN): code 4 (Hold Timer Expired Error), Reason: holdtime expired for XXXX (Internal AS NNNN), socket buffer sndcc: 8170 rcvcc: 0 TCP state: 4, snd_una: 2759988450 snd_nxt: 2759989898 snd_wnd: 16384 rcv_nxt: 1121198387 rcv_adv: 1121214771, hold timer out 90s, hold timer remain 0s

Dec 14 22:51:20 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (Internal AS NNNN) changed state from Established to Idle (event HoldTime) (instance master)

Dec 14 22:51:24 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:24 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:25 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:25 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:25 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179335561. States to be processed - 166174

Dec 14 22:51:29 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:29 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:30 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:30 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:30 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179337959. States to be processed - 168571

Dec 14 22:51:30 MX80-1 rpd[1465]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Dec 14 22:51:32 MX80-1 rpd[1465]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Dec 14 22:51:34 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:34 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:35 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:35 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:35 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179349225. States to be processed - 179732

Dec 14 22:51:35 MX80-1 rpd[1465]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Dec 14 22:51:37 MX80-1 rpd[1465]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Dec 14 22:51:37 MX80-1 rpd[1465]: bgp_hold_timeout:4304: NOTIFICATION sent to XXXX (External AS NNNN): code 4 (Hold Timer Expired Error), Reason: holdtime expired for XXXX (External AS NNNN), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 175629400 snd_nxt: 175629457 snd_wnd: 16384 rcv_nxt: 1806701893 rcv_adv: 1806718277, hold timer out 90s, hold timer remain 0s

Dec 14 22:51:37 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event HoldTime) (instance master)

Dec 14 22:51:38 MX80-1 rpd[1465]: bgp_hold_timeout:4304: NOTIFICATION sent to XXXX (External AS NNNN): code 4 (Hold Timer Expired Error), Reason: holdtime expired for XXXX (External AS NNNN), socket buffer sndcc: 76 rcvcc: 0 TCP state: 4, snd_una: 2988378135 snd_nxt: 2988378192 snd_wnd: 32008 rcv_nxt: 1292149130 rcv_adv: 1292165514, hold timer out 90s, hold timer remain 0s

Dec 14 22:51:38 MX80-1 rpd[1465]: RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer XXXX (External AS NNNN) changed state from Established to Idle (event HoldTime) (instance master)

Dec 14 22:51:39 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:39 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:40 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:40 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:40 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179356603. States to be processed - 183864

Dec 14 22:51:44 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:44 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:45 MX80-1 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Dec 14 22:51:45 MX80-1 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (298844160) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Dec 14 22:51:45 MX80-1 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 179356603. States to be processed - 185896

Dec 14 22:51:49 MX80-1 tfeb0 Packet send failed

Dec 14 22:51:54 MX80-1 last message repeated 3 times

Dec 14 22:52:22 MX80-1 last message repeated 10 times

Dec 14 23:03:53 MX80-1 last message repeated 236 times

Dec 14 23:13:53 MX80-1 last message repeated 240 times

Dec 14 23:23:53 MX80-1 last message repeated 240 times

Dec 14 23:33:53 MX80-1 last message repeated 240 times

Dec 14 23:36:18 MX80-1 last message repeated 58 times

 

После перезагрузки все поднялось. Помогите пожалуйста понять возможную причину отвала.

Спасибо!

Edited by mse.rus77

Share this post

Link to post
Share on other sites

Mystray   

Mystray
Posted · Report post

Может PR1108826 ?

Problem Report

Number PR1108826

Title The TOE wedge which may cause traffic blackhole and FPC restart may occur after upgrading to 13.3R7.3 or 14.1R5.4

Release Note

Due to a software defect found in 13.3R7.3 and 14.1R5.4 inclusively, Juniper Networks strongly discourage the use of Junos software version 13.3R7.3 on routers with MQ-based MPC. This includes MX-Series with MPC1, MPC2; all mid-range MX-Series; and some of EX9200 line cards.

Severity Critical

Status Closed

Last Modified 2016-05-16 21:37:08 PDT

Resolved In 13.3R7 13.3R7-S1 13.3R8 14.1R5 14.1R5-S1 14.1R6 14.2R4 14.2R5 15.1R2 15.1F3 16.1R1

Operating System Junos

Product MX-series, EX Series

Functional Area software

Problem

This issue can be identified by observing the following syslog messages:

router-re0 fpc3 MQCHIP(0) MALLOC Pre-Q Reference Count underflow - decrement below zero

<follow by>

router-re0 fpc3 Host Loopback:HOST LOOPBACK WEDGE DETECTED IN PATH ID 0

router-re0 fpc3 TOE Pkt Xfer:** WEDGE DETECTED IN PFE 0 stream 0 TOE host packet transfer: reason code 0x1

..

 

The list of MQ-based MPC, chassis, and line card for MX-Series are:

MX-Series Line Cards for MX960, MX480, MX240:

MX-MPC1-3D, MX-MPC1E-3D,MX-MPC1-3D-Q,MX-MPC1E-3D-Q,

MX-MPC2-3D, MX-MPC2E-3D,MX-MPC2-3D-Q,MX-MPC2E-3D-Q,

MX-MPC2-3D-EQ, MX-MPC2E-3D-EQ, MX-MPC2E-3D-P,

MX-MPC2E-3D-NG, MX-MPC2E-3D-NG-Q

MPC-3D-16XGE-SFP

 

Mid-range MX-Series routers

MX5,MX10,MX40,MX80,MX104

 

EX9200 Line Cards

EX9200-40T, EX9200-40F, EX9200-40F-M

Triggers

This issue might be seen if following conditions are met:

* On MQ-based MPC/FPC

* Upgrade to Junos software version 13.3R7.3 or 14.1R5.4

* Heavy traffic with large packets (packet size larger than 5000 bytes)

Share this post

Link to post
Share on other sites

orlik   

orlik
Posted · Report post

Toe wedge, обновляйтесь , должно помочь . Там в р8-р9 было парочку таких проблем. Хотя я бы рекомендовал дождаться r10, там тоже будут фиксы для подобной проблемы. Позже смогу посмотреть под какой pr ваша проблема матчится

Share this post

Link to post
Share on other sites

dmvy   

dmvy
Posted · Report post

Было год назад, что связь прервалась. оказалось, что PFE перезагрузился сам собой. RE при этом продолжал работать и связь восстановилась. 10-15 минут простоя было. Больше такого не было.

Share this post

Link to post
Share on other sites

smart85   

smart85
Posted · Report post

Toe wedge, обновляйтесь , должно помочь . Там в р8-р9 было парочку таких проблем. Хотя я бы рекомендовал дождаться r10, там тоже будут фиксы для подобной проблемы. Позже смогу посмотреть под какой pr ваша проблема матчится

Здравствуйте. Да, похоже, что оно. На текущий момент рекомендуют:

Junos 13.3R9/14.1R7

Обновиться на 13.3Р9 или 14.1Р7, а дальше ждать 13.3Р10? Как лучше поступить?

Спасибо!

Share this post

Link to post
Share on other sites

orlik   

orlik
Posted · Report post

 

Обновиться на 13.3Р9 или 14.1Р7, а дальше ждать 13.3Р10? Как лучше поступить?

Спасибо!

 

R9 должно быть достаточно для не повторения проблемы

Share this post

Link to post
Share on other sites

smart85   

smart85
Posted · Report post

Коллеги, всем доброго времени суток!

Перед обновлением по решил сделать request system software validate jinstall-ppc-13.3R9.13-domestic-signed.tgz - после чего роутер помер, помог только ребут по питанию.

user@MX80-1> request system software validate jinstall-ppc-13.3R9.13-domestic-signed.tgz

Checking compatibility with configuration

Initializing...

rm: /var/v/c/var/etc/pam.conf: Operation not permitted

rm: /var/v/c/var/etc: Directory not empty

rm: /var/v/c/var: Directory not empty

rm: /var/v/c: Directory not empty

Using jbase-ppc-13.3R7.3

// далее тишина

 

В логах - тишина:

Dec 20 18:01:29 MX80-1 rpd[1459]: bgp_listen_accept: Connection attempt from unconfigured neighbor: xxxx+58510

Dec 20 18:01:29 MX80-1 rpd[1459]: bgp_listen_accept:4587: NOTIFICATION sent to xxxx+58510 (proto): code 6 (Cease) subcode 5 (Connection Rejected), Reason: Connection attempt from unconfigured neighbor: xxxx+58510

Dec 20 18:42:07 MX80-1 eventd[1152]: SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down

Dec 20 18:42:07 MX80-1 eventd[1152]: SYSTEM_OPERATIONAL: System is operational

Dec 20 18:42:07 MX80-1 /kernel: platform_early_bootinit: MX-PPC Series Early Boot Initialization

Dec 20 18:42:07 MX80-1 /kernel: mxppc_set_re_type: hw.board.type is MX80

Dec 20 18:42:07 MX80-1 /kernel: mxppc_set_re_type: REtype:78, model:mx80, model:MX80, i2cid:2447

Dec 20 18:42:07 MX80-1 /kernel: WDOG initialized

Dec 20 18:42:07 MX80-1 /kernel: Copyright © 1996-2015, Juniper Networks, Inc.

 

Что это было? Баг или фича?

 

Спасибо за внимание.

Share this post

Link to post
Share on other sites

smart85   

smart85
Posted · Report post

Баг, посмотрите , может корки создались ...

Да, корки свалились:

user@MX80-1> show system core-dumps

-rw-rw---- 1 root wheel 247640064 Dec 20 18:42 /var/crash/vmcore.0

/var/tmp/*core*: No such file or directory

/var/tmp/pics/*core*: No such file or directory

-rw-r--r-- 1 root wheel 79176163 Dec 20 18:43 /var/crash/kernel.0

total files: 2

 

Их чем дебажить?

Share this post

Link to post
Share on other sites

smart85   

smart85
Posted · Report post

:) нуу вам ничем. В jtac отдать если есть саппорт.

Саппорта нет. Получается, что придется апдейтиться на 13.3R9 с ...software add no-validate, но взлетит ли после обновления...

Share this post

Link to post
Share on other sites

hsvt   

hsvt
Posted · Report post

А на сколько это может быть критично ?

 

show chassis alarms
1 alarms currently active
Alarm time               Class  Description
2016-12-06 01:39:15 GMT-3 Major Host 1 ECC single bit parity error

 

Вылезло после перехода на 14.1R7.4 и создании redudancy.

 

https://kb.juniper.net/InfoCenter/index?page=content&id=KB21580&actp=search

 

Софт одинаковый на двух RE.

Share this post

Link to post
Share on other sites

Davion   

Davion
Posted · Report post

Коллеги подскажите пожалуйста в логи при поднятие bgp сессий вываливаются

Jul 19 02:06:04 mx480 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 493811958. States to be processed - 84942

Jul 19 02:06:04 mx480 rpd[1786]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available

Jul 19 02:06:04 mx480 rpd[1786]: bgp_listen_accept: Connection attempt from unconfigured neighbor: xxxxx::1+54456

Jul 19 02:06:04 mx480 rpd[1786]: bgp_listen_accept:4587: NOTIFICATION sent to xxxx::1+54456 (proto): code 6 (Cease) subcode 5 (Connection Rejected), Reason: Connection attempt from unconfigured neighbor: xxxx::1+54456

Jul 19 02:06:23 mx480 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Jul 19 02:06:23 mx480 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8307957760) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Jul 19 02:06:23 mx480 /kernel: rt_pfe_veto: Possible slowest client is xdpc2. States processed - 494101874. States to be processed - 60819

Jul 19 02:06:23 mx480 /kernel: rt_pfe_veto: Possible second slowest client is xdpc0. States processed - 494101875. States to be processed - 60818

Jul 19 02:06:27 mx480 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Jul 19 02:06:27 mx480 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8307957760) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Jul 19 02:06:27 mx480 /kernel: rt_pfe_veto: Possible slowest client is xdpc1. States processed - 494227376. States to be processed - 85

Jul 19 02:06:27 mx480 /kernel: rt_pfe_veto: Possible second slowest client is xdpc2. States processed - 494227376. States to be processed - 85

Jul 19 02:06:32 mx480 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Jul 19 02:06:32 mx480 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8307957760) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

Jul 19 02:06:32 mx480 /kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 494308069. States to be processed - 700

Jul 19 02:06:37 mx480 /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2

Jul 19 02:06:37 mx480 /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8307957760) Current delayed unref = (40000) Max delayed unref on this platform = (40000) curproc = rpd

 

 

Model: mx480

Junos: 13.3R9.13

Share this post

Link to post
Share on other sites

orlik   

orlik
Posted · Report post

Коллеги подскажите пожалуйста в логи при поднятие bgp сессий вываливаются

Ну в принципе ничего страшного, просто маршруты массово на карту добавляются, из-за того что происходит медленно система об этом рапортует

Share this post

Link to post
Share on other sites

Davion   

Davion
Posted · Report post

Коллеги подскажите пожалуйста в логи при поднятие bgp сессий вываливаются

Ну в принципе ничего страшного, просто маршруты массово на карту добавляются, из-за того что происходит медленно система об этом рапортует

Спасибо, примерно такое объяснение и нашел на форумах джунипера)

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Followers 0
Go to topic listing Активное оборудование Ethernet, IP, MPLS, SDN/NFV...