19 messages in net.nether.puck.cisco-nsp[c-nsp] 12.0.30S (NPE-150)
FromSent OnAttachments
Brian FeenyJan 7, 2005 12:23 pm 
Dave TemkinJan 7, 2005 12:32 pm 
Rodney DunnJan 7, 2005 12:43 pm 
Brian FeenyJan 7, 2005 12:46 pm 
Ted MittelstaedtJan 8, 2005 1:52 am 
RoyJan 8, 2005 2:33 am 
Ted MittelstaedtJan 9, 2005 1:04 am 
Gert DoeringJan 9, 2005 1:09 pm 
Rodney DunnJan 10, 2005 3:59 pm 
RoyJan 10, 2005 7:46 pm 
Rodney DunnJan 11, 2005 11:47 am 
Ted MittelstaedtJan 12, 2005 1:03 am 
Gert DoeringJan 12, 2005 2:46 am 
Rodney DunnJan 12, 2005 8:27 am 
Rodney DunnJan 12, 2005 8:32 am 
Gert DoeringJan 12, 2005 8:50 am 
RoyJan 12, 2005 10:12 am 
Rodney DunnJan 12, 2005 10:46 am 
Ted MittelstaedtJan 12, 2005 4:55 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] 12.0.30S (NPE-150)Actions...
From:Gert Doering (ge@greenie.muc.de)
Date:Jan 9, 2005 1:09:25 pm
List:net.nether.puck.cisco-nsp

Hi,

On Sat, Jan 08, 2005 at 10:04:09PM -0800, Ted Mittelstaedt wrote:

If I read the following correctly, the only NPE left for non-VXR is the NPE-225

Which is a shame as I recall there's some hardware issues with certain older PA cards and certain of their hardware revisions and that NPE.

As far as I understand, the problem occurs only if your run those "old PAs" in a VXR chassis. The higher bus clock in the VXR is what causes the problem, not the NPE-225 in itself.

At least we haven't seen any issues with "known-old" PAs in non-VXR/225s, while the same PAs did definitely not work in VXR/225s.

gert