nice sentinel user’s guide

153 Chapter 7: Customizing NICE Sentinel

NICE Sentinel Rel. 2.1 User’s Guide (Rev A3)

Forwarding SNMP Traps to Centralized Network Monitoring Systems (NMS)


You can configure NICE Sentinel to forward SNMP traps to centralized network monitoring

systems. This allows you to keep track of your system from remote locations.

To forward SNMP traps to centralized network monitoring systems:

1. In the Navigation Pane, navigate to NetOps > Rules > SNMP Trap Rules, and right-click

Create SNMP Trap Rule.

Figure 7-4 Navigation Pane

The Rule Wizard starts.




Figure 7-5 Rule Wizard - Select an SNMP Trap Window

2. Select the SNMP traps you want to forward.

3. Click Next.

The Select the Network Elements window appears.

TIP: When you select a parent, all the children are automatically selected as well. To

select only some of the children, expand the SNMP trap parent, and select the desired

SNMP trap children.

Next

Button




Figure 7-6 Rule Wizard - Select the Network Elements Window

4. Select all the objects listed in the Pick Inventory Object area.

In the Selected Inventory Objects area, select Use Network Element List.

5. Click the Apply button .

6. The inventory objects to which this rule applies are listed in the Selected Inventory Objects

area, as in Figure 7-7.

Apply

Button




Figure 7-7 Rule Wizard - Selected Inventory Objects

7. Click Next.

The Choose the Actions window appears.




Figure 7-8 Rule Wizard - Choose the Actions Window

8. Click the Create New Action button.

The Action Editor window appears.

Figure 7-9 Action Editor Window

9. In the Action Type field, select Trap Forward.

The fields for forwarding SNMP traps appear.

Create New

Action

Button




Figure 7-10 Action Editor Window

10. Enter the following:

a. Action Name - Enter a name for this action.

b. IP Address - Enter the IP address of the server to which you want to forward the SNMP

traps.

c. Description - (optional) enter a description of this action.

11. Click Save.

The Choose the Actions window reappears; the Trap Forward action you created appears in

the Actions list.

Figure 7-11 Rule Wizard - Choose the Actions Window

12. Expand Trap Forward, and select the action you created.




13. Click Next.

The Pick a Name window appears.

Figure 7-12 Rule Wizard - Pick a Name Window

14. Enter a name for this rule and click Finish.

The wizard closes. Verify that the new SNMP trap rule appears in the Navigation Pane, as in

Figure 7-13.

Finish

Button




Figure 7-13 Navigation Pane

New SNMP

Trap Rule



Setting up a NICE Sentinel Remote Client

Setting up a NICE Sentinel Remote Client

You can access NICE Sentinel via a Remote Client. To configure the remote client, use the Remote

Client Configurator Utility.

In addition, you can configure the Remote Client manually. Use the manual configuration for

troubleshooting, or if the Configurator Utility fails to successfully set up the Remote Client. To

manually set up the Remote Client, see the NICE Sentinel Troubleshooting Guide.

Setting up the NICE Sentinel Remote Client Using the Configurator

Utility

Setting up the NICE Sentinel Remote Client using the Remote Client Configuration Utility

includes the following steps:

1. Verify connectivity to the NICE Sentinel server (see Verifying Connectivity to the NICE

Sentinel Server on page 161).

2. Run the .NET Framework Version Configuration Utility:

• For 32 bit environments, see Running the .NET Framework Version 2.0 Configuration

Utility: 32 bit Configuration on page 164.

-or-

• For 64 bit environments, see Running the .NET Framework Version 2.0 Configuration


3. Run the Remote Client Configuration Utility (see Running the Remote Client

Configuration Utility on page 166).

4. Access the NICE Sentinel server (see Accessing the NICE Sentinel Server on page 167).

Verifying Connectivity to the NICE Sentinel Server

Before beginning, verify that the Remote Client is able to ping the host name (not the IP address)

of the NICE Sentinel server.

• If you are able to ping the host name of the NICE Sentinel server, skip this section and

continue with Running the .NET Framework Version 2.0 Configuration Utility: 32 bit

Configuration on page 164 or Running the .NET Framework Version 2.0 Configuration


• If you are unable to ping the host name of the NICE Sentinel server, update the configurations

described below.

NOTE: The standard NICE Sentinel license supports a maximum of five remote client

servers. However, you can expand the license to support up to 20 remote client servers.

See Increasing the Number of Licenses on page 168.

nice sentinel user’s guide

Documents