Руководство По Устранению Ошибки для Cisco Cisco Nexus 5010 Switch
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
input rate 2.83 Mbps, 4.74 Kpps; output rate 3.54 Gbps, 290.64 Kpps
30 seconds input rate 7036025712 bits/sec, 577854 packets/sec
30 seconds output rate 5627216 bits/sec, 9498 packets/sec
input rate 3.54 Gbps
, 290.64 Kpps; output rate 2.83 Mbps, 4.75 Kpps
The traffic interruption, as before, is only short lived.
Under above mentioned testing conditions 50-80 packets were lost from a single session.
Remove "feature vpc" command also caused vPC configuration o be removed from port-channels.
This configuration needs to be readded.
Conclusion
vPC feature is intended to bring resiliency performance by splitting data traffic in a port channel
among multiple devices.
among multiple devices.
This simple idea requires complicated control plane implementations.
The above tests were meant to show disruptions to both the control- and data-plane which may
occur during life cycle of the feature.
occur during life cycle of the feature.
As expected data plane disruptions were detected and corrected almost immediately - with single
packets lost in tests.
packets lost in tests.
The control plane disruptions tested show that vPC still maintains sub-second convergence time
even when control plane is affected.
even when control plane is affected.
The most disruptive test performed - vPC peer link being shut down - potentially combines both
data and control plane failure. Still a fast convergence time was demonstrated.
data and control plane failure. Still a fast convergence time was demonstrated.