Release Notes for Application Assurance Networking, Version 4.0

Transcription

1 Release Notes for Application Assurance Networking, Version 4.0 Overview These release notes support the Avaya Application Assurance Networking (AAN) product line, Version 4.0. This product line includes the following: Converged Network Analyzer (CNA) Adaptive Path Controller Enterprise (APC-E) Adaptive Path Controller-Internet (APC-I) CNA server platforms For a complete list of certified platforms, see Certified Platform Models on page 5. Release notes are periodically updated. For detailed information about your product, see the following documents: Application Assurance Networking Installation Guide, Application Assurance Networking Fundamentals Guide, Application Assurance Networking Monitoring Guide, Application Assurance Networking Operator Guide, Application Assurance Networking Command Reference Guide, Adaptive Path Controller Enterprise Guide, Adaptive Path Controller Internet Guide, Application Assurance Networking Appendices, To download the latest release notes, and other documentation, see Avaya strongly recommends that you run the latest version of the software. Please contact your Avaya sales representative for details on how to obtain the AAN 4.0 software release. For information on how to install the software, see the Application Assurance Networking Installation Guide. These release notes cover the following topics: Changes and New Features in Version 4.0 on page 2 Compatible CNA agent platforms on page 3 Certified Platforms on page 5 Fixes in Version 4.0 on page 10 Known Issues in Version 4.0 on page 17 Technical Support on page 25 Documentation Feedback on page 25 Issue 3 September

2 Application Assurance Networking Release Notes for Software Version 4.0 Changes and New Features in Version 4.0 AAN Version 4.0 is the successor release to CNA Version Changes in Version 4.0 The following feature have changed in Version 4.0: Upgrading the CNA server and removal of the license file Use the following procedure to upgrade your product and remove the license file:! Important: Important: Version 4.0 does not use license files. The 3.X license must be removed as instructed in the upgrade procedure. 1. Place the upgrade CD in the drive of a computer or server with access to your network. 2. Copy the file 4_0_0GA.img from the CD to a server with FTP capability on your network. The CNA server targeted for the upgrade should be able to reach this ftp server. 3. Log into the CNA server command line and enter enable mode. 4. From the CNA server command line, enter the following command: ls xml The result of this command produces a directory list containing a file with a.xml extension. 5. From the directory list, locate the.xml file and enter the following command: delete <filename.xml> 6. From the CNA server command line, run the following command: reload 7. From the CNA server command line, run the following command (replacing the placeholders with the appropriate FTP server information): restore image ftp://username:password@server/pathtofile/4_0_0ga.img 8. Once the image download is complete, be sure any configuration changes have been saved. From the CNA server command line, run the following command to complete the upgrade: reload Trending calculated bandwidth and 95th Percentile Beginning with Version 4.0, trending calculated bandwidth and 95th percentile are no longer supported. The CPU temperature custom trend report is not supported in Version 4.0. This custom trend report is still visible in the CNA Viewer; however, it is obsolete and will be removed in a later version of the software. 2

3 Compatible CNA agent platforms The application model has been changed from web to voice Starting in CNA 4.0 the default application model has been changed from web to voice. Customers using a 3.x version and planning to upgrade to 4.0 should check the CNA config to see what application model is applied in any configured active-measurement groups. On a 3.x CNA, if no application model is listed, then the default 'web' application model is in place. Any instances of the web application model would need to be explicitly configured once the upgrade from 3.x to 4.0 is complete. New features in Version 4.0 The following features are new in Version 4.0. Web User Interface Improvements The Web User Interface (UI) has been redesigned to include three screen views. The screen views are server (CNA), agent (Chatter), and endpoint (VMM). Each view can be displayed by selecting the desired tab at the upper left panel. Beginning in this release, the Web control panel will be known as the CNA Viewer (Viewer). Voice Monitoring Manager (VMM) aggregation The CNA Viewer now includes an aggregated view of multiple VMM servers from one console. Use the endpoint screen view to display the VMM server information. Improved Trending The CNA Viewer now includes a Trending Wizard that guides the user through the process of creating user-defined reports. Compatible CNA agent platforms Specific devices and the corresponding firmware/software versions that include compatible CNA agents are listed in Table 1. For a list of CNA certified devices, see Table 2: Certified Platform Models. Table 1: Compatible CNA Agent platforms and firmware/software versions Vendor Product Model(s) Firmware/Software Version Notes Avaya CNA Server Any server platform listed in Table 2. Avaya CNA Agent Device Axis 83+CNA agent device CNA 3.0. and later CNA 3.0. and later Embedded agent is included with the CNA server software Dedicated standalone agent platform 1 of 2 Issue 3 September

4 Application Assurance Networking Release Notes for Software Version 4.0 Table 1: Compatible CNA Agent platforms and firmware/software versions (continued) Vendor Product Model(s) Firmware/Software Version Notes Avaya IP Telephone SW 4621SW 4622SW R2.3 H.323 and later and R2.2.2 SIP VPNremote Phone R2.1 Avaya IP Telephone 4625SW R2.8 H.323 and later VPNremote Phone R2.1 Avaya IP Telephone 96XX R1.2 H.323 and later Avaya Media Gateway G250 Vintage and later Avaya Media Gateway G350 Vintage 67 and later Avaya Security Gateway SG203 VPNos and later Avaya Security Gateway SG208 VPNos and later Extreme L3 switch BlackDiamond 8800 BlackDiamond Summit X450 XOS 11.3 and later 2 of 2! Important: Important: Only compatible agent device and firmware/software versions should be used with CNA. Please ensure that incompatible devices and versions do not register with the CNA server, as those configurations have not been tested and may result in unexpected behavior within the devices or within CNA itself. Use the commands show cna-agent detail and show cna-agent to check which devices are registered with CNA and their respective types and versions.! Important: Important: When one or more Avaya 4600 series IP phones running software versions older than version R2,8 are part of a CNA agent deployment, the maximum number of CNA agents in the deployment must total no more than 64. 4

5 Certified Platforms Certified Platforms Version 4.0 software supports multiple server platforms. The minimum requirements for CNA software running on any platform include an Intel CPU, 1.5GB of RAM, an 80GB hard disk, a CD-ROM drive, and one or more 10/100/1000 Ethernet network interfaces. Specific model and configuration requirements are listed in Table 2.! WARNING: WARNING: Version 4.0 cannot run on the RouteScience PathControl 3000 or 5000 series platforms. RouteScience PathControl devices only support ANS 6.4 and earlier software releases. Table 2: Certified Platform Models Platform Avaya Material Code Components Included Part Numbers IBM x3250 N/A Base Server (512 MB RAM) 512 MB memory upgrade (2 x 512 MB) 160 GB 15K disk drive Pro/1000 PT dual port NIC (Intel) IBM x3550 N/A Base Server (1.0 GB RAM) Xeon processor ECC DDR2 Chipkill (2X1GB) 73GB, SAS, 3.5 inch 15K Hot Swap Hard Drive HDD Controller: IBM ServerRAID 8K-l SAS Controller Card Dual port ethernet adapter (Broadcom) Redundant power supply PCI-X riser card 43652BU 41Y M Y U 40K M K R Y R R2816 Dell PowerEdge 850 N/A Base Server 2GB RAM GB SATA HDD CD-ROM Drive Optional 10/100/1000 adapter NOTE: A minimum of 1.5 GB RAM is required. 1 of 4 Issue 3 September

6 Application Assurance Networking Release Notes for Software Version 4.0 Table 2: Certified Platform Models (continued) Platform Avaya Material Code Components Included Part Numbers Dell PowerEdge 1950 N/A Base Server: Dual Core Xeon Processor MB cache, 3.00GHz, 1333MHz FSB, PE 1950) Processor: Dual Core Xeon 2nd Processor MB cache, 3.00GHz, 1333MHz FSB, PE Memory: 4GB 667MHxz (4X1GB), Dual Ranked Fully Buffered DIMMs HDD: 146GB, SAS, 3.5 inch 15K RPM Hard Drive HDD Controller: PERC 5/i, Integrated Controller Card NIC: Dual Embedded Broadcom NetXtreme II 5708 Gigabit Ethernet NIC CD-ROM: 24X IDE CD-RW/DVD ROM Drive for PowerEdge Servers, All OS Dell PowerEdge 2950 N/A Base Server Riser, PCIE, PE INTEL Pro 1000PT CU,DUAL,PCIe PE2950,4MB/2.66GHZ,1333FSB,2 ND PRC X6 Backplane,3.5HDD, PE PE2950, 4MB/2.66GHZ, 1333FSB X DVD-ROM, PE PERC5/I, X6, Integrated, PE DRAC5, PE29/ GB, SAS, 3.5IN, 10K, PE Note: Note: Two minimum and 6 maximum 4GB, 667MHZ, (4X1GB), 2R, FBD BCOM, TOE, Not Enabled RDNT PWR SPLY, NO Cord, PE2950 Rapid/Verse Rail, Sliding, PE2950 LPE1150, 4GB, OPT, HBA, PCIe (for SAN attached only) of 4 6

7 Certified Platforms Table 2: Certified Platform Models (continued) Platform Avaya Material Code Components Included Part Numbers HP ProLiant DL320 G4 N/A Base Server (with 512MB RAM) 1GB RAM B B21 512MB RAM B21 80GB SATA HDD B21 CD-ROM Drive B21 Optional 10/100/1000 adapter B21 NOTE: A minimum of 1.5 GB RAM is required. HP ProLiant DL360 G5 N/A Base Server Processor Upgrade (2 Dual Core Xeon 5140) B L21 Processor Upgrade Kit 2GB RAM Add-on Kit B21 1GB RAM (2 x 512 MB) B21 80GB SAS HDD B21 Combo Drive B21 E200I Controller B21 SA E200 64MB Cache B21 PCIe 1000T Gig Adaptor B B21 Avaya S8500C No longer available for purchase. Base Server(3.0 GHz P4, 512MB RAM) 2 GB RAM (1 GB x 2) N/A 80GB SATA HDD Dual port 10/100/1000 adapter Note: Note: A minimum of 1.5 GB RAM is required. This device as specified has 2.5 GB RAM. IBM x305 No longer available for purchase. Base Server (2.8 GHz P4, 256MB RAM, 40GB EIDE HDD) X 256MB RAM 33L MB RAM 33L5038 x 2 Dual GigE adapter 31P6401 NOTE: A minimum of 1.5 GB RAM is required. 3 of 4 Issue 3 September

8 Application Assurance Networking Release Notes for Software Version 4.0 Table 2: Certified Platform Models (continued) Platform Avaya Material Code Components Included Part Numbers IBM x306 No longer available for purchase. Base Server(3.0 GHz P4, 256MB RAM) 512MB RAM 88364SU 06P MB RAM 06P4049 x 2 80GB SATA HDD 73P8002 Dual GigE adapter NOTE: A minimum of 1.5 GB RAM is required. 73P4201 IBM x306m No longer available for purchase. Base Server(3.0 GHz P4, 512MB RAM) 512MB RAM 88491OU 30R5148 x 2 80GB SATA HDD 39M4500 Optional dual port 10/100/1000 adapter 73P4201 NOTE: A minimum of 1.5 GB RAM is required. IBM x335 No longer available for purchase. Base Server (3.0 GHz Xeon, 512MB RAM) 2nd CPU 8676M1X 02R8959 1GB RAM 33L5039 x GB SCSI HDD 32P0727 Dual GigE adapter 31P6401 NOTE: A minimum of 1.5 GB RAM is required. IBM x336 No longer available for purchase. Base Server (3.2 GHz Xeon, 1GB RAM) 2nd CPU U 25R8905 1GB RAM 73P MB RAM 73P GB SCSI HDD 90P1305 Dual port 10/100/1000 adapter 73P4201 Redundant PS 90P5280 NOTE: A minimum of 1.5 GB RAM is required. IBM x345 No longer available for purchase. Base Server (3.2 GHz Xeon) 2nd CPU 8670G1X 23K4523 1GB RAM 33L5039 x GB SCSI HDD 32P0727 Dual GigE adapter 31P6401 Redundant PS 74P4965 NOTE: A minimum of 1.5 GB RAM is required. 4 of 4 8

9 Supported Browsers and Operating Systems! Important: Important: The official End-of-Life date for all RouteScience PathControl 3000 and 5000 series hardware platforms was December 31st, No new ANS 6.4 software maintenance releases or hardware maintenance contracts will be made available. An upgrade program is in place to migrate RouteScience PathControl customers to current IBM xseries rackmount servers. For more information on the upgrade program, please contact your Avaya sales representative. Supported Browsers and Operating Systems The CNA Viewer uses JRE 1.5 update 11. Java update 11 addresses both a security advisory issued by CERT and the change to adjust the Daylight Saving Time (DST) rules in accordance with the U.S. Energy Policy Act of Note: Note: Where the JRE is installed prior to CNA, you must update the JRE to update 11 manually. The CNA Viewer has been tested on the following configurations Table 3: Table 3: Supported Platforms and Operating Systems Operating System Browser Microsoft Windows 2000 Internet Explorer 6.0 Microsoft Windows XP Internet Explorer 6.0, 7.0 Firefox 2.0 Issue 3 September

10 Application Assurance Networking Release Notes for Software Version 4.0 Fixes in Version 4.0 Table 4 lists software fixes included in the Version 4.0 release: Table 4: Fixes in Version 4.0 Reference Number Issue Resolution 7591 Change performance-group command to site command. The performance group commands have been deprecated in Version 4.0. The performance group commands will be translated to the site commands Loss and reporting in Chatter. The chatter loss rate is computed as an average over a sliding window containing the loss values from the last 10 tests. A new loss rate value is computed every time a new test arrives, and the last 150 loss rate values are kept Traceroute holes cause major data loss Incorrect show run date stamp format. Previously, end-to-end test results such as ping and rtp were not redistributed to edges of non-contiguous paths. For example, if the path between two agents obtained through traceroute contained holes, no end-to-end data was mapped to any of the edges in the path. With this fix, ping and rtp data are now mapped to any edges that have been discovered in a path, irrespective of if the edges form a continuous path or not. This way, valuable end-to-end data is not lost. The show run date stamp is changed to yyyy-mm-dd. 1 of 7 10

11 Fixes in Version 4.0 Reference Number Issue Resolution Adding or removing a server to/from a hive Moving module engine across interfaces requires a reload Underlying EFC ACL is not updating correctly. When attempting to remove a server from a hive with the chatter leave-hive command, or to join a server to a hive with the chatter join-hive command, it is strongly suggested that the user first verify the operational status of the hive by running the show hive command from any server in the hive. If all of the hive members are not included in the output, or if the status of any of the hive members shown is other than "OK," it is recommended that the remove or join operation not be performed until such time as these conditions are met. If you need to move module engine from the default interface (Ethernet0) to Ethernet1, you will need to make the changes, save the running config, and reload the server. The default ACL rules have been updated to include a new rule. The new rule allows Port 6343 UDP to open as the sflow default port Inconsistent.name files. The.name files are no longer used in Version 4.0 for naming. The upgrade to Version 4.0 includes the conversion of the entries in the.name files into subnet-alias commands, as well as the removal of the.name files. The latter is used to know when the upgrade does not need to happen again. 2 of 7 Issue 3 September

12 Application Assurance Networking Release Notes for Software Version 4.0 Reference Number Issue Resolution Explicit knob to control the adequacy test Limit Configuration template content Deprecate the performance-group command in Version 4.0 The adequacy knob controls the number and nature of links on which enough performance evidence needs to be acquired before the prefix is allowed to move to a new link. The configuration template content has now been limited to include only a basic set of commands that apply generically to all customers. Commands that used to assume the need of EFC or per-host measurement and decision policies in the configuration have been removed. The performance-group command was deprecated in Version 4.0. The site command is now used The command ip http server on under module ustat is no longer a default setting The show last subnet all hrtt command reports an error The CNA Viewer applet launches behind the browser launch window. After upgrading to Version 4.0, customers interested in using the passive server-based measurements (GIF downloads) must add ip http server on and save the configuration. The show last commands are no longer valid in Version 4.0. The show last commands have been removed from the CLI. The CNA Viewer applet is now launched in front of the browser launch window. 3 of 7 12

13 Fixes in Version 4.0 Reference Number Issue Resolution Removal of rsync commands from system The colors in the CNA Viewer are not consistently assigned Change persistent hosts default to ENABLE and increase persistent hosts timeout. The rsync command set is no longer supported in Version 4.0. This includes the removal of rsync enable, rsync target, and rsync user name. The ColorMap.txt file has been modified in the following ways: The entry with ID notrescued: <colordefinition id="notrescued" hex="cc0000"/> Has been given the new name "subnetsintrouble" to reflect the change in the title in the CNA Viewer. The entry now looks like: <colordefinition id="subnetsintrouble" hex="cc0000"/>. Customer who have a modified ColorMap.txt file should replace the ID "notrescued" with the new id "subnetsintrouble". Also, restoring a new image will overwrite the custom ColorMap.txt file so any customization will need to be reapplied after the new image is installed. Persistent hosts default is changed to enable and the persistent hosts timeout is increased.! Important: must change or remove the persistent host default from enable to disable. Important:APC-I customers 4 of 7 Issue 3 September

14 Application Assurance Networking Release Notes for Software Version 4.0 Reference Number Issue Resolution The default application-model has changed from web to voice The show cell application-performance command does not show any results. Customers interested in continuing to use web model, in particular APC Internet customers, will be required to manually configure set-application-model web statements to any decision-policy blocks including the global decision-policy. A lack of any application-model statement in the running-config in Version 4.0 implies that the voice application-model is in use. First check if the Supernode command has been configured. This command is required to populate data for many commands that need aggregated data. Another reason for lack of data would be the failure of the pgsql service is show medic detail. If the pgsql service is not in the PASS state, the show commands show count, show subnet-pair, and show outage-not-res will not show the hive-wide aggregated data. Run the medic call database reinitialize command.! CAUTION: CAUTION: Running the medic call database re-initialize command should be used as a last resort. This command will wipe clean the entire trending database. It is important to make sure that the pgsql service is down before considering using this command. 5 of 7 14

15 Fixes in Version 4.0 Reference Number Issue Resolution Module chatter binds to the default interface only, and module cna-agent (the CNA server s internal CNA agent) requires additional commands to complete binding to a non-default interface. Module chatter has been deprecated under Interface. Currently, module chatter can only bind to the default Ethernet 0 interface. Module cna-agent can be bound to a different interface. The default is Ethernet 0. To bind module cna-agent to a different interface, use the following commands: configure terminal interface Ethernet <num> module cna-agent chatter remove cna-agent <ip-address of old interface> restart decision-maker The show subnet-pair information command may not always find a subnet pair in a multiple server hive Too many relative alarms are generated by chatter default settings. The show subnet-pair command can be used to lookup the subnet pair associated with a given IP pair. This can be quite common when interested in looking up the subnet pair associated with a pair of chatter agents. The query is only performed in the supernode, irrespective of the server in the hive on which the command has been issued. If the subnet pair associated with the IP pair does not exist in the supernode, but it does exist in another server, the subnet pair will not be found. Use the "local" option of the show subnet-pair command under remote-exec to ensure that the query is performed in all servers. Chatter default setting is changed to alarm-relative disable. 6 of 7 Issue 3 September

16 Application Assurance Networking Release Notes for Software Version 4.0 Reference Number Issue Resolution When using SNMP polling, the ifdescr uses the IP address incorrectly The show nodes command takes a long time to display node information. The string (ifdescr) option for module engine link polling interface has been removed. With this release, only integers (ifindex) and IP addresses are allowed. The show nodes command now includes a cache for IP or DNS name queries. As a result of the cache, subsequent queries are not necessary. The show nodes command now displays node information quickly Manually re-sorting the charts in a Trend series is not allowed The erase chatter-config command which erases all chatter configurations except the CNA agent cna-agent registrations may not cleanly succeed in erasing. Version 4.0 has implemented an automatic sort for the charts in a Trend series. Use the medic call chatter restart command after executing the erase chatter-config command. Zone names Root and Unassigned are reserved names and cannot be used for user-defined zone names. Note: Note: Zone names are case sensitive. 7 of 7 16

17 Known Issues in Version 4.0 Known Issues in Version 4.0 The following table lists all know issues and workarounds for Version 4.0. In Table 5 lists all the known issues and workarounds. Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround 7565 If the CNA login window is canceled, the launch page locks and the Viewer can not be launched If module cna-agent is moved from the default interface to an interface on a different subnet, this results in the change of the source subnet for the server-based data in decision-maker. As new measurements arrive, new subnet-pairs are created, but the old subnet-pairs with out-dated data continue to exist and contribute to aggregate {APR, availability} values When a CNA Agent is moved from one zone to another, measurements from that point forward contribute to the cells associated with the agent's new zone. However, older measurements continue to contribute to the cells associated with the agent's old zone. This can only be cleared with a restart of the decision maker process. Restart the browser and navigate to the CNA server home page. If the browser does not close, a force-kill of the browser application/process may be necessary. For example, by using End Process in Windows Task Manager. Restart the decision maker process. Restart the decision-maker process. 1 of 8 Issue 3 September

18 Application Assurance Networking Release Notes for Software Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround The CNA Agent Device is not compatible with the Cisco 65xx switches with POE when both sides are set to 100/FULL The VMM Client tab fails to load in the CNA Viewer due to mismatched security certificates Some CNA Agent platforms' registration attempts may quietly fail Backward compatibility between a Version 4.0 CNA Agent Device and a Version 3.0 CNA Server Time zone discrepancy between the CNA Viewer and VMM client. Change the Cisco device to AUTO/AUTO with the CNA Agent Device still in 100/FULL. This change allows the CNA Agent Devices to attempt to establish connectivity. A check has been implemented to spot this situation; however, the check introduces a delay of seconds in the case where it is successful. That is when things work fine it will significantly reduce the responsiveness of the interface. It is possible that the registration may be failing due to inaccurate date/time on the CNA agent platform. Please ensure that the CNA Agent platform has a reasonably accurate current time. Backward compatibility between the a Version 4.0 CNA Agent Device and a Version 3.0 CNA Server in not supported. For assistance, please contact Technical Support at The time and date information in the CNA Viewer is displayed in the time zone of the CNA server location. The VMM aggregator also uses this convention. However, when a VMM client is started within the CNA Viewer, it will use the timezone of the local machine. This may cause some confusion to the customer. 2 of 8 18

19 Known Issues in Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround A saved results file from the CNA Viewer is blank Chatter TCP tests directed toward some agent types may fail Ping command may fail if a large packet size is used Custom trend reports CPU temperature at.5 degrees celsius-centigrade. Some.csv files may be saved without content and will show up as blank when opened using Excel. There is no workaround at this time. All chatter TCP tests directed to IP Phone CNA Agents will fail, as IP Phones will not respond to TCP connection attempts on any port. All chatter TCP tests to CNA Agent Devices will fail if they are directed to Port 80, the default port for the TCP test. For TCP tests directed to CNA Agent Devices to succeed, they must be directed to Port 22 on the CNA Agent Device using the active-measurement name tcp command in the chatter configuration module of the CLI. The maximum packet size supported for the ping command is The CPU temperature custom trend report is not supported in Version 4.0. This custom trend report is still visible in the CNA Viewer; however, it is obsolete and will be removed in a later version of the software. 3 of 8 Issue 3 September

20 Application Assurance Networking Release Notes for Software Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround Charts are unable to display negative values The report view does not refresh when moving between servers in a hive that reside in different timezones. There are some cases where negative values are used in the product. One example is the case of Traceroute HopRTTs some of which may be marked negative implying that a hop, further away than another, responded faster in the traceroute. When this information is displayed in the trends and charts, only positive values are plotted as the charting system does not handle negative values. The chart legend may, however, show the negative values. There is no workaround at this time. Configure hives using Best Practices for configuring hives and timezones. Best Practices: 1. Solid NTP configurations for all Servers in the HIVE, at very minimum synchronized to multiple instances of "Official Corporate Time". 2. Single timezone for all servers in the hive. When customers employ both of the above best practices, the problems cited in this Known Issue will be avoided. When customers do not employ both of the above best practices, the customer must take responsibility for adjusting all time-based queries between device agents. 4 of 8 20

21 Known Issues in Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround RTP test data is preferred over ICMP data when computing agent-based APR (application performance rating) Adding a new trend line to a graph or changing the time range can result in a blank graph Some commands are not allowed to be run under remote-exec mode and if the user tries to issue them an error is generated. However a few other commands that should be prevented are nevertheless allowed. If either ICMP test or RTP test detects an outage, this information is used for computing the corresponding application performance rating. However, in the absence of an outage, RTP data is preferred over ICMP data. If RTP test is disabled, out dated data may continue to impact APR computation. To clear outdated RTP data, a restart of the decision maker process is required. Two trend lines that have different sample rates, could result in a blank graph. In this case, avoid mixing trends variables. In other cases you can use the units of the trend variable to determine if the variables should be plotted together. If the units do not match, then they could possible have different sample rates. The following commands are NOT recommended to be run under remote-exec mode: chatter node chatter remove-cna-agent disable logout terminal tree backup copy export halt 5 of 8 Issue 3 September

22 Application Assurance Networking Release Notes for Software Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround Serial synchronization between CNA servers in a hive can lead to the re-appereance of removed CNA agents when the command chatter remove-cna-agent not-assigned is issued Upgrade to Version 4.0 fails when license for Version 3.1.x is found In large hives, running the restore image command over remote-exec can overwhelm the FTP server hosting the CNA image IBM x305 and IBM x306 fail to upgrade to Occasionally CNA servers do not resolve the hostnames. Ensure all agents are assigned to a zone. Or use the command module chatter scheduling use-unassigned-agent disable A license is no longer needed for Version 4.0. The license file should be removed, and the server should be reloaded, prior to the upgrade to Version 4.0 See the Upgrading the CNA server and removal of the license file procedure. Restore image can be run individually per server. IBM x305 and IBM x306 servers cannot be upgraded to Version They can, however, be upgraded directly from Version or earlier to Version 4.0. See Upgrading the CNA server and removal of the license file in the Changes in Version 4.0 section. If the IP address of a CNA server is not resolved to a name via DNS in the output of show hive, the workaround is to use the subnet-alias command to associate a name to the IP address. The subnet-alias command overrides any DNS resolution. 6 of 8 22

23 Known Issues in Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround Leaving a hive and removing the CNA Agents creates an out-of-sync hive The show statistics link-monitor command may contain some invalid data for the billing link. When a server leaves the hive and then rejoins the hive, there might be situations where a zone may end up with both a cna-agent subnet assignment, and a cna-agent assignment. In this case, the zone where that happens will not be present in the running config. The workaround is to remove either of the two cna-agent statements. The link billing formula max-avg-percentile-daily-in-avg -percentile-daily-out is no longer supported. 7 of 8 Issue 3 September

24 Application Assurance Networking Release Notes for Software Version 4.0 Table 5: Known Issues and Workarounds Reference Number Known Issue Workaround The existing phone registration type is not re-classified in 3.x -> 4.0 upgrade If one or more restricted IP Phone CNA Agents are activated, the total number of activated CNA Agents is limited to 64. Normally, if the restricted CNA agents are then removed or deactivated, the total number of active agents can increase up to the value of max-active-agents, if the number of registered agents is sufficient. However, if the cna-agent subnet a.b.c.d/e command has been used previously to assign agents to zones based on their subnets, any registered phones in those subnets that were not already activated will not become activated when the restricted agents are removed. The 96xx phones agents are no longer considered restricted agents, but the upgrade script to 4.0 does not handle the status update. The workaround to this issue is to use the chatter remove-cna-agent command for the old registrations and then reboot the phones to get a fresh registration. If the cna-agent subnet a.b.c.d/e command is used to assign CNA Agents to zones, some of the registered agents in those subnets may need to be rebooted and/or re-registered when a restricted phone is deactivated, in order to activate the maximum number of agents according to the value of max-active-agents. 8 of 8 24

25 Technical Support Technical Support To contact Avaya Technical Support: From the United States: Outside North America: Contact your distributor From the Internet Documentation Feedback If you have comments about the technical accuracy or general quality of this document, please send us an message at Please cite the document title, part number, and page reference, if appropriate. Issue 3 September

26 Application Assurance Networking Release Notes for Software Version