VMware NSX and VMware SDN | IT NETWORKS

-
programming no copyright photo

VMware NSX and VMware SDN



VMware NSX is the VMware SDN network security and virtualization platform that emerged from VMware in 2012. This acquisition launched VMware in the world of software-defined networks (SDN) and network function virtualization (NFV).

The solution decouples the network functions of the physical devices, analogously to the decoupling of virtual servers (VMs) from physical servers.

To decouple the new virtual network from the traditional physical network, NSX recreates traditional network constructions in virtual space: these constructions include ports, switches, routers, firewalls, and other required components.

In the past, It was possible to see and touch the switch port to which a server is connected, but now, this is no longer possible.

Basically, they still exist with NSX, but it is no longer possible to touch them physically. It is for this reason, the virtual network is sometimes harder to conceptualize.

There are two different product editions of NSX:

NSX for vSphere and NSX for Multi-Hypervisor (MH).

 NSX for vSphere is the perfect solution for VMware environments, while NSX for MH is designed to integrate into cloud environments that take advantage of open standards like OpenStack.

VMware NSX for vSphere

The recent version of VMware NSX is designed specifically for vSphere environments,or NSX for vSphere.

NSX for vSphere will be implemented 90% of the time, as it has native integration with other VMware platforms, such as vCenter and vCloud for Automation Center (vCAC).



Also NSX integrates with third parties, such as Palo Alto Networks and F5.


Next-generation NVP product represents NSX second edition, which is initially from NICIRA.

NSX for MV does not have a native integration with vCenter because it was created specifically from scratch to support any cloud environment, such as OpenStack and CloudStack.


While there is no native integration with vCenter, in fact, it is still compatible with vSphere, KVM and XEN hypervisors, although it contains fewer functions than NSX for vSphere, from a network perspective.

Learn more:


In Security

Endpoint introduction :
https://itnetworks2020.blogspot.com/2019/10/endpoints-introduction.html

Firewalls:
https://itnetworks2020.blogspot.com/2019/10/firewalls.html



Comments

Post a Comment

Popular Posts

Network Access Control NAC | IT NETWORKS

-
Image
Network Access Control NAC It's something that controls access to the network. And at its simplest level, this is what NAC does.  But if that's all that it was, then it wouldn't be fundamentally different from a network authentication and authorization server. Traditional authentication to the network follows the IEEE 802.1X standard that provided an authentication method to devices wishing to join a Local Area Network (LAN) or wireless LAN. 802.1X Wireless/Wired Authentication The mechanism was a port-based network access control which used agents, the software running on client devices that provide credentials to the authenticator to control access to the network. Another means to control access to a public network such as one serving a coffee shop or in a hotel, is a captive portal. If you've ever connected to a network in an airport, hotel, or coffee shop, you might recall interacting with a web page, sometimes agreeing t
Read more

CISCO : Dynamic Multipoint Virtual Private Network (DMVPN) | ITNETWORKS

-
Image
1- Definition   DMVPN is a technology that's used in secure networks exchanging data between them without needing to redirect traffic through a  headquarter  server  or router . Dynamic Multipoint VPN ( DMVPN ) is a Cisco IOS Software solution for building reliable IPsec Virtual Private Networks (VPN). DMVPN basically is a centralized architecture that provides easier management and implementation for deployments that need very specific access controls, authorizations and restrictions for diverse branches, users, applications and partners. DMVPN + IPSEC 2- Benefits DMVPN provides the ability to create dynamic VPNs without configuring static tunnels between remote peers, including Internet Protocol (IP), IPSEC and Key Management Protocol (ISAKMP peers).   DMVPN is designed  to make HUB-AND-SPOKE   topology  by statically configuring the hub IP address on the spokes, no other changes are needed  in the configuration ns of the hub to accept ne
Read more

Issues with CISCO WIRELESS Controller (And resolution) | IT NETWORKS

-
Image
On Cisco Wireless controller 5520, The Access POINTS try to join the Controller by bringing up a connection through the CAPWAP Tunnel, you can see these attempts through the AP log itself. The problem is that the DHCP server when trying to serve IP Addresses it shows the error BAD_ADDRESS in front of each IP assigned. So I Took a single access point, started debugging it, after that, I noticed that the CAPWAP connection was empty of errors BUT!! it was trying to resolve this name  CISCO-CAPWAP-CONTROLLER This resolution is made with DNS protocol, of course, I honestly wasn't so sure of what I was doing, so I added a new entry in my DNS server and it's corresponding IP was the Controller's after that magically all the Access Points where UP and showed UP on my controller. The controller I'm working with is the CISCO WIRELESS CONTROLLER 5520 Model:  AIR-CT5520-K9 Software Version:  8.3.150.0 Image of the controller Learn
Read more