Resource Library

Session Initiation Protocol (SIP) is an internet signaling protocol, developed by the IETF (starting in 1996), for establishing, maintaining, and tearing down sessions between a variety of real-time media, including voice, video, and chat. SIP allows endpoints to locate other endpoints, whether stationary or mobile. SIP doesn't have to worry about transporting voice or video as Real Time Transport Protocol (RTP) takes care of that. It also relies on Session Description Protocol (SDP) to negotiate capabilities and codecs. SIP does not provide a Directory Service or Authentication, but it does work with services such as LDAP or RADIUS. SIP is only concerned with signaling. This white paper is going to look at the way SIP is used in the converged Unified Communications environment.

This paper proposes a unifying model for project plans. A distinction will be made between the outputs of project planning and the project plan itself. The significance of this distinction is to allow projects of all types to be described at a high level, in a common language, regardless of the type of analysis used to develop the plan.

A local area network (LAN) provides a path of communication, allowing the delivery of packets of data, voice, or video originating from the sender (logical source address) to the receiver (logical destination address). Ethernet is the most common LAN used. As you start to learn about networking, remember that communication and the movement of large numbers, whether it is people, cars, mail, or network traffic, have a commonality. Everything you know and use in your daily life can be compared to the way traffic moves.

One of the most important steps in mastering a new technology is learning the associated terminology or vocabulary. In the IT field, this can be a very challenging step, as much of the terminology is often used inconsistently. This white paper defines the terminology associated with IT virtualization. It is mainly vendor-agnostic, but it does provide some vendor-specific terms, product names, and feature names used by VMware, Citrix, and Microsoft.

The utility that many senior VMware administrators rely on to address performance and troubleshooting issues is the built-in utility called ESXTOP. The tool has been built in to the hypervisor, and can be used in both ESXi and the old ESX host. The first tool many VMware Administrators rely upon is esxtop, to check real-time performance on an ESXi host using a command-line tool such as ssh to start the esxtop CLI utility. This paper will introduce and demonstrate how to start and use esxtop, specifically looking at the CPU fields. In addition, we will cover information that can be used to help with performance issues of the CPU. The esxtop utility is an excellent tool to use when you want to observe an individual ESXi host's performance.

The OSI model is a conceptual tool used to discuss and describe network functions. The use of a standard reference model is essential to communicate ideas as well as create new technologies. It is a good idea to be familiar with the OSI model, the features assigned to each layer, and examples of common protocols or technologies associated with the OSI layers.

This white paper has three main goals. The first is to generate a better understanding of the cloud in both the business and IT communities. The second is to describe the major components of vCloud and the virtual datacenters they provide. The third is help businesses visualize and understand how vClouds could be beneficial in addressing their specific IT needs.

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.

As with the adoption of any new technology, the move from IP version 4 to IP version 6 will take a number of years to complete. During that transition phase, various mechanisms will be necessary to continue support of the older protocol as the newer gains widespread momentum. In addition, there has been some evolution even within the availability of these mechanisms, some of which have already passed from general use into deprecated status. Network engineering professionals already proficient in the use of IPv6, as well as the available coexistence mechanisms, will undoubtedly stay in high demand throughout this process.

In 1998, the Internet Engineering Task Force (IETF) released RFC 2460, outlining the technical specifications of IPv6, which addressed the shortcomings of the aging IPv4 protocol. As with any evolution of technology, new elements exist in the protocol that may seem strange and unfamiliar. This certainly includes address representation, space, and so forth, but also includes a number of different types of addresses as well. A subset of these new addressing types has corresponding types in IPv4, but many will seem significantly different. The purpose of this white paper is to examine addressing classifications in detail and outline their functions within the context of the protocol.