[j-nsp] em0/em1 intreface

[Doug Hanks]

fxp0 is still used for the external Ethernet port on the RE.

em0/em1 are also NICs on the RE, but they're internal and cross-connected
to the internal 24x1GE switch on each SCB.

Thank you,

-- 
Doug Hanks - JNCIE-ENT #213,  JNCIE-SP #875
Sr. Systems Engineer
Juniper Networks



On 3/16/12 1:48 PM, "Saku Ytti" <saku at ytti.fi> wrote:

>On (2012-03-16 22:21 +0200), Saku Ytti wrote:
>
>Reread the OP and seems the implication of fxp->em was not ever made. Just
>fxp[12] -> em[01].
>So confusion was just mine. And indeed new REs uses 1GE/em[01] for
>internal
>signalling instead of 100M/fxp[12] (but all still use 100M/fxp0 for
>management)
>
>> On (2012-03-16 12:05 -0700), Doug Hanks wrote:
>> 
>> > Depends on the platform, hardware, and routing engine.
>> > 
>> > At least on the MX the current RE uses em0 and em1.
>> 
>> This gives the impression in conjunction with OP that there is agreement
>> that fxp has been replaced by em. I'm not sure if that implication was
>> intended or not.
>> However that is not true, fxp are on-band dedicated management ethernet
>> (please JNPR, take page from CSCO and roll proper oob ethernet, like
>>CMP).
>> While em are used for internal signalling.
>> And current RE model uses both, but obviously for different purpose.
>> 
>> > >Hi All, Just wanted to clarify my understanding in emo and em1
>>interface.
>> > >
>> > >In the latest hardware (REs/CBs), juniper have replaced he fxp1 and
>>fxp2
>> > >interface with em0 and em1. Is this right?
>> 
>> -- 
>>   ++ytti
>
>-- 
>  ++ytti
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp