What is our primary use case?
DX NetOps is used for demographic and topological views of network device monitoring. All network devices are onboarded into Spectrum, which performs monitoring, alerting, and related functions. DX NetOps provides a topological view and hierarchically displays how network devices are operating and whether they are experiencing communication issues. DX NetOps shows network device health and related information.
DX NetOps integrates with ServiceNow so any alert from Spectrum automatically transfers to ServiceNow.
End-to-end visibility through DX NetOps scans the entire customer landscape, covering devices in different clouds or on-premises setups, including Azure, AWS, public cloud, or private cloud, using SNMP traps. In some cases, TCP/IP is also used, but the majority of devices rely on SNMP traps.
Network performance is measured using DX NetOps by focusing on device health and establishing thresholds and metrics. We check for any faulty devices or devices that may be out of support or nearing warranty issues and certification problems. All these checks are essential as preparation for the Christmas peak from November 17th to January 6th, ensuring identification of particular reports related to devices that might be out of support or requiring certifications.
What is most valuable?
The most valuable feature in DX NetOps is the topological view, which is the network topological view. Additionally, DX NetOps has dashboards for each device type, with separated dashboards that contain numerous metrics. These metrics show the reports, and if any particular device is not able to get those metrics data, we check the SNMP traps, which tell us if there is any issue with the servers or devices unable to communicate through SNMP. DX NetOps checks for any issues with particular devices, and we confirm the checks. DX NetOps is fundamentally about dashboards and the network topological view.
Real-time insights through DX NetOps benefit diagnosing and resolving network issues since Spectrum has all sorts of details, but it lacks dashboards and a readable tabular format. DX NetOps integrates the Spectrum data to show topological views and dashboards. End users, such as the network team or customers, utilize DX NetOps to check for any faulty devices or communication issues, including identifying and replacing problematic devices. For example, Sainsbury's, with over 1600 stores and devices, depends on Spectrum to scan everything, including printers, handsets, and barcode readers. When anything is problematic, it identifies the issues and alerts the specific store teams for action.
DX NetOps dashboards have helped in making data-driven decisions as we used to have different dashboards based on the end users. We have Aruba devices, network switches, routers, handsets, and various printers, each represented on separate dashboards customized for different customers. All data comes from Spectrum, and DX NetOps customizes these dashboards based on user needs, allowing them to export reports or print pie charts and drill-down dashboards.
What needs improvement?
DX NetOps can be improved by expanding its integrations with different tools, as it can currently integrate with Spectrum and other Broadcom products. It would be beneficial to gain integration capabilities with tools such as New Relic or SolarWinds. Integration with DX NetOps occurs through API, which fetches metrics from those tools, and this is currently happening in our area, with DX NetOps receiving data not only from Spectrum but also from New Relic and SolarWinds.
DX NetOps could be improved by providing more communication methods beyond SNMP traps to accommodate different private clouds, especially as customers increasingly adopt vendor-specific clouds. For example, Sainsbury's uses SAP cloud, SAS, and Oracle cloud, where monitoring is not currently possible through DX NetOps and Spectrum, which are limited to certain mechanisms. Within the organization, SNMP is usable, but to display metrics from outside the organization, different communication methods such as agent-based connections, TCP/IP, or secured connections are necessary—features not currently available in DX NetOps and Spectrum.
For how long have I used the solution?
DX Spectrum has been used for more than 10 years, while DX NetOps has been used for two to three years.
How are customer service and support?
The technical support provided by Broadcom is rated highly. Creating a support case based on priority allows for immediate responses. When there is an issue, we raise a request, and they respond based on availability, with ticket priorities ranging from P1 to P4. They respond according to severity and send necessary patches when required.
How would you rate customer service and support?
How was the initial setup?
The implementation process is straightforward as we transitioned from on-premises to the cloud. Broadcom provides a complete software package, along with prerequisites for installation and post-installation guidelines, making it easy to install any monitoring tools, whether it is Spectrum, DX NetOps, UIM, Unicenter, or other Broadcom tools.
What about the implementation team?
Currently, we are working with Control-M, TWS, Spectrum, and DX NetOps.
Concerning pricing, we are not aware since the customer team manages it. They have a product team with Broadcom and some kind of contract, likely bundling the various tools they have rather than paying separately for DX NetOps alone.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.