Discover how using a Network Management System will make you proactive rather than reactive when troubleshooting. Determine which features are best for your environment. Compare the attributes of an opensource system vs a closed source system. Learn how having an NMS that consolidates multiple systems will speed repair.
- [Narrator] Having a Network Monitoring System…is the single most important part…of the troubleshooting process.…An NMS can allow you to be more proactive,…instead of reactive.…When shopping for a system, there are a lot of choices.…Price always come into play,…but that should be much further down the list.…Step one should always be features.…I start by evaluating what I'll primarily be monitoring.…I'm a Network Engineer first.…So my systems always lean towards network features.…
This may not always be the case though.…A lot of the clients I work with are big data shops.…So they'll be 95% server and application,…while only needing to monitor…a small number of network devices.…Different systems will generally cater to different…sectors of the market.…I'll break the features into two categories,…must have and would be nice.…Once I have my features set, I'll then determine…if I want to go open or closed source.…I'll always use open source NMS's because I'm…somewhat Linux savvy and don't mind investing…the time and energy required to support an open system.…
Even if you're rusty on your OSI model knowledge, this course is invaluable if you're having trouble with your network. It offers a clear, practical troubleshooting guide to narrowing down and solving most problems related to network connectivity.
- Troubleshooting the physical layer: POTS, Ethernet, and more
- Troubleshooting the data link layer
- Troubleshooting the network layer
- Troubleshooting the transport layer
- Troubleshooting Wi-Fi
- Troubleshooting proactively