Mailing List Archive

VLAN sub-interfaces in VRR em0?
Hey,

Running the JunOS VRR image on EVE-NG trying to get a vlan sub-interface working on em0:

root@R4# show interfaces em0
traps;
vlan-tagging;
mtu 1614;
hold-time up 10000 down 0;
unit 14 {
vlan-id 14;
family inet {
address 100.1.4.4/24;
}
family iso;
family inet6 {
address 2607:f0c8::100:1:4:4/112;
}
family mpls;
}
unit 45 {
vlan-id 45;
family inet {
address 100.4.5.4/24;
}
family iso;
family inet6 {
address 2607:f0c8::100:4:5:4/112;
}
family mpls;
}

[edit]
root@R4#

R4 can ping itself at 100.1.4.4. While capturing on em0 and tying to ping 100.1.4.1 from R4, I see correctly tagged ARP request/reply, but the ARP table is empty, so no pingy.

Is this not supported, or am I missing something?

Thanks in advance!
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: VLAN sub-interfaces in VRR em0? [ In reply to ]
Jason, I don't think vlan sub-interfaces are supported. We used multiple interfaces mapped to different vlans via the Hypervisor. You can map em0 to vlan 14 and em1 to vlan 45, ...

--
Clinton Work

On Mon, Nov 4, 2019, at 9:02 AM, Jason Lixfeld wrote:
> Hey,
>
> Running the JunOS VRR image on EVE-NG trying to get a vlan
> sub-interface working on em0:
>
> root@R4# show interfaces em0
> traps;
> vlan-tagging;
> mtu 1614;
> hold-time up 10000 down 0;
> unit 14 {
> vlan-id 14;
> family inet {
> address 100.1.4.4/24;
> }
> family iso;
> family inet6 {
> address 2607:f0c8::100:1:4:4/112;
> }
> family mpls;
> }
> unit 45 {
> vlan-id 45;
> family inet {
> address 100.4.5.4/24;
> }
> family iso;
> family inet6 {
> address 2607:f0c8::100:4:5:4/112;
> }
> family mpls;
> }
>
> [edit]
> root@R4#
>
> R4 can ping itself at 100.1.4.4. While capturing on em0 and tying to
> ping 100.1.4.1 from R4, I see correctly tagged ARP request/reply, but
> the ARP table is empty, so no pingy.
>
> Is this not supported, or am I missing something?
>
> Thanks in advance!
> _______________________________________________
> 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
Re: VLAN sub-interfaces in VRR em0? [ In reply to ]
? 4 novembre 2019 11:02 -05, Jason Lixfeld <jason-jnsp@lixfeld.ca>:

> Running the JunOS VRR image on EVE-NG trying to get a vlan
> sub-interface working on em0:

It doesn't work when using virtio, but it works with e1000. Dunno if
EVE-NG allows you to pick which NIC device to use.
--
Don't go around saying the world owes you a living. The world owes you
nothing. It was here first.
-- Mark Twain
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: VLAN sub-interfaces in VRR em0? [ In reply to ]
My situation might be different than yours, but, I'm using vlan tags in
junos vMX on eve-ng... (17.4R1.16)


root@sabn-960-e> show interfaces ae161.0
Logical interface ae161.0 (Index 344) (SNMP ifIndex 546)
Flags: Up SNMP-Traps 0x20004000 VLAN-Tag [ 0x8100.10 ] Encapsulation:
VLAN-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 6278792 0 525388584 0
Output: 5878898 0 497667878 256
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Protocol bridge, MTU: 1522


root@sabn-960-e> show configuration interfaces ae161.0 | display set
set interfaces ae161 unit 0 encapsulation vlan-bridge
set interfaces ae161 unit 0 vlan-id 10


root@sabn-960-e> show arp interface irb.10 no-resolve
MAC Address Address Interface Flags
02:05:86:71:20:00 172.223.10.30 irb.10 [.local..8] permanent remote
02:05:86:71:3e:00 172.223.10.31 irb.10 [ae161.0] permanent remote
Total entries: 2


root@sabn-960-e> show configuration interfaces irb.10 | display set
set interfaces irb unit 10 family inet address 172.223.10.1/24
set interfaces irb unit 10 mac 00:00:00:00:00:0a

root@sabn-960-e> ping 172.223.10.31
PING 172.223.10.31 (172.223.10.31): 56 data bytes
64 bytes from 172.223.10.31: icmp_seq=0 ttl=64 time=106.272 ms
64 bytes from 172.223.10.31: icmp_seq=1 ttl=64 time=144.518 ms
64 bytes from 172.223.10.31: icmp_seq=2 ttl=64 time=180.567 ms
^C
--- 172.223.10.31 ping statistics ---
4 packets transmitted, 3 packets received, 25% packet loss
round-trip min/avg/max/stddev = 106.272/143.786/180.567/30.335 ms


- Aaron

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