What is your primary use case for SolarWinds Network Configuration Manager?

We use the solution in our organization. We also implement it for our customers. The tool is used not only for monitoring purposes but also for device management. We can back up the running and startup configurations for all vendors. It’s the main use case of the tool. The product is also used for network automation. If we want to configure the network devices, we can put the configuration in thousands of devices through the tool. It enables automation. The client mainly uses the automation features. Sometimes, we have to push the configuration into 50 to 100 devices. We usually configure it on one device and check its compatibility for one to two days. If everything works well, we make rules and push the configuration into 1000 devices. If we want to check something available out of the box, we create rules using the command in a policy. These rules can then be embedded in the policy, and the policy runs against the node. It will help detect vulnerabilities or check anything particular in the devices.

It's primarily for network configuration. Our primary use case is for compliance, specifically patch compliance and backups. Backups are crucial for disaster recovery. Because of the backup, if I need to recover from any disaster, like a faulty switch, I can restore the switch configuration without starting from scratch. With a backup, I can flash that into the device along with the configuration, restoring everything as it was before the failure. NCM has the capability to back up the devices, which reduces my turnaround time significantly. If I need to come out of a situation, having a backup of the configuration makes it much easier. NCM also helps with vulnerability assessment and remediation. We can immediately remediate vulnerabilities on any specific switches or modules.

At our company, we use the solution for remote network configuration. As part of our organization, we configure the database to all the branches; the solution helps in auto-detecting all the branches through a simple command. From the head office of our organization, we can detect branches of remote offices using SolarWinds Network Configuration Manager.

The primary use cases include configuration compliance, backup and restoration procedures, configuration change management, vulnerability management for core devices, and inventory capture of network devices.

We use the solution to manage network devices such as Cisco switches, Palo Alto devices, and Cisco devices in our 34 offices worldwide. We use it to ensure that all configurations of these network devices are properly backed up across our network infrastructure.

Network Configuration Manager is a component of the SolarWinds suite, primarily utilized for managing configuration items, particularly for devices on the network like switches and routers from various vendors such as Juniper or Cisco. It employs scripts to access these devices, enabling the copying of configurations to SolarWinds for archival and review purposes. Additionally, it facilitates making mass changes, offering convenience in managing configurations across multiple devices.

We're interested in utilizing SolarWinds Network Configuration Manager for various purposes, including network monitoring, SNMP monitoring, and creating customized layouts and maps. We're particularly keen on the ability to customize maps to visualize our network infrastructure effectively. Additionally, we value features like the dashboard, which provides insights into recent issues, helping us stay on top of any potential problems. In our network operations, we employ SolarWinds Configuration Manager to oversee all our devices, including network switches, computers, servers, virtualized equipment, POCs, and power meters. Whenever possible, we activate SMP capability for these devices and utilize it to gain insights into potential issues such as performance degradation, resource exhaustion, or downtime.

With NPM, I've created a couple of dashboards because I have a SOC view. I also have a few device groups because we provide services to customers. We're like a small ISP. So I've set up groups with alerting and maps. Visually, we have screens in the office, so if anything happens on the network, we can see it on our three or four SOC pages. We have all the top ten interfaces, so, at any given time, we can see if there's a lot of bandwidth traffic before it becomes an issue. That's where I use NPM most of the time. NCM is for backing up the configs, checking compliance, and running backup jobs every night. That's also very helpful. There aren't many tools in the market with configuration backups and conformance checks. What's nice with NCM is you can set up policies that you can then check against the configs to make sure that your device configs are adhering to a baseline or standard that you've set in place. This way, you can get a sort of order to port, which is quite nice.

We have more than 200 devices in our network. We use the product to check all the changes in the configuration and keep a base configuration. If we have new routers or switches, we have to compare them with this standard configuration.

Our primary use case for this solution is the network configuration.

We are using SolarWinds Network Configuration Manager for managing network configurations of our network devices. It helps with configuration management, network visibility and automation, and compliance and reporting. Additionally, the solution can help in mapping out network topology.

We have deployed SolarWinds Network Configuration Manager in a financial institution. The solution is used to control all the equipment, configurations, backups, configuration management, and schedule jobs from a single point. There is a bit of automation involved.

We are using the solution mainly for running backup jobs and comparing integrations.

I'm using SolarWinds Network Configuration Manager to configure and manage devices like Aruba, and it's working fine.

SolarWinds Network Configuration Manager can be used for backing up network device configuration. It helps you be more secure when you have a system failure, you can get the information back.

We use this solution to store and manage the configuration of Cisco switches and routers.

I use it for monitoring the entire network for the company. We oversee nodes, we oversee devices heading up to crossing the threshold for CPU usage. We oversee power, we oversee if they're down or if they're failing. We oversee any node down or any router from any vendor. We have MPLS, so we have a lot of those MPLS routers on the node. We can see when those routers are down. SolarWinds can give us not only that, but we can also create running tasks. It can schedule backup for the devices. We can do active jobs, we generate reports and oversee and look for any peaks of ranges or network slowness or network interruptions. These events trigger immediate alerts and the alert brings up the attention to the NOC that brings up the troubleshooting with whoever is local, depending upon who manages the network in that place. It's a helpful tool and I really like it.

They are four areas that we use the Network Configuration Manager for. One is to automate configuration backup. The second is for configuration compliance. The third is for security vulnerability detection. The fourth is to upgrade the firmware of Cisco devices.

We primarily deploy it for our customers. We don't use the solution ourselves. Customers schedule it with us and we troubleshoot for the customer as well. We have files and templates from NCM as well as confirmation templates. We sometimes schedule the backups too.

We primarily use the solution to check the configuration for Cisco, Juniper or L3 devices in our network.

I use this to monitor our system. I also use it as a configuration manager where all changes of a configuration are stalled.