Tom Hollingsworth shares his frustration at non-support of third-party interface modules (SFPs, as Tom calls them). If you try to use a non-vendor device, the switch will spit out an error and refuse to support it.
Why do vendors do this? Some claim it’s vendor lock in. You are stuck ordering your modules from the vendor at an inflated cost instead of buying them from a different source. Others claim it’s to help TAC troubleshoot the switch better in case of a failure. Still others say that it’s because the manufacturing tolerances on the vendor SFPs is much better than the third party offerings, even from the same OEM. I don’t have the answer, but I can tell you that Cisco, HP, Dell, and many others do this all the time.
Tom goes on to present a simple workaround, using undocumented Cisco commands, to force the switch to use these devices anyway. Read the whole thing at The Networking Nerd.
- The Cloud Extends Into the Datacenter: Druva at AWS re:Invent - December 13, 2019
- Docker Enterprise Sold to Mirantis, Docker Desktop, Hub Raise $35MM - November 19, 2019
- Juniper NXTWORK 2019 Keynote Live Blog - November 12, 2019
- Where Did Tech Field Day Come From? Tech Field Day at 10 - November 4, 2019
- Druva Protects Corporate Data Outside the Firewall - October 30, 2019
- It’s All About the Delegates: Tech Field Day at 10 - October 27, 2019
- Nth Generation Symposium Keynote Live Blog - October 24, 2019
- SolarWinds Aims to Connect the Data Dots - October 24, 2019
- Celebrating 10 Years of Pure Storage and Tech Field Day - October 23, 2019
- Meeting the Storage Performance Requirements of AI and ML Workloads with WekaIO - October 23, 2019