Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.2021.250.255 | unknown | 9.1, 9.2, 9.3 |
| 1.3.6.1.4.1.3375.2.1.3.4.4 | bigip1500 | 9.1, 9.2, 9.3 |
| 1.3.6.1.4.1.3375.2.1.3.4.11 | bigip6800 | 9.1, 9.2, 9.3 |
Please make sure the full access user is assigned an administrator role with Advanced Shell access enabled in user setting. The same is true for RADIUS/TACACS+ users.
Every snapshot is saved no matter the binary configuration is the same as previous one or not. (every binary configuration captured is checksumed, the checksum is appended to ASCII configuration) When the 'compare to previous' link is clicked on in the case of no real difference, the 'No difference detected' warning page will be shown. Tracking bug: 173012
The .ucs binary backup file saves configuration files and system directories, such as user home directories. When backing up large files, such as .iso images, the size of the .ucs binary backup file can increase significantly. A large .ucs binary backup file could cause a SCP timeout. To configure the .ucs binary backup file to include and/or exclude specific directories and files, refer to your vendor's documentation or Support website for information.
The configuration snapshot needs to use both CLI and SCP, therefore, SSH and SCP need to be enabled in order for snapshot to succeed.
The system has only one binary configuration deploy option available which is with reboot even though the binary configuration deploy on F5 is just a simple binary backup restore which does not require reboot, however, every binary configuration deploy will go through reboot process but without actually rebooting the device due to this limitation.
Community string management is not supported by the system Password Management. However, you can use Edit & Deploy to modify device community strings if necessary.
After resetting device passwords and setting a network-wide password rule, the Deploy Password task populates the username field on the Edit Device page with the username of the first password rule tried. This potential mismatch, where the username is not the one used by the Deploy Password task to access the device, but rather the username of the first password rule, does not cause device access issues.
For F5 devices with OS versions 9.4.5.x or 9.4.7.x running on a Windows platform, the Configure Syslog task fails due to a timeout error. However, the Syslog host is configured on the device while the task is running.
The Big-IP does not support telnet connections by default, so the system attempts to access the device using this protocol will normally fail. We recommend disabling telnet as a protocol to use on these devices to avoid unnecessary failures.
Community string management is not supported by the system Password Management. However, you can use Edit & Deploy to modify device community strings if necessary.
For real-time change detection, we recommend that network engineers use the system integrated SSH client, the console port, or the device's graphical user interface (GUI). Otherwise, the system may not detect configuration changes.