Driver Support Document

Juniper routers, EX series switches, OS version 5.5, 6.x, 7.x, 8.x, 9.x (OBSOLETE, PLEASE REDISCOVER)

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.2636.1.1.1.1.2 M20 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.5 M5 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.1.6 T640 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.8 M40e 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.10 M7i 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.11 M10i 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.13 J2300 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.14 J4300 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.15 J6300 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.19 J4350 9.3R4.4
 1.3.6.1.4.1.2636.1.1.1.2.20 J6350 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.23 J2320 8.5
 1.3.6.1.4.1.2636.1.1.1.2.25 MX480 9.3R2.8
 1.3.6.1.4.1.2636.1.1.1.2.26 SRX5800 5.5, 6.x, 7.x, 8.x, 9.x
 1.3.6.1.4.1.2636.1.1.1.2.27 T1600 9.3R4.4
 1.3.6.1.4.1.2636.1.1.1.2.28 SRX5600 9.5R1.8
 1.3.6.1.4.1.2636.1.1.1.2.31 EX4200-24T 9.2R3.5
 1.3.6.1.4.1.2636.1.1.1.4.31.3 EX4200-48T 9.2B2.4
 1.3.6.1.4.1.2636.1.1.1.2.39 SRX240 8.3, 9.3

Driver Features Support Grid

Driver FeaturesAccess Methods
(X signifies feature support)CLISNMPTFTPCLI+TFTPSNMP+TFTPFTPCLI+FTPSNMP+FTPCLI+SFTPSCPCLI+SCPSNMP+SCPHTTP/HTTPS
  Driver Discovery                            
X General Access release notes
(CLI protocols: telnet, ssh1, ssh2, console)
Supports SecurID
X     X           X      
Configuration
X Retrieve Running Configuration   X     X           X      
  Retrieve Startup Configuration                            
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running   X     X           X      
X Configuration Deployment to Startup (with reboot)   X     X           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                        
X Duplex Parsing   X                        
  Enhanced VLAN Parsing  
Features
X Software Center release notes       X           X X    
X Software Image Synchronization release notes                   X      
X Password Management  
(Can modify: full password, read-only community strings, read/write community strings)
X                        
X Syslog Configuration and Change Detection   Syslog patterns X                        
X Custom Scripts and Diagnostics release notes
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

Configuration format

By default, Juniper driver handles device configuration in stanza format. To change the format of the stored configuration to "set format", similar to Cisco, go to Edit/Edit Device, scroll down to Device Access Settings and set a custom setting "config_set_format" with the value "true". The only configuration deployment solution available in this format is "Deploy to running configuration". Using "Deploy to startup configuration" or "Deploy to startup configuration and reboot" will result in task failure.

Chassis Cluster (High Availability) management

Once configured as part of a Chassis Cluster, the two devices share the same configuration. In addition, interface numbers on secondary nodes are re-indexed and commands/diagnostics run on either device are run at Cluster level. Although both devices can be assigned a Management IP address, adding both devices to NA can result in unpredictable results, such as duplicate inventory data or commands that run multiple times on each device.

Workaround:

To manage a Chassis Cluster configuration, use a Master-only IP address.

return to top

Custom Scripts and Diagnostics

Release Notes

Juniper bulk script deployment

The JunOS operating system stores its configuration in a hierarchiacal structure rather than as a series of commands. Bulk configuration deployment is designed to handle the merging of blocks of configuration data directly while line-by-line deployment is designed to run a series of commands.

Displaying error messages when running custom scripts

Some Juniper devices do not report errors after configuration deployment until the configuration is committed. However, NA does not correctly extract the error messages.

Workaround:

To ensure error messages are reported, use the Bulk Deploy option rather than line-by-line deployment when possible.

return to top

Software Center

Release Notes

Juniper filename limitations

The JunOS operating system requires that certain characters be escaped with a leading slash when they are used on the device's command line. NAS can not support use of these characters in filenames when used for deploying a SoftwareUpdate image or when deleting files from the device using the Image Sync task. These disallowed characters are known to include the bracket and brace characters, but there may be other non-alphanumeric characters that are similarly not supported.

JunOS SCP library incompatibility

Software Center operations may experience protocol errors due to issues with SCP library compatibility with JunOS version 8.1R3.3.

JunOS Image Validation

When running the Update Device Software task, if the software image validation fails, the Update Device Software task will fail. Workaround: If you want to avoid the OS verification errors and continue running the Update Device Software task, you must initialize the following custom variable:

1. Login to the system.
2. On the menu bar, select Devices and click Inventory.
3. On the Inventory page, locate the Juniper device
4. In the Actions column for teh Juniper device, click the Edit option.
5. On the Edit Device page, scroll down to the Device Access Settings field.
6. Add the following Custom Setting variable: ignoreValidation
7. Set the Value to: true
8. Click the Save Device button.

return to top

Syslog Triggering

return to top