Hi,
Multiple gr-0/0/0 units works fine for me.
Example:
gr-0/0/0 {
unit 0 {
tunnel {
source 192.168.110.1;
destination 192.168.100.1;
routing-instance {
destination 1;
}
}
family inet {
address 1.2.3.1/24;
}
}
unit 1 {
tunnel {
source 192.168.110.1;
destination 192.168.100.100;
routing-instance {
destination 1;
}
}
family inet {
address 2.3.4.1/24;
}
}
}
In my case I have my gr-0/0/0 units in a routing-instance called 1, hence that configuration line under tunnel.
Add both units to a zone, add routes to the other side.
route 3.4.5.0/24 next-hop gr-0/0/0.0;
route 4.5.6.0/24 next-hop gr-0/0/0.1;
And do the opposite on the other device.
show interfaces terse:
gr-0/0/0 up up
gr-0/0/0.0 up up inet 1.2.3.1/24
gr-0/0/0.1 up up inet 2.3.4.1/24
and ping tests:
adam@second> ping 4.5.6.1 routing-instance 1 detail verbose count 3
PING 4.5.6.1 (4.5.6.1): 56 data bytes
64 bytes from 4.5.6.1 via gr-0/0/0.1: icmp_seq=0 ttl=64 time=4.073 ms
64 bytes from 4.5.6.1 via gr-0/0/0.1: icmp_seq=1 ttl=64 time=3.913 ms
64 bytes from 4.5.6.1 via gr-0/0/0.1: icmp_seq=2 ttl=64 time=4.077 ms
--- 4.5.6.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.913/4.021/4.077/0.076 ms
adam@second> ping 3.4.5.1 routing-instance 1 detail verbose count 3
PING 3.4.5.1 (3.4.5.1): 56 data bytes
64 bytes from 3.4.5.1 via gr-0/0/0.0: icmp_seq=0 ttl=64 time=5.166 ms
64 bytes from 3.4.5.1 via gr-0/0/0.0: icmp_seq=1 ttl=64 time=4.126 ms
64 bytes from 3.4.5.1 via gr-0/0/0.0: icmp_seq=2 ttl=64 time=4.182 ms
On loopback however, you can only have one unit per routing instance, so you could have lo0.0 in master, and lo0.1 in a different one.
Interface config:
lo0 {
unit 0 {
family inet {
address 10.1.0.2/32;
}
}
unit 1 {
family inet {
address 10.2.0.2/32;
}
}
}
Add them to different routing instances, commit and you're left with this show interfaces terse:
lo0 up up
lo0.0 up up inet 10.1.0.2 --> 0/0
lo0.1 up up inet 10.2.0.2 --> 0/0