Working with iBGP speakers, some reasons we need to have our static, or connected routes to be advertised.
This how the config should be.
1. Define in iBGP group ‘the export’ or advertised routes.
group iBGP-INTERNAL {
type internal;
neighbor 192.168.224.109 {
description ***PEER-NAP1***;
import IMPORT-NAP1;
export EXPORT-NAP1;
peer-as 3852;
}
}
Please see BGP step by step config for more detail on how configuring this.
2. Create Policy Statement below policy-options
policy-statement REDISTRIBUTE-ROUTE
term connected {
from protocol direct;
then accept;
}
term static {
from protocol static;
then accept;
}
term local {
from protocol local;
then accept;
}
term else {
then reject
}
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term connected from protocol direct
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term connected then accept
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term static from protocol static
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term static then accept
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term local from protocol local
you@junOS#set policy options policy-statement REDISTRIBUTE-ROUTE term local then accept
you@junOS#commit
a. rahman isnaini rangkayo sutan
