Skip to main content

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization.

In the era of cloud computing, servers are virtualized and used in Data Centers.

We are facing a lot of problem when we virtualized our Servers,

1) Routing and Switching Problem

Routing become the issue when we create Virtual Switch and VLANs according to production requirement.
Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end.

၂) Firewall Services

Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements.
New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management.

၃) Load Balancing

Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures.
Once a tenant reaches their maximum capacity, it can be difficult to scale.

၄) VPN Services

Your company supports a single hardware VPN solution for multiple teanants currently and once a tenant reaches their maximum capacity, it is difficutl to scale.

These facts are just fews things that we will face when we use server virtualization without network virtualization.
Server Virtualization Team need to wait Network Team to make changes to meet with updates.
Can you imagine how difficult if it is at Data Center Network without Network Virutalization?

That's why we need network virtualization solutions.

Anyway, this post is just overview for network virtualization and yes I might missed a lot of things.

Reference: VMware Network Virtualization Fundamentals.

Have a good time.
(Be knowledgeable, pass it on then)


Popular posts from this blog

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a