Forum Discussion
senthil147_1421
Jun 06, 2017Nimbostratus
F5 LTM sending reset packets to Pool member
F5 LTM has a pool member listening on port 8003 and its mainframe server. Pool member is UP but Mainframe console shows consistently F5 is rejecting the connection ( No issues in accessing the VIP )....
NAG_65570
Jun 06, 2017Historic F5 Account
F5 BigIP can add reset cause in to the packet or in to LTM logs. You can use following commands for enabling reset cause related dbkeys.
Example::
Reset cause: BIG-IP: [0x1abb6c9:1532] Policy action
To log a message in ltm logs:: tmsh modify /sys db tm.rstcause.log value enable To to include reset cause within packet:: tmsh modify /sys db tm.rstcause.pkt value enable
To disable dbkey after troubleshooting:: tmsh modify /sys db tm.rstcause.log value disable tmsh modify /sys db tm.rstcause.pkt value disable
Once you know the reset cause, it is relatively easy to find the root cause
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects