Table Of Contents

Managing the Event Listener

Introduction

Installation and Configuration

Configuring Multiple Event Listeners in Cisco ANA

RegTool Command Parameters

Example

Managing the Event Listener

---

This chapter describes the Cisco ANA Event Listener and configuring it to run on both a gateway and a unit.

•Introduction

•Installation and Configuration

•Configuring Multiple Event Listeners in Cisco ANA

•RegTool Command Parameters

•Example

Introduction

Cisco ANA Event Listener is a Cisco ANA internal service which runs inside the AVM 100. The event listener listens to the SNMP traps and syslogs sent by the network elements and forwards the traps and syslogs to their corresponding VNEs. VNEs must register with an event listener to receive these SNMP traps and syslogs.

Each event listener has a Cisco ANA internal address, which is used by the VNEs for registration. When a VNE is initialized, the VNE reads the address of the event listener from the registry and registers with the event listener with its own IP address. After registration is performed, any trap or syslog arriving at the event listener that has the VNE registered IP as its source IP is sent to that VNE.

After the VNE receives a SNMP trap or syslog from the event listener, it uses a framework to identify the event and operate upon it.

The Cisco ANA Event Listener can be configured to run on both a gateway and a unit. The system can also be configured to support multiple event listeners, up to one per unit or gateway. Each event listener has its own unique address, which is used for registration by the VNEs. Each VNE registers with a specific event listener to which its corresponding network element sends SNMP traps and syslogs.

Installation and Configuration

An AVM 100 containing the Cisco ANA Event Listener service is created by default during installation of a Cisco ANA gateway or unit. However, there is an important difference:

•On the gateway, the AVM 100 is not loaded by default; that is, the admin state of the AVM 100 is disabled after installation. To load the Cisco ANA Event Listener service on the gateway, AVM 100 needs to be started with Cisco ANA Manage.

•On a unit, the AVM 100 is enabled by default, and thus the Cisco ANA Event Listener service on the unit is loaded by default.

After installation, any event listener configured on a gateway or unit has the internal address 1.2.3.4. By default, any VNE registered with the event listener uses this internal address.

When one event listener is deployed in the system, its AVM 100 should be enabled and the AVM 100s on all other gateways or units should be disabled. No configuration changes are required; that is, the default event listener internal address and VNE configuration can be used.

When multiple event listeners are deployed, each event listener must be configured with a unique internal address, as described Configuring Multiple Event Listeners in Cisco ANA.

---

Note Network elements must be configured to send SNMP traps and syslogs to the gateway or unit IP address on which the event listener is running. If the event listener is running on a unit which has a hot standby server, the network elements should be configured to send SNMP traps and syslogs to both the primary unit and to the hot standby server.

---

Configuring Multiple Event Listeners in Cisco ANA

This procedure describes how to configure multiple event listeners in Cisco ANA.

Important: Before performing this procedure, make sure that:

1. The Cisco ANA gateway and units are installed.

2. The gateway is loaded.

3. All units have been configured in the system using Cisco ANA Manage.

Complete the following procedure for each event listener that needs to be configured:

---

Step 1 Choose a unique address for the event listener.

Step 2 Log into the gateway as user sheer, and change to the Main directory using the command:

# cd Main 

Step 3 From the gateway, issue the following RegTool command:

# ./runRegTool.sh -gs 127.0.0.1 set <server-ip>  "avm100/agents/trap/xidip" 
<event-listener-address> 

This command updates the registry's golden source. The update is propagated from the gateway to the relevant units automatically.

Step 4 Start AVM 100 on the unit with Cisco ANA Manage.

---

---

Note Before performing the following procedure, make sure that all VNEs are configured in the relevant units.

---

Complete the following procedure for each new VNE configured in any AVM on a unit:

---

Step 1 Choose the event listener that is to receive the traps and syslogs for that VNE.

Step 2 Locate the AVM on which this VNE resides.

Step 3 Log into the gateway as user sheer, and change to the Main directory using the command:

# cd Main 

Step 4 Issue the following RegTool command:

# ./runRegTool.sh -gs 127.0.0.1 set <server-ip> "<vne-avm>/agents/da/<vne-name>/trap/ip" 
<event-listener-address> 

This command updates the registry's golden source. The update is propagated to the relevant units automatically.

Step 5 Reload the VNE.

---

RegTool Command Parameters

The RegTool command accepts the following parameters:

•vne-avm—The AVM on which the VNE is configured.

•server-ip—The IP address of the UNIX machine on which the gateway or unit resides. This IP is defined during installation and configuration.

•vne-name—The name of the VNE in Cisco ANA.

•event-listener-address—The Cisco ANA internal address of the event listener.

This address is used for communication between the VNEs and the event listener. For example, VNE registration is performed using this address.

The format of the internal address is a standard IP address. The address must be unique in the system; the same address cannot be used by other VNEs or event listeners.

---

Note VNEs use their management IPs as the internal address.

---

Example

This example contains a gateway and two units.

•Gateway IP: 192.168.10.1

•Unit 1 IP: 192.168.10.2

–Contains AVM 100, which is an event listener with the address 1.1.1.1.

–Contains AVM 200, which is a VNE AVM.

•Unit 2 IP: 192.168.10.3

–Contains AVM 100, which is an event listener with the address 1.1.1.2.

–Contains AVM 300, which is a VNE AVM.

In this example, two event listeners are configured, one on each unit. Each event listener will handle the events (SNMP traps and syslogs) sent from the network elements that correspond to the VNEs it manages.

After installing the gateway and the two units, configure the event listeners and the VNEs:

---

Step 1 Log into the gateway with user sheer, and change to the Main directory using the command:

# cd Main 

Step 2 Issue the following commands to configure the event listener addresses:

# ./runRegTool.sh -gs 127.0.0.1 set 192.168.10.2  "avm100/agents/trap/xidip" 1.1.1.1 

# ./runRegTool.sh -gs 127.0.0.1 set 192.168.10.3  "avm100/agents/trap/xidip" 1.1.1.2 

Step 3 Issue the following commands to configure the VNEs to register to their event listener:

•For each VNE configured to receive traps and syslogs from AVM 100 on Unit 1, use the command:

# ./runRegTool.sh -gs 127.0.0.1 set 192.168.10.2 "avm200/agents/da/<vne-name>/trap/ip" 
1.1.1.1 

•For each VNE configured to receive traps and syslogs from AVM 100 on Unit 2, use the command:

# ./runRegTool.sh -gs 127.0.0.1 set 192.168.10.3 "avm300/agents/da/<vne-name>/trap/ip" 
1.1.1.2 

---