SDDC SDN Vmware VMware Horizon Vmware Vcloud VMware vSAN VMware Workstation 15

Review of F5 Architecture for VMware NSX – Part I

The software-based datacenter architecture approach, or SDDC, is capable of meeting the needs of increasing agility of the preparation service, facilitating the implementation process and improving the economic conditions of the datacenter.

Most organizations want to increase competitiveness, reduce time to market, and accelerate their business. On the other hand, managing traditional network architectures is very complex and costly and unable to meet the expected expectations. These networks are very static and slow to respond to dynamic environments created by changing datacenter traffic patterns and rapidly increasing numbers of users, devices and applications. In addition, software designers and executives often feel that the network is preventing them from doing things properly, rather than helping them. With this interpretation of networking organizations, in order to increase agility to meet business needs, they need a change in network architecture.

The change in architecture can dramatically reduce Lead Time (the amount of delay between start time and process execution) for new applications and services, and eliminate Down Time caused by unexpected increases in workloads, as well as speed recovery processes. forgives. This change does not focus on servers, connection between them, security, switching, routing or load balancing . This solution combines all the elements of a data center network and an Application Delivery architecture . To meet the expectations of today's business world, helping organizations change their data center economics and increasing program implementation agility, there is a pressing need for a software-based or SDDC architecture approach.

Challenges of not using SDDC

The versatility of datacenter agility helps organizations maintain their competitiveness and maximize resource efficiency. Comprehensive capabilities should include server virtualization, storage, and networking. Static, silo-based, and hardware-based datacenter, abbreviated as HDDC, prevents applications from responding. In other words, SDDC architecture is better suited to meet the needs of today's world, as it avoids unnecessary disruptions to existing services or delays in implementing new services.

Check presentation time

Enterprise applications do not run in a vacuum, and improvements to server implementation dramatically improve application implementation time. But applications, beyond the virtual components of the server infrastructure, require both communication services such as Switching and Routing as well as application services. These include Local and Global Load Balancing as well as encryption, optimization, acceleration, access and security services. Recent advances in network virtualization and its management tools can reduce the time it takes to implement network and application services. The network design and implementation facilitation under SDDC architecture enables organizations to more rapidly change network configuration and behavior.


F5 architecture review for VMware NSX

Preparing application services will not take weeks.

It's time to change

The variety of Application Delivery requirements and widespread fluctuations in Throughput needs have made it increasingly difficult to plan for data center growth. This situation is exacerbated by the evolution of Internet-based technologies and the increasing demand for these technologies. As a result, the need to speed up IT has never been the same as it is now, not only for the implementation of new services, but also for the services that need to be constantly changing.

Unforeseen needs for data center resources can be the result of successful marketing or sales campaigns, unforeseen company growth or even cyberattacks. In such cases, given today's pressing need for technology, data center speed and the ability to respond quickly to business continuity and brand protection are crucial.

SDN shortcomings

While Software-Defined Networking, abbreviated as SDN, with most of today's SDN solutions, they are not able to provide sufficient benefits to customers and application layer challenges. SDN network-centric challenges commonly known as Network Centric (layers 2-4) but focuses largely driven challenges program or the Application Centric does not consider (layers 4-7). Since the network is meant to support the applications that use it, any new network architecture must meet the challenges of the network without overriding the Application layer.

Specific areas where the current SDN architecture is not very compatible with the Application layer requirements include:

  • Stateful Networks : Packet transfer decisions in the network layer do not contain much status information. However, application layer technologies maintain an overview of the status of application layer interactions to manage data exchange and application behavior between those endpoints.
  • Decisions based on messages ( Message-Based ) rather than packet-based ( Packet-Based ) . SDN operates on "Flow" (such as TCP connection) However, application layer decisions are often based on HTTP messages and a single stream, and may contain several messages. As a result, most SDN architectures are not suitable for messaging-based applications.
  • Layer 4 to 7 content . Many of the challenges cannot be answered by focusing only on layer 2 and layer data. Functions such as authentication, access, measurement, command, message forwarding, cross-origin resource sharing, data protection, performance, flexibility, crash isolation, SSL offloading and many more that require application-based logic, status, and decisions. Cannot be answered in this way.
  • Correct product implementation . Due to SDN design constraints, current products have not been developed to meet application-based requirements (layers 4 to 7), limiting computing power, addressing tables, and updating updates.

When evaluating a new architectural paradigm such as the Agile Datacenter network, it is very important to consider how the network will be affected by the applications and the services available.


Review of F5 Architecture for VMware NSX – Part I

Checking F5 Architecture for VMware NSX – Part II

Sabir Hussain Soomro
About Sabir Hussain Experienced IT Specialist with a history of working in the information technology and services industry. Skilled in VMware ESX, Domain Name System (DNS), DHCP, VoIP, Water Backup Solutions, Adobe Connect, Servers, and Data Center. but quickly found a large following of readers and subscribers. Connect on: Google + or Feel free to network via Twitter.@VMGate110

Leave a Reply

Your email address will not be published. Required fields are marked *