Решено стек cisco 3850

Engineer

Engineer

Активный участник
Доброго времени суток, коллеги! Выручайте, что то происходит с сеткой не могу понять в чем дело. Часть серверов доступна а часть нет, даже пинг не проходит. Есть несколько сетей пользовательских
172.17.11x.0/24, x от 1 до 6. Люди физически воткнуты в коммутаторы cisco catalyst 2960G, аплинки от каждого свитча идут в своеобразное ядро состоящее из стека cisco catalyst 3850. Как раз на этот стек пока падают все подозрения. Подскажите как проверить что cisco стек живой?
 
Давайте
Код: 
Show log

и так же
Код: 
show switch
 
Код: 
Oct 14 21:28:59.847 Moscow: %SSH-5-ENABLED: SSH 2.0 has been enabled
Oct 17 15:59:47.961 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1539781187.962778. --> Now:1539781187.960973.
Oct 17 17:12:59.437 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1539785579.437210. --> Now:1539785579.436981.
Oct 19 20:11:42.383 Moscow: %IOSXE-3-PLATFORM: STANDBY:2 process kernel: ERROR L                                                                   2C_TADX_INT(0)[L2DSBE]: Data Single-Bit Error
Oct 19 20:11:42.383 Moscow: %IOSXE-3-PLATFORM: STANDBY:2 process kernel: ERROR C                                                                   VMX_L2C_ERR_TDT: 0x48600000000f2af2
Oct 22 13:12:20.188 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1540203140.188297. --> Now:1540203140.187985.
Oct 27 22:21:49.440 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1540668109.440115. --> Now:1540668109.439973.
Nov  3 02:52:50.918 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1541202770.918442. --> Now:1541202770.917952.
Nov  3 17:05:50.931 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1541253950.935922. --> Now:1541253950.930952.
Nov 10 02:23:36.228 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detec                                                                   ted backward time shift. Last: 1541805816.229392. --> Now:1541805816.228042.
Nov 15 20:09:52.117 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1542301792.118305. --> Now:1542301792.116984.
Nov 18 02:43:01.011 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1542498181.11262. --> Now:1542498181.10986.
Nov 19 07:48:52.408 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1542602932.409090. --> Now:1542602932.407970.
Nov 19 16:16:05.770 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1542633365.770349. --> Now:1542633365.769986.
Nov 24 00:10:23.876 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1543007423.877426. --> Now:1543007423.875974.
Dec  1 17:38:54.637 Moscow: *%OSAPI-4-TIME_SHIFT_DETECTED: STANDBY:2 wcm:  Detected backward time shift. Last: 1543675134.639504. --> Now:1543675134.636989.
Dec  6 16:45:19.692 Moscow: %STACKMGR-6-SWITCH_REMOVED: STANDBY:2 stack-mgr:  Switch 1 has been removed from the stack.
Dec  6 16:45:21.256 Moscow: %PLATFORM_STACKPOWER-6-CABLE_EVENT: Switch 2 stack power cable 2 inserted
Dec  6 16:45:21.256 Moscow: %PLATFORM_STACKPOWER-6-LINK_EVENT: Switch 2 stack power protocol is up on cable 2
Dec  6 16:45:23.148 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/6, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/12, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/14, changed state to down
Dec  6 16:45:23.149 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/15, changed state to down
Dec  6 16:45:23.155 Moscow: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 172.30.0.189 port 514 started - CLI initiated
Dec  6 16:45:23.156 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/16, changed state to down
Dec  6 16:45:23.156 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down
Dec  6 16:45:23.156 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/21, changed state to down
Dec  6 16:45:23.157 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/22, changed state to down
Dec  6 16:45:23.157 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to down
Dec  6 16:45:23.162 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to down
Dec  6 16:45:23.162 Moscow: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/3, changed state to down
Dec  6 16:45:23.162 Moscow: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/4, changed state to down
Dec  6 16:45:23.424 Moscow: %LINK-3-UPDOWN: Interface Null0, changed state to up
Dec  6 16:45:23.425 Moscow: %LINK-3-UPDOWN: Interface Vlan300, changed state to up
Dec  6 16:45:23.425 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/13, changed state to up
Dec  6 16:45:23.426 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to up
Dec  6 16:45:23.427 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to up
Dec  6 16:45:23.427 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/16, changed state to up
Dec  6 16:45:23.428 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/20, changed state to up
Dec  6 16:45:23.429 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/21, changed state to up
Dec  6 16:45:23.430 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/22, changed state to up
Dec  6 16:45:23.431 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/23, changed state to up
Dec  6 16:45:23.432 Moscow: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/24, changed state to up
Dec  6 16:45:23.433 Moscow: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/1/3, changed state to up
Dec  6 16:45:23.434 Moscow: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/1/4, changed state to up
Dec  6 16:45:23.435 Moscow: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
Dec  6 16:45:23.435 Moscow: %LINK-3-UPDOWN: Interface Port-channel10, changed state to up
Dec  6 16:45:23.436 Moscow: %LINK-3-UPDOWN: Interface Port-channel11, changed state to up
Dec  6 16:45:23.436 Moscow: %LINK-3-UPDOWN: Interface Port-channel20, changed state to up
Dec  6 16:45:23.436 Moscow: %LINK-3-UPDOWN: Interface Port-channel30, changed state to up
Dec  6 16:45:23.492 Moscow: %LINK-5-CHANGED: Interface Vlan1, changed state to administratively down
Dec  6 16:45:24.425 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state to up
Dec  6 16:45:24.425 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan300, changed state to up
Dec  6 16:45:24.426 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/13, changed state to up
Dec  6 16:45:24.426 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to up
Dec  6 16:45:24.427 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to up
Dec  6 16:45:24.427 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/16, changed state to up
Dec  6 16:45:24.427 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/20, changed state to up
Dec  6 16:45:24.427 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/21, changed state to up
Dec  6 16:45:24.428 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/22, changed state to up
Dec  6 16:45:24.428 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/23, changed state to up
Dec  6 16:45:24.428 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/24, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/1/3, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/1/4, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel10, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel11, changed state to up
Dec  6 16:45:24.436 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel20, changed state to up
Dec  6 16:45:24.437 Moscow: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel30, changed state to up
CORE_2_3850#
 
Ага. А дайте вывод команд пожалуйста
Код: 
[B]dir crashinfo-1:[/B]
и
Код: 
[B]dir crashinfo-2:[/B]
 
Еще в логах вот такая подозрительная строка
Код: 
Switch/Stack Mac Address : 80e8.6f62.a680 - Foreign Mac Address Mac persistency wait time: Indefinite
 
Oct 19 20:11:42.383 Moscow: %IOSXE-3-PLATFORM: STANDBY:2 process kernel: ERROR L2C_TADX_INT(0)[L2DSBE]: Data Single-Bit Error
Oct 19 20:11:42.383 Moscow: %IOSXE-3-PLATFORM: STANDBY:2 process kernel: ERROR CVMX_L2C_ERR_TDT: 0x48600000000f2af2
Нажмите, чтобы раскрыть...
какая то ошибка в ядре ios. Или ошибка памяти. Если вы видите это 1 раз то можно забить болт. Если это повторяется регулярно то похоже на аппаратную проблему и отказ оборудования
 
помогла перезагрузка. Но все таки хочется докопаться до причины падения.
Сейчас:
Код: 
#sh swit
Switch/Stack Mac Address : 80e8.6f62.a680 - Local Mac Address
Mac persistency wait time: Indefinite
                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
------------------------------------------------------------
*1       Active   80e8.6f62.a680     10     V05     Ready
 2       Standby  80e8.6f13.1c80     1      V05     Ready
 
Что с прошивкой и версией ios? Попробуйте обновить прошивку в cisco
 
Для ответа нужно войти/зарегистрироваться
Назад
Верх