[j-nsp] P-4CHDS3

[info at beprojects.com]

  So are you saying that if I have a regular CHDS3 card and I setup
  queueing, it is for the whole card itself?  I can't setup queueing
  individually on the 28 T1's I mux out of it unless I have an IQ card?


> Julio Alba wrote:
> 
>> The hardware of the P and PE cards are identical, the only difference 
>> is the
>> mechanical estructure of the PIC. The PE has an ejector to take the 
>> card out
>> of the FPC, the P cards has not that ejector because that card is for M20
>> and that platform is not PIC hot swapable, it is FPC hot swapable. Anyway
>> both cards has the same features.
>>
>> The difference between and IQ PIC and one that is not, is that in the 
>> IQ PIC
>> you can have queues for logical interface, and in an interface that it is
>> not an IQ PIC the queues are for the physical interface. You can also get
>> more layer 2 information (Juniper says that, i have not experience on 
>> it).
>> The IQ cards has some feature limitations like MLPPP and other 
>> features, you
>> can find it in the Juniper Technical information, i suppose.
>>
>> Regards
>> Julio
>>
>>  
>> Julio Alba Soto
>> Consultor / Director de Proyectos (Área de Redes)
>> jalba at satec.es
>>  
>> SATEC-MADRID
>> Avda. Europa 34 A 28023 Aravaca, Madrid
>> Tlfn: +34 91 708 90 00
>> Fax: +34 91 708 90 90
>> www.satec.es
>>  
>>
>>
>>> -----Mensaje original-----
>>> De: juniper-nsp-bounces at puck.nether.net 
>>> [mailto:juniper-nsp-bounces at puck.nether.net] En nombre de 
>>> info at beprojects.com
>>> Enviado el: jueves, 14 de abril de 2005 19:13
>>> Para: juniper-nsp at puck.nether.net
>>> Asunto: [j-nsp] P-4CHDS3
>>>
>>> Someone just told me that you can actually use a P-4CHDS3 in an 
>>> M5/M10/M7i instead of the PE version that is listed as the correct 
>>> module for that series.  Does anybody know if this is true?
>>>
>>> Also, does anybody know what extra features you get with an IQ PIC v. 
>>> just a regular channelized PIC?  I see all sorts of vague things like 
>>> "Granular QoS", but no solid examples of what that means.  The only 
>>> thing I really care about at the moment is doing something similar to 
>>> Cisco's LLQ, where I create a couple of classes of traffic (voice is 
>>> priority queued, and data falls into llq or something similar).
>>>
>>> Thanks.
>>>
>>> Peder
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net 
>>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>
>>
>>
>>
>