3 ms·
We have very competent network engineers, but it never hurts to have a second opinion. Verifying that there are no subtle interactions that we've missed is simp
by imbriaco 12y ago
We have very competent network engineers, but it never hurts to have a second opinion. Verifying that there are no subtle interactions that we've missed is simply prudent.
At our scale, partnering with our vendors is a necessity. We often operate in areas that, while they are technically within specification, are toward the higher end of the range.
- jwatte 12y agoWhich vendor? I have experience with two brands in similar condos, one good, one not so much...
- imbriaco 12y agoI prefer not to publicly name the vendor. This is about problems on our network, and it's ultimately our responsibility.
- insaneirish 12y agoI urge you to seriously reconsider your design. VPC/MLAG/etc. are attractive because of the ease of making any VLAN available anywhere without the traditional spanning tree nightmare of doing so. However, you're trading one nightmare for another. Your core or aggregation switches are now stateful, and you've just experienced the results of stateful network components not failing cleanly. I'm not saying an overlay (e.g. VMware NSX née Nicira) is the solution either. I'd suggest rethinking why you need any VLAN anywhere, which is likely the reason for VPC/MLAG. If I'm wrong and you don't put the same VLAN in multiple cabinets, then rip VPC/MLAG out immediately and switch to a pure L3 design. It is so much simpler and consistent with industry best practices.