Supported VPN services with associated subservices

The Service Health L2VPN and L3VPN types with their associated subservices provide a detailed, service-centric monitoring framework that benefits users by improving visibility, troubleshooting efficiency, and operational assurance for IOS XE and IOS XR devices in Crosswork Network Controller.

Supported VPN services with associated subservices for IOS XE devices

Supported VPN services Associated subservices Details
L2VPN P2P Plain

  • Device Health

  • Path Reachability

  • Summary (aggregator) nodes

  • VPN Interface Health

  • Y.1731 Health

IOS XE does not support SNMP or gNMI collection type for this subservice (CEF route; XConnect).

Note

 

The reference to ‘Plain’ implies that L2VPN/L3VPN traffic takes the IGP path and does not use any transports, like SR.
L2VPN Point to Point over MPLS LDP

  • Device Health

  • Path Reachability

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane health

  • Y.1731 Health

 IOS XE does not support SNMP or gNMI collection type for this subservice (CEF route; XConnect).
L2VPN Point to Point with SR underlay

  • Device Health

  • Path Reachability

  • Summary (aggregator) nodes

  • VPN Interface Health

  • Y.1731 Health

 IOS XE does not support SNMP or gNMI collection type for this subservice (CEF route; PCEP Session State; SRPolicy State; XConnect).
L3VPN SR

  • BGP Neighbor Health (DynExp)

  • CE-PE Route Health

  • eBGP Neighbor Health

  • Path Reachability

  • Summary (aggregator) nodes

  • VPN Interface Health

 IOS XE does not support SNMP or gNMI collection type for this subservice (CEF route; PCEP Session State). SR-ODN is also not supported.

Supported VPN services with associated subservices for IOS XR devices

Supported VPN services Associated subservices
L2VPN EVPN Plain

  • BGP

    • Neighbor Health (DynExp)

    • Nexthop Health (DynExp)

  • Device Health

  • EVPN Health

  • Path

    • Reachability

    • SLA

  • Plain LSP Path Health (DynExp)

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane health

Note

 

The reference to ‘Plain’ implies that L2VPN and L3VPN traffic takes the IGP path and does not use any transports, like SR.
L2VPN EVPN SR

  • BGP

    • Neighbor Health (DynExp)

    • Nexthop Health (DynExp)

  • Device Health

  • EVPN Health

  • Fallback Enabled or Disabled (DynExp)

  • Path

    • Reachability

    • SLA

  • PCEP Session Health (DynExp)

  • SR Policy

    • PCC

    • PCE

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane Health

  • Y.1731 Health
L2VPN P2P Plain

  • Device Health

  • Path Reachability

  • Path SLA

  • Plain LSP Path Health

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane Health

  • Y.1731 Health

Note

 

The reference to ‘Plain’ implies that L2VPN and L3VPN traffic takes the IGP path and does not use any transports, like SR.
L2VPN Point to Point over MPLS LDP

  • Device Health

  • Fallback Enabled/Disabled

  • Path Reachability

  • Path SLA

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane Health

  • Y.1731 Health
L2VPN Point to Point over RSVP

  • Device Health

  • Fallback Enabled/Disabled

  • Path Reachability

  • Path SLA

  • RSVP-TE Health

  • VPN Interface Health

  • VPWS Control Plane Health/Xconnect Health

  • Y.1731 Health
L2VPN Point to Point with SR underlay

  • Device Health

  • Fallback Enabled/Disabled

  • Path

    • Reachability

    • SLA

  • PCEP Session Health (DynExp)

  • SR Policy

    • PCC

    • PCE

  • Summary (aggregator) nodes

  • VPN Interface Health

  • VPWS Control Plane Health

  • Y.1731 Health
L3VPN SR

  • BGP Neighbor Health (DynExp)

  • CE-PE Route Health

  • Device Health

  • eBGP Neighbor Health

  • Path Reachability

  • PCEP Session Health (DynExp)

  • SR and SRv6 polices

  • Summary (aggregator) nodes

  • VPN Interface Health

  • Vrf Plain LSP Path Health