Driver Support Document

EXT_Enterasys Switches, B2, B3, B5, C2, C5, D2, & G3 Series, Matrix N1 & N3 Platinum, SSA Chassis, OS version 1.x, 3.x, 4.x, 5.x, 6.x & 7.x

• Internal Driver Name: EXT_Enterasys_Switches
• Driver Package: EXT_Enterasys_Switches.rdp
  
• Driver Tier: 3
• Vendor: Enterasys
• Family: Enterasys
• IPv6 Support: Not Supported

Show Tested Devices Grid

Driver Features Support Grid

General Access

Release Notes

Configuration scripting mode

Most Enterasys devices support a "routing" mode, with a configuration mode within. For such devices, the "configuration" scripting mode will enter this mode. For some models (SSA), there is a routing mode but it does not contain a configuraton mode; for these devices, "configuration" scripts will use this routing mode. If a routing mode is not supported, "configuration" scripts will simply stay in the mode entered at login.

return to top

Retrieve Running Configuration

Release Notes

Get the whole configuration

Many Enterasys devices support a 'show config all' command that includes all default settings in the returned configuration. To retrieve this configuration, set the device access variable "showConfigAll" to "true".

Saving configuration for SCP/TFTP transport

Many Enterasys devices support a 'show config all' command that includes all default settings in the returned configuration. To retrieve this configuration, set the device access variable "showConfigAll" to "true".

Deploy SNMP protocol versions

Enterasys devices support separate access settings for each SNMP protocol version for each community string. SNMPv2c strings are deployed by default, but other security models can be deployed by adding the model after the string, e.g. "public (v1)" as the string would deploy the public string with version 1.

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:
logged in from
logged out from


User Patterns

These patterns are used to determine the username/IP responsible for a change:
/User:(\S+) logged (?:in/
/out) from (\d+\.\d+\.\d+\.\d+)/

return to top