Hello guys,
We are running in a bit of an argument with our server team.
We are trying to standarize the configuration of adding servers to the network. This in many ways but mainly on Cisco Nexus switches for the data center. A alot of the servers are also added into a vPC configuration to allow active/active forwarding.
Now the problem is that according to the server team sometimes problems arise. The server team will blame it as always on the network end it of. Most of the time in regards to LACP blocking a port.
interface port-channel100 description DHR005DL101-lag0 - 2*10G - vPC channel switchport mode trunk switchport trunk native vlan 999 switchport trunk allowed vlan 203-204,207,312,330-333 spanning-tree port type edge trunk spanning-tree bpduguard disable spanning-tree guard root spanning-tree bpdufilter disable logging event port link-status logging event port trunk-status storm-control broadcast level 80.00 storm-control multicast level 80.00 lacp mode delay vpc 1121
My standard way has always been to configure an etherchannel with LACP towards a server, certaintly with a vPC setup. I see no reason why not to do this.
They are saying that ports can also be configured with port-channels without LACP. Just use a static port-channel.
However i have found at this time no exact configuration tips for this on Vmware side. I would like to find a document that describes what the pro's and con's are of such a setup. How would the server prohibit a tx/rx misfire that could result in a loop?
On Cisco end i assume a simple port-channel with mode on and bpdu guard would do it i assume.
No comments:
Post a Comment