|
This instruction book provides information about installing and running Cisco Enterprise Accounting (CEA) on your Sun SPARC workstation and PC.
CEA is an end-user application that monitors, costs, and reports on ISDN network usage. For more information about using CEA, see the Cisco Enterprise Accounting Getting Started Guide.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
This section describes Cisco Enterprise Accounting (CEA) software and hardware requirements.
You must install the following software in order to run CEA:
If SunNet Manager 2.2.2 is used, CEA requires that patches 101953-0, 102469-0, and 102747-0 are installed in the SunNet Manager home directory. These patches are contained in the files 101953-0.tar.Z, 102469-0.tar.Z, and 102747-0.tar.Z and can be obtained via anonymous FTP to zippy.telcom.arizona.edu in the /pub/snm /patches/SunOS4.1.x/ SNM2.2.x directory. Instructions for installing the patches are contained in the files 101953-0.readme, 102469-0.readme, and 102747-0.readme, available at the same location.
Each Cisco ISDN router must run Cisco IOS 11.0(7) or later to support the Cisco-call-history MIB required for Cisco Enterprise Accounting.
Refer to the Cisco Enterprise Accounting Release Notes (on Cisco Connection Online or the Cisco Connection Documentation CD) for details on routers and Cisco IOS version information.
The minimum hardware requirements for running CEA include the following:
The Sun SPARC workstation used as the data collection engine should be on the same subnetwork as the IBM PC-compatible Pentium running the Windows application. The name and IP address of the workstation should be listed in the C:Windows\hosts file.
Perform the following procedure to install the Cisco Enterprise Accounting (CEA) data collection engine on a Sun SPARC 20 workstation:
Make sure to include the ./ in the ./install_cea command.
When prompted, enter the directory where the software should be installed. This directory must be readable and writable by the CEA administrator. If the executables already exist in the same directory, the script will ask permission to overwrite them. The installation script will create a /svr directory in the destination directory.
Before starting Cisco Enterprise Accounting (CEA), the SPARC workstation must be properly configured. The following tasks must be done before running CEA:
Set the user's environment variables listed in Table 1 to the desired directories. These environment variables should be set in the login profile file, such as a .cshrc or .profile file, for the CEA user. In order for these variables to work, log out and log back in.
For example, to set $SNMHOME to /var/snm, type the following command:
setenv SNMHOME /var/snmTo add the location of the CEA svr/bin executables to your PATH, type the following command:
setenv PATH ${PATH}:${CEAHOME}/svr/binThe $CEAHOME/svr/data/cea_hosts.cnf file identifies the routers CEA monitors.
Include one line in the file for each router. Each entry consists of fields separated by blanks or tabs. Blank lines and those starting with a pound sign (#) are ignored. Do not include peer (remote) hostnames in this file.
The command syntax is:
hostname nwaddr [collector method poll com log]Table 2 lists the fields and field descriptions.
Variable | Explanation |
---|---|
hostname | Fully-qualified hostname of router. |
nwaddr | IP address of router using dotted-decimal notation. |
collector | (Optional) Type of data collector to be used:
|
method | (Optional) Method to be used for collecting call data:
|
poll | (Optional) Poll interval for call data collection in minutes. The default is 10 minutes, with a minimum is 5 minutes. |
com | (Optional) Community string for SNMP GET. The default is public. |
log | (Optional) Enable or disable detailed logging for collector:
|
For example, to poll the router called server1 every ten minutes, include the following line in your cea_hosts.cnf file:
server1 171.68.1.1 E P 10 public DEach router identified in the cea_hosts.cnf file must be included in the local /etc/hosts file. Check the /etc/hosts file to verify that all routers are present.
The CEA administrator must create a SunNet Manager (SNM) database.
Make sure that you are logged in as the user who will be running CEA, and that the $SNMHOME and $SNMDBDIR environment variables have been set.
cd $SNMHOME
snm
db.<user> will be saved in $SNMDBDIR, where <user> is the user who started SNM.
CEA data collection uses SNMP to gather data from the Cisco ISDN MIB. You must load SNM with the Cisco MIB schemas.
**before** Do not skip this step or your current database will be lost.@@before@@ | Caution **after** Do not skip this step or your current database will be lost.@@after@@ |
This causes SNM to reinitialize the database, reloading its schema files in the process.
SNM is now configured to recognize the traps and MIBs required by the CEA Data Collector.
All routers to be monitored must appear in the SNM database owned by the user who will run the CEA server.
Adding routers to SNM can be done manually by following the instructions provided with SNM. However, the IP addresses of the routers are automatically added during CEA startup if you set $CEAAUTOVIEW to the name of an SNM view.
To instruct CEA to add elements automatically to the view named "cea," type the following before starting CEA:
setenv CEAAUTOVIEW ceaIf $CEAAUTOVIEW is set, CEA will attempt to update the SNM database when reading the cea_hosts.cnf file.
Configure the routers with a read community string which matches the value configured in the cea_hosts.cnf file. Perform these steps on each monitored router:
The Cisco Enterprise Accounting (CEA) installation program installs all the required files.
If you already have a previous version of CEA installed on your machine, manually remove the application before installing the current version.
To install CEA, complete the following steps:
d:\setupCEA.exe
The Welcome dialog boxes appear. Click Next on these two screens; you will see the Licence Agreement screen. Read this screen and select the Yes button if you accept the stated terms and agreements.
The setup program will decompresses and install all the needed files and ask if you want to restart the system.
You now have a Cisco Enterprise Accounting program group in your Program Manager window.
To start the Cisco Enterprise Accounting (CEA) data collection engine, enter the following command:
cea_startdsErrors can be seen in the $CEAHOME/svr/log/cea_ds_logfile file. To check the status of the data collection engine, use the cea_chkds command.
To exit the CEA data collection engine, enter the following command:
cea_killdsThe Program Manager window for Cisco Enterprise Accounting (CEA) contains the following icons:
In order to run CEA applications, complete the following tasks:
The Main Window will appear.
In order to begin the recording processes, you must start the Port Monitor application.
The products and specifications, configurations, and other technical information regarding the products contained in this manual are subject to change without notice. All statements, technical information, and recommendations contained in this manual are believed to be accurate and reliable but are presented without warranty of any kind, express or implied, and users must take full responsibility for their application of any products specified in this manual. THIS MANUAL IS PROVIDED "AS IS" WITH ALL FAULTS. CISCO DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING THOSE OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. IN NO EVENT SHALL CISCO BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES, INCLUDING WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Some states do not allow limitation or exclusion of liability for consequential or incidental damages or limitation on how long implied warranties last, so the above limitations or exclusions may not apply to you. This warranty gives Customers specific legal rights, and you may also have other rights that vary from state to state.
|