31
Troubleshooting / Debug : Corrupt Datastore
« on: September 17, 2014, 02:19:28 PM »
Removed due to outdated info.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
32
General Discussion / Version 1.4.1
« on: September 13, 2014, 08:05:37 PM »
Please test thoroughly before deploying in production.
Update process: http://wanos.org/forum/index.php?topic=95
Version: 1.4.1
Minor Updates:
10-20% Throughput improvement @ 0% reduction loss.
Fixed a bug where reloading a full datastore on one side would lead to sub-optimal optimization due to syncing.
Fixed a bug introduced in 1.3.4 that caused Netflow data to not expire correctly.
Alpha Netmap support.
Version: 1.4.0
Major Update:
If 1.3.4 is running in a stable environment, it is not required to upgrade yet.
Upgrade if the current deployment is in the trial/test phase.
Changes:
Significant changes to improve multi-threading.
Shellshocker security updates, although Wanos is not vulnerable from unauthenticated sessions.
Version: 1.3.4
Minor Update:
Changed the default multithreading config.
Top Protocols sorting added.
Fixed the 64GB partition sizes in the .OVA and .VHD packages.
Version: 1.3.3:
Minor update:
QoS traffic graphs
Per Peer LAN/WAN traffic graphs
Initial process priorities
Version: 1.3.2:
Minor update:
Fixed a case where fragments caused NetFlow to crash.
Version: 1.3.1:
Is a maintenance release:
Patched a bug that dropped UDP traffic.
Added default Encrypted and Interactive bypass policies.
Enabled UDPEncap peering sample rates to be adjustable or disabled.
Version: 1.3.0:
Is a major update.
Changes:
More safety nets implemented for UDP and TCP fragments.
Fix implemented where click process froze randomly when CPU threads were >= 6. Only affected high spec devices with 8-12 cores.
Traffic policies changed to require a protocol in order to avoid accidental UDP optimization.
UDP Optimization improved.
Traffic Session Flow statistics e.g. src_ip dst_ip 90% reduction.
Top protocol/application statistics e.g. www, pop3
Live graph added to help monitoring. live ratio and live bytes saved (From LAN to WAN and vice versa)
Per Peer/Site optimization graphs e.g. possible to see stats for Site_A, Site_B and Site_C
Ratio Graphs added e.g. Ratio 2X for the last Hour, Day etc.
Ability to export graphs added.
Peering Status to see which sites are online.
Bypassed/Passthrough traffic excluded from optimization graphs.
Netflow export to external collector.
UDP Encapsulation of optimized traffic.
Core/Edge renamed to High/Low to reduce confusion. Docs will be updated as well.
wanos-show utility added.
What's next?
Update process: http://wanos.org/forum/index.php?topic=95
Version: 1.4.1
Minor Updates:
10-20% Throughput improvement @ 0% reduction loss.
Fixed a bug where reloading a full datastore on one side would lead to sub-optimal optimization due to syncing.
Fixed a bug introduced in 1.3.4 that caused Netflow data to not expire correctly.
Alpha Netmap support.
Version: 1.4.0
Major Update:
If 1.3.4 is running in a stable environment, it is not required to upgrade yet.
Upgrade if the current deployment is in the trial/test phase.
Changes:
Significant changes to improve multi-threading.
Shellshocker security updates, although Wanos is not vulnerable from unauthenticated sessions.
Version: 1.3.4
Minor Update:
Changed the default multithreading config.
Top Protocols sorting added.
Fixed the 64GB partition sizes in the .OVA and .VHD packages.
Version: 1.3.3:
Minor update:
QoS traffic graphs
Per Peer LAN/WAN traffic graphs
Initial process priorities
Version: 1.3.2:
Minor update:
Fixed a case where fragments caused NetFlow to crash.
Version: 1.3.1:
Is a maintenance release:
Patched a bug that dropped UDP traffic.
Added default Encrypted and Interactive bypass policies.
Enabled UDPEncap peering sample rates to be adjustable or disabled.
Version: 1.3.0:
Is a major update.
Changes:
More safety nets implemented for UDP and TCP fragments.
Fix implemented where click process froze randomly when CPU threads were >= 6. Only affected high spec devices with 8-12 cores.
Traffic policies changed to require a protocol in order to avoid accidental UDP optimization.
UDP Optimization improved.
Traffic Session Flow statistics e.g. src_ip dst_ip 90% reduction.
Top protocol/application statistics e.g. www, pop3
Live graph added to help monitoring. live ratio and live bytes saved (From LAN to WAN and vice versa)
Per Peer/Site optimization graphs e.g. possible to see stats for Site_A, Site_B and Site_C
Ratio Graphs added e.g. Ratio 2X for the last Hour, Day etc.
Ability to export graphs added.
Peering Status to see which sites are online.
Bypassed/Passthrough traffic excluded from optimization graphs.
Netflow export to external collector.
UDP Encapsulation of optimized traffic.
Core/Edge renamed to High/Low to reduce confusion. Docs will be updated as well.
wanos-show utility added.
What's next?
33
Installation / Update Process
« on: September 13, 2014, 04:25:21 PM »
This post may be outdated. Please refer to the Update Process Documentation
v.2.6.2 or later update to 3.2.3
It is recommended to create a snapshot vm/img if it's in production in case things go wrong.
Update will create a restore point, but don't count on it.
Update will retain basic settings e.g. IP, Gateway, Datastore, SSH, Hostname, Deployment mode, Virt_lan0, MAC wan0 & lan0 mappings.
Traffic policies, MultiSite, PortObjects and Groupobjects are migrated.
Some settings may be set to defaults.
Most stats will reset.
It is recommended to add a default bypass rule during the update.
Update is not backward compatible, hence please update all devices.
It is strongly recommended to test the upgrade in a test lab offline first a couple of times.
Howto:
If the device has access to the internet:
wget http://wanos.org/updateinfo/update-3.2.3.sh
wget http://wanos.org/updateinfo/update-3.2.3.tar.gz
bash update-3.2.3.sh update
Update script works on:
2.6.2 and later
Please leave a reply here if there is a problem with the upgrade.
And remember versions are not backwards compatible. Update all sites.
v.2.6.2 or later update to 3.2.3
It is recommended to create a snapshot vm/img if it's in production in case things go wrong.
Update will create a restore point, but don't count on it.
Update will retain basic settings e.g. IP, Gateway, Datastore, SSH, Hostname, Deployment mode, Virt_lan0, MAC wan0 & lan0 mappings.
Traffic policies, MultiSite, PortObjects and Groupobjects are migrated.
Some settings may be set to defaults.
Most stats will reset.
It is recommended to add a default bypass rule during the update.
Update is not backward compatible, hence please update all devices.
It is strongly recommended to test the upgrade in a test lab offline first a couple of times.
Howto:
If the device has access to the internet:
wget http://wanos.org/updateinfo/update-3.2.3.sh
wget http://wanos.org/updateinfo/update-3.2.3.tar.gz
bash update-3.2.3.sh update
Update script works on:
2.6.2 and later
Please leave a reply here if there is a problem with the upgrade.
And remember versions are not backwards compatible. Update all sites.
34
General Discussion / 1.2.2 Release
« on: July 04, 2014, 01:54:04 PM »
Note: versions are not backwards compatible
1.2.2
Is a maintenance update.
Additional datastore and traffic integrity checks.
Beta Core-Core capability. Please feedback any issues with this.
Bidirectional stats updated.
MultiSite numbering bug fixed.
To upgrade from 1.2.1 to 1.2.2 follow this guide:
1.2.1
Is available for download at http://wanos.co/wan-optimization/download/. This is a raw disk image, which can be written to HDD/USB/Compact Flash/Mounted in a virtual environment or converted to another virtual disk format. The OVA package is the recommended image for virtual environments and available at http://wanos.co/wan-optimization/download/.
Changes:
Maximum Express datastore has increased to 60GB. Min disk space required is 64GB.
Minimum memory required increased to 2 GB.
Major improvements in the deduplication engine.
Performance improvement in the compression engine.
Minor GUI improvements.
Beta UDP Optimization available.
Beta UDP Encapsulation available (firewalls and PAT).
Multiple Cores per edge supported via MultiSite config.
Service restart times have been reduced to <1 second.
Peer Discovery. This also enable keep alive and timeouts, which improves auto bypass when peers go down. Hold time is configurable in seconds.
Bidirectional Optimization. Edges now optimize Edge<->Core and Edge<->Edge.
Unlimited Edge<->Edge optimization enables very large optimized networks. E.g. its theoretically possible to have 1000 fully meshed Edge<->Edge sites.
Unless stated all Wanos versions are not backwards compatible.
1.2.2
Is a maintenance update.
Additional datastore and traffic integrity checks.
Beta Core-Core capability. Please feedback any issues with this.
Bidirectional stats updated.
MultiSite numbering bug fixed.
To upgrade from 1.2.1 to 1.2.2 follow this guide:
1.2.1
Is available for download at http://wanos.co/wan-optimization/download/. This is a raw disk image, which can be written to HDD/USB/Compact Flash/Mounted in a virtual environment or converted to another virtual disk format. The OVA package is the recommended image for virtual environments and available at http://wanos.co/wan-optimization/download/.
Changes:
Maximum Express datastore has increased to 60GB. Min disk space required is 64GB.
Minimum memory required increased to 2 GB.
Major improvements in the deduplication engine.
Performance improvement in the compression engine.
Minor GUI improvements.
Beta UDP Optimization available.
Beta UDP Encapsulation available (firewalls and PAT).
Multiple Cores per edge supported via MultiSite config.
Service restart times have been reduced to <1 second.
Peer Discovery. This also enable keep alive and timeouts, which improves auto bypass when peers go down. Hold time is configurable in seconds.
Bidirectional Optimization. Edges now optimize Edge<->Core and Edge<->Edge.
Unlimited Edge<->Edge optimization enables very large optimized networks. E.g. its theoretically possible to have 1000 fully meshed Edge<->Edge sites.
Unless stated all Wanos versions are not backwards compatible.
35
FAQ / How to help the Wanos project
« on: June 18, 2014, 10:07:00 PM »
How to help the project is a frequently asked question and a great question, thanks for asking. Any help is incredibly valuable and highly appreciated.
Wan Optimization enthusiasts that are interested in contributing and making the technology more accessible are encouraged to get in touch.
How to help?
The easiest way to help is to simply start using wanos. Deploy in a network and let us know what the most essential next feature is.
Tell a friend, colleague, anyone that can benefit from wan optimization.
Wanos working well in your network scenario? Great, post the results.
Document any questions and answers that are not yet covered.
Help improve the documentation via feedback or editing the wiki: http://wanos.org/wiki/
Found a way to deploy the solution that has not yet been documented? Fantastic, let us hear about it and someone might benefit from this contribution.
More options?
Developers, Linux and Networking skills are very valuable to the effort. Please get in touch and you will most likely find an open door policy.
Wan Optimization enthusiasts that are interested in contributing and making the technology more accessible are encouraged to get in touch.
How to help?
The easiest way to help is to simply start using wanos. Deploy in a network and let us know what the most essential next feature is.
Tell a friend, colleague, anyone that can benefit from wan optimization.
Wanos working well in your network scenario? Great, post the results.
Document any questions and answers that are not yet covered.
Help improve the documentation via feedback or editing the wiki: http://wanos.org/wiki/
Found a way to deploy the solution that has not yet been documented? Fantastic, let us hear about it and someone might benefit from this contribution.
More options?
Developers, Linux and Networking skills are very valuable to the effort. Please get in touch and you will most likely find an open door policy.
36
Installation / Installation Guides
« on: May 26, 2014, 07:05:13 PM »
Note: Please see full configuration guide at: Admin Guide
The Quick Configuration Guide be found at: Quick Config Guide
If you have any trouble with any of the steps, please create a new forum post and together we will figure it out.
The Quick Configuration Guide be found at: Quick Config Guide
If you have any trouble with any of the steps, please create a new forum post and together we will figure it out.
37
Features / Feature Requests
« on: May 07, 2014, 02:27:51 PM »
Please vote for the most important feature you would like to see added
Wishlist:
Central Reporting/Manager
HTTPS/SSL Decrypt
Encrypted Exchange Optimization
Wishlist:
Central Reporting/Manager
HTTPS/SSL Decrypt
Encrypted Exchange Optimization
38
General Discussion / wanos.dk
« on: May 04, 2014, 12:00:11 PM »
Special thanks to Veloci Group for hosting a Danish translation at http://wanos.dk
Veloci contact info can be found at www .veloci-group. com
VELOCIgroup kan også hjælpe med at implementere wanos WAN optimering korrekt i din virksomhed, så den bedste udnyttelse opnås.
Veloci contact info can be found at www .veloci-group. com
VELOCIgroup kan også hjælpe med at implementere wanos WAN optimering korrekt i din virksomhed, så den bedste udnyttelse opnås.
40
General Discussion / 0.1.8 Release
« on: May 02, 2014, 01:36:09 AM »
Edit: Outdated info
Feedback most welcome. Muchas gracias
Feedback most welcome. Muchas gracias
41
FAQ / ESX - Traffic is not flowing through the bridge
« on: April 16, 2014, 03:54:06 PM »
ESX - The appliance seems to have booted up fine, but traffic is not flowing through the bridge. Lan0 and Wan0 are connected and cabled correctly.
Most likely, promiscuous mode needs to be enabled for each interface.
Most likely, promiscuous mode needs to be enabled for each interface.
42
Installation / Vmware ESX single physical NIC
« on: April 07, 2014, 07:32:51 PM »
Although it is recommended to dedicate separate physical NIC's for lan0 and wan0, in certain cases only a single NIC might be available for Wanos and worth the compromise.
Things to consider when only one physical NIC is available:
1) Performance compromise, traffic will traverse the same interface at least twice
2) The bridge appliance will bridge traffic from the lan0 to the wan0 and vice versa. Bridge loops can still occur.
3) To split the single NIC traffic into two virtual interfaces, two VLAN's are required, the inside lan0 VLAN and the outside wan0 VLAN.
4) Promiscuous mode needs to be enabled on portgroup level and not vswitch level. In other words promiscuous is disabled (reject) for the vswitch and enabled for the outside and inside VLAN's.
5) Vmware is not native VLAN aware. Use normal VLAN's to ensure the traffic flow is predictable.
Caveats:
1) On a Cisco switch and possibly other spanning-tree enabled switches, 'spanning-tree bpdufilter enable' is required on the trunk interface between the host NIC and the switch.
2) The switch can't also be the gateway for the inside lan0 VLAN if it's a Layer3 switch. On the switches tested, frames were implicitly dropped on the trunk if the destination MAC was also the one of the switch local MAC addresses. This is either a feature or a bug, either way take note that the gateway needs to be another L3 switch, router or firewall.
Example:
Switch config:
interface FastEthernet0/5
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 30,101
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
Credit goes to spoonzw
Things to consider when only one physical NIC is available:
1) Performance compromise, traffic will traverse the same interface at least twice
2) The bridge appliance will bridge traffic from the lan0 to the wan0 and vice versa. Bridge loops can still occur.
3) To split the single NIC traffic into two virtual interfaces, two VLAN's are required, the inside lan0 VLAN and the outside wan0 VLAN.
4) Promiscuous mode needs to be enabled on portgroup level and not vswitch level. In other words promiscuous is disabled (reject) for the vswitch and enabled for the outside and inside VLAN's.
5) Vmware is not native VLAN aware. Use normal VLAN's to ensure the traffic flow is predictable.
Caveats:
1) On a Cisco switch and possibly other spanning-tree enabled switches, 'spanning-tree bpdufilter enable' is required on the trunk interface between the host NIC and the switch.
2) The switch can't also be the gateway for the inside lan0 VLAN if it's a Layer3 switch. On the switches tested, frames were implicitly dropped on the trunk if the destination MAC was also the one of the switch local MAC addresses. This is either a feature or a bug, either way take note that the gateway needs to be another L3 switch, router or firewall.
Example:
Switch config:
interface FastEthernet0/5
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 30,101
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
Credit goes to spoonzw
43
FAQ / Minimum Requirements
« on: April 05, 2014, 12:42:40 PM »
Minimum Hardware Requirements:
Point to Point:
2 GB memory
13 GB Storage (HDD, USB or Compact Flash)
1-2 Ethernet Interfaces
Multisite:
4Gb memory
64 GB Storage (HDD, USB or Compact Flash)
1-2 Ethernet Interfaces
A minimum of 2x CPU cores is recommended, unless the link size is less than 1 Mbps.
It is recommended to use two physical interfaces in a production network. This provides the best performance and simplifies the network config and cabling. It is possible to use a single physical interface in the virtual networks. In this case two VLANs are required and promiscuous mode enabled on the portgroup level via vSphere.
Point to Point:
2 GB memory
13 GB Storage (HDD, USB or Compact Flash)
1-2 Ethernet Interfaces
Multisite:
4Gb memory
64 GB Storage (HDD, USB or Compact Flash)
1-2 Ethernet Interfaces
A minimum of 2x CPU cores is recommended, unless the link size is less than 1 Mbps.
It is recommended to use two physical interfaces in a production network. This provides the best performance and simplifies the network config and cabling. It is possible to use a single physical interface in the virtual networks. In this case two VLANs are required and promiscuous mode enabled on the portgroup level via vSphere.
44
Configuration / By-pass rules required on which end?
« on: April 04, 2014, 10:11:35 AM »
Traffic policy rules apply to traffic going out on wan0.
To bypass traffic from a Server going towards a remote site, the rule would normally be applied on the server side device.
To bypass upstream traffic from the remote site going towards the server, the rule would be applied on the user side device.
To bypass traffic from a Server going towards a remote site, the rule would normally be applied on the server side device.
To bypass upstream traffic from the remote site going towards the server, the rule would be applied on the user side device.
45
FAQ / High Availability - Bypass
« on: March 10, 2014, 01:46:41 PM »
How can high availability be achieved to avoid total loss of network traffic flow?
1) Bypass NIC's. Wanos Appliance 200 has a built-in bypass NIC.
2) Since Wanos is a bridge, another easiest method to create high availability is to run a second backup network cable along side the Wanos bridge appliance. Convergence happens within a few milliseconds and the switch-over is unlikely to be detected by a continuous ping. Unlike leading vendor fail-over scenarios, traffic sessions are not reset during the switch-over and users are unaware of the network change.
3) With out of path deployment, IP SLA can be used to track the status of the optimization device and remove the PBR rule when required.
4) External bypass switches. This is an option if they are gathering dust.
1) Bypass NIC's. Wanos Appliance 200 has a built-in bypass NIC.
2) Since Wanos is a bridge, another easiest method to create high availability is to run a second backup network cable along side the Wanos bridge appliance. Convergence happens within a few milliseconds and the switch-over is unlikely to be detected by a continuous ping. Unlike leading vendor fail-over scenarios, traffic sessions are not reset during the switch-over and users are unaware of the network change.
3) With out of path deployment, IP SLA can be used to track the status of the optimization device and remove the PBR rule when required.
4) External bypass switches. This is an option if they are gathering dust.