[Contents] [Prev] [Next] [Index] [Report an Error]

Examples: Configuring IS-IS Routing Policy

Define a policy that allows only host routes from USC (128.125.0.0/16), and apply the policy to routes exported from the routing table into IS-IS:



policy-options {


policy-statement usc-hosts-only {


term first {


from {
route-filter 128.125.0.0/16 upto /31;
}


then reject;
}


then accept;
}


}
protocols {


isis {
export usc-hosts-only;
}


}

Define a policy that takes Border Gateway Protocol (BGP) routes from the Edu community and places them into IS-IS with a metric of 14. Apply the policy to routes exported from the routing table into IS-IS:



protocols {


isis {
export edu-to-isis;
}


}
policy-options {
community Edu members 666:5;


policy-statement edu-to-isis {


from {
protocol bgp;
community Edu;
}


to protocol isis;
then metric 14;
}


}

Define a policy that rejects all IS-IS Level 1 routes so that none are exported into IS-IS:



policy-options {


policy-statement level1 {


term first {
from level 1;
then reject;
}


then accept;
}


}
protocols {


isis {
export level1;
interface fxp0;
}


}

Define a routing policy to export IS-IS Level 1 internal-only routes into Level 2:



[edit]
protocols {


isis {
export L1-L2;
}


}
policy-statement L1-L2 {


term one {


from {
level 1;
external;
}


then reject;
}




term two {
from level 1;
to level 2;
then accept;
}


}

Define a routing policy to export IS-IS Level 2 routes into Level 1:



[edit]
protocols {


isis {
export L2-L1;
}


}
policy-statement L2-L1 {


term one {
from level 2;
to level 1;
then accept;
}


}

[Contents] [Prev] [Next] [Index] [Report an Error]