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

Juniper MX80 дёрнул порты

Добрый день.

 

Кто-нибудь может что-то посоветовать.

 

Стоял, работал Juniper MX80 как бордер, потом взял и дёрнул порты (и физические и логические), т.е. сам сделал выкл/вкл:

 

И больше в логах как-то ничего и нет

 

show log interface-logs:

May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> lc-0/0/0.32769 index 2684275400 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> lc-0/0/0 index 134 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> pfh-0/0/0.16383 index 2684275400 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> pfh-0/0/0 index 135 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> pfe-0/0/0.16383 index 2684275400 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> pfe-0/0/0 index 136 <Broadcast Multicast>
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> xe-0/0/0.0 index 2684275400 <Broadcast Multicast> address #0 8.81.f4.83.57.f0
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> xe-0/0/0 index 137 <Broadcast Multicast> address #0 8.81.f4.83.57.f0
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/0.0 index 2684275400 <Broadcast Multicast> address #0 8.81.f4.83.58.50
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/0 index 141 <Broadcast Multicast> address #0 8.81.f4.83.58.50
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.32767 index 2684275400 <Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.978 index 2684275400 <Broadcast Multicast> address #0 3.d2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.946 index 2684275400 <Broadcast Multicast> address #0 3.b2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.902 index 2684275400 <Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.854 index 2684275400 <Broadcast Multicast> address #0 3.56.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1 index 142 <Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.32767 index 2684275400 <Broadcast Multicast> address #0 8.81.f4.83.58.57
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.978 index 2684275400 <Broadcast Multicast> address #0 3.d2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.854 index 2684275400 <Broadcast Multicast> address #0 3.56.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7 index 148 <Broadcast Multicast> address #0 8.81.f4.83.58.57
May  6 15:41:39  rt1-jmx80 rpd[1405]: EVENT <UpDown> ae0 index 128 <Broadcast Multicast> address #0 8.81.f4.83.58.b0
May  6 15:42:41  rt1-jmx80 rpd[1405]: EVENT <UpDown> em0.0 index 2684275400 <Broadcast Multicast> address #0 2.0.0.0.0.4


May  6 15:42:44  rt1-jmx80 rpd[1405]: EVENT <UpDown> em0.0 index 2684275400 <Up Broadcast Multicast> address #0 2.0.0.0.0.4
May  6 15:44:54  rt1-jmx80 rpd[1405]: EVENT <UpDown> xe-0/0/0.0 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.57.f0
May  6 15:44:54  rt1-jmx80 rpd[1405]: EVENT <UpDown> xe-0/0/0 index 170 <Up Broadcast Multicast> address #0 8.81.f4.83.57.f0
May  6 15:45:07  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/0.0 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.50
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/0 index 174 <Up Broadcast Multicast> address #0 8.81.f4.83.58.50
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.978 index 2684275400 <Up Broadcast Multicast> address #0 3.d2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.946 index 2684275400 <Up Broadcast Multicast> address #0 3.b2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.32767 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.854 index 2684275400 <Up Broadcast Multicast> address #0 3.56.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1.902 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/1 index 175 <Up Broadcast Multicast> address #0 8.81.f4.83.58.51
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.978 index 2684275400 <Up Broadcast Multicast> address #0 3.d2.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.854 index 2684275400 <Up Broadcast Multicast> address #0 3.56.f.ff.0.0.0.0.0.0.81.0.81.0.0.1
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7.32767 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.57
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/7 index 181 <Up Broadcast Multicast> address #0 8.81.f4.83.58.57
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/8.32767 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.58
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/8.1232 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.58
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/8 index 182 <Up Broadcast Multicast> address #0 8.81.f4.83.58.58
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/9.230 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.59
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/9.217 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.59
May  6 15:45:08  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/0/9 index 183 <Up Broadcast Multicast> address #0 8.81.f4.83.58.59
May  6 15:45:20  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/1/8.0 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.b0
May  6 15:45:20  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/1/8 index 192 <Up Broadcast Multicast> address #0 8.81.f4.83.58.b0
May  6 15:45:22  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/1/9.0 index 2684275400 <Up Broadcast Multicast> address #0 8.81.f4.83.58.b0
May  6 15:45:22  rt1-jmx80 rpd[1405]: EVENT <UpDown> ge-1/1/9 index 193 <Up Broadcast Multicast> address #0 8.81.f4.83.58.b0

 

show version              
 

Hostname: rt1-jmx80
Model: mx80
JUNOS Base OS boot [12.3R6.6]
JUNOS Base OS Software Suite [12.3R6.6]
JUNOS Kernel Software Suite [12.3R6.6]
JUNOS Crypto Software Suite [12.3R6.6]
JUNOS Packet Forwarding Engine Support (MX80) [12.3R6.6]
JUNOS Online Documentation [12.3R6.6]
JUNOS Routing Software Suite [12.3R6.6]

 

 

show chassis routing-engine 
 

Routing Engine status:
    Temperature                 46 degrees C / 114 degrees F
    CPU temperature             58 degrees C / 136 degrees F
    DRAM                      2048 MB (2048 MB installed)
    Memory utilization          95 percent
    CPU utilization:
      User                       1 percent
      Background                 0 percent
      Kernel                     7 percent
      Interrupt                  1 percent
      Idle                      91 percent
    Model                          RE-MX80
    Serial ID                      S/N ----
    Start time                     2019-05-10 13:46:47 Europe_Moscow
    Uptime                         362 days, 6 hours, 40 minutes
    Last reboot reason             Router rebooted after a normal shutdown.
    Load averages:                 1 minute   5 minute  15 minute
                                       0.13       0.12       0.12


show route summary 

Autonomous system number: ASN
Router ID: 10.10.10.100

inet.0: 817485 destinations, 2435614 routes (817480 active, 3 holddown, 2 hidden)
              Direct:     11 routes,     11 active
               Local:     12 routes,     12 active
                OSPF:    846 routes,    843 active
                 BGP: 2434736 routes, 816605 active
              Static:      1 routes,      1 active
           Aggregate:      6 routes,      6 active
                 PIM:      2 routes,      2 active

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
                 PIM:      2 routes,      2 active

inet6.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
           Multicast:      1 routes,      1 active

 

Share this post


Link to post
Share on other sites

Походу обновляться надо с 12-ой

 

# show nvram

MPC: Reset reason (0x80): Software initiated CPU reset
[LOG] -----------------------------------------------------
      PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC
      (caller pc: 0x412777c8)
 

Share this post


Link to post
Share on other sites

12.3 до сих пор поддерживается, накати последний R12-S15 и живи дальше . 

 

4 hours ago, Urs_ak said:

MPC: Reset reason (0x80): Software initiated CPU reset
[LOG] -----------------------------------------------------
      PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC
      (caller pc: 0x412777c8)

 покажи то что было после 

Share this post


Link to post
Share on other sites
5 часов назад, orlik сказал:

покажи то что было после 

Вот:

MPC: Reset reason (0x80): Software initiated CPU reset
[LOG] -----------------------------------------------------
      PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC
      (caller pc: 0x412777c8)


System Exception: Vector/Code 0x00900, Signal -1
Event occurred at: May  6 12:41:34.279955 

Juniper Embedded Microkernel Version 12.3R6.6
Built by builder on 2014-03-13 05:05:41 UTC
Copyright (C) 1998-2014, Juniper Networks, Inc.
All rights reserved.
Reason string: "Panic"
Context: Thread (1s Medium Periodic)

Registers:
R00: 0x40041f74 R01: 0x43f17b10 R02: 0x43f15bc8 R03: 0x00000017 
R04: 0x00000000 R05: 0x43f17b18 R06: 0x00000000 R07: 0x80000000 
R08: 0x00000000 R09: 0x00000017 R10: 0x43edc718 R11: 0x42830000 
R12: 0x24002022 R13: 0xf2bdc6f7 R14: 0xa33adb75 R15: 0xdafedea3 
R16: 0x2fd6e1fe R17: 0x67e0cf98 R18: 0x0ff6fde8 R19: 0x3df4bf47 
R20: 0xff700000 R21: 0x41f358ac R22: 0x426a0000 R23: 0x426a0000 
R24: 0x426a0000 R25: 0x426a3f80 R26: 0x42ff3bf0 R27: 0x430147e8 
R28: 0x00000000 R29: 0x00000001 R30: 0x412777c8 R31: 0x42383cb8 
MSR: 0x00029200 CTR: 0x000f4220 Link: 0x40041f74 SP: 0x43f17b10
 CR: 0x24002022 XER: 0x20000000 DEAR: 0x00000000 PC: 0x40041f78
ESR: 0x00000000 K_MSR: 0x00021200

Stack Traceback:
Frame 01: sp = 0x43f17b10, pc = 0x40041f74
Frame 02: sp = 0x43f17b58, pc = 0x412777c8
Frame 03: sp = 0x43f17b60, pc = 0x4003d074
Frame 04: sp = 0x43f17b98, pc = 0x4003d220
Frame 05: sp = 0x43f17bc8, pc = 0x40030f40

[LOG] syslog called with interrupts off (caller pc:0x416db32c)
[LOG] Dumping core-TAZ-TBB-0 to 1
[LOG] syslog called with interrupts off (caller pc:0x416da208)
[LOG] Coredump finished!
[LOG] TBB: Drive Level for LU-MQ as 0x10100b09
[LOG] TBB: Post Emphasis for LU-MQ as 0xd0d0900
[LOG] Set the IP IRI for table #1 to 0x80000032
[LOG] IPV4 Init: Set the IP IRI to 0x80000032
[LOG] GN2405: JSPEC V 1.0 Module Init.
[LOG] wp_module_init : 
[LOG] ddos_issu_helper_register: issu state is 0 at ddos startup
[LOG] ddos sock support init ...
[LOG] ddos sock connection proto in use 4 ...
[LOG] RSMON rsmon_msg_thread_init 
[LOG] creating ifstats trace buffer with compile-time requested size of 1048576

MPC: Reset reason (0x80): Software initiated CPU reset

ROM NVRAM:
 0 available bytes, 0 used, 0 free

 

> show system core-dumps core-file-info /var/crash/core-TAZ-TBB-0.gz.core.0 
error: No valid core file found in "/var/crash/core-TAZ-TBB-0.gz.core.0"

Share this post


Link to post
Share on other sites
8 hours ago, Urs_ak said:

Stack Traceback:

Frame 01: sp = 0x43f17b10, pc = 0x40041f74

Frame 02: sp = 0x43f17b58, pc = 0x412777c8

Frame 03: sp = 0x43f17b60, pc = 0x4003d074

Frame 04: sp = 0x43f17b98, pc = 0x4003d220

Frame 05: sp = 0x43f17bc8, pc = 0x40030f40

 

Увы , этого мало для в данном случае. Могу только сказать что проблема связана с ppm(lacp/bfd/vrrp и т.д.) Обновитесь на 12.3R12-S15 и пусть живет дальше 

Share this post


Link to post
Share on other sites
3 часа назад, orlik сказал:

 

Увы , этого мало для в данном случае. Могу только сказать что проблема связана с ppm(lacp/bfd/vrrp и т.д.) Обновитесь на 12.3R12-S15 и пусть живет дальше 

Спасибо, обновлюсь. Есть 17-ая версия (17.3R3-S3.3)

 

ppm(lacp/bfd/vrrp и т.д.)  - кстати ничего этого не используется, а например ae0 - это статический LAG на прозрачный DPI и в Cisco с "channel-group 2 mode on"

Share this post


Link to post
Share on other sites

мы курили:

show chassis environment cb
show chassis alarms

show chassis fpc

show chassis fpc detail

show chassis fabric summary
show chassis fabric map | no-more
show chassis fabric fpc | no-more
show chassis fabric plane | no-more

 

> start shell pfe network fpcx  <<< from both 0 and 1

# show nvram

# show syslog messages

# show hsl2 statistics detail

# show cmerror module

# show cmerror module X error XXXXX <<< replace with module number and error number from above output # show hsl2 statistics

----

после курева было найдено "%PFE-6: fpc1 Error (0x701ca), module: XMCHIP(0), type: HSL2_PROTECT: Detected: Major CRC errors", "Major  FPC 1 offlined due to unreachable destinations
Major  FPC 0 offlined due to unreachable destinations
Major  FPC 1 Major Errors - XM Chip Error code: 0x701ca"

 

 

после этого Juniper поменял железо

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this