Hi,
Had few observations with regards to the output:
1. I believe the announcement is for IP Transit and can see some prefixes with longer than /24. As a best practice, it is recommended not to announce longer than /24 prefixes
http://archive.apnic.net/meetings/22/docs/tut-routing-pres-bgp-bcp.pdf
2. From the cisco config, I gathered prefixes in AES-ip & TCL-ip were being set local-preference of 500 towards AS9498 and AS4755 respectively. However, since this is eBGP, the local-preference attribute is only local within an AS and does not get announced with the set local-preference to eBGP peers.
To influence inbound routing for specific prefixes, AS-PATH preprend would be more appropriate.
3. The order of the export policies is also import in the configuration. For example:
set protocols bgp group group-1 neighbor 14.142.79.177 export bgp-redistributes set protocols bgp group group-1 neighbor 14.142.79.177 export bgp-policies-group-1-1-export
Policy "bgp-redistributes" already contains accept actions, hence the same prefix does not get evaluated in the next policy. Re-ordering the policy can be beneficial.
There are different ways to configure the policy for AS-PATH preprend. An example could be as below:
set policy-options prefix-list EXPORT-BGP 123.255.250.0/24
set policy-options prefix-list EXPORT-BGP 123.255.251.0/24
set policy-options prefix-list EXPORT-BGP 203.223.188.0/24
set policy-options prefix-list EXPORT-BGP 203.223.189.0/24
set policy-options prefix-list EXPORT-BGP 203.223.190.0/24
set policy-options prefix-list EXPORT-BGP 203.223.191.0/24
set policy-options prefix-list AES-AS-PREPEND 203.223.188.0/24
set policy-options prefix-list AES-AS-PREPEND 203.223.189.0/24
set policy-options prefix-list TCL-AS-PREPEND 43.225.164.0/24
set policy-options prefix-list TCL-AS-PREPEND 103.21.76.0/24
set policy-options prefix-list TCL-AS-PREPEND 123.255.250.0/24
set policy-options prefix-list TCL-AS-PREPEND 123.255.251.0/24
set policy-options prefix-list TCL-AS-PREPEND 203.223.190.0/24
set policy-options prefix-list TCL-AS-PREPEND 203.223.191.0/24
set policy-options policy-statement AES-AS-PREPEND term AES-PREPEND from prefix-list-filter AES-AS-PREPEND exact
set policy-options policy-statement AES-AS-PREPEND term AES-PREPEND then as-path-prepend "45536 45536"
set policy-options policy-statement AES-AS-PREPEND term AES-PREPEND then next policy
set policy-options policy-statement TCL-AS-PREPEND term TCL-PREPEND from prefix-list-filter TCL-AS-PREPEND exact
set policy-options policy-statement TCL-AS-PREPEND term TCL-PREPEND then as-path-prepend "45536 45536"
set policy-options policy-statement TCL-AS-PREPEND term TCL-PREPEND then next policy
set policy-options policy-statement EXPORT-BGP term EXPORT-STATIC from protocol static
set policy-options policy-statement EXPORT-BGP term EXPORT-STATIC from prefix-list-filter EXPORT-BGP exact
set policy-options policy-statement EXPORT-BGP term EXPORT-STATIC then community delete all
set policy-options policy-statement EXPORT-BGP term EXPORT-STATIC then accept
set policy-options policy-statement EXPORT-BGP term EXPORT-BGP from prefix-list-filter EXPORT-BGP exact
set policy-options policy-statement EXPORT-BGP term EXPORT-BGP then community delete all
set policy-options policy-statement EXPORT-BGP term EXPORT-BGP then accept
set policy-options policy-statement EXPORT-BGP term DEFAULT then reject
set protocols bgp group group-1 neighbor 14.142.79.177 export EXPORT-BGP
set protocols bgp group group-1 neighbor 14.142.79.177 export TCL-AS-PREPEND
set protocols bgp group group-2 neighbor 72.14.194.177 export EXPORT-BGP
set protocols bgp group group-2 neighbor 72.14.194.177 export AES-AS-PREPEND
It's important that the order of the export policies is in the correct order. Example:
export [ TCL-AS-PREPEND EXPORT-BGP ];
As mentioned before, there could be other ways of writing export policies to achieve the same objective.
Hope this helps.
Cheers,
Ashvin