FSM features available for JunOS devices

1. JunOS imports – file based, NCM, and through direct device connectivity
2. Device detail views with filtering
3. Queries
4. Service availability Reports
5. Rule Object cleanup – structural and file-based log data

JunOS constructs included

1. Address and applications objects, including object hierarchy
2. Global objects (must precede objects that reference it)
3. Zone to Zone policy
4. Global policy
5. Source, Destination, and static NAT.
6. Filter rules
7. Static and dynamic routes

JunOS constructs NOT Included

1. Cannot specify deny in route rules
2. IPv6 objects
3. Deny in route rules
4. VPN’s
5. Wild-card mask and its usage in policies.
6. Routing-instances.
7. Loopback interfaces and its usage.
8. Usage of “except” keyword for negation.
9. Inheriting policies using apply-groups feature.
10. Clusters.
11. NAT pool with multiple ranges.

Known Issues

1. If the route file contains  “ > “, then the remainder of the file is skipped. This is because, the device connector also uses “ > “ as the default device prompt. There is a high probability of a JunOS route file containing a ">". The workaround is to enable the checkbox that shows optional parameters and enter the correct device prompt, such as the device name followed by “  > “.
2. Pushing of JunOS scripts to SRX devices in a non test environment has some risks since testing has not finished  (e.g. regression).  Users should save their configurations in case a recovery is needed.
3. If “global” is used as the name of an address object following global object declarations are skipped.
4. Configuration containing  a license block are not imported.
5. Some pre-defined applications are not recognized by the translator
6. Configuration report does not show static routes in configuration.
7. Help pages have not been upddated to include JunOS.
8. Release notes have not been updated