February 14th, 2011 | 
Author: Why do we need to use this layered architecture? What is wrong with viewing the network as one big task?
FIX PC ERRORS
PC Integrity Scanner
Know What Happens on YOUR PC
If you enjoyed this post, make sure you subscribe to my RSS feed!
- Computer/graphics card help?
- WHAT A GREAT NEWS! GDI .WS Internationalized Domain Names
- I am very interested in learning computer or IT, I want to get scholarship?
- What is the best computer certification for beginners?
- CLICKBANK MARKETING SECRETS HOW TO USE SEO TO GENERATE LEADS AND MAKE MONEY ONLINE
- Is this a good computer build?
- Is this a good computer build?
- Articles
- Basics
- Computer Networking Training
- Computer Programming Learning
- Computer Repair Training
- Computer Security Training
- Computer Software Training
- Computer Training For Special User Groups
- Data Recovery
- Hacking
- Home Computer Training
- How To Use The Internet
- Internet Access
- PC Spy Software
- Registry Cleaner
- Self Help and Motivational
Posted in 
Tags: 
FOR FREE!"
about
Access
adware
antivirus
Auctions
Basic
best
check
Cleaner
computer
Computers
Data
Download
Drive
find
free
from
good
Hacking
Hard
help
home
Home Computer Training
Internet
Latest
learn
learning
Need
Network
Newbie
Notebook
Program
Recovery
Registry
Repair
right
security
software
spyware
This
Training
virus
windows
Wireless
work
the layered architecture provides a standard so that manufacturers of networkable equipment can design them properly. also, RFC 894 for ethernet datagrams shows the way the data being sent along is encapsulated. This shows you how layer 3 information is in one place, layer 2 info in another, destination ip, source ip, and crc flags exist so that devices passing the data along know what to do with it.
you would have chaos if someone came along and made a network device that didnt recognize the OSI layers.
we need the OSI layers to have a standard. In having a standard and layered approach, we can troubleshoot more easily if there are any problems with the application or network. If it is a routing problem, it is just a layer 3 problem, if it is switching, it just a layer 2 concern.
It is much like a multiple choice question — eliminate which does not apply to your problem so that you would be able to know what to fix.
If we just one big lump of data without any layers, then we will troubleshoot that data from top to bottom.
I take it you’ve never tried to view a large enterprise network as “one big task.”
It’s one thing to manage a small, single-site network by yourself. It’s an entirely different matter with a large distributed enterprise network spanning 200+ sites with 1,000 or more servers covering a dozen or more roles and 30,000 client machines. Add in 3 or 4 network operating systems and half a dozen client operating systems and you have a recipe for disaster with a single person trying to manage and monitor the whole mess.
This has nothing to do directly with the OSI model as a couple of respondents have implied. However in a large network you will have a number of folks who are versed in it with respect to the areas of their expertise. Routing and switching staffers will be familiar with layers 1 through 3 in particular while programmers will be familiar with higher layers in the OSI model.
In a large network you will have experts in a number of areas on staff such as:
1. Routing & Switching
2. Network Operating Systems
3. Client Operating Systems
4. E-Mail & Messaging
5. Databases
6. Telecommunications
7. Server Hardware
8. Client Hardware
9. Application Development
10. Mainframe Systems
11. Cabling & Infrastructure
It’s humanly impossible for one person to be a subject matter expert in all areas or to attempt to guide and manage a large workforce that may include over 200 people.