Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

WAN Edge Actions

SUMMARY Use the Actions dashboard to resolve issues affecting your WAN Edge devices.

When you click the WAN Edge button on the Actions dashboard, you'll see a list of all available actions. You can then click an action to investigate further. Available actions are described later in this topic.

WAN Edge Button on the Actions Dashboard

Note:

Your subscriptions determine the actions that you can see on the Actions dashboard. For more information, see Subscription Requirements for Marvis Actions.

MTU Mismatch

Marvis detects MTU mismatches between a port on the WAN Edge device and a port on the directly connected device. All devices on the same Layer 2 (L2) network must have the same MTU size. When an MTU mismatch occurs, devices might either fragment packets resulting in a network overhead or discard packets. The Details column lists the port on which the mismatch occurs. You'll need to review the port configuration on the WAN edge device and the connected device to resolve the issue.

MTU Mismatch Example

Bad WAN Uplink

The Bad WAN Uplink action identifies instances where the uplink interfaces on your Juniper Networks® SRX Series Firewall or Session Smart™ Router are experiencing issues. Marvis identifies interface-related issues (such as cable issues, congestion) or it could be network-related (high latency, packet drops, and jitter). These issues can cause poor user experience and result in an unhealthy WAN link. You might see errors in the overlay even though there are no issues in the underlay.

When you see a Bad WAN Uplink action, we recommend that you check the uplink connection on your device to troubleshoot the issue. Marvis highlights the issue indicating the need to check the connection as shown in the following example:

Poor LTE connectivity can cause uplink issues. For a bad LTE WAN link, Marvis shows a timeline of affected clients and signal strength. This timeline view is like the Anomaly Detection view for connectivity failures. Marvis automatically finds and displays the worst signal strength metric during this time. Marvis displays any one of the following signal strength metrics:

  • Received signal strength indicator (RSSI)

  • Reference Signal Received Power (RSRP)

  • Signal-to-noise ratio (SNR)

After you fix the issue in your network, Mist AI monitors the WAN link for a certain period of time to see if users are experiencing any issues. Hence, it might take up to 24 hours for the Bad WAN Uplink action to automatically resolve and appear in the Latest Updates section.

VPN Path Down

Marvis monitors the VPN paths that are associated with WAN edge nodes (Juniper Networks® SRX Series Firewall or Session Smart™ Router) in the overlay network. If all VPN tunnels or peer paths towards a hub go down, Marvis displays the VPN Path Down action so that you can take immediate action. In the following example, Marvis reports that a hub gateway is down. Notice that Marvis provides detailed information such as the impacted sites, applications, and clients.

For SSR Series Routers, the VPN Path Down action lists the specific type of peer path that is down:

  • Spoke Interface Unreachable—All the peer paths originating from a spoke interface are down as the interface is down.

  • Spoke Gateway Unreachable—All the paths originating from a spoke are experiencing a peer path down issue.

  • Hub Gateway Unreachable—All the paths terminating at a hub are experiencing a peer path down issue.

  • Hub Interface Down—All the paths to a hub interface are down as the hub interface is down.

After you fix the issue in your network, Mist AI monitors the VPN path for a certain period of time to see if users are experiencing any issues. Hence, it might take up to 24 hours for the VPN Path Down action to automatically resolve and appear in the Latest Updates section.

Non-Compliant

Marvis monitors the Junos OS version running on the primary and backup partitions on SRX Series devices at a site. The Non-Compliant action flags an SRX device if the Junos OS version on the backup partition is different from the version running on the primary partition.

The following example shows the details for the Non-Compliant action. You can click the View More link to view the details.

After you upgrade the backup partition on the SRX Series device to the proper version, the Non-Compliant action automatically resolves and appears in the Latest Updates section within 30 minutes.