Quantcast
Channel: All Routing posts
Viewing all articles
Browse latest Browse all 8688

Instance Import / Export Policies Does Not Allow Traffic Between Routing Instances

$
0
0

Hi All,

I have configured one routing-instance on this MX104 see below:

 

root@a00-e-lab-00> show configuration routing-instances
test {
    instance-type virtual-router;
    interface irb.1;
    routing-options {
        instance-import import-workstation;
        instance-export export-direct;
    }
}

See the configuration for irb unit 1 and bridge domain below:

 

root@a00-e-lab-00> show configuration interfaces irb
mtu 1500;
unit 1 {
    family inet {
        address 169.254.254.14/30;
    }
}
root@a00-e-lab-00> show configuration bridge-domains

srx-bd-out {
    domain-type bridge;
    vlan-id 101;
    interface ge-0/0/8.0;
    interface ge-0/0/9.0;
    routing-interface irb.1;
}

I have configured the following route export/import policies to share a specific route (169.254.254.12/30) between the routing-instances: 

 

root@a00-e-lab-00> show configuration routing-options
nonstop-routing;
static {
    route 0.0.0.0/0 {
        next-hop 169.254.254.9;
        preference 1;
    }
}
autonomous-system 65311;
instance-import import-to-master;

root@a00-e-lab-00> show configuration policy-options
prefix-list workstation {
    10.38.140.100/30;
}
prefix-list export-direct {
    169.254.254.12/30;
}
policy-statement export-direct {
    from {
        prefix-list export-direct;
    }
    then accept;
}
policy-statement import-to-master {
    term import {
        from {
            instance test;
            prefix-list export-direct;
        }
        then accept;
    }
    term else {
        then reject;
    }
}
policy-statement import-workstation {
    from {
        prefix-list workstation;
    }
    then accept;
}

root@a00-e-lab-00> show configuration routing-instances
test {
    instance-type virtual-router;
    interface irb.1;
    routing-options {
        instance-import import-workstation;
        instance-export export-direct;
    }
}

When I show the route tables, the route is active in both routing tables, however I am unable to ping from the default routing-instance, while i am able to ping from the test routing instance. It appears that my route leaking is not working as intended, and I may be missing a configuration. Please advise.

Thanks

 

 

root@a00-e-lab-00> show route

inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0          *[Static/1] 02:59:43
                    > to 169.254.254.9 via irb.0
169.254.254.4/30   *[Direct/0] 18:47:42> via ae0.0
169.254.254.6/32   *[Local/0] 18:48:26
                      Local via ae0.0
169.254.254.8/30   *[Direct/0] 02:59:43> via irb.0
169.254.254.10/32  *[Local/0] 18:48:26
                      Local via irb.0
169.254.254.12/30  *[Direct/0] 00:23:08> via irb.1
172.17.0.140/32    *[Direct/0] 18:49:31> via lo0.0

test.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

169.254.254.12/30  *[Direct/0] 00:35:53
                    > via irb.1
169.254.254.14/32  *[Local/0] 00:35:53
                      Local via irb.1

Viewing all articles
Browse latest Browse all 8688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>