On 7 Nov 2011, at 17:00, cisco-nsp-requ...@puck.nether.net wrote:
> That sounds like an IOS bug.
>
> What does "sh idprom int Tex/y | inc endor" say for one of the non-Cisco
> parts, compared to a Cisco part?
Mystery solved: without going into the full long story, 75oC ambient
temperature in a
Architect
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Michael Balasko
Sent: Monday, November 07, 2011 3:16 PM
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Third Party Xenpaks
What we have done is order one legit optic so
What we have done is order one legit optic so we can get around the "TAC" issue
when we call and then we tend to use finisar or merge for our optics.
Nary an issue yet and oddly I feel happy that I am not being asked to grab the
far side of the desk.
Michael Balasko
CCSP,CCNP,MCSE,SCP
Network Sp
On 07/11/11 17:56, Scott Voll wrote:
unfortunatelyit all came from a very large customer..
They were using 3rd party stuff and things were failing. couldn't figure
it out told cisco to figure it out or they were going to rip
everything out.
Cisco sent staff and found that the fiber
unfortunatelyit all came from a very large customer..
They were using 3rd party stuff and things were failing. couldn't figure
it out told cisco to figure it out or they were going to rip everything
out.
Cisco sent staff and found that the fiber transciever they were using was
over
On 07/11/11 14:09, Michael Robson wrote:
After seeing how much money there is to be saved from using third
party optics instead of Cisco branded ones, we finally bought a few
to try. We have encountered no issues with using 10Gbps xenpaks, we
plugged them in and they just worked. However, we did
After seeing how much money there is to be saved from using third party optics
instead of Cisco branded ones, we finally bought a few to try. We have
encountered no issues with using 10Gbps xenpaks, we plugged them in and they
just worked. However, we did notice that DOM support was missing for