Synchronization

The Synchronization tab of the Administration > Devices/Interfaces page lists the polling status of SteelHead, AppResponse and NetShark appliances, and of Cisco devices using class-based QoS configurations. It polls these devices to get the following data:

• Riverbed QoS Device- Application identification information and SteelHead QoS shaping configuration information. Polling begins as soon as NetProfiler receives SteelFlow Net data from a SteelHead.

• NetShark - Application identification information. Polling begins when NetShark sends data to NetProfiler.

• AppResponse - URL and Auto-Recognized application identification information. Polling begins when AppResponse sends data to NetProfiler.

• CBQoS Device - Statistics and configuration information for traffic classes and traffic policies defined in the Cisco router’s Quality of Service configuration. Polling begins when NetProfiler receives NetFlow data from a properly-configured router.   more

NetProfiler polls these devices every 24 hours. Additionally, you initiate polling on any or all devices manually from the Selected Actions menu or the Global Actions menu. Select the Device Type to see the polling status. The polling status can be:

• Synchronization initializing - NetProfiler has received contact from a device and is now polling it for information.

• Synchronization succeeded - NetProfiler successfully obtained information from the device and has updated its databases.

• Synchronization failed - NetProfiler was unable to obtain information. This can happen with a Cisco router if the device is not correctly configured or if it becomes unreachable. Polling can fail with a NetShark if the appliance becomes unreachable. It can fail with a SteelHead if:

• • REST access is disabled on the SteelHead.

  • Authentication failed (for example, the SteelHead and NetProfiler are not using the same access code).

  • The SteelHead is not using SteelFlow Net, CascadeFlow-compatible, or NetFlow v9 format for exporting flow data.

  • There is a network communication error, such as a firewall blocking the REST API access port.

• Synchronization not available - This applies to only NetShark appliances. It happens if NetShark is running an older software version that does not support the REST API for application synchronization.

• Device access disabled - Polling has been disabled on NetProfiler. This could mean that someone has used the Selected Actions menu and disabled polling of this particular appliance, or someone has used the Global Actions menu and disabled polling of all devices.

Hover your mouse over the status indicator to see the time that the status was determined.

The list of devices is sortable by column. Click the column heading to sort the table by a column.

The page has two menus:

• Selected Actions - Applies to only those devices that are selected in the check box column.

• Global Actions - Applies to all devices in the list.

The menu selections differ slightly between device types.

To check polling status or configure polling options for an information source, set the "Device type" as required:

• SteelHead

• NetShark

• AppResponse

• CBQoS Devices

Note that "synchronization" on Synchronization tab of the Administration > Devices/Interfaces page refers to NetProfiler being able to obtain information to synchronize its data with other devices. It does not include sending information to other devices. NetShark and AppResponse 11 have synchronization features that cause NetProfiler to send port names and user-defined application information to them. That type of synchronization is initiated from the NetShark and AppResponse 11 appliances and is not performed from the NetProfiler user interface.

Devices/Interfaces