Bug ID 1753033: Snmp is not working if mgmt is in 172.17.x.x network in 1.8.0

Last Modified: Jul 27, 2025

Affected Product(s):
F5OS F5OS-A, Install/Upgrade(all modules)

Known Affected Versions:
F5OS-A 1.8.0

Fixed In:
F5OS-A 1.5.3

Opened: Nov 19, 2024

Severity: 2-Critical

Symptoms

The snmpwalk command times out after an upgrade.

Impact

The snmpwalk command fails if the management IP is in 172.17.x.x network in 1.8.0

Conditions

-- The management IP address is in the 172.17.x.x network -- The system is upgraded from 1.5.2

Workaround

Remove the iptables entries with 172.x network as source from the file /etc/sysconfig/iptables and reboot the system Steps are as below Verify existing entries: # iptables-save | grep 172.17 -A POSTROUTING -s 172.17.0.0/16 ! -o br-97c791a9e730 -j MASQUERADE -A POSTROUTING -s 172.17.0.0/16 ! -o br-e4f09d90e378 -j MASQUERADE Make a backup of the iptables file # cp /etc/sysconfig/iptables /etc/sysconfig/iptables.bak Edit the entries in the iptables file # grep -v '\-s 172.' /etc/sysconfig/iptables.bak > /etc/sysconfig/iptables Run this command: # iptables-save | grep -vF 172.17.0.0/16 > iptables Reboot the device: # reboot Verify entries. Either of these commands should return no results # iptables-save | grep 172.17 # grep '172.17' /etc/sysconfig/iptables

Fix Information

During the upgrade from 1.5.2 to any higher version, the iptables for default docker network (172 network) are removed

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips