For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

TomSu_93471's avatar
TomSu_93471
Icon for Nimbostratus rankNimbostratus
Jan 30, 2012

Splitting 2 production Viprion clusters(active-stdby) into two..

Hi,   I need to split 2 production Viprion clusters (redundant pair -Active/Stdby) into two standalone clusters.   Since this is Active-Stdby config I suppose I could just force offline the stdb...
basic
getting started
new to f5
nitass's avatar
nitass
Icon for Employee rankEmployee
Jan 30, 2012
i did test on my pair. nothing was restarted but i noticed sod went offline and came back to active in ltm log. it happened in a second. anyway, i do not have much traffic, so i am not sure if it affects. let us see if somebody here has done before. 

[root@B1600-R66-S17:Active] config  tail -f /var/log/ltm
(1) Jan 30 07:23:16 local/B1600-R66-S17 notice sod[3422]: 010c003e:5: Offline
Jan 30 07:23:16 local/B1600-R66-S17 notice mcpd[3453]: 01070413:5: Updated existing subscriber tmrouted with new filter class 800c000.
(2) Jan 30 07:23:16 local/B1600-R66-S17 notice sod[3422]: 010c0051:5: Active (not redundant)
Jan 30 07:23:16 local/B1600-R66-S17 notice mcpd[3453]: 01070413:5: Updated existing subscriber tmrouted with new filter class 4800d210.
Jan 30 07:23:16 local/B1600-R66-S17 notice mcpd[3453]: 01070410:5: Removed subscription with subscriber id bgpd
Jan 30 07:23:20 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 1.1.1.19 (00:01:d7:b4:60:44) on vlan 3422
Jan 30 07:23:21 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 200.200.200.19 (00:01:d7:b4:60:43) on vlan 423
Jan 30 07:23:21 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 2.2.2.19 (00:01:d7:b4:60:45) on vlan 3421
Jan 30 07:23:21 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 1.1.1.19 (00:01:d7:b4:60:44) on vlan 3422
Jan 30 07:23:22 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 200.200.200.19 (00:01:d7:b4:60:43) on vlan 423
Jan 30 07:23:22 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 2.2.2.19 (00:01:d7:b4:60:45) on vlan 3421
Jan 30 07:23:22 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 1.1.1.19 (00:01:d7:b4:60:44) on vlan 3422
Jan 30 07:23:23 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 200.200.200.19 (00:01:d7:b4:60:43) on vlan 423
Jan 30 07:23:23 local/tmm warning tmm[5113]: 01190004:4: address conflict detected for 2.2.2.19 (00:01:d7:b4:60:45) on vlan 3421
Jan 30 07:23:23 local/tmm info tmm[5113]: 01190004:6: Per-invocation log rate exceeded; throttling.