- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- How to add a second Sync interface in VSX
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to add a second Sync interface in VSX
Hi:
We're looking for redundancy at Sync level and, therefore, to add a second Sync interface in our VSX enviroment (R81.10 JHF169). I was reading the VSX Admin Guide but didn't find the proccess to do it. Does someone know how to achieve it?
Thanks
Regards
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You will need to create a bond (which requires at least one unused interface), then you will need to change sync to use the bond instead of whatever interface it's using now. Once you have the bond and the members are using it for sync, you can add the old interface you used for sync to the bond. Redundancy is then handled by the bond configuration, which is local to each member.
Note that sync traffic is always from the same port, IP, and MAC to the same port, IP, and MAC. LACP will always hash it to the same link, regardless of configuration. Round-robin transmit link selection is generally best for this, as it ensures all of the available sync links are actually tested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In general the process to change the Sync interface is outlined by sk36977.
As Bob has recommended definitely a Bond is the way to go.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You will need to create a bond (which requires at least one unused interface), then you will need to change sync to use the bond instead of whatever interface it's using now. Once you have the bond and the members are using it for sync, you can add the old interface you used for sync to the bond. Redundancy is then handled by the bond configuration, which is local to each member.
Note that sync traffic is always from the same port, IP, and MAC to the same port, IP, and MAC. LACP will always hash it to the same link, regardless of configuration. Round-robin transmit link selection is generally best for this, as it ensures all of the available sync links are actually tested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In general the process to change the Sync interface is outlined by sk36977.
As Bob has recommended definitely a Bond is the way to go.
