A Strategic Roadmap for Purchasing Network Management Software: Guide for Nate, the very busy Network Manager
Managing a complex network environment can be a daunting task. It's no surprise that the person responsible for this - the Network Manager - is always on the lookout for effective solutions to maintain and enhance the network's performance. In our case, let's consider Network Manager Nate who works for medium to large enterprise and is facing various challenges in his current role.
Firstly, Nate strives for mission-critical uptime and network performance. He also wants to manage his complex network efficiently, which involves coordinating multiple teams and stakeholders. A significant challenge for Nate is the inability to retain critical knowledge when IT staff transition or leave the company. This, coupled with the aspiration to shift towards a proactive approach to network management, makes his quest for a suitable Network Management Software (NMS) quite critical.
To cater to Nate's challenges and pain points, the ideal NMS can help solve this problem. ?
Here's a step-by-step guide for Nate to consider when purchasing NMS:
Step 1 - Research
The first step involves gaining an understanding of the NMS market. Nate should explore different vendors, read reviews, and study the key features of each software.
A quick google search, chatGPT, a quick whip around of the forums, DuckDuckGo, Gartner and even a visit to SourceForge to see what the open-source community is using will help.
Step 2 - Define Requirements
Nate should list down his specific needs, from ensuring network uptime to managing a diverse range of network devices and retain his teams 'tribal knowledge'. This will help him identify the features he needs in his NMS.
Here is a list of features Nate should consider and determine if they are right for his organisation.
A.?????Performance Management – Ability to collect any type of data from any vendor to report, capacity plan, alert or troubleshoot.
B.?????Alarm, Event & Log Management – Ability to collect normalised and enriched, alarm and event data from any source. Enable event deduplication, automatic remediation and custom to maximise the effectiveness of your team.
C.?????Business Focused Solutions – Software built with a commercial structure that allows flexibility in the use of the software and aligns with your business model.
D.?????Automation Management - Software that allows for operational process automation, has the ability to abstract control from users to achieve consistent results from procedures and the ability to integrate everything maximising the efficiency of Nate's team. Operation Process Automation not only improves your effectiveness, it harnesses and protects critical IP and helps Nate retain his “tribal knowledge”.
E.??????Configuration & Compliance - Software that collects, backs up and compare configuration data from any vendor and can detect changes automatically so Nate is sure he is complying with the relevant data network standards and create compliance reports.
F.??????Trend Analysis for capacity planning – Ability to use collected performance data and build live baselines that compare the same periods. These dynamic baselines will allow Nate to build true operational trends. Nate should consider asking the software provider if custom charting is available to easily show metrics.
G.?????Polling Engine – Nate needs to get this right, too many enterprises have purchased expensive well-known software that is heavily marketed but just does not do the job. Make sure you ask the vendor about this capability and have them demonstrate the following.
????????????????????????????????i.???????????Scalability - A robust polling engine should have the capability to handle a high number of devices and interfaces, and scale as the network grows. This attribute is essential, especially for medium to large enterprises, where the network may consist of thousands of devices.
??????????????????????????????ii.???????????Frequency - ??The polling engine should be able to adjust the frequency of polling according to the requirements. Critical devices may require more frequent polling while others may need less. This attribute should be customizable to suit the specific needs of the network.
????????????????????????????iii.???????????Fault Tolerance - In the event of a failure or outage, the polling engine should be capable of resuming its operations from where it left off once it's back online. This is important to ensure no significant data is lost during such events.
????????????????????????????iv.???????????Real-time Monitoring - The polling engine should offer real-time or near-real-time monitoring. This attribute is crucial for detecting network issues promptly and taking quick corrective action.
??????????????????????????????v.???????????Protocol Support - It should support a range of protocols, including SNMP, ICMP, and others. This versatility allows the engine to communicate effectively with a wide variety of network devices.
????????????????????????????vi.???????????Data Collection - It should be capable of collecting various types of data, such as bandwidth usage, packet loss, latency, uptime, CPU utilization, memory usage, and more. The range of data it can collect determines the scope of the monitoring capabilities.
???????????????????????????vii.???????????Integration - A good polling engine should be able to integrate seamlessly with other components of the NMS, including the alerting system, reporting module, and the dashboard. This attribute is key to providing a cohesive, unified view of the network's status and performance.
?????????????????????????viii.???????????Security - Given the sensitive nature of the data it handles, the polling engine must have strong security features, including encryption for data in transit and at rest, and stringent authentication and access control mechanisms.
Here is a list of attributes Nate should consider and determine if they are right for his organisation.
领英推荐
Step 3 - Shortlist NMS Vendors
Based on steps 1 & 2, Nate should then create a shortlist of vendors that provide solutions meeting these criteria. Consider customer reviews, recommendations, and vendor reputation.
Ask the shortlisted vendors to provide an estimate or guidance on a budget pricing for the project based on your requirements.
Step 4 - Request a Demo
Before making a purchase decision, Nate should request a product demo from a short list of vendors. This will allow him to see the NMS in action and help him visualise how it will operate within his network.
Nate should ask the NMS vendor to demonstrate the critical features and demonstrate how they will achieve the attributes of what he considers important for his network operation.
Step 6 - Check Support and Training
Given the critical nature of network management, Nate needs to ensure that the vendor provides comprehensive support and training, allowing his team to quickly familiarize themselves with the NMS and leverage its capabilities fully. Nate should check if there is a community wiki to support users and foster collaborative exchange.
Step 6 – Reference Checks
Nate should ask the current favourite NMS vendor to arrange an introduction to an existing customer with similar attributes and interview them to determine if the software is fit for purpose.
Questions areas are on quality of support, how the software performs and has the software added features and functionality over the years.
Step 6 - Negotiate and Purchase
Once Nate is convinced that NMS is the right choice for his needs, he can proceed to negotiate the terms of purchase. This includes the pricing model, licensing terms, and other key details.
Ensure licensing is very simple and straightforward such as licenses by Node/Device not by number of interfaces. He needs to try and understand the costs for additional modules and support.
To conduct a pricing comparison of a shortlist of network management software vendors, Network Manager Nate can consider the Total Cost of Ownership (TCO) - It's not just the software cost that matters. Nate should include installation costs, maintenance, upgrade costs, and training costs. He should also factor in the costs associated with any downtime or inefficiencies if the software doesn't meet all the requirements.
Once Nate has all the necessary information, he should compare the vendors on his shortlist. He should not only consider the pricing but also the value each solution would bring to his organization, such as improved efficiency, decreased downtime, and enhanced visibility into the network.
Finally, Nate should consider performing a cost-benefit analysis to see which solution would provide the best value for his organisation. This will involve comparing the potential benefits of each solution (in terms of improved operations, time, and cost savings) with its associated costs.
Based on this comparison, Nate should be able to make an informed purchasing decision. However, it's also essential for him to consider non-price factors like vendor reputation, customer support, software scalability, and future-proofing.
In conclusion, comparing vendor pricing is a multi-step process that goes beyond simply looking at the cost. By comprehensively analysing the costs and benefits of each solution, Nate can make a decision that offers the best value for his organization.
Step 7 - Implementation and Onboarding
After purchasing the NMS, the focus shifts to successful implementation and onboarding. This stage involves installing the software, configuring it, and training the team to use it.
In a world where network performance and uptime are mission-critical, an NMS can make all the difference.
Conclusion
By following this strategic roadmap, Network Manager Nate can address his key pain points, enhance network?