[j-nsp] Junos to IOS translation

Mon Jun 6 09:34:09 EDT 2016

What code and platform are you intending to get this converted to? This is
not a complicated config on the Cisco side.

On Mon, Jun 6, 2016 at 6:53 AM, Mohammad Khalil <eng.mssk at gmail.com> wrote:

> set routing-options aggregate defaults preference 250
> set routing-options aggregate route 192.168.1.0/19
> set routing-options aggregate route 192.168.2.0/20
> set routing-options aggregate route 192.168.3.0/21
>
> set policy-options community ALL-COMM members *:*
> set policy-options community From-ARBOR members 48832:1919
> set policy-options community From-MOBILE members 48832:601
> set policy-options community To-GGC-1-8C members 48832:201
> set policy-options community To-GGC-1-AA members 48832:202
> set policy-options community To-GGC-2-8C members 48832:203
> set policy-options community To-TINET-LNDN-1 members 48832:116
> set policy-options community To-TINET-LNDN-2 members 48832:118
> set policy-options community To-TINET-MRS-AA members 48832:112
>
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term PRIMARY-ADV
> from community To-TINET-LNDN-1
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term PRIMARY-ADV
> then community delete ALL-COMM
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term PRIMARY-ADV
> then accept
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term BACKUP-ADV
> from community To-TINET-LNDN-2
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term BACKUP-ADV
> then community delete ALL-COMM
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term BACKUP-ADV
> then as-path-prepend "48832"
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term BACKUP-ADV
> then accept
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term MOBILE-TEMP
> from route-filter 46.32.124.0/24 exact
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term MOBILE-TEMP
> then community delete ALL-COMM
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term MOBILE-TEMP
> then as-path-prepend "48832"
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term MOBILE-TEMP
> then accept
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> ZAIN-AGG-SUBNETS from route-filter 192.168.1.0/19 exact
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> ZAIN-AGG-SUBNETS from route-filter 192.168.2.0/20 exact
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> ZAIN-AGG-SUBNETS from route-filter 192.168.3.0/21 exact
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> ZAIN-AGG-SUBNETS then accept
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-ZG-AA
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-ZG-MRS-AA
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-ZG-AQ-AA
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-TINET-MRS-AA
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-ZG-8C
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-ZG-MRS-8C
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-TS-ZG-8C
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-UMNIAH
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC from community From-TINET-LNDN-2
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term
> PREVENT-TRANSIT-TRAFFIC then reject
> set policy-options policy-statement EXPORT-TINET-LNDN-1 term REJECT-ELSE
> then reject
> set policy-options policy-statement IMPORT-TINET-LNDN-1 term DEFAULT-ROUTE
> from route-filter 0.0.0.0/0 exact
> set policy-options policy-statement IMPORT-TINET-LNDN-1 term DEFAULT-ROUTE
> then community add From-TINET-LNDN-1
> set policy-options policy-statement IMPORT-TINET-LNDN-1 term DEFAULT-ROUTE
> then accept
> set policy-options policy-statement IMPORT-TINET-LNDN-1 term REJECT-ELSE
> then reject
> set policy-options policy-statement NHS term 1 from protocol bgp
> set policy-options policy-statement NHS term 1 from route-type external
> set policy-options policy-statement NHS term 1 then next-hop self
>
>
> set protocols bgp group IBGP type internal
> set protocols bgp group IBGP local-address 192.168.106.201
> set protocols bgp group IBGP family inet unicast
> set protocols bgp group IBGP family inet-vpn unicast
> set protocols bgp group IBGP family l2vpn signaling
> set protocols bgp group IBGP export NHS
> set protocols bgp group IBGP neighbor 192.168.106.204
> set protocols bgp group LNDN-1 import IMPORT-TINET-LNDN-1
> set protocols bgp group LNDN-1 export EXPORT-TINET-LNDN-1
> set protocols bgp group LNDN-1 remove-private all
> set protocols bgp group LNDN-1 peer-as 3257
> set protocols bgp group LNDN-1 neighbor 77.67.90.181
>
> On Mon, Jun 6, 2016 at 2:23 PM, Sebastian Becker <sb at lab.dtag.de> wrote:
>
> > Be aware that this is not like translating word by word to get the same
> > functionality. The same will apply if you compare Google Translator
> against
> > a real studied translator in person.
> >
> > --
> > Sebastian Becker
> > sb at lab.dtag.de
> >
> > > Am 05.06.2016 um 17:51 schrieb Mark Tinka <mark.tinka at seacom.mu>:
> > >
> > >
> > >
> > >
> > > On 5/Jun/16 16:37, Doug McIntyre wrote:
> > >
> > >> I would expect to find such a tool on *cisco's* website, its not like
> > >> a vendor will write a tool for you to go away from them. But then
> > >> again I wouldn't expect Cisco to be that accomidating either.
> > >>
> > >> I've not heard of such a tool, of course several vendors provide an
> IOS
> > >> to their kit, but the opposite doesn't tend to happen all that often.
> > And
> > >> with the slight subtle differences in IOS vs IOS-XE and IOS-XR
> depending
> > >> on what your target platform is, might be pretty difficult to
> maintain.
> > >>
> > >> It would probably be pretty straight forward to translate Juniper
> > >> configs over to IOS, the layout of the config should be pretty
> > >> straightforward and self-documenting (unlike IOS, with hidden
> defaults,
> > >> or really magical things, like dynamic routing prefix filter lists).
> > >
> > > You can't even get an IOS to IOS XR converter, so no chance Cisco will
> > > write a Junos to IOS converter.
> > >
> > > Back in 2008, when I deployed my first IOS XR box (a 4-slot CRS
> router),
> > > I spent a month reading about IOS XR (3.9 at the time), and mapping
> > > every IOS command to IOS XR where one existed.
> > >
> > > Mark.
> > > _______________________________________________
> > > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>