R&M Data Center Handbook
R&M Data Center Handbook
R&M Data Center Handbook
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
www.datacenter.rdm.com<br />
Layer 6 – Presentation Layer<br />
Different computer systems use different structures for data formatting. Layer 6 interprets the data, and ensures<br />
the syntax is uniform and correct (character set, coding language). Here, the data format from the transmitter is<br />
converted into a format that is not specific to any terminal device. Cryptography is used in this layer for data security<br />
purposes.<br />
Layer 7 – Application Layer<br />
In this layer, the data that was transmitted is made available to the user, or rather his/her programs. Standardization<br />
is hardest for this layer because of the multitude of applications that are available. These include wellknown<br />
application protocols like http, ftp, smtp, dns, dhcp, etc.<br />
Order of events in a transmission<br />
If a piece of information is being transmitted from one device to another, the transmitter begins with the information<br />
flow in layer 7 and forwards it down, layer by layer, right down to layer 1. In the process, each layer places a socalled<br />
header containing header information in front of the actual information to be transmitted. So, for example,<br />
the IP source and destination address as well as other information are added in layer 3, and routers use this information<br />
for path selection. An “FCS” field (checksum field) is added in layer 2 for a simple security check.<br />
By adding all this extra information, the total amount of information which is transmitted on the cable becomes far<br />
greater than the actual net information. However, the length of an Ethernet frame is limited: Its minimum length is<br />
64 bytes, and its maximum 1,518 bytes. The frame length was expanded by 4 bytes to 1,522 bytes for the purpose<br />
of tagging VLANs, as a result of the Frame Extension established in IEEE 802.3as.<br />
VLAN<br />
Virtual networks or virtual LANs (VLANs) are a technological concept for implementing logical work groups within<br />
a network. A network of this type is implemented via LAN switching or virtual routing on the link layer or on the<br />
network layer. Virtual networks are extended by a great number of switches, which for their part are connected to<br />
one another through a backbone.<br />
Half- / Full-Duplex<br />
The terms full-duplex and half-duplex are understood to mean, in a telecommunications context, a transmission of<br />
information that is based on direction and time. For half-duplex, this generally means that only one transmission<br />
channel is available. <strong>Data</strong> can be either sent or received but never both at the same time.<br />
In full-duplex operation, two stations connected with one another can send and receive data simultaneously. <strong>Data</strong><br />
streams are transmitted in both directions at the same speed. In a gigabit Ethernet (1 Gbit/s) full-duplex process,<br />
for example, this translates into a transmission speed of 2 Gbit/s.<br />
OSI & TCP/IP<br />
Toward the end of the 1960s, as the “cold war” reached its high point, the United<br />
States Department of Defense (DOD) demanded a network technology that would be<br />
very secure against attacks. It should be possible for the network to continue to<br />
operate, even in case of a nuclear war. <strong>Data</strong> transmission over telephone lines was not<br />
suitable for this purpose, since these were too vulnerable to attacks. For this reason,<br />
the United States Department of Defense commissioned the Advanced Research<br />
Projects Agency (ARPA) to develop a reliable network technology. ARPA was founded<br />
in 1957 as a reaction to the launch of Sputnik by the USSR, and had the task of<br />
developing technologies that were of use to the military.<br />
In the meantime, ARPA was renamed the Defense Advanced Research Projects Agency (DARPA), since its<br />
interests primarily served military purposes. ARPA was not an organization that employed scientists and researchers,<br />
but one which handed out orders to universities and research institutes.<br />
Over time and as ARPANET grew, it became clear that the protocols selected up to that point were no longer<br />
suitable for operating a larger network that also connected many (sub)networks to one another. For this reason,<br />
other research projects were finally initiated, which led to the development of TCP/IP protocols, or the TCP/IP<br />
model, in 1974. TCP/IP (Transmission Control Protocol / Internet Protocol) was developed with the goal of<br />
connecting various networks of different types with one another for purposes of data transmission. In order to<br />
force the integration of TCP/IP protocols into ARPANET, (D)ARPA commissioned the company of Bolt, Beranek &<br />
Newman (BBN) and the University of California at Berkeley to integrate TCP/IP into Berkeley UNIX. This also laid<br />
the foundation for the success of TCP/IP in the UNIX world.<br />
R&M <strong>Data</strong> <strong>Center</strong> <strong>Handbook</strong> V2.0 © 08/2011 Reichle & De-Massari AG Page 97 of 156