Forum Discussion
Device Shows Peer (synced) as "Offline"
I have sync-failover configured among three devices. They are all in sync but one of them shows the peers as "Offline". What could the problem be? Thank you.
8 Replies
- Tosin_Omojola
Altostratus
This is a follow-up on the question above. All the three devices are in sync but all are also ACTIVE at the same time. I want only one to be active while the other two are in STANDBY mode. Now, the Failover sequence in the traffice-group for all three devices are same i.e D1-D2-D3. Is that a correct sequence? Should they all have the same failover sequence in the traffic group? The "Next-Active-Device" status in each traffic group also indicates (Initializing/Not synced). Whereas, they all share the global status of IN-SYNC??? Thank you - PeteWhite
Employee
which software version are you using? Have you pinged between the devices? Are the HA Self-IPs set as Allow Default? Is the HA config set correctly? - Tosin_Omojola
Altostratus
Yes, Pete. The HA Self-IPs are all set to Allow Default (what effect might that have on the situation?) The configs are set correctly. All the three devices see each other as peer and they all are in the same device group. They show their sync status as "in sync". Can they show "in-sync" if they are not all interconnected? Be sure to follow the Device Service Clustering (DSC) troubleshooting guide. There are a few reasons this happens, usually fairly easy to resolve.
Things you will want to check include making sure that in the Device list, that each device has the information for each other device. If a device is not showing up correctly, you will want to start there. You must have the device certificates for each unit imported into the sister units. The Device Group must be configured identically on all devices.
SOL13946: Troubleshooting ConfigSync and device service clustering issues (11.x) https://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.html
If all else fails, you may want to start at the beginning and reset the peering relationship between all of the units.
Manual: BIG-IP Device Service Clustering: Administration https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-device-service-clustering-admin-11-5-0.html
Came across this guide directed at ScaleN configurations. Maybe it will help?
- Mgullia_176222
Nimbostratus
Hi, i have the same issue on viprion 11.6 HF4 Have you solved the problem? What was the solution?? Thank you.
M.G.
- Tosin_Omojola
Altostratus
It's been a long time and I can't remember what solution exactly solved the problem because I usually try so many things in my bid to troubleshoot. However, there are standard procedures to follow. Please check this guide:
https://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.html
and this too
https://support.f5.com/kb/en-us/solutions/public/7000/000/sol7024.html
If the DSC config steps are followed strictly, it should be fine. Watch out specifically for the DEVICE GROUP NAME. It must be the same on all the cluster members. Watchout also for the ConfigSync address/interface and the HA vlan set ( It is "internal" vlan by default if you choose to use existing vlan and not create a separate HA vlan).
Goodluck!
- Mgullia_176222
Nimbostratus
I've solve this just creating a new traffic-group. I thik it is a bug.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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