44 Results Found
The short answer (and a common one in our industry): it depends. When comparing Cisco IOS with Juniper Junos, the decision to choose one over the other is difficult and often boils down to cost. Of course, there are other factors to consider.
The technologies examined reduce operational expenses (OpEx), not capital expenses (CapEx) that has traditionally been the focus of virtualization. Many companies implemented virtualization with the goal of saving money in the form of fewer servers to buy with a side benefit of reducing the footprint of the servers and lowering the required power and cooling. Most of the savings were in capital, but do not expect the same with many of the technologies listed here, because some may even require some additional capital expenditures, at least for software, in order to save on the day-to-day operations of IT. The bigger cost in running an IT department is in the OpEx category anyway, so savings there are recurring.
vSphere 5.5 is now available with myriad small improvements such as a faster Web Client, LACP, Autoscale and higher configuration maximums. In addition, there are changes coming such as VSAN, which may be ground-breaking in regard to VM storage of the future. Since the release of vSphere 5.5, they have not yet announced a change to the blueprint for the test. That being the case, I will say, for now, that the VCP-510 test should remain unchanged as well. My goal here is not to reeducate you on everything that you need to know for the test; instead, it is to point out the few changes that might apply in your company or organization.
If you’ve been around IT for even a few minutes, you’ve likely heard the acronyms “LAN” and “WAN” used by fellow technicians. But with all of the possible variations of networks—different sizes, different arrangements, and different protocols—how do you tell the difference between a LAN and a WAN and everything in between? The simple answer is one of scope and size.
What’s the difference between high availability and fault tolerance in VMware vSphere? This article elaborates on first configuring high availability and then layer on the fault tolerance capability. Learn more.
Software-defined networking (SDN) is a solution that will enable your organization to meet the demands of network programmability and automation. The result will be greater network agility to support new applications while complying with increasing security needs.
In 2013, VMware announced VMware Virtual SAN (VSAN), which is VMware's native version of Software Defined Storage (SDS). It is simple, easy to setup and managed by user-defined policies. This paper explains VSAN, its basic requirements and how it works.
Resource Pools are often misunderstood, disliked, and untrusted by vSphere Administrators. However, resource pools can be very useful tools for administrators who want to configure resource management without having to individually configure each VM. This leads to the administrator’s desire to explore the proper usage of resource pools.
This vSphere Essentials white paper will give you a basic understanding of some of the concerns or planning points to consider as you get ready to deploy vSphere in your organization. This is a glimpse into some of the essential things to consider for implementing vSphere. This will focus on some of the basics that vSphere administrators run into when installing the latest features and not realizing they still have some older versions implemented.
There are two types of virtual switches available using vSphere, the vSphere Standard Switch and the vSphere Distributed Switch. The vSphere Standard Switch (vSwitch or vSS) resides in and is manually configured and administered on each ESXi host. The vSphere Distributed Switch (dvSwitch or vDS) provides similar functionality but is centralized to vCenter Server and is more featured. This white paper will cover the vDS architecture as well as an overview of many of the different features that are exclusive to the vSphere Distributed Switch.