Associating NetSharks and Sensors with SteelHeads
When links in a network are using WAN optimization, the NetProfiler must receive data from a NetShark or Sensors monitoring traffic on the LAN side of the SteelHead that is located on the server side of the optimized connection. This is necessary in order to determine server delay time and network response time.
The Definitions > NetSharks & SteelHeads page enables you to specify NetSharks and Sensors that are monitoring the LAN on the server side of the WAN optimization devices.
When the WAN optimization is being performed by Riverbed SteelHeads, the NetProfiler requires the following information in order to measure server delay and to compute response time for reporting network performance:
-
SteelFlow Net (SteelHead NetFlow v9) or CascadeFlow-compatible data from the SteelHeads at both ends of the WAN.
-
Traffic statistics from a Sensor or NetShark that is monitoring the LAN that the server-side SteelHead is connected to.
The NetProfiler automatically discovers which Sensors are associated with SteelHeads that are acting in the role of being on the server side of the WAN. It does this whenever it has sufficient data to make the association. It adds these associations to the Sensors/NetSharks & SteelHeads section and lists them as "Dynamic" in the type column. They are dynamic in the sense that the NetProfiler automatically deletes them when they become stale and reassigns them when new associations are discovered, based on its analysis of the role that the SteelHeads are performing.
The NetProfiler does not automatically discover which NetShark is closest to the LAN side of a SteelHead. For NetShark appliances, and for Sensors that the NetProfiler did not have enough data to discover automatically, you must make the association manually as a "Static" assignment. Click New on the Definitions > NetSharks & SteelHeads page to display a section in which to make the assignment.
When you make a static assignment, your assignment remains in effect until you edit it or delete it. The dynamic discovery and maintenance features do not affect your static assignments.
For accurate reporting of server delay and response times, use this page to identify all Sensors and NetSharks that are monitoring the LAN-side traffic of SteelHeads that are likely to act in the role of server-side SteelHead for optimized traffic flows.