Has anyone experienced Juniper OEM SFPs appearing as 'unsupported' on 'not supported' on initial boot-up. It frustrating somewhat since a reboot resolves the problem, or sometimes re-seating a perfected seated SFP fixes.
Platform is EX and MX
One possibility is SFP+ ports not supporting SFP without explicit configuration:
But it doesn't make sense this one toggles on a reboot. You are probably looking at a transient/cosmetic HW issue. If the issue is for a few SFPs or a module, please try to move ports and/or swap it to check if the issue follows the SFP or the port.
Hope this helps.
If this solves your problem, please mark this post as "Accepted Solution."Kudos are always appreciated :).
Please paste "show chassis hardware" and "show chassis pic fpc-slot x pic-slot x" so that we know the exact module we are discussing.
A few possibilities:
1. Transient HW issue. Something went wrong during FPC reboot process or insertion of SFP. This is most likely your case, since a reboot can resolve the issue
2. sfp sfp+ incombatibility
3. There're corner cases that a particular Juniper SFP is supported for platform 1, for example MX, but not supported for platform 2, for example EX. Those are really corner cases and we have been working on to close such gap
If this is constantly repeatable, I'd suggest to open a JTAC case to track such issue
Does this happens to a certain set of optics or it happens to all the optics on that particular FPC/PIC.
A sample of "show chassis hardware" and "show chassis pic fpc-slot <> pic-slot <>" showing those optics will help determining further details of make/model/vendor-name etc. Please provide that.
Also as the previous expert informed, if its consistently reproducible, opening a JTAC case should be the next steps.