![]() |
Table Of Contents
Release Notes for the Cisco Mobile Wireless Transport Manager 6.1.6
Supported IOS Releases in MWTM 6.1.6
INSTANCE_NUMBER on Single-Instance ITP
Multiprocessor Multithread Vendor Exception
Credentials for Nodes with Multiple IP Address
Symbol Style and Line Style Preferences
Avoid Colon (:) in ITP Object Names
Appearance of MSU Rates Real-Time Charts
Provisioning Problem Due to Credentials
Special Characters in ITP AS/ASP/Linkset Names in Reports
Using MWTM With the RealPlayer Plugin Installed
APN and GTP Reports Disabled for GGSN on Patch Upgrade
Historical Statistics Collection During Upgrade
New Features and Resolved MWTM Caveats
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco Mobile Wireless Transport Manager 6.1.6
Date: May, 2011
These release notes describe features added, caveats, known bugs, and other important information for installing and using Cisco Mobile Wireless Transport Manager (MWTM) 6.1.6.
Note
You can access the most current Cisco documentation, including these release notes, online at:
http://www.cisco.com/en/US/products/ps6472/tsd_products_support_series_home.html.For the latest MWTM information and software updates, go to http://www.cisco.com/go/mwtm.
Contents
These release notes contain:
•
New Features and Resolved MWTM Caveats
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
What's New in MWTM 6.1.6
Table 1 lists the new features in MWTM 6.1.6.
Supported IOS Releases in MWTM 6.1.6
This section contains the following tables:
•
Table 2, Supported IOS Releases for ITP Devices
•
Table 3, Supported IOS Releases for IPRAN Devices
•
Table 4, Supported IOS Releases for mSEF Devices
1. "Other" may include: Cisco 2650, Cisco 2651, Cisco 2811, Cisco 7204, Cisco 7206, Cisco 7301, Cisco 7507, and Cisco 7513.
2. CDT software release, not an IOS release.
Unsupported IOS Releases
The MWTM no longer supports the IOS releases listed in Table 4:
Table 5
Unsupported IOS Releases in MWTM 6.1.6(contd)
Limitations and Restrictions
This section describes limitations and restrictions that are associated with the MWTM:
•
INSTANCE_NUMBER on Single-Instance ITP
•
Multiprocessor Multithread Vendor Exception
•
Credentials for Nodes with Multiple IP Address
•
Symbol Style and Line Style Preferences
•
Avoid Colon (:) in ITP Object Names
•
Using MWTM With the RealPlayer Plugin Installed
•
APN and GTP Reports Disabled for GGSN on Patch Upgrade
•
Historical Statistics Collection During Upgrade
Provisioning Timeout
When using the MWTM provisioning feature to modify the management interface, sometimes the operation fails with this message:
No prompt responseThis response can occur when changing the duplex or speed attributes for the Ethernet interface. The response can also occur for other interface attributes that affect IP connectivity between the MWTM and the device.
The default setting for a provisioning operation timeout is 50 seconds. As a workaround, the system administrator can increase the TGS_OP_TIMEOUT attribute in the System.properties file to a higher value. You must restart the MWTM server for this change to take effect.
SSH-Enabled Nodes
The MWTM Node > Home Page right-click menu option does not work correctly for the following SSH-enabled IP Transfer Point (ITP) nodes:
•
Cisco 2600
•
Cisco 7200
•
Cisco 7300
•
Cisco 7500
•
Cisco 7600
The browser launches, as expected, but the user is not prompted for login information.
Note
This limitation exists for any ITP node running the 12.2(x) IOS with SSH enabled.
INSTANCE_NUMBER on Single-Instance ITP
Symptom If a command with INSTANCE_NUMBER is included in the UserCommands.ts file, the instance number will appear on all nodes in the GUI. If you run this command on a node that does not have multi-instance enabled, it fails.
Workaround
If you have a network with both single-instance and multi-instance nodes, you must configure a separate set of troubleshooting commands for each node type in the UserCommands.ts file. Do this by grouping the commands for each type under a separate category.
Multiprocessor Multithread Vendor Exception
Sometimes when using the MWTM client on a Solaris multi-processor computer, an exception occurs when the topology window is open and you are manipulating views. The workaround is to close the topology window, then reopen it.
External SSH Client Use
If you enable the MWTM terminal proxy (mwtm termproxy) and use an external SSH terminal client to connect to a device, you might receive a warning message indicating a man-in-the-middle attack. This warning occurs because the MWTM server is operating as an SSH proxy to the device. In this scenario, ignore any warning messages indicating a man-in-the-middle attack. These warnings do not occur if you disable the MWTM terminal proxy or if you use the SSH terminal included with the MWTM.
SSH and Telnet Terminal
The SSH and Telnet terminals that are included with the MWTM provide basic terminal functionality. They do not support non-English character sets or the UNIX curses library (for example, colors). If these, or other, additional terminal functions are required, you can configure the MWTM to use an external SSH or Telnet program.
Tooltip Text Truncated
The Firefox 2 browser truncates tool tips that contain long text strings (see Firefox bug 218223). The MWTM contains only a few tool tips that exhibit this problem. The problem is resolved in Firefox 3. The problem does not occur when using the Internet Explorer (IE) browser.
Credentials for Nodes with Multiple IP Address
Credentials for a node are associated with a unique IP address. If a node has more than one accessible IP address, functions that require credentials might not resolve to a credential based on the selected IP address, and the requested function would fail. The MWTM functions that require credentials include:
•
Discovery of ONS and RAN_SVC nodes
•
Troubleshooting
•
Provisioning
•
Route, MLR Address, and Global Title Translation (GTT) table deployment
To work around this limitation, specify the credentials for all accessible IP addresses for a node.
Unprintable Characters
CSCse81393
In various GUI and web pages, simple text fields might contain unprintable characters. An example is the Model Name PID field for a RAN service (RAN_SVC) card in an ONS chassis. This is a cosmetic problem and does not affect functionality.
Symbol Style and Line Style Preferences
CSCsg83861
The preferences dialog box of the MWTM client interface allows you to customize the way that data series appear in charts. You can specify series color, line style, and symbol style. However, symbol style and line style preferences do not work when displaying real-time charts for MSU rates and for RAN backhauls and shorthauls.
Java Exception
CSCsh15638
The following exception with corresponding stacktrace can occur. The MWTM captures this exception in the sgmConsoleLog.txt file:
java.net.SocketException: Broken pipeThis exception can occur when users access the MWTM web interface and frequently abort connections while the server is under heavy load (for example, during discovery). Clicking the Stop button on the web browser or navigating to a different web page before the current page finishes loading can cause this exception to occur.
Note
The root cause of this condition is an internal bug in the Tomcat web application that ships with this release of the MWTM.
You can safely ignore these log messages.
Avoid Colon (:) in ITP Object Names
CSCsh58070
The following error messages may appear when performing these operations:
These error messages occur when ITP linkset, AS, and ASP names contain a colon (:). To prevent these errors, do not use the colon (:) in ITP linkset, AS, and ASP names.
Note
In general, the MWTM does not support ITP AS, ASP, or linkset names that contain special characters, such as: !@#$%^&*()+=[]{};',./\:"<>?|
The supported characters in ITP AS, ASP, and linkset names are: [a-z], [A-Z], [0-9], - and _.
Unprintable Characters in GUI
On some GUI windows and web pages simple text fields might contain unprintable characters. An example is the Model Name PID field for a RAN service (RAN_SVC) card in an ONS chassis. This might occur one some RAN_SVC cards in an ONS chassis.
Appearance of MSU Rates Real-Time Charts
The preferences dialog box of the MWTM client interface allows you to customize the way that data series appear in charts. You can specify series color, line style, and symbol style. However, symbol style and line style preferences do not work when displaying real-time charts for MSU rates and for RAN backhauls and shorthauls.
Provisioning Problem Due to Credentials
After switching the SNMP IP address, provisioning stops working due to credentials. Credentials for a node are associated with a unique IP address. If a node has more than one accessible IP address, functions that require credentials might not resolve to a credential based on the selected IP address, and the requested function would fail. The MWTM functions that require credentials include:
•
Discovery of ONS and RAN_SVC nodes
•
Troubleshooting
•
Provisioning
•
Route and Global Title Translation (GTT) table deployment
This might occur with nodes with multiple, accessible IP addresses with credentials set for a subset of those IP addresses. To work around this limitation, specify credentials for all accessible IP addresses for a node.
Special Characters in ITP AS/ASP/Linkset Names in Reports
The following error messages might appear when performing these operations:
The error messages occur when ITP linkset, AS, and ASP names contain a colon (:). To work around this problem, remove the colon (:) from ITP linkset, AS, and ASP names.
Using MWTM With the RealPlayer Plugin Installed
If you use a computer that has the RealPlayer plugin installed, the Provision launch window will not work properly. When you change types on the Provision launch window, the provisioned item list will not refresh.
This is a known issue with the RealPlayer plugin. This issue occurs on both Internet Explorer and Firefox browsers.
Disable the RealPlayer plugin to use the Provision launch window. If you use Internet Explorer, you might need to reboot your computer after disabling the plugin. If you use Firefox, you might need to restart your browser after disabling the plugin.
Online Help System
The online help system is updated only during major release updates. New features added in patch releases (for example, 6.0.4) are not contained in the online help system. Instead, new features are documented in the release notes for the patch release.
APN and GTP Reports Disabled for GGSN on Patch Upgrade
CSCtj21269
If you enable GGSN reporting in MWTM 6.1.1 and then upgrade to MWTM 6.1.2 and apply the latest service pack, then APN reports are disabled. You may have to re-enable the APN reports even if they were previously enabled.
To enable APN reports, execute mwtm statreps apn command or from the web interface select "Reports" and enable APN.
Historical Statistics Collection During Upgrade
When you upgrade to MWTM 6.1.6 from an earlier version, there may be a temporary stop in the collection of data. This could result in a time gap shown in historical reports for shorter interval reports (For example, 15 minute reports). No intervention is required for collection to resume.
Important Notes
This section contains important notes about RAN Backhaul Utilization.
RAN Backhaul Utilization
When the backhaul utilization for transmit traffic exceeds 100%, the likely cause is oversubscription of the shorthaul links that constitute the backhaul. The backhaul utilization is the amount of traffic that the system attempted to send, not the amount that was actually sent. If utilization is greater than 100%, you should see queue drops or other errors during the same time period. A backhaul utilization of greater than 100% is possible for a heavily loaded link with some occasional oversubscription.
New Features and Resolved MWTM Caveats
The following new features and bugs fixes have been fixed in MWTM 6.1.6:
Open MWTM Caveats
This section describes caveats that exist in the MWTM 6.1.6 software.
•
CSCsg92892
Symptom When provisioning ITP nodes from the Provision tab of the web interface, some provisioning operations might fail on the node with these symptoms and conditions:
Workaround
None. The user must know the ITP card information and specify correct values in the provisioning request.
•
CSCsz16365
Symptom When provisioning IPRAN nodes from the Provision tab of the web interface, some provisioning operations might fail on the node with these symptoms and conditions:
Workaround
None. The user must know the card/slot/module type information and submit provision requests based on the capabilities of the card.
•
CSCsz56999
Symptom When provisioning IPRAN nodes from the Provision tab of the web interface, some provisioning operations might fail on the node with these symptoms and conditions:
Workaround
None. The user must know the card type information and submit provision requests based on the capabilities of the card.
•
CSCsu02993
Symptom When IOS running-config contains the following characters in the object name, MWTM web user interface may exhibit unexpected behavior:
Double quote (")
Less than (<)
Conditions
When IOS running-config contains following characters in the object name:
Double quote (")
Less than (<)
Additional MWTM provisioning or other functions may behave unexpectedly when IOS running-config contains following characters:
!,#,$,%,^,*,(,),',+,=, and ,
Workaround
Remove special characters from IOS running-config.
•
CSCtf51338
Symptom The MWTM web client is very slow or unresponsive when expanding the Default View node in the inventory tree.
Conditions
Internet Explorer version 6 is being used as the web browser. The network latency between the web client and the MWTM server is very high. MWTM is being used to monitor a medium-sized or large network.
Workaround
Use a different web browser such as Firefox or Internet Explorer 7 or later.
•
CSCtf56323
Symptom When provisioning IPRAN interfaces with a VRF from the Provision tab of the web interface, provisioning operation might fail with "Incompatible with xconnect command on <x> - command rejected." Similarly while provisioning a PWE3 Xconnect on IPRAN object, the provisioning operation might fail with "Incompatible with ip vrf command on <x> - command rejected."
Conditions
Both PWE3 Xconnect and VRF appear to be mutually exclusive on Parent-Child interfaces. On some interfaces, if Parent has PWE3 Xconnect then child interface of the parent cannot add VRF and vice versa.
Workaround
None. The user must gain knowledge about the parent-child interfaces and specify correct values in the provisioning request.
•
CSCtf54835
Symptom When provisioning IPRAN Gigabit or Ten Gigabit Ethernet interfaces with a VRF from the Provision tab of the web interface, the provisioning operation might fail with "% Invalid input detected at '^' marker."
Conditions
Gigabit and Ten Gigabit Ethernet interfaces can be provisioned either with switchport or VRF. When the Ethernet interface is already set as switchport, the user is attempting to configure VRF in the MWTM provision request.
Workaround
None. The user must have knowledge about the interfaces and specify correct values in the provisioning request.
Open Device Caveats
•
CSCsz69451
The historical and real-time KPIs for the GGSN R9 from the CISCO-GGSN-EXT-MIB always have the value 0 due to an IOS defect in 12.4(22)YE.
The following realtime KPIs are impacted:
–
GTP Throughput Upstream Bytes - cGgsnExtUpstreamByteCount
–
GTP Throughput Downstream Bytes - cGgsnExtDownstreamByteCount
–
GTP Throughput Upstream Packets - cGgsnExtUpstreamPktCount
–
GTP Throughput Downstream Packets - cGgsnExtDownstreamPktCount
–
Mobile Stations With Active PDP Contexts - cGgsnExtActivatedMs
–
PDP PPP-Regen Interfaces Created - cGgsnExtGtpPppRegenCreatedIntfs
–
Active PDP Contexts with Direct Tunnel - cGgsnExtGtpDtActivePDPs
–
PDP Contexts Deleted without waiting for the SGSN - cGgsnExtNoWaitSgsnLocalDelPDPs
–
PDP Contexts Deleted without sending to the SGSN - cGgsnExtNoReqSgsnLocalDelPDPs
–
Update PDP Context Requests Sent - cGgsnExtSentPdpUpdateReqs
–
Update PDP Context Responses Received - cGgsnExtRcvdSuccPdpUpdateResponses
–
COA Messages Received - cGgsnExtRcvdCoaMsgs
–
COA Messages Dropped - cGgsnExtDiscardedCoaMsgs
–
COA QOS Updates Sent - cGgsnExtSentCoaUpdateReqs
–
Error Indication Messages Sent - cGgsnExtSentErrorIndications
–
Error Indication Messages Received - cGgsnExtRcvdErrorIndications
–
Direct Tunnels Enabled - cGgsnExtTotalDtEnabled
–
Error Indications for DT PDP Contexts - cGgsnExtRcvdDtPdpErrorIndications
–
DT PDP Contexts Deleted due to Update Response - cGgsnExtTotalDtUpdFailDeletedPDPs
Related Documentation
Use this document in conjunction with the following documents:
•
User Guide for the Cisco Mobile Wireless Transport Manager 6.1.6
http://www.cisco.com/en/US/products/ps6472/products_user_guide_list.html
•
Installation Guide for the Cisco Mobile Wireless Transport Manager 6.1.6
http://www.cisco.com/en/US/products/ps6472/prod_installation_guides_list.html
•
OSS Integration Guide for the Cisco Mobile Wireless Transport Manager 6.1.6
http://www.cisco.com/en/US/products/ps6472/products_programming_reference_guides_list.html
•
Supported IOS Releases for the Cisco Mobile Wireless Transport Manager and the Cisco Signaling Gateway Manager
http://www.cisco.com/en/US/products/ps6472/products_device_support_tables_list.html
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2011 Cisco Systems, Inc. All rights reserved.