Pass the Riverbed RCSP-NPM 299-01 Questions and answers with ExamsMirror

A service segment is the update time period when devices send Netflow to Cascade Gateways.

A service segment is defined by its components and the applications and/or ports in use between them.

A service segment is defined as the front-end tier that directly services end users with an application.

A service segment is the update time period when Cascade Sensors send MNMP Flow to Cascade Profilers.

Line Graphs

Stacked Area Graphs

Pie Charts

Bar charts

Connection Graphs

Tables

Cascade Profiler can use switch port discovery to retrieve ARP and CAM tables directly from the NMS.

Most NMS' can be configured to SNMP Poll Cascade Profiler to retrieve conversation information.

Network API (from NMS via URL strings to get Cascade Reports)

There are no integrations; NMS' are competitors to Cascade Profiler.

External Links (from Cascade Profiler via URL strings to NMS)

Traps sent via NetFlow, sFlow, or IPFX

Alerts sent via eMail

Traps sent via SNMP

Traps sent via SPAN

Traps sent via FIX Protocol

From packets via the Cascade Sensor or Shark

From NetFlow and other standard flow protocols

From IP SLAs on any network-attached device

From CDP

From NBAR

Event List

Exception List

Report Criteria

Alarm List

Event Summary

obtain MAC addresses.

improve accuracy of the security baseline.

force lease extensions longer to make tracking unique PCs easier.

obtain an IP for itself.

Active Directory information for successful/failed login association to IPs

DHCP for host IP to MAC address association.

SNMP polling to routers, switches, and servers for CPU information.

SNMP trap data from routers, switches, and servers for security events.

SNMP polling to routers and switches for MAC address and physical switch port association.

Define an application availability analytic for the application being monitored

Define an interface-based user-defined policy

Enable the Bandwidth Surge security policy

Run a report that identifies any traffic flows that have had two different QoS taggings applied

Cascade does not have the capability to trigger such an alert.

On the Sensor, you must define either a hex string, text string, or URL.

On the Profiler, you must define either a hex string, text string, or URL.

On the Gateway, you must define either a hex string, text string, or URL.

You have to first enable security analytics on the Profiler, then you define either a string or URL on either the Profiler or the Sensor.

Custom applications cannot be defined, but the Sensor can identify most off-the-shelf programs.