Site Level Issues

Site level issues may impact a single site or all sites. Select a site with an issue and quickly isolate site, link, or circuit issues. You can also isolate the issues through a quick view of alarms for a site.
Site related issues include overall quality of a link, VPNs down or VPNs configured for another site, connectivity issues, circuit issues, incorrect circuit definitions or inaccurate characteristics for a circuit, bandwidth issues, device assignment for a site, or issues with prefixes at a site.
A few other site level issues include scenarios where none of the applications are prioritized. If no applications are prioritized, check QoS, and then check if LQM is enabled or disabled. If the flow browser indicates that traffic is bridged, despite a configured port and an existing policy, then the issue could be the result of an interface without a circuit label.
The device or the controller, depending on alarm specifics, raise site level category of alarms and deals with site level connectivity issues. For example:
  • Direct Internet path unavailable at a branch site (Alarm—major).
  • Private WAN path unavailable at a branch site (Alarm—major).
  • All paths unavailable at a branch site (Alarm—critical), raised by the controller.
  • Loss of connectivity with the device/site (Alarm—critical), raised by the controller.
  • Path labels specified in policies not available/assigned for the site.
From Release 5.5.1, two new alarms are generated for site connectivity issues.
When the site has lost connectivity with the controller and all of the remote branches or data center, an alarm is raised. The behavior is different for a branch and data center.
  • At a data center site, this alarm is raised when all the network secure fabric links are down.
  • At a branch site, this alarm is raised when all network secure fabric links are down and all devices at the site are disconnected from the controller for more than 10 minutes.
The alarm is cleared when connectivity is re-established or if at least one of the VPNs is up.
The controller raises this alarm when any one of the below conditions exist:
  • The Direct Internet or Direct Private WAN is down.
  • At least one of the secure fabric links at the site is down.
  • At least one of the service links is down.
This alarm is cleared when all WAN paths are up.

Recommended For You