Release Notes for Cisco Collection Manager, Release 3.8.x

Transcription

1 Release Notes for Cisco Collection Manager, Release 3.8.x Revised: December 21, 2012, Note This document supports all 3.8.x releases. Contents Introduction, page 2 Installation Notes, page 3 Release New Features, page 4 Release New Features, page 4 Release New Features, page 5 Release New Features, page 5 Release New Features, page 6 Release New Features, page 6 Resolved and Open Caveats, page 10 Obtaining Documentation and Submitting a Service Request, page 12 Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA

2 Introduction Introduction The Cisco Collection Manager is an implementation of RDR-collection software. The software receives raw data-records (RDRs) from Cisco SCE devices, and performs pre-aggregation and persistency into a database or text-files in CSV format. This document outlines the new features and states known caveats. For a list of the caveats that apply to Cisco Collection Manager, Release 3.8.x see the Resolved and Open Caveats, page 10. Note We have streamlined and improved the user interface. To access it, follow these instructions. To access the online Cisco Service Control documentation site, do the following: 1. On cisco.com, go to the following page: 2. From the Select a category list, select Service Exchange. 3. From the Select a subcategory list, select the desired Cisco Service Control category. 4. From the Select a product list, select the desired Cisco Service Control product. 2

3 Installation Notes Installation Notes Supported Platforms, page 3 Supported External Databases, page 4 Upgrading the Cisco Collection Manager to Release 3.8.x, page 4 Supported Platforms The Cisco Collection Manager and its database are software components that run on a server platform. They can be installed on any of the following configurations: Sun SPARC machine (64-bit) running 64-bit versions of Solaris 9 or Solaris 10. Intel machine (32-bit or 64-bit) running 32-bit versions of Red Hat Enterprise Linux 4.0 or 32-bit versions of Red Hat Enterprise Linux 5.0. Intel machine (32-bit or 64-bit) running 64-bit versions of Red Hat Enterprise Linux 5.0 or 64-bit versions of Red Hat Enterprise Linux 6.0. Caution Sybase installation on Red Hat Enterprise Linux 6.0 is not supported. Intel machine (32-bit or 64-bit) running 32-bit or 64-bit versions of CentOS 5.x. (Requires Cisco Collection Manager version or higher.) Intel machine (32-bit or 64-bit) running VMware Server or VMware ESX VMware-VMvisor-Installer x86_64.iso. Cisco Unified Computing System (UCS) server model R with a Intel(R) Xeon(R) X GHz CPU with 8 Cores (minimum memory 4 GB). All configurations use a 32-bit Java Virtual Machine (JVM). Caution The Cisco Collection Manager must run on its own server platform. It cannot run on the same machine as the Cisco Subscriber Manager or other applications. Note You can find more operating system specific information for using the Cisco Collection Manager with the Cisco Service Control Management Suite in the Cisco Service Control Management Suite Collection Manager User Guide at: Note The Cisco Collection Manager bundled Sybase server is assigned to one CPU core at the time of installation. The Sybase license allows you to assign a maximum of four CPU cores. Note The maximum database size supported by the bundled Sybase database is 50GB. For database support larger than 50GB, use an external database. 3

4 Release New Features Supported External Databases The Cisco Collection Manager supports the following external databases: MySQL Releases 4.1, 5.0, and 5.1 Oracle Releases 9.2, 10.2, and 11 Sybase Releases 12.5 and 15 Caution Sybase installation on Red Hat Enterprise Linux 6.0 is not supported. Upgrading the Cisco Collection Manager to Release 3.8.x For upgrade information, please refer to the Cisco Service Control Management Suite Collection Manager Quick Start Guide, Release 3.8.x. at: Release New Features This section lists the features introduced in this release: Virtual Link Bandwidth Usage per Package The Cisco Collection Manager supports the IP_TYPE along with the existing PACKAGE_ID and UP_VLINK_ID/DOWN_VLINK_ID based aggregation. Records aggregate based on each unique combination of PACKAGE/UP_LINK/IP_TYPE and PACKAGE/DOWN_LINK/IP_TYPE. IPv6 Support for RDRs: The below RDR's are enhanced to support IPv6 Virtual Link Usage RDR (VLUR) Media Flow RDR SPAM RDR Note Initial IPV6 support began in Release Release New Features This section lists the features introduced in this release: IP Type based aggregation in the topper/aggregator (TA) Adapter: IP Type based aggregation is added to the TA Adapter in addition to the existing service/package based aggregation. The TA Adapter now aggregates the records and lists the top subscribers for each service/package/iptype combination with a different metric. IP Type based aggregation is enabled by default The removal of NetFlow support: 4

5 Release New Features CM:NetFlow data collection and all NetFlow related utility script support has been removed from Cisco Collection Manager package. Additional IPv6 RDR support: The below RDR's are enhanced to support IPv6 Subscriber Usage RDR (RPT_NUR) Package Usage RDR (RPT_PUR) Real-time Subscriber Usage RDR (RPT_SUR) Zone Usage RDR (RPT_ZUR) Note Initial IPV6 support began in Release Release New Features This section describes the features introduced in this release: Initial IPV6 support: The below RDR's are enhanced to support IPv6 Link Usage RDR (LUR) Transaction RDR(TR) HTTP TUR RDR Video TUR RDR Operating System Finger Printing Support (OSFP) OSFP is supported for the Subscriber Usage RDR (NUR). New fields are added to RPT_NUR. Release New Features This section describes the features introduced in this release: Custom Adapter The Custom Adapter receives RDRs, processes specific fields configured by the user, and writes the records to files on the disk in comma-separated value format. Using standard mechanisms such as FTP, a service provider's OSS or a third-party billing system can retrieve these records to generate enhanced accounting and network traffic analysis records. CDMA Support The Cisco Collection Manager now supports both GSM and CDMA mobile based reports. Previously the Cisco Collection Manager only supported GSM. TA Adapter Package Based Aggregation From 3.7.2, The TA Adapter aggregates the records and lists the top subscribers for each service/package combination with different metrics. The TA Adapter package based aggregation is disabled by default. Customized Sybase Installation 5

6 Release New Features Release New Features This section describes the features introduced in this release: Global Usage Monitor Support The Cisco Collection Manager supports Global usage records. These are the records of many applications running over an interface. These records monitor the total network traffic. The Global usage records can show the collected application usage over a specific time period, the peak usage, and the average usage. IPv6 support for NetFlow The Cisco Collection Manager supports a mix of IPv4 and IPv6 traffic from a Cisco ASR 1000 Series Router. IP Version based report Option Template processing from Cisco ASR 1000 Series Router Release New Features This section describes the features introduced in this release: The Cisco Collection Manager supports Cisco IOS NetFlow and the Cisco ASR 1000 Series Router. The Cisco Collection Manager operating with the Cisco IOS NetFlow is part of the Cisco ASR 1000 Application Visibility and Control solution. Refer to the Cisco ASR 1000 Application Visibility and Control Collection Manager User Guide for information on this solution. The Cisco Collection Manager supports a menu-driven installation wizard. The Cisco Collection Manager supports Network Address Translation (NAT) gateway detection through Operating System (OS) fingerprinting. The feature detects prohibited network masquerading (or IP masquerading). Network masquerading is a technique that hides an entire IP address space behind a single IP address in another, often public address space. The Cisco Collection Manager supports all scripting on both the Sybase and MySql databases. In earlier releases, certain scripting was only supported for the Sybase database. The Cisco Collection Manager scripts support both CM:RDR and CM:NetFlow features. Refer to the Cisco ASR 1000 Application Visibility and Control Collection Manager User Guide for more information on CM:NetFlow features. The Cisco Collection Manage supports Anti-SPAM for SPAM RDR. 6

7 Changes in Scripts, Tables, and RDRs Changes in Scripts, Tables, and RDRs Release Changes The following changes were made in Release 3.8.5: Release Table Changes Release RDR Changes Release Script Changes List of tables changed for this release: RPT_VLUR RPT_MEDIA RPT_SPAM RPT_PUR RPT_ZUR RPT_GUR RPT_VLUR RPT_SUR List of RDRs changed for this release. These RDRS are changed to be IPv6 compatible: Virtual Link Usage RDR (VLUR) Media Flow RDR SPAM RDR There are no script changes. Release Changes List of tables changed for this release: RPT_ZUR RPT_PUR RPT_SUR RPT_NUR RPT_TOPS_PEAK_CUMULATIVE RPT_TOPS_PEAK_PERIOD RPT_TOPS_PERIOD0 RPT_TOPS_PERIOD1 7

8 Changes in Scripts, Tables, and RDRs RPT_TOPS_PERIOD0_CUMULATIVE RPT_TOPS_PERIOD1_CUMULATIVE Release Changes Release Table Changes List of tables changed for this release: RPT_LUR RPT_TR RPT_USAGE_NF RPT_TRANSACTION_NF RPT_GLB_USAGE_NF Release Scripts and RDR Changes There are no changes in scripts, or RDRs for Release Release Changes There are no changes in scripts, tables, or RDRs for Release Release Changes There are no changes in scripts, tables, or RDRs for Release Release Changes The below changes are made in the 3.70 release. Release Script Changes The following scripts have been upgraded as part Cisco Collection Manager Release and will not have backward compatibility. You need to run the below scripts with specified options: ~scmscm/scripts/loadsqlprocedures.sh ~scmscm/scripts/droptable.sh ~scmscm/scripts/dbtables.sh ~scmscm/scripts/dbperiodic.sh ~scmscm/scripts/dbfree.sh ~scmscm/scripts/dbconf.sh ~scmscm/scripts/createaggevents.sh 8

9 Changes in Scripts, Tables, and RDRs ~scmscm/scripts/sybrestore.sh ~scmscm/scripts/sybback.sh ~scmscm/scripts/prunetable.sh ~scmscm/scripts/partitions.sh ~scmscm /cm/bin/updatetimezone.sh ~scmscm /cm/bin/jselect-sce-tz.sh ~scmscm/db_maint/ create_periodic_del_procs.sh ~scmscm/setup/monitor/monitor.sh Table Changes List of Tables changed for this release: RPT_SPAM RPT_SUR RPT_LUR RDR Changes New Columns added in SPAM RDR. New Columns added in Real-time Subscriber Usage RDR (SUR) Columns Data Types altered in Link Usage RDR 9

10 Resolved and Open Caveats Resolved and Open Caveats The following sections list the resolved and open caveats for the specific releases. A resolved caveat is one fixed in the listed release. An open caveat is one that exists in the listed release. Release Caveats There are no new open or resolved caveats for Release Release Caveats Resolved Caveats Open Caveats CSCty63870 The Cisco Collection Manager CSV/JDBC adapter processes are not killed when the Cisco Collection Manager restarts. This failure permits the dual processes for the CSV/JDBC Adapter to remain UP. This condition may cause a memory heap error. CSCuc36537 There is a database insert error during the RAG Adapter Aggregation. The Cisco Collection Manager delivers an error message when receiving RDRs. Workaround None Release Caveats Resolved Caveats Open Caveats CSCtx02426 The Cisco Collection Manager does not store the UTC value in the Cisco NetFlow records. CSCtx54792 The Cisco Collection Manager does not upgrade the existing Netflow table data to UTC value. CSCty63870 Multiple adapter processes may boot up after the Cisco Collection Manager restarts. CSCuc36537 There is a database insert error during the RAG Adapter Aggregation. The Cisco Collection Manager delivers an error message when receiving RDRs. 10

11 Resolved and Open Caveats Release Caveats There are no new open or resolved caveats for Release Release Caveats There are no new open or resolved caveats for Release Release Resolved Caveats This section describes the resolved issues in Release 3.7.0: CSCtj66866 The Auto timezone update functionality does not work properly on a Solaris 9 server. CSCtj75103 The prerequisites script generates error messages when run on CentOS and VMware platforms. CSCto08237 Collection Manager database fields for RPT_LUR table columns Up/Down volumes modified. CSCtj09066 Default Vlink Names are reversed in VLINKJ_INI table. CSCtl08183 Updatetimezone.sh gives an error if the timezone is greater than +7 or -7. CSCte54817 CM and RDR servers fail to boot if empty "tags" line in queue.conf. CSCtn20945 Service Control Engine Collection Manage Topper CSV Files Release Open Caveats This section describes the open caveats in Cisco Collection Manager release CSCtq09664 free_db.sh and free_log.sh is not working in the monitor script. 11

12 Obtaining Documentation and Submitting a Service Request Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: Subscribe to the What s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. 12