Table Of Contents

Launching WBM

Setting Up the WBM

Enabling WBM on the Detector Module

Activating Remote Guards

Launching WBM

---

This chapter provides an overview of the basic procedures in Web-Based Management (WBM) and includes the following sections:

•Setting Up the WBM

•Activating Remote Guards

Setting Up the WBM

Before setting up the Web-Based Management (WBM), you must configure the Detector module from the Command Line Interface (CLI).

For detailed information on the Detector module's CLI, refer to the Cisco Traffic Anomaly Detector Module Configuration Guide.

In order to manage the Detector module, you must have the following information:

•The IP address of the Detector module

•A user-name and password for Administration or Configuration privilege level.

Users with Administration or Configuration privileges can configure WBM access for users with Dynamic and Show privileges.

Enabling WBM on the Detector Module

To enable the Detector module web-based management service, WBM, perform the following steps:

---

Step 1 Enable the WBM service. Enter the following command:

service wbm

Step 2 Permit access to the Detector module from the remote manager's IP address. Enter the following command:

permit wbm ip-addr [ip-mask]

The ip-addr and ip-mask arguments define the remote manager's IP address.

For example:

admin@DETECTOR-conf# service wbm

admin@DETECTOR-conf# permit wbm 192.168.30.32

Step 3 Open the browser and enter the following address:

https://Detector module-ip-address/ 

The Detector module-ip-address argument is the IP address of the Detector module.

The Detector module WBM login window appears.

---

Caution Note that you must HTTPS and not HTTP to enable web-based management control.

---

Step 4 Enter your username and password and click OK.

After you enter the user name and password correctly, the Detector module home page is displayed (see Figure 1-1).

---

For example:

admin@DETECTOR-conf# service wbm

admin@DETECTOR-conf# permit wbm 192.168.30.321

If you fail to connect to the Detector module, check the following:

•Make sure that you entered the correct user name and password.

•Make sure that you entered the correct IP address and that you connected using HTTPS.

•Check the network connections of both the manager's station and the Detector module.

•Check whether you can connect to the Detector module using SSH.

•Verify that the WBM service is enabled and that access from the remote manager's IP address is permitted.

Activating Remote Guards

When the Detector detects a zone traffic anomaly, it activates a remote Guard or Guards or logs the event (an action known as notify). These Guards initialize protection measures to protect the zone. The zone name in both the Guard and the Detector must be identical.

---

Note You can only configure a list of remote Guards using CLI.

---

A list of the remote Guards to be activated is defined when configuring the zone (refer to the Cisco Traffic Anomaly Detector Module Configuration Guide) or when configuring the Detector default list. The Detector first turns to the zone-configured remote Guard list and then, if nothing is specified, to the default list.

We recommend that you configure the zone Guard-protection activation forms (protect-ip-state) to determine the type of activation. See the Cisco Traffic Anomaly Detector Module Configuration Guidefor further details.

---

Note Both the default Guard list and zone specific Guard lists can include one or more Guards.

---