Cisco Systems 5, NAM manual Managing Waas Devices, Deployment Scenarios

Chapter 2 Setting Up The NAM Traffic Analyzer

Traffic

Deployment Scenarios

Table 2-12, WAAS Data Source Configurations lists six different deployment scenarios you might consider to monitor the optimized traffic on your WAAS network. Scenario #1 is typical when using WS-SVC-NAM-1 and WS-SVC-NAM-2 blades. Scenario #2 is typical when using NME-NAM devices.

Table 2-12		WAAS Data Source Configurations
	Deployment Scenario		Edge WAE Data Source	Core WAE Data Source
1	• Clients in the edge (branch)		Client	Server
	• Servers in the core (data center)			Server WAN
	• NAM in the core
2	• Clients in the edge (branch)		Client	Server
	• Servers in the core (data center)		Client WAN
	• NAM in the edge
3	• Servers in the edge (branch)		Server	Client
	• Clients in the core (data center)			Client WAN
	• NAM in the core
4	• Servers in the edge (branch)		Server	Client
	• Clients in the core (data center)		Server WAN
	• NAM in the edge
5	• Clients and servers in the edge (branch) and the core (data		Client	Client
	center)		Server	Server
	• NAM in the core			Client WAN
				Server WAN
6	• Clients and servers in the edge (branch) and the core (data		Client	Client
	center)		Server	Server
	• NAM in the edge		Client WAN
			Server WAN

Managing WAAS Devices

Before you can monitor WAAS traffic, you must first configure the WAAS device to export WAAS flow record data to the NAM using the WAAS command-line interface (CLI) flow monitor command like the following:

flow monitor tcpstat-v1 host <nam IP address>

flow monitor tcpstat-v1 enable

After you enable flow export to the NAM using WAAS CLI commands like those above, WAAS devices will be detected and automatically added to the NAM’s WAAS device list.

	User Guide for the Cisco Network Analysis Module (NAM) Traffic Analyzer, 5.0
2-32	OL-22617-01