Cisco C-EDGE vs V-EDGE

[paul_huss]

I've noticed the pattern for Network Routers has not been updated in 2 yrs.  About a year and a half ago we started replacing our vedge routers with cedge routers. (Cisco's move away from Viptella).  Unfortunately, we are no longer discovering network interfaces like we did with the vedge devices.

Anyone else seeing this issue?

[DanielJ43996773]

Hey  how are you?

So basically What changed (vEdge → cEdge)

When you were using vEdge (Viptela):

Discovery typically worked via SNMP + standard MIBs
Interfaces were exposed in a more “traditional” way
ServiceNow patterns (or SNMP classifiers) could pick them up more easily

With cEdge (IOS-XE SD-WAN):

Cisco changed the architecture significantly
Interfaces and telemetry are often:
Exposed via NETCONF / RESTCONF / APIs
Not fully represented via legacy SNMP MIBs
Some interface data is abstracted or controller-driven (vManage)

Result:
Your existing Discovery Pattern (or SNMP-based classification) doesn’t see interfaces the same way anymore.

Why your interfaces stopped showing

Most common causes I’ve seen in this exact scenario:

1. SNMP is no longer sufficient
cEdge may:
Return incomplete IF-MIB data
Hide SD-WAN logical interfaces (like VPN interfaces)
So ServiceNow Discovery doesn’t populate cmdb_ci_network_adapter

2. Pattern is outdated (your suspicion is correct)
If your Network Router pattern hasn’t been updated in 2 years, it likely:
Was built/tested for Viptela or traditional IOS
Doesn’t include:
IOS-XE SD-WAN OIDs
API-based retrieval logic

3. Missing credentials / protocols

cEdge often requires:

SSH (CLI parsing) instead of SNMP
Or even:
NETCONF
REST API (via vManage)

If Discovery is only using SNMP → you’ll miss a lot

4. Different interface types

cEdge introduces:

Tunnel interfaces
VPN-based segmentation
Overlay vs underlay interfaces

These may:

Not map cleanly to standard IF-MIB tables
Require custom parsing logic

What experienced teams are doing (real-world fixes)
Option 1 — Enhance pattern (most common)

Update your Discovery Pattern to:

Use SSH step
Parse commands like:
show interface
show ip interface brief
show sdwan interface

Then map results to:

cmdb_ci_network_adapter
cmdb_rel_ci

Option 2 — Integrate with vManage (best long-term)

Instead of discovering devices directly:

Pull data from Cisco SD-WAN (vManage)

Benefits:

Centralized truth
Full interface visibility
Better mapping of:
VPNs
Tunnels
Logical interfaces

This is not just a “pattern outdated” issue.

It’s a shift from device-based discovery → controller/API-based discovery

And ServiceNow out-of-the-box:

Still leans heavily on SNMP + traditional models

If you want to validate fast:

Can you SNMP walk IF-MIB on a cEdge and see full interfaces?
If you SSH and run show interface, do you see them?

If SSH shows more than SNMP → you’ve confirmed the root cause

Design a custom Discovery Pattern for cEdge
Map exact commands → CMDB tables
Or design vManage → ServiceNow integration architecture

If this solution worked for you, please mark it as Accepted Solution, give it a like, and thank you for your time!