It's a name change. vlan is now irb. It depends on platform, but the newer
ones use irb instead of vlan.
So it doesn't work with vlan.103 because the vlan interface physically does not
exist. But you can configure nonexistent interfaces in JunOS.
On Feb 18, 2014, at 9:44 PM, Janusz Wełna wrote:
> Hi,
>
>
> Why when I have below config:
>
> ge-0/0/44 {
> description test;
> unit 0 {
> family ethernet-switching {
> vlan {
> members vlan103;
> }
> storm-control default;
>
> unit 103 {
> description test;
> family inet {
> address 10.46.163.1/29;
>
>
> vlan103 {
> description test;
> vlan-id 103;
> l3-interface vlan.103;
>
>
>
>
> I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
> server connected to ge-0/0/44
>
>
>
>
> But when I add below:
>
>
> irb {
> unit 103 {
> family inet {
> address 10.46.163.1/29;
>
>
> and delete :
>
>
> vlan103 {
> description SGI;
> vlan-id 103;
> l3-interface vlan.103
>
>
>
>
> ping works correctly.
>
>
> On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need on
> EX4300 ?
>
>
>
> Br,
>
>
> Janusz
> _______________________________________________
> 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
