F5 Sites
  • F5.com
  • LearnF5
  • NGINX
  • MyF5
  • Partner Central
Contact
  • Under Attack?
  • F5 Support
  • DevCentral Support
  • F5 Sales
  • NGINX Sales
  • F5 Professional Services
Skip to contentBrand Logo
Forums
CrowdSRC
Articles
Groups
EventsSuggestionsHow Do I...?
RegisterSign In
  1. DevCentral
  2. Articles
  3. Technical Articles

LTM: Interface Failsafe

Nathan McMahon and Kirk Bauer bring us another slick solution for a couple of common requirements in high performance environments: To fail over immediately when a single physical network connection ...
Published Mar 05, 2008
Version 1.0
BIG-IP Access Policy Manager (APM)
news
security
tech tip
Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
Joined September 25, 2004
View Profile
Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
Joined September 25, 2004
View Profile
gavincheng_1049's avatar
gavincheng_1049
Icon for Nimbostratus rankNimbostratus
Apr 02, 2010
Hello,all.

 

 

I used to two virtual BIGIP that HA Lab, but fail,

 

 

the two BIGIP version is "BIG-IP 10.1.0 Build 3341.1084 Final "

 

 

BIGIP_1-------(HA mode Network Failover )--------BIGIP_2

 

 

HA mode Active-active

 

 

High Availability : Redundancy, unit 1 of BIGIP_1 device,unit 2 of BIGIP_2 device.

 

 

BIGIP_1: ConfigSync Peer Address set 198.18.19.252 ,BIGIP_1 management ip address is 192.168.0.105

 

BIGIP_2: ConfigSync Peer Address set 198.18.19.251 ,BIGIP_2 management ip address is 192.168.0.106

 

Detect ConfigSync Status enable

 

 

 

BIGIP_1: failover1|198.18.19.251|198.18.19.252|1026

 

failover2|192.168.0.105|192.168.0.106|1026

 

 

BIGIP_2: failover1|198.18.19.252|198.18.19.251|1026

 

failover2|192.168.0.106|192.168.0.105|1026

 

 

network mirroring:

 

BIGIP_1:Self _198.18.19.251,remote_198.18.19.252

 

BIGIP_2:Self _198.18.19.252,remote_198.18.19.251

 

 

 

High Availability-Fail_self--gateway:

 

 

add pool : failover_pool, pool member only include 198.18.19.1(default gateway),health moniter select "gateway_icmp"

 

 

ok, them can Synchronize configuration,but not switch over ,

 

 

down BIGIP_2 , BIGIP_1 can't take over BIGIP_1 's traffic .

 

 

b unit command on BIGIP_1 , display unit 1 :

 

[root@BIGIP_1:Active] config b unit

 

UNITS 1

 

 

reboot BIGIP_2, b failover standby command on BIGIP_2,and b unit command on BIGIP_1,dispaly:

 

 

[root@BIGIP_1:Active] config b unit

 

UNITS 1 and 2

 

 

but shutdown BIGIP_2,

 

 

[root@BIGIP:Active_] config b unit

 

UNITS 1 and 2

 

 

why ? ?

 

 

more /var/log/ltm

 

 

Apr 2 23:04:07 local/BIGIP notice sod[2598]: 010c0044:5: Command: go failback BIGpipe.

 

Apr 2 23:04:25 local/BIGIP notice sod[2598]: 010c0020:5: Unit 1 and 2

 

Apr 2 23:05:00 local/BIGIP notice sod[2598]: 010c0020:5: Unit 1

 

Apr 2 23:05:03 local/BIGIP notice mcpd[2596]: 01070640:5: Node 198.18.19.252 monitor status down.

 

Apr 2 23:05:03 local/tmm err tmm[3626]: 01010028:3: No members available for pool failover_pool

 

Apr 2 23:05:05 local/BIGIP notice mcpd[2596]: 01070638:5: Pool member 198.18.19.252:0 monitor status down.

 

 

 

how kill this problem ? HA still does not work, switch to complete the normal process of proposed solutions or have you ideas?

 

 

Thanks !

ABOUT DEVCENTRAL

DevCentral NewsTechnical ForumTechnical ArticlesTechnical CrowdSRCCommunity GuidelinesDevCentral EULAGet a Developer Lab LicenseBecome a DevCentral MVP

RESOURCES

Product DocumentationWhite PapersGlossaryCustomer StoriesWebinarsFree Online CoursesF5 CertificationLearnF5 Training

SUPPORT

Manage SubscriptionsProfessional ServicesProfessional ServicesCreate a Service RequestSoftware DownloadsSupport Portal

PARTNERS

Find a Reseller PartnerTechnology AlliancesBecome an F5 PartnerLogin to Partner Central

F5 logo©2024 F5, Inc. All rights reserved.
TrademarksPoliciesPrivacyCalifornia PrivacyDo Not Sell My Personal Information