We recently ran into a issue where LACP on a server link took down one of our switches (let's say switch 1) with LACP packets flooded to the SUP. This also caused a "UDLD empty echo" error on switch 2 in the VPC domain because switch 1 stopped echoing UDLD. This of course, killed the VPC peer-link. What we ended up finding out is that we didn't apply the new copp policy to the new code so the l2 copp profile was not in the configuration (coming from code version 5.0.3, we are currently on 5.2(3a) ). Having looked back at the copp l2 policy, it doesn't do anything but allow the flood to continue:
class-map type control-plane copp-system-class-l2-unpoliced
match access-group name copp-system-acl-mac-lacp
mac access-list copp-system-acl-mac-lacp
permit any 0180.c200.0002 0000.0000.0000 0x8809
police cir 8 gbps bc 5 mbytes conform transmit violate transmit (how does this help at all?)
We are trying to keep this from happening again. I was wondering if any of you have suggestions on whether we should go with storm control or if there something out there with copp configurations that can be applied to keep this from happening. Of course, at this point, applying storm control to all of the data center switches will be a tedious task but maybe that's the best solution? Any help is greatly appreciated!
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...
RBAC users like firstname.lastname@example.org may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...