I don't see anything wrong with being able to differentiate layers between the two models. On the plus side, having knowledge of the OSI model comes in handy when you're talking to people or reading documentation referencing the top 4 layers of the OSI model:
Here are some links with explanation on what each layer does:
As techs we use the OSI model all the time as a network tech when trouble shooting a network connection. Since our networks were built on this model we use it even if we aren't really aware of it.
When troubleshooting a network problem we often go up the OSI model.
- Physical - Is the network cable plugged in?
- Data Link - Do you have a link light?
- Network - Are you getting an IP?
- Transport - Can you ping (or more more accurately as SaveTheRbtz pointed out telnet to) your default gateway?
- Session - Do you have DNS server information? Can you ping 188.8.131.52 but not google.com?
- & 7. Presentation & Application - Can you browse to a site?
You use the OSI even if your not aware of it. Being aware of it might help you communicate better with people/vendors about network situations. Many companies require extensive OSI knowledge for a networking certification (I know Cisco did).
I got my first job in 1990 by reciting the OSI layer model. They were most impressed. I didn't actually understand it but boy could I recite it well.
You need to know the OSI model because a lot of documentation for proxies, load balancers and other such things will refer to "Layer 7" or "Layer 4", and you need to know what they are talking about.
That wiki page does a pretty good job explaining the layers. The TCP/IP model sits on top of the OSI model.
As to whether it applies today, the answer I'd say is, "sort of". A lot of devices these days are hybrids and work on multiple layers at the same time to route packets more efficiently. However, if you are doing any sort of network design, knowing at least the basics and some of the key acronyms for at least layer 2,3,4 and 7 are handy.
These days, you don't need to know the whole OSI model.
You really just need to know:
- Layer 2 - ethernet, wifi, ppp, etc frames
- Layer 3 - IP packets
- Layer 4 - TCP and UDP packets
- Layer 7 - everything else
(invert to taste, if it offends you to have Layer 7 at the bottom)
I find my knowledge of the OSI model incredible useful in solving networking and system issues. It is a theoretical model one can use to guide investigation into a problem even though TCP/IP does not directly map to the OSI model.
You can find information about OSI model by visiting http://www.linuxconfig.net/basic-information/osi-model
As a system administrator myself, proficiency of the OSI model helped me a lot in identifying problems on my network. The link below is a simple explanation on how you could use the OSI model to troubleshoot networks.
I genuinely don't believe that many, if any, sysadmins need to know the OSI model in any specific way, however the IP model is staggeringly relevant and is used all the time.