[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juniper-nsp
Subject:    [j-nsp] 10G optics showing up as OC3
From:       Jared Mauch via juniper-nsp <juniper-nsp () puck ! nether ! net>
Date:       2024-04-19 15:12:35
Message-ID: A64EAB52-8EB4-49D2-A806-5D08836CC5D8 () puck ! nether ! net
[Download RAW message or body]

Hello, I wanted to share this for others.  I had received a 10G DWDM optic from my \
carrier and it wouldn't work.  Turns out the optic did not have the reach programmed \
into it and JunOS didn't handle this well.

I addressed this by writing the reach into byte 0x3 on the optic, which for the FS \
ones required writing a password to change the byte, which was 0x00000000 for this FS \
optic.

Apr 16 19:27:41  Router fpc0 Unknown transceiver type. Set to default OC3C  
Apr 16 19:27:41  Router fpc0 sfp-0/0/36(36), SFP 21: unknown OC3 optic type 0 

Before fixing:
https://github.com/jaredmauch/sfppi/blob/master/data_samples/sfp-dwdm-ch44-nonjnpr

After fixing:

https://github.com/jaredmauch/sfppi/blob/master/data_samples/sfp-dwdm-ch44-nonjnpr-fixed


I wanted to share this in case someone else had a similar problem.  It's interesting \
that an ethernet-only platform even allowed OC3 to be a default.  Have a good \
weekend.

- jared
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[prev in list] [next in list] [prev in thread] [next in thread]