[j-nsp] MX - DWDM no link

Luca Salvatore Luca at ninefold.com
Wed Nov 7 06:40:24 EST 2012


Thanks for the info Ben,
Actually got it working just now.

Silly me... I left off the 'set chassis network-services ip' command.
Once that was configured my interfaces came up

________________________________________
From: Ben Dale [bdale at comlinx.com.au]
Sent: Wednesday, 7 November 2012 10:36 PM
To: Luca Salvatore
Cc: juniper-nsp at puck.nether.net nsp
Subject: Re: [j-nsp] MX - DWDM no link

Hi Luca,

I have a funny feeling you'll need to plug the tunable into one of the built-in XFP ports to make it work.

If this doesn't work:

- Confirm that the MUXes you are connecting to are definitely DWDM and not CWDM.  If they are CWDM, make sure you are connecting to the 1530nm (Channel 53) or 1550nm (Channel 55) interface and that the channel you are using on your MX corresponds (eg: Channel 55 will work with 1547.72 through 1553.33)

- Confirm that the port you are connected to on the mux is the same at both sides (all other wavelengths will be filtered)

- Confirm that the channel you have set under your interface configuration is EXACTLY the same as the wavelength supported on your MUX port - the tuneable optic will allow you to change channels in increments of 50Ghz, whereas most muxes will only offer channels spaced 100Ghz apart (so every 2nd channel on the tuneable will be filtered out no matter what port you plug it into)

As mentioned by others, DWDM wavelengths aren't visible to the naked eye as they sit in the Infra-red bad of the EM Spectrum.  Aside from that, some I'm sure I've seen some gear (EX4200s with 4xGE module) seems to implement Auto-Laser Shutdown by default which drops the continuous beam to short (sub-second) pulses when loss of signal is detected at either end so if you unplug even the RX on the optic, you generally won't see any link.  Much better than having to screw around with UDLD though.

If you're stuck without the proper equipment, use the camera on your mobile phone to view the FOBOT - it's much better at detecting infra-red light and you'll avert the free eye surgery.  That said, I don't know how sensitive your phone camera will be to be to wavelengths >1500nm

The output from show interfaces diagnostics looks clipped.  There should be alarm statuses as well?

Also check out:

http://labs.spritelink.net/juniper-mx-and-tunable-xfps

It lists some are some pfe shell commands you can run to confirm the wavelength the optic has been set to (which should tell you if it's supported).  Why Juniper don't include the current wavelength in the diagnostics output is beyond me...

Cheers,

Ben

On 07/11/2012, at 8:30 PM, Luca Salvatore <Luca at ninefold.com> wrote:

> Well thanks for the info.
> p.s. i'm not trolling, i have done lots of troubleshooting - but was posting from my iphone so didn't have the info handy.  It is all included below.
>
> The fibre run is about 40Km point to point.  There are other people already using it on their own frequencies at 10Gb so I know it works.
> While i'll admit my knowledge about DWDM stuff is not great, I do have plenty of experience in the routing and switching space - just not much with the long haul fiber stuff.
>
> Anyway here are some of the steps I have taken:
>
> We have tried to reverse the Tx/Rx already with no luck.
> Changed / removed the wavelength frequencies
> Reboot routers
> offline / online FPC.
>
> So the is tunable 10Gb optic supported in MX10 or not?
>
> I have attached some outputs from some show commands and interface diagnostics
>
> mx10-1> show chassis fpc pic-status
> Slot 0   Online
>  PIC 0  Online       4x 10GE XFP
> Slot 1   Online
>  PIC 0  Online       10x 1GE(LAN) SFP
>  PIC 1  Online       10x 1GE(LAN) SFP
>  PIC 2  Online       1x 10GE XFP
>  PIC 3  Online       1x 10GE XFP
>
>
> mx10-1> show interfaces diagnostics optics xe-1/2/0
> Physical interface: xe-1/2/0
>    Laser bias current                        :  20.861 mA
>    Laser output power                        :  1.4120 mW / 1.50 dBm
>    Module temperature                        :  32 degrees C / 89 degrees F
>    Laser rx power                            :  0.0000 mW / - Inf dBm
>
> mx10-1> show chassis hardware
> <snip>
> FPC 1                     BUILTIN      BUILTIN           MPC BUILTIN
>  MIC 0          REV 26   750-028392   CAAM5167          3D 20x 1GE(LAN) SFP
>    PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
>      Xcvr 9     REV 02   740-011613   AA0945ST7PM       SFP-SX
>    PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
>  MIC 1          REV 21   750-028380   CAAN6158          3D 2x 10GE XFP
>    PIC 2                 BUILTIN      BUILTIN           1x 10GE XFP
>      Xcvr 0     REV 03   740-031585   FC0691140180      XFP-10G-T-DWDM-ZR
>
>
> Here is the MX at the other end:
>
> MX10-2> show interfaces diagnostics optics xe-1/2/0
> Physical interface: xe-1/2/0
>    Laser bias current                        :  22.166 mA
>    Laser output power                        :  1.4120 mW / 1.50 dBm
>    Module temperature                        :  28 degrees C / 83 degrees F
>    Laser rx power                            :  0.0000 mW / - Inf dBm
>
> MX10-2>show chassis hardware
> Hardware inventory:
> <snip>
> MIC 0          REV 26   750-028392   CAAM6764          3D 20x 1GE(LAN) SFP
>    PIC 0                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
>      Xcvr 9     REV 02   740-011613   PN174MT           SFP-SX
>    PIC 1                 BUILTIN      BUILTIN           10x 1GE(LAN) SFP
>      Xcvr 0     REV 02   740-011613   PN23ZW4           SFP-SX
>  MIC 1          REV 21   750-028380   CAAN6147          3D 2x 10GE XFP
>    PIC 2                 BUILTIN      BUILTIN           1x 10GE XFP
>      Xcvr 0     REV 03   740-031585   FC0994260069      XFP-10G-T-DWDM-ZR
>    PIC 3                 BUILTIN      BUILTIN           1x 10GE XFP
> Fan Tray                                                 Fan Tray
>
> MX10-2> show chassis fpc pic-status
> Slot 0   Online
>  PIC 0  Online       4x 10GE XFP
> Slot 1   Online
>  PIC 0  Online       10x 1GE(LAN) SFP
>  PIC 1  Online       10x 1GE(LAN) SFP
>  PIC 2  Online       1x 10GE XFP
>  PIC 3  Online       1x 10GE XFP
>
>
>
>
>
>
> ________________________________________
> From: Jeff Wheeler [jsw at inconcepts.biz]
> Sent: Wednesday, 7 November 2012 7:08 PM
> To: Luca Salvatore
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] MX - DWDM no link
>
> On Wed, Nov 7, 2012 at 2:37 AM, Luca Salvatore <Luca at ninefold.com> wrote:
>> This might seem silly but when I look into the XPF in the router I don't see any red lights coming from inside the XPF. Normally when you look into a XFP or SFP you can see the red laser inside it. I'm not seeing that with the XFP in the MX. Should I be able to see a light?
>>
>> Any suggestions?  I have configured the wavelengths on each side and the interface is just configured as a simple inet interface.
>
> <SwedeMike> don't look into laser with remaining good eye!
>
> The light coming from that XFP is not within the visible spectrum.
> You can't see it BUT IT CAN DAMAGE YOUR EYE.  Do not look into it!
>
> To be honest, I'm not sure your post isn't a troll!  However, there
> are plenty of things that could be wrong with your installation.  The
> Tx/Rx fibers could be reversed.  You may be using the wrong wavelength
> for the underlying DWDM system.  The fiber span may not be good enough
> for 10G -- are there other 10G waves working on it?  1G/2.5G waves?
> You might need amplification or chromatic dispersion correction
> equipment.  Your XFPs could be bad.  Maybe it's vendor fiber and it is
> not patched correctly?  Perhaps you have in-building cross-connects
> which are not completed or are of poor quality?
>
> Who really knows?  You have done zero basic troubleshooting steps.
> The reason why is (assuming you aren't a troll) you don't understand
> what you are doing.  I think your project will be more successful if
> you find a local contractor to help you.  This may sound rude, but you
> are not even working SAFELY at this point, let alone effectively.  Get
> yourself some assistance so you can get the job done without damaging
> your eyesight or delaying your work.  You probably need someone local
> to you, because there is a very big knowledge gap between what you've
> got (in this specific context) and what you might need to troubleshoot
> quickly and SAFELY.  The mailing list can hand-hold you through it if
> you post more information and do a bunch of troubleshooting steps, but
> I wouldn't want to be on the phone with my dark fiber vendor going,
> "well, some guys on juniper-nsp told me to rent a light meter and I
> used it and can't see any signal from my other POP..."  :-/
>
> $0.02.  Again, I apologize if my response seems rude, but you are
> going to harm your eyes!
> --
> Jeff S Wheeler <jsw at inconcepts.biz>
> Sr Network Operator  /  Innovative Network Concepts
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list