|
Summary
|
|
The DX NetOps Summer 2026 update enhances network visibility by introducing expanded multi-vendor discovery across traditional networks and SD-WAN platforms. With this release, operations teams can accelerate triage workflows, employ custom topology annotations, and leverage flexible export capabilities. See how the release enables you to quickly isolate root causes and streamline cross-team collaboration.
Key Takeaways
- Gain end-to-end visibility across traditional layer 2/3 networks and SD-WAN platforms like Versa and Viptela.
- Accelerate troubleshooting using port condition and group health roll-ups that pinpoint the root cause.
- Export high-quality views and programmatic data that can be shared efficiently across your teams.
|
Your enterprise network is more distributed, diverse, and complex than ever before. Your campus, WAN, data center, and SD-WAN environments span multiple technologies and vendors. Now more than ever, the complex relationships between devices, interfaces, and network layers are critical to your day-to-day operations.
When an issue arises, knowing that something is wrong is only the beginning. You also need to understand exactly where the problem is occurring, which elements are affected, how affected elements are connected, and where to investigate next. Without this context, troubleshooting is slow and inefficient.
Our Summer 2026 updates mark a major step forward for topology. Building on the foundation delivered over the past year, we have expanded network coverage, improved layer 2 and layer 3 discovery, accelerated operational triage, enabled the insertion of custom information, and made topology data easier to share and integrate.
Expanded coverage
You cannot always understand your enterprise network through a single discovery protocol or data source. To address this challenge, DX NetOps topology now delivers coverage across these areas:
-
SD-WAN: Versa and Viptela environments are now supported, helping your network teams visualize and navigate a broader range of platforms.
-
Layer 2 discovery: Network discovery has been enhanced with multiple complementary sources, such as Nokia LLDP, MAC address table (SAT), and LACP relationships.
-
Layer 3 relationships: Using IP address tables, routing tables, and ARP information, topology can derive additional layer 3 relationships between your monitored network elements.
Together, these capabilities improve topology fidelity and allow you to represent relationships that cannot be learned through traditional neighbor protocols alone.
Accelerated triage
Large enterprise networks often contain thousands of devices and many more interfaces. The new updates help you narrow incident investigations from a broad area of impact down to the specific devices, ports, and relationships that need attention. The release offers insights into these aspects:
-
Port condition: This feature rolls up interface health to the device level, helping you identify if an underlying port condition requires attention, without forcing you to inspect every interface individually.
-
Group health: This capability enables progressive troubleshooting from an affected area, such as a site or a region, down to specific elements, to help you investigate the relevant context.
Especially useful in large environments, topology-driven contextual troubleshooting makes it simpler to determine where network problems are located.
Custom information
Automated discovery does not always capture everything your network teams know about your infrastructure. To complement the discovered topology with your operators' existing knowledge, you can now use these additional capabilities:
-
Notes and custom labels: You can add operational notes and custom labels to devices and links, allowing your team to preserve environment knowledge directly in the topology context.
-
Manual connections: When automated discovery is incomplete, this feature enables you to add connections to create a more complete picture of the network.
-
Background images: This provides greater flexibility to create views that reflect how network devices are physically implemented. You can use such visual references as site diagrams, floor plans, and rack layouts.
-
Tag-based clustering: You can organize network elements using meaningful attributes. With this capability, you can arrange views by location, technology, or any other relevant classification.
By combining automated discovery with team insights, you ensure your topology maps accurately reflect your actual deployment, while providing immediate, actionable context to any operator.
Sharing and integrating
Cross-team collaboration and external workflows frequently require you to exchange topology information with various stakeholders. DX NetOps now features options to export these assets:
-
Views: You can export topology views as PNG or SVG files. These views can be used in incident reports, operational documentation, and other areas in which you need to share network context outside the solution.
-
Topology data: This feature enables you to programmatically export topology information, such as data on devices, interfaces, relationships, discovery protocols, and attributes. Once exported, this information can be consumed by automation, reporting, and other external systems.
These export options help you break down operational silos and inject accurate network context directly into your third-party automation tools and ticketing systems.
A stronger operational foundation
DX NetOps topology continues its evolution from a network visualization tool into a more integrated workspace for discovery, triage, and collaboration. With these updates, you gain a broader, more accurate understanding of your monitored environment.
By bringing together multi-vendor data, logical relationships, physical contexts, and real-time health indicators, this release helps you work more efficiently. You no longer have to jump between disparate tools to piece together how a network issue affects your services. Instead, you have a unified, interactive map that guides you from a high-level regional alert down to the specific physical port that’s experiencing a problem. We encourage you to implement these new topology features to simplify your daily workflows and reduce your mean time to resolution.
