Prime Performance Manager is a simple-to-deploy and easy-to-use, unified management system that helps you monitor an all-Cisco or multi-vendor and multi-technology network. It allows you to view reports and perform administrative tasks, using a Web 2.0 user interface.
Prime Performance Manager is an integral part of the Cisco Prime product family. You can integrate it with Cisco Prime Central to provide a seamless user experience to view performance reports integrated with network and service topologies. You can also integrate it with Cisco Prime Network, Cisco Prime Network Services Controller, and Cisco Prime Service Catalog.
Prime Performance Manager:
Collects network performance information and generates statistics on delay, jitter, and packet loss in a packet network.
Monitors performance statistics for Internet Protocol/Multi-Protocol Label Switching (IP/MPLS), Carrier Ethernet, mobile backhaul, Mobile Evolved Packet Core (EPC), Code Division Multiple Access (CDMA), and data center, small cell, OpenStack, and optical networks, and technologies. Using a web-based user interface, you can view over 6500 reports in the following areas:
– Application Traffic
– IP Protocols
– IP Quality of Service (QoS)
– IP Service Level Agreements (SLA)
– JMX Applications
– Layer 2 Protocols
– Mobile Internetwork Operating System (IOS) Statistics
Provides an extensive REST interface and other options for easy integration into existing systems and an advanced web-based reporting with many user-customizable features.
Allows you to integrate with the following applications:
– Cisco Prime Central 1.3, 1.4, and 1.4.1
– Cisco Prime Network 3.10, 3.11, 4.0, 4.1, 4.2, and 4.2.1
Allows you to discover network devices by importing the device inventory from other Cisco Prime applications or by running device discovery from Prime Performance Manager.
Allows you to install cross-launch scripts on Prime Network gateways, which enables Prime Performance Manager reports to be launched from the Prime Network GUI.
Synchronizes device lists, credentials, and business tags from Prime Network.
Provides a simple administrative interface that allows you to manage gateways and units, assign devices to units, administer autodiscovery, manage users, administer reports, and other tasks.
Reduces time to troubleshoot and recover from problems that affect service.
Prime Performance Manager features and benefits include:
Carrier class scale—Prime Performance Manager is designed to manage large service provider class networks and provide high performance access to data from multiple simultaneous clients using different access methods. Prime Performance Manager is designed for low startup and administrative costs with support for Cisco Unified Computing System (UCS), Linux, and VMware. The Prime Performance Manager embedded database eliminates third-party license and maintenance costs. Its distributed architecture provides reliability, deployment flexibility, and horizontal scaling to grow with the network.
Prepackaged reports—Prime Performance Manager can generate more than 6500 prepackaged reports on a wide range of network services, technologies, and devices. These reports provide visibility into the network and service performance characteristics of core, aggregation, access, and data center network devices. Reports are automatically generated and do not require complex customization or configuration.
Data collection and processing—Prime Performance Manager standards-based data collection can be applied to any device enabled for Simple Network Management Protocol (SNMP). Summarized reports can be generated in 1-minute, 5-minute, 15-minute, hourly, daily, or longer intervals and can be viewed using the Cisco Prime Performance Manager web interface. They can also be generated as a comma-separated value (CSV) data file for integration with a third-party OSS. Prime Performance Manager also supports Command Line Interface (CLI) based reports by Telnet, Secure Shell Protocol (SSH), and Web Services Management Agent (WSMA).
For hypervisors, Prime Performance Manager supports:
– ESXi/vCenter by SOAP
– Hyper-V by WMI CIM
– Xen and KVM by libvirtd
Data Collectors—Prime Performance Manager supports the following data collectors:
– ICMP ping
– SNMP ping
– StarOS bulk statistics
– Windows Management Interface (WMI)
– gmond (Ganglia)
– OpenStack Ceilometers
– IOS Data Collection Manager (DCM)
– Internet Protocol Service Level Agreement (IPSLA)
– Cisco IOS-XR Web Services Management Agent (WSMA) and Network Configuration Protocol (NETCONF) over SSH
– Small cell 3rd Generation Partnership Program (3GPP) access point (AP) XML, RAN Management System (RMS) Upload Server (ULS), Broadband Access Center (BAC), Device Provisioning Engine (DPE), and Provisioning Management Gateway (PMG)
– Cisco Optical Networking Service (ONS) HTTP bulk statistics
– Cisco Network Analysis Module (NAM) REST, TCP, UDP, and HTTP port probes
– DNS, DHCP, and NTP client queries.
Bulk statistics reports—For the Cisco ASR 5000 and Cisco ASR 5500, the ability to generate reports based on bulk statistics.
Report aggregation and grouping—Prime Performance Manager provides the ability to create reports based on groups of network objects such as interfaces or devices within specified regions.The grouping feature works flexibly according to customized algorithms.
Multi-technology support—Prime Performance Manager supports many network services, technologies, and devices. It facilitates proactive service assurance by allowing you to quickly detect network congestion and other issues.
After you install Prime Performance Manager 1.6 Service Pack 3, run the ppm compilemibs command to compile the MIBs that were added in SP3:
The command compiles MIB files in the /opt/CSCOppm-gw/etc/mibs folder and generates a compiled output file. During execution the system reports inconsistencies like duplicate variables names, duplicate OIDs and missing dependent MIBs. After it has completed, you are prompted to reload the compiled output to the Prime Performance Manager server.
This command is available only on the gateway.
Enabling Third Party CA Certificates for Cisco Prime Performance Manager
To enable third-party Certificate Authority (CA) SSL certificates for your website, you must purchase certificates issued by a third-party CA vendor such as Symantec (previously VeriSign), DigiCert, GoDaddy or other third party vendor. When you order the certificate, the vendors might ask you to enter the number of servers that will be secured with the certificate. This is the number of licenses you want to purchase for the certificate, or the number of web servers on which you're going to install the certificate.
To generate a self-signed key and certificate for Prime Performance Manager:
Step 1 From the Prime Performance Manager gateway, enter the following command:
/opt/CSCOppm-gw/bin/ppm keytool genkey
The command generates the following files:
-rw-r--r--. 1 root root 1647 Jun 12 15:42 server.crt
-rw-r--r--. 1 root root 1054 Jun 12 15:42 server.csr
-rw-------. 1 root root 1675 Jun 12 15:37 server.key
-rw-r--r--. 1 root root 2973 Jun 12 15:42 sgmSslCerts
-rw-------. 1 root root 2896 Jun 12 15:42 sgmSslKey
where server.csr is the certificate signing request file (CSR).
Step 2 Purchase the third-party CA certificate:
a. Log into the third-party CA website and register an account to purchase your SSL certificate.
b. During the order, open the server.csr file listed above in a text editor and copy the entire content including the BEGIN CERTIFICATE REQUEST and END CERTIFICATE REQUEST lines.
c. Paste the content in the form that asks you to enter the CSR on the third-party CA website.
d. Enter any additional required information, then submit the purchase order.
Note When you enable SSL in Prime Performance Manager, the ppm ssl enable command also generates the above key/certificate files. However, the default CSR file is generated with a few items left empty such as: Country Name, State or Province Name, Locality Name, Organization Name. and other fields. If you request a third-party CA signed certificate, do not use the default CSR file during the purchase because it will not pass the CA validation and an SSL certificate will not be issued.
Step 3 Download the signed, third-party CA certificate:
After your SSL certificate purchase request is validated, the CA company issues you a signed SSL certificate. Depending on the vendor, you can have the signed SSL certificate sent to you by email or you can download the certificate from the vendor’s website. Usually the signed SSL certificate is named <your-domain-name>.crt. (The certificate file can also have the extension DER, PEM, or CER). Save the signed SSL certificate file locally for later import into Prime Performance Manager.
Note Some CA vendors might also send you an intermediate certificate file. If so, download it and save locally.
Step 4 In Prime Performance Manager, enter the following command to import the signed third-party CA certificate:
where the <cert_filename> is the signed CA certificate from the CA vendor.
Note If you received an intermediate certificate file from the CA vendor, import it before you import the above signed certificate. Contact the CA vendor for any technical support and service.
After the import, the old self-signed certificate is replaced with the imported one.
Step 5 Complete the “Enabling SSL on a Gateway or Collocated Gateway and Unit” procedure in the Cisco Prime Performance Manager 1.6 User Guide to configure SSL for the gateway.
The web interface is now be secured by the signed CA certificate.
Note Gateway and unit communication uses Java RMI. After SSL is enabled, the gateway and unit also uses SSL to secure the communication. However, because the unit is not open to end users, a signed CA SSL certificate is not required for gateway and unit communication. Therefore, you can still use the default Prime Performance Manager self-signed certificate for the unit servers.
/opt/CSCOppm-gw/bin/ppm ifnameformat [ desc | alias | both | ifindex ]
Defines the format for displaying interface names in the Prime Performance Manager GUI:
desc—Only the interface description is displayed.
alias—Only the interface alias is displayed.
both—Both the interface description and alias are displayed.
ifindex—Displays the interface by its Interface Index value, a unique identifying number associated with a physical and logical interfaces.
You can run this command on the gateway, and it will update all units.
Note After you change the interface name format, restart the gateway and all units.
Available in GUI
Release 1.6 Service Pack 2 New Features and Enhancements
Cisco Evolved Programmable Network
Add device.properties entries for Cisco ME 4620, 4605, and 4601 Optical Line Terminal devices
– Divided the BGP Routes report into a separate category
– Sensor report polling updates
Improve performance of web report lookups and drop down menu
Allow users to save custom column exports and reload and run later
– New schemas and new counters
– Data type counter updates
– Support for EPDG, EGTPC, HNBGW, TAI, MME, ECS,SAMOG, EPDG, EGTPC, HNBGW, HeNBGW, ICSR
– Divided MME into multiple all-counter reports
StarOS 18.1 - new counters
StarOS 17.2 - data type changes
– KPI reports - NOS Guide v7.0 - MME/HSS/IMSA
– Enable exporting for all counters: vlan-npu, link-aggr, mipv6ha, mvs, cscf
– StarOS 17.3 and 15.6 regression testing
Aggregate unknown ports into single other category
Added other reports
SCS 4.1 - AP 3.5.x MR: new AP counters
Reports: faster time to support new counters driven by AP counter definition file and to support new counter updates to the current report XML files
Import PM files from past time periods
RMS 3G to menu group automatic documentation
Update default GDDT inventory mapping properties
Group file update: Enterprise and site
Workaround for AP PM file with an out-of-spec granPeriod
Support decreasing UPTIME value in PM file
Support missing PM file
Handle malformed XP XML data files
Combine all 3G KPI values into one report
AP inventories name changed in SmallCell.groupby
Improved handling of missing and daily AP data files
Update grouping categories based on customer input
Show non-graphic columns without specifying DN_prefix as keys
Report XML changes
Add documentation for REPORT_MUST_RUN_INTERVAL
Added “Prime Performance Manager and Prime Carrier Management Geographical HA Deployment Guide” document to runtime image
GUI/NBAPI: allow giant custom names
Release 1.6 Service Pack 2 Documentation
The following sections provide new or updated documentation covering key Service Pack 2 features and enhancements;
You can export Cisco Prime Performance Manager report data to CSV files, which you can display in a spreadsheet or database management application for further review and analysis. The data exported depends on the output mode. In Graph mode, the summary table is exported. In Table mode, the detailed data table page is exported.
To export a report to a CSV file:
Step 1 From the Performance menu, choose Reports.
Step 2 Navigate to the report you want to export to CSV.
Step 3 On the report toolbar, click Export Report Page as CSV.
Note Report Page only applies to Table view. Only the table page currently displayed is exported. If you want to export all the Table view data, set the page size to the maximum, export each page, then merge the files in your spreadsheet or database application.
Step 4 In the Export Report Columns to CSV dialog box you can do any of the following:
By default, all report columns are selected for export. To remove a column, select it and click Remove. The column moves to Available Columns. To add the column, select it and click Add
To change the order in which columns appear in the CSV file, select the column and click Move Up or Move Down. Columns at the top appear first in the CSV; columns at the bottom appear last.
To save the customized columns for future exports, click Save.
To load a previously-saved column filter, click Load.
Note Columns in bold are the table keys.
Step 5 When finished, click Export to export the data and leave the dialog displayed, or Export and Close to export the data and close the dialog.
Creating a Mail Report
You can create report emails for report graphs or tables in the views, dashboards, network or device reports, or star graphs. Creating a report email creates a schedule for sending a report, view, or dashboard graph to individuals by email. Graphs can be included as attachments or embedded in the email in PNG, JPG, GIF, or PDF format.
To create a report email:
Step 1 Verify the SMTP server is configured for Prime Performance Manager:
a. From the Administration menu, choose System Settings.
b. In the System Configuration Settings, verify an SMTP server is entered in the SMTP Mail Server field. If not, provision the mail server that Prime Performance Manager should use for outgoing emails. This can be the mail server IP address or host name. In many cases, you can enter localhost. If needed, consult your network administrator.
Step 2 From the Performance menu, choose Reports, Views, or Dashboards.
Step 3 Navigate to the report containing the graph(s) for which you want to create an email report.
Step 4 Perform one of the following, depending on what you want to email:
Entire report—Click Email Report on report toolbar.
An individual report graph—Click Email Report on the vertical toolbar to the left of the graph.
Step 5 In the Email Report dialog box, complete the report fields.
Email Configuration—Provides the email address and subject:
Email From Address—Enter the email address that you want used as the report sender. This is the address to which replies are sent. You can enter any legitimate email address. However, the intent is for the user creating the report email to enter their email address or an alias to which replies can be sent, for example, firstname.lastname@example.org.
Note If a global email from address is configured, that address automatically populates the Email From Address field. You can remove or edit the global address, however. The global email from address is configured in Administration > System Settings > System Configuration.
Email To Addresses—Enter the email address(es) of the individual(s) to whom you want to send the report. The addresses must be legitimate. If you enter multiple addresses, separate the addresses with semicolons and no spaces. You can enter an email alias or list as long as it is recognized by the email server.
Email Subject—Is the subject line in the email that is sent. It is required. You can enter variables that will list the report and server names in the email subject:
– $name—The ReportMail name.
– $server—The gateway server name.
For example, if your gateway server is gateway_123, your ReportMail is named SampleReport, and you type $name from $server in the Subject field, the email subject will be SampleReport from gateway_123.
Note $name only applies to scheduled report emails. If you click Send Now, $name is replaced with “current_state” indicating the report email current state is the time you clicked Send Now.
Output Configuration—Defines the report output and email delivery.
Output Format—Enter the format in which you want the graph to be sent. Options include PNG (default), JPG, and GIF graphic formats, as well as PDF and CSV. File sizes will vary, In one sample report, the file sizes were:
– PNG: 202.5 K
– GIF: 91.1 K
– JPG: 209.1 K
– PDF: 45.6 K
– CSV: 42.2 K
PNG produces the best overall results, depending on the graph complexity, so is the format you should generally use. PDF is not recommended for complex reports or views with multiple graphs, GIF image quality is lower overall.
Embed Image—If checked, the image will be embedded in the email. If not checked, it will be attached to the email.
Width—If you want to change the width, enter it in this field. The default is 1280 pixels.
Height—If you want to change the width, enter it in this field. The default is 1024 pixels.
Note Embed Image, Width, and Height apply only to PNG, GIF, and JPG output formats.
Note The width and height do not guarantee the image size will match exactly. However, the resulting image will generally be close to the width provided and the height will vary depending on the image itself.
Schedule Configuration—Allows you to define a report email schedule:
Scheduled—If selected, displays fields that allow you to schedule the timeframe and frequency to email the report. If you do not want to schedule the report, you can click Send Now to send the report immediately.
Name—Allows you to add additional information to distinguish the report when viewed in the Report Mail Editor. Spaces and special characters are not allowed, with the exception of underscores and hyphens, which are allowed.
Enabled—If checked, enables the email report. If not checked, the email will not be sent. This parameter allows you to create the report and enable it at a later time. You can also disable the report email temporarily at a later point.
Repeat—Enter the interval at which you want the email report to run:
Frequency—Sets the number of times the report should run for the selected Recurs Type. For example, if you select a recurs type of hourly and enter a frequency of 4, an email will be sent every four hours. The Start Date and End Date are optional fields that further refine the time that emails are sent. If you enter a start date, no emails are sent prior to that date. Similarly, if you enter an end date, no emails are sent after that date. If you do not enter dates, no date restrictions are applied.
Start Date—Enter the report start date by clicking the field and choosing the start date from the calendar.
Beneath the Start Date, choose the days you want the report run. The days selected are another way to restrict when emails are sent. If the day is selected, emails are sent. If the day is not selected, no emails are sent.
In other words, all selected criteria must be met for an email to be sent. The day must be selected, the date has to be in range (if dates are specified), the time of day has to be between the times specified (if they are not set to the same time).
End Date—If you entered a start date, enter the end date by clicking the field and choosing the end date from the calendar.
Begin Time—Enter the report start time: hour (24-hour clock):minute
End Time—Enter the report end time: hour:minute
Note If both times are set to 0:00, no time of day restriction is applied.
Note If the report mail runs near the top of the hour, which is the default, the Prime Performance Manager will not have time to process all the last time interval statistics. If recipients receive an email at, for example, 10:04. The report will include hourly data up to 9:00 but not 10:00 because data collecting and processing takes time. Adding an offset to the start and end times can produce better results. If the report email is scheduled for ten minutes after the hour, time is allocated for the data to be processed. For example, if you set the Start Time and End Time to 12:10, the report mail will run at 10 minutes after the hour, every hour and have sufficient time to collect statistics for the 10:00-11:00 interval.
Step 6 Perform one of the following:
If you are not scheduling the email, click Send Now.
If you scheduled the email, click Save.
The report is added to the Network Report Mail Editor screen. To view it, from the Network menu, choose Report Mail Editor.
Collecting Small Cell Access Point Inventory Data
Note The following section includes updates that were made in Service Pack 2.
Small cell access point (AP) inventory data is static, and not performance KPIs for which you can create threshold crossing alerts in Prime Performance Manager. Collecting AP inventory data can be used to group AP performance reports. For example, you might want to group AP performance reports by a particular AP site or Home Node B Gateway (HNBGW).
To collect AP inventory data, you must provide information to the ApInv.properties file located in the /opt/CSCOppm-gw/etc/apInventory/template/ directory. ApInv.properties collects AP inventory from:
Get Device Data Tool (GDDT). This script is included in the Provisioning Management Gateway (PMG) component of the RAN Management System (RMS).
DNPrefix. DNPrefix is contained in normal AP performance file polled by other collectors.
Note Prime Performance Manager merges inventory data from DNPrefix and GDDT. When merging for a specific AP node, the inventory data coming from GDDT has a higher priority and overrides the DNPrefix data.
Information you will provide includes:
The field name that represents the unique AP ID.
The fields to extract from the exported GDDT CSV file.
The path of the file exported by the GDDT script.
The default GDDT output file extension is.csv.
The local directory where the exported GDDT file will be copied.
Interval in (hours) at which Prime Performance Manager retrieves the GDDT exported file from PMG. The default is 24 hours.
The length of the time, in days, that Prime Performance Manager should keep copied CSV files. The default is three days. Files are archived and deleted after this time period.
Indicator telling Prime Performance Manager how to treat the field, Role, in inventory data. If this property is set to false, Prime Performance Manager assigns Role with the value contained in the GDDT output identified by the field, Enterprise, or DNPrefix, identified by the field, Enterprise. Otherwise, Prime Performance Manager treats Role as a binary value, namely Enterprise or Residential.
The name of the DNPrefix output field to reference for the Role value. The default is Enterprise.
The name of the GDDT output field to reference for the Role value. The default is Enterprise,
The number of attempts allowed to retrieve the GDDT output file before considering it a failure. The default is 3.
The interval, in minutes, between each adjacent attempt to retrieve the GDDT output file, The default is 3 minutes.
Prime Performance Manager uses a minimum set of fixed field names, shown in Table 1-2. To generate small cell reports, the constructed AP inventory data must have corresponding fields names. The preferred method is to configure RMS to have field names that match the names used by Prime Performance Manager for each inventory item, whether it is from GDDT output or DNPrefix. For example, when configuring the inventory item, site, (for DNPrefix or GDDT output), the name, SITEID, should be used to match the site name used by Prime Performance Manager. If you cannot name inventory items on the RMS side, you must do additional field name mapping on the Prime Performance Manager side so Prime Performance Manager knows what field to look for a certain inventory items. The field mapping can be configured in /opt/CSCOppm-gw/etc/apInventory/template/FieldName.properties. After you modify FieldName.properties, restart the gateway and units. See Restarting Gateways and Units.
Table 1-2 AP Inventory Field Names
Field Name Used by Prime Performance Manager
Unique ID for the Cisco ASR 5000 chassis at discretion of the SP. This tag is only provided for HNB.
HNB-GW service name within a chassis. Same value as in ASR 5000 CLI. This tag is only provided for HNB.
Unique ID for Cisco ASR 5000 chassis at discretion of SP. This tag is only provided for HeNB.
HeNB-GW service name within a chassis. Same value as in Cisco ASR 5000 CLI. This tag is only provided for HeNB.
Unique ID for SeGW chassis at discretion of SP. In case of Cisco ASR 5000 SeGW, the value is the same as for HNB-GW tag.
Unique ID for SeGW service within the chassis. In case of Cisco ASR 5000 SeGW, the value is the same as for HNB-GW-SRV tag.
Geographical area of Small Cell. Optional in some deployments - empty value or no tag.
Numeric enterprise ID for Small Cell. Empty value or no tag for Resi APs.
Numeric enterprise Site ID for Small Cell. Empty value or no tag for Resi APs.
The device ID.
The ID of the chassis of the multi-stack AP. Empty value or no tag for single-stack AP.
The HNB ID or HeNB ID.
The optional secondary ID for the AP, at SP discretion. Tag can be missing or have empty value.
3G or LTE
Live HW Model
After you modify ApInv.properties, it is automatically sent to all connected units. You must restart the units. A sample ApInv.properties file is shown below:
# What capability a device should have to enable this template.
deviceCapability = RMS_PMG_PERF
# Name of the field representing the unique id of Access Point node.
apNodeIdField = EID
# A list of fields users want to extract from GDDT exported csv file. Empty
# value or non-explicitly specified value means users want to extract all fields
# File extension of the GDDT output file, will use '.csv' as default
# if not explicitly specified.
# Local directory which the GDDT exported file will be copied to.
dropDir = /tmp/apinv/
# Interval(hours) in which PPM regularly pull GDDT exported file from RMS-PMG.
updateInterval = 24
# Length of the time(days) PPM will keep those copied csv files. Those pulled
# files will be archived and deleted after this period of time.
ageOutInterval = 3
# Toggle telling PPM how to treat the field 'Role' in inventory data. If this
# property is explicitly specified with 'false' value, PPM will assign 'Role'
# with the value contained in GDDT output(identified by field 'ENTID') or
# DNPrefix(identified by field 'EnterPriseID'). Otherwise, PPM will treat 'Role'
# as a binary value, namely Enterprise or Residential.
roleAttrBinary = true
# Name of the field in DNPrefix which we refer to for the value of 'Role',
# default with 'Enterprise'
entidInDnprefix = Enterprise
# Name of the field in GDDT output which we refer to for the value of 'Role',
# default with 'Enterprise'
entidInGddt = Enterprise
# Number of attempts allowed to retrieve GDDT output file before considered failure.
retryCount = 3
# Interval between each adjacent attempt to retrieve GDDT output file, in minutes.
retryInterval = 3
GDDT and DNPrefix field names must match the field names used by Prime Performance Manager listed in Table 1-2. If the field names do not match, configure the mapping in the FieldName.properties to map from GDDT to Prime Performance Manager or from DNPrefix to Prime Performance Manager.
Service Pack 2 adds automatic update capability to dashboards. Icons are added to dashboard toobars to allow you to disable and enable automatic updates as well as refresh the dashboard manually.
Extend Device Custom Name Limit
The ppm allowgiantnames command allows you to extend the limit allowed for device custom names from 100 to 255 characters.
enable—Enables giant names and allows custom names for devices to be up to 255 characters.
disable—Disables giant names and reduces the length for custom names to 100 characters.
status—Displays the status of the giant names option, either enabled or disabled.
Available in GUI
Setting Up Small Cell Access Point Performance Monitoring
The RMS 3G AP Single DB Table report examines specific counters gathered by Prime Performance Manager for the Cisco Small Cell solutions during debugging. Only enable this report when Prime Performance Manager is monitoring a small number of APs during lab testing or other situations requiring detailed debugging of all counters.
For best performance, enable only the RMS 3G AP Single DB Table report and set the following value in the gateway and unit System.properties:
REPORT_MUST_RUN_INTERVAL = 259200000
Release 1.6 Service Pack 1 New Features and Enhancements
New features and enhancements provided in Prime Performance Manager 1.6 Service Pack 1 include:
Cisco Evolved Programmable Network
Cisco IOS XR Release 5.1.4
Cisco Catalyst 3850 Series Switches
Cisco Carrier Packet Transport (CPT) 126.96.36.199
– CPT optical power reports through HTTP bulk statistics
– Additional ISIS reports
Ceph Giant release
GUI and email report enhancements
StarOS Release 15.6, 17.1, and 17.2
StarOS KPI report updates
Additional StarOS schema file exports
Column selection from TableView WebReports and REST API
Prime Performance Manager 1.6 new features and enhancements are provided in the following sections. You can view a detailed list of changes in this release after installation by choosing Help > READMEs and CLI Commands > CHANGES.
Alarm improvements include:
Variables for customizing alarm and event messages
CLIs for generating system alarms
Ability to create compound TCAs
Customize subject of TCA email notification including variables
Upstream filter by device groups and report policy
Events and alarms per tenant, events, and alarms
Host and service up/down events
Send TCA alarms to Moogsoft
Cisco Prime features include:
Cisco Prime browser compatibility: Firefox 24, Firefox 24 ESR, Internet Explorer 9, 10, and 11, XWT 1.7.3.x
Inventory modifications for Cisco Carrier Packet Transport (CPT) cards imported from Prime Network
Prime Carrier Management compatibility:
– Prime Carrier Management April, 2014 release
– Cisco Prime Central 1.3
– Cisco Prime Network 4.1
Satellite Network Virtualization (nV) Switching System cluster support, new topologies, and scale
Remove Prime Central integration when Prime Performance Manager is uninstalled
Upgrade from Prime Performance Manager 1.5.1 to 1.6
Upgrade Java to 1.7.0_60
Upgrade XWT to Version 188.8.131.52
Support for vSphere 5.5 and 5.5 Update1
New collectors include:
DHCP and DNS probes and reports
HTTP bulk statistics collector for Cisco ONS and Cisco CPT devices plus support for static GNE and ENE mapping
Multiple collectd collection directories
NAM collector through REST APIs and ART reports
Windows Management Instrumentation (WMI)
Improved Ceph pool statistics
Device uptime for hypervisors
HTTP/HTTPS remote check
ICMP and SNMP ping
TCP remote check
New and updated Data Center devices and technologies include:
Ability to append service profile names to Cisco UCS M-Series Modular Servers blade numbers in dashboards
Device and OS Support
New supported devices and operating systems include:
Cisco ASR 903 and 920 IOS XE 3.13
Cisco Carrier Packet Transport:
– Modification of port use based on software version
– New sysObjectIDs for Cisco CPT 200/600
– Support for Cisco CPT 9.7.01 uniform login feature
Note We sometimes update the documentation after original publication. Therefore, you should review the documentation on Cisco.com for any updates.
Accessibility Features in Prime Performance Manager 1.6
The Prime Performance Manager 1.6 software does not provide any accessibility features. All product documents are accessible except for images, graphics, and some charts. If you would like to receive the product documentation in audio format, braille, or large print, contact email@example.com.
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: www.cisco.com/go/trademarks. 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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.