SRX

Hi All,

 

   I have a question about importing routes from other Virtual-routers into the main Master table (inet.0).  currently I have 3 VR's ( Master plus two othe VR).  I want to import some routes from the VR's into the Main table. To do this I created a policy statements that matches some static routes.  the policies look somethign like this (syntax not correct)

 

 

policy statement VM1

    term one

           from

                routing-instance VM1

                protocol static

           then

                accept

     term last

            then reject

 

policy statement VM2

    term one

           from

                routing-instance VM2

                protocol static

           then

                accept

     term last

            then reject

 

 

Then I got into the routing options of the main table and import them in.

 

 

[routing-options]

    instance-import (VM1 || VM2)

 

As you can see here I have to use an or (||) operation in order to get routes from both tables imported.  I will eventually have about 100 Virtual routers in this SRX.  Does anyone know a way i can do the imports without having to have a instance-import command that will have 99 OR statements inside?

 

thanks

 

 

 

 

 

 

you can use rib-groups for route import and export. http://kb.juniper.net/InfoCenter/index?page=content&id=KB16133 I don't know if you can use wildcard in the rib groups, or ranges. maybe you can ask juniper for the range option in the rib group, or ask for this feature to be added to a future release.

Thanks for the suggestion PKC but I wanted to stay away from this aswell because this will still require me to have the inport rib command in my main table which will get WAY to big.

 

ex) when i have 100 VR's

 

routing-options      {
         rib-groups  {
               test {
                 import-rib [ inet.0 test.inet.0 a.inet.0 z.inet.0 b.inet.0 c.inet.0 d.inet.0 e.inet.0 f.inet.0 g.inet.0 h.inet.0 .....ETC  ];
          }
}

Maybe this will work for you:

routing-instances {

    vr_98 {
        routing-options {
            auto-export;
        }
    }

    vr_99 {
        routing-options {
            auto-export;
        }
    }
and so on.

Solution was that my policy statements had a term reject all at the end.  The policy-import would then hit only the first one in the list the || operation would never even get used.

could you not put it all in one policy and use the then next-term statement to jump from term to term until a final reject?