Hi Thong, We experienced same difficulty on 3rd party 1000base-T SFP.
We are preparing few MX5 (JUNOS 11.4R7.5) new deployment, and figured out all of our 3rd party 1000base-T SFP became UP even there is no cable plugged in. Those 3rd party 1000base-T SFP came from different vendors; they are working very well on M10i (JUNOS 10.4R4.5), and Cisco 6509. We also have some 3rd party SFP-SX and LX, they work well on MX5. On Wed, Aug 14, 2013 at 5:02 AM, Thong Hawk Yen <hawk.yen.th...@time.com.my> wrote: > Hi Mathias, > > We have experience something quite similar with out MX480 BRAS as well. Can > remember what version of Junos we were running but it was the "X" track > specifically for the subscriber management features instead of the "R" track. > It was a 3rd party copper SFP as well. > > Regards > thong > > >> Date: Sun, 31 Mar 2013 21:55:36 +0200 >> From: math...@nilings.se >> To: juniper-nsp@puck.nether.net >> Subject: [j-nsp] 1000Base-T SFP shows Link Up without cable inserted >> >> I've just upgraded two of my MX5-T boxes to 11.4R7.5 and after that my >> 3rd party 1000Base-T SFP (Transmode originals based on Finisar) started >> to show Link Up as soon as the SFP is inserted (no cable inserted). >> >> On 11.2R5.4 it worked as it should. 11.4R1.14 that the boxes came with >> was also broken. >> >> Bug or feature? Has anyone used any Juniper original 1000Base-T SFPs on >> the MX-5/10/40/80-T platform with JunOS 11.4? >> >> masun@solir1> show version >> Hostname: solir1 >> Model: mx5-t >> JUNOS Base OS boot [11.4R7.5] >> JUNOS Base OS Software Suite [11.4R7.5] >> JUNOS Kernel Software Suite [11.4R7.5] >> JUNOS Crypto Software Suite [11.4R7.5] >> JUNOS Packet Forwarding Engine Support (MX80) [11.4R7.5] >> JUNOS Online Documentation [11.4R7.5] >> JUNOS Routing Software Suite [11.4R7.5] >> >> masun@solir1> show chassis pic fpc-slot 1 pic-slot 1 >> FPC slot 1, PIC slot 1 information: >> Type 10x 1GE(LAN) SFP >> State Online >> PIC version 2.26 >> Uptime 2 days, 23 hours, 7 minutes, 20 seconds >> >> PIC port information: >> Fiber Xcvr vendor >> Port Cable type type Xcvr vendor part number Wavelength >> 0 GIGE 1000T n/a FINISAR CORP. FCLF8521P2BTL-TR n/a >> >> masun@solir1> show interfaces ge-1/1/0 >> Physical interface: ge-1/1/0, Enabled, Physical link is Up >> Interface index: 158, SNMP ifIndex: 526 >> Description: Link sthir2 for Logical Systems (VPLS Lab) >> Link-level type: Ethernet, MTU: 2000, Speed: 1000mbps, BPDU Error: None, >> MAC-REWRITE Error: None, >> Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, >> Auto-negotiation: Enabled, >> Remote fault: Online >> Device flags : Present Running >> Interface flags: SNMP-Traps Internal: 0x0 >> Link flags : None >> CoS queues : 8 supported, 8 maximum usable queues >> Current address: 08:81:f4:81:26:68, Hardware address: 08:81:f4:81:26:68 >> Last flapped : 2013-03-31 15:11:42 EDT (00:04:46 ago) >> Input rate : 0 bps (0 pps) >> Output rate : 0 bps (0 pps) >> Active alarms : None >> Active defects : None >> Interface transmit statistics: Disabled >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > > ________________________________ > > CONFIDENTIALITY > ------------------------- > The contents of and any attachments to this email are private and > confidential. If you are not the intended recipient or addressee indicated in > this message, please notify the sender of the error and destroy the email and > any attachments. Please do not reproduce the contents of the email or its > attachments as such reproduction is a breach of confidentiality and for which > legal action including injunctive relief may be sought against you. If it is > your company policy that official communications are not by email, please > advise immediately. Any opinions, conclusions and other information in this > message that do not relate to the official business of TIME dotCom shall be > understood as neither given nor endorsed by TIME dotCom, nor shall TIME > dotCom shall be liable (directly or vicariously) for such opinions, > statements or communications. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp -- -- Michel~ _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp