[c-nsp] 3rd party dwdm 80km optics in asr 9001

Jared Mauch jared at puck.Nether.net
Wed Sep 28 07:40:52 EDT 2016


	We've had good luck working with Cisco to report problems
with them accepting 3rd party optics.  Sometimes it's the optics fault
sometimes it's a software constraint issue.

	I would check the EEPROM results for conformance to SFF-8472
and if Cisco is handling SFF-8472 wrong, you can get them to fix it.

	It may take a few rounds, but is worthwhile.  We've gone so far
as to work with them to send them 3rd party optics for their labs to
help with their testing.

	- Jared

On Wed, Sep 28, 2016 at 11:09:15AM +0000, Gustav Ulander wrote:
> Yepp
> We actually got an error that says unsupported transceiver so that's why we are going to try a different supplier. 
> 
> LC/0/0/CPU0:Sep 27 08:26:43.698 : pfm_node_lc[294]: %PLATFORM-SFP-3-DEV_SFP_SUPPORTED_ERROR : Clear|vic[475264]|0x1029000|SFP Module for port 00 is not a supported module type
> LC/0/0/CPU0:Sep 27 08:26:43.699 : pfm_node_lc[294]: %PLATFORM-SFP-3-DEV_SFP_PID_NOT_SUPPORTED : Clear|vic[475264]|0x1029000|SFP Module for port 00 is not a supported Product ID (PID)
> RP/0/RSP0/CPU0:Sep 27 08:26:44.151 : invmgr[255]: %PLATFORM-INV-6-IF_OIROUT : xFP OIR: 0/0/2 port_num: 0 is removed, state: 0
> RP/0/RSP0/CPU0:Sep 27 08:27:28.669 : invmgr[255]: %PLATFORM-INV-6-IF_OIRIN : xFP OIR: 0/0/2 port_num: 0 is inserted, state: 1
> LC/0/0/CPU0:Sep 27 08:27:29.775 : pfm_node_lc[294]: %PLATFORM-SFP-3-DEV_SFP_SUPPORTED_ERROR : Set|vic[475264]|0x1029000|SFP Module for port 00 is not a supported module type
> LC/0/0/CPU0:Sep 27 08:27:29.775 : pfm_node_lc[294]: %PLATFORM-SFP-3-DEV_SFP_PID_NOT_SUPPORTED : Set|vic[475264]|0x1029000|SFP Module for port 00 is not a supported Product ID (PID)
> When looking at the optics. 
> 
> Operational data for interface TenGigE0/0/2/0:
> 
> State:
>     Administrative state: enabled
>     Operational state: Down (Reason: Link loss or low light, no loopback)
>     LED state: Red On
> 
> Phy:
>     Media type: Not known
>     Optics:
>         Vendor: Pro10Optix
>         Part number: SFP-10G-DWDM-192
>         Serial number: D1509180341
>         Wavelength: 0 nm
>     Digital Optical Monitoring:
>         Transceiver Temp: 37.000 C
>         Transceiver Voltage: 3.217 V
> 
> Im starting to wonder if it's the wrong partnumber that it is reacting on. 
> 
> //Gustav
> 
> -----Ursprungligt meddelande-----
> Från: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] För Shawn L
> Skickat: den 28 september 2016 12:54
> Till: Cisco Network Service Providers <cisco-nsp at puck.nether.net>
> Ämne: Re: [c-nsp] 3rd party dwdm 80km optics in asr 9001
> 
> I've found cisco routers to be especially picky about 3rd party optics lately.  I have guaranteed compatible optics that work flawlessly in Cisco switches the will absolutely not work in a cisco router (asr-1001 /
> ASR-9001 / 9k).  Generally in the router you can see them, etc.  they just don't ever establish a link.
> 
> On Wed, Sep 28, 2016 at 6:47 AM, Curtis Piehler <cpiehler2 at gmail.com> wrote:
> 
> > I am rather shocked this doesn't work.   I'm not sure about the 9001
> > however we use varies MPAs for the 9006/9010 with third party dwdm 
> > xfp/sfp+ no issues.
> >
> > On Sep 28, 2016 6:42 AM, "Gustav Ulander" 
> > <gustav.ulander at telecomputing.se
> > >
> > wrote:
> >
> > > Hello.
> > >
> > > Iam woundering if anyone has had issues running 3rd party optics in 
> > > the built in optics ports of a ASR9001 .
> > > We have some 80km DWDM optics that we get module is not supported for.
> > > We tried with transceiver permit pid all. We have similar SR-MM 
> > > modules installed in the same machine that is working as advertised.
> > > Iam beginning to wounder if the ASR 9001 is more sensitive with the 
> > > longrange optics?
> > > We have been using the same optics in a couple of 6500 SUP2t with X2 
> > > converters without issues but we cant seem to be bale to get a link 
> > > on
> > the
> > > ASR9001.
> > > We are running 5.3.3 on these routers which might be an issue also 
> > > we haven't tried downgrade them to something earlier.
> > > Perhaps others has had the same issue?
> > >
> > > //Gustav
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.


More information about the cisco-nsp mailing list