CategoryVMware

The Future of Virtual Networking from VMworld – Part 1

VMworld Europe took place in Barcelona last week and my experience was mostly centered around NSX. A few technical sessions and a lot of meetings later, I have been given an insight into the future of virtual networking and it’s awesome! In a mini series (otherwise it’d be much too long and windy) of posts, I am going to discuss my interpretation on how this will look.

Disclaimer: this post is based on public roadmap information divulged by VMware (mostly the great mind Bruce Davie) and can be subject to change. Also, some of this is my interpretation of

Read more

vCloud NFV Kick-starts Telco Providers

VMworld2015LogoDuring VMworld Europe 2015, VMware announced a new program under their vCloud naming, called vCloud NFV (Network Function Virtualization).

What is vCloud NFV?

vCloud NFV is essentially a bundle with the best of VMware targeted to telecom/service providers (or any NFV company) to kickstart them towards operational readiness. vCloud NFV delivers the following products in the bundle:

  • vSphere.
  • VSAN.
  • NSX.
  • vRealize Operations.
  • vRealize Log Insight.
  • Site Recovery Manager.
  • vCloud Director.
  • VMware Integrated Openstack.

Architecture of vCloud NFV

vCloud NFV is aligned to the European Telecommunications Standards Institute (ETSI) NFVI Architecture Framework, which is widely adopted by providers using NFV. Along … Read more

VMware NSX 6.2: Support for Multiple vCenters

VMware NSX 6.2 dropped yesterday with some pretty awesome features. I’ll be going through most features in separate posts and this one is for the Cross-vCenter feature. Before 6.2, the NSX Manager and vCenter had a one to one relationship, making certain dual datacenter designs quite difficult. Unless you had deployed stretched clusters, your network policies were linked to one site (unless you scripted your way out). With NSX 6.2, this changes in a big way.



NSX 6.2 introduces Cross-vCenter, which allows you to deploy multiple NSX Managers (up to eight!) that synchronise their configuration. The NSX … Read more

Manually preparing ESXi hosts for VMware NSX

Usually when installing VMware NSX, the Update Manager takes care of ESXi host preparation. It takes a few VIB packages from the NSX Manager and pushes those to the ESXi hosts to prepare them for VXLAN, the distributed firewall and the distributed router.

It can happen that this process fail, for one reason or another. For instance, if your Update Manager is on the fritz or if you don’t have an Update Manager (haven’t tested this, but would imagine that that would be an issue). In those cases, whatever you do, you won’t be able to properly prepare your … Read more

Integrating VMware NSX with VMware vRealize Log Insight

VMware vRealize Log Insight is a log analyser with capabilities to receive logs from regular syslog (so every device that can send syslog over the network) and from agents for Windows and Linux. Mostly every device can be configured to send logs to it and it can be used for quick and easy operation tasks, giving one a full picture of their environment.

Inside Log Insight, you can install (or create your own) content packs. These content packs are a way to create dashboards with filtered data. The filtered data is usually determined by queries to the Log Insight search … Read more

Removing VMware Data Security after vShield to NSX upgrade

An existing vShield environment can be upgraded to a full NSX environment, as described in my VCIX post “Upgrade VMware NSX Components”. All vShield components can be upgraded, except for one; vShield Data Security.

The documentation states: NSX Data Security does not support a direct upgrade. You must uninstall the current Data Security software before upgrading to NSX Manager. After NSX Manager is upgraded, you can install NSX Data Security version 6.0. If you upgraded to NSX Manager without uninstalling Data Security, you must do so using a REST call.

A few days ago, someone came to me with … Read more

New VMware Home Lab

Until a few weeks ago, my test lab environment was the same as my production environment (where WhatPulse and this website runs on), but in a different resource pool for some prioritisation. The test environment on occasion would make trouble for the production and it was growing too big to keep it where it was. So I decided I needed a dedicated test environment.

So I made a list of requirements I had and did what everybody does, I started to google for these specs. My requirements were pretty basic: small enclosures, low power, at least 32GB of RAM, multiple … Read more

© 2024 Lostdomain

Theme by Anders NorénUp ↑