Cisco Configuration Engine Installation & Configuration Guide, 3.0

Scalability Among Event Gateway Ports

For scalability, we recommend that you distribute devices evenly among Event Gateway ports. This chapter provides information about Event Gateway and provides the script for executing scalability among the ports.

This chapter contains the following sections:

•Understanding Cisco Event Gateway

•Adding Devices Evenly Among Event Gateway Ports

Understanding Cisco Event Gateway

Cisco Event Gateway enables network elements to publish and subscribe to events, which allows developers to write event-driven applications to communicate with Cisco network elements. The Event Gateway also acts as an interface to the Event Bus, enabling event-based communication. Each Event Gateway port can support up to a maximum of 500 devices. To support more than 500 devices, you must run multiple event gateway processes. You can configure a maximum of 20 event gateways on the Solaris platform and a maximum of 10 event gateways on the Linux platform.

Note Performance is not affected if you enter the maximum number of event gateways.

During Cisco Configuration Engine setup, you can configure the number of concurrent gateway processes to start with either one or both of the following prompts, depending on how you set up the SSL (see Encryption Settings, page 2-5) communications:

Enter number of Event Gateways that will be started with crypto operation:

Enter number of Event Gateways that will be started with plaintext operation:

Note•The ports for Event Gateways with crypto operation are even numbers that start from 11012.

•The ports for Event Gateways with plaintext operation are odd numbers that start from 11011.

Adding Devices Evenly Among Event Gateway Ports

To add devices evenly between Event Gateway ports, follow these steps:

Step 1 Determine the number of Event Gateway ports that are running on the Cisco Configuration Engine. From the Cisco Configuration Engine server, do one of the following:

•For crypto, enter the following command:

/etc/init.d/EvtGatewayCrypto status

•For plaintext, enter the following command:

/etc/init.d/EvtGateway status

You might see output similar to the following:

TibGate (Event Gateway) process at port 11011 is running with pid 30213 

TibGate (Event Gateway) process at port 11013 is running with pid 30373 

TibGate (Event Gateway) process at port 11015 is running with pid 30425 

TibGate (Event Gateway) process at port 11017 is running with pid 30478 

TibGate (Event Gateway) process at port 11019 is running with pid 30530 

The example shows that the Cisco Configuration Engine is running five plaintext ports.

Step 2 Determine the number of devices that are connected to an Event Gateway port. Enter the following command from the Cisco Configuration Engine server:

netstat -a | grep <port number>

Example:

[root@myHost root]# netstat -a | grep 11011

tcp        0      0 *:11011                     *:*

LISTEN      

tcp        0      0 myHost:11011           111.20.119.241:11630

ESTABLISHED 

tcp        0      0 myHost:11011           111.20.119.243:11424

ESTABLISHED 

tcp        0      0 myHost:11011           111.20.119.244:21367

ESTABLISHED 

Step 3 Distribute devices evenly among the Event Gateway ports. You can distribute devices by using the Cisco Configuration Engine user interface or by using the command-line interface (CLI):

If you use the Cisco Configuration Engine user interface, follow these steps:

a. Create a template, and then enter the scalability script. Do the following:

–Choose Tools > Template Managers > Add Template.

–Click the Legacy Template Engine radio button. Then click Next.

–In the Template File field, enter a unique name for the template file.

–Enter the scalability script in the template.

For crypto, enter:

#call event_setup_security.js keepalive 60 3

For plaintext, enter:

#call event_setup.js keepalive 60 3

–Click Save.

b. Update the script that you added to the template on the Event Gateway ports on the routers. Do the following:

–Choose Devices > Update Device > Update Config. The Update Device Config page appears with a Groups list.

–From the Groups list, choose the group that contains the device you want to update, and then click the icon for the device. The Update Config page appears.

–From the Step 1 options, click the Select Static Configuration File radio button, then choose the template file that you created from the drop down list.

–Click Update.

If you use the CLI instead of the user interface, follow these steps:

•For crypto, enter the following command:

cns event <x.x.x.x> encrypt <random port> keepalive 60 3

where:

<x.x.x.x> is the IP address of the Cisco Configuration Engine server.

<random port> can range from 11012 to 11030.

•For plaintext, enter the following command:

cns event <x.x.x.x> <random port> keepalive 60 3

where:

<x.x.x.x> is the IP address of the Cisco Configuration Engine server.

<random port> can range from 11011 to 11029.

The random port range differs, depending on the number of crypto or plaintext ports that you configured during the initial Setup program.