Riverbed SteelCentral NetProfiler (Cascade Profiler) Alert
The JSA DSM for Riverbed SteelCentral NetProfiler collects alert logs from your Riverbed SteelCentral NetProfiler system. This product is also known as Cascade Profiler.
The following table identifies the specifications for the Riverbed SteelCentral NetProfiler DSM:
Table 1: Riverbed SteelCentral NetProfiler Specifications
RPM file name
Recorded event types
Includes custom properties?
Riverbed website (http://www.riverbed.com/)
To integrate Riverbed SteelCentral NetProfiler with JSA, complete the following steps:
If automatic updates are not enabled, download and install the most recent versions of the following RPMs on your JSA Console.
Riverbed SteelCentral NetProfiler RPM
Configure your Riverbed SteelCentral NetProfiler system to enable communication with JSA.
Create a log source on the JSA Console. Use the following table to define the Riverbed-specific parameters:
Table 2: Riverbed SteelCentral NetProfiler JDBC Log Source Parameters
Log Source Type
Riverbed SteelCentral NetProfiler
Log Source Identifier
Type a name for the log source. The name can't contain spaces and must be unique among all log sources of the log source type that is configured to use the JDBC protocol.
If the log source collects events from a single appliance that has a static IP address or host name, use the IP address or host name of the appliance as all or part of the Log Source Identifier value; for example, 192.168.1.1 or JDBC192.168.1.1. If the log source doesn't collect events from a single appliance that has a static IP address or host name, you can use any unique name for the Log Source Identifier value; for example, JDBC1, JDBC2.
You can type the actual name of the Riverbed database. For most configurations, the database name is mazu.
Tip: Confirm the actual name of the Riverbed database.
IP or Hostname
The IP address or host name of the database server.
Enter the JDBC port. The JDBC port must match the listener port that is configured on the remote database. The database must permit incoming TCP connections. The valid range is 1 - 65535.
The defaults are:
MSDE - 1433
Postgres - 5432
MySQL - 3306
Sybase - 1521
Oracle - 1521
Informix - 9088
DB2 - 50000
If a database instance is used with the MSDE database type, you must leave the Port field blank.
The list of fields to include when the table is polled for events. You can use a comma-separated list or type an asterisk (*) to select all fields from the table or view. If a comma-separated list is defined, the list must contain the field that is defined in the Compare Field.
The user name for the account that is configured to access the PostgreSQL database on the Riverbed SteelCentral NetProfiler system.
The password that is required to connect to the database.
Use Prepared Statements
Prepared statements enable the JDBC protocol source to set up the SQL statement, and then run the SQL statement numerous times with different parameters. For security and performance reasons, most JDBC protocol configurations can use prepared statements.
Start Date and Time (Optional)
Type the start date and time for database polling in the following format: yyyy-MM-dd HH:mm with HH specified by using a 24-hour clock. If the start date or time is clear, polling begins immediately and repeats at the specified polling interval.
The number of Events Per Second (EPS) that you do not want this protocol to exceed. The valid range is 100 - 20,000.
Configuring Your Riverbed SteelCentral NetProfiler System to Enable Communication with JSA
To collect Riverbed SteelCentral NetProfiler alert events, you must configure your Riverbed SteelCentral NetProfiler system to allow JSA to retrieve events from the PostgreSQL database.
- Log in to your Riverbed SteelCentral NetProfiler host user interface.
- Select Configuration > Appliance Security > Security Compliance.
- Check the Enable ODBC Access check box.
- Select Configuration > Account Management > User Accounts.
- Add an account that JSA can use to access to the PostgreSQL database.