Resource Library

Moving data from one networked device to another requires several different functions. Each function has its own protocol or protocols that define how it is accomplished. Also, the process of delivering data from one device to another can vary. The main factor in data delivery is determining whether the two devices are directly connected or remotely connected.

Increased interconnectivity via machine-to-machine (M2M) communications, the IoE, and smart systems holds profound implications for how business trends continue to evolve. In terms of M2M growth, key developments in security will be essential, from the design and manufacture of devices to more robust cloud security and ensuring the integrity of wireless data transmissions. Without these safeguards in place, organizations and industries that rely on M2M will continue to place themselves at risk.

With VMware's recent release of the Horizon Suite (specifically View 6), VMware has taken the performance and usability features and put them all under the Blast moniker. This category of features is grouped from a marketing perspective but will retain their technical terms in the documentation, similar to how the term vSphere encompasses both ESXi and vCenter. Learn about the various features of the components that comprise the Blast family, including a brief discussion of what they are, improvements in version 6, and any notes or requirements for implementation.

VMware Horizon 6 was announced in April and began shipping in June 2014, bringing a more unified suite delivering more integration with infrastructure and cloud products and more simplicity for all devices. Along with the numerous updates across the Horizon suite, VMware has transitioned to a more traditional product licensing hierarchy. This paper explores the new licensing model and provides an overview of the new features associated with VMware Horizon 6.

While the Internet uses IP addresses assigned by an Internet authority such as the American Registry for Internet Numbers (ARIN), there are too few of these numbers to uniquely identify the millions of computers and computing devices in the world. Therefore, most enterprises use private addresses which allow them to identify the aforementioned computers. Of course, these IP numbers cannot be allowed on the Internet because all private networks use the same ones so there would be vast overlapping of addresses, and the addresses are not compliant anyway. Therefore, it is necessary to change the identity of a private host to a legal public host. This process is called Network Address Translation (NAT) and may be implemented on Cisco firewall products and Cisco routers. The firewall device(s) at the Internet demarcation point is by far the more popular way to implement NAT, but routers are used in small offices or small-to-medium-sized networks in which a separate firewalling solution is not possible or affordable. The focus of this paper is on the router-based NAT solution.

Network Functions Virtualization (NFV) is gaining momentum along with Software-Defined Networking (SDN). This paper examines the history of NFV and explores the prospects for networking to gradually evolve from a hardware-centric approach to a software-driven model. It concludes with an examination of future market implications and how NFV can help organizations to achieve their goals.

Cisco Access Control Lists (ACLs) are used in nearly all product lines for several purposes, including filtering packets (data traffic) as it crosses from an inbound port to an outbound port on a router or switch, defining classes of traffic, and restricting access to devices or services. Knowing how to design, configure, and troubleshoot ACLs is required for all network engineers working within a Cisco network.

The National Institute of Standards and Technology (NIST) created a cloud definition that has been well-accepted across the IT industry. NIST was mandated to assist government agencies to adopt cloud computing for their IT operations. As part of their mandate, NIST created multiple working groups to define cloud computing, its architecture, and requirements. In this paper we explore the center core of NIST's cloud definition.

This white paper addresses four different components of the Tivoli monitoring infrastructure for creating a high availability environment while providing redundancy and failover capacity. Although the principles are the same for each of these systems, the methods for adhering to these principles are different for each of them.

Many people believe that cloud computing requires server (or desktop) virtualization. But does it? We will look at using virtualization without cloud computing, cloud computing without virtualization, and then look at using both together. In each case, we'll look at where each deployment might be most useful, some use cases for it and some limitations.