Posts

Showing posts with the label OSPF

Deep Dive on DMPO and its Performance Features (available and missing) Part 1

Image
 In the last year I got quite deep insight into ther vendors SD-WAN implementation and also have seen what various vendors are critizising about the VMware DMPO features. Also there are a lot of misconceptions on the market around some of these features. So let´s try and evaluate and look a little bit deeper into typical performance features and the VMware implementation of them Features discussed in this Blog (Part 1) Per Packet Load Balancing Forward Error Correction (FEC) Packet Replication Latency Remediation The following Features will be discussed in Part 2 of my blog TCP Optimization Techniques Dejitter Buffering SAAS Application Monitoring   Per Packet Load Balancing  Unfortunately this term can be quite easily misinterpreted, when you Google for the term and get the following result:  This behaviour (often criticized by other vendors about VMware) as described above would only work quite well when you have very similar or equal connections. If for example 2 ...

EDGEs OSPF redundancy and filtering troubles

Image
  OSPF v2 ( IPv4) is supported for LAN and WAN interfaces. I recently defined a redundant OSPF LAN connection between an VMware 6X0 edge and a Sophos UTM 9 Firewall  The Edge forwards Overlay Routes to LAN as OSPF E1 routes, thus playing an ASBR (Autonomous System Boundary Router) within the OSPF area and domain. On the UTM Firewall static routes and connected routes are advertised via OSPF E2, again playing the role of an ASBR. During testing various features for Internet Backhaul we also played with advertising a default route into the Velocoud Overlay.  In order to prevent the default route from being advertised via OSPF to the UTM FW we entered a filter on "Outbound Route Advertisement" on both SFP interfaces. But on one of the connecting interfaces we forgot to check the "Exact Match" field which resulted in a Outbound filter of DENY ANY instead of the planned DENY DEFAULT ROUTE. The result was not what we expected: When testing we found out that routes adveri...