Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.388.1.5 | AP-4121 | 02.52-13, 03.70-62 |
| 1.3.6.1.4.1.388.1.8 | AP-4131 | 02.52-13, 03.70-62 |
| Driver Features | Access Methods | ||||||||||||||
| (X signifies feature support) | CLI | SNMP | TFTP | CLI+TFTP | SNMP+TFTP | FTP | CLI+FTP | SNMP+FTP | CLI+SFTP | SCP | CLI+SCP | SNMP+SCP | HTTP/HTTPS | ||
| X | Driver Discovery | X | |||||||||||||
| X |
General Access
(CLI protocols: telnet, console) |
X | |||||||||||||
| Configuration | |||||||||||||||
| X | Retrieve Running Configuration | X | |||||||||||||
| Retrieve Startup Configuration | |||||||||||||||
| Retrieve Binary Configuration | |||||||||||||||
| X | Device information parsing | ||||||||||||||
| X | Enhanced Layer2 Basic IP information parsing | ||||||||||||||
| Configuration Deployment to Running release notes | |||||||||||||||
| Configuration Deployment to Startup | |||||||||||||||
| Binary Configuration Deployment | |||||||||||||||
| Diagnostics | |||||||||||||||
| Routing Table | |||||||||||||||
| OSPF Neighbors | |||||||||||||||
| X | Interfaces | X | |||||||||||||
| Modules and Inventory | |||||||||||||||
| Flash Storage Space | |||||||||||||||
| File System | |||||||||||||||
| X | Uptime | X | |||||||||||||
| ICMP Test | |||||||||||||||
| X | Topology Parsing | X | |||||||||||||
| Duplex Parsing | |||||||||||||||
| Enhanced VLAN Parsing | |||||||||||||||
| Features | |||||||||||||||
| Software Center | |||||||||||||||
| Software Image Synchronization | |||||||||||||||
|
Password Management
|
|||||||||||||||
| Syslog Configuration and Change Detection | |||||||||||||||
|
Custom Scripts and Diagnostics
|
|||||||||||||||
| ACL Parsing | |||||||||||||||
| ACL Provisioning | |||||||||||||||
| VLAN Provisioning | |||||||||||||||
| Configlet Parsing | |||||||||||||||
| QoS Parsing | |||||||||||||||
| VRF Parsing | |||||||||||||||
| Context Management | |||||||||||||||
The Symbol AP-41xx Access Point does not report errors in the deployment of a configuration before a restart, instead it ignores errors (and restarts with whatever the last saved configuration is).
It is important to review the detected changes in the configuration after a configuration deployment to ascertain whether the desired changes took effect.
Because the device reboots on deployment, a configuration deployment attempt will result in the TFTP server being set to the NAS server used for deployment and the config file name will be set to the filename used by NAS for the deployment.
Since passwords and community strings cannot be captured from the device configuration NAS has no way of knowing if these have changed. If an Edit & Deploy action is taken that includes changes to these values, NAS will not be able to identify these changes and may end up losing connectivity to the device after the deployment.
You will need to manually reconfigure NAS with the new passwords and/or community strings in order to restore connectivity with the device.