Driver Support Document

Juniper Edge Routing Switch ERX 320, 700, 1400, 1440, OS version 8.x & 9.x

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.2636.3.1.1 ERX1440 8.1.2
 1.3.6.1.4.1.4874.1.1.1.1.1 ERX1400 8.0.3
 1.3.6.1.4.1.4874.1.1.1.1.2 ERX700 9.3.0
 1.3.6.1.4.1.4874.1.1.1.1.3 ERX1440 9.3.3
 1.3.6.1.4.1.4874.1.1.1.6.1 ERX320 9.3.3

Driver Features Support Grid

Driver FeaturesAccess Methods
(X signifies feature support)CLISNMPTFTPCLI+TFTPSNMP+TFTPFTPCLI+FTPSNMP+FTPCLI+SFTPSCPCLI+SCPSNMP+SCPHTTP/HTTPS
X Driver Discovery release notes X X                      
X General Access release notes
(CLI protocols: telnet, console)
Supports SecurID
X           X            
Configuration
X Retrieve Running Configuration release notes X           X            
  Retrieve Startup Configuration                            
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running release notes             X            
X Configuration Deployment to Startup (with reboot)               X            
  Binary Configuration Deployment                            
Diagnostics
X Routing Table   X                        
X OSPF Neighbors   X                        
X Interfaces   X                        
X Modules and Inventory   X                        
  Flash Storage Space                            
X File System   X                        
X Uptime     X                      
X ICMP Test   X                        
X Topology Parsing   X                        
  Duplex Parsing                            
  Enhanced VLAN Parsing  
Features
  Software Center                            
  Software Image Synchronization                            
  Password Management  
(Can modify: limited username, limited password, full username, full password, read-only community strings, read/write community strings)
                         
X Syslog Configuration and Change Detection   Syslog patterns X                        
X Custom Scripts and Diagnostics  
Bulk deploy available
X                        
X ACL Parsing  
X ACL Provisioning   X                        
  VLAN Provisioning                            
X Configlet Parsing  
  QoS Parsing  
  VRF Parsing  
  Context Management                            

General Access

Release Notes

Enable username usage

Older versions of this driver used the command "enable 15" to access enable mode, but this has been changed to simply use "enable" to support newer devices. To revert back to using the "enable 15" command, set the device access variable "enable15" to "true".

return to top

Retrieve Running Configuration

Release Notes

Take Snapshot task

The Take Snapshot task will fail if the manual-commit service is used by the device.

return to top

Configuration Deployment to Running

Release Notes

Deploy to startup configuration and reboot

When deploying a large device configuration to startup, it could take more than 30 minutes for the device to reboot and load the new configuration. As a result, this could cause the optional post Deploy Configuration Snapshot task to fail.

return to top

Driver Discovery

Release Notes

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

return to top