____________________________________________
So Why do we go through all of this models…..
It’s natural to ask why we use networking model in the first place. It’s a good question, and there are some good answers!
Networking models do help software vendors create products that are interoperable. (At least, we hope they’re interoperable.) That doesn’t affect us directly as network admins, but two uses of these models affect up directly both as admins and as students.
Breaking networking operations up into smaller parts make it easier to learn networking in the first place. By using the OSI model in particular, you can take a structured approach to your learning.
- First, learn about cables and physical specifications (L1)
- Then learn about switches and MAC addresses (L2)
- Then start on routing (L3)
Using the OSI model to structure your troubleshooting approach is a real help, too. I always tell students to “start troubleshooting at the physical layer”, and you’ll see what I mean in the Troubleshooting section of the course. There are two kinds of troubleshooters in the world:
- Those who have a structured approach
- Those who don’t and are basically throwing stuff out there and hoping something works
____________________________________________
So Why do we go through all of this models…..
It’s natural to ask why we use networking model in the first place. It’s a good question, and there are some good answers!
Networking models do help software vendors create products that are interoperable. (At least, we hope they’re interoperable.) That doesn’t affect us directly as network admins, but two uses of these models affect up directly both as admins and as students.
Breaking networking operations up into smaller parts make it easier to learn networking in the first place. By using the OSI model in particular, you can take a structured approach to your learning.
- First, learn about cables and physical specifications (L1)
- Then learn about switches and MAC addresses (L2)
- Then start on routing (L3)
Using the OSI model to structure your troubleshooting approach is a real help, too. I always tell students to “start troubleshooting at the physical layer”, and you’ll see what I mean in the Troubleshooting section of the course. There are two kinds of troubleshooters in the world:
- Those who have a structured approach
- Those who don’t and are basically throwing stuff out there and hoping something works
____________________________________________
No comments:
Post a Comment