Show Posts
571
General Discussion / Re: 1.2.1 Release
« on: July 07, 2014, 12:17:44 AM »
Hi Peter,
That is correct, the design was to provide a solution for the majority of small companies with a Head Office and three or four remote offices. That is really where wanos was initially aimed at. If we look at the traffic patterns of these companies, 80%-90% of the time the problem area is getting data to the remote users. Since then larger companies have started using Wanos in more complex networks and bidirectional optimization is a nice to have in case to reduce traffic in the upstream direction as well. Then in even larger and more complex networks Core-Core is also a bonus between Head Offices or a DR site.
A dummy site can be used to "engineer" a work around, but in fact a Core is not even required. All sites can be Edges and this could be say 100 fully meshed sites. There is no design requirement for Core-Core, it is merely a design option to provide better reduction. Cores are important in the network since they are configured to provide the best reduction (Within 10% of Silver-Peak in realistic cold tests). In your scenario an option would be to make one Head Office an Edge: HO1(core) -> HO2(edge). Optionally also configure all sites in MultiSite on each device to ensure the peer discovery / auto detection / fail-over continues to work on each individual site level.
A lot of work has gone into the dedup engine over the last few months and Core-Core is now undergoing some final testing before the release. The alpha results are very good and about ready for beta testing. Then if all four sites have enough resources, they can all be configured as cores. For larger networks it would make sense to use a few cores and the rest edges.
Update: Core-Core is ready for beta testing
That is correct, the design was to provide a solution for the majority of small companies with a Head Office and three or four remote offices. That is really where wanos was initially aimed at. If we look at the traffic patterns of these companies, 80%-90% of the time the problem area is getting data to the remote users. Since then larger companies have started using Wanos in more complex networks and bidirectional optimization is a nice to have in case to reduce traffic in the upstream direction as well. Then in even larger and more complex networks Core-Core is also a bonus between Head Offices or a DR site.
A dummy site can be used to "engineer" a work around, but in fact a Core is not even required. All sites can be Edges and this could be say 100 fully meshed sites. There is no design requirement for Core-Core, it is merely a design option to provide better reduction. Cores are important in the network since they are configured to provide the best reduction (Within 10% of Silver-Peak in realistic cold tests). In your scenario an option would be to make one Head Office an Edge: HO1(core) -> HO2(edge). Optionally also configure all sites in MultiSite on each device to ensure the peer discovery / auto detection / fail-over continues to work on each individual site level.
A lot of work has gone into the dedup engine over the last few months and Core-Core is now undergoing some final testing before the release. The alpha results are very good and about ready for beta testing. Then if all four sites have enough resources, they can all be configured as cores. For larger networks it would make sense to use a few cores and the rest edges.
Update: Core-Core is ready for beta testing