[j-nsp] Juniper MX80 IRB

[Tim Vollebregt]

All,

Thanks a lot for your comments, seems that there are more occasions 
where this problem is occurring.
We are having the MX80-48T which has the Trio chip.

It was a bit strange while building the configuration, at some point it 
seemed to work the 10.x way. There was ARP, but no connectivity.
The system is now live with the following configuration and performing well:

ge-1/0/0 {
         encapsulation ethernet-bridge;
         gigether-options {
             no-flow-control;
         }
         unit 0;

   irb {
         description med-srvrs;
         unit 0 {
             description ALL;
             family inet {
                 address x.x.x.x/29;
                 address x.x.x.x/27;

bridge-domains {
     all {
         domain-type bridge;
         vlan-id none;
         interface ge-1/0/0.0;
         routing-interface irb.0

Regards,

Tim







On 28-07-10 15:49, Addy Mathur wrote:
> On Wednesday, July 28, 2010, Mark Tinka<mtinka at globaltransit.net>  wrote:
>    
>> On Tuesday, July 27, 2010 10:31:18 pm Chuck Anderson wrote:
>>
>>      
>>> Finally, JTAC/ATAC can't even figure out the above!!!  I
>>> have a case open and they *still* haven't come to the
>>> solution because they haven't realized that "Today Trio
>>> only supports the old style config" and what that really
>>> means.
>>>        
>> The disconnect between JTAC and the core of the development
>> team has always been there, in my opinion. It took a whole
>> year of back-and-forth with JTAC on a case that, when it was
>> finally escalated to a senior engineer within Juniper, was
>> resolved in 30 minutes. No, seriously...
>>
>> It's easy to assume that just because JTAC work for Juniper,
>> they're familiar with JUNOS and the Juniper hardware. But
>> this, as I've seen time&  time again, really isn't the case.
>>
>> Mark.
>>
>>      
> Although it doesn't answer the specific question raised via this
> thread, the following link dose offer some general guidance on Trio
> chipset features.  Should mostly be applicable to the MX80 as well.
>
> http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/general/mpc-mx-series-features.html
>
> Regards,
> Addy.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>