Igor_Morgado_38
Nimbostratus
NimbostratusRedundant Pair + Network Failover
Hello!
My first post:
I have two VE installations, both are using the "default" network environment:
- 1 mgmt interface in admin lan
- 1 external interface to wan lab
- 1 internal interface to internal server restricted vlan.
Hostname big1.company.com
Chassis 79ef654dbdc3
Version BIG-IP 10.1.0 Build 3341.1084 Final
UnitID 1
hostname big2.company.com
Chassis 3f0e497198f3
Version BIG-IP 10.1.0 Build 3341.1084 Final
UnitID 2
As you can notice, diff names, chassis and same version/build. The ids are ok, and both are on active/standby . I set redundancy state preference as none. Link down failover as 0.0.
ConfigSync is working fine (443 open), ips stated as expected.
Network fail over is checked in both as you can see here:
In big1 we have:
self 172.16.0.10 {
netmask 255.255.0.0
vlan internal
allow all
}
failover {
force active disable
peer mgmt addr 172.16.0.20
unicast peer big2 {
dest addr 172.16.0.20
port 1026
source addr 172.16.0.10
}
}
statemirror {
addr 172.16.0.10
peer addr 172.16.0.20
}
And in big2:
self 172.16.0.20 {
netmask 255.255.0.0
vlan internal
allow default
}
failover {
force standby disable
peer mgmt addr 172.16.0.10
unit 2
unicast peer big1 {
dest addr 172.16.0.10
port 1026
source addr 172.16.0.20
}
}
statemirror {
addr 172.16.0.20
peer addr 172.16.0.10
}
But both systems are on standby mode. BTW no filters are enabled.
If I set the preferable mode as active in unit1 and standby in unit2 it works but I want to let them as NONE. Where can the problem lies?
As is a VE i dont have the fail over cable connected, anyway in a case of failure detection both should assume the active mode, instead both on standby.
Any lights?
