Driver Support Document

Avaya (Formerly Nortel Secure Router and Tasman) 4134, OS version 10.x

Show Tested Devices Grid

SYSOID Mapping
SYSOID MODEL OS VERSION
 1.3.6.1.4.1.562.73.2.2.4.1.1 Nortel Secure Router 4134 10.x
 1.3.6.1.4.1.562.73.2.2.5.1.1 Nortel Secure Router 4134 10.3.0.0

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  
(CLI protocols: telnet, ssh2, console)
Supports SecurID
X     X                  
Configuration
X Retrieve Running Configuration release notes X     X                  
X Retrieve Startup Configuration   X                        
  Retrieve Binary Configuration                            
X Device information parsing  
X Enhanced Layer2 Basic IP information parsing  
X Configuration Deployment to Running         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                        
X Duplex Parsing   X                        
  Enhanced VLAN Parsing  
Features
X Software Center         X                  
X Software Image Synchronization         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  
Bulk deploy available
X                        
X ACL Parsing  
X ACL Provisioning release notes X                        
  VLAN Provisioning                            
X Configlet Parsing  
X QoS Parsing  
  VRF Parsing  
  Context Management                            

Retrieve Running Configuration

Release Notes

CLI and TFTP configurations variations

A configuration captured via CLI is different when compared to a configuration captured via TFTP. The TFTP configuration contains several empty configlet blocks that are not reported in the CLI configuration.

return to top

Password Management

Release Notes

SNMP community strings

Depending on the current security and privacy settings on the Nortel Secure Router 4134 device, SNMP community strings could be masked in the configuration, making it impossible for the driver to parse them. As a result, this feature is disabled. The Deploy Password task will only show the two SNMP community strings stored in the NAS database in the Password Information section. The driver only supports one read-only and one read-write community string.

return to top

ACL Parsing

Release Notes

Editing ACLs

When editing ACLs, NAS merges the new rules into the current configuration.

Workaround: Before editing an ACL, remove ACLs targeted for modification. The Edit ACL task will merge the new rules to the current configuration.

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