Hoi,
Wij hebben hier een geheel nieuw netwerk gebouwd 3 weken geleden en gisteren trok een collega van mij een stroom kabel eruit. (dom dom dom)..
Alle switches zijn 2960S switches met stacking modules achter in de switch.
Situatie is als volgt..
De FW is trouwens ook redundant aangesloten met EtherChannel op beide switches. (BERS001).
Gisteren hadden we een probleem met BERS001-1, deze kreeg geen power meer.
Gevolg was dat het gehele netwerk op de kop lag gedurende 30-45 seconden en alles down was.
Toen kwam BERS001-2 als master op..
Mijn idee achter deze config is dat door de stacking en de uplinks naar andere switches te verdelen over beide switches er geen downtime mag ontstaan en dat het eigenlijk in active-active moet draaien..
Maarja dit gebeurde dus niet..
Iemand een idee wat er aan de hand kan zijn?
Hier de config van de switch BERS001
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
!
hostname BERS001
!
logging buffered 32768
aaa authentication login default local
aaa authentication login CONSOLE local
!
clock summer-time CET recurring last Sun Mar 2:00 last Sun Oct 3:00
no ip gratuitous-arps
!
vtp domain vtp01
vtp mode transparent
ip subnet-zero
no ip source-route
!
ip domain-name blaat.com
!
ip name-server 8.8.8.8
ip name-server 8.8.4.4
!
!
spanning-tree mode rapid-pvst
spanning-tree vlan 1-4094 pri 8192
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
vlan 100
name Server
!
vlan 107
name Client
!
interface range GigabitEthernet 1/0/1 - 23
switchport mode access
switchport access vlan 107
spanning-tree portfast
!
interface range GigabitEthernet 2/0/1 - 23
switchport mode access
switchport access vlan 107
spanning-tree portfast
!
interface GigabitEthernet 1/0/24
des BERS002 port 1/0/48
channel-group 2 mode active
!
interface GigabitEthernet 2/0/24
des BERS002 port 2/0/48
channel-group 2 mode active
!
interface GigabitEthernet 1/0/25
des BERS003 port 1/0/49
channel-group 3 mode active
udld port aggressive
!
interface GigabitEthernet 2/0/25
des BERS003 port 2/0/49
channel-group 3 mode active
udld port aggressive
!
interface GigabitEthernet 1/0/26
des BERS004 port 1/0/49
channel-group 4 mode active
udld port aggressive
!
interface GigabitEthernet 2/0/26
des BERS004 port 2/0/25
channel-group 4 mode active
udld port aggressive
!
interface Po 2
description Uplink To BERS002
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface Po 3
description Uplink To BERS003
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface Po 4
description Uplink To BERS004
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface vlan 100
ip address 172.16.100.91 255.255.255.0
!
Hier een deel van de log wat er gebeurde nadat BERS001-1 uitviel.
Nov 27 14:20:11.076: %STACKMGR-4-SWITCH_REMOVED: Switch 1 has been REMOVED from the stack
Nov 27 14:20:11.081: license_init_config_queue: initializing the license_switch_boot_config_q
Nov 27 14:20:11.087: %STACKMGR-4-MASTER_ELECTED: Switch 2 has been elected as MASTER of the stack
Nov 27 14:20:11.448: %CFGMGR-6-APPLYING_RUNNING_CFG: as new master
Nov 27 14:20:11.543: %SSH-5-ENABLED: SSH 1.99 has been enabled
Nov 27 14:20:13.158: %LINK-3-UPDOWN: Interface Port-channel2, changed state to up
Nov 27 14:20:13.262: %LINK-3-UPDOWN: Interface Port-channel3, changed state to up
Nov 27 14:20:13.283: %LINK-3-UPDOWN: Interface Port-channel4, changed state to up
Nov 27 14:20:13.283: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Nov 27 14:20:13.294: %LINK-3-UPDOWN: Interface Port-channel6, changed state to up
Nov 27 14:20:13.383: %LINK-3-UPDOWN: Interface Vlan1, changed state to up
Nov 27 14:20:13.383: %LINK-3-UPDOWN: Interface Vlan100, changed state to up
Nov 27 14:20:13.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Nov 27 14:20:13.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan100, changed state to up
Nov 27 14:20:14.164: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to up
Nov 27 14:20:14.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel3, changed state to up
Nov 27 14:20:14.290: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to up
Nov 27 14:20:14.290: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Nov 27 14:20:14.306: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel6, changed state to up
Nov 27 14:20:16.571: %PKI-4-NOAUTOSAVE: Configuration was modified. Issue "write memory" to save new certificate
Nov 27 14:20:16.655: %STACKMGR-5-MASTER_READY: Master Switch 2 is READY
Nov 27 14:20:16.974: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Nov 27 14:20:17.756: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to down
Nov 27 14:20:17.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel3, changed state to down
Nov 27 14:20:17.792: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
Nov 27 14:20:17.908: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Nov 27 14:20:17.934: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel6, changed state to down
Nov 27 14:20:18.746: %LINK-5-CHANGED: Interface GigabitEthernet2/0/24, changed state to administratively down
Nov 27 14:20:18.762: %LINK-3-UPDOWN: Interface Port-channel2, changed state to down
Nov 27 14:20:18.767: %LINK-5-CHANGED: Interface GigabitEthernet2/0/25, changed state to administratively down
Nov 27 14:20:18.783: %LINK-3-UPDOWN: Interface Port-channel3, changed state to down
Nov 27 14:20:18.783: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down
Nov 27 14:20:18.804: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
Nov 27 14:20:18.888: %LINK-5-CHANGED: Interface GigabitEthernet2/0/17, changed state to administratively down
Nov 27 14:20:18.899: %LINK-5-CHANGED: Interface GigabitEthernet2/0/18, changed state to administratively down
Nov 27 14:20:18.914: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Nov 27 14:20:18.919: %LINK-5-CHANGED: Interface GigabitEthernet2/0/19, changed state to administratively down
Nov 27 14:20:18.930: %LINK-5-CHANGED: Interface GigabitEthernet2/0/20, changed state to administratively down
Nov 27 14:20:18.946: %LINK-3-UPDOWN: Interface Port-channel6, changed state to down
Nov 27 14:20:19.748: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/24, changed state to down
Nov 27 14:20:19.769: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/25, changed state to down
Nov 27 14:20:19.785: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/26, changed state to down
Iemand een idee waarom ineens alle poorten op switch2 down gingen (en daarna weer up?)
Wij hebben hier een geheel nieuw netwerk gebouwd 3 weken geleden en gisteren trok een collega van mij een stroom kabel eruit. (dom dom dom)..
Alle switches zijn 2960S switches met stacking modules achter in de switch.
Situatie is als volgt..
De FW is trouwens ook redundant aangesloten met EtherChannel op beide switches. (BERS001).
Gisteren hadden we een probleem met BERS001-1, deze kreeg geen power meer.
Gevolg was dat het gehele netwerk op de kop lag gedurende 30-45 seconden en alles down was.
Toen kwam BERS001-2 als master op..
Mijn idee achter deze config is dat door de stacking en de uplinks naar andere switches te verdelen over beide switches er geen downtime mag ontstaan en dat het eigenlijk in active-active moet draaien..
Maarja dit gebeurde dus niet..
Iemand een idee wat er aan de hand kan zijn?
Hier de config van de switch BERS001
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
!
hostname BERS001
!
logging buffered 32768
aaa authentication login default local
aaa authentication login CONSOLE local
!
clock summer-time CET recurring last Sun Mar 2:00 last Sun Oct 3:00
no ip gratuitous-arps
!
vtp domain vtp01
vtp mode transparent
ip subnet-zero
no ip source-route
!
ip domain-name blaat.com
!
ip name-server 8.8.8.8
ip name-server 8.8.4.4
!
!
spanning-tree mode rapid-pvst
spanning-tree vlan 1-4094 pri 8192
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
vlan 100
name Server
!
vlan 107
name Client
!
interface range GigabitEthernet 1/0/1 - 23
switchport mode access
switchport access vlan 107
spanning-tree portfast
!
interface range GigabitEthernet 2/0/1 - 23
switchport mode access
switchport access vlan 107
spanning-tree portfast
!
interface GigabitEthernet 1/0/24
des BERS002 port 1/0/48
channel-group 2 mode active
!
interface GigabitEthernet 2/0/24
des BERS002 port 2/0/48
channel-group 2 mode active
!
interface GigabitEthernet 1/0/25
des BERS003 port 1/0/49
channel-group 3 mode active
udld port aggressive
!
interface GigabitEthernet 2/0/25
des BERS003 port 2/0/49
channel-group 3 mode active
udld port aggressive
!
interface GigabitEthernet 1/0/26
des BERS004 port 1/0/49
channel-group 4 mode active
udld port aggressive
!
interface GigabitEthernet 2/0/26
des BERS004 port 2/0/25
channel-group 4 mode active
udld port aggressive
!
interface Po 2
description Uplink To BERS002
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface Po 3
description Uplink To BERS003
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface Po 4
description Uplink To BERS004
switchport trunk native vlan 999
switchport mode trunk
switchport nonegotiate
storm-control broadcast level 4.00 2.00
port-channel load-balance src-dst-ip
!
interface vlan 100
ip address 172.16.100.91 255.255.255.0
!
Hier een deel van de log wat er gebeurde nadat BERS001-1 uitviel.
Nov 27 14:20:11.076: %STACKMGR-4-SWITCH_REMOVED: Switch 1 has been REMOVED from the stack
Nov 27 14:20:11.081: license_init_config_queue: initializing the license_switch_boot_config_q
Nov 27 14:20:11.087: %STACKMGR-4-MASTER_ELECTED: Switch 2 has been elected as MASTER of the stack
Nov 27 14:20:11.448: %CFGMGR-6-APPLYING_RUNNING_CFG: as new master
Nov 27 14:20:11.543: %SSH-5-ENABLED: SSH 1.99 has been enabled
Nov 27 14:20:13.158: %LINK-3-UPDOWN: Interface Port-channel2, changed state to up
Nov 27 14:20:13.262: %LINK-3-UPDOWN: Interface Port-channel3, changed state to up
Nov 27 14:20:13.283: %LINK-3-UPDOWN: Interface Port-channel4, changed state to up
Nov 27 14:20:13.283: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Nov 27 14:20:13.294: %LINK-3-UPDOWN: Interface Port-channel6, changed state to up
Nov 27 14:20:13.383: %LINK-3-UPDOWN: Interface Vlan1, changed state to up
Nov 27 14:20:13.383: %LINK-3-UPDOWN: Interface Vlan100, changed state to up
Nov 27 14:20:13.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Nov 27 14:20:13.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan100, changed state to up
Nov 27 14:20:14.164: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to up
Nov 27 14:20:14.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel3, changed state to up
Nov 27 14:20:14.290: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to up
Nov 27 14:20:14.290: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Nov 27 14:20:14.306: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel6, changed state to up
Nov 27 14:20:16.571: %PKI-4-NOAUTOSAVE: Configuration was modified. Issue "write memory" to save new certificate
Nov 27 14:20:16.655: %STACKMGR-5-MASTER_READY: Master Switch 2 is READY
Nov 27 14:20:16.974: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Nov 27 14:20:17.756: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed state to down
Nov 27 14:20:17.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel3, changed state to down
Nov 27 14:20:17.792: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel4, changed state to down
Nov 27 14:20:17.908: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Nov 27 14:20:17.934: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel6, changed state to down
Nov 27 14:20:18.746: %LINK-5-CHANGED: Interface GigabitEthernet2/0/24, changed state to administratively down
Nov 27 14:20:18.762: %LINK-3-UPDOWN: Interface Port-channel2, changed state to down
Nov 27 14:20:18.767: %LINK-5-CHANGED: Interface GigabitEthernet2/0/25, changed state to administratively down
Nov 27 14:20:18.783: %LINK-3-UPDOWN: Interface Port-channel3, changed state to down
Nov 27 14:20:18.783: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down
Nov 27 14:20:18.804: %LINK-3-UPDOWN: Interface Port-channel4, changed state to down
Nov 27 14:20:18.888: %LINK-5-CHANGED: Interface GigabitEthernet2/0/17, changed state to administratively down
Nov 27 14:20:18.899: %LINK-5-CHANGED: Interface GigabitEthernet2/0/18, changed state to administratively down
Nov 27 14:20:18.914: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Nov 27 14:20:18.919: %LINK-5-CHANGED: Interface GigabitEthernet2/0/19, changed state to administratively down
Nov 27 14:20:18.930: %LINK-5-CHANGED: Interface GigabitEthernet2/0/20, changed state to administratively down
Nov 27 14:20:18.946: %LINK-3-UPDOWN: Interface Port-channel6, changed state to down
Nov 27 14:20:19.748: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/24, changed state to down
Nov 27 14:20:19.769: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/25, changed state to down
Nov 27 14:20:19.785: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/26, changed state to down
Iemand een idee waarom ineens alle poorten op switch2 down gingen (en daarna weer up?)