Driver Support Document

Juniper routers, EX series switches, SRX series firewalls, JUNOS version 10.x - 16.x

• Internal Driver Name: Junos10
• Driver Package: Junos10.rdp
  
• Driver Tier: 3
• Vendor: Juniper
• Family: Juniper JunOS
• IPv6 Support: Yes

Show Tested Devices Grid

Driver Features Support Grid

General Access

Release Notes

Configuration format

Juniper driver handles device configuration in stanza format by default. To change the format of the stored configuration to the "set" format, similar to Cisco, set the access variable "config_set_format" to "true".

VLAN deployment and Ethernet switching

Starting with JUNOS Release 10.0, the factory default configuration for SRX100, SRX210, and SRX240 devices automatically enables Layer 2 Ethernet switching. The "New VLAN" provision functions correctly when Layer 2 Ethernet switching is disabled on the device.

Setting terminal width enabled by default

This driver sends the command "set cli screen-width 0" by default when logging into a device, because of noted problems with line-wrapping on the device when a terminal width is set. To disable usage of this command, set the device access variable "skip_width" to any value.

Idle timeout

Juniper devices support a CLI idle out timeout, that cuts the terminal session after a set number of minutes. This can interfere with operations that take a long time, such as the capture of a large configuration by CLI. If the device access variable "idle_timeout" is set to a number of minutes, the command "set cli idle-timeout " will run after login.

Saving the configuration

Juniper devices do not have a "startup" configuration, and they allow commands to be submitted in configuration without necessarily being committed. To facilitate this behavior, the "force save" checkbox for tasks is used to control the "commit" behavior that is employed. If the checkbox is checked, a 'commit' will be run when exiting configuration mode. If it is not checked, the script will exit without committing changes.

return to top

ACL Parsing

Release Notes

Disable ACL parsing

This driver allows the disabling of ACL parsing, for situations where the ACLs may not be needed for device monitoring. To disable ACL parsing, set the Device Access variable "skip_acl" to "true".

return to top

Custom Scripts and Diagnostics

Release Notes

Commit failures are sometimes hidden

Junos devices do not have apply changes immediately, but only after a commit operations. In absense of a commit operation, changes are applied when exiting from configuration mode. Since normally this happens during the logout portion of tasks, the errors seen by the commit check can be buried. To ensure that errors are not buried, use the command "commit check" at the end of configuration mode scripts, which will ensure that any failures are detected before logout.

return to top

Driver Discovery

Release Notes

Driver Discovery fails if sysDescr is changed

Some Juniper devices allow user to change the sysDescr field. SNMP Discovery will work only if the sysDescr in the required format as per Juniper doc.

Deployment of Stanza configuration

The stanza configuration format can only be deployed by transport protocols. Deployment by the CLI-only option is not supported for stanza deployment. Some difficulties were noted in removing elements from the configuration, but these are caused by the device performing a merge rather than a replacement operation. If difficulties are seen, deploying using line-by-line SET scripts is recommended.

Override and Merge in deployment

The device may support the command "load override" or "load merge" to cause configuration deployment to choose an overwrite of the configuration or a merge. Set the device access variables "config_override" or "config_merge" to "true" to choose a specific mode; "load replace" is used by default.

return to top

Retrieve Running Configuration

Release Notes

Logical interface parsing

Some Juniper devices can contain literally 100,000 or more logical interfaces, which can cause serious performance degredation if they are parsed as interfaces. Set the device access variable "skip_logical" to "true" to skip the parsing for these interfaces.

return to top

Driver Discovery

Release Notes (inherited)

More prompt causes an unexpected disconnection

Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".

Wakeup Ctrl-U character can cause discovery to fail

Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.

return to top

Syslog Triggering

Trigger Patterns

Devices supported by this driver trigger changes using the following patterns:
UI_COMMIT


User Patterns

These patterns are used to determine the username/IP responsible for a change:
/UI_COMMIT: User '(\S+)' requested/

return to top