Why do some SFPs work in one switch but not another?

SFP vendor locking is when switches only accept modules with matching vendor identification codes stored in the module's EEPROM.

How Vendor Locking Works

• Every SFP has EEPROM with vendor info per SFF-8472
• Switch reads vendor name, part number, serial
• Some switches whitelist only approved codes
• Rejects modules from unknown vendors

Common Vendors That Lock

• Cisco (strong lock, needs "compatible" coded SFPs)
• HP/Aruba (medium lock)
• Juniper (medium lock)
• Extreme (medium lock)
• Most industrial switch vendors are more open

Solutions

1. Buy Vendor-Coded Modules

• Third-party companies sell modules pre-coded for target switch
• 60-80% cheaper than OEM
• Same optics, different EEPROM
• Reputable suppliers: FS.com, ProLabs, Wintop

2. Enable Unauthorized Mode

Many switches have commands to bypass lock:

• Cisco: service unsupported-transceiver
• HP: allow-unsupported-transceiver
• May void warranty support for that link

3. Program Your Own

• SFP coding devices available ($200-500)
• Reprogram EEPROM for target switch
• Practical for bulk deployments

Compatibility Verification

Even bypassing vendor lock, verify:

• Correct speed for slot
• Correct wavelength/distance for partner
• Match connector type and fiber (SM/MM)
• Test in lab before production deployment

Third-Party SFP Quality

Reputable third-party modules from established vendors are functionally identical to OEM. Look for:

• SFF-8472 compliance
• DDM support
• Warranty (typically 5 years)
• Reference customer list