Chapter 2: Cisco ANA 4.0 Installation Prerequisites

This chapter describes the prerequisites for installing ANA, including the hardware and software requirements for Cisco ANA 4.0 in various deployment scenarios.

Before You Begin

•

Oracle is installed. The installation will not take care of the installation of Oracle. You must install and configure Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi.

•

SUN SPARC server is running Solaris 10 Generic_118822-25 or later with required patches.

•

You have logged in as the UNIX root user on the system where you want to install and configure ANA 4.0.

•

Any naming service (NIS, NIS+, LDAP) needs to be disabled on the gateway machine before installation. The installation assumes that the machine used for the install is not using a networked user credentials management feature such as NIS+ or LDAP.

•

As part of the ANA installation, some default users and user groups are created. They are:

•

The installation prompts you to create a new user ID while installing. To ensure communication between the gateway and the unit, the user ID must be the same for both units and gateways.

Oracle Requirements and Version

You must install and configure Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi, before starting the Cisco ANA installation, according to the standard software installation flow. Do not remove any features or modules since they may be required by Cisco ANA.

Oracle installation and configuration will not be part of ANA 4.0 gateway installation. For information about installing Oracle, see the Oracle user documentation at http://www.oracle.com

We recommend that the Cisco ANA database be allowed to grow and therefore it is important to check that there is sufficient disk space at the Oracle installation location.

ANA requires a minimum of 4.5 GB of free space in $ANAHOME for a small network, where, $ANAHOME is the ANA installation directory. For medium-sized and large networks increase the amount of free space in the ANA installation directory. By default, ANA is installed in /export/home/ana40.

•

Gateway and Local database (small network)—The ANA gateway and processes require 2.5 GB and ANA database requires 2 GB. The available free space is verified at the time of installation.

•

Gateway and Local database (medium-sized network)—See Hardware Requirements for disk space requirements.

•

Gateway and Local database (large network with many potential alarms)—See Hardware Requirements for disk space requirements.

•

Gateway and Remote database—ANA does not check the remote machine (/export/home/oracledata) for free space because all of the data is on a different machine.

The database instance installation can be performed as part of the Oracle software installation or separately using the dbca utility.

Installing the ANA Schema

The location of the Oracle database will be required while installing the Cisco ANA gateway. During the installation of the ANA gateway, you will also be prompted for the following Oracle database information:

Recommended Values for Database Initialization Parameters

After the Oracle database has been successfully installed, and the Oracle process has been started, the following system parameters must be configured with these minimum values:

Hardware and Software Requirements

Hardware Requirements

•

You can install the gateway and units on separate servers and install the database on the gateway server. In this scenario, the gateway and units are separated to provide a more scalable solution, intended for medium and larger-sized deployments.

•

You can install the gateway, units, and the database all on separate servers. This scenario provides a scalable solution and is suitable for large deployments.

The minimum requirements for each of these installation scenarios are detailed in the following sections.

For more details, see the section Guidelines for adding Network Elements to ANA in the Cisco Active Network Abstraction 4.0 User and Administration Guide.

Hardware Requirements for a Small Deployment

These are the minimum hardware requirements for the gateway and database installed on separate servers, for a small deployment:

The following are the hardware requirements for the unit that is installed separate from the gateway and database, in this installation scenario:

Hardware Requirements for a Medium-sized Deployment

These are the minimum hardware requirements for the gateway and database installed on separate servers, for a medium-sized deployment:

The following are the hardware requirements for the unit that is installed separate from the gateway and database, in this installation scenario:

Hardware Requirements for a Large Deployment

These are the minimum hardware requirements for the gateway, in a large deployment installation scenario, where the gateway, and units are installed on separate servers:

These are the minimum hardware requirements for the unit, in this installation scenario, where the gateway, and units are installed on separate servers:

Software Requirements

Client Requirements

Server Size: Small
Number of CPUs	2
Total Memory	16 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v490

Unit
Number of CPUs	2
Total Memory	16 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v490

Server Size: Medium
Number of CPUs	4
Total Memory	16 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v490 or SUN FIRE v890

Unit
Number of CPUs	4
Total Memory	16 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v490 or SUN FIRE v890

Server Size: Large
Number of CPUs	8
Total Memory	32 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v890

Unit
Number of CPUs	8
Total Memory	32 GB
Network	1 x 10/100M ethernet ports
Disk Space	2x73 GB HDD space
Example Platform	SUN FIRE v890

Software Requirements
Operating System	•Solaris 5.10 (Generic_118822-25 or later with required patches) •Solaris 10 patch cluster release as published by Sun on February 13, 2007. •Platform is SPARC.
Database	Customer supplied and installed Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi with partitioning option

•

A display set up with a minimum resolution for the GUI of 1024x768 and 96dpi.

Patches

The following sections detail the Solaris and Windows patches required for an ANA installation.

Solaris Patches

The ANA installation requires that the system is running SPARC based Solaris 10 with patch level 118822-25 or later.

Windows Patches

The ANA installation requires that the system is running Microsoft Windows XP Service Pack 2 or later.

User Privileges for Installation

Client Size	CPU	Total Memory	Network	Free Disk Space
Small	2GHz	2GB	1MB connection to the gateway	160 MB
Medium	2GHz	2GB	2MB connection to the gateway	160 MB
Large	3GHz	2GB	10MB connection to the gateway	160 MB

For the ANA gateway and units, and the ANA applications, there is a single installer that is provided on the ANA DVD. The Unix user ID (default anauser) must be the same for both units and gateways.

You must enable superuser (SU) on your Solaris server. The gateway and the unit installation runs with a user ID that has root privileges.

The ANA installation creates and configures the required user IDs in the Solaris system and then switches to the ANA user for the rest of the installation.

As part of the gateway installation, components such as JBOSS, Perl, licensing, logging etc., are installed. These are the platform components. Subsequently after these are installed, the ANA applications are installed seamlessly.

For more details about the ANA 4.0 applications, see Cisco Active Network Abstraction User and Administration Guide.

Ports and Protocols

Note JBOSS server may open a dynamic TCP port with the port number range from 3000 to 4000. AVMs may open dynamic TCP ports with the port number range from 32000 to 65535.

Table 2-1 ANA 4.0 Ports and Protocols
Transport Protocol	Port (Range)	Static or Dynamic Allocation	Service Name	Component	GW, Unit, Client	Direction	Process Name
ICMP	7	Static	ping	Network Autodiscovery Unit to GW communication	GW, Unit	Server to Device, Unit to GW	fping, AVM
FTP	21	Statid	FTP	AVM	GW, Unit	VNE to device	AVM
TCP	22	Static	ssh v1/v2 (TelnetCollector, EventCollector, Activation Framework)	VNE Framework	GW, Unit	VNE to device	TelnetCollector
TCP	23	Static	telnet (TelnetCollector, EventCollector, Activation Framework	VNE Framework	GW, Unit	VNE to device	TelnetCollector
TFTP	69	Static	TFTP	NEIM, Config Archive	Unit	Gateway/ Unit to Device, Device to Gateway/ Unit	TFTP
NTP	123	Static	NTP Server	Jboss	GW	Jboss to client	Jboss.Main
UDP	161	Static	snmp (SnmpCollector, Activation Framework)	VNE Framework	GW, Unit	VNE to device	SnmpCollector
UDP	162	Static	SnmpTrap	VNE Framework	GW, Unit	VNE to device	EventCollector
UDP	514	Static	SysLog	VNE Framework	GW, Unit	device to VNE	EventCollector
TCP	1098¹	Static	Naming	Jboss	GW	JBoss client to Jboss server	JBoss server
TCP	1099 1	Static	Naming	Jboss, GW secure storage EJB	GW	JBoss client to Jboss server	JBoss server
SSL	1101	Static	openssl	Secure Daemon	GW, Unit	GW to Unit, Unit to GW	sheer_secured
SNMP	1161	Static	SnmpAgentService	Jboss	GW	Jboss to client	Jboss.SnmpAgentService
SNMP	1163	Static	snmp-generator	AVM	GW, Unit	VNE to device	AVM
RMI	1237	Static	JRMPInvoker	Jboss	GW	Jboss to client	Jboss.JRMPInvoker
TCP	1310 1	Static	HTTP Web Server (Apache)	GW Diag FW, Reporting FW, WSDM GW	GW	Client to GW	Apache web server, gw.cisco.fw.war
HTTPS	1311	Static	Secure Web Server	Apache server	GW	Web server to client, client to web server	Web server
UDP	1514	Static	Syslog	AVM, VNE FW	GW, Unit	AVM to device	AVM
TCP	1521	Static	Oracle	DMM	DMM	DMM to database	DMM
SNMP	1611	Static	AVM	AVM	GW, Unit	AVM to device	AVM
TCP	2000 to 2999	Static	AVM	AVM	GW, Unit	AVM management ports	AVM
IIOP	3528	Static	iiop-service	Jboss	GW	Jboss to client	Jboss.CorbaORB
TCP	3873	Static	DefaultEjb3Connector	Jboss	GW	Jboss to client	Jboss.DefaultEjb3Connector
UDP	4162	Static	SnmpTrap	VNE Framework	GW, Unit	VNE to device	EventCollector
TCP	4445²	Static	Pooled Invoker	Jboss	GW	JBoss client to Jboss server	JBoss server
UDP	4514	Static	SysLog	VNE Framework	GW, Unit	device to VNE	EventCollector
TCP	8009 2	Static	AJP connector	Jboss	GW	JBoss client to Jboss server	JBoss server
TCP	8000 to 8999	Static	AVM	AVM	GW, Unit	Within gateway for monitoring and sending commands to AVMs	XmlRpcClient
TCP	8080 1	Static	HTTP connector	Jboss	GW	JBoss client to Jboss server	JBoss server
TCP	8083 2	Static	WebService	Jboss	GW	JBoss web service client to Jboss server	JBoss server
TCP	8443 2	Static	HTTPS connector	Jboss	GW	JBoss client to Jboss server	JBoss server
TCP	9002 1	Static	BQL	GW workflow, GW seedfile	GW	workflow (avm66) to Gateway, seedfile client to gateway	AVM
TCP	9390 2	Static	Transport	Transport across AVMs and UNITs to GW	GW, Unit	GW to Unit, Unit to GW, Unit to Unit	AVM
TCP	9490	Static	Transport (if SSL is used)	Transport across AVMs and UNITs to GW	GW, Unit	GW to Unit, Unit to GW, Unit to Unit	AVM
TCP	9771 2	Static	PTP Adaptor	GW-PTP Adaptor	GW	Jboss to legacy GW	GJC
TELNET	13873	Static	AVM	AVM	GW	GW to device	AVM
UDP	162 or 1162	Static	snmp trap	VNE Framework	GW, Unit	device to VNE	EventCollector

¹This port must be open on a firewall

²This port may be open or closed on a firewall

Table 2-2 details the ports which must be open on a firewall, and those ports which are optional.

Required (must be open)	Optional (may be open or closed)
69 (TFTP)	4444
161 (SNMP)	8090
514 (syslog)	8092
1098	8093
1099	9390
1310	9770
1311	9771
3873
4445
4457
8009
8080
8083
8443
9002

Table Of Contents

Cisco ANA 4.0 Installation Prerequisites