asm error
2 TopicsConfig Sync problem in F5
Dear Folks, I am getting below error messages in ltm log file. Active Device Aug 7 13:09:00 MyLoadbalancer info mcpd[7608]: 0107148c:6: Received advertisement for device group /Common/Sync-Failover from remote device /Common/Peer_LB.xyz.com, force true, error '' commit_id 329 5317022206481634851 /Common/MyLoadbalancer.xyz.com 0, local commit id is 329 5317022206481634851 /Common/MyLoadbalancer.xyz.com 0 cached remote device data id 0 Aug 7 13:09:00 MyLoadbalancer info mcpd[7608]: 01071528:6: Device group '/Common/Sync-Failover' sync inconsistent, Incremental config sync may not be complete on one or more devices in this devicegroup, Sync status may not be consistent until incremental config sync is complete.. Standby device Aug 7 13:09:00 MyPeerLoadbalancer info mcpd[6443]: 0107148f:6: Advertising device group /Common/Sync-Failover, force true, error '' commit_id 329 5317022206481634851 /Common/MyLoadbalancer.xyz.com 0. Aug 7 13:10:47 MyPeerLoadbalancer info mcpd[6443]: 0107148c:6: Received advertisement for device group /Common/Sync-Failover from remote device /Common/MyLoadbalancer.xyz.com, force true, error '' commit_id 329 5317022206481634851 /Common/MyLoadbalancer.xyz.com 0, local commit id is 329 5317022206481634851 /Common/MyLoadbalancer.xyz.com 0 cached remote device data id 0 Please suggest solution if any , this log is continuosly getting logged in log files. In GUI everything looks ok . Furthermore , getting below ASM error log as well. Aug 7 13:28:24 MyLoadbalancer err tmm1[16325]: 016e0002:3: Execution of action 'asm enable policy=/Common/ASM-Policy-Name' failed, error ERR_UNKNOWN499Views0likes1CommentF5 ASM and Avepoint Docave
I'm trying to configure a virtual server for a Docave host, but when I try to navigate to the page with ASM enabled on the VS I get the following message in /var/log/ltm tmm1[29648]: 01230140:3: RST sent from *.*.*.*:443 to *.*.*.*:51570, [0x223b824:820] Internal error (ASM requested abort (plugin abort error)) However, when I remove the ASM policy from the VS navigation works fine. Has anyone had any experience getting this sort of setup working?200Views0likes2Comments