Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.8744.1.16 | MSM313 | 5.2.8, 5.3.5, 5.4.2 |
| 1.3.6.1.4.1.8744.1.20 | MSM310 | 5.2.8, 5.3.5, 5.3.6, 5.4.2 |
| 1.3.6.1.4.1.8744.1.23 | MSM323 | 5.2.8, 5.3.4, 5.4.2 |
| 1.3.6.1.4.1.8744.1.24 | MSM320 | 5.2.8, 5.3.5, 5.4.2 |
| 1.3.6.1.4.1.8744.1.25 | MSM730 | 5.2.8, 5.3.5 |
| 1.3.6.1.4.1.8744.1.27 | MSM750 | 5.2.8, 5.3.5 |
| 1.3.6.1.4.1.8744.1.28 | MSM422 | 5.2.8, 5.3.5, 5.4.2,5.7.0 |
| 1.3.6.1.4.1.8744.1.29 | MSM335 | 5.2.8, 5.3.5, 5.4.2 |
| 1.3.6.1.4.1.8744.1.35 | MSM710 | 5.2.8, 5.3.5 |
| 1.3.6.1.4.1.8744.1.41 | MSM410 | 5.2.8, 5.3.5, 5.4.2 |
| 1.3.6.1.4.1.8744.1.43 | MSM310-R | 5.2.8, 5.3.5, 5.4.2 |
| 1.3.6.1.4.1.8744.1.44 | MSM320-R | 5.2.8, 5.3.x, 5.4.2 |
| 1.3.6.1.4.1.8744.1.45 | MSM313-R | 5.2.8, 5.3.x, 5.4.2 |
| 1.3.6.1.4.1.8744.1.46 | MSM323-R | 5.2.8, 5.3.x, 5.4.2 |
| 1.3.6.1.4.1.8744.1.47 | MSM765 | 5.3.6,5.4.2,5.7.0 |
| 1.3.6.1.4.1.8744.1.48 | MSM760 | 5.2.8, 5.3.5, 5.4.2, 6.0 |
| 1.3.6.1.4.1.8744.1.52 | MSM460 | 5.5.0 |
| 1.3.6.1.4.1.8744.1.54 | MSM430 | 5.5.0 |
| 1.3.6.1.4.1.8744.1.55 | MSM466 | 5.5.0 |
| 1.3.6.1.4.1.8744.1.56 | MSM720 | 5.7.0 |
| 1.3.6.1.4.1.8744.1.58 | MSM466R | 5.7.0 |
The device may only allow a since manager to be logged in at a time. By default, tasks will fail if an existing manager login is detected. To override this behavior and boot the existing session, set the Device Access variable "admin_override" to "true".
Setting the device access variable "disable_http" to "true" will skip the HTTP portion of the snapshot.
Due to a device error, no error will be detected when deploying a software images that is both invalid and larger than 80MB.
The MSM device typically reports its CLI configuration with several commands that are not executable as-is from the device prompt. Individual devices may also have bugs that leave the device in the wrong context while executing through the config line by line. These lines must be modified to prevent warnings, including but not limited to the following commands: clock dst begin, clock dst end, ip route gateway, and dot11n multicast rate. Execution contexts around the command "virtual ap binding
" may need to be adjusted due to device context issues.
Only the CLI portion of the configuration will be deployed to the device; changes made to the HTTP portion will be ignored.
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".
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.