One of the strengths of Aruba Orchestrator and EdgeConnect enterprise solution is the amount of visibility and control, as well as reporting that we give customers. In this section, we'll discuss some of the tools available to monitor the operation of your Aruba SD-LAN. On many Orchestrator pages, including the flows table, you see the terms inbound and outbound. These refer to the direction the traffic flows with regards to the EdgeConnect. Inbound traffic comes from the when outbound traffic flows to the LAN. Unlike a traditional switch or router, an EdgeConnect has a very defined sense of LAN and WAN sides, as well as inbound and outbound directions. When we talk about those, inbound and outbound are referred to with the respect of the site where the local appliance is. This is true for LAN traffic, shown in the light blue bars, the flow table, and WAN traffic shown in the dark blue bars. Outbound light blue LAN traffic is shown as a longer bar than the dark blue WAN traffic, because LAN traffic leaving the site is compressed and duplicate it. Similarly, on the inbound side, the light blue bar is longer because inbound WAN traffic is being decompressed to its original size. The reduction percent column on each side gives a percentage comparison of the inbound and outbound data streams in the flow to give you a quantified results related to the relative lengths of the light blue and dark blue bars. Flow monitoring is one of the most useful tools for troubleshooting, where you can view flows for one or more appliances simultaneously from the orchestrators flow tabs using data pulled in real-time from the appliance. Clicking a flows chart icon produces a flow bandwidth chart so you can see how it's functioning from moment to moment. Clicking the detail icon brings up detailed information about a specific flow. Here's an example of the flows details. It contains critical information that helps to diagnose problems. There are five sections here, each providing information as to how traffic was forwarded, what traffic was matched, and how the overlay was determined. With the Flows tab, there's also things that indicate that the EdgeConnect is dropped. In this instance, the red tech shows that the action taken was denied and we can see that this flow matched the critical apps overlay. Here, looking at the security policies for traffic between default and Southeast Asia shows that traffic was denied. Part of the orchestrator dashboard is the health map, which displays a color-coded hourly status for each selected appliance and clicking any of the hourly status block shows the status for that appliance and any alerts related to it. Built-in pie charts and orchestrator can show you the distribution of traffic through different overlays. There are many more charts available than we have time to go into in this course. Built-in reports can show which applications are using bandwidth in your network. The ratio of dark to light bars on the inbound and outbound side also give you an implicit feeling for the data reduction you're getting. This is also spelled out as a percentage on either side of the bars. The last tab can show you the amount of packet loss you are experiencing on a link as reported by the receiving end and how successful that is at correcting the loss. The green bar shows the actual prefect packet loss on the link for receive packets and the orange bars show the effect of post-fact loss or the remaining loss after FEC is applied. It's also possible to display real-time appliance charts directly from the orchestrator. Many options are available from the menu on the left. Another cool thing is the orchestrator can be configured to generate custom reports that run at scheduled times, daily, weekly, or on-demand. The granularity of the charts and the time range covered by each type of report is selectable. By checking the appropriate box, you enable or omit the types of charts generated for applications, appliances or tunnels. By selecting the appliances and orchestrators tree view and then clicking the use tree selection button, you can tell orchestrator which appliances to include in the report. You can create multiple reports with different data views and save them with different names and reporting schedules. Each report can be mailed to one or more recipients at a scheduled time. It's important that you can determine the operational status of the Aruba SD-WAN systems. You can view this information at the website status.silverpeak.cloud. Here let's look at a few logging features supported by orchestrator and the appliances. Again, there are many options and this is just a select sample. On the Orchestrator audit logs and Orchestrator debug logs are available to help you find problems in your network. On the EdgeConnect event logs, record system events, and the level of the corresponding event, and the alarm logs display alarm events. It is possible to have emails sent to recipients whenever an alarm is generated. You can control the severity level of the alarms that are sent to email so that you are not bothered by low-level issues. EdgeConnect appliances support NetFlow and IPFIX reporting. They send statistics directly to one or more collectors, not the Orchestrator, although you do configure them via the Orchestrator using a template shown here. The Wan export does not report on the tunnel packets themselves, it reports on the flows that are going through the tunnel. In other words, it reports in the packets that are destined for the tunnel prior to encapsulation and transmission across the LAN. We support many other things such as syslog, which is pretty standard. Records are sent directly to a syslog server. Appliance syslog configuration can be done in an orchestrator template group and applied to multiple devices at once in a consistent manner. You can see here that the logging configuration is quite straightforward and easy to understand. That's it. Thanks for taking the time to go through this SD-WAN essentials course.
