How SMEs can manage their Network Faults using Event Actions

How SMEs can manage their Network Faults using Event Actions

Fault management is the process of detecting, analysing and responding to faults in a system. It is an essential part of any IT infrastructure because it helps maintain availability and quality of service for applications.

 

Event actions, inside opEvents, provides your organisation with fault management visibility at the time of the event, while proactively remediating events, before they become major faults. Its ability to provide early warning detection of potential problems is more than an asset to businesses. By identifying potential hazards before they happen, signifying steps that need to be addressed or escalated before they become significant is highly desirable. You’ll be able to always see happening on your network, including; when events occur on a network, what events occur before faults, what steps were taken to remedy the faults. The combination of these factors will allow you to automatically close events and stop them from escalating to future faults.

This performance management tool will help you save time, money, resources and reputation when dealing with unexpected situations that may arise and allow you to better plan for IT emergencies.

 

Why Fault Tool Management is so important

The Fault Configuration Accounting Performance Security (FCAPS) framework for managing information security was developed by the National Institute of Standards and Technology (NIST) to provide a structured approach to Network Management.

It provides an overview of the capabilities required to manage networks effectively, and the F in FCAPS stands for Fault Management, including monitoring, detection and diagnosis.

This framework aims to improve the quality of service that users receive from their networks while also reducing costs associated with faults, outages, and maintenance.

 

How is your network performing?

Opmantek’s opEvents platform provides an automated network management solution for IT events and faults, making it easy for SMEs to monitor their networks with minimal effort. With our software, you can identify where problems are happening in real-time; without affecting your business operations and customer experience.

We offer an integrated suite of products that can be tailored to meet any business’ needs, from small and medium-sized enterprises (SME) up to large corporations. In addition, our solutions are designed to provide maximum visibility into your networks so you can identify and resolve problems before they cause downtime or financial loss.

Network management system’s like NMIS (Network Management Information System) will send fault and performance events. Increasing the breadth and depth of event management, Opmantek senior engineer Mark Henry explains this in our recent webinar ‘opEvents: All about Event Actions’.

“NMIS has a foundation escalation system that handles events singularly, however by employing opEvents you have the ability of automated event correlation”.

You can install opEvents easily as a standalone product at our downloads page, or it is available as part of our Opmantek virtual appliance package.

 

Why log analysis tools are essential for all businesses

Pro-consumer cyber security and privacy comparison website Comparitech has ranked opEvents in its list of 12 Best Log Analysis Tools, stating that it ranks highly because: “This centralised log and event manager reduces the impact of network faults and failures using proactive event management.”

In the article, Comparitech network administration expert Tim Keary wrote that: “Poor performance can emerge unexpectedly at any time. Network monitoring platforms like log analysis tools allow you to spot performance issues before they arise.”

Keary outlined that strong log analysers like opEvents provided users with data they wouldn’t otherwise have that included:

  • The ability to quantify the number of log messages that arrive in a given period by using statistics to understand and improve performance-related issues and optimise security measures.
  • Filtering and sorting tools that are capable of identifying and separating sources and events.
  • Correlation systems enable log messages generated in different formats to be analysed together to make sense of fragmented data.
  • A system of highlighting to make patterns in data more accessible to identify visually.
  • The ability to interpret a wide range of raw data and then present it to you through charts that make sense.

 

Here at Opmantek, we have seen many IT departments transformed by implementing our suite of tools to automate network Fault Management. To start making decisions through meaningful and actionable data to automatically troubleshoot your events book a demo today.

Book a Demo

Why Configuration & Compliance Management Is Crucial

Why Configuration & Compliance Management Is Crucial

Network security is of paramount concern for all businesses in 2021 and beyond, one facet of network security that should be at the forefront of most organizations is Configuration and Compliance Management.

Creating and enforcing configuration and compliance management ensures that all your network devices are configured to meet your organisation’s standards and requirements. It also encapsulates all connected devices and helps identify potential risks.

The average cost of a cybercrime attack on an Australian business is $276,323. It then takes a company an average of 23 days to recover from an attack, this stresses the importance of having configuration and compliance in place. Simple processes for opConfig involve backing up all configuration data of your network devices, comparing configuration between your devices, and creating events when configuration changes. When it comes to recuperating from an attack or fixing the problem caused by a breach, heavy losses of time and money are a continual variable amongst many businesses, these are reduced by using opConfig if they occur at all.

Unauthorised devices, installing non-compliant software, or user errors are just a few ways of how systems can be compromised. From Open-AudIT to monitor new devices on a network or non-authorised software installation to using opConfig to monitor default passwords enabled, these risks can be reduced.

 

Early warnings are paramount to network security

Early warnings are essential for network security. If you can detect a security or compliance breach early, it’s easier to stop and prevent damage. But most companies don’t have the tools they need to do this effectively. Despite this, Opmantek senior engineer Mark Henry said many IT systems were running with low-scale early warning solutions.

“Generally speaking, a lot of the customers that we talked to, who haven’t adopted NMIS (Network Management Information System) as their network monitoring solution, are sitting down around the level zero or level one area (Gartner’s IT Service Management Maturity Model). That’s also the same for many kinds of low end, off-the-shelf, free or open-source monitoring solutions,” he said.

The truth is that most companies don’t have the time or resources to monitor their networks 24/7. Using NMIS, a reliable and robust monitoring system, means you don’t have to.

 

The benefits of an integrated network management information system

Network Management Information System (NMIS) is an open-source network management system that provides real-time monitoring, configuration, and troubleshooting capabilities. It’s used by many companies worldwide who are looking for ways to manage their networks efficiently, integrating this with other modules that Opmantek offer will help build an efficient and effective strategy to help mitigate network security risk.

Open-AudIT can be installed onto Linux, Windows, or Virtual machines and once installed, needs only credentials and a subnet to discover all the devices attached to that network. Integrating Open-AudIT and NMIS is incredibly easy, Open-AudIT will discover all the devices on your network and with a click of a button, they will all be managed by NMIS, read more here. Integrating opConfig into this is a matter of importing the nodes from NMIS and then creating/applying a credential set for that node, detailed here. From here, we have a system in place that will discover any devices on your network, monitor all software installations, monitor the status/availability of devices, and report on any configuration changes.

 

To test this out on a lab network, download Opmantek’s virtual machine, with everyone installed and ready to go, and see how easy it is to get ahead of network issues.

4 Best Practices For Automating Your Network Management

4 Best Practices For Automating Your Network Management

This excerpt comes from a blog originally posted on MSP Insights

Murphy’s Law states: “Anything that can go wrong will go wrong.” Equipment always breaks when you’re on vacation, often when the on-call engineer is as far away as possible, and with little useful information from the network management software (NMS).

 

It’s critical for a network to be available 100% of the time and always performing at 100%. Network management is a core component of IT infrastructure that is put in place to minimize disruptions, ensure high performance, and help businesses avoid security issues. Network architectures and networking products handle the brunt of the work, but management tools and technologies are essential for picking up the slack and allowing the shift from reactive to proactive strategies.

 

Network automation can automate repetitive tasks to improve efficiency and ensure consistency in network teams. Ultimately, automation will improve the meantime time to resolve (MTTR) and drive down the total cost of ownership (TCO). Network automation enables staff to gain process and configuration agility while maintaining compliance standards. It will help simplify your network and lower maintenance costs.

 

Save Time And Money With Automation

According to Gartner, “The undisputed number one cause of network outages is human error.” As humans, we all make mistakes, which is why businesses must have comprehensive automation in place. Automation can reduce the likelihood of issues being missed by ensuring consistency and reducing the need for tedious manual configuration. It also can save time, money and improve productivity. The following are four steps organizations can take to build a reliable and agile network through automation.

 

1. Implement Operation Process Automation (OPA)

OPA is about getting the right systems in place to automate repetitive operational tasks to improve efficiency and ensure consistency in operations teams. OPA delivers process automation specifically to IT and network operations teams. As well as emulating actions that network engineers take within a network management system, OPA also can perform advanced maintenance tasks, assist in the interpretation of network data, and communicate effectively with other digital systems to categorize, resolve, and escalate potential network issues. Ultimately, OPA is about improving the MTTR and decreasing the cost of operations.

 

2. Improve Configuration Management

When considering automation solutions to scale your business, a critical variable to consider is time saved through automation compared to the amount of time tasks take if performed manually. A significant amount of administration time is consumed managing configurations and firmware updates, which could be better spent on proactive tasks. Organizations looking to become more efficient should consider an automated network management tool that integrates configuration management to reduce the risk of human errors and enable easier implementation of network-wide changes. This concept is not new, and it is the fundamental basis of making impactful decisions on how your organization can scale.

 

3. Single View Multi-Vendor Support

Most networks are composed of elements from multiple manufacturers. This can create challenges when overseeing the elements of each management system. A better, more efficient approach is to find and deploy management tools that offer true multi-vendor support. This will reduce the number of tools needed for day-to-day tasks and eliminate the need for learning and maintaining multiple management tools, which will improve operational responsiveness and efficiency.

 

4. Policy-Based Management Systems

Many common network administration activities should be handled by the network management system automatically. These systems should not require repeated configuration but be configured through a policy that captures the business rules and ensures that devices are handled consistently. Automated device discovery and classification is another important aspect, automatically determining what the device is, what to monitor, and what type of alerts and events will be generated, all without human intervention.

 

Combining People And Process Automation

According to Forrester, 56% of global infrastructure technology decision-makers have implemented/are implementing or are expanding/upgrading their implementation of automation software. It’s important to note that automation does not mean the replacement of individuals. Instead, it can benefit IT workers, by transferring routine and tedious elements of managing networks to machine learning models that can reduce the noise from the vast number of alerts and notifications. For organizations that are looking to scale, a combination of people and process automation will yield the best results book a demo from our experts to learn more.

Book a Demo

How To Leave Work At 5 PM: Visibility, Event Management & Automation

How To Leave Work At 5 PM: Visibility, Event Management & Automation

This excerpt comes from a blog originally posted on Packetpushers.net

As organizations manage increasingly interdependent network infrastructure in an increasingly chaotic world, how can you, as a Network Operations professional, maintain control of your network without losing control of your time?

The answers are: network visibility, flexible event management, and powerful automation. All of this is possible within Opmantek’s network management platform. The software streamlines workflows and lets network engineers and operators accomplish more work with fewer distractions, allowing them to go home on time.

The Importance Of Visibility

We often hear from network engineers that they don’t know what devices are on the network or where they’re located. This lack of visibility introduces security risks and increases Mean Time To Recovery (MTTR). The ability to see as much of the network as possible on a single dashboard allows for fast response times when you and your team need them most.

The robust network visualization tools built into Opmantek’s opCharts and opEvents give you the ability to see a network and react in real-time to precisely what’s happening with confidence. That’s essential for daily operations and in emergencies. For example, did you know that storm-related outages cost the U.S. economy up to $55 billion every year? When a major storm like Hurricane Sandy blasts through your infrastructure overnight, you’ll be able to identify the points of failure and…READ ON.

Book a Demo

Packet Pushers: Detect, Diagnose, And Act Podcast

Packet Pushers: Detect, Diagnose, And Act Podcast


Podcast: Download (46.2MB)
Keith Sinclair, CTO and progenitor of NMIS, joins Greg Ferro on Packet Pushers

They discuss:

  • What NMIS does and how it works
  • Protocol support including SNMP, WMI, SSH, RESTful APIs, and more
  • The persistence of SNMP
  • Opmantek’s approach of detect, diagnose, and act
  • Automation capabilities
  • How NMIS uses dashboards, portals, and maps

Discovery to Monitoring, Automatic & On Your Terms

Discovery to Monitoring, Automatic & On Your Terms

Introduction

So you have this great discovery and auditing tool called Open-AudIT and you also have an amazing monitoring tool called NMIS. How can you automatically take your discovered devices and have NMIS monitor them…and why would you want to?

With version 4.2.0 of Open-AudIT, we have re-implemented Integrations in an extremely easy-to-use yet extremely configurable way.

Why?

Discovery provides network transparency. Monitoring provides network visibility. Both are essential to good network management and go hand-in-hand with diagnosing network performance issues and device management and lifecycle.

You cannot manage something if you don’t know it exists, and you cannot plan for the future if you don’t know the current performance of your devices – be they desktops, servers, switches, or routers.

Why wouldn’t you want the ability to automatically monitor select device types (for example) as they come online? You can set up a scheduled Integration and automatically include all discovered routers and switches.

 

Let that sink in for a moment.

Automatically monitor devices without having to set them up individually in your monitoring solution. From discovery to monitoring automatically, on your terms.

 

Less time spent entering details.

More accurate information with zero possibility of spelling mistakes mistyped credentials, etc.

No double handling of information between systems is required.

 

It just works.

Discover it in Open-AudIT, monitor it in NMIS – seamlessly.

 

How does it work?

Integrations take a list of devices from NMIS and a list of devices from Open-AudIT. They match the devices based on selected attributes, combine their attributes according to which system (NMIS or Open-AudIT) should be the point of truth, and update both systems based on any changes.

The list of devices may actually be empty on either side. We can restrict the device list on either side based on device attributes. We can select attributes to be stored – even if they don’t exist in Open-AudIT. NMIS and Open-AudIT don’t even need to be on the same server. There is so much flexibility!

But with great flexibility, comes (potentially) great complexity. This is an area we are particularly proud of. We’ve kept the creation of an Integration as easy as possible. At its most simple level, if NMIS and Open-AudIT are installed on the same server, you can click a ‘create’ button and everything is automatically done for you. You don’t need to supply any information. We’ve chosen sensible defaults and the Integration just works.

On the other end of the scale, you might have NMIS running on Debian and Open-AudIT running on Windows. You might wish to only integrate devices that are routers. You might even have some fields in NMIS that don’t exist in Open-AudIT, – but you wish to track and be able to edit them in Open-AudIT which then updates NMIS. It’s all completely achievable with just a few clicks.

More than the simple integration above, – but still very easy to accomplish.

No code to write, just a simple-to-use web interface. Oh, – and there is also the JSON RESTful based Open-AudIT API as well.

Questions

Now let’s back up a little bit and set the scene. You’ve been using Open-AudIT for a while and have discovered some devices on your network. You have working credentials for these devices and can see their configuration. You may have computers, switches, printers, routers, firewalls, etc.

How can we easily send some of these devices to NMIS for monitoring?
When you create an Integration in Open-AudIT, by default we include all discovered devices that have working SNMP credentials. However,  you might not want every device integrated with NMIS. Some of your servers, for example, may use SNMP – but you don’t need NMIS monitoring them. Integration has a section to select which devices to include from Open-AudIT. Every device is defaulted to have its “manage_in_nmis” attribute set to “y”. There is also a rule in Open-AudIT that sets this attribute if we talk to the device using SNMP.

 

But in this example, we don’t want every SNMP talking device, we only want our routers in NMIS.

In this instance, we can simply change the used attribute to “type” (instead of “manage_in_nmis”) and the value of that attribute to “router” (instead of “y”) – then we’re done!

What if I want the SNMP Community string to be defined in NMIS, not Open-AudIT?
An Integration contains a list of the fields used by both systems (NMIS and Open-AudIT). Each field has a flag that defines its ‘priority’. This can be set to either NMIS or Open-AudIT (actually stored as external or internal). Just select NMIS for the priority for the NMIS → configuration. community field and if this value is changed in NMIS, the next time the Integration is run Open-AudIT will be updated.

How can I automatically run the Integration?
Integrations can be scheduled within Open-AudIT just like discoveries, queries, baselines, et al. You can choose to run an Integration on whatever time frame you choose.

What if I’m an NMIS user, have just installed Open-AudIT, and don’t have any devices in it?
Simply run the default Integration. Your NMIS devices will be sent to Open-AudIT and discovered automatically. Open-AudIT stores more information about the make-up of a device, as opposed to NMIS’s performance data. When you run an Integration; Open-AudIT has the device’s IP and the device’s credentials.  You can then run a discovery and retrieve everything Open-AudIT can.

 

Again – this is configurable. You might not wish to run a discovery on the device – that’s up to you! To enable or disable a discovery is a single attribute. Click, done!

Making it Happen
As usual, the Open-AudIT wiki has all the technical details you should need. Check the Integrations page and if you still have questions, please do ask in the Community Forums.