How to Exclude Traffic from NAT on a Junos SRX
Connect Juniper Hardware to the Junos OS
How to Link an Explicit Route to the LSP Using Junos

Juniper Translators to Ease Conversion to Junos

A set of translators are available to convert configurations from other operating systems to Junos. Users paste their existing configuration into one of the translators, which translates the configuration and provides output suitable for downloading to a device running Junos. Juniper recommends that you review all output from the tools, but the tools can give you a good running start, typically translating 80 percent or more of your configuration.

Here are the two most popular translators:

  • IOS to Junos (I2J): Translates full IOS configurations for Cisco 65xx, 75xx, and 12xxx platforms into Junos OS configurations. I2J supports interfaces, routing protocols, routing policy, packet filtering, and system commands. EX Series Ethernet Switch features include VLAN, RVI, Access Port, Trunk Port, STP, LAG, Voice VLAN, IP Source Guard, AutoQoS, 802.1x, Port Security, RADIUS Server, DHCP Snooping & DAI, and AAA Authentication.

  • ScreenOS to Junos (S2J): Provides conversion of ScreenOS configuration files to Junos OS configuration files for SRX Series Services Gateways branch and datacenter platforms. S2J supports interfaces, protocols, policies, zones, route, NAT, user authentication, flow, HA, security, and other system commands.

Juniper customers with a support login can access the tools. Find out how to use the I2J tool in a freely available eTraining module by selecting the Training link on the I2J tool page.

blog comments powered by Disqus
How to Configure Routing Policies that Advertise Routes in Junos
How to Provide Redundancy with Junos Virtual Chassis
The Function of the Three Planes of Junos Network OS
Divide an IS-IS Network into Areas
How to Check Junos Configuration before Commit