I’ve often wondered what the point of an IRB on an ethernet only platform is.  
In the olden days IRB/CRB interfaces were used to bridge TDM interfaces into 
ethernet vlans to for the purposes of pure evil.  With ethernet you can just 
add your physical interfaces to the same vlan.  I suppose you could bridge two 
vlans together, but that’s better done by moving the physical interfaces.

I say this only to illustrate the fact that IRB’s are different than RVI’s, but 
probably unnecessary on an ethernet only platform.

The newer feature guide makes no mention of IRB’s.  I did find a page for 10.2 
which confirms old info.

http://www.juniper.net/techpubs/software/junos-security/junos-security10.2/junos-srx-jseries-support-reference/jd0e5921.html

On Apr 5, 2014, at 2:32 PM, Morgan McLean <wrx...@gmail.com> wrote:

> Klaus,
> 
> Yes its RVI on branch but its IRB on datacenter SRX; you can't even
> configure vlans on them.
> 
> Anyway, thanks all for the answers, just needed to verify I wasn't going
> crazy.
> 
> Thanks,
> Morgan
> 
> 
> On Sat, Apr 5, 2014 at 5:58 AM, Klaus Groeger <kla...@gmail.com> wrote:
> 
>> On SRX branches one configures :
>> 
>> 
>> 
>> 
>> interfaces {
>> 
>>    vlan {
>> 
>>         unit 123 {
>> 
>>             family inet {
>> 
>>                        address 192.168.123.1/24
>> 
>>             }
>> 
>>         }
>> 
>>    }
>> 
>>    ge-0/0/0 {
>> 
>>          unit 0 {
>> 
>>             family ethernet-switching
>> 
>>                  vlan {
>> 
>>                       members 123
>> 
>>                   }
>> 
>>             }
>> 
>>         }
>> 
>>    }
>> 
>> }
>> 
>> 
>> 
>> 
>> vlan {
>> 
>>    onetwothree {
>> 
>>        vlan-id 123
>> 
>>        l3-interface vlan.123
>> 
>>    }
>> 
>> }
>> 
>> 
>> 
>> 
>> On SRX IRBs are called RVIs (Routed VLAN Interfaces). This way one gets
>> interfaces configured
>> 
>> as switching interfaces with a routable address. You may apply most L2
>> options in branch SRX as needed, even LAGs and all the other stuff.
>> 
>> 
>> 
>> 
>> Regards,      Klaus
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp


_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to