[c-nsp] 3rd party Xenpak for 65xx

[Richard A Steenbergen]

On Fri, Sep 22, 2006 at 04:47:15PM +0200, Blake Willis wrote:
> On Wed, Sep 20 2006, Richard A Steenbergen wrote:
> 
> > Not true, service unsupported-transceiver enables third party XENPAKs as 
> > well. I have more than a few Foundry branded LR XENPAKs which only run 
> > with service unsupported and detect as:
> >
> > Te3/1                      connected    trunk         full    10G bad EEPROM
> > Te3/4                      connected    trunk         full    10G bad EEPROM
> 
>  	Hmmm, when I tested a few (Mitsu, Agilent, etc), I couldn't even get 
> a CDP neighbor to show up:
> 
> Te2/2                      disabled     1             full    10G unapproved
> Te2/3                      disabled     1             full    10G unapproved
> 
>  	Admittedly this was quite a while ago, and the lab box I was using 
> at the time was running either SXB or an early version of SXE (had one of 
> each, don't remember which one I was using that day, but probably SXE2 or 
> something as I don't recall SXB having 'unsupported transceiver' capability, 
> and I remember having some Sumitomo SFPs in the sup at the time that 
> worked).  Good to know that with newer releases this behaviour has changed.

I think you're confusing "disabled" with "errdisabled". In your example 
above, you just need to go "no shut" the port which is admin down by 
default. :)

And yes "service unsupported-transceiver" was added in SXE, in code 
earlier than this there was no way to turn off the vendor locking for SFP 
and XENPAK.

-- 
Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)