版权声明：本博客为博主原创博文，可以任意转载。转载请附上博客链接： http://blog.csdn.net/qiqishuang https://blog.csdn.net/qiqishuang/article/details/51542087
现象：node3节点挂了，从node4 ssh上去 ping不通网关192.168.19.254。
解决办法：现在通过串口minicom登录交换机，利用内置的安全保护机制阻止网络风暴。
1. 先查看网桥是否正确连接
node3：$ ovs-vsctl show：- br-in
- br-out
2. minicom登录交换机并enable
Switch#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 63 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 63 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 66 message lines logged
Logging Source-Interface: VRF Name:
Log Buffer (4096 bytes):
hanged state to up
Mar 30 01:28:15.449: %LINK-3-UPDOWN: Interface GigabitEthernet0/10, changed stap
Mar 30 01:28:15.449: %LINK-3-UPDOWN: Interface GigabitEthernet0/12, changed stap
Mar 30 01:28:15.486: %LINK-3-UPDOWN: Interface GigabitEthernet0/14, changed stap
Mar 30 01:28:15.486: %LINK-3-UPDOWN: Interface GigabitEthernet0/15, changed stap
Mar 30 01:28:15.544: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed stap
Mar 30 01:28:15.565: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed statp
Mar 30 01:28:15.570: %LINK-3-UPDOWN: Interface GigabitEthernet0/6, changed statp
Mar 30 01:28:15.607: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed stap
Mar 30 01:28:15.607: %LINK-3-UPDOWN: Interface GigabitEthernet0/16, changed stap
Mar 30 01:28:15.643: %LINK-3-UPDOWN: Interface GigabitEthernet0/9, changed statp
Mar 30 01:28:15.643: %LINK-3-UPDOWN: Interface GigabitEthernet0/24, changed stap
Mar 30 01:28:15.816: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthn
Mar 30 01:28:16.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.482: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed stap
Mar 30 01:28:16.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.545: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.566: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.608: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.608: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.645: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.645: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:16.723: %LINK-3-UPDOWN: Interface GigabitEthernet0/17, changed stap
Mar 30 01:28:16.723: %LINK-3-UPDOWN: Interface GigabitEthernet0/18, changed stap
Mar 30 01:28:16.765: %LINK-3-UPDOWN: Interface GigabitEthernet0/20, changed stap
Mar 30 01:28:17.484: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:17.725: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:17.725: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:17.767: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:21.772: %PKI-6-AUTOSAVE: Running configuration saved to NVRAM
Mar 30 01:28:24.986: %LINK-3-UPDOWN: Interface GigabitEthernet0/7, changed statp
Mar 30 01:28:25.988: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:37.218: %LINK-3-UPDOWN: Interface GigabitEthernet0/22, changed stap
Mar 30 01:28:38.219: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthp
Mar 30 01:28:42.193: %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation.
Mar 30 02:18:10.717: %ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on Gigab.
Mar 30 02:18:10.717: %PM-4-ERR_DISABLE: loopback error detected on Gi0/19, putte
Mar 30 02:18:11.724: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthn
Mar 30 02:18:12.730: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed stan
Switch#
Switch#
Switch#
Switch#configure
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#errdisable recovery cause loopback
Switch(config)#eixt
^
% Invalid input detected at '^' marker.
Switch(config)#show errdisable recovery
^
% Invalid input detected at '^' marker.
Switch(config)#show errdisable recovery
^
% Invalid input detected at '^' marker.
Switch(config)#exit
Switch#
Mar 30 02:59:05.434: %SYS-5-CONFIG_I: Configured from console by consoleshow
% Type "show ?" for a list of subcommands
Switch#
Switch#show errdisable recovery
ErrDisable Reason Timer Status
----------------- --------------
bpduguard Disabled
channel-misconfig (STP) Disabled
dhcp-rate-limit Disabled
dtp-flap Disabled
gbic-invalid Disabled
inline-power Disabled
link-flap Disabled
mac-limit Disabled
loopback Enabled
pagp-flap Disabled
port-mode-failure Disabled
pppoe-ia-rate-limit Disabled
psecure-violation Disabled
security-violation Disabled
sfp-config-mismatch Disabled
small-frame Disabled
storm-control Disabled
udld Disabled
vmps Disabled
psp Disabled
Timer interval: 300 seconds
Interfaces that will be enabled at the next timeout:
Interface Errdisable reason Time left(sec)
--------- ----------------- --------------
Gi0/19 loopback 264
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#show errdisable recovery