Table Of Contents
Enabling and Launching the WBM
Configuring Network Access to the WBM
Launching the WBM
Enabling and Launching the WBM
To access the Guard module WBM, you must first use the CLI to enable the WBM service on the Guard module and permit network access to the WBM service from the client IP address. Once this is complete, you can access the Guard module WBM through a network connection using the client Web browser.
The following sections are included in this chapter:
•
Configuring Network Access to the WBM
•
Launching the WBM
Configuring Network Access to the WBM
Use the Guard module CLI to enable the WBM service and permit network access to it. You must log on as a user with either administration or configuration user privilege level rights to make the necessary configuration changes. For detailed information on accessing and using the Guard module CLI, refer to the Anomaly Guard Module Configuration Guide.
To enable the Guard module WBM service:
Step 1
Log on to the Guard module CLI using a console or SSH connection.
Step 2
Change from global mode to configuration mode. Enter the following command:
Step 3
Enable the WBM service. Enter the following command:
admin@GUARD-conf# service wbm
Step 4
Permit access to the Guard module from the remote client. Enter the following command:
admin@GUARD-conf# permit wbm ip-addr [ip-mask]
The ip-addr and ip-mask arguments define the client IP address.
For example:
admin@GUARD-conf# service wbm
admin@GUARD-conf# permit wbm 192.168.30.32
After you finish configuring network access to the WBM service on the Guard module, you may exit the CLI and launch the WBM using the client Web browser.
Launching the WBM
To launch the WBM from the client:
Step 1
Open the Web browser and enter the Guard module IP address using HTTPS (secure):
https://Guard module-ip-address/
The Guard module-ip-address argument is the management IP address of the Guard module.
The Guard module WBM login window appears.
Step 2
Enter your username and password and click OK. The WBM home page appears.
If you fail to connect to the Guard module, check the following troubleshooting tips:
•
Verify that you have entered a valid user name and password.
•
Verify that you have entered the correct Guard module management IP address and are using HTTPS.
•
Check the network connections of the client and the Guard module.
•
Ensure that you can connect to the Guard module using SSH. This will validate the network connection between the client and the Guard module.
•
Use the CLI to verify that the WBM service is enabled on the Guard module and that access from the client IP address is permitted (see the "Configuring Network Access to the WBM" section).