Switching

last person joined: 3 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  EX4550: skewed SFP+ Receiver signal average optical power

    Posted 01-27-2015 01:31

    Hi,

     

    we have 2 distinct FO connections betwean EX3300 and EX4550, about 20km long. FO was mesured and the data is ok.

     

    On EX4550 we are observing 100 times or 20dBm lower "Receiver signal average optical power" then expected.

     

    EX4550

    Receiver signal average optical power     :  0.0011 mW / -29.64 dBm

    Receiver signal average optical power     :  0.0010 mW / -29.84 dBm

     

    Laser rx power high alarm threshold       :  0.0100 mW / -20.00 dBm

    Laser rx power low alarm threshold        :  0.0002 mW / -38.01 dBm

     

    EX3300s:

    Receiver signal average optical power     :  0.1196 mW / -9.22 dBm

    Receiver signal average optical power     :  0.2027 mW / -6.93 dBm

     

    Laser rx power high alarm threshold       :  1.0000 mW / 0.00 dBm

    Laser rx power low alarm threshold        :  0.0158 mW / -18.01 dBm

     

    It seems that the EX4550 is misinterpreting the data from SFP+.

    Did anyone came acros this issue ?

     

    the transceevers are same in EX4550 and EX3300 and ofcrs non juniper ones

     

     



  • 2.  RE: EX4550: skewed SFP+ Receiver signal average optical power
    Best Answer

     
    Posted 01-27-2015 01:40

    Yes, this is a known issue. Please check this:

     

    https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1007055

     


    =====

    If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.



  • 3.  RE: EX4550: skewed SFP+ Receiver signal average optical power

    Posted 01-27-2015 02:46

    Thank You, this seems to be it.



  • 4.  RE: EX4550: skewed SFP+ Receiver signal average optical power

     
    Posted 01-27-2015 06:09
    Just FYI but the fix for this situation is in 12.3R8.