Driver Support Document

Brocade (formerly Foundry) Iron devices, IronWare versions 2.x, 3.x, 4.x, 5.x, 7.x, 8.x, & 10.x; TrafficWork version 12.x

• Internal Driver Name: Foundry_JS
• Driver Package: Foundry_JS.rdp
  
• Driver Tier: 3
• Vendor: Brocade
• Family: Brocade Iron
• IPv6 Support: Not Supported

Show Tested Devices Grid

Driver Features Support Grid

Retrieve Running Configuration

Release Notes

Startup Configuration by CLI

Some Foundry devices do not support retrieval of the startup configuration via CLI methods, but only by TFTP. TFTP must be enabled to gather startup configurations in this case.

return to top

Configuration Deployment to Running

Release Notes

Duplication of ACL objects during configuration deployment

Some Foundry devices do not properly merge ACL objects in a deployed configuration with the objects existing on the device, resulting in duplicate configuration statements for the affected To prevent this, NA removes ACL definitions from the configuration before it is merged with the device configuration. To deploy ACL modifications to the device, use a Command Script rather than standard deployment options.

SCP deployment to startup falsely succeeds

Brocade devices support deployment to startup by SCP, but in some cases seem to ignore the changes. The correct filename is used by the driver (startConfig) and the transaction succeeds, but changes don't show. Currently known affected models: SuperX, FGS624P-POE. It seems to be a device issue, as yet unfixed, because it appears in the latest OS versions.

return to top

General Access

Release Notes

Extra support for drivers that use HTTP

This note applies only for drivers that use HTTP requests for driver functions. HTTP proxy operations are supported by setting the device access variable "http_proxy" to "ip:port", replacing with the IP and port values of the proxy server. SNI-requiring devices (e.g CloudGenix & Cisco Meraki) can be supported by using the device access variable "alternate_host" to contain the DNS name of the host. The host name will be used rather than the normal management IP address for all HTTP requests, effectively supporting SNI.

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

Trigger Patterns

Devices supported by this driver trigger changes using the following patterns:
added by
was changed by
modified by
enabled by
disabled by
Warm start


User Patterns

These patterns are used to determine the username/IP responsible for a change:
/was changed by (\S+)/
/modified by (\S+)/
/enabled by (\S+)/
/disabled by (\S+)/

return to top