– I will be using this series of posts as an aide for teaching myself about Cisco SD-WAN. These posts are not meant to be used as a tutorial or any kind of learning guide for others and therefore may not follow logical steps or may be missing crucial information!

– Flexible NetFlow is as the name states, a more flexible version of NetFlow. Flexible NetFlow gives us more granular control over the traffic flows that we want to see and what information we want to pull out of those flows.

– NetFlow is used to collect information about traffic flows in your environment, this information is exported to a NetFlow analyzer which converts the raw data into human readable formats such as graphs, charts and tables.

– NetFlow is used to collect information about traffic flows in your environment, this information can be exported to a NetFlow analyzer which converts the raw data into human readable formats such as graphs, charts and tables.

– The Issue I had an issue on a recent project where I had a WGB-client directly connected to Gi0 on a Cisco IW3702 WGB that I wanted to be in VLAN200 so I configured the workgroup-bridge client-vlan 200 command, therefore the MAC address for this WGB-client should be in bridge-group 200 (BG200).

– debug dot11 <radio_interface> trace print rates is a pretty cool command you can use to show debugging information related to the dynamic changing of WIFI MCS rates. Below is an output from one of my lab APs while running this debug, the drop to M6 and M7 data rates is when I put a metal pot over the top of one of the APs!

– The debug dot11 <radio_interface> trace print uplink command can be used to see detailed information on what the radio interface is doing while looking for a parent. The below shows the output from a WGB client AP when it lost its parent AP.

– These Cisco WGB configurations enable support for WGB-clients in different VLANs. In this deployment I have two VLANs: VLAN100 is for device management such as the AP BVI interfaces.

– Simple Network Management Protocol version 3 introduces much needed security features to the SNMP protocol, SNMPv1 and v2c do not support authentication or encryption of SNMP data. SNMPv3 introduces authentication based on the HMAC-MD5 and HMAC-SHA algorithms, and encryption using AES algorithms (weaker algorithms are also supported).