LogicMonitor's out-of-the-box monitoring for Cisco SD-WAN networking architecture leverages the Cisco vManage API to monitor performance and availability metrics for various edge devices across your network. Cisco SD-WAN is also known as Viptela SD-WAN.
Add Resources Into Monitoring
Add your Cisco SD-WAN vManage host into monitoring. For more information on adding resources into monitoring, see Adding Devices.
LogicMonitor must provide the appropriate credentials in order to successfully access the Cisco vManage resource's data. These credentials must belong to a vManage/API user. See Cisco's vManage REST API documentation for details.
Assign Properties to Resources
Once credentials have been obtained, the following custom properties must be set on the vManage resource within LogicMonitor. For more information on setting properties, see Resource and Instance Properties.
|vmanage.port||The TCP port used to connect to vManage API endpoint. If not set, the port defaults to 8443.|
From the LogicMonitor public repository, import all Cisco SD-WAN LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent versions.
Once the LogicModules are imported (assuming all previous setup requirements have been met), data collection will automatically commence.
LogicModules in Package
LogicMonitor's package for Cisco SD-WAN consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.
|addERI_Cisco_vManage||PropertySource||Sets Cisco HyperFlex host UUID ERI for topology mapping.|
|addCategory_Cisco_vManage||PropertySource||Identifies if the device is a vManage host and sets a system category.|
|Cisco_SDWAN_Topology||TopologySource||Generate Cisco SD-WAN topologies based on data from the vManage API.|
|Cisco vManage: WAN Edge Inventory||DataSource||Monitors the WAN edge inventory of devices and their validity and deployed/staging state.|
|Cisco vManage: Transport Health||DataSource||Monitors vManage overall transport performance metrics such as jitter, loss and latency.|
|Cisco vManage: Sites||DataSource||Monitors all sites associated to the vManage portal.|
|Cisco vManage: OMP Peers||DataSource||Display information about active OMP peering sessions.|
|Cisco vManage: OMP||DataSource||Monitors vManage device OMP (Overlay Management Protocol) metrics.|
|Cisco vManage: IPv4 Interfaces||DataSource||Display information about IPv4 interfaces.|
|Cisco vManage: Devices||DataSource||Monitors all sites associated to the vManage portal.|
|Cisco vManage: Control WAN Interfaces||DataSource||Display information about the WAN interface control connection.|
|Cisco vManage: Certificate Summary||DataSource||Display information about certificates.|
|Cisco vManage: BFD Summary Per TLOC||DataSource||Monitors BFD session metrics by device per TLOC (transport location).|
|Cisco vManage: BFD Sessions||DataSource||Display information about BFD sessions.|
|Cisco vManage: BFD Device Summary||DataSource||Monitors BFD session metrics by device.|
|Cisco vManage: Application Aware Routing Stats||DataSource||Monitors Application Aware Routing metrics.|
|Cisco vManage: Application Aware Routing SLA Classes||DataSource||Monitors Application Aware Routing metrics.|
|Cisco vManage: Alarms||DataSource||Monitors vManage portal active and cleared alarms.|
The DataSources in this package do not include predefined datapoint thresholds (that is, no alerts will trigger based on collected data). This is because the technology owner has not provided KPIs that can be reliably extended to the majority of users. If you'd like to receive alerts for collected data, you'll need to manually create custom thresholds, as discussed in Tuning Static Thresholds for Datapoints.