Hi All,
I am currently working with a pair of MX80s on 11.2r7.4 and am using multiple Routing Instances for the first time.
The design is fairly strightforward:
1. The default Master Routing table is used for Interior Routing.
2. Additional Tables for Peering, Transit and additional ones for special cases where I need to get subsets of either Transit or Peering to other customers.
All of this works very well, however I'm experiencing something I can't explain with a loopback interface I have configured. Let's say the loopback is on 123.0.0.1/32 (not its actual address).
1. Routers/Switches that are within the Master Routing instance can ping 123.0.0.1/32 and get 123.0.0.1/32 as the source of the return packets.
2. Pings that come via one of the other routing tables (i.e. Peering or Transit) are received by the loopback, but return the ping as from an address associated with the physical interface (either the IRB or Physical interface - whichever is the egress for the return packet).
For the routing instance peering, I have the following (abbreviated):
router-peering {
instance-type virtual-router;
interface ge-1/1/2.599;
interface irb.306;
interface irb.315;
routing-options {
instance-import vr-send-to-peering-provider;
}
....
}
Here's part of the vr-send-to-peering-provider policy that imports routes which exposes (among other things) the loopback interface to the router-peering instance.
term 4 {
from protocol [ direct ospf ];
then accept;
}
Sure enough, the route is there
------
router-peering.inet.0: 10668 destinations, 10674 routes (10668 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
123.0.0.1/32 *[Direct/0] 10:15:10
> via lo0.0
------
The configuration of my loopback interface is fairly straightforward:
----
unit 0 {
description LO-MGMNT;
family inet {
no-redirects;
filter {
input-list [ accept-common-services ... discard-all ];
}
address 123.0.0.0.1/32 {
primary;
preferred;
}
address 127.0.0.1/32;
}
----
Clearly I have misunderstood something here. Thoughts anyone?
Thanks!