<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2enclosuresfull.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>vandiska.com</title>
	
	<link>http://vandiska.com</link>
	<description>Just Share</description>
	<lastBuildDate>Sat, 19 Nov 2011 06:19:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/vandiska" /><feedburner:info uri="vandiska" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>Just Share</itunes:subtitle><item>
		<title>Network Foundations</title>
		<link>http://feedproxy.google.com/~r/vandiska/~3/cBsxgc6mN8A/</link>
		<comments>http://vandiska.com/network-foundations/#comments</comments>
		<pubDate>Sat, 19 Nov 2011 06:18:58 +0000</pubDate>
		<dc:creator>vandiska</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OSI Layer]]></category>

		<guid isPermaLink="false">http://vandiska.com/?p=4</guid>
		<description><![CDATA[The Purpose and Pieces of Networking When you move into the realm of Cisco networking, you have entered a world of building the roads that makes business possible. Most of the time, users and other network administrators take these roads for granted, just like you take them for granted when you drive a car. You [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The Purpose and Pieces of Networking</strong></p>
<p><strong> </strong>When you move into the realm of Cisco networking, you have entered a world of building the roads that makes business possible. Most of the time, users and other network administrators take these roads for granted, just like you take them for granted when you drive a car. You simply assume that the roads will be there and that they’ll carry you through to your destination. However, a poorly timed construction project (network maintenance) or unscheduled road closure (network outage) will bring the entire infrastructure crumbling down. The goal of a network is to establish communications throughout an organization. Let’s take a look at the core building blocks that make this communication possible:</p>
<ul>
<li><strong>Personal Computers (PCs) and Servers</strong> – these devices serve as the endpoints in the network and are responsible for sending and receiving data to and from the network. <span id="more-4"></span></li>
<li><strong>Network Connections</strong> <span class="Apple-style-span" style="font-family: Consolas, Monaco, monospace; font-size: 12px; line-height: 18px; white-space: pre;"><span class="Apple-style-span" style="font-family: Consolas, Monaco, monospace; font-size: 12px; line-height: 18px; white-space: pre;">– </span></span>you must have a way to attach a device to the network; this building block includes the network interface card (NIC), cabling and connectors.</li>
<li><strong>Hubs and Switches</strong> <span class="Apple-style-span" style="font-family: Consolas, Monaco, monospace; font-size: 12px; line-height: 18px; white-space: pre;"><span class="Apple-style-span" style="font-family: Consolas, Monaco, monospace; font-size: 12px; line-height: 18px; white-space: pre;">– </span></span>these devices provide points on which all the end systems of a network can attach.</li>
<li><strong>Routers </strong>– routers connect multiple networks together and find the best way to reach each network.</li>
</ul>
<p>These components can build a network within a local area (LAN) or across a wide area (WAN). In recent<br />
years, the lines between a LAN and WAN have begun to blur, since Wireless and Fiber Optic technology<br />
can extend the reach of a LAN much further than older technology ever could. Regardless, the following<br />
definitions still stand strong:</p>
<ul>
<li><strong>Local Area Network (LAN)</strong> –  a computer network covering a small geographic area such as a<br />
home, office or group of buildings.</li>
<li><strong>Wide Area Network (WAN)</strong> – a computer network covering a large geographic area such as a city, state, nation or globe.</li>
</ul>
<p><strong>Interpreting a Network Diagram</strong></p>
<p>The following figure shows the placement of each of the core network components:</p>
<div id="attachment_5" class="wp-caption aligncenter" style="width: 623px"><a href="http://vandiska.com/wp-content/uploads/2011/11/Interpreting-a-Network-Diagram.png"><img class="size-full wp-image-5" title="Interpreting a Network Diagram" src="http://vandiska.com/wp-content/uploads/2011/11/Interpreting-a-Network-Diagram.png" alt="Interpreting a Network Diagram" width="613" height="457" /></a><p class="wp-caption-text">Interpreting a Network Diagram</p></div>
<p>&nbsp;</p>
<p><strong>Types of Network Communication</strong><br />
Not that long ago, network communication was solely restricted to data: internal corporate data or external<br />
Internet data. Nowadays, the network has evolved to support all types of communication. Organizations<br />
have begun to merge their telephone system with the network, creating Voice over IP (VoIP)<br />
network traffic. Users have begun to mount video cameras on their computers and in conference rooms to<br />
create streaming video traffic. What’s more, the network has begun to become so entirely saturated with<br />
different application types, network administrators now require a way to divide the different traffic types<br />
into application classes, some of which are far more important than others. Because of this, all of Cisco’s<br />
newer equipment supports Quality of Service (QoS) features allowing you to manage the priorities of data<br />
crossing the network. For example, at a major bottleneck in the network (such as the transition from the<br />
high-speed LAN to the low-speed WAN), you could set up a system stating that the VoIP traffic is sent first,<br />
followed by the streaming video, followed by the business-critical applications and so on.<br />
<strong></strong></p>
<p><strong>Using the OSI Model</strong></p>
<p><strong></strong><br />
With all of this network communication occurring, trying to understand the network can become very complex,<br />
very quickly. In order to try to make sense of it all, you can use the handy OSI Model. It’s a little known<br />
fact that the OSI Model was never meant to be just a model that describes network communication. There<br />
is also an OSI protocol (technically called the “OSI Networking Suite”) that was designed to compete with<br />
TCP/IP. We now know the end of the story: TCP/IP wins. However, the OSI Model is still used today as an excellent<br />
way to describe and fully understand network communication. You will find that a deep understanding<br />
of the OSI Model is critical to your networking success in the Cisco world. This is not one of those models that<br />
you learn in order to pass the exam and then never use again. With that foundation, let’s begin.<br />
<strong>The Layers of the OSI Model</strong></p>
<p><strong></strong><br />
The OSI Model is comprised of 7 layers, each of which describes a specific aspect of network communication:</p>
<div id="attachment_6" class="wp-caption alignleft" style="width: 225px"><a href="http://vandiska.com/wp-content/uploads/2011/11/OSI-Layer.png"><img class="size-full wp-image-6 " title="OSI Model" src="http://vandiska.com/wp-content/uploads/2011/11/OSI-Layer.png" alt="OSI Model" width="215" height="410" /></a><p class="wp-caption-text">OSI Layer</p></div>
<p>Once you’ve got the layers down, you now need to know what each of them accomplishes. I’ll present this to you in two ways. First, we’ll look at the cold, hard facts about each layer, and then we’ll look at a practical example of how the OSI Model is used in real-world network communication. So, here are the facts:<br />
<strong>Application Layer</strong>: This layer interfaces directly with the network-aware application, giving it access to network resources. Without this layer, no user application would be able to get access to the network.<br />
<strong>Presentation Layer</strong>: Encodes the data being sent or received into a generic format that will be understood by both devices.</p>
<p>For example, a web browser might receive data in HTML format or a picture in JPG format, which are generic and well understood standards.</p>
<p><strong>Session Layer</strong>: Begins, ends, and manages the sessions between devices.<br />
Transport Layer: Handles the reliability of the connection and logical separation of applications.</p>
<p>For example, if a computer is surfing the Internet with a web browser and at the same time listening to Internet-radio, this layer ensures the correct data arrives to the correct application. In addition, this layer handles flow-control (ensuring one side does not send information faster than the other can receive) and data integrity (ensuring the data is not corrupt). The most common</p>
<p><strong>Transport Layer</strong> protocol is TCP.<br />
<strong>Network Layer</strong>: Provides logical addressing services allowing a device to dictate the source and destination address used for end-to-end communication. This layer is also responsible for routing the packet from its source to its destination. The most common Network layer protocol is IP.<br />
<strong>Data Link Layer</strong>: Provides physical addressing services allowing a device to dictate the source and<br />
destination address used for local network communication. This layer permits communication<br />
between devices connected to the same network. This layer is also responsible for error detection.<br />
<strong>Physical Layer</strong>: Defines the physical standards used for network communication.</p>
<p>(copy from : ) PrepLogic CCNA</p>
<h4>Incoming search terms:</h4><ul><li>Diska Com</li><li>topology star</li></ul><img src="http://feeds.feedburner.com/~r/vandiska/~4/cBsxgc6mN8A" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://vandiska.com/network-foundations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://vandiska.com/network-foundations/</feedburner:origLink></item>
		<item>
		<title>Hello world!</title>
		<link>http://feedproxy.google.com/~r/vandiska/~3/71c5YYiPTBU/</link>
		<comments>http://vandiska.com/hello-world/#comments</comments>
		<pubDate>Sat, 19 Nov 2011 00:09:21 +0000</pubDate>
		<dc:creator>vandiska</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://vandiska.com/?p=1</guid>
		<description><![CDATA[Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!]]></description>
			<content:encoded><![CDATA[<p>Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!</p>
<img src="http://feeds.feedburner.com/~r/vandiska/~4/71c5YYiPTBU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://vandiska.com/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://vandiska.com/hello-world/</feedburner:origLink></item>
	<media:rating>nonadult</media:rating></channel>
</rss>

